Method and apparatus for transmitting and receiving signal in wireless communication system
By introducing multi-cell scheduling DCI fields in the wireless communication system, channel control and resource allocation between multiple cells are optimized, the problem of low signal transmission and reception efficiency in the prior art is solved, and efficient multi-cell scheduling and signaling is realized transfer.
Patent Information
- Application Number
- CN202380035544.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-02-16
- Filing Date
- 2023-04-27
- Publication Date
- 2024-12-03
AI Technical Summary
The existing wireless communication system has problems with low signal transmission and reception efficiency in multi-cell scheduling, especially in resource scheduling and channel control information transmission between multiple cells, resulting in high signal processing complexity and low efficiency.
By introducing multi-cell scheduling DCI fields between user equipment (UE) and base station (BS), the size and configuration of the DCI field are used to support the common scheduling of multiple cells, including the DCI field of co-scheduling of cells and the DCI field of reference cells. , optimize channel access and cyclic prefix information, and improve the efficiency of channel access and resource allocation.
It realizes efficient multi-cell scheduling and signal transmission in wireless communication systems, reduces the complexity of channel access and resource allocation, improves the efficiency of signal transmission and reception, and enhances the flexibility and spectrum utilization efficiency of the system.
Smart Images

Figure CN119072890A_ABST
Abstract
Description
Technical Field
[0001] 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. Background Art
[0002] In general, wireless communication systems are developing to cover a wide range in various ways to provide communication services such as audio communication services, data communication services, etc. Wireless communication is a multiple access system that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, etc.). For example, the multiple access system can 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. Summary of the invention
[0003] Technical issues
[0004] An object of the present disclosure is to provide a method and apparatus for efficiently performing a wireless signal transmission / reception process.
[0005] Those skilled in the art will understand that the objectives that can be achieved using the present disclosure are not limited to those specifically described above, and the above and other objectives that can be achieved by the present disclosure will be more clearly understood from the following detailed description.
[0006] Technical Solution
[0007] According to one aspect, a method for receiving a signal in a user equipment (UE) in a wireless communication system comprises the following steps: monitoring a physical downlink control channel (PDCCH) candidate; and detecting downlink control information (DCI) by monitoring the PDCCH candidate. DCI can support multi-cell scheduling based on multiple cells configured in the UE. DCI may include a first DCI field configured for co-scheduled cells. Based on multiple serving cells including a first cell and a second cell and the size-related configuration of the first DCI field being M bits for scheduling the first cell and N bits for scheduling the second cell respectively: the size of the first DCI field configured for co-scheduled cells can be determined based on the larger of the M bits and the N bits.
[0008] The first DCI field may include a field about antenna port information, a field about sounding reference signal (SRS) resource information, a field about precoding and layer number related information, a field about β offset information, an open-loop power control parameter set indication (OLPC) field, and at least one of a field about channel access and cyclic prefix (CP) information.
[0009] The first DCI field may indicate a common code point for the co-scheduled cells. Parameters mapped to the indicated code point may be configured separately for each co-scheduled cell. A table providing parameters of the corresponding scheduled cells mapped to each code point of the first DCI field may be configured in the UE.
[0010] The size of the first DCI field may be determined based on a cell having a maximum size-related configuration of the first DCI field among a plurality of cells.
[0011] The DCI may include a second DCI field applied to a reference cell among the co-scheduled cells.
[0012] The reference cell may be a cell having a smallest serving cell index among the co-scheduled cells.
[0013] The second DCI field may include a channel state information (CSI) request field.
[0014] The UE may obtain CSI related to the CSI request field based on channel state information-reference signal (CSI-RS) information of a reference cell having a minimum serving cell index among co-scheduled cells.
[0015] The UE may transmit a CSI report related to the CSI request field on a reference cell having a smallest serving cell index among the co-scheduled cells through a physical uplink shared channel (PUSCH).
[0016] According to another aspect, there may be provided a processor-readable recording medium having recorded thereon a program for executing the method.
[0017] According to another aspect, a UE for performing the method may be provided.
[0018] According to another aspect, a device for controlling a UE to perform the method may be provided.
[0019] According to one aspect, a method for sending a signal by a base station (BS) in a wireless communication system includes the following steps: generating downlink control information (DCI); and sending the DCI to a user equipment (UE) based on at least one physical downlink control channel (PDCCH) candidate of the UE. The DCI can support multi-cell scheduling based on multiple cells configured in the UE. The DCI may include a first DCI field configured for co-scheduled cells. Based on the multiple cells including a first cell and a second cell and the size-related configuration of the first DCI field is M bits for scheduling the first cell and N bits for scheduling the second cell, the size of the first DCI field configured for the co-scheduled cells can be determined by the larger of the M bits and the N bits.
[0020] According to another aspect, a BS for performing the method may be provided.
[0021] Beneficial Effects
[0022] According to at least one of various embodiments, a wireless signal transmission / reception process can be efficiently performed.
[0023] Those skilled in the art will understand that the technical effects that can be achieved using the present disclosure are not limited to those specifically described above, and the above and other technical effects that can be achieved by the present disclosure will be more clearly understood from the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS
[0024] Figure 1 Physical channels used in a 3rd Generation Partnership Project (3GPP) system as an exemplary wireless communication system and a general signal transmission method using the same are shown.
[0025] Figure 2 Shows the radio frame structure.
[0026] Figure 3 A resource grid showing time slots.
[0027] Figure 4 An exemplary mapping of physical channels in time slots is shown.
[0028] Figure 5 An exemplary PDCCH / PDSCH reception and acknowledgement / negative acknowledgement (ACK / NACK) transmission process is shown.
[0029] Figure 6 An exemplary physical uplink shared channel (PUSCH) transmission process is shown.
[0030] Figure 7 An example of carrier aggregation is shown.
[0031] Figure 8 An exemplary wireless communication system supporting an unlicensed frequency band is shown.
[0032] Fig. 9 A method of occupying resources in an unlicensed band is shown.
[0033] Fig.10 It is a diagram for explaining a specific type of field in a multi-cell scheduling DCI according to an embodiment.
[0034] Fig.11 It is a diagram for explaining a CSI request field in a multi-cell scheduling DCI according to an embodiment.
[0035] Fig.12 It is a diagram for explaining the size configuration of a specific type of field in a multi-cell scheduling DCI according to an embodiment.
[0036] Fig.13 is a diagram for explaining a method of receiving a signal by a user equipment (UE) according to an embodiment.
[0037] Fig.14 is a diagram for explaining a method of transmitting a signal by a base station (BS) according to an embodiment.
[0038] Figures 15 to 18 A communication system 1 and a wireless device suitable for use with the present disclosure are shown.
[0039] Fig.19 A discontinuous reception (DRX) operation suitable for the present disclosure is shown. DETAILED DESCRIPTION
[0040] Embodiments of the present disclosure are applicable to various 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 part of Universal Mobile Telecommunications System (UMTS). 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is a 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.
[0041] As more and more communication devices require greater communication capacity, enhanced mobile broadband communications relative to traditional radio access technologies (RATs) are needed. In addition, large-scale machine-type communications (MTC), which can provide various services anytime and anywhere by connecting multiple devices and objects, is another important issue to be considered for next-generation communications. Discussions are also underway to design communication systems that take into account services / UEs that are sensitive to reliability and latency. Therefore, discussions are underway to introduce new radio access technologies that take into account enhanced mobile broadband communications (eMBB), massive MTC, and ultra-reliable low-latency communications (URLLC). In this disclosure, for simplicity, this technology will be referred to as NR (new radio or new RAT).
[0042] For the sake of brevity, 3GPP NR is mainly described, but the technical concept of the present disclosure is not limited thereto.
[0043] In the present disclosure, the term "setting" may be replaced by "configuration", and the two may be used interchangeably. In addition, conditional expressions (e.g., "if", "in the case of..." or "when") may be replaced by "based on..." or "under the state of...". In addition, the operation or software / hardware (SW / HW) configuration of the user equipment (UE) / base station (BS) may be derived / understood based on satisfying the corresponding conditions. When the processing of the receiving (or transmitting) side can be derived / understood from the processing of the transmitting (or receiving) side in the signal transmission / reception between the wireless communication device (e.g., BS and UE), its description may be omitted. For example, the signal determination / generation / encoding / transmission of the transmitting side may be understood as the signal monitoring reception / decoding / determination of the receiving side. In addition, when it is said that the UE performs (or does not perform) a specific operation, this may also be interpreted as the BS expecting / assuming (or not expecting / assuming) that the UE performs the specific operation. When it is said that the BS performs (or does not perform) a specific operation, this may also be interpreted as the UE expecting / assuming (or not expecting / assuming) that the BS performs the specific operation. In the following description, for the convenience of description, sections, implementations, examples, options, methods, schemes, etc. are distinguished and indexed from each other, which does not mean that each of them must constitute an independent disclosure or that each of them should only be implemented separately. Unless explicitly contradicted, it can be deduced / understood that at least some sections, implementations, examples, options, methods, schemes, etc. can be implemented in combination or can be omitted.
[0044] In a wireless communication system, a user equipment (UE) receives information from a base station (BS) through a downlink (DL) and transmits information to the BS through an 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 the type / purpose of the information transmitted and received by the UE and the BS.
[0045] Figure 1 Physical channels used in the 3GPP NR system and a general signal transmission method using the same are shown.
[0046] When the UE is powered on again from a power-off state or enters a new cell, in step S101, the UE performs an initial cell search process (e.g., establishes synchronization with the BS). 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 obtains information such as a cell identity (ID). The UE can obtain broadcast information in the cell based on the PBCH. The UE can receive a DL reference signal (RS) during the initial cell search process to monitor the DL channel status.
[0047] After the initial cell search, the UE may acquire more specific system information by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) based on information of the PDCCH in step S102.
[0048] The UE may perform a random access procedure to access the BS in steps S103 to S106. For random access, the UE may send a preamble to the BS on a physical random access channel (PRACH) (S103) and receive a response message to the 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 sending a PRACH (S105) and receiving a PDCCH and a PDSCH corresponding to the PDCCH (S106).
[0049] After the foregoing process, the UE may receive PDCCH / PDSCH (S107) and send a physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) (S108) as a general downlink / uplink signal transmission process. The control information sent from the UE to the BS is called uplink control information (UCI). UCI includes hybrid automatic repeat and request confirmation / negative determination (HARQ-ACK / NACK), scheduling request (SR), channel state information (CSI), etc. CSI includes channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), etc. Although UCI is usually sent on PUCCH, UCI may be sent on PUSCH when control information and business data need to be sent simultaneously. In addition, UCI may be sent aperiodically via PUSCH according to the request / command of the network.
[0050] The purpose of the random access procedure (RACH procedure) is not limited to the initial network access (e.g., S103 to S106). That is, the random access procedure can be used for various purposes. For example, the random access procedure can be used for at least one of the 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 can obtain UL synchronization and / or UL transmission resources from the random access procedure.
[0051] Figure 2 The radio frame structure is shown. In NR, uplink transmission and downlink transmission are configured in frames. Each radio frame has a length of 10ms and is divided into two 5ms half frames (HF). Each half frame is divided into five 1ms subframes (SF). A subframe is divided into one or more time slots, and the number of time slots in a subframe depends on the subcarrier spacing (SCS). Depending on the cyclic prefix (CP), each time slot includes 12 or 14 orthogonal frequency division multiplexing (OFDM) symbols. When a normal CP is used, each time slot includes 14 OFDM symbols. When an extended CP is used, each time slot includes 12 OFDM symbols.
[0052] 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 a normal CP is used.
[0053] [Table 1]
[0054] SCS(15*2^u) <![CDATA[N slot symb ]]> <![CDATA[N frame,u slot ]]> <![CDATA[N subframe,u slot ]]> 15KHz(u=0) 14 10 1 30KHz(u=1) 14 20 2 60KHz(u=2) 14 40 4 120KHz(u=3) 14 80 8 240KHz(u=4) 14 160 16
[0055] *N slot symb : The number of symbols in a time slot
[0056] *N frame,u slot : Number of time slots in a frame
[0057] *N subframe,u slot : Number of time slots in a subframe
[0058] Table 2 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 extended CP is used.
[0059] [Table 2]
[0060] SCS(15*2^u) <![CDATA[N slot symb ]]> <![CDATA[N frame,u slot ]]> <![CDATA[N subframe,u slot <!-- 4 -->]]> 60KHz(u=2) 12 40 4
[0061] The structure of the frame is only an example. The number of subframes, the number of time slots, and the number of symbols in a frame may vary.
[0062] In the NR system, OFDM parameter sets (e.g., SCS) may be configured differently for multiple cells aggregated for one UE. Therefore, the (absolute time) duration of a time resource (e.g., SF, time slot, or TTI) (referred to as a time unit (TU) for simplicity) consisting of the same number of symbols may be configured differently between aggregated cells. Here, the symbol may include an OFDM symbol (or CP-OFDM symbol) and an SC-FDMA symbol (or a discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbol).
[0063] Figure 3 A resource grid showing a time slot. A time slot includes multiple symbols in the time domain. For example, when a normal CP is used, a time slot includes 14 symbols. However, when an extended CP is used, a time slot includes 12 symbols. A carrier includes multiple subcarriers in the frequency domain. A resource block (RB) is defined as a plurality of consecutive subcarriers (e.g., 12 consecutive subcarriers) in the frequency domain. A bandwidth part (BWP) may be defined as a plurality of consecutive physical RBs (PRBs) in the frequency domain and corresponds to a single parameter set (e.g., SCS, CP length, etc.). A carrier may include up to N (e.g., five) BWPs. Data communication may be performed via enabled BWPs, and only one BWP may be enabled for a UE. In a resource grid, each element is referred to as a resource element (RE), and a complex symbol may be mapped to each RE.
[0064] Figure 4 An exemplary mapping of physical channels in a time slot is shown. PDCCH may be sent in the DL control region, and PDSCH may be sent in the DL data region. PUCCH may be sent in the UL control region, and PUSCH may be sent in the UL data region. A guard period (GP) provides a time gap for a transmission mode to a reception mode switch or a reception mode to a transmission mode switch at the BS and the UE. Some symbols in a subframe at the time of a DL to UL switch may be configured as a GP.
[0065] The individual physical channels are described in more detail below.
[0066] PDCCH transmits DCI. For example, PDCCH (i.e., DCI) may carry information about the transmission format and resource allocation of the DL shared channel (DL-SCH), resource allocation information of the uplink shared channel (UL-SCH), paging information about the paging channel (PCH), system information about DL-SCH, information about resource allocation of high-level control messages (e.g., RAR sent on PDSCH), transmit power control commands, information about the activation / release of the configured scheduling, etc. DCI includes a cyclic redundancy check (CRC). The CRC is masked using various identifiers (IDs) (e.g., radio network temporary identifier (RNTI)) according to the owner or purpose of the PDCCH. For example, if the PDCCH is used for a specific UE, the CRC is masked by the UE ID (e.g., cell-RNTI (C-RNTI)). If the PDCCH is used for a paging message, the CRC is masked by the paging-RNTI (P-RNTI). If the PDCCH is for system information (eg, system information block (SIB)), the CRC is masked by a system information RNTI (SI-RNTI). When the PDCCH is for RAR, the CRC is masked by a random access-RNTI (RA-RNTI).
[0067] The PDCCH includes 1, 2, 4, 8 or 16 control channel elements (CCEs) depending on its aggregation level (AL). CCE is a logical allocation unit for providing a specific code rate to the PDCCH according to the radio channel state. CCE includes 6 resource element groups (REGs), each REG being defined by one OFDM symbol × 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 set of parameters (e.g., SCS, CP length, etc.). Multiple CORESETs for one UE may overlap with each other in the time / frequency domain. The CORESET may be configured by system information (e.g., master information block (MIB)) or UE-specific high-level signaling (e.g., radio resource control (RRC) signaling). Specifically, the number of RBs and the number of symbols (up to 3) in a CORESET may be configured by high-level signaling.
[0068] For PDCCH reception / detection, the UE monitors PDCCH candidates. PDCCH candidates are CCEs that the UE should monitor to detect PDCCH. Each PDCCH candidate is defined as 1, 2, 4, 8 or 16 CCEs according to the AL. Monitoring includes (blind) decoding of the PDCCH candidates. The set of PDCCH candidates decoded by the UE is defined as the PDCCH search space (SS). The SS can be a common search space (CSS) or a UE-specific search space (USS). The UE can obtain DCI by monitoring PDCCH candidates in one or more SSs configured by MIB or high-level signaling. Each CORESET is associated with one or more SSs, and each SS is associated with a CORESET. The SS can be defined based on the following parameters.
[0069] -controlResourceSetId: CORESET related to SS
[0070] -monitoringSlotPeriodicityAndOffset: PDCCH monitoring periodicity (time slot) and PDCCH monitoring offset (time slot)
[0071] -monitoringSymbolsWithinSlot: PDCCH monitoring symbols in a slot (e.g., the first symbol of CORESET)
[0072] -nrofCandidates: the number of PDCCH candidates for each AL={1,2,4,8,16} (one of 0, 1, 2, 3, 4, 5, 6 and 8)
[0073] *The timing (eg, time / frequency resources) at which the UE is to monitor a PDCCH candidate is defined as a PDCCH (monitoring) timing. One or more PDCCH (monitoring) timings may be configured in a time slot.
[0074] Table 3 shows the characteristics of each SS.
[0075] [Table 3]
[0076]
[0077] Table 4 shows the DCI format transmitted on the PDCCH.
[0078] [Table 4]
[0079]
[0080] DCI format 0_0 can be used to schedule TB-based (or TB-level) PUSCH, and DCI format 0_1 can be used to schedule TB-based (or TB-level) PUSCH or code block group (CBG)-based (or CBG-level) PUSCH. DCI format 1_0 can be used to schedule TB-based (or TB-level) PDSCH, and DCI format 1_1 can be used to schedule TB-based (or TB-level) PDSCH or CBG-based (or CBG-level) PDSCH (or DL grant DCI). DCI format 0_0 / 0_1 can be called UL grant DCI or UL scheduling information, and DCI format 1_0 / 1_1 can be called DL grant DCI or DL scheduling information. DCI format 2_0 is used to transmit dynamic slot format information (e.g., dynamic slot format indicator (SFI)) to the UE, and DCI format 2_1 is used to transmit DL preemption information to the UE. DCI format 2_0 and / or DCI format 2_1 can be transmitted to a corresponding group of UEs on a group common PDCCH (a PDCCH pointing to a group of UEs).
[0081] DCI format 0_0 and DCI format 1_0 may be referred to as fallback DCI formats, while DCI format 0_1 and DCI format 1_1 may be referred to as non-fallback DCI formats. Under the fallback DCI format, the DCI size / field configuration remains the same regardless of the UE configuration. In contrast, under the non-fallback DCI format, the DCI size / field configuration varies according to the UE configuration.
[0082] PDSCH transmits DL data (e.g., DL shared channel transport block (DL-SCHTB)) and uses modulation schemes such as quadrature phase shift keying (QPSK), 16-ary quadrature amplitude modulation (16QAM), 64QAM, or 256QAM. TB is encoded as a codeword. PDSCH can transmit up to two codewords. Scrambling and modulation mapping can be performed on the basis of the codeword, and the modulation symbols generated from each codeword can be mapped to one or more layers. Each layer is mapped to a resource together with a demodulation reference signal (DMRS), and an OFDM symbol signal is generated from the layer mapped with the DMRS and sent through the corresponding antenna port.
[0083] PUCCH transmits uplink control information (UCI). UCI includes the following information.
[0084] -SR (Scheduling Request): Information used to request UL-SCH resources.
[0085] -HARQ (Hybrid Automatic Repeat Request) -ACK (Acknowledgement): A response to a DL data packet (e.g., a codeword) on the PDSCH. HARQ-ACK indicates whether the DL data packet was successfully received. In response to a single codeword, a 1-bit HARQ-ACK may be sent. In response to two codewords, a 2-bit HARQ-ACK may be sent. HARQ-ACK responses include positive ACK (abbreviated as ACK), negative ACK (NACK), discontinuous transmission (DTX), or NACK / DTX. The term HARQ-ACK may be used interchangeably with HARQ ACK / NACK and ACK / NACK.
[0086] -CSI (Channel State Information): Feedback information of DL channels. Multiple Input Multiple Output (MIMO) related feedback information includes RI and PMI.
[0087] Table 5 shows an exemplary PUCCH format. Based on PUCCH transmission duration, the PUCCH format may be divided into short PUCCH (formats 0 and 2) and long PUCCH (formats 1, 3, and 4).
[0088] [Table 5]
[0089]
[0090] PUCCH format 0 transmits up to 2 bits of UCI and is mapped in a sequence-based manner for easy transmission. Specifically, the UE sends a specific UCI to the BS by sending one of multiple sequences on the PUCCH of PUCCH format 0. The UE sends the PUCCH of PUCCH format 0 in the PUCCH resources configured for the corresponding SR only when the UE sends a positive SR.
[0091] PUCCH format 1 transmits up to 2 bits of UCI, and the modulation symbol of UCI is spread in the time domain with an orthogonal cover code (OCC) (configured differently depending on whether frequency hopping is performed). DMRS is transmitted in symbols where modulation symbols are not transmitted (ie, transmitted in time division multiplexing (TDM)).
[0092] PUCCH format 2 transmits more than 2 bits of UCI, and the modulation symbols of DCI are sent with frequency division multiplexing (FDM) using DMRS. DMRS are located in symbols #1, #4, #7, and #10 of a given RB at a density of 1 / 3. Pseudo-noise (PN) sequences are used for DMRS sequences. For 2-symbol PUCCH format 2, frequency hopping can be enabled.
[0093] PUCCH format 3 does not support UE multiplexing in the same PRBS and transmits UCI of more than 2 bits. In other words, the PUCCH resource of PUCCH format 3 does not include OCC. The modulation symbol is transmitted in TDM using DMRS.
[0094] PUCCH format 4 supports multiplexing of up to 4 UEs in the same PRBS and transmits UCI of more than 2 bits. In other words, the PUCCH resource of PUCCH format 3 includes OCC. The modulation symbol is transmitted in TDM using DMRS.
[0095] The PUSCH transmits 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 sent with a DFT-s-OFDM waveform, the UE sends the PUSCH with transform precoding. For example, when transform precoding is not possible (e.g., disabled), the UE may send the PUSCH with a CP-OFDM waveform, and when transform precoding is possible (e.g., enabled), the UE may send the PUSCH with a CP-OFDM or DFT-s-OFDM waveform. PUSCH transmission may be dynamically scheduled by a UL grant in the DCI, or semi-statically scheduled by higher layer (e.g., RRC) signaling (and / or layer 1 (L1) signaling such as PDCCH) (configured scheduling or configured grant). PUSCH transmission may be performed in a codebook-based or non-codebook-based manner.
[0096] Figure 5 An exemplary PDCCH / PDSCH reception and ACK / NACK transmission process is shown. Figure 5 , the UE may detect the PDCCH in slot #n. The PDCCH includes DL scheduling information (e.g., DCI format 1_0 or DCI format 1_1). The PDCCH indicates DL assignment with PDSCH offset K0 and PDSCH with HARQ-ACK report offset K1. For example, DCI format 1_0 and DCI format 1_1 may include the following information.
[0097] - Frequency domain resource assignment: indicates the RB set assigned to PDSCH.
[0098] - Time domain resource assignment: indicates K0 and the starting position (eg, OFDM symbol index) and length (eg, number of OFDM symbols) of the PDSCH in the slot.
[0099] -PDSCH-to-HARQ_feedback timing indicator: indicates K1.
[0100] -HARQ process number (4 bits): indicates the HARQ process ID of the data (eg, PDSCH or TB).
[0101] After receiving PDSCH in slot #(n+K0) according to the scheduling information of slot #n, the UE may send UCI on PUCCH in slot #(n+K1). UCI may include a HARQ-ACK response to PDSCH. For convenience, Figure 5 Based on the assumption that the SCS of PDSCH is equal to the SCS of PUCCH and slot #n1=slot #(n+K0), this should not be construed as limiting the present disclosure. When the SCSs are different, K1 may be indicated / interpreted based on the SCS of PUCCH.
[0102] In the case where the PDSCH is configured to carry up to one TB, the HARQ-ACK response may be configured in one bit. In the case where the PDSCH is configured to carry up to two TBs, if spatial bundling is not configured, the HARQ-ACK response may be configured in two bits, and if spatial bundling is configured, the HARQ-ACK response may be configured in one bit. When slot #(n+K1) is designated as the HARQ-ACK transmission timing of multiple PDSCHs, the UCI sent in slot #(n+K1) includes HARQ-ACK responses to multiple PDSCHs.
[0103] Whether the UE should perform spatial bundling for HARQ-ACK responses may be configured for each cell group (e.g., via RRC / high-layer signaling). For example, spatial bundling may be configured for each individual HARQ-ACK response sent on the PUCCH and / or a HARQ-ACK response sent on the PUSCH.
[0104] Spatial bundling can be supported when up to two (or two or more) TBs (or codewords) can be received at a time (can be or be scheduled by one DCI) in the corresponding serving cell (for example, when the high-level parameter maxNrofCodeWordsScheduledByDCI indicates 2 TBs). More than four layers can be used for 2TB transmission, and up to four layers can be used for 1TB transmission. As a result, when spatial bundling is configured for the corresponding cell group, spatial bundling can be performed for serving cells in the cell group where more than four layers can be scheduled. A UE that wants to send a HARQ-ACK response through spatial bundling can generate a HARQ-ACK response by performing a (bit-by-bit) logical AND operation on the A / N bits of multiple TBs.
[0105] For example, assuming that a UE receives a DCI that schedules two TBs and receives the two TBs on a PDSCH based on the DCI, the UE that performs spatial bundling can generate a single A / N bit by a logical AND operation between a first A / N bit of a first TB and a second A / N bit of a second TB. As a result, when both the first TB and the second TB are ACK, the UE reports an ACK bit value to the BS, and when at least one TB is NACK, the UE reports a NACK bit value to the BS.
[0106] For example, when only one TB is actually scheduled in a serving cell configured to receive two TBs, the UE may generate a single A / N bit by performing a logical AND operation on the A / N bits of the one TB and a bit value 1. As a result, the UE reports the A / N bits of the one TB to the BS.
[0107] There are multiple parallel DL HARQ processes at the BS / UE for DL transmissions. Multiple parallel HARQ processes allow continuous DL transmissions while the BS waits for HARQ feedback indicating the success or failure of reception of the previous DL transmission. Each HARQ process is associated with a 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, HARQ feedback for the MAC PDUs in the buffer, and the current redundancy version. Each HARQ process is identified by a HARQ process ID.
[0108] Figure 6 An exemplary PUSCH transmission process is shown. Figure 6 , the UE may detect the PDCCH in slot #n. The PDCCH includes DL scheduling information (eg, DCI format 1_0 or 1_1). The DCI format 1_0 or 1_1 may include the following information.
[0109] - Frequency domain resource assignment: indicates the RB set assigned to PUSCH.
[0110] -Time domain resource assignment: Indicates the slot offset K2 and the starting position (e.g., OFDM symbol index) and duration (e.g., number of OFDM symbols) of the PUSCH in the slot. The starting symbol and length of the PUSCH may be indicated by a start and length indicator value (SLIV) or separately.
[0111] Then, the UE may transmit the PUSCH in slot #(n+K2) according to the scheduling information in slot #n. The PUSCH includes the UL-SCH TB.
[0112] Carrier Aggregation
[0113] NR can support wider UL / DL bandwidth by aggregating multiple UL / DL carriers (i.e., carrier aggregation). Signals can be sent / received in multiple carriers through carrier aggregation. When carrier aggregation is applied, each carrier (see Figure A2) may be referred to as a component carrier (CC). CCs may be adjacent or non-adjacent in the frequency domain. The bandwidth of each CC may be determined independently. Asymmetric carrier aggregation in which the number of UL CCs and the number of DL CCs are different from each other is also possible.
[0114] - Primary cell (PCell): A cell operating on a primary frequency (e.g., a primary component carrier (PCC)) on which a UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure in the case of a UE configured with carrier aggregation. A primary cell group (MCG) cell operating in a primary frequency on which a UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure.
[0115] - Secondary Cell (SCell): A cell that provides additional radio resources in addition to the special cell in case of a UE configured with carrier aggregation.
[0116] -Primary SCG cell (PSCell): A secondary cell group (SCG) cell to which a UE performs random access when performing RRC reconfiguration and synchronization processes in case of DC.
[0117] - Special cell (SpCell): In case of DC, the special cell refers to the PCell of the MCG or the PSCell of the SCG. Otherwise (ie, non-DC), the special cell refers to the PCell.
[0118] - ServCell: This refers to the cell configured in the UE in the RRC_CONNECTED state. When CA / DA is not configured, there is only one serving cell (ie, PCell). When CA / DA is configured, the serving cell refers to a special cell and a cell set including all SCells.
[0119] Control information may be configured to be sent and received only through special cells. For example, UCI may be sent via a special cell (e.g., PCell). When an SCell (hereinafter, PUCCH-SCell) that allows PUCCH transmission is configured, UCI may also be sent via PUCCH-SCell. As another example, the BS may allocate a scheduling cell (set) to reduce the complexity of PDCCH blind decoding (BD) on the UE side. For PDSCH reception / PUSCH transmission, the UE may perform PDCCH detection / decoding only in the scheduling cell. The BS may send PDCCH only through the scheduling cell (set). For example, a PDCCH for DL allocation may be sent in cell #0 (i.e., the scheduling cell), and the corresponding PDSCH may be sent in cell #2 (i.e., the 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 includes a special cell (e.g., PCell).
[0120] For cross-carrier scheduling, a carrier indicator field (CIF) is used. The CIF can 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 can be used to indicate the (serving) cell index of the scheduled cell.
[0121] - CIF disabled: CIF does not exist in PDCCH. The PDCCH on the scheduling cell allocates PDSCH / PUSCH resources on the same cell. That is, the scheduling cell is the same as the scheduled cell.
[0122] -CIF enabled: CIF is present in PDCCH. PDCCH in the scheduling cell can use CIF to allocate PDSCH / PUSCH resources on one of multiple cells. The scheduling cell can be the same or different from the scheduled cell. PDSCH / PUSCH means PDSCH or PUSCH.
[0123] Figure 7 is a diagram for explaining carrier aggregation. Figure 7 In FIG. 1 , it is assumed that three cells are aggregated. When CIF is disabled, each cell can only send a PDCCH that schedules its own PDSCH / PUSCH (self-carrier scheduling (SCS)). On the other hand, when CIF is enabled by UE-specific (or UE group-specific or cell-specific) high-layer signaling and cell A is configured as a scheduling cell, cell A can send not only a PDCCH that schedules the PDSCH / PUSCH of cell A, but also a PDCCH that schedules the PDSCH / PUSCH of other cells (i.e., the scheduled cell) (cross-carrier scheduling (CCS)). In this case, the PDCCH that schedules its own cell is not sent in cell B / C.
[0124] NR shared spectrum / unlicensed band (NR-U) operation
[0125] Figure 8 A wireless communication system supporting an unlicensed band is shown. For convenience, a cell operating in an authorized band (hereinafter, L-band) is defined as LCell, and a carrier of LCell is defined as (DL / UL)LCC. A cell operating in an unlicensed band (hereinafter, U-band) is defined as UCell, and a carrier of UCell is defined as (DL / UL)UCC. The carrier of a cell may represent an operating frequency (eg, center frequency) of the cell. Cells / carriers (eg, CCs) may be collectively referred to as cells.
[0126] When carrier aggregation is supported, one UE can send and receive signals to and from a BS in multiple aggregated cells / carriers. If multiple CCs are configured for one UE, one CC can be configured as a primary CC (PCC) and the other CCs can be configured as secondary CCs (SCCs). Specific control information / channels (e.g., CSS PDCCH and PUCCH) can be configured to send and receive signals only in the PCC. Data can be sent and received in the PCC and / or SCC. Figure 8 In (a), the UE and the BS transmit and receive signals in the LCC and the UCC (non-standalone (NSA) mode). In this case, the LCC may be configured as a PCC and the UCC may be configured as an SCC. If multiple LCCs are configured for the UE, one specific LCC may be configured as a PCC and the other LCCs may be configured as SCCs. Figure 8 (a) corresponds to LAA of the 3GPP LTE system. Figure 8 (b) shows a case where the UE and the BS send and receive signals in one or more UCCs without an LCC (SA mode). In this case, one UCC may be configured as a PCC and the other UCCs may be configured as SCCs. To this end, PUCCH, PUSCH, and PRACH transmissions may be supported. Both NSA mode and SA mode may be supported in the unlicensed band of the 3GPP NR system.
[0127] Unless otherwise stated, the following definitions apply to terms used in this disclosure.
[0128] - Channel: A carrier or a portion of a carrier including contiguous RBs for performing a channel access procedure (CAP) in a shared spectrum.
[0129] - Channel Access Procedure (CAP): A process of evaluating the availability of a channel based on sensing before signal transmission to determine whether the channel is used by other communication nodes. The basic unit of sensing is a sensing slot with a duration Tsl of 9us. When the BS or UE senses the channel during the sensing slot duration, and the power detected for at least 4us within the sensing slot duration is less than the energy detection threshold XThresh, the sensing slot duration Tsl may be considered idle. Otherwise, the 9us sensing slot duration Tsl may be considered busy. CAP may be referred to as Listen Before Talk (LBT).
[0130] - Channel occupancy: Transmissions from BS / UE on the channel after CAP.
[0131] - Channel Occupancy Time (COT): The total time that a BS / UE and any BS / UE that shares the channel occupancy perform transmissions on a channel after the BS / UE corresponding CAP. When determining the COT, if a transmission gap is less than or equal to 25us, the gap duration may also be included in the COT. Transmissions between a BS and a corresponding UE may share the COT.
[0132] -DL transmission burst: A collection of transmissions from a BS without any gaps greater than 16us. Transmissions from a BS separated by gaps greater than 16us are considered separate DL transmission bursts. The BS may perform transmissions after gaps within a DL transmission burst without sensing channel availability.
[0133] -UL transmission burst: A set of transmissions from a UE without any gaps greater than 16us. Transmissions from a UE separated by gaps greater than 16us are considered separate UL transmission bursts. The UE may perform transmissions after a gap within a UL transmission burst without sensing channel availability.
[0134] - Discovery Burst: A DL transmission burst that includes a set of signals and / or channels confined within a window and associated with a duty cycle. In an LTE-based system, a discovery burst may be a transmission initiated by the BS, including a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a cell-specific reference signal (CRS), and also includes a non-zero power CSI-RS. In an NR-based system, a discovery burst may be a transmission initiated by the BS, including at least a SS / PBCH block, and also includes a CORESET for scheduling a PDSCH with SIB1, a PDSCH carrying SIB1, and / or a PDCCH with non-zero power CS-RS.
[0135] Fig. 9A method for occupying resources in an unlicensed band is shown. According to regional regulations regarding unlicensed bands, communication nodes in unlicensed bands need to determine whether other communication nodes use channels before signal transmission. Specifically, a communication node may first perform carrier sensing (CS) before signal transmission to check whether other communication nodes send signals. If it is determined that other communication nodes do not send signals, this means confirming an idle channel assessment (CCA). When there is a CCA threshold configured by high-level (e.g., RRC) signaling or a predefined CCA threshold, if energy above the CCA threshold is detected in the channel, the communication node may determine that the channel is in a busy state, otherwise, the communication node may determine that the channel is in an idle state. For reference, in the Wi-Fi standard (802.11ac), the CCA threshold is set to -62dBm for non-Wi-Fi signals and -82dBm for Wi-Fi signals. When it is determined that the channel is in an idle state, the communication node may start sending signals in the UCell. The above process may be referred to as listen-before-talk (LBT) or a channel access procedure (CAP). LBT and CAP are used interchangeably.
[0136] Table 6 shows an exemplary CAP supported in NR-U.
[0137] [Table 6]
[0138]
[0139] Multi-cell scheduling DCI
[0140] NR supports wide spectrum across various frequency ranges. The availability of 5G Advanced spectrum is expected to increase through the reallocation of frequency bands used in previous generations. In particular, for low-band FR1, available spectrum blocks tend to be further segmented and distributed. For FR2 bands and some FR1 bands, the available spectrum can be widened, so multiple carriers / cells need to operate within the band. There is a need to improve throughput and coverage by using these distributed spectrum bands or wider bandwidth spectrum in a more energy-efficient and flexible manner.
[0141] It is important to increase flexibility and spectrum / power efficiency when scheduling data across multiple cells (including intra-band cells and inter-band cells), but in the current 5G NR scheduling scheme, DCI may only perform PUSCH / PDSCH scheduling for a single cell. However, in the future, due to spectrum expansion / changes, etc., the demand for simultaneous scheduling of multiple cells is expected to increase. In order to reduce the control overhead caused by scheduling, it is advantageous to perform PUSCH / PDSCH scheduling of multiple cells through a single DCI.
[0142] In order to reduce the DCI overhead required for PDSCH / PUSCH scheduling when multiple cells are configured for carrier aggregation (CA) in the future, a multi-cell scheduling method in Rel-18 may be considered to simultaneously schedule multiple (serving) cells / CCs (through which PDSCH / PUSCH transmissions are transmitted) with a single DCI.
[0143] Therefore, for the design of the DCI structure (multi-cell DCI structure) for performing the above-mentioned multi-cell scheduling, a method for configuring and interpreting each field in the corresponding DCI is proposed. The part of this specification that mainly describes the multi-cell scheduling operation for PUSCH or PDSCH transmission can also be applied to the operating principle of the proposed method in the same manner as the multi-cell scheduling for PDSCH or PUSCH transmission, respectively. In this specification, a cell may refer to the (active) BWP configured / indicated to the corresponding cell.
[0144] Hereinafter, the multi-cell scheduling DCI may be referred to as multi-cell DCI or simply DCI, and may include at least one of a DL grant DCI for scheduling a PDSCH and a UL grant DCI for scheduling a PUSCH.
[0145] Hereinafter, the reference cell may be determined based on at least one of the following i) to viii), but is not limited thereto. i) The cell with the lowest (or highest) cell index within the cell combination (co-scheduled cell set or each cell subgroup) scheduled simultaneously by the same multi-cell DCI (or within each cell subgroup described below); ii) The cell with the earliest (or latest) indicated PDSCH / PUSCH transmission start symbol time (when there are multiple cells with the earliest (or latest) PDSCH / PUSCH start symbol time, the cell with the lowest (or highest) cell index among the multiple cells); iii) The cell with the earliest (or latest) indicated PDSCH / PUSCH transmission end symbol time among the simultaneously scheduled cell combination. symbol time (when there are multiple cells with the earliest (or latest) PDSCH / PUSCH end symbol time, the cell with the lowest (or highest) cell index among the multiple cells); iv) a cell pre-designated by a CIF field value or a cell indicated by RRC; v) a cell with the lowest (or highest) cell index in a schedulable cell set (i.e., a schedulable cell set) of all cells that can be scheduled via any multi-cell DCI; vi) a cell indicated by a CIF field value; vii) a cell to which the multi-cell DCI is sent; and / or viii) a cell previously designated via RRC.
[0146] For the fields to which the shared reference cell method, shared cell common method and shared state extension method proposed in the present disclosure are applied, i) only one field may be configured in the multi-cell DCI (i.e., commonly applied to all cells belonging to the co-scheduled cell set), ii) in a state where all cells belonging to the co-scheduled cell set are grouped into one or more (multiple) cell subgroups, one (commonly applied) DCI field may be configured for each cell subgroup (a separate / independent field may be configured between cell subgroups), or iii) in a state where all cells belonging to the schedulable cell set may be grouped into one or more (multiple) cell subgroups, one DCI field (commonly applied) may be configured for each cell subgroup (a separate / independent field may be configured between cell subgroups) (i.e., the shared reference cell / shared cell common / shared state extension method and the field / information configuration / indication method based thereon may be applied to each cell subgroup). Each cell subgroup may be configured / set by a specific cell or specific multiple cells belonging to the co-scheduled cell set or the schedulable cell set (e.g., some or all cells belonging to the co-scheduled cell set or the schedulable cell set).
[0147] In detail, the cell subgroup configuration (grouping) may be i) independently configured for each DCI field, or ii) may be configured for each field group (including one or more DCI fields) (in this case, the same cell subgroup configuration is applied to the DCI fields belonging to the same group). In addition, in the case of the cell subgroup configuration (grouping), i) regardless of the number of (candidate) BWPs configured for each cell (belonging to the schedulable cell set or the co-scheduled cell set) and the (active) BWP combination of each cell, the cell subgroup may be configured / applied (at the cell level) (for example, in a state where, for cells 1 / 2 / 3 / 4, cells 1 and 2 are configured as one subgroup and cells 3 and 4 are configured as another subgroup, the subgroup configuration is always applied regardless of changes in the (active) BWP combination of each cell), or ii) for each cell (belonging to the schedulable cell set or the co-scheduled cell set) Each combination of (active) BWP configures a cell subgroup (independently) (for example, in a case where the (active) BWP of cells 1 / 2 / 3 / 4 is a specific combination, cells 1 and 2 are configured as one subgroup and cells 3 and 4 are configured as another subgroup, and when the (active) BWP of 1 / 2 / 3 / 4 is another specific combination, it can be a structure in which cells 1, 2, and 3 are configured as one subgroup and only cell 4 is configured as another subgroup. In the case of a DCI field that is subjected to cell subgrouping configuration / application or configured based on the cell subgrouping configuration, at least some of the following DCI fields may be included, but are not limited thereto.
[0148] - Frequency Domain Resource Assignment (FDRA) field
[0149] -Time Domain Resource Assignment (TDRA) field
[0150] - Modulation and Coding Scheme (MCS) field
[0151] -HARQ Process Number (HPN) field
[0152] - Antenna Port (AP) field
[0153] -Transmission Configuration Indication (TCI) field
[0154] -SRS Resource Indicator (SRI) field
[0155] - Precoding Information and Layer Number (TPMI) field
[0156] -DMRS sequence initialization (DMRS init) field
[0157] -PTRS-DMRS Association (PTRS asso) field
[0158] - VRB to PRB Mapping (RB Mapping) field
[0159] -PRB Bundling Size Indicator (PRB Bundling) field
[0160] - Beta_offset indicator (β offset) field (eg, information about a β offset parameter used for (rate matching to) determine the number of modulation symbols (number of REs))
[0161] - Frequency Hopping Flag (FH) field
[0162] -TPC command (TPC) field for scheduled PUSCH
[0163] - ChannelAccess-CPext-CAPC (for PUSCH) (LBT) field (e.g., information about channel access type and CP extension on shared spectrum, may additionally provide channel access priority (CAPC) information)
[0164] - Open loop power control parameter set indication (OLPC) field
[0165] As a case where the DCI field of the shared cell common method proposed in the present specification is an existing one (scheduling based on a single-cell DCI), when one of the (multiple) states / indexes in the corresponding table is indicated in a state where a table in which one or more (multiple) states / indexes (including different parameters / values (combinations)) is configured for each cell in advance (or defined) by RRC or MAC-CE (for example, in the case of the following CSI request and / or Beta_offset indicator and / or ChannelAccess-CPext-CAPC (LBT) and / or OLPC parameter set indication and / or invalid symbol pattern indicator and / or TDRA field and / or MCS field and / or AP field and / or TCI field and / or SRI field and / or TPMI field), the DCI field commonly configured to a cell set (for example, a co-scheduled cell set or a cell subgroup) to which the shared cell common method is applied is indicated. The specific state / index / code point indicated by the I field (option X) may be interpreted / applied (i.e., for each cell) as a parameter / value (combination) corresponding to a corresponding state / index / code point in a table configured for each cell belonging to the cell set, (option Y) a parameter / value (combination) corresponding to a state / code point / index in a table configured for a specific reference cell in the corresponding cell set may be commonly applied to the cells belonging to the corresponding cell set (e.g., in the case of ChannelAccess-CPext-CAPC (LBT)), or (option Z) in a separate (common) table commonly applied to the corresponding cell set pre-configured in RRC / MAC-CE in the same manner as described above, a parameter / value (combination) corresponding to a corresponding state / code point / index in a common table may be commonly applied to the cells belonging to the cell set (e.g., in the case of ChannelAccess-CPext-CAPC (LBT)). For example, Fig.10 2 is a diagram for explaining the case where Option X is applied to the DCI field to which the shared cell common method is applied. Fig.10, assuming that the co-scheduled cell set may include at most N cells, the actual number of cells co-scheduled by one multi-scheduling DCI may be N or less, for which various combinations of N or less co-scheduled cells may be configured. The value indicated by a state (code point) of the shared cell common DCI field may be independently configured for each cell. For example, assuming that a first state / code point (e.g., 00) is indicated, the first state / code point may mean a value a for cell #1, a value b for cell #2, and a value c for cell #N. Configuring values independently for the respective cells includes (but is not limited to) configuring different values in different cells, and may not exclude configuring the same value for two or more cells. That is, it is sufficient that the values between the cells are independently configured, and there may be no constraint that the independently configured values need to be the same or different. Some cells may not have values configured for the corresponding state / code point. For example, for the i-th state / code point, cell #2 may have a value x, but cell #1 and cell / #N may not have values configured. Information (e.g., a table) containing cell values to be applied to interpret the shared cell common DCI field may be configured in the UE (for each cell). As described above, each of the Beta_offset indicator field, the ChannelAccess-CPext field, the OLPC parameter set indication field, the antenna port (AP) field, the SRS resource indication (SRI) field, and / or the precoding and layer number information (TPMI) field may correspond to a different shared cell common DCI field. For example, the Beta_offset indicator field may be a first shared cell common DCI field of a first table configurable (for each cell), the ChannelAccess-CPext field may be a second shared cell common DCI field of a second table configurable (for each cell), the OLPC parameter set indication field may be a third shared cell common DCI field of a third table configurable (for each cell), the antenna port (AP) field may be a fourth shared cell common DCI field of a fourth table configurable (for each cell), the SRS resource indication (SRI) field may be a fifth shared cell common DCI field of a fifth table configurable (for each cell), and the precoding and layer information (TPMI) field may be a sixth shared cell common DCI field of a sixth table configurable (for each cell), but is not limited thereto.
[0166] When multiple cells are scheduled through multi-cell DCI, a method (e.g., a shared cell common method or a shared state extended method) of simultaneously indicating a parameter / value combination to be applied to multiple cells by indicating a specific state / code point / index in a corresponding table based on a (multi-cell) joint table in which each state / code point / index (row) is configured with a combination of multiple parameters / values of multiple cells through a DCI field may be applied to a specific field (e.g., a CSI request and / or a Beta_offset indicator and / or a ChannelAccess-CPext-CAPC (LBT) and / or an OLPC parameter set indication and / or an invalid symbol pattern indicator and / or a TDRA field and / or an MCS field and / or an AP field and / or a TCI field and / or an SRI field and / or a TPMI field), and when only one cell is scheduled through multi-cell DCI, the state / code point / index indicated by the specific field may be interpreted / applied as a parameter / value (corresponding to the state / code point / index) in a (single cell) table of a scheduling configuration based on a single-cell DCI for the corresponding cell.
[0167] [Common-T1A: Invalid state handling]
[0168] First, a more specific example of the shared cell common method (specifically, the option X method) is presented as follows.
[0169] First, for a specific DCI field in the existing single-cell DCI-based scheduling, when one of the N states / code points / indexes is indicated through the DCI field in a state where N (different) parameters / values (combinations) are pre-configured for each of the N states / code points / indexes indicated by the DCI field through RRC or MAC-CE, the UE can perform PDSCH / PUSCH transmission / reception operations by applying the parameters / values (combination) configured to the indicated state / code point / index, and in this case, the size of the DCI field can be determined by ceil{log2(N)} bits, where N can be configured to different (or the same) values for each cell.
[0170] For reference, in the present disclosure, ceil(X) means a minimum integer greater than or equal to X, and a value obtained by performing a modulo B operation on A means a remainder when A is divided by B.
[0171] For a specific DCI field in multi-cell DCI-based scheduling, when a specific state / code point / index is indicated through a corresponding DCI field in a state where parameters / values (combinations) of various states / code points / indexes are pre-configured for each cell as described above (applicable to scheduling based on single-cell DCI), the UE can perform the sending / receiving operation of the PDSCH / PUSCH scheduled for each cell by interpreting / applying the parameters / values (combination) configured for each cell for the indicated state / code point / index.
[0172] In multi-cell DCI based scheduling, among the N values configured for the corresponding cell of the corresponding cell set belonging to the entire schedulable cell set (or each co-scheduled cell set), the size of a specific DCI field may be determined as (Alternative A) ceil{log2(N_max)} bits based on a maximum value N_max (in this case, it may be a structure indicating at most (initial) N_max states / code points / indexes through the DCI field) or (Alternative B) ceil{log2(N_min)} bits based on a minimum value N_min (in this case, it may be a structure indicating at most (initial) N_min states / code points / indexes through the DCI field).
[0173] [Common-T2: Field size determination]
[0174] An example of a method of determining a DCI field size when a separate method is applied is described below.
[0175] First, for a specific DCI field in an existing single-cell DCI, the size of the corresponding DCI field may be configured as L=ceil{log2(N)} bits (when N states / code points / indexes are to be indicated by the corresponding DCI field), where L may be configured as different (or the same) values for each cell.
[0176] When a specific DCI field in a multi-cell DCI is configured based on a separate method, first, the sum L_sum of L values configured for each of multiple (for example, N_co) co-scheduled cell sets configured in the entire schedulable cell set can be calculated, and the maximum value of the N_co L_sum values calculated for each of the N_co co-scheduled cell sets can be determined as the size of the specific DCI field (configured in the multi-cell DCI).
[0177] [Reference SC-DCI format for MC-DCI field]
[0178] When the shared cell common method (based on the Option X method) and / or the individual method (and / or the shared reference cell method and / or the shared state extension method) is applied to a specific DCI field, if the N states / code points / indexes indicated by the corresponding DCI fields configured in the single-cell DCI of each cell (belonging to the schedulable cell set or the co-scheduled cell set) and the size LL=ceil{log2(N)} of the corresponding DCI field are referred to, it may be necessary to determine which single-cell DCI format (defined as "reference DCI format" for convenience) to represent the N states / code points / indexes and the corresponding field size L value.
[0179] In detail, for DL, when only one of DCI format 1_1 and DCI format 1_2 is configured for a specific cell, the configured corresponding DCI format may be determined / referenced as a reference DCI format, and when both DCI format 1_1 and DCI format 1_2 are configured, the BS may configure (option 1) DCI format 1_2 to be determined / referenced as a reference DCI format, (option 2) DCI format 1_1 to be determined / referenced as a reference DCI format, or (option 3) whichever of the two is determined / referenced as a reference DCI format (when neither DCI format 1_1 nor DCI format 1_2 is configured, DCI format 1_0 may be determined / referenced as a reference DCI format).
[0180] For UL, when only one of DCI format 0_1 and DCI format 0_2 is configured for a specific cell, the configured corresponding DCI format may be determined / referenced as a reference DCI format, and when both DCI format 0_1 and DCI format 0_2 are configured, the BS may configure (option 1) DCI format 0_2 to be determined / referenced as a reference DCI format, (option 2) DCI format 0_1 to be determined / referenced as a reference DCI format, or (option 3) whichever of the two is determined / referenced as a reference DCI format (when neither DCI format 0_1 nor DCI format 0_2 is configured, DCI format 0_0 may be determined / referenced as a reference DCI format).
[0181] [Determination of the entire MC-DCI payload size]
[0182] The following method may be considered as a method of determining the total payload size of multi-cell DCI (format).
[0183] For each DCI field, when the shared cell common method (defined as a "Type-1A" field for convenience) (based on the Option X method) and / or the individual method (defined as a "Type-2" field for convenience) and / or the shared reference cell method (defined as a "Type-1C" field for convenience) and / or the shared state extension method (defined as a "Type-1B" field for convenience) are applied, first, for each of multiple (e.g., N_co) co-scheduled cell sets configured in the entire schedulable cell set, the size and P_sum of all Type-1A / 1B / 1C / 2 fields required for scheduling the corresponding co-scheduled cell set (the cells belonging to it) are calculated, and the maximum value among the N_co P_sum values calculated for each of the N_co co-scheduled cell sets can be determined as the payload size of the multi-cell DCI (format).
[0184] Configure the UL (or DL) DCI field for multi-cell PUSCH (or PDSCH) scheduling
[0185] The various methods of configuring DCI fields described below (e.g., methods 1 to 7) may be understood as types applied to each DCI field, and not all fields of the multi-cell scheduling DCI may be configured in a specific method. For example, in a multi-cell scheduling DCI, the first DCI field may be configured based on method X, and the second DCI field may be configured based on method Y. For ease of explanation, the classification of the following methods assumes the most detailed configuration form, so a single DCI field may be configured by a combination of different DCI field configuration methods within a non-conflicting range. For example, a single type 1A DCI field may be configured by a combination of method 3: shared cell common and method 4: shared state extension, in which case the interpretation / application of a single type 1A DCI field common to all cells may be independent for each cell.
[0186] 1) DCI field configuration type
[0187] A. Method 1: Shared reference cell
[0188] i. Only one field may be configured in a multi-cell DCI, and the value indicated by the corresponding DCI field may be applied only to a specific reference cell (e.g., the cell to which the DCI is sent, the cell with the lowest (or highest) cell index, or the cell indicated by the CIF field value) among the cells scheduled by the multi-cell DCI (configuration operates according to the indication of the DCI field), and a predefined / configured specific default value may be applied to the remaining cells.
[0189] 1. The reference cell may be determined as the cell having the earliest (or latest) PDSCH / PUSCH transmission start symbol time on the corresponding cell (when there are multiple cells having the earliest (or latest) PDSCH / PUSCH start symbol time, it is determined as the cell having the lowest (or highest) cell index among the corresponding multiple cells), or may be determined as the cell having the earliest (or latest) PDSCH / PUSCH transmission end symbol time on the corresponding cell (or when there are multiple cells having the earliest (or latest) PDSCH / PUSCH end symbol time, it is determined as the cell having the lowest (or highest) cell index).
[0190] B. Method 2: Sharing a single cell
[0191] i. The corresponding DCI field can be configured only when only (at most) one field is configured in the multi-cell DCI and one cell is scheduled (via the multi-cell DCI). The value indicated by the field applies to this one cell. When multiple cells are scheduled, the corresponding DCI field may not be configured and may be omitted (in this case, the predefined / configured specific default value corresponds to multiple cells).
[0192] C. Method 3: Shared Community Public
[0193] i. Only one field may be configured within a multi-cell DCI, and the value indicated by the DCI field may be commonly applied to all cells (scheduled by the multi-cell DCI).
[0194] D. Method 4: Shared State Extension
[0195] i. Only one field may be configured within a multi-cell DCI, and each of the multiple states / code points indicated by the DCI field may be configured / set to a combination of multiple pieces of information about multiple cells (rather than information about a single cell).
[0196] ii. As mentioned above, the distinction between Method 4 and Method 3 is for the convenience of explanation. Method 4: Shared state extension can also be understood as a specific form of Method 3: Shared cell common.
[0197] E. Method 5: Alone
[0198] i. The number of fields (within DCI) is configured to be as many as the number of cells scheduled by multi-cell DCI (whose operation is configured according to the indication of the corresponding DCI field), and each scheduled cell is assigned a separate field so that the value indicated by the corresponding field applies to the corresponding cell.
[0199] F. Method 6: Omit
[0200] i. A method of not configuring and omitting the corresponding DCI field in the multi-cell DCI (in this case, a predefined / configured specific default value is applied to the cells scheduled by the multi-cell DCI).
[0201] G. Method 7: This may be a method of configuring which method between Method 3 and Method 5 is applied for a specific DCI field.
[0202] i. A method of configuring (from the BS to the UE) which method of method 3 (common to shared cells) and method 5 (individual) is applied to each cell combination (for each scheduled cell combination) simultaneously scheduled for a specific DCI field by the same multi-cell DCI.
[0203] 1. For example, when scheduled cell combination #1 includes {cell #1, cell #2} and scheduled cell combination #2 includes {cell #1, cell #3}, in the case of scheduled cell combination #1, it is configurable which method between method 3 and method 5 is applied to configure / indicate a specific field, and (independently) in the case of scheduled cell combination #2, it is configurable which method between method 3 and method 5 is applied to configure / indicate a specific field.
[0204] 2. The specific DCI field may include at least one of the following.
[0205] - Frequency Domain Resource Assignment (FDRA) field
[0206] -Time Domain Resource Assignment (TDRA) field
[0207] - Modulation and Coding Scheme (MCS) field
[0208] -HARQ Process Number (HPN) field
[0209] - Antenna Port (AP) field
[0210] -Transmission Configuration Indication (TCI) field
[0211] -SRS Resource Indicator (SRI) field
[0212] - Precoding Information and Layer Number (TPMI) field
[0213] -DMRS sequence initialization (DMRS init) field
[0214] -PTRS-DMRS Association (PTRS asso) field
[0215] - VRB to PRB Mapping (RB Mapping) field
[0216] -PRB Bundling Size Indicator (PRB Bundling) field
[0217] -Beta_offset indicator (β offset) field
[0218] - Frequency Hopping Flag (FH) field
[0219] -TPC command (TPC) field for scheduled PUSCH
[0220] - Open loop power control parameter set indication (OLPC) field
[0221] 2) DCI field type signaling (Type 3 DCI field)
[0222] Which method is applied for a specific DCI field can be configured from method 1 or method 2 or method 3 or method 4 (for convenience, these methods are defined as "Type-1x method") and method 5 (for convenience, this method is defined as "Type-2 method").
[0223] A method may be provided (BS to UE) to configure which method between the Type-1x method and the Type-2 method is applied for co-scheduled cells simultaneously scheduled by the same multi-cell DCI for a specific DCI field (this method is conveniently defined as "Type-3 method").
[0224] When applying the Type-3 method to multiple (e.g., N) DCI fields, the N DCI fields can be divided into multiple (e.g., K (<N)) field groups, and for each field group, the structure can configure which method between the Type-1x method and the Type-2 method to apply to all fields belonging to that field group.
[0225] Therefore, all fields belonging to the same field group can be configured to apply only one method (e.g., all apply only the Type-1x method or all apply only the Type-2 method), fields belonging to the same field group can be configured not to apply different methods, and fields in different field groups can be configured to apply the same method or different methods.
[0226] Therefore, when configuring to apply the same (Type-1x or Type-2) method to all fields belonging to a field group as described above, the implementation complexity required by the UE (e.g., the number of cases that need to be tested by the UE) can be reduced from approximately (2 N ) to approximately 2 K .
[0227] The DCI fields to which the Type-3 method (Type-1x / 2 method setting based on field group units) is applied can correspond to at least some (or all) of the following.
[0228] - HARQ process number (for convenience, called HPN)
[0229] - MCS (for convenience, called MCS)
[0230] - Bandwidth part indicator (for convenience, called BWP)
[0231] - Frequency domain resource assignment (for convenience, called FDRA)
[0232] - VRB to PRB mapping (for convenience, called V2P)
[0233] - PRB bundling size indicator (for convenience, called bund)
[0234] - Rate matching indicator (for convenience, called RM)
[0235] - ZP CSI-RS trigger (for convenience, called ZCR)
[0236] - Antenna port (for convenience, called AP)
[0237] - Transmission configuration indication (for convenience, called TCI)
[0238] - DMRS sequence initialization (for convenience, called DMRS)
[0239] -Frequency Hopping Flag (referred to as FH for convenience)
[0240] -TPC command for scheduled PUSCH (referred to as TPC for convenience)
[0241] - Precoding information and number of layers (referred to as TPMI for convenience)
[0242] -PTRS-DMRS association (referred to as PTRS for convenience)
[0243] -SRS request (for convenience, referred to as A-SRS)
[0244] -SRS Resource Indicator (referred to as SRI for convenience)
[0245] -SRS offset indicator (referred to as SOI for convenience)
[0246] - Open loop power control parameter set indication (for convenience, referred to as OLPC)
[0247] For example, the above-mentioned MCS and AP and / or TCI and / or TPMI and / or SRI may belong to the same field group.
[0248] For example, the above-mentioned FDRA and V2P and / or bund may belong to the same field group.
[0249] For example, the above-mentioned V2P and bund may belong to the same field group.
[0250] For example, the above-mentioned RM and ZCR may belong to the same field group.
[0251] For example, the above-mentioned AP and TCI and / or TPMI and / or SRI may belong to the same field group.
[0252] For example, the above-mentioned DMRS and PTRS may belong to the same field group.
[0253] For example, the above-mentioned TPC and OLPC may belong to the same field group.
[0254] For example, the above-mentioned A-SRS and SOI may belong to the same field group.
[0255] 3) Application example of the method through the DCI field
[0256] A.UL / SUL designator
[0257] i. Option 1: Example of applying the shared reference cell method
[0258] 1. The value (UL index) indicated by the DCI field may only be applied to a specific reference cell (among cells scheduled via multi-cell DCI) for which the SUL carrier is configured via the parameter supplementaryUplink. For the remaining cells, the currently operated UL carrier may be maintained without UL carrier switching.
[0259] ii. Option 2: Example of applying the shared single cell approach
[0260] 1. The corresponding DCI field may be configured only when one cell is scheduled (via multi-cell DCI) (or only when one cell with a SUL carrier configured is scheduled) (and the value indicated thereby (UL index) may be applied to the corresponding cell), and when multiple cells are scheduled (or when multiple cells are scheduled or one cell without a SUL carrier configured) the corresponding DCI field may not be configured and may be omitted (in this case, the currently operating UL carrier may be maintained without UL carrier switching for the corresponding (multiple) cells).
[0261] iii. Option 3: Example of applying the omission method
[0262] 1. The corresponding DCI field may not be configured and may be omitted within the multi-cell DCI (in this case, the currently operating UL carrier may be maintained without UL carrier switching to the cell scheduled by the multi-cell DCI).
[0263] B. Frequency Hopping (FH) Flag
[0264] i. Option 1: Example of applying the common method of shared cells
[0265] 1. The value indicated by the corresponding DCI field (whether to apply FH) can be commonly applied to PUSCH on all cells (scheduled by multi-cell DCI), and all cells can be all cells configured with the FH flag (among the cells scheduled by multi-cell DCI).
[0266] ii. Option 2: Example of applying the shared reference cell method
[0267] 1. The value indicated by the DCI field (whether FH is applied) can be applied only to the PUSCH on a specific reference cell (among the cells scheduled by multi-cell DCI) configured with the FH flag, and assuming that FH is not applied to the PUSCH on the remaining cells, PUSCH can be sent (without FH).
[0268] iii. Option 3: Example of applying the shared single cell approach
[0269] 1. The corresponding DCI field may be configured only when one cell is scheduled (via multi-cell DCI) (or only when one cell with the FH flag configured is scheduled) (and the value indicated thereby (whether FH is applied) may be applied to the PUSCH on the corresponding cell), when multiple cells are scheduled (or when multiple cells are scheduled or one cell with the FH flag not configured is scheduled), the corresponding DCI field may not be configured and may be omitted (in this case, assuming that FH is not applied to the PUSCH on multiple cells, PUSCH is sent (without FH).
[0270] iv. Option 4: Example of applying the elision method
[0271] 1. The corresponding DCI field may not be configured and may be omitted in the multi-cell DCI (in this case, assuming that FH is not applied to PUSCH on the cell scheduled by the multi-cell DCI, PUSCH may be transmitted (without FH)).
[0272] v. Note 0: In this case, the specific reference cell may be determined as a specific cell among the cells configured with the FH flag (in the existing single-cell (scheduling) DCI).
[0273] vi. Note 1: In this case, for cell A configured with an FH flag / indicator (within the existing single-cell (scheduling) DCI) and cell B not configured with an FH flag / indicator, it can be configured / restricted so that only cell A or only cell B belongs to the same cell subgroup (i.e., so that cell A and cell B do not belong together), and in this state, the shared reference cell or shared cell common method can be applied separately to each cell subgroup.
[0274] vii. Note 2: As another method, cell A and cell B may be configured to belong to the same cell subgroup, and in this state, the shared reference cell or shared cell common method may be applied individually to each cell subgroup.
[0275] 1. When the shared cell common method is applied to the cell subgroup to which the above-mentioned cell A and cell B belong, a) assuming that the indicator field configuration is omitted and FH is not always applied to the cell subgroup, PUSCH (without FH) may be transmitted, b) it is considered / assumed that there is no scheduling for cell B when the indicator field is configured for the cell subgroup and the application of FH is indicated by the corresponding field, or c) assuming that the indicator field is configured for the cell subgroup and FH is not always applied to cell B, PUSCH (without FH) may be transmitted.
[0276] 2. A cell subgroup may be considered / applied as a co-scheduled cell set (all cells belonging to the corresponding set).
[0277] C. Downlink Assignment Index (DAI)
[0278] i. Option 1: Example of applying the common method of shared cells
[0279] The value indicated by the corresponding DCI field (DAI value) may be commonly applied to PUSCH on all cells (scheduled via multi-cell DCI).
[0280] ii. Option 2: Example of applying the shared reference cell method
[0281] The value (DAI value) indicated by the corresponding DCI field may be applied only to the PUSCH on a specific reference cell (among the cells scheduled via multi-cell DCI), and a specific DAI value (e.g., 4) may be assumed for the PUSCH on the remaining cells, or the cell may operate assuming that there is no indication / corresponding DAI (in this case, the HARQ-ACK payload to be multiplexed on the corresponding PUSCH is configured based on the counter / total-DAI indicated / received via DL DCI) (similar to PUSCH based on configuration permission).
[0282] The PUSCH on the reference cell may be determined as: alternative 1) the PUSCH on the cell with the lowest cell index (among the cells scheduled with the same multi-cell DCI); alternative 2) the PUSCH with the earliest transmission start symbol time (when there are multiple PUSCHs with the earliest start symbol time, the PUSCH on the cell with the lowest cell index among the multiple PUSCHs); or alternative 3) the PUSCH selecting the multiplexed HARQ-ACK.
[0283] iii. Option 3: Example of applying the shared single cell approach
[0284] When only one cell is scheduled (via multi-cell DCI), the corresponding DCI field may be configured (the value indicated by it (DAI value) is applied to the PUSCH on the corresponding cell), and when multiple cells are scheduled, the corresponding DCI field may not be configured and may be omitted (in this case, a specific DAI value (e.g., 4) is assumed for the PUSCH on multiple cells, or the cell may operate assuming that there is no indication / corresponding DAI (in this case, the HARQ-ACK payload to be multiplexed on the corresponding PUSCH is configured based on the counter / total-DAI indicated / received via the DLDCI).
[0285] iv. Option 4: Example of applying the elision method
[0286] In a multi-cell DCI, the corresponding DCI field may be omitted and not configured (in which case a specific DAI value (e.g., 4) is assumed for the PUSCH on the cell scheduled by the multi-cell DCI), or it may be assumed that there is no indication / corresponding DAI (in which case the HARQ-ACK payload multiplexed on the corresponding PUSCH is configured based on the counter / total-DAI indicated / received by the DLDCI).
[0287] D. TPC command for scheduled PUSCH
[0288] i. Option 1: Example of applying the common method of shared cells
[0289] The value (TPC value) indicated by the corresponding DCI field may be commonly applied to PUSCH on all cells (scheduled via multi-cell DCI).
[0290] ii. Option 2: Example of applying the shared reference cell method
[0291] The value (TPC value) indicated by the DCI field may be applied only to the PUSCH on a specific reference cell (among cells scheduled by multi-cell DCI), and the PUSCH may be transmitted assuming that there is no TPC value indication for the PUSCH on the remaining cells.
[0292] iii. Option 3: Example of applying the shared single cell approach
[0293] The corresponding DCI field (the value indicated by it (TPC value) is applied to the PUSCH on the corresponding cell) can be configured only when one cell is scheduled (via multi-cell DCI). When multiple cells are scheduled, the corresponding DCI field may not be configured and may be omitted (in this case, it is assumed that there is no TPC value indication for the PUSCH on multiple cells and the PUSCH is sent).
[0294] iv. Option 4: Example of applying the elision method
[0295] The corresponding DCI field may not be configured and may be omitted in the multi-cell DCI (in this case, assuming that there is no TPC value indication for the PUSCH on the cell scheduled by the multi-cell DCI, the PUSCH may be sent).
[0296] v. Option 5: Example of applying separate methods
[0297] For each of a plurality of cells scheduled via a multi-cell DCI, a TPC field / information may be individually configured / indicated, and in this case, the TPC field of each cell may be configured with 1 bit and may indicate one of values of 0 dB and X dB (e.g., X=1 or X=3 or X=-1) or one of values of X dB and -X dB (e.g., X=1 or X=4).
[0298] When only one cell is scheduled through the multi-cell DCI, the TPC field of the corresponding cell is configured with 2 bits as before, and one of four predefined values can be indicated through the corresponding field.
[0299] vi. Note: As another method of option 1 above, a shared cell common method may be applied to cells configured in a cumulative TPC mode in which TPC values received until the current time point are accumulated and applied, and cells configured in an absolute TPC mode in which only TPC values received at the current time point are instantaneously applied without accumulation, so that the value indicated by a single TPC field corresponding to a cell in the cumulative TPC mode may be commonly applied only to the corresponding cell, and the value indicated by a single TPC field corresponding to a cell in the absolute TPC mode may be commonly applied only to the corresponding cell.
[0300] vii. Note A: In this case, the shared reference cell or shared cell common method may be applied individually to each cell subgroup.
[0301] 1. Here, each cell subgroup may consist of only cells configured in cumulative TPC mode or only cells configured in absolute TPC mode, and the cells configured in cumulative TPC mode and the cells configured in absolute TPC mode may be configured such that the cells do not belong to the same cell subgroup.
[0302] 2. When the shared cell common method is applied to the above-mentioned respective cell subgroups, the TPC field / information may be separately configured / indicated for each cell subgroup scheduled by the multi-cell DCI, and in this case, the TPC field of each cell subgroup may be configured with 1 bit, and one of the values of 0 dB and X dB (e.g., X=1 or X=3 or X=-1) may be indicated through the field, or one of the values of X dB and -X dB (e.g., X=1 or X=4) may be indicated (the indicated values are commonly applied to the multiple cells belonging to the cell subgroup).
[0303] a. When only one cell is scheduled through the multi-cell DCI, the TPC field of the corresponding cell is configured with 2 bits as before, and one of four predefined values can be indicated through the corresponding field.
[0304] E.CSI Request
[0305] i. Option 1: Example of applying the shared reference cell method
[0306] The CSI report indicated by the DCI field can be applied only to the PUSCH on a specific reference cell (among the cells scheduled by the multi-cell DCI), and assuming that there is no CSI report indication for the PUSCH on the remaining cells, the PUSCH can be transmitted.
[0307] A. The PUSCH on the reference cell can be determined as: Alternative 1) the PUSCH on the cell with the lowest (or highest) cell index (among the cells scheduled by the same multi-cell DCI); or Alternative 2) the PUSCH with the earliest (or latest) transmission start symbol time (when there are multiple PUSCHs with the earliest (or latest) start symbol time, the PUSCH on the cell with the lowest (or highest) cell index among the multiple PUSCHs). For example, Fig.11 An example showing the CSI request field applying Alternative 1) is presented. In Fig.11 , the UE can receive the multi-cell scheduling DCI through the PDCCH. The multi-cell scheduling DCI can be in the UL grant DCI format. The multi-cell scheduling DCI allows for co-scheduling of UL transmissions (such as PUSCH) for one or more cells in a co-scheduled cell set. The multi-cell scheduling DCI can include a CSI request field. When a CSI report is requested through the CSI request field, the UE can send the CSI report through the PUSCH on the reference cell. For example, when X < Y, in Case 1 where the co-scheduled cell set corresponds to the cell index of assumed cell #X < the cell index of cell #Y, the UE can send the CSI report through the PUSCH on cell #1 with the smallest cell index. In Case 2, the UE can send the CSI report through the PUSCH on cell #2 with the smallest cell index. In Case x, the UE can send the CSI report through the PUSCH on cell #N with the smallest cell index.
[0308] ii. Option 2: Apply the shared single-cell method
[0309] Only when scheduling one cell (via the multi-cell DCI), can the corresponding DCI field (whose indicated CSI report is sent through the PUSCH on the corresponding cell) be configured. When scheduling multiple cells, the corresponding DCI field may not be configured and can be omitted (in this case, assuming that there is no CSI report indication for the PUSCH on the multiple cells, the PUSCH is transmitted).
[0310] iii. Option 3: Apply the omission method
[0311] The corresponding DCI field may not be configured and can be omitted in the multi-cell DCI (in this case, assuming that there is no TPC value for the PUSCH on the cells scheduled by the multi-cell DCI, the PUSCH can be transmitted).
[0312] iv. Note: When applying the option 1 (shared reference cell) method, if a specific CSI report set / status / codepoint is indicated by the CSI request field in the multi-cell DCI, the UE may operate to send a CSI report (based on reception and measurement) of the CSI-RS transmission corresponding to the corresponding CSI report set / status / codepoint configured for the specific reference cell over the PUSCH on the specific reference cell. For example, in Fig.11 if X < Y, when the co-scheduled cell set corresponds to case 1 where the cell index of the hypothesized cell #X < the cell index of the cell #Y, the UE may measure / report CSI based on the CSI-RS corresponding to the corresponding CSI report set / status / codepoint configured on the cell #1 with the smallest cell index. In case 2, the UE may measure / report CSI based on the CSI-RS corresponding to the CSI report set / status / codepoint configured on the cell #2 with the smallest cell index. In case x, the UE may measure / report CSI based on the CSI-RS corresponding to the CSI report set / status / codepoint configured on the cell #N with the smallest cell index.
[0313] v. Note A: In this case, the specific reference cell may be determined as one specific cell among the cells (within the existing single-cell (scheduling) DCI) configured with the CSI request / indicator. For example, the reference cell may be determined as the cell with the smallest index set with the CSI request / indicator within the co-scheduled cell set.
[0314] vi. Note B: In this case, for cell A (within the existing single-cell (scheduling) DCI) configured with the CSI request / indicator and cell B not configured with the FH flag / indicator, it may be configured / restricted such that only cell A or only cell B belongs to the same cell subgroup (i.e., such that cell A and cell B do not belong together), and in this state, the shared reference cell or shared cell common method may be applied separately to each cell subgroup.
[0315] vii. Note C: As another method, cell A and B may be configured to belong to the same cell subgroup, and in this state, the shared reference cell or shared cell common method may be applied separately to each cell subgroup.
[0316] 1. When applying the shared cell common method to the cell subgroup to which the above cell A and cell B belong, a) assuming the indicator field configuration is omitted and there is always no CSI report indication for the cell subgroup, a PUSCH may be sent, b) it is considered / assumed that there is no scheduling of cell B when the indicator field is configured for the cell subgroup and (at least one) bit "1" is indicated by the corresponding field, or c) assuming the indicator field is configured for the cell subgroup and there is always no CSI report indication for cell B, a PUSCH may be sent.
[0317] 2. A cell subgroup may be considered / applied as a co-scheduled cell set (all cells belonging to the corresponding set).
[0318] viii. Note D: In addition, cell X whose CSI request / indicator field is configured as a specific X-bit size (within the existing single-cell (scheduling) DCI) and cell Y whose CSI request / indicator field is configured as a Y-bit size larger than the X-bit size may be configured to belong to the same cell subgroup, and in this state, the shared reference cell or shared cell common method may be applied individually to each cell subgroup.
[0319] 1. When the shared cell common method is applied to a cell subgroup to which cell X and cell Y belong together, a) for the cell subgroup, the indicator field may be configured with a smaller size of X bits, for cell Y, which of the {2^X-1} CSI report sets / states / code points (e.g., with the lowest (or highest) index) is applied (and whether to report), and the indication of the remaining CSI report sets / states / code points (indexes) may be omitted (i.e., it is assumed that there is no indication of the remaining CSI report sets / states / code points), b) for the cell subgroup, the indicator field may be configured with a smaller size of X bits, and it is assumed that there is no CSI report indication for cell Y to perform PUSCH transmission. c) for the corresponding cell subgroup, the indicator field may be configured with a larger Y bit size, and for cell X, the CSI report set / state / code point (index) may be indicated by specific X bits in the field (e.g., with the lowest (or highest) index) (in this case, when bits other than the specific X bits are indicated as "1", it may be assumed that there is no CSI report indication for the corresponding cell X to perform PUSCH transmission, or it may be considered / assumed that there is no scheduling for the corresponding cell X), or d) for the corresponding cell subgroup, the indicator field may be configured with a larger Y bit size, and it may be assumed that there is no CSI report indication for cell X to perform PUSCH transmission.
[0320] 2. A cell subgroup may be considered / applied as a co-scheduled cell set (all cells belonging to the corresponding set).
[0321] F. Beta_offset indicator
[0322] i. Option 1: Applying the shared reference cell approach
[0323] 1. The value (β offset) indicated by the corresponding DCI field can be applied only to the PUSCH on the specific reference cell (among the cells scheduled via multi-cell DCI) for which the dynamic β offset indication is configured. For the PUSCH on the remaining cells, a specific semi-static β offset value or a specific β offset value (for example, with the lowest index) configured individually among multiple candidate β offsets (which can be dynamically indicated) can be applied.
[0324] a. The PUSCH on the reference cell may be determined as (among the cells scheduled with the same multi-cell DCI) (Alternative 1) the PUSCH on the cell with the lowest cell index, (Alternative 2) the PUSCH with the earliest transmission start symbol time (when there are multiple PUSCHs with the earliest start symbol time, the PUSCH on the cell with the lowest cell index among the multiple PUSCHs), or (Alternative 3) the PUSCH selected for multiplexing of HARQ-ACK.
[0325] ii. Option 2: Applying the shared single cell approach
[0326] 1. The corresponding DCI field may be configured (and the indicated value (β offset) may be applied to the PUSCH on the corresponding cell) only when a single cell is scheduled (via multi-cell DCI) (or only when a single cell with a dynamic β offset indication set is scheduled), and the corresponding DCI field may not be configured and may be omitted (in this case, an operation may be performed to apply a separately configured specific semi-static β offset value or a specific (e.g., lowest indexed) β offset value among multiple candidate β offsets (which may be dynamically indicated) to the PUSCH on multiple cells).
[0327] iii. Option 3: Apply the Shared State Extension Method
[0328] 1. Each of the multiple states / code points indicated by the corresponding DCI field can be configured / set to a combination of multiple β offset values of multiple PUSCHs on multiple cells (rather than the β offset value of the PUSCH on a single cell). Therefore, a specific combination of β offset values (of multiple PUSCHs on multiple cells) can be indicated by a corresponding field.
[0329] iv. Option 4: Apply a separate method
[0330] 1. A separate field may be configured for each cell scheduled by a multi-cell DCI, and the size of the corresponding separate field may vary according to the number of scheduled cells (for example, the field size may be configured to be smaller when the number of scheduled cells exceeds N, compared to when the number of scheduled cells is N (for example, N=1) or less).
[0331] A. In this case, for example, when the number of scheduled cells is N (e.g., N = 1) or less, the individual field per cell can be configured with K (e.g., K = 2) bits, and one of 2 K β-offset values (sets) can be indicated by this field. When the number of scheduled cells exceeds N, the individual field per cell can be configured with L (L < K, e.g., L = 1) bits, and one of 2 L β-offset values (sets) can be indicated by the corresponding field.
[0332] v. Option 5: Applying the omission method
[0333] 1. In multi-cell DCI, the corresponding DCI field may not be configured and can be omitted (in this case, for the PUSCH on the cell scheduled by the multi-cell DCI, a specific semi-static β-offset value configured separately or a specific (e.g., the lowest-index) β-offset value among multiple candidate β-offsets (which can be dynamically indicated) can be applied).
[0334] vi. Note 0: In this case, a specific reference cell can be determined as a specific cell among the cells configured with a β-offset indicator within the existing single-cell (scheduling) DCI, and the specific semi-static β-offset value configured separately or the specific β-offset value (e.g., with the lowest index) among multiple candidate β-offsets (which can be dynamically indicated) is conveniently referred to as the specific default β-offset value.
[0335] vii. Note 1: In this case, for cell A configured with a β-offset indicator and cell B without an FH flag / indicator within the existing single-cell (scheduling) DCI, it can be configured / constrained such that only cell A or only cell B belongs to the same cell subgroup (i.e., such that cell A and cell B do not belong together), and in this state, the shared reference cell or shared cell common method can be applied separately to each cell subgroup.
[0336] viii. Note 2: As another method, cell A and B can be configured to belong to the same cell subgroup, and in this state, the shared reference cell or shared cell common method can be applied separately to each cell subgroup.
[0337] 1. When applying the shared cell common method to the cell subgroup to which both cell A and cell B belong, a) the indicator field configuration can be omitted for the corresponding cell subgroup and a specific default β-offset value can always be applied, b) when the indicator field is configured for the corresponding cell subgroup and only the bit "0" is indicated by this field, the specific default β-offset value can be applied for cell B, and when (at least one) bit "1" is indicated, it can be considered / assumed that there is no scheduling for cell B, or c) when the indicator field is configured for the corresponding cell subgroup, the specific default β-offset value can always be applied for cell B.
[0338] 2. A cell subgroup may be considered / applied as a co-scheduled cell set (all cells belonging to the corresponding set).
[0339] G.UL-SCH indicator
[0340] i. Option 1: Applying the shared reference cell approach
[0341] 1. The value indicated by the DCI field (whether UL-SCH exists) can be applied only to the PUSCH on a specific reference cell (among the cells scheduled by multi-cell DCI), and assuming that UL-SCH transmission is indicated for the PUSCH on the remaining cells, the PUSCH can be sent.
[0342] a. The PUSCH on the reference cell may be determined as (among the cells scheduled with the same multi-cell DCI) (Alternative 1) the PUSCH on the cell with the lowest (highest) cell index or (Alternative 2) the PUSCH with the earliest (latest) transmission start symbol time (when there are multiple PUSCHs with the earliest (latest) start symbol time, the PUSCH on the cell with the lowest (highest) cell index among the multiple PUSCHs).
[0343] ii. Option 2: Applying the shared single cell approach
[0344] 1. The corresponding DCI field (the value indicated by it (whether UL-SCH exists) is applied to the PUSCH on the corresponding cell) can be configured only when one cell is scheduled (via multi-cell DCI). When multiple cells are scheduled, the corresponding DCI field may not be configured and may be omitted (in this case, it is assumed that UL-SCH transmission is indicated for PUSCH on multiple cells and PUSCH is sent).
[0345] iii. Option 3: Apply the Omission Method
[0346] 1. The corresponding DCI field may not be configured in the multi-cell DCI and may be omitted (in this case, assuming that for PUSCH on the cell scheduled by the multi-cell DCI indicates UL-SCH transmission, PUSCH may be sent).
[0347] iv. Note A: In this case, the specific reference cell may be determined as a specific cell among the cells configured with a CSI request / indicator (in the existing single-cell (scheduling) DCI). For example, the reference cell may be determined as the minimum index cell configured with a CSI request / indicator in the co-scheduled cell set.
[0348] H.ChannelAccess-CPext-CAPC(LBT)
[0349] i. Option 1: Apply the shared cell common method
[0350] 1. The values indicated by the corresponding DCI field (LBT method and related parameters) are commonly applicable to PUSCH on all cells (operating in the unlicensed band) (scheduled via multi-cell DCI).
[0351] ii. Option 2: Applying the shared reference cell method
[0352] 1. The value indicated by the corresponding DCI field (LBT method and related parameters) can be applied only to the PUSCH on a specific reference cell (among the cells scheduled via multi-cell DCI). For the PUSCH on the remaining cells, a combination of predefined / configured {LBT method (e.g., Type-1 LBT (based on random backoff)), CP extension parameters, CAPC} values can be applied to send PUSCH.
[0353] iii. Option 3: Applying the shared single cell approach
[0354] 1. The corresponding DCI field (the value indicated by it (LBT method and related parameters) is applied to the PUSCH on the corresponding cell) can be configured only when one cell is scheduled (via multi-cell DCI). When multiple cells are scheduled, the corresponding DCI field may not be configured and may be omitted (in this case, PUSCH is sent by applying a predefined / configured combination of {LBT method (e.g. (random backoff-based) Type-1 LBT), CP extension parameters, CAPC} values to the PUSCH on multiple cells).
[0355] iv. Option 4: Apply the Omission Method
[0356] 1. In multi-cell DCI, the corresponding DCI field may not be configured and may be omitted (in this case, for PUSCH on cells scheduled by multi-cell DCI, PUSCH may be sent by applying a combination of predefined / configured {LBT method (e.g., Type-1 LBT (based on random backoff)), CP extension parameters, CAPC} values).
[0357] v. Note 0: In this case, the specific reference cell may be determined as a specific cell configured with a ChannelAccess-CPext-CAPC (LBT) indicator (within the existing single-cell (scheduling) DCI), and the combination of the above-mentioned predefined / configured specific (default) {LBT method, CP extension parameter, CAPC} values may be specified as, for example, a combination of {LBT method, CP extension parameter, CAPC} configured in a ChannelAccess-CPext-CAPC with a specific (e.g., highest or lowest) index (among the ChannelAccess-CPext-CAPC (index) configured in the single-cell DCI).
[0358] vi. Note 1: In this case, the ChannelAccess-CPext-CAPC (LBT) indicator field (within the legacy single-cell (scheduling) DCI) may be configured such that cell X configured with a specific X-bit size and cell Y configured with a Y-bit size greater than X bits belong to the same cell subgroup, and in this state, the shared reference cell or shared cell common method may be applied individually to each cell subgroup.
[0359] 1. When the shared cell common method is applied to a cell subgroup to which cell X and cell Y belong together, a) for the corresponding cell subgroup, the indicator field may be configured with a smaller size of X bits, and for cell Y, which index among 2^X ChannelAccess-CPext-CAPC (index) is to be applied (e.g., with the lowest (or highest) index) may be indicated, and the indication of the remaining ChannelAccess-CPext-CAPC (index) is omitted (i.e., it is assumed that there is no indication of the remaining ChannelAccess-CPext-CAPC), b) for the cell subgroup, the indicator field may be configured with a smaller size of X bits, and for cell Y, a specific default ChannelAcc may always be applied ess-CPext-CAPC, c) for a cell subgroup, the indicator field may be configured with a larger Y bit size, and for cell X, ChannelAccess-CPext-CAPC(index) may be indicated by a specific X bit in the field (e.g., with the lowest (or highest) index) (in this case, when any bit other than the specific X bit is indicated as "1", a specific default ChannelAccess-CPext-CAPC may be applied to cell X, or it may be considered / assumed that there is no scheduling for cell X), or d) for a cell subgroup, the indicator field may be configured with a larger Y bit size, and a specific default ChannelAccess-CPext-CAPC may always be applied to cell X. For example, in Fig.12In the present invention, it is assumed that the DCI field is a ChannelAccess-CPext-CAPC field (or ChannelAccess-CPext field) and the shared cell common method is applied to the ChannelAccess-CPext-CAPC field. In the single-cell scheduling DCI of each cell, the size of the ChannelAccess-CPext-CAPC field can be independently configured. For example, it can be assumed that the ChannelAccess-CPext-CAPC field has size A in cell #1 (its active BWP), size B in cell #2 (its active BWP), size C in cell #3 (its active BWP), size D in cell #4 (its active BWP), size E in cell #5 (its active BWP), and size G in cell #N (its active BWP). Sizes A to G may be different from each other or may be the same, and may include size 0. When the union of the co-scheduled cell sets to be scheduled by the multi-cell scheduling DCI includes all cells #1 to cell #N, the size of the ChannelAccess-CPext-CAPC field in the multi-cell scheduling DCI may be Max{A, B, C, D, E, ..., G}. When the union of the co-scheduled cell sets to be scheduled by the multi-cell scheduling DCI includes only some cells among cells #1 to cell #N, the size of the ChannelAccess-CPext-CAPC field in the multi-cell scheduling DCI may be determined based on the cell with the largest ChannelAccess-CPext-CAPC field size in the union of the co-scheduled cell sets. In other words, the size of the ChannelAccess-CPext-CAPC field in the multi-cell scheduling DCI may be determined as Max{value 1, value 2, value 3, ....., value M}. For example, in the multi-cell scheduling DCI, when the size of the ChannelAccess-CPext-CAPC field is k bits and may indicate 0 to 2 k -1 state / codepoint, and when for a specific cell (its active BWP) among the co-scheduled cells, the k -m to 2 k -1 corresponding to the state / code point does not exist ChannelAccess-CPext-CAPC field configuration, the UE can apply 0 or 2 for a specific cell (its active BWP) as in method c). k -m-1 corresponding state / codepoint, or apply the default ChannelAccess-CPext-CAPC for a specific cell (its active BWP) as in method d).
[0360] 2. A cell subgroup may be considered / applied as a co-scheduled cell set (all cells belonging to the corresponding set).
[0361] I. Open-Loop Power Control (OLPC) Parameter Set Indication
[0362] i. Option 1: Applying the shared reference cell approach
[0363] 1. The value indicated by the corresponding DCI field (OLPC parameter set index) can be applied only to the PUSCH on a specific reference cell (among the cells scheduled via multi-cell DCI). For the PUSCH on the remaining cells, a predefined / configured specific OLPC parameter set (index) can be applied to send the PUSCH.
[0364] ii. Option 2: Applying the shared single cell approach
[0365] 1. The corresponding DCI field (the value indicated by it (OLPC parameter set index) is applied to the PUSCH on the corresponding cell) can be configured only when one cell is scheduled (via multi-cell DCI). When multiple cells are scheduled, the corresponding DCI field may not be configured and may be omitted (in this case, PUSCH is sent by applying a specific OLPC parameter set (index) predefined / configured to PUSCH on multiple cells).
[0366] iii. Option 3: Apply the Omission Method
[0367] 1. The corresponding DCI field may not be configured in the multi-cell DCI and may be omitted (in this case, PUSCH may be transmitted by applying a specific OLPC parameter set (index) predefined / configured for PUSCH on cells scheduled by the multi-cell DCI).
[0368] iv. Note 0: In this case, the specific reference cell may be determined as a specific cell among the cells in which the OLPC parameter set indicator is configured (within the existing single-cell (scheduling) DCI), and the specific (default) OLPC parameter set may be specified as, for example, the OLPC parameter set with the lowest index (among the set OLPC parameter sets).
[0369] v. Note 1: In this case, for cell A configured with an OLPC parameter set indicator (within the existing single-cell (scheduling) DCI) and cell B not configured with an FH flag / indicator, it can be configured / restricted so that only cell A or only cell B belongs to the same cell subgroup (i.e., so that cell A and cell B do not belong together), and in this state, the shared reference cell or shared cell common method can be applied separately to each cell subgroup.
[0370] vi. Note 2: As another method, cells A and B may be configured to belong to the same cell subgroup, and in this state, the shared reference cell or shared cell common method may be applied individually to each cell subgroup.
[0371] 1. When the shared cell common method is applied to the cell subgroup to which both cell A and cell B belong, a) the indicator field configuration may be omitted for the corresponding cell subgroup and the default OLPC parameter set may always be applied, b) when the indicator field is configured for the corresponding cell subgroup and only bit "0" is indicated by the field, a specific default OLPC parameter set may be applied for cell B, and when (at least one) bit "1" is indicated, it may be considered / assumed that there is no scheduling for cell B, or c) when the indicator field is configured for the corresponding cell subgroup, a specific default OLPC parameter set may always be applied for cell B.
[0372] 2. A cell subgroup may be considered / applied as a co-scheduled cell set (all cells belonging to the corresponding set).
[0373] vii. Note 3: (Within the existing single-cell (scheduling) DCI) the OLPC parameter set indicator field may be configured such that a cell X configured with a specific X (e.g., 1 bit) and a cell Y configured with a larger Y (e.g., 2 bits) belong to the same cell subgroup, and in this state, a shared reference cell or a shared cell common method may be applied individually to each cell subgroup.
[0374] 1. When the shared cell common method is applied to the cell subgroup to which cell X and cell Y belong together, a) for the cell subgroup, the indicator field may be configured with a smaller size X (e.g., 1 bit), and for cell Y, indicate which of two OLPC parameter sets (e.g., with the lowest index and the second lowest index) is applied, and the indication of the remaining OLPC parameter sets (indexes) is omitted (i.e., it is assumed that there is no indication of the remaining OLPC parameter sets), b) for the cell subgroup, the indicator field may be configured with a smaller size X (e.g., 1 bit), and for cell Y, a specific default OLPC parameter set is always applied, c ) For a cell subgroup, the indicator field may be configured with a larger size Y (e.g., 2 bits), and for cell X, an OLPC parameter set (index) may be indicated via a specific 1 bit (e.g., MSB or LSB) in the field (in this case, when any specific bit other than the 1 bit is indicated as "1", a specific default OLPC parameter set may be applied to the corresponding cell X, or it may be considered / assumed that there is no scheduling for the corresponding cell X), or d) For a corresponding cell subgroup, the indicator field may be configured with a larger size Y (e.g., 2 bits), and a specific default OLPC parameter set may always be applied to cell X. For example, in Fig.12In the DCI field, it is assumed that the DCI field is an OLPC parameter set indicator field for open-loop power control, and a shared cell common method is applied to the OLPC parameter set indicator field. In the single-cell scheduling DCI of each cell, the size of the OLPC parameter set indicator field can be independently configured, for example, it can be assumed that the OLPC parameter set indicator field has a size A in cell #1 (its active BWP), a size B in cell #2 (its active BWP), a size C in cell #3 (its active BWP), a size D in cell #4 (its active BWP), a size E in cell #5 (its active BWP), and a size G in cell #N (its active BWP). Sizes A to G may be different from each other or may be the same, and may include size 0. When the union of the co-scheduled cell sets to be scheduled by the multi-cell scheduling DCI includes all cells #1 to cell #N, the size of the OLPC parameter set indicator field in the multi-cell scheduling DCI may be Max{A,B,C,D,E,...,G}. When the union of the co-scheduled cell sets to be scheduled by the multi-cell scheduling DCI includes only some cells among cell #1 to cell #N, the size of the OLPC parameter set indicator field in the multi-cell scheduling DCI may be determined based on the cell with the largest OLPC parameter set indicator field size in the union of the co-scheduled cell sets. In other words, the size of the OLPC parameter set indicator field in the multi-cell scheduling DCI may be determined as Max{value 1, value 2, value 3, ..., value M}. For example, in the multi-cell scheduling DCI, when the size of the OLPC parameter set indicator field is k bits and may indicate 0 to 2 k -1 state / codepoint, and when for a specific cell (its active BWP) among the co-scheduled cells, the same as 2 k -m to 2 k -1 corresponding to the state / code point does not exist OLPC parameter set indicator field configuration, the UE can apply 0 or 2 for a specific cell (its active BWP) as in method c). k -m-1 corresponding state / codepoint, or apply the default OLPC parameter set indicator for a specific cell (its active BWP) as in method d).
[0375] 2. A cell subgroup may be considered / applied as a co-scheduled cell set (all cells belonging to the corresponding set).
[0376] J. Priority Indicator (PI)
[0377] i. Option 1: Apply the shared cell common method
[0378] 1. The value (LP or HP) indicated by the corresponding DCI field is commonly applicable to PUSCH on all cells (scheduled by multi-cell DCI), and all cells may be all cells configured with PI (among cells scheduled by multi-cell DCI).
[0379] a. When HP is indicated by a field in a multi-cell DCI, for the PUSCH on a cell that is not configured with PI (among the cells scheduled by the corresponding DCI), (Alternative Solution 1) it can be assumed that there is no PI indication (or indication LP) to send PUSCH, or (Alternative Solution 2) it can be assumed that there is no PUSCH scheduling for the corresponding cell (not configured with PI), and the PUSCH transmission on the cell can be omitted (discarded).
[0380] b. When LP is indicated by a field in a multi-cell DCI, alternative 1 operation may be applied to PUSCH on a cell (among cells scheduled by DCI) for which PI is not configured.
[0381] ii. Option 2: Applying the shared reference cell method
[0382] 1. The value (LP or HP) indicated by the DCI field may be applied only to the PUSCH on a specific reference cell configured with PI (among cells scheduled by multi-cell DCI), and alternative 1 and / or alternative 2 operations may be applied to the PUSCH on the remaining cells.
[0383] iii. Option 3: Applying the shared single cell approach
[0384] 1. The corresponding DCI field may be configured only when one cell is scheduled (via multi-cell DCI) (or only when one cell configured with a PI is scheduled) (and the value indicated thereby (LP or HP) may be applied to the PUSCH on the corresponding cell). When multiple cells are scheduled (or when multiple cells are scheduled or one cell not configured with a PI is scheduled), the corresponding DCI field may not be configured and may be omitted (in this case, alternative 1 operation is applied).
[0385] iv. Option 4: Apply the Omission Method
[0386] 1. It may not be configured in the multi-cell DCI and the corresponding DCI field may be omitted (in this case, Alternative 1 operation applies).
[0387] v. Note 0: In this case, the specific reference cell may be determined as a specific cell among cells configured with a priority indicator (in the existing single-cell (scheduling) DCI).
[0388] vi. Note 1: In this case, for (cell A configured with a priority indicator in the existing single-cell (scheduling) DCI and) cell B not configured with an FH flag / indicator, it may be configured / restricted so that only cell A or only cell B belongs to the same cell subgroup (i.e., so that cell A and cell B do not belong together), and in this state, a shared reference cell or a shared cell common method may be applied separately to each cell subgroup. For example, when all cells belonging to a co-scheduled cell set indicated by a multi-cell DCI are cell A configured with a priority indicator, the priority (e.g., HP or LP) indicated by the priority indicator field in the DCI may be equally assumed / applied to PDSCH / PUSCH on all cells belonging to the co-scheduled cell set.
[0389] vii. Note 2: As another method, cells A and B may be configured to belong to the same cell subgroup, and in this state, a method of individually sharing a reference cell or sharing a cell common may be applied to each cell subgroup.
[0390] 1. When a shared cell common method is applied to a cell subgroup to which cell A and cell B belong together, a) the indicator field configuration may be omitted for the cell subgroup and may always be regarded / assumed as indicated as LP. For example, when at least one cell among the cells belonging to the co-scheduled cell set scheduled / indicated by a multi-cell DCI is cell A configured with a priority indicator (PI) (in the case of a single-cell DCI) and at least one cell is cell B not configured with a PI (in the case of a single-cell DCI), the UE / BS may operate to assume / apply the same one priority (e.g., LP) for DL / UL signal scheduling (e.g., PDSCH / PUSCH) of all cells belonging to the co-scheduled cell set (e.g., assuming that a specific priority (e.g., LP) is indicated via the PI field in the multi-cell DCI). The PI field configuration / indication itself may be omitted in the multi-cell DCI, or the PI field may still be configured / indicated in the multi-cell DCI, but the UE / BS may ignore the PI field. Alternatively, when the shared cell common method is applied to a cell subgroup to which cell A and cell B belong together, b) an indicator field is configured for the corresponding cell subgroup and HP is indicated through the field, and the cell can operate assuming that there is no scheduling for cell B, or c) an indicator field is configured for the corresponding cell subgroup and the cell can operate assuming that LP is always indicated for cell B.
[0391] 2. A cell subgroup may be considered / applied as a co-scheduled cell set (all cells belonging to the corresponding set).
[0392] K. Invalid symbol pattern indicator
[0393] i. Option 1: Applying the shared reference cell approach
[0394] 1. The value indicated by the DCI field (invalid symbol pattern) can be applied only to the PUSCH on a specific reference cell configured with an invalid symbol pattern among the cells scheduled by multi-cell DCI. Assuming that there is no indication of an invalid symbol pattern for the PUSCH on the remaining cells, the PUSCH can be transmitted.
[0395] ii. Option 2: Apply the shared single-cell method
[0396] 1. The corresponding DCI field can be configured only when scheduling one cell (via multi-cell DCI) (or only when scheduling one cell configured with an invalid symbol pattern). And thus the indicated value (whether to apply the invalid symbol pattern) can be applied to the PUSCH on the corresponding cell. When scheduling multiple cells (or when scheduling multiple cells or one cell not configured with an invalid symbol pattern), the corresponding DCI field may not be configured and can be omitted. In this case, assuming that there is no indication of an invalid symbol pattern for the PUSCH on multiple cells, the PUSCH can be transmitted.
[0397] iii. Option 3: Apply the omission method
[0398] 1. The corresponding DCI field may not be configured and can be omitted in multi-cell DCI. In this case, assuming that there is no indication of an invalid symbol pattern for the PUSCH on the cells scheduled by multi-cell DCI, the PUSCH can be transmitted.
[0399] iv. Option 4: Apply the separate method
[0400] 1. Separate fields can be configured for each cell scheduled by multi-cell DCI, and the size of the separate fields can vary according to the number of scheduled cells. For example, when the number of scheduled cells exceeds N, the field size can be configured to be less than when the number of scheduled cells is N (e.g., N = 1) or fewer.
[0401] a. In this case, for example, when the number of scheduled cells is N (e.g., N = 1) or fewer, the separate field for each cell can be configured with K bits, and one of 2 K invalid symbol patterns can be indicated by this field. While when the number of scheduled cells exceeds N, the separate field for each cell can be configured with L (L < K) bits, and one of 2 L invalid symbol patterns can be indicated by this field.
[0402] v. Option 5: Apply the shared state extension method
[0403] 1. Each of the multiple states / code points indicated by the corresponding DCI field can be configured / set to a combination of multiple invalid symbol patterns of multiple PUSCHs on multiple cells (rather than an invalid symbol pattern of PUSCH on a single cell). Therefore, a specific combination of invalid symbol patterns (of multiple PUSCHs on multiple cells) can be indicated by a corresponding field.
[0404] vi. Note 0: In this case, the specific reference cell may be determined as a specific cell among cells configured with an invalid symbol pattern indicator (in the existing single-cell (scheduling) DCI).
[0405] vii. Note 1: In this case, for cell A configured with an invalid symbol pattern indicator (within the existing single-cell (scheduling) DCI) and cell B not configured with an FH flag / indicator, it can be configured / restricted so that only cell A or only cell B belongs to the same cell subgroup (i.e., so that cell A and cell B do not belong together), and in this state, the shared reference cell or shared cell common method can be applied separately to each cell subgroup.
[0406] viii. Note 2: As another method, cells A and B may be configured to belong to the same cell subgroup, and in this state, the shared reference cell or shared cell common method may be applied individually to each cell subgroup.
[0407] 1. When the shared cell common method is applied to the cell subgroup to which the above-mentioned cell A and cell B belong, a) assuming that the indicator field configuration is omitted and there is no invalid symbol pattern indication for the cell subgroup, PUSCH can be sent, b) it is considered / assumed that there is no scheduling for cell B when the indicator field is configured for the cell subgroup and the corresponding field indicates bit "1", or c) assuming that the indicator field is configured for the cell subgroup and there is no invalid symbol pattern indication for cell B, PUSCH can be sent.
[0408] 2. A cell subgroup may be considered / applied as a co-scheduled cell set (all cells belonging to the corresponding set).
[0409] Fig.13 An example implementation of signal reception of a UE based on at least some of the above embodiments is shown. Even if not separately described, reference may be made to the previously described contents to help understand Fig.13 .
[0410] The UE monitors Physical Downlink Control Channel (PDCCH) candidates (1305).
[0411] The UE may detect a downlink control channel (DCI) by monitoring PDCCH candidates (1310).
[0412] The DCI may support multi-cell scheduling based on multiple cells configured in the UE. The DCI may include a first DCI field commonly configured for co-scheduled cells. Based on the multiple serving cells including a first cell and a second cell and the size-related configuration of the first DCI field being M bits for scheduling the first cell and N bits for scheduling the second cell: the size of the first DCI field commonly configured for the co-scheduled cells may be determined as the larger of M bits and N bits.
[0413] The first DCI field may include at least one of a field about antenna port information, a field about sounding reference signal (SRS) resource information, a field about precoding and layer number related information, a field about β offset information, an open-loop power control parameter set indication (OLPC) field, and a field about channel access and cyclic prefix (CP) information.
[0414] The first DCI field may indicate a common code point for the co-scheduled cells. Parameters mapped to the indicated code point may be configured separately for each co-scheduled cell. A table may be configured in the UE to provide parameters mapped to the corresponding scheduled cells for each code point of the first DCI field.
[0415] The size of the first DCI field may be determined based on a cell having a maximum size-related configuration of the first DCI field among a plurality of cells.
[0416] The DCI may include a second DCI field applied to a reference cell among the co-scheduled cells.
[0417] The reference cell may be a cell having a smallest serving cell index among the co-scheduled cells.
[0418] The second DCI field may include a channel state information (CSI) request field.
[0419] The UE may obtain CSI related to the CSI request field based on channel state information-reference signal (CSI-RS) information of a reference cell having a minimum serving cell index among co-scheduled cells.
[0420] The UE may send a CSI report related to the CSI request field on a reference cell having a smallest serving cell index among the co-scheduled cells through a physical uplink shared channel (PUSCH).
[0421] Fig.14 An example implementation of signal transmission of a BS based on at least some of the above embodiments is shown. Even if not separately described, reference can be made to the contents of the previous description to help understand Fig.14 .
[0422] The BS generates downlink control information (DCI) (1405). The DCI may support multi-cell scheduling based on multiple cells configured in the UE. The DCI may include a first DCI field configured for co-scheduled cells. Based on the multiple cells including a first cell and a second cell and the size-related configuration of the first DCI field is M bits for scheduling the first cell and N bits for scheduling the second cell, the size of the first DCI field configured for the co-scheduled cells may be determined by the larger of the M bits and the N bits.
[0423] The BS may send DCI to the UE based on at least one physical downlink control channel (PDCCH) candidate of the UE (1410).
[0424] The first DCI field may include at least one of a field about antenna port information, a field about sounding reference signal (SRS) resource information, a field about precoding and layer number related information, a field about β offset information, an open-loop power control parameter set indication (OLPC) field, and a field about channel access and cyclic prefix (CP) information.
[0425] The first DCI field may indicate a common code point for the co-scheduled cells. Parameters mapped to the indicated code point may be configured separately for each co-scheduled cell. The BS may configure in the UE a table that provides parameters mapped to the corresponding scheduled cells for each code point of the first DCI field.
[0426] The size of the first DCI field may be determined based on a cell having a maximum size-related configuration of the first DCI field among a plurality of cells.
[0427] The DCI may include a second DCI field applied to a reference cell among the co-scheduled cells.
[0428] The reference cell may be a cell having a smallest serving cell index among the co-scheduled cells.
[0429] The second DCI field may include a channel state information (CSI) request field.
[0430] The CSI related to the CSI request field may be determined based on channel state information-reference signal (CSI-RS) information of a reference cell having a minimum serving cell index among the co-scheduled cells.
[0431] The BS may receive a CSI report related to a CSI request field on a reference cell having a smallest serving cell index among co-scheduled cells through a Physical Uplink Shared Channel (PUSCH).
[0432] Fig.15 A communication system 1 applied to the present disclosure is shown.
[0433] Reference Fig.15 , the communication system 1 applied to the present disclosure includes a wireless device, a base station (BS), and a network. Herein, a wireless device refers to a device that performs communication using a radio access technology (RAT) (e.g., 5G new RAT (NR) or long term evolution (LTE)), and may be referred to as a communication / radio / 5G device. The wireless device may include, but is not limited to, a robot 100a, vehicles 100b-1 and 100b-2, an extended reality (XR) device 100c, a handheld device 100d, a home appliance 100e, an Internet of Things (IoT) device 100f, and an artificial intelligence (AI) device / server 400. For example, a vehicle may include a vehicle with a wireless communication function, an autonomous driving vehicle, and a vehicle capable of performing communication between vehicles. Herein, a vehicle may include an unmanned aerial vehicle (UAV) (e.g., a drone). XR devices may include augmented reality (AR) / virtual reality (VR) / mixed reality (MR) devices, and may be implemented in the form of a head mounted device (HMD), a head up display (HUD) installed in a vehicle, a television, a smart phone, a computer, a wearable device, a home appliance device, a digital sign, a vehicle, a robot, etc. Handheld devices may include smart phones, smart boards, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., notebooks). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters. For example, a BS and a network may be implemented as wireless devices, and a specific wireless device 200a may operate as a BS / network node relative to other wireless devices.
[0434] The wireless devices 100a to 100f may be connected to the network 300 via the BS 200. The 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 via the BS 200 / network 300, the wireless devices 100a to 100f may perform direct communication (e.g., side link communication) with each other without passing through the BS / network. For example, vehicles 100b-1 and 100b-2 may perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). An IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., a sensor) or other wireless devices 100a to 100f.
[0435] Wireless communication / connection 150a, 150b or 150c may be established between wireless devices 100a to 100f / BS200 or BS200 / BS200. Herein, wireless communication / connection 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 device and the BS / wireless device may send / receive radio signals to / from each other through wireless communication / connection 150a and 150b. For example, wireless communication / connection 150a and 150b may send / receive signals through various physical channels. To this end, at least a portion of various configuration information for configuring processes for sending / receiving radio signals, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, and resource mapping / demapping), and resource allocation processes may be performed based on various proposals of the present disclosure.
[0436] Fig.16 A wireless device suitable for use with the present disclosure is shown.
[0437] Reference Fig.16 , the first wireless device 100 and the second wireless device 200 may transmit radio signals via various RATs (e.g., LTE and NR). Herein, {the first wireless device 100 and the second wireless device 200} may correspond to Fig.15 {wireless device 100x and BS 200} and / or {wireless device 100x and wireless device 100x}.
[0438] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and further include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may control the memory 104 and / or the transceiver 106, and may be configured to implement the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. For example, the processor 102 may process the information in the memory 104 to generate first information / signals, and then transmit a radio signal including the first information / signals through the transceiver 106. The processor 102 may receive a radio signal including second information / signals through the transceiver 106, and then store information obtained by processing the second information / signals in the memory 104. The memory 104 may be connected to the processor 102, and may store various information related to the operation of the processor 102. For example, the memory 104 may store software codes including commands for executing part or all of the processes controlled by the processor 102 or for executing the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. Herein, the processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver 106 may be connected to the processor 102 and transmit and / or receive radio signals through one or more antennas 108. Each transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be used interchangeably with a radio frequency (RF) unit. In the present disclosure, a wireless device may represent a communication modem / circuit / chip.
[0439] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and further include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may control the memory 204 and / or the transceiver 206, and may be configured to implement the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. For example, the processor 202 may process the information in the memory 204 to generate third information / signals, and then transmit a radio signal including the third information / signals through the transceiver 206. The processor 202 may receive a radio signal including fourth information / signals through the transceiver 206, and then store information obtained by processing the fourth information / signals in the memory 204. The memory 204 may be connected to the processor 202, and may store various information related to the operation of the processor 202. For example, the memory 204 may store software codes including commands for executing part or all of the processes controlled by the processor 202 or for executing the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. Herein, the processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver 206 may be connected to the processor 202 and transmit and / or receive radio signals through one or more antennas 208. Each transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be used interchangeably with an RF unit. In the present disclosure, a wireless device may represent a communication modem / circuit / chip.
[0440] In the following, the hardware elements of the wireless devices 100 and 200 will be described in more detail. One or more protocol layers may be implemented by (but not limited to) one or more processors 102 and 202. For example, 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). One or more processors 102 and 202 may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs) according to the descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document. One or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document. One or more processors 102 and 202 may generate a signal (e.g., a baseband signal) including a PDU, SDU, message, control information, data, or information according to the description, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document, and provide the generated signal to one or more transceivers 106 and 206. One or more processors 102 and 202 may receive a signal (e.g., a baseband signal) from one or more transceivers 106 and 206 and obtain the PDU, SDU, message, control information, data, or information according to the description, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document.
[0441] One or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. 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 one or more processors 102 and 202. The descriptions, functions, processes, proposals, methods, and / or operational flow charts disclosed in this document may be implemented using firmware or software, and the firmware or software may be configured to include modules, processes, or functions. Firmware or software configured to execute the descriptions, functions, processes, proposals, methods, and / or operational flow charts disclosed in this document may be included in one or more processors 102 and 202 or stored in one or more memories 104 and 204 to be driven by one or more processors 102 and 202. The descriptions, functions, processes, proposals, methods and / or operational flow charts disclosed in this document may be implemented in the form of codes, commands and / or command sets using firmware or software.
[0442] One or more memories 104 and 204 may be connected to one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, codes, instructions and / or commands. One or more memories 104 and 204 may be configured by read-only memory (ROM), random access memory (RAM), electrically erasable programmable read-only memory (EPROM), flash memory, hard disk drive, register, cache memory, computer-readable storage medium and / or a combination thereof. One or more memories 104 and 204 may be located inside and / or outside of one or more processors 102 and 202. One or more memories 104 and 204 may be connected to one or more processors 102 and 202 by various technologies such as wired or wireless connections.
[0443] One or more transceivers 106 and 206 may send user data, control information and / or radio signals / channels mentioned in the method and / or operation flow chart of this document to one or more other devices. One or more transceivers 106 and 206 may receive user data, control information and / or radio signals / channels mentioned in the description, function, process, proposal, method and / or operation flow chart disclosed in this document from one or more other devices. For example, one or more transceivers 106 and 206 may be connected to one or more processors 102 and 202 and send and receive radio signals. For example, one or more processors 102 and 202 may perform control so that one or more transceivers 106 and 206 may send user data, control information or radio signals to one or more other devices. One or more processors 102 and 202 may perform control so that one or more transceivers 106 and 206 may receive user data, control information or radio signals from one or more other devices. One or more transceivers 106 and 206 may be connected to one or more antennas 108 and 208, and one or more transceivers 106 and 206 may be configured to send and receive user data, control information and / or radio signals / channels mentioned in the description, functions, processes, proposals, methods and / or operation flow charts disclosed in this document through one or more antennas 108 and 208. In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106 and 206 may convert received radio signals / channels, etc. from RF band signals to baseband signals so as to process received user data, control information, radio signals / channels, etc. using one or more processors 102 and 202. One or more transceivers 106 and 206 may convert user data, control information, radio signals / channels, etc. processed using one or more processors 102 and 202 from baseband signals to RF band signals. To this end, one or more of the transceivers 106 and 206 may include (analog) oscillators and / or filters.
[0444] Fig.17 Another example of a wireless device applicable to the present disclosure is shown. The wireless device can be used according to the usage / service (refer to Fig.15 ) are implemented in various forms.
[0445] Reference Fig.17 , the wireless devices 100 and 200 may correspond to Fig.16The wireless devices 100 and 200 of the present invention may be configured by various elements, components, units / parts and / or modules. For example, each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130 and an additional component 140. The communication unit may include a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 may include Fig.16 One or more processors 102 and 202 and / or one or more memories 104 and 204. For example, the transceiver 114 may include Fig.16 The control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional components 140, and controls the overall operation of the wireless device. For example, the control unit 120 may control the electrical / mechanical operation of the wireless device based on the program / code / command / information stored in the memory unit 130. The control unit 120 may transmit information stored in the memory unit 130 to the outside (e.g., other communication devices) via the communication unit 110 through a wireless / wired interface, or store information received from the outside (e.g., other communication devices) via the communication unit 110 in the memory unit 130 through a wireless / wired interface.
[0446] The additional components 140 may be configured differently depending on the type of wireless device. For example, the additional components 140 may include at least one of a power supply unit / battery, an input / output (I / O) unit, a drive unit, and a computing unit. The wireless device may be configured in the form of, but not limited to, a robot ( Fig.15 100a), vehicles ( Fig.15 100b-1 and 100b-2), XR devices ( Fig.15 100c), handheld device ( Fig.15 100d), household appliances ( Fig.15 100e), IoT devices ( Fig.15 100f), digital broadcasting terminal, holographic device, public safety device, MTC device, medical device, fintech device (or financial device), security device, climate / environmental device, AI server / device ( Fig.15 400), BS( Fig.15 200), network nodes, etc. The wireless device can be used in a mobile or fixed location according to the usage example / service.
[0447] exist Fig.17In the wireless devices 100 and 200, various elements, components, units / parts and / or modules in the wireless devices 100 and 200 may all be connected to each other through a wired interface, or at least a part thereof may be wirelessly connected through the communication unit 110. For example, in each of the wireless devices 100 and 200, the control unit 120 and the communication unit 110 may be wired, and the control unit 120 and the first cell (e.g., 130 and 140) may be wirelessly connected through the communication unit 110. The various elements, components, units / parts and / or modules within the wireless devices 100 and 200 may also include one or more elements. For example, the control unit 120 may be configured by a collection of one or more processors. As an example, the control unit 120 may be configured by a collection of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing unit and a memory control processor. As another example, the memory unit 130 may be configured by a random access memory (RAM), a dynamic RAM (DRAM), a read-only memory (ROM)), a flash memory, a volatile memory, a non-volatile memory and / or a combination thereof.
[0448] Fig.18 A vehicle or an autonomous vehicle applied to the present disclosure is shown. The vehicle or the autonomous vehicle can be implemented by a mobile robot, a car, a train, a manned / unmanned aerial vehicle (AV), a ship, etc.
[0449] Reference Fig.18 , the vehicle or autonomous driving vehicle 100 may include an antenna unit 108, a communication unit 110, a control unit 120, a drive unit 140a, a power supply unit 140b, a sensor unit 140c, and an autonomous driving unit 140d. The antenna unit 108 may be configured as a part of the communication unit 110. Blocks 110 / 130 / 140a to 140d correspond to Fig.17 Block 110 / 130 / 140.
[0450] The communication unit 110 may send and receive signals (e.g., data and control signals) to and from external devices such as other vehicles, BSs (e.g., gNBs and roadside units), and servers. The control unit 120 may perform various operations by controlling elements of the vehicle or autonomous vehicle 100. The control unit 120 may include an electronic control unit (ECU). The drive unit 140a may enable the vehicle or autonomous vehicle 100 to travel on a road. The drive unit 140a may include an engine, a motor, a power system, wheels, brakes, a steering device, etc. The power supply unit 140b may supply power to the vehicle or autonomous vehicle 100, and include a wired / wireless charging circuit, a battery, etc. The sensor unit 140c may obtain vehicle status, surrounding 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 depth sensor, an ultrasonic sensor, a lighting sensor, a pedal position sensor, etc. The autonomous driving unit 140d may implement a technology for maintaining a lane in which the vehicle is traveling, a technology for automatically adjusting a speed (e.g., adaptive cruise control), a technology for autonomously traveling along a determined path, a technology for traveling by automatically setting a path if a destination is set, and the like.
[0451] 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 drive unit 140a so 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 obtain the latest traffic information data from the external server and obtain surrounding traffic information data from neighboring vehicles. In the middle of autonomous driving, the sensor unit 140c may obtain vehicle status and / or surrounding environment information. The autonomous driving unit 140d may update the autonomous driving path and driving plan based on the newly obtained data / information. The communication unit 110 may transmit information about the vehicle position, autonomous driving path, and / or driving plan to an external server. The external server may predict traffic information data based on information collected from the vehicle or autonomous driving vehicle using AI technology, etc., and provide the predicted traffic information data to the vehicle or autonomous driving vehicle.
[0452] Fig.19 is a diagram illustrating a DRX operation of a UE according to an embodiment of the present disclosure.
[0453] The UE may perform DRX operation in the process and / or method described / proposed above. A UE configured with DRX may reduce power consumption by discontinuously receiving DL signals. DRX may be performed in the RRC_IDLE state, the RRC_INACTIVE state, and the RRC_CONNECTED state. The UE performs DRX in the RRC_IDLE state and the RRC_INACTIVE state to discontinuously receive paging signals. DRX in the RRC_CONNECTED state (RRC_CONNECTED DRX) will be described below.
[0454] Reference Fig.19 , the DRX cycle includes an on-duration and a DRX opportunity. The DRX cycle defines the time interval between periodic repetitions of the on-duration. The on-duration is the time period during which the UE monitors the PDCCH. When the UE is configured with DRX, the UE performs PDCCH monitoring during the on-duration. When the UE successfully detects the PDCCH during the PDCCH monitoring, the UE starts the inactivity timer and remains awake. On the contrary, when the UE fails to detect any PDCCH during the PDCCH monitoring, the UE transitions to a sleep state after the on-duration. Therefore, when DRX is configured, PDCCH monitoring / reception may be performed discontinuously in the time domain in the process and / or method described / proposed above. For example, when DRX is configured, the PDCCH reception timing (e.g., a time slot with a PDCCHSS) may be configured discontinuously according to the DRX configuration in the present disclosure. On the contrary, when DRX is not configured, PDCCH monitoring / reception may be performed continuously in the time domain. For example, when DRX is not configured, the PDCCH reception timing (e.g., a time slot with a PDCCHSS) may be configured continuously in the present disclosure. Regardless of whether DRX is configured, PDCCH monitoring may be restricted during time periods configured as measurement gaps.
[0455] Table 9 describes the DRX operation of the UE (in the RRC_CONNECTED state). Referring to Table 9, DRX configuration information is received through high-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 while executing the above-described / proposed procedures and / or methods.
[0456] [Table 9]
[0457]
[0458] MAC-CellGroupConfig includes configuration information required to configure MAC parameters for a cell group. MAC-CellGroupConfig may also include DRX configuration information. For example, when defining DRX, MAC-CellGroupConfig may include the following information.
[0459] -drx-OnDurationTimer value: defines the duration of the start period of the DRX cycle
[0460] -drx-InactivityTimer value: defines the duration of the time period during which the UE wakes up after detecting a PDCCH opportunity indicating a PDCCH for initial UL or DL data
[0461] -drx-HARQ-RTT-TimerDL value: defines the duration of the maximum time period after receiving a DL initial transmission until a DL retransmission is received
[0462] -drx-HARQ-RTT-TimerDL value: defines the duration of the maximum time period after receiving the UL initial transmission grant until receiving the UL retransmission grant
[0463] -drx-LongCycleStartOffset: defines the duration and start time of the DRX cycle
[0464] -drx-ShortCycle (optional): defines the duration of the short DRX cycle
[0465] When any one of drx-OnDurationTimer, drx-InactivityTimer, drx-HARQ-RTT-TimerDL and drx-HARQ-RTT-TimerDL is running, the UE performs PDCCH monitoring at each PDCCH opportunity and remains in the awake state.
[0466] The above-mentioned embodiments correspond to the combination of elements and features of the present disclosure in a prescribed form. And, unless explicitly mentioned, each element or feature may be regarded as selective. Each element or feature may be implemented in a form that is not combined with other elements or features. In addition, it is possible to implement the embodiments of the present disclosure by partially combining elements and / or features together. The order of operations described for each embodiment of the present disclosure may be modified. Some configurations or features of an embodiment may be included in another embodiment, or may replace the corresponding configuration or features of another embodiment. And, it is obvious to understand that the embodiment is configured by combining claims that do not have a clear reference relationship in the attached claims, or may be included as a new claim by modification after submitting the application.
[0467] Those skilled in the art will appreciate that the present disclosure may be implemented in other specific forms other than those described herein without departing from the spirit and essential characteristics of the present disclosure. Therefore, the above-described embodiments should be interpreted as being illustrative in all respects, rather than restrictive. The scope of the present disclosure should be determined by the appended claims and their legal equivalents, rather than by the above description, and all changes falling within the meaning and equivalent scope of the appended claims are intended to be covered therein.
[0468] Industrial Applicability
[0469] The present disclosure is applicable to UE, BS or other devices in a wireless mobile communication system.
Claims
1. A method for receiving a signal in a user equipment UE in a wireless communication system, the method comprising the following steps: Monitoring physical downlink control channel PDCCH candidates; as well as Detecting downlink control information DCI by monitoring the PDCCH candidates, The DCI supports multi-cell scheduling based on multiple cells configured in the UE, The DCI includes a first DCI field commonly configured for co-scheduled cells, and Wherein, based on the fact that the multiple cells include a first cell and a second cell and the size-related configurations of the first DCI field are respectively M bits for scheduling the first cell and N bits for scheduling the second cell: The size of the first DCI field commonly configured for the co-scheduled cells is determined based on a larger one of the M bits and the N bits.
2. The method according to claim 1, wherein: The first DCI field includes at least one of a field about antenna port information, a field about sounding reference signal SRS resource information, a field about precoding and layer number related information, a field about β offset information, an open-loop power control parameter set indication OLPC field, and a field about channel access and cyclic prefix CP information.
3. The method according to claim 1, wherein: The first DCI field indicates a common code point of the co-scheduled cells, and Parameters mapped to an indicated code point are individually configured for each of the co-scheduled cells.
4. The method according to claim 3, wherein: A table is configured in the UE to provide mappings of parameters of corresponding scheduled cells to each code point of the first DCI field.
5. The method according to claim 1, wherein: The size of the first DCI field is determined based on a cell having a maximum size-related configuration of the first DCI field among the plurality of cells.
6. The method according to claim 1, wherein: The DCI includes a second DCI field applied to a reference cell among the co-scheduled cells, and The reference cell is a cell with a minimum serving cell index among the co-scheduled cells.
7. The method according to claim 6, wherein: The second DCI field includes a channel state information (CSI) request field.
8. The method according to claim 7, wherein: The UE obtains CSI related to the CSI request field based on channel state information-reference signal CSI-RS information of the reference cell having the minimum serving cell index among the co-scheduled cells.
9. The method according to claim 7, wherein: The UE sends a CSI report related to the CSI request field on the reference cell having the smallest serving cell index among the co-scheduled cells through a physical uplink shared channel PUSCH. 10 . A computer-readable recording medium having recorded thereon a program for executing the method according to claim 1 .
11. An apparatus for wireless communication, the apparatus comprising: a memory configured to store instructions; as well as a processor configured to perform operations by executing the instructions, The operation of the processor includes monitoring a physical downlink control channel PDCCH candidate and detecting downlink control information DCI by monitoring the PDCCH candidate. wherein the DCI supports multi-cell scheduling based on multiple cells configured in the device, The DCI includes a first DCI field commonly configured for co-scheduled cells, and Wherein, based on the fact that the multiple cells include a first cell and a second cell and the size-related configurations of the first DCI field are respectively M bits for scheduling the first cell and N bits for scheduling the second cell: The size of the first DCI field commonly configured for the co-scheduled cells is determined based on a larger one of the M bits and the N bits.
12. The device according to claim 11, further comprising: a transceiver configured to send or receive wireless signals under the control of the processor, The device includes a user equipment UE in a wireless communication system.
13. The device according to claim 11, wherein: The device includes an application specific integrated circuit ASIC or a digital signal processing device for controlling the UE.
14. A method for sending a signal by a base station BS in a wireless communication system, the method comprising the following steps: Generate downlink control information DCI; as well as sending the DCI to a user equipment UE based on at least one physical downlink control channel (PDCCH) candidate of the UE, The DCI supports multi-cell scheduling based on multiple cells configured in the UE, The DCI includes a first DCI field commonly configured for co-scheduled cells, and Wherein, based on the fact that the multiple cells include a first cell and a second cell and the size-related configurations of the first DCI field are respectively M bits for scheduling the first cell and N bits for scheduling the second cell: The size of the first DCI field commonly configured for the co-scheduled cells is determined based on a larger one of the M bits and the N bits.
15. A base station BS for sending signals in a wireless communication system, the BS comprising: Transceiver; as well as a processor configured to generate downlink control information DCI and send the DCI to a user equipment UE based on at least one physical downlink control channel PDCCH candidate of the UE through the transceiver, The DCI includes a first DCI field commonly configured for co-scheduled cells, and Wherein, based on the fact that the multiple cells include a first cell and a second cell and the size-related configurations of the first DCI field are respectively M bits for scheduling the first cell and N bits for scheduling the second cell: The size of the first DCI field commonly configured for the co-scheduled cells is determined based on a larger one of the M bits and the N bits.
