UE features for multi-cell multi-pdsch / pusch scheduling

Abstract

An apparatus configured to generate, for transmission to a network, user equipment (UE) capability information associated with a single-Downlink Control Information (single-DCI) multi-cell Multi-Physical Downlink Shared Channel (multi-PDSCH) scheduling capability, process, based on signaling from a scheduling cell of the network, a DCI Format 1_3 comprising scheduling information for a set of cells, wherein each of the set of cells are scheduled with one or more PDSCHs and process, based on signaling from the network, the one or more PDSCHs received from each of the set of cells.

Description

Attorney Docket No . 30164 / 104102Ref . No . P71621WO1UE Features for Multi-Cell Multi-PDSCH / PUSCH Scheduling Inventors : Ankit Bhamri, Haitong Sun, Rolando E Bettancourt Ortega, Wanshi Chen and Wei ZengPriority / Incorporation By Reference

[0001] This application claim priority to U. S . Provisional Application Serial No . 63 / 777, 242 filed on March 25, 2025, and entitled "UE Features for Multi-Cell Multi-PDSCH / PUSCH Scheduling, " the entirety of which is incorporated herein by reference .Background

[0002] In 3GPP networks starting with Release 18, a user equipment (UE) was allowed to be scheduled by a single Downlink Control Information (DCI ) for multiple cells / carriers . However, this single-DCI multi-cell scheduling included certain restrictions such as the fact that the multiple carriers had to be the same type (e . g. , Time Division Duplexing (TDD) or Frequency Divisional Duplexing (FDD) ) , the subcarrier spacing (SCS) of each carrier had to be the same, etc. These restrictions may result in less flexibility in scheduling for the network.Summary

[0003] Some example embodiments are related to an apparatus having memory coupled to processing circuitry, the processing circuitry configured to generate, for transmission to a network, user equipment (UE) capability information associated with a single-Downlink Control Information (single-DCI ) multi-cell Multi-Physical Downlink Shared Channel (multi-PDSCH) scheduling capability, process, based on signaling from a scheduling cellAttorney Docket No . 30164 / 104102Ref . No . P71621WO1of the network, a DCI Format 1 3 comprising scheduling information for a set of cells, wherein each of the set of cells are scheduled with one or more PDSCHs and process, based on signaling from the network, the one or more PDSCHs received from each of the set of cells .

[0004] Other example embodiments are related to an apparatus having memory coupled to processing circuitry, the processing circuitry configured to generate, for transmission to a network, user equipment (UE) capability information associated with a single-Downlink Control Information (single-DCI ) multi-cell Multi-Physical Uplink Shared Channel (multi-PUSCH) scheduling capability, process, based on signaling from a scheduling cell of the network, a DCI Format 0 3 comprising scheduling information for a set of cells, wherein each of the set of cells are scheduled with one or more PUSCHs and generate, for transmission to the network, the one or more PUSCHs scheduled for each of the set of cells .Brief Description of the Drawings

[0005] Fig. 1 shows an example network arrangement according to various example embodiments .

[0006] Fig. 2 shows an example user equipment (UE) according to various example embodiments .

[0007] Fig. 3 shows an example base station according to various example embodiments .

[0008] Fig. 4 shows an example method for a UE to report a capability related to single-DCI multi-cell multi-PDSCHAttorney Docket No . 30164 / 104102Ref . No . P71621WO1scheduling to a network according to various example embodiments .

[0009] Fig . 5 shows an example method for a UE to report a capability related to single-DCI multi-cell multi-PUSCH scheduling to a network according to various example embodiments .Detailed Description

[0010] The example embodiments may be further understood with reference to the following description and the related appended drawings , wherein like elements are provided with the same reference numerals . The example embodiments relate to single-DCI , multi-cell, multi-PDSCH / PUSCH scheduling for a UE .Specifically, the example embodiments relate to UE capability reporting associated with single-DCI , multi-cell , multi-PDSCH / PUSCH scheduling .

[0011] The example embodiments are described with regard to a UE . However, reference to a UE is merely provided for illustrative purposes . The example embodiments may be utilized with any electronic component that may establish a connection to an accessory device and is configured with the hardware, software, and / or firmware to exchange information and data with accessory devices . Therefore, the UE as described herein is used to represent any electronic component .

[0012] The example embodiments are also described with reference to a 5G New Radio (NR) network . However, the example embodiments may also be implemented in other types of networks , including but not limited to LTE networks , future evolutions ofAttorney Docket No . 30164 / 104102Ref . No . P71621WO1the cel lular protocol ( e . g . , 5G-advanced networks , 6G networks , 7G networks , etc . ) , or any other type of network .

[0013] The example embodiments relate to s ingle-DCI , multicel l , multi-PDSCH / PUSCH schedul ing for a UE . The single-DCI may be a DCI Format 1_3 for PDSCH schedul ing and DCI Format 0_3 for PUSCH schedul ing . A UE that supports thi s type o f capabi l ity may have various capabi l ities related to single-DCI , multi-cel l , multi-PDSCH / PUSCH schedul ing . These UE capabi l ities may af fect the DCI and or the scheduling information provided by the network . The example embodiments provide UE reporting capabi l ities for s ingle-DCI , multi-cell , multi-PDSCH / PUSCH schedul ing so that the network may determine how the s ingle-DCI , multi-cel l , multi-PDSCH / PUSCH schedul ing i s s ignaled to the UE and the conf iguration o f the s ingle-DCI , multi-cell , multi-PDSCH / PUSCH schedul ing . Each o f these example embodiments will be described in greater detai l below .

[0014] Fig . 1 shows an example network arrangement 100 according to various example embodiments . The example network arrangement 100 includes a UE 110 . The UE 110 may be any type o f electronic component that i s conf igured to communicate via a network, e . g . , mobi le phones , tablet computers , des ktop computers , smartphones , embedded devices , wearables , Internet o f Things ( loT ) devices , etc . An actual network arrangement may include any number o f UEs being used by any number o f users .Thus , the example o f one UE 110 is merely provided for i l lustrative purposes .

[0015] The UE 110 may be configured to communicate with one or more networks . In the example o f the network arrangement 100 ,Attorney Docket No . 30164 / 104102Ref . No . P71621WO1the network with which the UE 110 may wireles s ly communicate i s a 5G NR radio acces s network ( RAN) 120 . The UE 110 may al so communicate with other types o f networks ( e . g . , 5G cloud RAN, a next generation RAN (NG-RAN) , a legacy cel lular network, etc . ) and the UE 110 may also communicate with networks over a wired connection . With regard to the example embodiments , the UE 110 may establi sh a connection with the 5G NR RAN 120 . There fore , the UE 110 may have a 5G NR chipset to communicate with the NR RAN 120 .

[0016] The 5G NR RAN 120 may be portions o f a cel lular network that may be deployed by a network carrier ( e . g . , Veri zon, AT &T , T-Mobile , etc . ) . The RAN 120 may include cel ls or base stations that are configured to send and receive traf f ic from UEs that are eguipped with the appropriate cel lular chip set . In thi s example , the 5G NR RAN 120 includes the gNB 120A and the gNB 120B . However , re ference to a gNB i s merely provided for i l lustrative purposes , any appropriate base station or cel l may be deployed ( e . g . , Node Bs , eNodeBs , HeNBs , eNBs , gNBs , gNodeBs , macrocel l s , microcel l s , smal l cel ls , femtocel ls , etc . ) .

[0017] Any association procedure may be performed for the UE 110 to connect to the 5G NR RAN 120 . For example , as discus sed above , the 5G NR RAN 120 may be as sociated with a particular network carrier where the UE 110 and / or the user thereof has a contract and credential information ( e . g . , stored on a S IM card) . Upon detecting the presence o f the 5G NR RAN 120 , the UE 110 may transmit the corresponding credential information to as sociate with the 5G NR RAN 120 . More speci f ically, the UE 110 may as sociate with a speci fic cell ( e . g . , gNB 120A and / or gNB 120B ) .Attorney Docket No . 30164 / 104102Ref . No . P71621WO1

[0018] The network arrangement 100 also includes a cellular core network 130, the Internet 140, an IP Multimedia Subsystem ( IMS) 150, and a network services backbone 160. The cellular core network 130 manages the traffic that flows between the cellular network and the Internet 140. The IMS 150 may be generally described as an architecture for delivering multimedia services to the UE 110 using the IP protocol . The IMS 150 may communicate with the cellular core network 130 and the Internet 140 to provide the multimedia services to the UE 110. The network services backbone 160 is in communication either directly or indirectly with the Internet 140 and the cellular core network 130. The network services backbone 160 may be generally described as a set of components (e . g. , servers, network storage arrangements, etc. ) that implement a suite of services that may be used to extend the functionalities of the UE 110 in communication with the various networks .

[0019] Fig. 2 shows an example UE 110 according to various example embodiments . The UE 110 will be described with regard to the network arrangement 100 of Fig. 1. The UE 110 may represent any electronic device and may include a processor 205, a memory arrangement 210, a display device 215, an input / output ( I / O) device 220, a transceiver 225, and other components 230. The other components 230 may include, for example, an audio input device, an audio output device, a battery that provides a limited power supply, a data acquisition device, ports to electrically connect the UE 110 to other electronic devices, sensors to detect conditions of the UE 110, etc .Attorney Docket No . 30164 / 104102Ref . No . P71621WO1

[0020] The processor 205 may be configured to execute a plurality of engines for the UE 110. For example, the engines may include a UE capability engine 235 for performing various operations related to reporting UE capabilities associated with support of single-DCI, multi-cell, mult i-PDSCH / PUSCH scheduling, of the example embodiments . The operations include, but are not limited to, determining parameters related to single-DCI, multicell, multi-PDSCH / PUSCH scheduling supported by the UE 110, reporting the parameters as part of UE capability information and monitoring for single-DCI, multi-cell, multi-PDSCH / PUSCH scheduling from the network. Each of these example operations will be described in more detail below.

[0021] The above referenced engine being an application (e . g. , a program) executed by the processor 205 is only an example . The functionality associated with the engines may also be represented as a separate incorporated component of the UE 110 or may be a modular component coupled to the UE 110, e . g. , an integrated circuit with or without firmware . For example, the integrated circuit may include input circuitry to receive signals and processing circuitry to process the signals and other information. The engines may also be embodied as one application or separate applications . In addition, in some UEs, the functionality described for the processor 205 is split among two or more processors such as a baseband processor and an applications processor. The example embodiments may be implemented in any of these or other configurations of a UE .

[0022] The memory arrangement 210 may be a hardware component configured to store data related to operations performed by the UE 110. The display device 215 may be a hardware componentAttorney Docket No . 30164 / 104102Ref . No . P71621WO1configured to show data to a user while the I / O device 220 may be a hardware component that enables the user to enter inputs . The display device 215 and the I / O device 220 may be separate components or integrated together such as a touchscreen.

[0023] The transceiver 225 may be a hardware component configured to establish a connection with the 5G NR-RAN 120, an LTE-RAN (not pictured) , a legacy RAN (not pictured) , a WLAN (not pictured) , etc . The transceiver 225 may include a main radio (MR) and a low power wakeup radio (LP-WUR) . Accordingly, the transceiver 225 may operate on a variety of different frequencies or channels (e . g. , set of consecutivefrequencies) . The transceiver 225 includes circuitry configured to transmit and / or receive signals (e . g. , control signals, data signals) . Such signals may be encoded with information implementing any one of the methods described herein. The processor 205 may be operably coupled to the transceiver 225 and configured to receive from and / or transmit signals to the transceiver 225. The processor 205 may be configured to encode, decode and / or process signals (e . g. , signaling from a base station of a network) for implementing any one of the methods described herein.

[0024] In the example of Fig. 2, the processor 205 and the radio frequency (RF) circuitry (e . g. , transceiver 225) are illustrated as separate components . However, in some example embodiments, the RF circuitry and the processing circuitry may be integrated into the same chip, e . g. , a system on chip that includes a baseband processor and RF circuitry.Attorney Docket No . 30164 / 104102Ref . No . P71621WO1

[0025] Fig . 3 shows an example base station 300 according to various example embodiments . The base station 300 may represent the gNB 120A, gNB 120B or any other access node through which the UE 110 may establish a connection and manage network operations .

[0026] The base station 300 may include a processor 305, a memory arrangement 310, an input / output ( I / O) device 315, a transceiver 320, and other components 325. The other components 325 may include, for example, an audio input device, an audio output device, a battery, a data acquisition device, ports to electrically connect the base station 300 to other electronic devices and / or power sources , etc .

[0027] The processor 305 may be configured to execute a plurality of engines for the UE 110 . For example, the engines may include a PDSCH / PUSCH Scheduling engine 330 for performing operations related to single-DCI , multi-cell, multi-PDSCH / PUSCH scheduling for a UE . The operations include, but are not limited to, processing UE capabilities associated with single-DCI , multi-cell, multi-PDSCH / PUSCH scheduling and scheduling the UE using single-DCI , multi-cell , multi-PDSCH / PUSCH scheduling . Each of these example operations will be described in more detail below.

[0028] The memory arrangement 310 may be a hardware component configured to store data related to operations performed by the base station 300. The I / O device 315 may be a hardware component or ports that enable a user to interact with the base station 300 . The transceiver 320 may be a hardware component configuredAttorney Docket No . 30164 / 104102Ref . No . P71621WO1to exchange data with the UE 110 and any other UE in the network arrangement 100 .

[0029] The transceiver 320 may be a hardware component configured to exchange data with the UE 110 and any other UE in the network arrangement 100 . The transceiver 320 may operate on a variety o f di f ferent frequencies or channel s ( e . g . , set o f consecutive frequencies ) . The transceiver 320 includes circuitry configured to transmit and / or receive s ignals ( e . g . , control s ignal s , data signal s ) . Such s ignal s may be encoded with information implementing any one o f the methods described herein . The proces sor 305 may be operably coupled to the transceiver 320 and conf igured to receive from and / or transmit s ignal s to the transceiver 320 . The proces sor 305 may be configured to encode , decode and / or proces s s ignals ( e . g . , s ignal ing from a UE ) for implementing any one o f the methods described herein .

[0030] In the example o f Fig . 3 , the proces sor 305 and the radio frequency ( RF) circuitry ( e . g . , transceiver 325 ) are i l lustrated as separate components . However , in some example embodiments , the RF circuitry and the process ing circuitry may be integrated into the same chip, e . g . , a system on chip that includes a baseband processor and RF circuitry .

[0031] As described above , the example embodiments are related to multi-cel l multi-PDSCH / PUSCH schedul ing us ing a s ingle DCI . In the example embodiments , the DCI may be DCI Format 0 3 for schedul ing PUSCH or DCI Format 1 3 for scheduling PDSCH . As wi l l be described in greater detail below, some f ields o f these DCI formats may be enhanced to accommodate the s ingleAttorney Docket No . 30164 / 104102Ref . No . P71621WO1DCI multi-cell multi-PDSCH / PUSCH scheduling . In addition, single-DCI , multi-cell multi-PDSCH / PUSCH scheduling may affect a Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) codebook to handle multiple PDSCHs per cell . The HARQ-ACK codebook may be transmitted by a UE on a Physical Uplink Control Channel (PUCCH) . The single-DCI , multi-cell multi-PDSCH / PUSCH scheduling may also affect the HARQ-ACK PUCCH timeline . Because of these and other issues or principles related to single-DCI , multi-cell multi-PDSCH / PUSCH scheduling, the network may use additional information concerning the UE capabilities when scheduling the UE using this technique . The example embodiments provide operations for the UE to report the UE capability information related to single-DCI , multi-cell multi-PDSCH / PUSCH scheduling to the network .

[0032] Prior to describing the example embodiments , some general principles related to single-DCI , multi-cell multi-PDSCH / PUSCH scheduling are described . Initially, the general principles related to the DCI Format are described. Enhancing the fields of the DCI Format 0 3 / 1 3 may follow the general principles that for the New Data Indicator / Redundancy Version (NDI / RV) field in the DCI format 0 3 / 1 3 for a transport block ( TB) , for each block of the NDI / RV field, the number of bits is equal to the maximum number of schedulable PUSCHs / PDSCHs on the corresponding cell by the DCI format 0 3 / 1 3. The maximum number of schedulable PUSCHs / PDSCHs on the corresponding cell may be determined using the Time Domain Resource Allocation (TDRA) table for the cell . Within each block of the NDI / RV field, the NDI / RV bits may be placed in the least significant bits (LSBs ) based on the Start and Length Indicator Value ( SLIV) position inAttorney Docket No . 30164 / 104102Ref . No . P71621W01the indicated TDRA row. Padding bits , if any, may be placed in the most significant bits (MSBs ) within the block .

[0033] In addition, a common Frequency Domain Resource Allocation ( FDRA) and Modulation and Coding Scheme (MCS ) may be applied to the PUSCHs / PDSCHs on the cell similar to Rel-16 / 17 mul ti-PUSCH / PDSCH scheduling . A single TDRA field in DCI format 0 3 / 1 3 may indicate one row from a j oint TDRA table . Each row in the table may include only one TDRA index for each bandwidth part (BWP) of each cell within the set of cells . Each TDRA index points to one or multiple time domain resource allocations in the TDRA table applicable for multi-PUSCH / PDSCH scheduling by DCI format 0 3 / 1 3 for the corresponding cell .

[0034] For Type-lC fields in DCI format 0_3 , when the TDRA field indicates more than one scheduled PUSCH on the scheduled cell with the smallest cell index, the Channel State Information (CSI ) request field may apply to the PUSCH determined based on Rel-17 multi-PUSCH scheduling on the same serving cell .Regarding the presence of UL-SCH field, a 1 bit UL-SCH field may be always present in DCI format 0_3 . The UL-SCH field and the CSI request field in a DCI format 0 3 may be applied to the same PUSCH .

[0035] For a DCI format 1 3 with fields repurposed for Secondary Cell (SCell ) dormancy indication and scheduling one or more PDSCHs , if the TDRA field indicates multiple SLIVs for the serving cell with smallest serving cell index with invalid FDRA, the HARQ-ACK information bit for the SCell dormancy indication may be an ACK for the first SLIV and followed by NACK bits for the remaining SLIVs .Attorney Docket No . 30164 / 104102Ref . No . P71621WO1

[0036] Wi th respect to the HARQ-ACK codebook, a HARQ proces s number indicated for the cel l may be appl ied to the f irst scheduled PUSCH / PDSCH and then incremented by 1 for subsequent PUSCHs / PDSCHs on the cel l (with modulo operation i f needed) as in the Rel- 1 6 / 17 multi-PUSCH / PDSCH schedul ing . Time domain HARQ-ACK bundl ing may be supported .

[0037] A Type-2 HARQ-ACK codebook may be generated by concatenating a f irst sub-codebook and a second sub-codebook . The f irst sub-codebook may comprise HARQ-ACK information bits for PDSCH ( s ) scheduled by DCI ( s ) with each scheduling a s ingle PDSCH, or each schedul ing a s ingle cell with multiple PDSCHs on it and nrofHARQ-BundlingGroups information element ( IE ) configured as 1 , and HARQ-ACK information bit ( s ) for DCI ( s ) having as sociated HARQ-ACK information without schedul ing PDSCH reception . The second sub-codebook may compri se HARQ-ACK information bits for PDSCHs scheduled by DCI ( s ) with each schedul ing more than one cel l , or each schedul ing a s ingle cel l with multiple PDSCHs on it without a nro fHARQ-Bundl ingGroups IE or a nro fHARQ-Bundl ingGroups IE conf igured larger than 1 .

[0038] Separate Downl ink As signment Index ( DAI ) counting may be appl ied for DCI ( s ) as sociated with the f irst sub-codebook and DCI ( s ) as sociated with the second sub-codebook as Rel- 18 . For the second sub-codebook, the number o f HARQ-ACK information bits for each DCI format 1_3 i s equal to M, where M i s the maximum number o f HARQ-ACK information bits which can be generated for a DCI format 1 3 acros s al l the conf igured cell set ( s ) in the Physical Upl ink Control Channel ( PUCCH) group for the UE . M mayAttorney Docket No . 30164 / 104102Ref . No . P71621WO1be implicitly derived based on a Radio Resource Control (RRC) configuration .

[0039] For the second sub-codebook, the HARQ-ACK information bits for a DCI format 1 3 are ordered firstly according to a same ordering as in Rel-17 multi-PDSCHs scheduling for PDSCH receptions on a same serving cell, then according to ascending order of associated serving cell indexes .

[0040] With respect to the HARQ-ACK PUCCH timeline (e . g . , the time the UE uses to receive the PDSCHs, process the PDSCHs and generate the HARQ-ACK codebook) , to determine the timing of a PUCCH carrying HARQ-ACK information corresponding to a set of co-scheduled PDSCHs by a DCI format 1 3, Rel-18 operations may be used . If the UE is not provided with a subslotLengthForPUCCH IE, the DL slot nD may be the DL slot ending last among the DL slots where more than one PDSCHs are scheduled by the DCI format 1 3 . I f the UE is provided with a subslotLengthForPUCCH IE, change from the legacy operation may be implemented. This feature (e . g . , single DCI multi-cell multi-PDSCH) may not impact the existing UE processing PDSCH timeline requirement for any individual PDSCH, as currently specified in 3GPP Technical Specification (TS ) 38 .214 Section 5. 3 . 1 .

[0041] In the example embodiments , a maximum number of PUSCHs / PDSCHs for a scheduled cell by a DCI format 0_3 / l_3 may be 8 . In some example embodiments, a payload size of a DCI format 0 3 / 1 3 may have a maximum value of 140 bits . In addition, some example embodiments may support up to two different subcarrier spacings ( SCS ) that may be scheduled by a DCI format 0 3 / 1 3 .Attorney Docket No . 30164 / 104102Ref . No . P71621WO1

[0042] The fol lowing provides some example use cases for scheduled cel l s when s ingle-DCI multi-cel l multi-PDSCH / PUSCH i s implemented . The example embodiments are not l imited to these uses cases , but these are merely provided to i l lustrate various scenarios that may result from single-DCI multi-cel l multi-PDSCH / PUSCH schedul ing . In a f irst use case , a DCI format 0_3 / l_3 may schedule PUSCHs / PDSCHs on Frequency Range 1 ( FR1 ) l icensed FDD cell ( s ) with a f irst SCS and FR1 l icensed TDD cel l ( s ) with a second SCS , where the first and second SCS may be the same or di f ferent . In a second use case , a DCI format 0_3 / l_3 may schedule PUSCHs / PDSCHs on FR1 licensed FDD cel l ( s ) with a f irst SCS and Frequency Range 2- 1 ( FR2 - 1 ) cel l ( s ) with a second SCS , where the f irst and second SCS may be the same or di f ferent . In a third use case , a DCI format 0_3 / l_3 may schedule PUSCHs / PDSCHs on FR1 l icensed TDD cel l ( s ) with a f irst and FR2 - 1 cel l ( s ) with a second SCS , where the f irst and second SCS may be the same or di f ferent . In a fourth use case , a DCI format 0 3 / 1 3 may schedule PUSCHs / PDSCHs on FR1 licensed FDD cel l ( s ) with di f ferent SCS . In a f i fth use case , a DCI format 0_3 / l_3 may schedule PUSCHs / PDSCHs on FR1 licensed TDD cel l ( s ) with di f ferent SCS . In a sixth use case , a DCI format 0 3 / 1 3 may schedule PUSCHs / PDSCHs on FR2- 1 cel l ( s ) with di f ferent SCS . The above use cases show some examples o f carrier combinations that may be supported by a UE . However, these examples are not exhaustive , and other combinations may be supported by a UE .

[0043] Initial ly, the example embodiments describe UE capabi l ities with respect to multi-cell multi-PDSCH schedul ing by DCI format 1_3 by a schedul ing cel l with a same or di f ferent SCS and / or a same or di f ferent carrier type ( e . g . , FDD, TDD )Attorney Docket No . 30164 / 104102Ref . No . P71621WO1between the cells in the set of cells . For example, if a UE reports a UE capability to the network that the UE supports single-DCI multi-cell multi-PDSCH scheduling by DCI format 1_3 , the UE may support the following features or components . In the example embodiments , the scheduling cell may be one of the set of cells that are scheduled by the DCI format 1_3 or the scheduling cell may not be one of the set of cells that are scheduled by the DCI format 1 3 .

[0044] In a first component, the UE may report and support monitoring DCI format 1 3 for DL scheduling with a same or different SCS and / or a same or different carrier type between the cells in the set, e . g . , the multiple cells serving the scheduled PDSCHs .

[0045] In a second component, the UE may report and support a capability that, when the set of cells includes a Primary Cell ( PCell ) , the scheduling cell is the PCell . However, when the set of cells includes only SCells , the scheduling cell may be a PCell or an SCell .

[0046] In a third component, the UE may report and support a capability related to a combination of carrier type and SCS value for a scheduling cell and co-scheduled cells . This capability may be reported from a candidate value set . For example, the value set may include { same SCS-same carrier type, same SCS-diff erent carrier type, different SCS-same carrier type, different SCS-diff erent carrier type } .

[0047] In a fourth component, the UE may report and support candidate values for the combination of SCS and carrier typeAttorney Docket No . 30164 / 104102Ref . No . P71621WO1depending on the capabilities reported for the third component . The candidate values for the fourth component may also include frequency band information as will be described below . For example, if the UE reported support in the third component of same SCS-same carrier type, the candidate value set in the fourth component may include { FR1 licensed FDD, FR1 licensed TDD, FR1 unlicensed TDD, FR2-1 , FR2-2 } , where the UE may report one or multiple of values from the value set . I f the UE reported support in the third component of same SCS-diff erent carrier type, the candidate value set in the fourth component may include { FR1 licensed FDD-FR1 licensed TDD, FR1 licensed-FR2-1 , FR1 licensed TDD-FR2-1 } , where the UE may report one or multiple of values from the value set . I f the UE reported support in the third component of different SCS-same carrier type, the candidate value set in the fourth component may include { FR1 licensed FDD : 15kHz-30kHz , FR1 licensed TDD : 15kHz-30kHz, FR2-1 : 60kHz-120kHz } , where the UE may report one or multiple of values from the value set . I f the UE reported support in the third component of different SCS-diff erent carrier type, the candidate value set in the fourth component may include { FR1 licensed FDD : 15kHz-FRl licensed TDD : 30kHz , FR1 licensed FDD : 30kHz-FRl licensed TDD : 15kHz , FR1 licensedFDD : 15kHz-FR2-l : 60kHz, FR1 licensed FDD : 15kHz-FR2-l : 120kHz , FR1 licensed FDD : 30kHz-FR2-l : 60kHz , FR1 licensed FDD : 30kHz-FR2-1 : 120kHz , FR1 licensed TDD : 15kHz-FR2-l : 60kHz, FR1 licensed TDD : 15kHz-FR2-l : 120kHz, FR1 licensed TDD : 30kHz-FR2- 1 : 60kHz , FR1 licensed TDD : 30kHz-FR2-l : 120kHz } , where the UE may report one or multiple of values from the value set .

[0048] The above example embodiments of the third and fourth component are related to the example use cases described above .Attorney Docket No . 30164 / 104102Ref . No . P71621WO1The example embodiments are not limited to these use cases but are merely provided to i l lustrate the example embodiments .

[0049] In a fi fth component , the UE may report and support a maximum number of co-scheduled cel l s per set o f cel l s . The candidate value set for the f i fth component may include { 2 , 3 , 4 } .

[0050] In a sixth component , the UE may report and support a maximum number of PDSCHs per co-scheduled cel l s per set o f cel l s and a maximum number of PDSCHs acros s al l the co-scheduled cel l s per set o f cel ls . As described above , within each cel l , a maximum number of 8 PDSCHs may be scheduled . However , thi s sixth component may limit an overal l number of PDSCHs that are scheduled by a single-DCI . For example , the UE may report support o f any of the fol lowing candidate value set combinations o f { 2 : 4 , 2 : 6 , 2 : 8 , 4 : 4 , 4 : 8 , 4 : 12 , 4 : 16 , 8 : 8 , 8 : 1 6 } . Thus , in one example , i f the UE reports support o f 2 : 4 in thi s s ixth component , the UE indicates that it supports a maximum number o f 2 PDSCHs per co-scheduled cel l and a maximum number o f 4 PDSCHs acros s al l the co- scheduled cel ls . In another example , i f the UE reports support o f 8 : 16 in thi s sixth component , the UE indicates that it supports a maximum number o f 8 PDSCHs per coscheduled cel l and a maximum number o f 1 6 PDSCHs acros s al l the co- scheduled cell s .

[0051] In a seventh component , the UE may report and support a maximum number o f sets o f cel ls acros s PUCCH groups . The UE may report a candidate value from a set o f { 1 , 2 , 3 , 4 , 5 , 6 , 7 , 8 } .Attorney Docket No . 30164 / 104102Ref . No . P71621WO1

[0052] In an eighth component , the UE may report and support a maximum number o f sets o f cel ls supported by the UE for a same schedul ing cel l . The UE may report a candidate value from a set o f { 1 , 2 , 3 , 4 } .

[0053] In a ninth component , the UE may report supported HARQ feedback types . The UE may report a candidate value from a set o f { type 1 , type2 , type 1 and type 2 } .

[0054] In a tenth component , the UE may report supported coscheduled cel l indication schemes . The UE may report a candidate value from a set o f { FDRA f ield based, co- scheduled cel l indicator field based, both } .

[0055] In an eleventh component , the UE may report supported Type-2 for an 'Antenna port ( s ) ' field .

[0056] In a twel fth component , the UE may report and support a number of unicast DL DCI s to proces s per N consecutive s lots o f scheduling cel l for a set o f cel l s conf igured for multi-cel l multi-PDSCH schedul ing by DCI format 1_3 . In a f irst example , the UE may support N = 1 for one DCI format 1 3 for the set of cel ls . In a second example , the UE may support one unicast DL DCI formats l_0 / l_l / l_2 ( i f supported) for each of the cel l s that are not scheduled by DCI 1 3 . In a third example , N =1 for the same SCS acros s scheduling cel l and al l the co- scheduled cel ls within the set .

[0057] In a fourth example , for co-scheduled cel l s with di f ferent SCS s , for the lowest-to-highest SCS , N = 1 , where the highest SCS corresponds to the maximum SCS among the coAttorney Docket No . 30164 / 104102Ref . No . P71621WO1scheduled cells within the set of cells and when the SCS of at least one co-scheduled cell within the set is higher than the SCS of the scheduling cell . In a fifth example, for co-scheduled cells with different SCSs, for highest-to-lowest SCS, N is based on pair of (scheduling CC SCS, scheduled CC SCS) : N=2 for (30, 15) , ( 60, 30) , ( 120, 60) and N=4 for ( 60, 15) , (120, 30) , N = 8 for (120, 15) , where the lowest SCS corresponds the minimum SCS among the co-scheduled cells within the set of cells and when the SCS of at least one co-scheduled cells within the set is lower than the SCS of the scheduling cell .

[0058] In a thirteenth component, the UE may report and support monitoring search space (SS) set (s) for DCI format 1 3 for a set of cells for the following cases . The difference between the twelfth component and the thirteenth component is that in the twelfth component, the UE capability is related to processing of actual DCIs that are received. The thirteenth component is related to the UE capability for monitoring for DCI . For example, the UE may be configured with a SS set that may include one or more monitoring occasions . The UE may or may not receive DCI in these monitoring occasions . The thirteenth component may include UE capability information related to this monitoring for DCI rather than processing actual DCI as in the twelfth component .

[0059] There may be multiple cases that are applicable to the UE capability related to the thirteenth component . In a first case, the SS set configuration for DCI format 1 3 for the set of cells is provided only on the scheduling cell .Attorney Docket No . 30164 / 104102Ref . No . P71621WO1

[0060] In a second case, when the scheduling cell is outside the set of cells, then the SS set configuration for DCI format 1_3 for the set of cells with the same searchSpaceld are provided on both the scheduling cell and a serving cell in the set of cells . In this case, when the scheduling cell is not in the set of cells, there may be various options for the UE to support which serving cell in the set of cells is provided with the SS set configuration. In a first option, the serving cell may be associated with the lowest SCS among all the co-scheduled cells within the cell set . In a second option, the serving cell may be associated with the highest SCS among all the coscheduled cells within the cell set . In a third option, the serving cell may be associated with the SCS that is at least not higher than the SCS of the scheduling cell . In a fourth option, the serving cell may be associated with the SCS that is at least not lower than the SCS of the scheduling cell .

[0061] In a third case, when the scheduling cell is also within the set of cells, then UE may report a capability that the SS set configurations for DCI format 1 3 for the set of cells with the same searchSpaceld may be provided on both the scheduling cell and a serving cell in the set of cells .

[0062] Fig. 4 shows an example method 400 for a UE to report a capability related to single-DCI multi-cell multi-PDSCH scheduling to a network according to various example embodiments . The method 400 may be performed by the UE 110 of Fig. 2 operating in the network arrangement 100 of Fig. 1.

[0063] In 410, the UE 110 may report a UE capability with respect to single-DCI multi-cell multi-PDSCH scheduling to theAttorney Docket No . 30164 / 104102Ref . No . P71621WO1network . Some example components that may be included in the UE capability reporting were described above .

[0064] In 420, the UE 110 may receive and process DCI Format 1 3 that includes multi-cell multi-PDSCH scheduling . In this example, the UE 110 supports single-DCI multi-cell multi-PDSCH scheduling and the received scheduling may be according to the UE capability reported in 410 .

[0065] In 430, the UE may receive and process the multiple PDSCHs based on the scheduling received in 430 .

[0066] The example embodiments also describe UE capabilities with respect to multi-cell multi-PUSCH scheduling by DCI format 0_3 on a scheduling cell with a same or different SCS and / or a same or different carrier type (e . g . , FDD, TDD) between the cells in the set of cells . For example, if a UE reports a UE capability to the network that the UE supports single-DCI multicell multi-PUSCH scheduling by DCI format 0 3 , the UE may support the following features or components . In the example embodiments , the scheduling cell may be one of the set of cells that are scheduled by the DCI format 0 3 or the scheduling cell may not be one of the set of cells that are scheduled by the DCI format 0_3 .

[0067] In a first component, the UE may report and support monitoring DCI format 0_3 for UL scheduling with a same or different SCS and / or a same or different carrier type between the cells in the set .Attorney Docket No . 30164 / 104102Ref . No . P71621WO1

[0068] In a second component, the UE may report and support a capability that, when the set of cells includes a Primary Cell ( PCell ) , the scheduling cell is the PCell . However, when the set of cells includes only SCells , the scheduling cell may be a PCell or an SCell .

[0069] In a third component, the UE may report and support a capability related to a combination of carrier type and SCS value for a scheduling cell and co-scheduled cells . This capability may be reported from a candidate value set . For example, the value set may include { same SCS-same carrier type, same SCS-diff erent carrier type, different SCS-same carrier type, different SCS-diff erent carrier type } .

[0070] In a fourth component, the UE may report and support candidate values for the combination of SCS and carrier type depending on the capabilities reported for the third component . For example, if the UE reported support in the third component of same SCS-same carrier type, the candidate value set in the fourth component may include { FR1 licensed FDD, FR1 licensed TDD, FR1 unlicensed TDD, FR2-1 , FR2-2 } , where the UE may report one or multiple of values from the value set . I f the UE reported support in the third component of same SCS-diff erent carrier type, the candidate value set in the fourth component may include { FR1 licensed FDD-FR1 licensed TDD, FR1 licensed-FR2-1 , FR1 licensed TDD-FR2-1 } , where the UE may report one or multiple of values from the value set . I f the UE reported support in the third component of different SCS-same carrier type, the candidate value set in the fourth component may include { FR1 licensed FDD : 15kHz-30kHz , FR1 licensed TDD : 15kHz-30kHz, FR2-1 : 60kHz-120kHz } , where the UE may report one orAttorney Docket No . 30164 / 104102Ref . No . P71621WO1multiple of values from the value set . I f the UE reported support in the third component of di f ferent SCS-di f f erent carrier type , the candidate value set in the fourth component may include { FR1 l icensed FDD : 15kHz- FRl l icensed TDD : 30kHz , FR1 l icensed FDD : 30kHz- FRl l icensed TDD : 15kHz , FR1 l icensedFDD : 15kHz-FR2 - l : 60 kHz , FR1 l icensed FDD : 15kHz- FR2- l : 120kHz , FR1 l icensed FDD : 30kHz- FR2 - l : 60kHz , FR1 l icensed FDD : 30 kHz-FR2 -1 : 120 kHz , FR1 licensed TDD : 15kHz-FR2 - l : 60 kHz , FR1 l icensed TDD : 15kHz-FR2 - l : 120 kHz , FR1 l icensed TDD : 30kHz- FR2- 1 : 60kHz , FR1 l icensed TDD : 30kHz- FR2 - l : 120 kHz } , where the UE may report one or multiple of values from the value set .

[0071] The above example embodiments o f the third and fourth component are related to the example use cases described above . The example embodiments are not limited to these use cases but are merely provided to i l lustrate the example embodiments .

[0072] In a fi fth component , the UE may report and support a maximum number of co-scheduled cel l s per set o f cel l s . The candidate value set for the f i fth component may include { 2 , 3 , 4 } .

[0073] In a sixth component , the UE may report and support a maximum number of PUSCHs per co-scheduled cel l s per set o f cel l s and a maximum number of PUSCHs acros s al l the co-scheduled cel l s per set o f cel ls . As described above , within each cel l , a maximum number of 8 PDSCHs may be scheduled . However , thi s sixth component may limit an overal l number of PUSCHs that are scheduled by a single-DCI . For example , the UE may report support o f any of the fol lowing candidate value set combinations o f { 2 : 4 , 2 : 6 , 2 : 8 , 4 : 4 , 4 : 8 , 4 : 12 , 4 : 16 , 8 : 8 , 8 : 1 6 } . Thus , in oneAttorney Docket No . 30164 / 104102Ref . No . P71621WO1example , i f the UE reports support o f 2 : 4 in thi s s ixth component , the UE indicates that it supports a maximum number o f 2 PUSCHs per co-scheduled cel l and a maximum number o f 4 PUSCHs acros s al l the co- scheduled cel ls . In another example , i f the UE reports support o f 8 : 16 in thi s sixth component , the UE indicates that it supports a maximum number o f 8 PUSCHs per coscheduled cel l and a maximum number o f 1 6 PUSCHs acros s al l the co- scheduled cell s .

[0074] In a seventh component , the UE may report and support a maximum number o f sets o f cel ls acros s PUCCH groups . The UE may report a candidate value from a set o f { 1 , 2 , 3 , 4 , 5 , 6 , 7 8 } .

[0075] In an eighth component , the UE may report and support a maximum number o f sets o f cel ls supported by the UE for a same schedul ing cel l . The UE may report a candidate value from a set o f { 1 , 2 , 3 , 4 } .

[0076] In a ninth component , the UE may report supported coscheduled cel l indication schemes . The UE may report a candidate value from a set o f { FDRA f ield based, co- scheduled cel l indicator field based, both } .

[0077] In a tenth component , the UE may report supported Type-2 for an 'Antenna port ( s ) ' field .

[0078] In an eleventh component , the UE may report and support a number o f unicast UL DCI s to proces s per N consecutive s lots o f scheduling cel l for a set o f cel l s conf igured for multi-cel l multi-PDSCH schedul ing by DCI format 0 3 . Thi sAttorney Docket No . 30164 / 104102Ref . No . P71621WO1capability may be based on whether the scheduling cell is an FDD cell or a TDD cell .

[0079] When the scheduling cell is an FDD cell, in a first example, the UE may support N = 1 for one DCI format 0 3 for the set of cells . In a second example, the UE may support one unicast DL DCI formats 0 0 / 0 1 / 0 2 (if supported) for each of the cells that are not scheduled by DCI 0 3. In a third example, N =1 for the same SCS across scheduling cell and all the coscheduled cells within the set .

[0080] When the scheduling cell is a TDD cell, in a first example, the UE may support N = 1 for one DCI format 0 3 for the set of cells . In a second example, the UE may support two unicast DL DCI formats 0_0 / 0_l / 0_2 (if supported) for each of the cells that are not scheduled by DCI 0 3. In a third example, N =1 for the same SCS across scheduling cell and all the coscheduled cells within the set .

[0081] When the scheduling cell is a TDD cell or an FDD cell, in a fourth example, for co-scheduled cells with different SCSs, for the lowest-to-highest SCS, N = 1, where the highest SCS corresponds the maximum SCS among the co-scheduled cells within the set of cells and when the SCS of at least one co-scheduled cell within the set is higher than the SCS of the scheduling cell .

[0082] When the scheduling cell is a TDD cell or an FDD cell, in a fifth example, for co-scheduled cells with different SCSs, for highest-to-lowest SCS, N is based on pair of (scheduling CC SCS, scheduled CC SCS) : N=2 for (30, 15) , ( 60, 30) , ( 120, 60) andAttorney Docket No . 30164 / 104102Ref . No . P71621WO1N=4 for ( 60, 15) , ( 120, 30) , N = 8 for (120, 15) , where the lowest SCS corresponds the minimum SCS among the co-scheduled cells within the set of cells and when the SCS of at least one coscheduled cells within the set is lower than the SCS of the scheduling cell .

[0083] In a twelfth component, the UE may report and support monitoring search space (SS) set (s) for DCI format 0 3 for a set of cells for the following cases . The difference between the twelfth component and the thirteenth component is that in the twelfth component, the UE capability is related to processing of actual DCIs that are received. The thirteenth component is related to the UE capability for monitoring for DCI . For example, the UE may be configured with a SS set that may include one or more monitoring occasions . The UE may or may not receive DCI in these monitoring occasions . The thirteenth component may include UE capability information related to this monitoring for DCI rather than processing actual DCI as in the twelfth component .

[0084] There may be multiple cases that are applicable to the UE capability related to the thirteenth component . In a first case, the SS set configuration for DCI format 0 3 for the set of cells is provided only on the scheduling cell .

[0085] In a second case, when the scheduling cell is outside the set of cells, then the SS set configuration for DCI format 0 3 for the set of cells with the same searchSpaceld are provided on both the scheduling cell and a serving cell in the set of cells . In this case, when the scheduling cell is not in the set of cells, there may be various options for the UE toAttorney Docket No . 30164 / 104102Ref . No . P71621WO1support which serving cell in the set of cells is provided with the SS set configuration. In a first option, the serving cell may be associated with the lowest SCS among all the co-scheduled cells within the cell set . In a second option, the serving cell may be associated with the highest SCS among all the coscheduled cells within the cell set . In a third option, the serving cell may be associated with the SCS that is at least not higher than the SCS of the scheduling cell . In a fourth option, the serving cell may be associated with the SCS that is at least not lower than the SCS of the scheduling cell .

[0086] In a third case, when the scheduling cell is also within the set of cells, then UE may report a capability that the SS set configurations for DCI format 0 3 for the set of cells with the same searchSpaceld may be provided on both the scheduling cell and a serving cell in the set of cells .

[0087] Fig. 5 shows an example method 500 for a UE to report a capability related to single-DCI multi-cell multi-PUSCH scheduling to a network according to various example embodiments . The method 500 may be performed by the UE 110 of Fig. 2 operating in the network arrangement 100 of Fig. 1.

[0088] In 510, the UE 110 may report a UE capability with respect to single-DCI multi-cell multi-PUSCH scheduling to the network. Some example components that may be included in the UE capability reporting were described above .

[0089] In 520, the UE 110 may receive and process DCI Format 0_3 that includes multi-cell multi-PUSCH scheduling. In this example, the UE 110 supports single-DCI multi-cell multi-PUSCHAttorney Docket No . 30164 / 104102Ref . No . P71621WO1scheduling and the received scheduling may be according to the UE capability reported in 510 .

[0090] In 530, the UE 110 may generate and transmit the multiple PUSCHs based on the scheduling received in 530.Examples

[0091] In a first example, a method, comprising generating, for transmission to a network, user equipment (UE) capability information associated with a single-Downlink Control Information ( single-DCI ) multi-cell Multi-Physical Downlink Shared Channel (multi-PDSCH) scheduling capability, processing, based on signaling from a scheduling cell of the network, a DCI Format 1 3 comprising scheduling information for a set of cells , wherein each of the set of cells are scheduled with one or more PDSCHs and processing, based on signaling from the network, the one or more PDSCHs received from each of the set of cells .

[0092] In a second example, the method of the first example, wherein the UE capability information comprises a supported capability associated with a subcarrier spacing (SCS ) of the set of cells , wherein the supported capability comprises each of the set of cells having a same SCS or at least one of the set of cells having a different SCS than other cells of the set of cells .

[0093] In a third example, the method of the first example, wherein the UE capability information comprises a supported capability associated with a carrier type of the set of cells, wherein the carrier type comprises a frequency domain duplexing ( FDD) type or a time domain duplexing ( TDD) type, wherein theAttorney Docket No . 30164 / 104102Ref . No . P71621WO1supported capability comprises each of the set of cells having a same carrier type or at least one of the set of cells having a different carrier type than other cells of the set of cells .

[0094] In a fourth example, the method of the first example, wherein the UE capability information comprises a supported combination of a carrier type and subcarrier spacing (SCS ) value for the scheduling cell and the set of cells, wherein the carrier type and SCS value comprise one or more of a) a same SCS-same carrier type, b) a same SCS-diff erent carrier type, c) a different SCS-same carrier type, or d) a different SCS-different carrier type .

[0095] In a fifth example, the method of the fourth example, wherein, when the UE capability information comprises the same SCS-same carrier type, the UE capability information further comprises one or more of frequency band and carrier type combinations of a) Frequency Range 1 ( FR1 ) licensed frequency domain duplexing ( FDD) , b) FR1 licensed time domain duplexing ( TDD) , or c) FR1 unlicensed TDD, Frequency Range 2-1 ( FR2-1 ) and Frequency Range 2-2 ( FR2-2 ) .

[0096] In a sixth example, the method of the fourth example, wherein, when the UE capability information comprises the same SCS-di f f erent carrier type, the UE capability information further comprises one or more of frequency band and carrier type combinations of a) Frequency Range 1 ( FR1 ) licensed frequency domain duplexing ( FDD) and FR1 licensed time domain duplexing ( TDD) , b) FR1 licensed FDD and Frequency Range 2-1 ( FR2-1 ) , or c) FR1 licensed TDD and FR2-1 .Attorney Docket No . 30164 / 104102Ref . No . P71621WO1

[0097] In a seventh example , the method of the fourth example , wherein, when the UE capabi l ity information compri ses the di f ferent SCS- same carrier type , the UE capabil ity information further comprises one or more o f carrier type : SCS combinations o f a ) Frequency Range 1 ( FR1 ) licensed frequency domain duplexing ( FDD) : 15kHz- 30 kH, b ) FR1 licensed time domain duplexing ( TDD ) : 15kHz- 30 kHz , or c ) Frequency Range 2 - 1 ( FR2 -1 ) : 60 kHz- 120 kHz .

[0098] In an eighth example , the method of the fourth example , wherein, when the UE capabi l ity information compri ses the di f ferent SCS-di f f erent carrier type , the UE capabil ity information further comprises one or more o f frequency band, carrier type : SCS combinations of a ) Frequency Range 1 ( FR1 ) l icensed frequency domain duplexing ( FDD ) : 15kHz and FR1 l icensed time domain duplexing ( TDD ) : 30 kHz , b ) FR1 licensed FDD : 30 kHz and FR1 l icensed TDD : 15kHz , c ) FR1 licensed FDD : 15kHz and Frequency Range 2 - 1 ( FR2 - 1 ) : 60 kHz , d) FR1 licensed FDD : 15kHz and FR2 -1 : 120 kHz , e ) FR1 l icensed FDD : 30kHz and FR2- 1 : 60 kHz , f ) FR1 l icensed FDD : 30kHz and FR2- 1 : 120kHz , g) FR1 l icensed TDD : 15kHz and FR2 - 1 : 60 kHz , h ) FR1 l icensed TDD : 15kHz and FR2- 1 : 120 kHz , i ) FR1 l icensed TDD : 30 kHz and FR2 - 1 : 60 kHz , and j ) FR1 l icensed TDD : 30 kHz and FR2 - 1 : 120 kHz .

[0099] In a ninth example , the method o f the first example , wherein the UE capabil ity information comprises a maximum supported number o f PDSCHs per cel l in the set o f cel l s and a maximum supported number o f PDSCHs acros s all cells in the set o f cel l s .Attorney Docket No . 30164 / 104102Ref . No . P71621WO1

[0100] In a tenth example , the method of the ninth example, wherein candidate values for the maximum supported number of PDSCHs per cell in the set of cells : the maximum supported number of PDSCHs across all cells in the set of cells comprise { 2 : 4 , 2 : 6 , 2 : 8 , 4 : 4 , 4 : 8 , 4 : 12 , 4 : 16 , 8 : 8 , 8 : 16 } , wherein the UE capability information comprises one of the candidate values .

[0101] In an eleventh example, the method of the first example , wherein the UE capability information comprises a supported number of unicast downlink (DL ) DCI s to process per N consecutive slots of the scheduling cell for the set of cells .

[0102] In a twel fth example , the method of the eleventh example , wherein, when the set of cells comprise more than one subcarrier spacing ( SCS ) , N = 1 for each of the more than one SCS from a lowest SCS to a highest SCS , where the highest SCS corresponds a maximum SCS among the set of cells when at least one of the set of cells has an SCS that is higher than an SCS of the scheduling cell .

[0103] In a thirteenth example, the method of the eleventh example , wherein, when the set of cells comprise more than one subcarrier spacing ( SCS ) , where for a highest SCS to a lowest SCS , N is based on a value of a pair of a scheduling component carrier (CC) SCS : scheduled CC SCS , wherein N =2 for the values of the pair { ( 30 , 15 ) , ( 60 , 30 ) , ( 120 , 60 ) } , N=4 for the values of the pair { ( 60 , 15 ) , ( 120 , 30 ) } and N = 8 for the value of the pair ( 120 , 15 ) .

[0104] In a fourteenth example, the method of the first example , wherein the UE capability information comprises aAttorney Docket No . 30164 / 104102Ref . No . P71621WO1search space set configuration to schedule SS occasions to monitor for the DCI format 1 3 for the set of cells .

[0105] In a fifteenth example, the method of the fourteenth example, wherein, when the scheduling cell is not included in the set of cells, the UE capability information indicates the search space set configuration is to be received from a serving cell in the set of cells .

[0106] In a sixteenth example, the method of the fifteenth example, wherein the UE capability information indicates the serving cell in the set of cells comprises one of a) a serving cell in the set of cells having a lowest subcarrier spacing (SCS) b) a serving cell in the set of cells having a highest SCS, c) a serving cell in the set of cells having an SCS that is not higher than an SCS of the scheduling cell, or d) a serving cell in the set of cells having an SCS that is not lower than the SCS of the scheduling cell .

[0107] In a seventeenth example, the method of the fourteenth example, wherein, when the scheduling cell is included in the set of cells, the UE capability information indicates the search space set configuration is to be received from the scheduling cell and a serving cell in the set of cells .

[0108] In an eighteenth example, a processor configured to perform any of the methods of the first through seventeenth examples .Attorney Docket No . 30164 / 104102Ref . No . P71621WO1

[0109] In a nineteenth example, a user equipment configured to perform any of the methods of the first through seventeenth examples .

[0110] In a twentieth example, a method, comprising generating, for transmission to a network, user equipment (UE) capability information associated with a single-Downlink Control Information ( single-DCI ) multi-cell Multi-Physical Uplink Shared Channel (multi-PUSCH) scheduling capability, processing, based on signaling from a scheduling cell of the network, a DCI Format 0 3 comprising scheduling information for a set of cells, wherein each of the set of cells are scheduled with one or more PUSCHs and generating, for transmission to the network, the one or more PUSCHs scheduled for each of the set of cells .

[0111] In a twenty first example, the method of the twentieth example, wherein the UE capability information comprises a supported capability associated with a subcarrier spacing ( SCS ) of the set of cells , wherein the supported capability comprises each of the set of cells having a same SCS or at least one of the set of cells having a different SCS than other cells of the set of cells .

[0112] In a twenty second example, the method of the twentieth example, wherein the UE capability information comprises a supported capability associated with a carrier type of the set of cells , wherein the carrier type comprises a frequency domain duplexing ( FDD) type or a time domain duplexing ( TDD) type, wherein the supported capability comprises each of the set of cells having a same carrier type or at least one ofAttorney Docket No . 30164 / 104102Ref . No . P71621WO1the set of cells having a different carrier type than other cells of the set of cells .

[0113] In a twenty third example, the method of the twentieth example, wherein the UE capability information comprises a supported combination of a carrier type and subcarrier spacing ( SCS ) value for the scheduling cell and the set of cells, wherein the carrier type and SCS value comprise one or more of a) a same SCS-same carrier type, b) a same SCS-diff erent carrier type, c) a different SCS-same carrier type, or d) a different SCS-di f f erent carrier type .

[0114] In a twenty fourth example, the method of the twenty third example, wherein, when the UE capability information comprises the same SCS-same carrier type, the UE capability information further comprises one or more of frequency band and carrier type combinations of a) Frequency Range 1 ( FR1 ) licensed frequency domain duplexing ( FDD) , b) FR1 licensed time domain duplexing ( TDD) , or c) FR1 unlicensed TDD, Frequency Range 2-1 ( FR2-1 ) and Frequency Range 2-2 ( FR2-2 ) .

[0115] In a twenty fifth example, the method of the twenty third example, wherein, when the UE capability information comprises the same SCS-dif ferent carrier type, the UE capability information further comprises one or more of frequency band and carrier type combinations of a) Frequency Range 1 ( FR1 ) licensed frequency domain duplexing ( FDD) and FR1 licensed time domain duplexing ( TDD) , b) FR1 licensed FDD and Frequency Range 2-1 ( FR2-1 ) , or c) FR1 licensed TDD and FR2-1 .Attorney Docket No . 30164 / 104102Ref . No . P71621WO1

[0116] In a twenty s ixth example , the method of the twenty third example , wherein, when the UE capabi lity information compri ses the di f ferent SCS- same carrier type , the UE capability information further comprises one or more o f carrier type : SCS combinations o f a ) Frequency Range 1 ( FR1 ) licensed frequency domain duplexing ( FDD) : 15kHz- 30 kH, b ) FR1 licensed time domain duplexing ( TDD ) : 15kHz- 30 kHz , or c ) Frequency Range 2 - 1 ( FR2 -1 ) : 60 kHz- 120 kHz .

[0117] In a twenty seventh example , the method o f the twenty third example , wherein, when the UE capabi lity information compri ses the di f ferent SCS-di f ferent carrier type , the UE capabi l ity information further compri ses one or more o f frequency band, carrier type : SCS combinations o f a ) Frequency Range 1 ( FR1 ) licensed frequency domain duplexing ( FDD ) : 15kHz and FR1 l icensed time domain duplexing ( TDD ) : 30 kHz , b ) FR1 l icensed FDD : 30kHz and FR1 l icensed TDD : 15kHz , c ) FR1 licensed FDD : 15kHz and Frequency Range 2 - 1 ( FR2- 1 ) : 60kHz , d) FR1 l icensed FDD : 15kHz and FR2 - 1 : 120 kHz , e ) FR1 l icensed FDD : 30kHz and FR2-1 : 60kHz , f ) FR1 l icensed FDD : 30 kHz and FR2 - 1 : 120 kHz , g ) FR1 l icensed TDD : 15kHz and FR2- 1 : 60 kHz , h ) FR1 licensed TDD : 15kHz and FR2 - 1 : 120 kHz , i ) FR1 licensed TDD : 30 kHz and FR2 - 1 : 60 kHz , and j ) FR1 l icensed TDD : 30 kHz and FR2- 1 : 120 kHz .

[0118] In a twenty eighth example , the method of the twentieth example , wherein the UE capabi l ity information compri ses a maximum supported number of PUSCHs per cel l in the set of cell s and a maximum supported number o f PUSCHs acros s al l cel ls in the set o f cel l s .Attorney Docket No . 30164 / 104102Ref . No . P71621WO1

[0119] In a twenty ninth example , the method of the twenty eighth example , wherein candidate values for the maximum supported number of PUSCHs per cell in the set of cells : the maximum supported number of PUSCHs across all cells in the set of cells comprise { 2 : 4 , 2 : 6 , 2 : 8 , 4 : 4 , 4 : 8 , 4 : 12 , 4 : 16 , 8 : 8 , 8 : 16 } , wherein the UE capability information comprises one of the candidate values .

[0120] In a thirtieth example, the method of the twentieth example , wherein the UE capability information comprises a supported number of unicast uplink (UL) DCIs to process per N consecutive slots of the scheduling cell for the set of cells .

[0121] In a thirty first example , the method of the thirtieth example , wherein, when the set of cells comprise more than one subcarrier spacing ( SCS ) , N = 1 for each of the more than one SCS from a lowest SCS to a highest SCS , where the highest SCS corresponds a maximum SCS among the set of cells when at least one of the set of cells has an SCS that is higher than an SCS of the scheduling cell .

[0122] In a thirty second example , the method of the thirtieth example , wherein, when the set of cells comprise more than one subcarrier spacing ( SCS ) , where for a highest SCS to a lowest SCS , N is based on a value of a pair of a scheduling component carrier ( CC) SCS : scheduled CC SCS , wherein N =2 for the values of the pair { ( 30 , 15 ) , ( 60 , 30 ) , ( 120 , 60 ) } , N=4 for the values of the pair { ( 60 , 15 ) , ( 120 , 30 ) } and N = 8 for the value of the pair ( 120 , 15 ) .Attorney Docket No . 30164 / 104102Ref . No . P71621WO1

[0123] In a thirty third example, the method of the twentieth example, wherein the UE capability information comprises a search space set configuration to schedule SS occasions to monitor for the DCI format 0 3 for the set of cells .

[0124] In a thirty fourth example, the method of the thirty third example, wherein, when the scheduling cell is not included in the set of cells, the UE capability information indicates the search space set configuration is to be received from a serving cell in the set of cells .

[0125] In a thirty fifth example, the method of the thirty fourth example, wherein the UE capability information indicates the serving cell in the set of cells comprises one of a) a serving cell in the set of cells having a lowest subcarrier spacing (SCS) b) a serving cell in the set of cells having a highest SCS, c) a serving cell in the set of cells having an SCS that is not higher than an SCS of the scheduling cell, or d) a serving cell in the set of cells having an SCS that is not lower than the SCS of the scheduling cell .

[0126] In a thirty sixth example, the method of the thirty third example, wherein, when the scheduling cell is included in the set of cells, the UE capability information indicates the search space set configuration is to be received from the scheduling cell and a serving cell in the set of cells .

[0127] In a thirty seventh example, a processor configured to perform any of the methods of the twentieth through thirty sixth examples .Attorney Docket No . 30164 / 104102Ref . No . P71621WO1

[0128] In a thirty eighth example, a user equipment configured to perform any of the methods of the twentieth through thirty sixth examples .

[0129] Those skilled in the art will understand that the above-described example embodiments may be implemented in any suitable software or hardware configuration or combination thereof . An example hardware platform for implementing the example embodiments may include, for example, an Intel x86 based platform with compatible operating system, a Windows OS, a Mac platform and MAC OS, a mobile device having an operating system such as iOS, Android, etc . The example embodiments of the above described method may be embodied as a program containing lines of code stored on a non-transitory computer readable storage medium that, when compiled, may be executed on a processor or microprocessor .

[0130] Although this application described various embodiments each having different features in various combinations, those skilled in the art will understand that any of the features of one embodiment may be combined with the features of the other embodiments in any manner not specifically disclaimed or which is not functionally or logically inconsistent with the operation of the device or the stated functions of the disclosed embodiments .

[0131] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users . In particular, personally identifiableAttorney Docket No . 30164 / 104102Ref . No . P71621WO1information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users .

[0132] It will be apparent to those skilled in the art that various modifications may be made in the present disclosure, without departing from the spirit or the scope of the disclosure . Thus, it is intended that the present disclosure cover modifications and variations of this disclosure provided they come within the scope of the appended claims and their equivalent .

Claims

Attorney Docket No . 30164 / 104102Ref . No . P71621WO1What is claimed:1 . An apparatus comprising memory coupled to processing circuitry, the processing circuitry configured to :generate, for transmission to a network, user equipment (UE ) capability information associated with a single-Downlink Control Information ( single-DCI ) multi-cell Multi-Physical Downlink Shared Channel (multi-PDSCH) scheduling capability;process , based on signaling from a scheduling cell of the network, a DCI Format 1_3 comprising scheduling information for a set of cells , wherein each of the set of cells are scheduled with one or more PDSCHs ; andprocess , based on signaling from the network, the one or more PDSCHs received from each of the set of cells .2 . The apparatus of claim 1 , wherein the UE capability information comprises a supported capability associated with a subcarrier spacing (SCS ) of the set of cells, wherein the supported capability comprises each of the set of cells having a same SCS or at least one of the set of cells having a different SCS than other cells of the set of cells .3 . The apparatus of claim 1 , wherein the UE capability information comprises a supported capability associated with a carrier type of the set of cells, wherein the carrier type comprises a frequency domain duplexing ( FDD) type or a time domain duplexing ( TDD) type, wherein the supported capability comprises each of the set of cells having a same carrier type or at least one of the set of cells having a different carrier type than other cells of the set of cells .Attorney Docket No . 30164 / 104102Ref . No . P71621WO14. The apparatus of claim 1, wherein the UE capability information comprises a supported combination of a carrier type and subcarrier spacing (SCS) value for the scheduling cell and the set of cells, wherein the carrier type and SCS value comprise one or more of a) a same SCS-same carrier type, b) a same SCS-diff erent carrier type, c) a different SCS-same carrier type, or d) a different SCS-dif ferent carrier type .

5. The apparatus of claim 1, wherein the UE capability information comprises a maximum supported number of PDSCHs per cell in the set of cells and a maximum supported number of PDSCHs across all cells in the set of cells .

6. The apparatus of claim 1, wherein the UE capability information comprises a supported number of unicast downlink (DL) DCIs to process per N consecutive slots of the scheduling cell for the set of cells .

7. The apparatus of claim 1, wherein the UE capability information comprises a search space set configuration to schedule SS occasions to monitor for the DCI format 1_3 for the set of cells .

8. The apparatus of claim 7, wherein, when the scheduling cell is not included in the set of cells, the UE capability information indicates the search space set configuration is to be received from a serving cell in the set of cells .

9. The apparatus of claim 8, wherein the UE capability information indicates the serving cell in the set of cells comprises one of a) a serving cell in the set of cells having aAttorney Docket No . 30164 / 104102Ref . No . P71621WO1lowest subcarrier spacing (SCS ) b) a serving cell in the set of cells having a highest SCS, c) a serving cell in the set of cells having an SCS that is not higher than an SCS of the scheduling cell, or d) a serving cell in the set of cells having an SCS that is not lower than the SCS of the scheduling cell .10 . The apparatus of claim 7 , wherein, when the scheduling cell is included in the set of cells , the UE capability information indicates the search space set configuration is to be received from the scheduling cell and a serving cell in the set of cells .11 . An apparatus comprising memory coupled to processing circuitry, the processing circuitry configured to :generate, for transmission to a network, user equipment (UE ) capability information associated with a single-Downlink Control Information ( single-DCI ) multi-cell Multi-Physical Uplink Shared Channel (multi-PUSCH) scheduling capability;process , based on signaling from a scheduling cell of the network, a DCI Format 0 3 comprising scheduling information for a set of cells , wherein each of the set of cells are scheduled with one or more PUSCHs ; andgenerate, for transmission to the network, the one or more PUSCHs scheduled for each of the set of cells .12 . The apparatus of claim 11 , wherein the UE capability information comprises a supported capability associated with a subcarrier spacing (SCS ) of the set of cells, wherein the supported capability comprises each of the set of cells having a same SCS or at least one of the set of cells having a different SCS than other cells of the set of cells .Attorney Docket No . 30164 / 104102Ref . No . P71621WO113 . The apparatus of claim 11 , wherein the UE capability information comprises a supported capability associated with a carrier type of the set of cells, wherein the carrier type comprises a frequency domain duplexing ( FDD) type or a time domain duplexing ( TDD) type, wherein the supported capability comprises each of the set of cells having a same carrier type or at least one of the set of cells having a different carrier type than other cells of the set of cells .14 . The apparatus of claim 11 , wherein the UE capability information comprises a supported combination of a carrier type and subcarrier spacing ( SCS ) value for the scheduling cell and the set of cells, wherein the carrier type and SCS value comprise one or more of a) a same SCS-same carrier type, b) a same SCS-diff erent carrier type, c) a different SCS-same carrier type, or d) a different SCS-dif ferent carrier type .

15. The apparatus of claim 11 , wherein the UE capability information comprises a maximum supported number of PUSCHs per cell in the set of cells and a maximum supported number of PUSCHs across all cells in the set of cells .

16. The apparatus of claim 11 , wherein the UE capability information comprises a supported number of unicast uplink (UL) DCIs to process per N consecutive slots of the scheduling cell for the set of cells .17 . The apparatus of claim 11 , wherein the UE capability information comprises a search space set configuration to schedule SS occasions to monitor for the DCI format 0_3 for the set of cells .Attorney Docket No . 30164 / 104102Ref . No . P71621WO118 . The apparatus of claim 17 , wherein, when the scheduling cell is not included in the set of cells , the UE capability information indicates the search space set configuration is to be received from a serving cell in the set of cells .

19. The apparatus of claim 18 , wherein the UE capability information indicates the serving cell in the set of cells comprises one of a) a serving cell in the set of cells having a lowest subcarrier spacing (SCS ) b) a serving cell in the set of cells having a highest SCS, c) a serving cell in the set of cells having an SCS that is not higher than an SCS of the scheduling cell, or d) a serving cell in the set of cells having an SCS that is not lower than the SCS of the scheduling cell .20 . The apparatus of claim 17 , wherein, when the scheduling cell is included in the set of cells , the UE capability information indicates the search space set configuration is to be received from the scheduling cell and a serving cell in the set of cells .

Images