Patent Application
20250234356
The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for transmitting or receiving a downlink/uplink radio signal in a wireless communication system.
Generally, a wireless communication system is developing to diversely cover a wide range to provide such a communication service as an audio communication service, a data communication service and the like. The wireless communication is a sort of a multiple access system capable of supporting communications with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). For example, the multiple access system may be any of a code division multiple access (CDMA) system, a frequency division multiple access (FDMA) system, a time division multiple access (TDMA) system, an orthogonal frequency division multiple access (OFDMA) system, and a single carrier frequency division multiple access (SC-FDMA) system.
An object of the present disclosure is to provide a method of efficiently performing wireless signal transmission/reception procedures and an apparatus therefor.
It will be appreciated by persons skilled in the art that the objects that could be achieved with the present disclosure are not limited to what has been particularly described hereinabove and the above and other objects that the present disclosure could achieve will be more clearly understood from the following detailed description.
According to an aspect, a method of receiving a signal by a user equipment (UE) in a wireless communication system includes monitoring physical downlink control channel (PDCCH) candidates, and detecting downlink control channel (DCI) through monitoring of the PDCCH candidates. The DCI may support multi-cell scheduling based on cell combinations regarding a plurality of cells configured in the UE. A payload size of the DCI may be determined based on a first cell combination in which a total number of DCI bits required for co-scheduled cells from among the cell combinations is the maximum.
The payload of the DCI may be determined based on the summed size of all DCI fields for the first cell combination.
Cells co-scheduled through the DCI may be indicated as one of the cell combinations.
The DCI may include first DCI field-related information for each of a first cell and a second cell which are co-scheduled. Based on that the first cell has a lower serving cell index than the second cell, the first DCI field-related information for the first cell may be located before the first DCI field-related information for the second cell in the DCI. The first DCI field may include at least one of a modulation and coding scheme (MCS) field, a new data indicator (NDI) field, a redundancy version (RV) field, a hybrid automatic repeat request (HARQ) process ID field, a frequency domain resource allocation (FDRA) field, a time domain resource allocation (TDRA) field, and a transmission power command (TPC) field for a physical uplink shared channel (PUSCH).
Transmission or reception of a scheduled signal may be performed only for remaining cells excluding at least one invalid cell from among cells co-scheduled through the DCI. The at least one invalid cell may include at least one of a deactivated secondary cell (SCell), a cell operating as a dormant bandwidth part (BWP), a cell of which resources allocated through the DCI overlap semi-static resources in which uplink (UL)/downlink (DL) directions are configured differently, and a cell of which frequency resource information indicated by the DCI is invalid. Hybrid automatic repeat request-acknowledgement (HARQ-ACK) information may be configured for remaining cells excluding the at least one invalid cell or may be configured to include negative acknowledgement (NACK) information for the at least one invalid cell. The DCI field values for at least one invalid cell in the DCI may be configured based on information for a specific bandwidth part (BWP).
According to another aspect, a processor-readable recording medium having recorded thereon a program for performing the method may be provided.
According to another aspect, a UE for performing the method may be provided.
According to another aspect, a device for controlling a UE for performing the method may be provided.
According to an aspect, a method of transmitting a signal by a BS in a wireless communication system may include generating downlink control information (DCI), and transmitting the DCI to the UE based on at least one of physical downlink control channel (PDCCH) candidates of the UE. The DCI may support multi-cell scheduling based on cell combinations for multiple cells configured for the UE. A payload size of the DCI may be determined based on a first cell combination having the largest total number of DCI bits required for co-scheduled cells from among the cell combinations.
According to another aspect, a BS for performing the method may be provided.
According to at least one of various embodiments wireless signal transmission/reception procedures can be performed efficiently.
It will be appreciated by persons skilled in the art that the technical effects that could be achieved with the present disclosure are not limited to what has been particularly described hereinabove and the above and other technical effects that the present disclosure could achieve will be more clearly understood from the following detailed description.
Embodiments of the present disclosure are applicable to a variety of wireless access technologies such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), and single carrier frequency division multiple access (SC-FDMA). CDMA can be implemented as a radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented as a radio technology such as Global System for Mobile communications (GSM)/General Packet Radio Service (GPRS)/Enhanced Data Rates for GSM Evolution (EDGE). OFDMA can be implemented as a radio technology such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wireless Fidelity (Wi-Fi)), IEEE 802.16 (Worldwide interoperability for Microwave Access (WiMAX)), IEEE 802.20, and Evolved UTRA (E-UTRA). UTRA is a part of Universal Mobile Telecommunications System (UMTS). 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is part of Evolved UMTS (E-UMTS) using E-UTRA, and LTE-Advanced (A) is an evolved version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE/LTE-A.
As more and more communication devices require a larger communication capacity, there is a need for mobile broadband communication enhanced over conventional radio access technology (RAT). In addition, massive Machine Type Communications (MTC) capable of providing a variety of services anywhere and anytime by connecting multiple devices and objects is another important issue to be considered for next generation communications. Communication system design considering services/UEs sensitive to reliability and latency is also under discussion. As such, introduction of new radio access technology considering enhanced mobile broadband communication (eMBB), massive MTC, and Ultra-Reliable and Low Latency Communication (URLLC) is being discussed. In the present disclosure, for simplicity, this technology will be referred to as NR (New Radio or New RAT).
For the sake of clarity, 3GPP NR is mainly described, but the technical idea of the present disclosure is not limited thereto.
In the present disclosure, the term “set/setting” may be replaced with “configure/configuration,” and both may be used interchangeably. Further, a conditional expression (e.g., “if”, “in a case”, or “when”) may be replaced by “based on that” or “in a state/status.” In addition, an operation or software/hardware (SW/HW) configuration of a user equipment (UE)/base station (BS) may be derived/understood based on satisfaction of a corresponding condition. When a process on a receiving (or transmitting) side may be derived/understood from a process on the transmitting (or receiving) side in signal transmission/reception between wireless communication devices (e.g., a BS and a UE), its description may be omitted. Signal determination/generation/encoding/transmission of the transmitting side, for example, may be understood as signal monitoring reception/decoding/determination of the receiving side. Further, when it is said that a UE performs (or does not perform) a specific operation, this may also be interpreted as that a BS expects/assumes (or does not expect/assume) that the UE performs the specific operation. When it is said that a BS performs (or does not perform) a specific operation, this may also be interpreted as that a UE expects/assumes (or does not expect/assume) that the BS performs the specific operation. In the following description, sections, embodiments, examples, options, methods, schemes, and so on are distinguished from each other and indexed, for convenience of description, which does not mean that each of them necessarily constitutes an independent disclosure or that each of them should be implemented only individually. Unless explicitly contradicting each other, it may be derived/understood that at least some of the sections, embodiments, examples, options, methods, schemes, and so on may be implemented in combination or may be omitted.
In a wireless communication system, a user equipment (UE) receives information through downlink (DL) from a base station (BS) and transmit information to the BS through uplink (UL). The information transmitted and received by the BS and the UE includes data and various control information and includes various physical channels according to type/usage of the information transmitted and received by the UE and the BS.
When a UE is powered on again from a power-off state or enters a new cell, the UE performs an initial cell search procedure, such as establishment of synchronization with a BS, in step S101. To this end, the UE receives a synchronization signal block (SSB) from the BS. The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). The UE establishes synchronization with the BS based on the PSS/SSS and acquires information such as a cell identity (ID). The UE may acquire broadcast information in a cell based on the PBCH. The UE may receive a DL reference signal (RS) in an initial cell search procedure to monitor a DL channel status.
After initial cell search, the UE may acquire more specific system information by receiving a physical downlink control channel (PDCCH) and receiving a physical downlink shared channel (PDSCH) based on information of the PDCCH in step S102.
The UE may perform a random access procedure to access the BS in steps S103 to S106. For random access, the UE may transmit a preamble to the BS on a physical random access channel (PRACH) (S103) and receive a response message for preamble on a PDCCH and a PDSCH corresponding to the PDCCH (S104). In the case of contention-based random access, the UE may perform a contention resolution procedure by further transmitting the PRACH (S105) and receiving a PDCCH and a PDSCH corresponding to the PDCCH (S106).
After the foregoing procedure, the UE may receive a PDCCH/PDSCH (S107) and transmit a physical uplink shared channel (PUSCH)/physical uplink control channel (PUCCH) (S108), as a general downlink/uplink signal transmission procedure. Control information transmitted from the UE to the BS is referred to as uplink control information (UCI). The UCI includes hybrid automatic repeat and request acknowledgement/negative-acknowledgement (HARQ-ACK/NACK), scheduling request (SR), channel state information (CSI), etc. The CSI includes a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), etc. While the UCI is transmitted on a PUCCH in general, the UCI may be transmitted on a PUSCH when control information and traffic data need to be simultaneously transmitted. In addition, the UCI may be aperiodically transmitted through a PUSCH according to request/command of a network.
The purpose of the random access procedure (RACH procedure) is not limited to initial network access (e.g., S103 to S106). That is, the random access procedure may be used for various purposes. For example, the random access procedure may be used for at least one of an RRC connection re-establishment procedure, handover, UE-triggered UL data transmission, transition from RRC_INACTIVE, SCell time alignment, system information request, beam failure recovery, or UL resource request. However, the random access procedure is not limited thereto. The UE may acquire UL synchronization and/or UL transmission resources from the random access procedure.
Table 1 exemplarily shows that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to the SCS when the normal CP is used.
Table 2 illustrates that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to the SCS when the extended CP is used.
The structure of the frame is merely an example. The number of subframes, the number of slots, and the number of symbols in a frame may vary.
In the NR system, OFDM numerology (e.g., SCS) may be configured differently for a plurality of cells aggregated for one UE. Accordingly, the (absolute time) duration of a time resource (e.g., an SF, a slot or a TTI) (for simplicity, referred to as a time unit (TU)) consisting of the same number of symbols may be configured differently among the aggregated cells. Here, the symbols may include an OFDM symbol (or a CP-OFDM symbol) and an SC-FDMA symbol (or a discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbol).
Each physical channel will be described below in greater detail.
The PDCCH delivers DCI. For example, the PDCCH (i.e., DCI) may carry information about a transport format and resource allocation of a DL shared channel (DL-SCH), resource allocation information of an uplink shared channel (UL-SCH), paging information on a paging channel (PCH), system information on the DL-SCH, information on resource allocation of a higher-layer control message such as an RAR transmitted on a PDSCH, a transmit power control command, information about activation/release of configured scheduling, and so on. The DCI includes a cyclic redundancy check (CRC). The CRC is masked with various identifiers (IDs) (e.g., a radio network temporary identifier (RNTI)) according to an owner or usage of the PDCCH. For example, if the PDCCH is for a specific UE, the CRC is masked by a UE ID (e.g., cell-RNTI (C-RNTI)). If the PDCCH is for a paging message, the CRC is masked by a paging-RNTI (P-RNTI). If the PDCCH is for system information (e.g., a system information block (SIB)), the CRC is masked by a system information RNTI (SI-RNTI). When the PDCCH is for an RAR, the CRC is masked by a random access-RNTI (RA-RNTI).
The PDCCH includes 1, 2, 4, 8, or 16 control channel elements (CCEs) according to its aggregation level (AL). A CCE is a logical allocation unit used to provide a PDCCH with a specific code rate according to a radio channel state. A CCE includes 6 resource element groups (REGs), each REG being defined by one OFDM symbol by one (P) RB. The PDCCH is transmitted in a control resource set (CORESET). A CORESET is defined as a set of REGs with a given numerology (e.g., an SCS, a CP length, and so on). A plurality of CORESETs for one UE may overlap with each other in the time/frequency domain. A CORESET may be configured by system information (e.g., a master information block (MIB)) or UE-specific higher-layer signaling (e.g., radio resource control (RRC) signaling). Specifically, the number of RBs and the number of symbols (3 at maximum) in the CORESET may be configured by higher-layer signaling.
For PDCCH reception/detection, the UE monitors PDCCH candidates. A PDCCH candidate is CCE(s) that the UE should monitor to detect a PDCCH. Each PDCCH candidate is defined as 1, 2, 4, 8, or 16 CCEs according to an AL. The monitoring includes (blind) decoding PDCCH candidates. A set of PDCCH candidates decoded by the UE are defined as a PDCCH search space (SS). An SS may be a common search space (CSS) or a UE-specific search space (USS). The UE may obtain DCI by monitoring PDCCH candidates in one or more SSs configured by an MIB or higher-layer signaling. Each CORESET is associated with one or more SSs, and each SS is associated with one CORESET. An SS may be defined based on the following parameters
* An occasion (e.g., time/frequency resources) in which the UE is to monitor PDCCH candidates is defined as a PDCCH (monitoring) occasion. One or more PDCCH (monitoring) occasions may be configured in a slot.
Table 3 shows the characteristics of each SS.
Table 4 shows DCI formats transmitted on the PDCCH.
DCI format 0_0 may be used to schedule a TB-based (or TB-level) PUSCH, and DCI format 0_1 may be used to schedule a TB-based (or TB-level) PUSCH or a code block group (CBG)-based (or CBG-level) PUSCH. DCI format 1_0 may be used to schedule a TB-based (or TB-level) PDSCH, and DCI format 1_1 may be used to schedule a TB-based (or TB-level) PDSCH or a CBG-based (or CBG-level) PDSCH (DL grant DCI). DCI format 0_0/0_1 may be referred to as UL grant DCI or UL scheduling information, and DCI format 1_0/1_1 may be referred to as DL grant DCI or DL scheduling information. DCI format 2_0 is used to deliver dynamic slot format information (e.g., a dynamic slot format indicator (SFI)) to a UE, and DCI format 2_1 is used to deliver DL pre-emption information to a UE. DCI format 2_0 and/or DCI format 2_1 may be delivered to a corresponding group of UEs on a group common PDCCH which is a PDCCH directed to a group of UEs.
DCI format 0_0 and DCI format 1_0 may be referred to as fallback DCI formats, whereas DCI format 0_1 and DCI format 1_1 may be referred to as non-fallback DCI formats. In the fallback DCI formats, a DCI size/field configuration is maintained to be the same irrespective of a UE configuration. In contrast, the DCI size/field configuration varies depending on a UE configuration in the non-fallback DCI formats.
The PDSCH conveys DL data (e.g., DL-shared channel transport block (DL-SCH TB)) and uses a modulation scheme such as quadrature phase shift keying (QPSK), 16-ary quadrature amplitude modulation (16QAM), 64QAM, or 256QAM. A TB is encoded into a codeword. The PDSCH may deliver up to two codewords. Scrambling and modulation mapping may be performed on a codeword basis, and modulation symbols generated from each codeword may be mapped to one or more layers. Each layer together with a demodulation reference signal (DMRS) is mapped to resources, and an OFDM symbol signal is generated from the mapped layer with the DMRS and transmitted through a corresponding antenna port.
The PUCCH delivers uplink control information (UCI). The UCI includes the following information.
Table 5 illustrates exemplary PUCCH formats. PUCCH formats may be divided into short PUCCHs (Formats 0 and 2) and long PUCCHs (Formats 1, 3, and 4) based on PUCCH transmission durations.
PUCCH format 0 conveys UCI of up to 2 bits and is mapped in a sequence-based manner, for transmission. Specifically, the UE transmits specific UCI to the BS by transmitting one of a plurality of sequences on a PUCCH of PUCCH format 0. Only when the UE transmits a positive SR, the UE transmits the PUCCH of PUCCH format 0 in PUCCH resources for a corresponding SR configuration.
PUCCH format 1 conveys UCI of up to 2 bits and modulation symbols of the UCI are spread with an orthogonal cover code (OCC) (which is configured differently whether frequency hopping is performed) in the time domain. The DMRS is transmitted in a symbol in which a modulation symbol is not transmitted (i.e., transmitted in time division multiplexing (TDM)).
PUCCH format 2 conveys UCI of more than 2 bits and modulation symbols of the DCI are transmitted in frequency division multiplexing (FDM) with the DMRS. The DMRS is located in symbols #1, #4, #7, and #10 of a given RB with a density of 1/3. A pseudo noise (PN) sequence is used for a DMRS sequence. For 2-symbol PUCCH format 2, frequency hopping may be activated.
PUCCH format 3 does not support UE multiplexing in the same PRBS, and conveys UCI of more than 2 bits. In other words, PUCCH resources of PUCCH format 3 do not include an OCC. Modulation symbols are transmitted in TDM with the DMRS.
PUCCH format 4 supports multiplexing of up to 4 UEs in the same PRBS, and conveys UCI of more than 2 bits. In other words, PUCCH resources of PUCCH format 3 include an OCC. Modulation symbols are transmitted in TDM with the DMRS.
The PUSCH delivers UL data (e.g., UL-shared channel transport block (UL-SCH TB)) and/or UCI based on a CP-OFDM waveform or a DFT-s-OFDM waveform. When the PUSCH is transmitted in the DFT-s-OFDM waveform, the UE transmits the PUSCH by transform precoding. For example, when transform precoding is impossible (e.g., disabled), the UE may transmit the PUSCH in the CP-OFDM waveform, while when transform precoding is possible (e.g., enabled), the UE may transmit the PUSCH in the CP-OFDM or DFT-s-OFDM waveform. A PUSCH transmission may be dynamically scheduled by a UL grant in DCI, or semi-statically scheduled by higher-layer (e.g., RRC) signaling (and/or Layer 1 (L1) signaling such as a PDCCH) (configured scheduling or configured grant). The PUSCH transmission may be performed in a codebook-based or non-codebook-based manner.
After receiving a PDSCH in slot #(n+K0) according to the scheduling information of slot #n, the UE may transmit UCI on a PUCCH in slot #(n+K1). The UCI may include an HARQ-ACK response to the PDSCH.
In the case where the PDSCH is configured to carry one TB at maximum, the HARQ-ACK response may be configured in one bit. In the case where the PDSCH is configured to carry up to two TBs, the HARQ-ACK response may be configured in two bits if spatial bundling is not configured and in one bit if spatial bundling is configured. When slot #(n+K1) is designated as an HARQ-ACK transmission timing for a plurality of PDSCHs, UCI transmitted in slot #(n+K1) includes HARQ-ACK responses to the plurality of PDSCHs.
Whether the UE should perform spatial bundling for an HARQ-ACK response may be configured for each cell group (e.g., by RRC/higher layer signaling). For example, spatial bundling may be configured for each individual HARQ-ACK response transmitted on the PUCCH and/or HARQ-ACK response transmitted on the PUSCH.
When up to two (or two or more) TBs (or codewords) may be received at one time (or schedulable by one DCI) in a corresponding serving cell (e.g., when a higher layer parameter maxNrofCodeWordsScheduledByDCI indicates 2 TBs), spatial bundling may be supported. More than four layers may be used for a 2-TB transmission, and up to four layers may be used for a 1-TB transmission. As a result, when spatial bundling is configured for a corresponding cell group, spatial bundling may be performed for a serving cell in which more than four layers may be scheduled among serving cells of the cell group. A UE which wants to transmit an HARQ-ACK response through spatial bundling may generate an HARQ-ACK response by performing a (bit-wise) logical AND operation on A/N bits for a plurality of TBs.
For example, on the assumption that the UE receives DCI scheduling two TBs and receives two TBs on a PDSCH based on the DCI, a UE that performs spatial bundling may generate a single A/N bit by a logical AND operation between a first A/N bit for a first TB and a second A/N bit for a second TB. As a result, when both the first TB and the second TB are ACKs, the UE reports an ACK bit value to a BS, and when at least one of the TBs is a NACK, the UE reports a NACK bit value to the BS.
For example, when only one TB is actually scheduled in a serving cell configured for reception of two TBs, the UE may generate a single A/N bit by performing a logical AND operation on an A/N bit for the one TB and a bit value of 1. As a result, the UE reports the A/N bit for the one TB to the BS.
There are plurality of parallel DL HARQ processes for DL transmissions at the BS/UE. The plurality of parallel HARQ processes enable continuous DL transmissions, while the BS is waiting for an HARQ feedback indicating successful or failed reception of a previous DL transmission. Each HARQ process is associated with an HARQ buffer in the medium access control (MAC) layer. Each DL HARQ process manages state variables such as the number of MAC physical data unit (PDU) transmissions, an HARQ feedback for a MAC PDU in a buffer, and a current redundancy version. Each HARQ process is identified by an HARQ process ID.
The UE may then transmit a PUSCH in slot #(n+K2) according to the scheduling information in slot #n. The PUSCH includes a UL-SCH TB.
NR may support wider UL/DL bandwidths by aggregating multiple UL/DL carriers (i.e., carrier aggregation). It may be possible to transmit/receive signals in multiple carriers through carrier aggregation. When carrier aggregation is applied, each carrier (see
Control information may be configured to be transmitted and received only through a specific cell. For example, UCI may be transmitted over a special cell (e.g., PCell). When a SCell (hereinafter, PUCCH-SCell) in which PUCCH transmission is allowed is configured, UCI may also be transmitted via PUCCH-SCell. As another example, a BS may allocate scheduling cells (set) to reduce PDCCH blinding decoding (BD) complexity at a UE side. For PDSCH reception/PUSCH transmission, the UE may perform PDCCH detection/decoding only in a scheduling cell. The BS may transmit PDCCH only through a scheduling cell (set). For example, a PDCCH for DL allocation may be transmitted in cell #0 (i.e., scheduling cell), and a corresponding PDSCH may be transmitted in cell #2 (i.e., scheduled cell) (Cross-carrier scheduling (CCS)). The scheduling cell (set) may be configured in a UE-specific, UE-group-specific or cell-specific manner. The scheduling cell include a special cell (e.g., PCell).
For cross-carrier scheduling, a carrier indicator field (CIF) is used. The CIF may be semi-statically disabled/enabled by UE-specific (or UE group-specific) higher layer (e.g. radio resource control (RRC)) signaling. The CIF field is an x-bit field (e.g., x=3) within the PDCCH (i.e., DCI) and may be used to indicate a (serving) cell index of the scheduled cell.
When carrier aggregation is supported, one UE may transmit and receive signals to and from a BS in a plurality of aggregated cells/carriers. If a plurality of CCs is configured for one UE, one CC may be configured as a primary CC (PCC) and the other CCs may be configured as secondary CCs (SCCs). Specific control information/channels (e.g., a CSS PDCCH and PUCCH) may be configured to transmit and receive signals only in the PCC. Data may be transmitted and received in the PCC and/or the SCCs. In
Unless otherwise mentioned, the definitions below are applicable to terms as used in the present disclosure
Table 6 illustrates exemplary CAPs supported in NR-U.
NR supports a wide spectrum across various frequency ranges. The usability of a 5G Advanced spectrum is expected to increase through re-farming of frequency bands used in previous generations. In particular, for a low frequency band FR1, available spectrum blocks tend to be more segmented and distributed. For a FR2 band and some FR1 bands, the available spectrum may be widened, and thus multiple carriers/cells need to be operated within the bands. There is a need to improve throughput and coverage by using these distributed spectrum bands or wider bandwidth spectrum in a more power-efficient and flexible manner.
It is important to increase flexibility and spectrum/power efficiency when data is scheduled across a plurality of cells including intra-band cells and inter-band cells, but in the current 5G NR scheduling scheme, DCI may only perform scheduling of the PUSCH/PDSCH for a single cell. However, a need for simultaneous scheduling of a plurality of cells is expected to increase in the future due to spectrum expansion/change and the like. To reduce control overhead due to scheduling, it is advantageous to perform PUSCH/PDSCH scheduling of the plurality of cells through single DCI.
To reduce the DCI overhead required for PDSCH/PUSCH scheduling in a carrier aggregation (CA) situation in which a plurality of cells are configured in the future, a multi-cell scheduling method that simultaneously schedules multiple (serving) cells/CCs (PDSCH/PUSCH transmission therethrough) with single DCI in Rel-18 may be considered.
Accordingly, a field configuring DCI for performing multi-cell scheduling as described above (multi-cell DCI) and a control/handling method for a corresponding DCI size are proposed. For convenience, a multi-cell scheduling operation for PDSCH transmission is mainly explained, but an operating principle of the proposed method may be applied equally to multi-cell scheduling for PUSCH transmission. Hereinafter, the term “cell” may refer to the (active) BWP configured/indicated to the corresponding cell.
Hereinafter, multi-cell scheduling DCI may be referred to as multi-cell DCI or simply DCI, and may include at least one of DL grant DCI for scheduling a PDSCH and UL grant DCI for scheduling a PUSCH.
[1] Configuration of DCI Fields for Each Scheduled Cell within Multi-Cell DCI
When a plurality of cells are scheduled through the same multi-cell DCI, the corresponding DCI fields for the respective cells may be arranged/configured in order of cell index for the same DCI field.
For example, a DCI field for a cell with a lower cell index may be located/configured at a lower bit index (within the DCI).
A single DCI field (commonly applied to cells belonging to the sub-group) may be configured for each cell sub-group including (single or) a plurality of cells, and in this case, the lowest cell index from among the cells belonging to each sub-group may be compared, and the DCI field for the sub-group to which the lower cell index belongs may be located/configured at a lower bit index (within the DCI).
For example, in
The DCI field may include, for example, but is not limited to, at least one of an MCS field and/or an NDI field and/or an RV field and/or a HARQ process ID (HARQ ID) field.
The DCI field may include, but is not limited to, at least one of a frequency domain resource assignment/allocation (FDRA) field and/or a time domain RA (TDRA) field and/or a TPC (for a PUSCH) field.
The cell index may be, for example, a serving cell index or a cell index (on the RRC configuration) used when configuring a candidate cell combination for multi-cell DCI scheduling.
Regardless of the maximum number of TBs to be transmitted via a single PDSCH configured for each cell (for convenience, this is defined as N_t, and may be configured to, for example, N_t=1 or N_t=2) and the number of cells scheduled via the same multi-cell DCI (for convenience, this is defined as N_c) or a combination of cells, the maximum value of the total number of TBs scheduled to a plurality of cells via a single multi-cell DCI may be limited to N_max or less (for example, N_max is configured by a BS or is determined as the maximum number of cells schedulable by the multi-cell DCI or N_max=4).
For example, up to N_max fields may be configured within the multi-cell DCI for (each of) the MCS and/or NDI and/or RV and/or HARQ ID fields.
For example, when the sum of the N_t values configured for each of the N_c cells scheduled with the same multi-cell DCI exceeds the N_max value, a rule may be determined such that a total of N_max TBs are allocated/scheduled to the N_c cells in a manner of cell index first-TB index second.
For example, when N_c=3 and all three cells (index=0, 1, 2) have N_t=2 and N_max=4, 2/1/1 TBs may be allocated/scheduled to cell indexes 0/1/2, respectively.
The cell index may be, for example, a serving cell index or a cell index (on the RRC configuration) used when configuring a candidate cell combination for multi-cell DCI scheduling.
When the number of cells scheduled through the multi-cell DCI is L (for example, L=1 or L=2) or less, scheduling is possible for up to N_t TBs configured for the corresponding cells, but when the number of cells scheduled through the multi-cell DCI exceeds L, scheduling may be limited to only a single TB for all of the corresponding cells.
For example, the maximum number of total TBs (scheduled to a plurality of cells) N_max through a single multi-cell DCI may be determined as the maximum number of cells to be scheduled with multi-cell DCI.
For example, up to N_max fields may be configured within the multi-cell DCI for (each of) the MCS and/or NDI and/or RV and/or HARQ ID fields.
[3] Processing Invalid Cells Scheduled with Multi-Cell DCI
1) When an invalid cell is included from among the cells scheduled/indicated through the multi-cell DCI, PDSCH/PUSCH transmission/reception may not be performed for the invalid cell, and PDSCH/PUSCH transmission/reception may be performed only for the remaining cells.
In this case, the DCI fields (e.g. MCS, NDI, RV, HARQ ID, FDRA, TDRA, TPC (for PUSCH), antenna port(s), transmission configuration indication, SRS resource indicator, precoding information and number of layers, DMRS sequence initialization, PTRS-DMRS association, VRB-to-PRB mapping, PRB bundling size indicator, rate matching indicator, ZP CSI-RS trigger, SRS request, frequency hopping flag, channelAccess-CPext-CAPC (for PUSCH), open-loop power control parameter set indication, and invalid symbol pattern indicator) corresponding to the invalid cell within the multi-cell DCI may not be configured and may be omitted (i.e., the DCI fields are configured sequentially (according to the cell index value/order) only for the remaining cells), or the corresponding DCI field may be configured based on parameters/values configured in a specific DL/UL BWP (e.g., a first active DL/UL BWP specified via a parameter firstActiveDownlinkBWP/firstActiveUplinkBWP or the latest active DL/UL BWP (excluding dormant BWP), or may be reserved with a predefined specific bit value, or the UE may operate to disregard the corresponding field.
For example, when configuring a HARQ-ACK feedback payload corresponding to the multi-cell DCI, a HARQ-ACK bit corresponding to the invalid cell may be omitted (i.e., the HARQ-ACK bit may be configured sequentially (according to the cell index value/order) only for the remaining cells), or the corresponding HARQ-ACK bit may be configured (according to the cell index value/order) for the invalid cell as well, but the corresponding bit may be mapped to NACK. For example, assuming that {Cell A, Cell B, Cell C} are co-scheduled through 1 DCI and Cell B is an invalid cell, HARQ-ACK may be configured with {A/N(s) for (TBs of) Cell A, A/N(s) for (TBs of) Cell C (and/or NACK(s) for remaining bit(s))} or HARQ-ACK may be configured with {A/N(s) for (TBs of) Cell A, NACK(s) for (TBs of) Cell B, A/N(s) for (TBs of) Cell C}.
The invalid cell is a deactivated Scell, a cell operating in a dormant BWP, a cell in which PDSCH (PUSCH) resources indicated through multi-cell DCI overlap in time with a semi-static UL (DL) symbol, a cell in which frequency resources of a PDSCH (PUSCH) allocated through multi-cell DCI are indicated with an invalid value (for example, in the form of a bitmap in which all bits are ‘0’ or in the form of a RIV (resource indication value) in which all bits are ‘1’), a cell in which time resources of a PDSCH (PUSCH) allocated through multi-cell DCI are indicated with an invalid value (for example, in the form of a SLIV in which all bits are ‘1’), a cell in which a TB disabling operation is indicated for all TBs (of the cell) through multi-cell DCI, a cell operating in a DRX off state (no PDCCH monitoring), and/or a cell corresponding to a specific time period (or a specific BWP) in which a series of transmission and reception operations are configured/instructed to be stopped for the purpose of BS energy/power saving. For example, assuming that information for resource allocation in DCI (e.g., FDRA field) is separately configured for each scheduled cell, a cell in which all bits of the information for resource allocation are configured to 0 or 1 (i.e., values that are not valid for resource allocation) may be an invalid cell (a cell that is not actually scheduled).
2) To reduce the complexity of the multi-cell DCI configuration and scheduling-related operations, a constraint may be imposed that the SCS used/applied to cells belonging to each cell combination (for convenience, referred to as a “co-scheduled cell set”) simultaneously scheduled from the corresponding DCI needs to all have the same value, and when the SCS used/applied between cells belonging to a specific co-scheduled cell set (active BWPs configured/indicated for each of the corresponding cells) have different values, PDSCH/PUSCH transmission/reception may be performed only for the cell to which a specific (valid) SCS is used/applied, and PDSCH/PUSCH transmission/reception may be omitted for the cells to which the remaining (invalid) SCSs are used/applied, and in this case, the cell to which the corresponding invalid SCS is used/applied may correspond to the invalid cell (therefore, the DCI field corresponding to the proposed invalid cell and (HARQ-ACK configuration method may be applied).
In the above case, the valid SCS may be preconfigured via RRC, or the like (for example, a separate valid SCS value may be configured for each co-scheduled cell set, or a single valid SCS value common to all co-scheduled cell sets may be configured) or determined based on a specific rule (for example, Alt 1) determined as an SCS value used/applied to a specific cell (e.g., lowest cell index) in the co-scheduled cell set, Alt 2) determined as the smallest/largest value from among the SCSs used/applied to the cells in the co-scheduled cell set, or Alt 3) determined as an SCS value used/applied to the largest number of cells in the co-scheduled cell set (when there are multiple SCS values used/applied to the largest number of cells, a value determined by applying Alt 1/2 to a plurality of SCS values).
In another method, when the SCS used/applied from among cells belonging to a specific co-scheduled cell set (active BWPs configured/indicated for the corresponding cells) have different values, scheduling via multi-cell DCI may not be allowed for the co-scheduled cell set (the UE may not expect scheduling for the co-scheduled cell set), and accordingly, the UE may omit DCI monitoring (blind decoding) for PDCCH candidates (search space) configured/corresponding to the co-scheduled cell set scheduling (DCI transmission).
[4] TB Disabling for PDSCH Scheduled with Multi-Cell DCI
In the case of existing single-cell DCI-based scheduling, when the maximum number of TBs to be transmitted through one PDSCH is configured to 2 (for example, 2 TB transmissions are scheduled through one PDSCH), if a combination of a specific MCS index (e.g., 26) and a specific RV index (i.e., RV ID) (e.g., 1) is indicated through DCI, an operation of disabling the corresponding specific TB index transmission/reception is specified.
When a plurality of cells are scheduled through the multi-cell DCI, RV index 0 or X (e.g. X=2) may be indicated for each cell (TB) through 1-bit RV, and when a single cell is scheduled through the multi-cell DCI (assuming that the corresponding scheduling is possible), RV index 0/1/2/3 may be indicated for the corresponding cell through 2-bit RV.
For a plurality of cells scheduled through the multi-cell DCI above, the cells may operate to receive a PDSCH while considering that a TB index for which a combination of a specific MCS index Z (e.g. Z=26) and the RV index X is indicated for each cell is disabled.
For the scheduled multiple cells, the cells may operate to receive a PDSCH assuming that there is no TB disabling for a cell that does not satisfy the condition.
For a plurality of cells scheduled through the multi-cell DCI, when a combination of the MCS index Z and the RV index X is indicated for the same TB index of all cells (where N_t=2), the TB index may be considered disabled for all cells (where N_t=2) and may operate to receive the PDSCH.
The method may be applied only when all cells scheduled with multi-cell DCI are cells configured with N_t=2, or may applied only to cells configured with N_t=2 from among the cells scheduled with multi-cell DCI.
For the scheduled multiple cells, the cells may operate to receive a PDSCH assuming that there is no TB disabling for a cell that does not satisfy the condition.
When only a single cell is scheduled through the multi-cell DCI, the TB index indicated by a combination of the MCS index Z and a specific RV index Y (e.g. Y=1) is considered disabled (same as before), and when a plurality of cells are scheduled through the multi-cell DCI, the PDSCH may be received assuming that there is always no TB disabling.
1) Existing operation
First, the out-of-order PDSCH/PUSCH/PUCCH scheduling constraints defined in the current standard with respect to single cell scheduling are briefly explained as follows.
According to an embodiment, the proposed out-of-order PDSCH/PUSCH/PUCCH scheduling constraints related to multi-cell scheduling may include one of the following.
A. For a plurality of PDSCHs #1 in a plurality of cells scheduled through the same multi-cell DCI PDCCH #1, the UE may operate not to expect a situation in which a relationship between the timing of the corresponding (multi-cell DCI) PDCCH #1 and PDSCH #1 on at least one of the corresponding plurality of cells and the timing of other PDCCH #2 and PDSCH #2 is scheduled to corresponding to the PDSCH OOO, and when scheduling is performed such that the relationship corresponds to the PDSCH OOO on at least one cell as described above, the UE may discard/ignore the multi-cell DCI, and/or omit (skip) reception of the plurality of PDSCHs on the scheduled multiple cells scheduled through the corresponding DCI. For example, in relation to multi-cell scheduling, PDSCH OOO is described as follows, when (i) at least one of DCI #1 and DCI #2 is a multi-cell scheduling DCI, (ii) the last symbol of DCI #2 is located after the last symbol of DCI #1, (iii) DCI #1 schedules M PDSCHs #1 {PDSCH #1-1, PDSCH #1-1, PDSCH #1-M} (on M Cells), and (iv) DCI #2 schedules N PDSCHs #2 {PDSCH #2-1, PDSCH #2-1, PDSCH #2-N} (on N Cells), and a start symbol of any one of N PDSCHs #2 {PDSCH #2-1, PDSCH #2-1, PDSCH #2-N} is located before the last symbol of (any one of) M PDSCHs #1 {PDSCH #1-1, PDSCH #1-1, PDSCH #1-M}, the relationship may correspond to PDSCH OOO. M and N may each be an integer greater than or equal to 1.
B. For a plurality of PUSCHs #1 in a plurality of cells scheduled through the same multi-cell DCI PDCCH #1, the UE may operate not to expect a situation in which a relationship between the timing of the corresponding (multi-cell DCI) PDCCH #1 and PUSCH #1 on at least one of the corresponding plurality of cells and the timing of other PDCCH #2 and PUSCH #2 is scheduled to corresponding to the PUSCH OOO, and when scheduling is performed such that the relationship corresponds to the PUSCH OOO on at least one cell as described above, the UE may discard/ignore the multi-cell DCI, and/or omit (skip) transmission of the plurality of PUSCHs on the scheduled multiple cells scheduled through the corresponding DCI. For example, in relation to multi-cell scheduling, PUSCH OOO is described as follows, when (i) at least one of DCI #1 and DCI #2 is a multi-cell scheduling DCI, (ii) the last symbol of DCI #2 is located after the last symbol of DCI #1, (iii) DCI #1 schedules M PUSCHs #1 {PUSCH #1-1, PUSCH #1-1, PUSCH #1-M} (on M Cells), and (iv) DCI #2 schedules N PUSCHs #2 {PUSCH #2-1, PUSCH #2-1, PUSCH #2-N} (on N Cells), and a start symbol of any one of N PUSCHs #2 {PUSCH #2-1, PUSCH #2-1, PUSCH #2-N} is located before the last symbol of (any one of) M PUSCHs #1 {PUSCH #1-1, PUSCH #1-1, PUSCH #1-M}, the relationship may correspond to PUSCH OOO. M and N may each be an integer greater than or equal to 1.
C. For the plurality of PDSCHs #1 on a plurality of cells scheduled through the same multi-cell DCI, the UE may operate not to expect a situation in which a relationship between a timing of HARQ-ACK corresponding to the corresponding PDSCH #1 on at least one of the corresponding plurality of cells and a timing of HARQ-ACK corresponding to other PDSCH #2 is scheduled to correspond to PUCCH OOO, and when as described above, when the relationship is scheduled to correspond to PUCCH OOO on at least one cell as described above, the UE may discard/ignore the multi-cell DCI and/or skip reception of a plurality of PDSCHs on a plurality of cells scheduled through the corresponding DCI and/or drop HARQ-ACK transmission on a plurality of PDSCHs on a plurality of cells scheduled through the corresponding DCI. PDSCH #2 may be related to multi-cell scheduling DCI or may be related to single-cell scheduling DCI. i) For example, assuming that M PDSCHs #1 {PDSCH #1-1, PDSCH #1-2, . . . , PDSCH #1-M} (M being an integer greater than or equal to 1) are scheduled via multi-cell scheduling DCI #1, N PDSCHs #2 {PDSCH #2-1, PDSCH #2-2, . . . , PDSCH #2-N} (N being an integer greater than or equal to 1), and at least one of the N PDSCHs #2 starts later than at least one of M PDSCHs #1, the case in which a slot of HARQ-ACK for N PDSCHs #2 is before a slot of HARQ-ACK for M PDSCHs #1 may correspond to PUCCH OOO. ii) As another example, assuming that M PDSCHs #1 {PDSCH #1-1, PDSCH #1-2, . . . , PDSCH #1-M} (M being an integer greater than or equal to 1) are scheduled via multi-cell scheduling DCI #1, PDSCH #2 is scheduled via single-cell scheduling DCI #2, and PDSCH #2 starts later than at least one of the M PDSCHs #1, the case in which a slot of HARQ-ACK for PDSCH #2 is before a slot of HARQ-ACK for M PDSCHs #1 may correspond to PUCCH OOO. iii) As another example, assuming that M PDSCHs #1 {PDSCH #1-1, PDSCH #1-2, . . . , PDSCH #1-M} (M being an integer greater than or equal to 1) are scheduled via multi-cell scheduling DCI #1, PDSCH #2 is scheduled via single-cell scheduling DCI #2, and at least one of M PDSCHs #1 starts later than PDSCH #2, the case in which a slot of HARQ-ACK for M PDSCHs #1 is before a slot of HARQ-ACK for PDSCH #2 may correspond to PUCCH OOO.
1) When the multi-cell DCI is transmitted/received based on configured scheduling (CS)-RNTI (and scrambling applied thereto), for a plurality of cells indicated through the corresponding DCI (with a specific (e.g. CIF or new) field in the corresponding DCI), a combination of specific fields (e.g. HARQ process ID, RV, MCS, all or part of frequency domain resource assignment) corresponding to each cell may be checked (validated) to satisfy SPS/CG related activation and/or release (and/or retransmission) indication conditions (refer to Section 10.2 of 3GPP TS 38.213 V16.2.0), and based thereon, the UE may perform the indicated (validated) operation for each cell.
For example, only the SPS/CG activation operation may be indicated for all (all or some) of the plurality of cells indicated through the same (CS-RNTI-based) multi-cell DCI, only the SPS/CG release operation may be indicated for all (all or some) of the multiple cells, or the SPS/CG activation operation may be indicated for a specific cell from among the corresponding plurality of cells (all or some) and the SPS/CG release operation may be indicated for other cells.
Alternatively, it may be specified that only SPS/CG activation operation is indicated for all (all or some) cells indicated via the same (CS-RNTI-based) multi-cell DCI, or only SPS/CG release operation is indicated for all (all or some) cells.
2) Alternatively, it may be specified that SPS/CG related activation and/or release (and/or retransmission) instructions (for the corresponding cell) are possible only when only one cell is indicated through the (CS-RNTI-based) multi-cell DCI, and that when a plurality of cells are indicated through the corresponding multi-cell DCI, SPS/CG related activation and/or release (and/or retransmission) instructions (all) are not allowed, or only SPS/CG related retransmission scheduling (activation and/or release instructions are not allowed) is allowed.
For a specific cell combination (including a plurality of cells) to be indicated/scheduled through multi-cell DCI, when CS-RNTI (i.e., SPS/CG) is configured for some cells (for convenience, referred to as “cell with CS-RNTI”) belonging to the corresponding cell combination, while CS-RNTI (i.e., SPS/CG) is not configured for the remaining cells (for convenience, referred to as “cell without CS-RNTI”),
Opt 1) When the specific cell combination is indicated through the CS-RNTI-based multi-cell DCI, transmission and reception operations are performed assuming that there is no PDSCH/PUSCH scheduling for the cell without CS-RNTI, or
Opt 2) For the specific cell combination, only instruction/scheduling via C-RNTI based multi-cell DCI may be possible/allowed (instruction/scheduling via CS-RNTI based multi-cell DCI may not be possible/allowed).
The (maximum) payload size of the multi-cell DCI may be determined as the maximum value from among total sum values, when each total sum value is the sum of the sizes of each of fields for a corresponding cell combination (each field corresponding to each cell within a corresponding cell combination), for each of all cell combinations to be scheduled through the DCI (for each cell combination). As a specific example, referring to
The UE may not expect/assume that a payload size of multi-DCI determined as described above is configured (such as a combination of cells for scheduling multi-cell DCI and/or a transmission parameter for each cell) to exceed the maximum number of bits N (e.g. N=140) to which a specific encoding scheme (e.g. polar code) is to be applied/supported, and when such a case occurs, the UE may not perform a monitoring/decoding operation for the multi-cell DCI, or may perform a monitoring/decoding operation for the DCI while a payload size of the DCI is adjusted to the number of bits N by removing certain bits (e.g., fields corresponding to high indices) configured/configured in the DCI.
Referring to
The UE may detect downlink control channel (DCI) through monitoring of the PDCCH candidates (1210).
The DCI may support multi-cell scheduling based on cell combinations regarding a plurality of cells configured in the UE. A payload size of the DCI may be determined based on a first cell combination in which a total number of bits required for co-scheduled cells from among the cell combinations is maximum.
The payload of the DCI may be determined based on the summed size of all DCI fields for the first cell combination.
Cells co-scheduled through the DCI may be indicated as one of the cell combinations. The DCI may include information indicating one of the cell combinations.
The DCI may include first DCI field-related information for each of a first cell and a second cell which are co-scheduled. Based on that the first cell has a lower serving cell index than the second cell, the first DCI field-related information for the first cell may be located before the first DCI field-related information for the second cell in the DCI. For example, the first DCI field may include, but is not limited to, at least one of a modulation and coding scheme (MCS) field, a new data indicator (NDI) field, a redundancy version (RV) field, a hybrid automatic repeat request (HARQ) process ID field, a frequency domain resource allocation (FDRA) field, a time domain resource allocation (TDRA) field, and a transmission power command (TPC) field for a physical uplink shared channel (PUSCH).
Transmission (e.g., PUSCHs for UL grant DCI) or reception (e.g., PDSCHs for DL grant DCI) of scheduled signals may be performed only for the remaining cells excluding at least one invalid cell from among the cells co-scheduled through the DCI. The at least one invalid cell may include, but is not limited to, at least one of a deactivated secondary cell (SCell), a cell operating as a dormant bandwidth part (BWP), a cell of which resources allocated through the DCI overlap semi-static resources in which uplink (UL)/downlink (DL) directions are configured differently, and a cell of which frequency resource information indicated by the DCI is invalid. For example, assuming that the DCI is a DL grant DCI that schedules PDSCHs, hybrid automatic repeat request-acknowledgement (HARQ-ACK) information for the PDSCHs may be configured for the remaining cells excluding at least one invalid cell, or may be configured to include negative acknowledgement (NACK) information for at least one invalid cell. The DCI field values for at least one invalid cell in the DCI may be configured based on information for a specific bandwidth part (BWP).
Referring to
The BS may transmit the DCI to the UE based on at least one of physical downlink control channel (PDCCH) candidates of a UE (1310).
The DCI may support multi-cell scheduling based on cell combinations for a plurality of cells configured for the UE. A payload size of the DCI may be determined based on a first cell combination having the largest total number of DCI bits required for co-scheduled cells from among the cell combinations.
The payload of the DCI may be determined based on the summed size of all DCI fields for the first cell combination.
Cells co-scheduled through the DCI may be indicated as one of the cell combinations. The DCI may include information indicating one of the cell combinations.
The DCI may include first DCI field-related information for each of a first cell and a second cell which are co-scheduled. Based on that the first cell has a lower serving cell index than the second cell, the first DCI field-related information for the first cell may be located before the first DCI field-related information for the second cell in the DCI. For example, the first DCI field may include, but is not limited to, at least one of a modulation and coding scheme (MCS) field, a new data indicator (NDI) field, a redundancy version (RV) field, a hybrid automatic repeat request (HARQ) process ID field, a frequency domain resource allocation (FDRA) field, a time domain resource allocation (TDRA) field, and a transmission power command (TPC) field for a physical uplink shared channel (PUSCH).
Reception (e.g., PUSCHs for UL grant DCI) or transmission (e.g., PDSCHs for DL grant DCI) of scheduled signals may be performed only for the remaining cells excluding at least one invalid cell from among the cells co-scheduled through the DCI. The at least one invalid cell may include, but is not limited to, at least one of a deactivated secondary cell (SCell), a cell operating as a dormant bandwidth part (BWP), a cell of which resources allocated through the DCI overlap semi-static resources in which uplink (UL)/downlink (DL) directions are configured differently, and a cell of which frequency resource information indicated by the DCI is invalid. For example, assuming that the DCI is a DL grant DCI that schedules PDSCHs, hybrid automatic repeat request-acknowledgement (HARQ-ACK) information for the PDSCHs may be configured for the remaining cells excluding at least one invalid cell, or may be configured to include negative acknowledgement (NACK) information for at least one invalid cell. The DCI field values for at least one invalid cell in the DCI may be configured based on information for a specific bandwidth part (BWP).
Referring to
The wireless devices 100a to 100f may be connected to the network 300 via the BSs 200. An AI technology may be applied to the wireless devices 100a to 100f and the wireless devices 100a to 100f may be connected to the AI server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although the wireless devices 100a to 100f may communicate with each other through the BSs 200/network 300, the wireless devices 100a to 100f may perform direct communication (e.g., sidelink communication) with each other without passing through the BSs/network. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (e.g., Vehicle-to-Vehicle (V2V)/Vehicle-to-everything (V2X) communication). The IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.
Wireless communication/connections 150a, 150b, or 150c may be established between the wireless devices 100a to 100f/BS 200, or BS 200/BS 200. Herein, the wireless communication/connections may be established through various RATs (e.g., 5G NR) such as uplink/downlink communication 150a, sidelink communication 150b (or, D2D communication), or inter BS communication (e.g., relay, Integrated Access Backhaul (IAB)). The wireless devices and the BSs/the wireless devices may transmit/receive radio signals to/from each other through the wireless communication/connections 150a and 150b. For example, the wireless communication/connections 150a and 150b may transmit/receive signals through various physical channels. To this end, at least a part of various configuration information configuring processes, various signal processing processes (e.g., channel encoding/decoding, modulation/demodulation, and resource mapping/demapping), and resource allocating processes, for transmitting/receiving radio signals, may be performed based on the various proposals of the present disclosure.
Referring to
The first wireless device 100 may include one or more processors 102 and one or more memories 104 and additionally further include one or more transceivers 106 and/or one or more antennas 108. The processor(s) 102 may control the memory(s) 104 and/or the transceiver(s) 106 and may be configured to implement the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. For example, the processor(s) 102 may process information within the memory(s) 104 to generate first information/signals and then transmit radio signals including the first information/signals through the transceiver(s) 106. The processor(s) 102 may receive radio signals including second information/signals through the transceiver 106 and then store information obtained by processing the second information/signals in the memory(s) 104. The memory(s) 104 may be connected to the processor(s) 102 and may store a variety of information related to operations of the processor(s) 102. For example, the memory(s) 104 may store software code including commands for performing a part or the entirety of processes controlled by the processor(s) 102 or for performing the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. Herein, the processor(s) 102 and the memory(s) 104 may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s) 106 may be connected to the processor(s) 102 and transmit and/or receive radio signals through one or more antennas 108. Each of the transceiver(s) 106 may include a transmitter and/or a receiver. The transceiver(s) 106 may be interchangeably used with Radio Frequency (RF) unit(s). In the present disclosure, the wireless device may represent a communication modem/circuit/chip.
The second wireless device 200 may include one or more processors 202 and one or more memories 204 and additionally further include one or more transceivers 206 and/or one or more antennas 208. The processor(s) 202 may control the memory(s) 204 and/or the transceiver(s) 206 and may be configured to implement the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. For example, the processor(s) 202 may process information within the memory(s) 204 to generate third information/signals and then transmit radio signals including the third information/signals through the transceiver(s) 206. The processor(s) 202 may receive radio signals including fourth information/signals through the transceiver(s) 106 and then store information obtained by processing the fourth information/signals in the memory(s) 204. The memory(s) 204 may be connected to the processor(s) 202 and may store a variety of information related to operations of the processor(s) 202. For example, the memory(s) 204 may store software code including commands for performing a part or the entirety of processes controlled by the processor(s) 202 or for performing the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. Herein, the processor(s) 202 and the memory(s) 204 may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s) 206 may be connected to the processor(s) 202 and transmit and/or receive radio signals through one or more antennas 208. Each of the transceiver(s) 206 may include a transmitter and/or a receiver. The transceiver(s) 206 may be interchangeably used with RF unit(s). In the present disclosure, the wireless device may represent a communication modem/circuit/chip.
Hereinafter, hardware elements of the wireless devices 100 and 200 will be described more specifically. One or more protocol layers may be implemented by, without being limited to, one or more processors 102 and 202. For example, the one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP). The one or more processors 102 and 202 may generate one or more Protocol Data Units (PDUs) and/or one or more Service Data Unit (SDUs) according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. The one or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. The one or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document and provide the generated signals to the one or more transceivers 106 and 206. The one or more processors 102 and 202 may receive the signals (e.g., baseband signals) from the one or more transceivers 106 and 206 and acquire the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document.
The one or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in the one or more processors 102 and 202. The descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be implemented using firmware or software and the firmware or software may be configured to include the modules, procedures, or functions. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be included in the one or more processors 102 and 202 or stored in the one or more memories 104 and 204 so as to be driven by the one or more processors 102 and 202. The descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be implemented using firmware or software in the form of code, commands, and/or a set of commands.
The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, code, instructions, and/or commands. The one or more memories 104 and 204 may be configured by Read-Only Memories (ROMs), Random Access Memories (RAMs), Electrically Erasable Programmable Read-Only Memories (EPROMs), flash memories, hard drives, registers, cash memories, computer-readable storage media, and/or combinations thereof. The one or more memories 104 and 204 may be located at the interior and/or exterior of the one or more processors 102 and 202. The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 through various technologies such as wired or wireless connection.
The one or more transceivers 106 and 206 may transmit user data, control information, and/or radio signals/channels, mentioned in the methods and/or operational flowcharts of this document, to one or more other devices. The one or more transceivers 106 and 206 may receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document, from one or more other devices. For example, the one or more transceivers 106 and 206 may be connected to the one or more processors 102 and 202 and transmit and receive radio signals. For example, the one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may transmit user data, control information, or radio signals to one or more other devices. The one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may receive user data, control information, or radio signals from one or more other devices. The one or more transceivers 106 and 206 may be connected to the one or more antennas 108 and 208 and the one or more transceivers 106 and 206 may be configured to transmit and receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document, through the one or more antennas 108 and 208. In this document, the one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports). The one or more transceivers 106 and 206 may convert received radio signals/channels etc. from RF band signals into baseband signals in order to process received user data, control information, radio signals/channels, etc. using the one or more processors 102 and 202. The one or more transceivers 106 and 206 may convert the user data, control information, radio signals/channels, etc. processed using the one or more processors 102 and 202 from the base band signals into the RF band signals. To this end, the one or more transceivers 106 and 206 may include (analog) oscillators and/or filters.
Referring to
The additional components 140 may be variously configured according to types of wireless devices. For example, the additional components 140 may include at least one of a power unit/battery, input/output (I/O) unit, a driving unit, and a computing unit. The wireless device may be implemented in the form of, without being limited to, the robot (100a of
In
Referring to
The communication unit 110 may transmit and receive signals (e.g., data and control signals) to and from external devices such as other vehicles, BSs (e.g., gNBs and road side units), and servers. The control unit 120 may perform various operations by controlling elements of the vehicle or the autonomous driving vehicle 100. The control unit 120 may include an Electronic Control Unit (ECU). The driving unit 140a may cause the vehicle or the autonomous driving vehicle 100 to drive on a road. The driving unit 140a may include an engine, a motor, a powertrain, a wheel, a brake, a steering device, etc. The power supply unit 140b may supply power to the vehicle or the autonomous driving vehicle 100 and include a wired/wireless charging circuit, a battery, etc. The sensor unit 140c may acquire a vehicle state, ambient environment information, user information, etc. The sensor unit 140c may include an Inertial Measurement Unit (IMU) sensor, a collision sensor, a wheel sensor, a speed sensor, a slope sensor, a weight sensor, a heading sensor, a position module, a vehicle forward/backward sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illumination sensor, a pedal position sensor, etc. The autonomous driving unit 140d may implement technology for maintaining a lane on which a vehicle is driving, technology for automatically adjusting speed, such as adaptive cruise control, technology for autonomously driving along a determined path, technology for driving by automatically setting a path if a destination is set, and the like.
For example, the communication unit 110 may receive map data, traffic information data, etc. from an external server. The autonomous driving unit 140d may generate an autonomous driving path and a driving plan from the obtained data. The control unit 120 may control the driving unit 140a such that the vehicle or the autonomous driving vehicle 100 may move along the autonomous driving path according to the driving plan (e.g., speed/direction control). In the middle of autonomous driving, the communication unit 110 may aperiodically/periodically acquire recent traffic information data from the external server and acquire surrounding traffic information data from neighboring vehicles. In the middle of autonomous driving, the sensor unit 140c may obtain a vehicle state and/or surrounding environment information. The autonomous driving unit 140d may update the autonomous driving path and the driving plan based on the newly obtained data/information. The communication unit 110 may transfer information about a vehicle position, the autonomous driving path, and/or the driving plan to the external server. The external server may predict traffic information data using AI technology, etc., based on the information collected from vehicles or autonomous driving vehicles and provide the predicted traffic information data to the vehicles or the autonomous driving vehicles.
The UE may perform a DRX operation in the afore-described/proposed procedures and/or methods. A UE configured with DRX may reduce power consumption by receiving a DL signal discontinuously. DRX may be performed in an RRC_IDLE state, an RRC_INACTIVE state, and an RRC_CONNECTED state. The UE performs DRX to receive a paging signal discontinuously in the RRC_IDLE state and the RRC_INACTIVE state. DRX in the RRC_CONNECTED state (RRC_CONNECTED DRX) will be described below.
Referring to
Table 7 describes a DRX operation of a UE (in the RRC_CONNECTED state). Referring to Table 7, DRX configuration information is received by higher-layer signaling (e.g., RRC signaling), and DRX ON/OFF is controlled by a DRX command from the MAC layer. Once DRX is configured, the UE may perform PDCCH monitoring discontinuously in performing the afore-described/proposed procedures and/or methods.
MAC-CellGroupConfig includes configuration information required to configure MAC parameters for a cell group. MAC-CellGroupConfig may also include DRX configuration information. For example, MAC-CellGroupConfig may include the following information in defining DRX.
When any of drx-OnDuration Timer, drx-InactivityTimer, drx-HARQ-RTT-TimerDL, and drx-HARQ-RTT-TimerDL is running, the UE performs PDCCH monitoring in each PDCCH occasion, staying in the awake state.
The above-described embodiments correspond to combinations of elements and features of the present disclosure in prescribed forms. And, the respective elements or features may be considered as selective unless they are explicitly mentioned. Each of the elements or features can be implemented in a form failing to be combined with other elements or features. Moreover, it is able to implement an embodiment of the present disclosure by combining elements and/or features together in part. A sequence of operations explained for each embodiment of the present disclosure can be modified. Some configurations or features of one embodiment can be included in another embodiment or can be substituted for corresponding configurations or features of another embodiment. And, it is apparently understandable that an embodiment is configured by combining claims failing to have relation of explicit citation in the appended claims together or can be included as new claims by amendment after filing an application.
Those skilled in the art will appreciate that the present disclosure may be carried out in other specific ways than those set forth herein without departing from the spirit and essential characteristics of the present disclosure. The above embodiments are therefore to be construed in all aspects as illustrative and not restrictive. The scope of the disclosure should be determined by the appended claims and their legal equivalents, not by the above description, and all changes coming within the meaning and equivalency range of the appended claims are intended to be embraced therein.
The present disclosure is applicable to UEs, BSs, or other apparatuses in a wireless mobile communication system.
| Number | Date | Country | Kind |
|---|---|---|---|
| 10-2022-0052001 | Apr 2022 | KR | national |
| 10-2022-0100144 | Aug 2022 | KR | national |
| 10-2022-0123684 | Sep 2022 | KR | national |
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/KR2023/005780 | 4/27/2023 | WO |
