Systems, methods, and devices for signaling enhancements for DCI-based multi-cell scheduling

Abstract

The techniques described herein can include solutions for signaling enhancements for communications scheduled by DCI. For example, solutions include scheduling multiple channels for multiple cells with a single DCI. For example, enhanced signaling DCI can include fields that address components of scheduling multiple physical uplink control channels (PUSCHs) or physical downlink shared channels (PDSCHs) for each cell. For example, enhanced signaling DCI can include resource scheduling, subcarrier spacing (SCS), and band type information for each channel of each cell. In some examples, a primary cell can transmit the enhanced signaling DCI to a user equipment (UE). The UE can communicate messages with multiple cells via multiple channels based on the signaling enhanced DCI.

Description

Attorney Docket No.: 106842241940 (P69626WO1)SYSTEMS, METHODS, AND DEVICES FOR SIGNALING ENHANCEMENTS FOR DCI-BASED MULTI-CELL SCHEDULINGCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 700,318, filed September 27, 2024, the content of which is herein incorporated by reference in its entirety for all purposes.FIELD

[0002] This disclosure relates to wireless communication networks and mobile device capabilities.BACKGROUND

[0003] Wireless communication networks and wireless communication services are becoming increasingly dynamic, complex, and ubiquitous. For example, some wireless communication networks can be developed to implement fourth generation (4G), fifth generation (5G) or new radio (NR) technology. Such technology can include solutions for scheduling communications between multiple devices.BRIEF DESCRIPTION OF THE DRAWINGS

[0004] The present disclosure will be readily understood and enabled by the detailed description and accompanying figures of the drawings. Like reference numerals can designate like features and structural elements. Figures and corresponding descriptions are provided as non-limiting examples of aspects, implementations, etc., of the present disclosure, and references to "an" or “one” aspect, implementation, etc., may not necessarily refer to the same aspect, implementation, etc., and can mean at least one, one or more, etc.

[0005] Figure 1 is a diagram of an example of an overview according to one or more implementations described herein.

[0006] Figure 2 is a diagram of an example network according to one or more implementations described herein.

[0007] Figure 3 is a diagram of an example process for signaling enhancements for downlink control information (DCI) based multi-cell scheduling according to one or more implementations described herein.

[0008] Figure 4 is a diagram of an example for signaling enhancements for DCI-based14903-6717-3736, v. 1Attorney Docket No.: 106842241940 (P69626WO1) multi-cell scheduling according to one or more implementations described herein.

[0009] Figure 5 is a diagram of an example for signaling enhancements for DCI-based multi-cell scheduling according to one or more implementations described herein.

[0010] Figure 6 is a diagram of an example of components of a device according to one or more implementations described herein.

[0011] Figure 7 is a diagram of example interfaces of baseband circuitry according to one or more implementations described herein.

[0012] Figure 8 is a block diagram illustrating components, according to one or more implementations described herein, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.

[0013] Figure 9 is a diagram of an example process for signaling enhancements for DCI-based multi-cell scheduling according to one or more implementations described herein.

[0014] Figure 10 is a diagram of an example process for signaling enhancements for DCI-based multi-cell scheduling according to one or more implementations described herein.

[0015] Figure 11 is a diagram of an example process for signaling enhancements for DCI-based multi-cell scheduling according to one or more implementations described herein.DETAILED DESCRIPTION

[0016] The following detailed description refers to the accompanying drawings. Like reference numbers in different drawings can identify the same or similar features, elements, operations, etc. Additionally, the present disclosure is not limited to the following description as other implementations can be utilized, and structural or logical changes made, without departing from the scope of the present disclosure.

[0017] Telecommunication networks can include user equipment (UEs) capable of communicating with base stations and / or other network access nodes. UEs and base stations can implement various techniques and communications standards for enabling UEs and base stations to discover one another, establish and maintain connectivity, and exchange information in an ongoing manner. Objectives of such techniques can include supporting signaling enhancements for DCI-based multi-cell scheduling. For example, the information and instructions can support receiving and implementing DCI that scheduled multiple communications for multiple cells.

[0018] UEs can send physical uplink shared channel (PUSCH) messages and receive physical downlink shared channel (PDSCH) messages with multiple cells. Cells can be an area of service coverage, and can include a single base station, or a base station can include multiple24903-6717-3736, v. 1Attorney Docket No.: 106842241940 (P69626WO1) cells. To instruct UEs to communicate PUSCH / PDSCH messages with base stations (e.g., cells), a serving base station can schedule the channels for communications by indicating downlink control information (DCI). DCI can indicate information for the UE to be able to successfully communicate with one or more base stations, such as timing, resources, and other signaling parameters.

[0019] One or more of the techniques described herein address signaling enhancements for communications scheduled by DCI by providing solutions for scheduling multiple PUSCHs / PDSCHs for multiple base stations with a single DCI. For example, enhanced signaling DCI can include parameters that address multiple PUSCHs / PDSCHs for each cell, such as cell scheduling for multiple cells, and resource scheduling for multiple PUSCHs / PDSCHs. Using a single DCI to schedule multiple communications and cells can result in reduced overhead and power consumption, as well as increased scheduling efficiency.

[0020] Figure 1 is a diagram of an example of an overview 100 according to one or more implementations described herein. UE 110 can communicate with multiple base stations 120 (e.g., cells, network entities). For example, UE 110 can communicate with primary base station 120-1, secondary base station 120-2, and secondary base station 120-3. In some examples, each base station 120 can be an example of a cell, each base station can include multiple cells, or both.

[0021] Primary base station 120-1, which could be a serving or source base station, can transmit multi-cell and multi-channel scheduling DCI 130 (e.g., DCI 130) to UE 110. DCI 130 can include configuration information for scheduling multiple channels, such as PUSCHs, PDSCHs, or both, for base stations 120 (e.g., multiple cells). Such channels can be scheduling with varying subcarrier spacings (SCSs). Rather than a single DCI 130 scheduling a single PUSCH / PDSCH, DCI 130 can schedule multiple PDSCHs / PUSCHs for multiple base stations 120 (e.g., cells). For example, each base station 120 can have multiple associated PDSCHs / PUSCHs. In some examples, DCI 130 can be formatted with a first format (e.g., DCI 0 3) for PUSCH scheduling and formatted with a second format (e.g., DCI 1 3) for PDSCH scheduling.

[0022] To schedule multiple PUSCHs / PDSCHs for multiple base stations 120, DCI 130 can include various parameters or configuration information. For example, DCI 130 can include multiple SCSs and carrier configurations for multiple base stations 120 being co-scheduled by DCI 130. In some examples, DCI 130 can include configuration information that schedules multiple messages 140 with different SCSs (e.g., PDSCHs, PUSCHs) for multiple base stations 120 as part of various fields of DCI 130. DCI 130 fields can include scheduled cell set indicator, scheduled cells indicator, time-domain resource allocation (TDRA) field, new data indicator34903-6717-3736, v. 1Attorney Docket No.: 106842241940 (P69626WO1) field, redundancy field, additional fields, or a combination thereof.

[0023] By scheduling multiple PUSCHs / PDSCHs for multiple base stations 120, flexibility of communication can be increased and resource overhead can be decreased. For example, primary base station 120-1 can use fewer resources to communicate configuration information, and UE 110 can use fewer resources to receive and decode DCI 130.

[0024] UE 210 can communicate multiple messages 140, such as messages with different SCSs, associated with base stations 120. Messages 140 can include multiple PDSCH / PUSCH communications according to the channels scheduled by DCI 130. UE 110 can receive DCI 130, and based on the information of DCI 130, communicate one or more messages 140 with multiple base stations 120. For example, UE 110 can communicate messages 140-1 with primary base station 120-1, messages 140-2 with secondary base station 120-2, and messages 140-3 with secondary base station 140-3.

[0025] Figure 2 is an example network 200 according to one or more implementations described herein. Example network 200 can include UEs 210, 210-2, etc. (referred to collectively as “UEs 210” and individually as “UE 210”), a radio access network (RAN) 220, a core network (CN) 230, application servers 240, and external networks 250.

[0026] The systems and devices of example network 200 can operate in accordance with one or more communication standards, such as 2nd generation (2G), 3rd generation (3G), 4th generation (4G) (e.g., long-term evolution (LTE)), and / or 5th generation (5G) (e.g., new radio (NR)) communication standards of the 3rd generation partnership project (3GPP). Additionally, or alternatively, one or more of the systems and devices of example network 200 can operate in accordance with other communication standards and protocols discussed herein, including future versions or generations of 3GPP standards (e.g., sixth generation (6G) standards, seventh generation (7G) standards, etc.), institute of electrical and electronics engineers (IEEE) standards (e.g., wireless metropolitan area network (WMAN), worldwide interoperability for microwave access (WiMAX), etc.), and more.

[0027] As shown, UEs 210 can include smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more wireless communication networks). Additionally, or alternatively, UEs 210 can include other types of mobile or non-mobile computing devices capable of wireless communications, such as personal data assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, etc. In some implementations, UEs 210 can include internet of things (loT) devices (or loT UEs) that can comprise a network access layer designed for low-power loT applications utilizing short-lived UE connections. Additionally, or alternatively, an loT UE can utilize one or more types of technologies, such as machine-to-44903-6717-3736, v. 1Attorney Docket No.: 106842241940 (P69626WO1) machine (M2M) communications or machine-type communications (MTC) (e.g., to exchanging data with an MTC server or other device via a public land mobile network (PLMN)), proximitybased service (ProSe) or device-to-device (D2D) communications, sensor networks, loT networks, and more. Depending on the scenario, an M2M or MTC exchange of data can be a machine-initiated exchange, and an loT network can include interconnecting loT UEs (which can include uniquely identifiable embedded computing devices within an Internet infrastructure) with short-lived connections. In some scenarios, loT UEs can execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the loT network.

[0028] UEs 210 can communicate and establish a connection with one or more other UEs 210 via one or more wireless channels 212, each of which can comprise a physical communications interface / layer. The connection can include an M2M connection, MTC connection, D2D connection, SL connection, etc. The connection can involve a PC5 interface. In some implementations, UEs 210 can be configured to discover one another, negotiate wireless resources between one another, and establish connections between one another, without intervention or communications involving RAN node 222 or another type of network node. In some implementations, discovery, authentication, resource negotiation, registration, etc., can involve communications with RAN node 222 or another type of network node.

[0029] UEs 210 can use one or more wireless channels 212 to communicate with one another. As described herein, UE 210 can communicate with RAN node 222 to request SL resources. RAN node 222 can respond to the request by providing UE 210 with a dynamic grant (DG) or configured grant (CG) regarding SL resources. A DG can involve a grant based on a grant request from UE 210. A CG can involve a resource grant without a grant request and can be based on a type of service being provided (e.g., services that have strict timing or latency requirements). UE 210 can perform a clear channel assessment (CCA) procedure based on the DG or CG, select SL resources based on the CCA procedure and the DG or CG; and communicate with another UE 210 based on the SL resources. The UE 210 can communicate with RAN node 222 using a licensed frequency band and communicate with the other UE 210 using an unlicensed frequency band.

[0030] UEs 210 can communicate and establish a connection with (e.g., be communicatively coupled) with RAN 220, which can involve one or more wireless channels 214-1 and 214-2, each of which can comprise a physical communications interface / layer. In some implementations, a UE can be configured with dual connectivity (DC) as a multi-radio access technology (multi-RAT) or multi-radio dual connectivity (MR-DC), where a multiple receive and transmit (Rx / Tx) capable UE can use resources provided by different RAN network nodes54903-6717-3736, v. 1Attorney Docket No.: 106842241940 (P69626WO1)(e.g., RAN network nodes 222-1 and 222-2) that can be connected via non-ideal backhaul (e.g., where one network node provides NR access and the other network node provides either E- UTRA for LTE or NR access for 5G). In such a scenario, one network node can operate as a master node (MN) and the other as the secondary node (SN). The MN and SN can be connected via a network interface, and at least the MN can be connected to the CN 230. Additionally, at least one of the MN or the SN can be operated with shared spectrum channel access, and functions specified for UE 210 can be used for an integrated access and backhaul mobile termination (IAB-MT). Similar for UE 210, the IAB-MT can access the network using either one network node or using two different nodes with enhanced dual connectivity (EN-DC) architectures, new radio dual connectivity (NR-DC) architectures, or the like. In some implementations, a base station (as described herein) can be an example of network RAN network nodes.

[0031] As shown, UE 210 can also, or alternatively, connect to access point (AP) 216 via connection interface 218, which can include an air interface enabling UE 210 to communicatively couple with AP 216. AP 216 can comprise a wireless local area network (WLAN), WLAN node, WLAN termination point, etc. The connection 214 can comprise a local wireless connection, such as a connection consistent with any IEEE 702.11 protocol, and AP 216 can comprise a wireless fidelity (Wi-Fi®) router or other AP. While not explicitly depicted in Fig. 2, AP 216 can be connected to another network (e.g., the Internet) without connecting to RAN 220 or CN 230. In some scenarios, UE 210, RAN 220, and AP 216 can be configured to utilize LTE- WLAN aggregation (LWA) techniques or LTE WLAN radio level integration with IPsec tunnel (LWIP) techniques. LWA can involve UE 210 in RRC CONNECTED being configured by RAN 220 to utilize radio resources of LTE and WLAN. LWIP can involve UE 210 using WLAN radio resources (e.g., connection interface 218) via IPsec protocol tunneling to authenticate and encrypt packets (e.g., Internet Protocol (IP) packets) communicated via connection interface 218. IPsec tunneling can include encapsulating the entirety of original IP packets and adding a new packet header, thereby protecting the original header of the IP packets.

[0032] RAN 220 can include one or more RAN nodes 222-1 and 222-2 (referred to collectively as RAN nodes 222, and individually as RAN node 222) that enable channels 214-1 and 214-2 to be established between UEs 210 and RAN 220. A RAN node 222 can be a base station and may be referred to herein as base station 222. RAN nodes 222 can include network access points configured to provide radio baseband functions for data and / or voice connectivity between users and the network based on one or more of the communication technologies described herein (e.g., 2G, 3G, 4G, 5G, WiFi®, etc.). As examples therefore, a RAN node can be64903-6717-3736, v. 1Attorney Docket No.: 106842241940 (P69626WO1) an E-UTRAN Node B (e.g., an enhanced Node B, eNodeB, eNB, 4G base station, etc.), a next generation base station (e.g., a 5G base station, NR base station, next generation eNBs (gNB), etc.). RAN nodes 222 can include a roadside unit (RSU), a transmission reception point (TRxP or TRP), and one or more other types of ground stations (e.g., terrestrial access points). In some scenarios, RAN node 222 can be a dedicated physical device, such as a macrocell base station, and / or a low power (LP) base station for providing femtocells, picocells or the like having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

[0033] Some or all of RAN nodes 222, or portions thereof, can be implemented as one or more software entities running on server computers as part of a virtual network, which can be referred to as a centralized RAN (CRAN) and / or a virtual baseband unit pool (vBBUP). In these implementations, the CRAN or vBBUP can implement a RAN function split, such as a packet data convergence protocol (PDCP) split wherein radio resource control (RRC) and PDCP layers can be operated by the CRAN / vBBUP and other Layer 2 (L2) protocol entities can be operated by individual RAN nodes 222; a media access control (MAC) / physical (PHY) layer split wherein RRC, PDCP, radio link control (RLC), and MAC layers can be operated by the CRAN / vBBUP and the PHY layer can be operated by individual RAN nodes 222; or a “lower PHY” split wherein RRC, PDCP, RLC, MAC layers and upper portions of the PHY layer can be operated by the CRAN / vBBUP and lower portions of the PHY layer can be operated by individual RAN nodes 222. This virtualized framework can allow freed-up processor cores of RAN nodes 222 to perform or execute other virtualized applications.

[0034] In some implementations, an individual RAN node 222 can represent individual gNB-distributed units (DUs) connected to a gNB-control unit (CU) via individual Fl or other interfaces. In such implementations, the gNB-DUs can include one or more remote radio heads or radio frequency (RF) front end modules (RFEMs), and the gNB-CU can be operated by a server (not shown) located in RAN 220 or by a server pool (e.g., a group of servers configured to share resources) in a similar manner as the CRAN / vBBUP. Additionally, or alternatively, one or more of RAN nodes 222 can be next generation eNBs (i.e., gNBs) that can provide evolved universal terrestrial radio access (E-UTRA) user plane and control plane protocol terminations toward UEs 210, and that can be connected to a 5G core network (5GC) 230 via an NG interface.

[0035] Any of the RAN nodes 222 can terminate an air interface protocol and can be the first point of contact for UEs 210. In some implementations, any of the RAN nodes 222 can fulfill various logical functions for the RAN 220 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. UEs 210 can be configured74903-6717-3736, v. 1Attorney Docket No.: 106842241940 (P69626WO1) to communicate using orthogonal frequency-division multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 222 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an OFDMA communication technique (e.g., for downlink communications) or a single carrier frequency-division multiple access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink (SL) communications), although the scope of such implementations may not be limited in this regard. The OFDM signals can comprise a plurality of orthogonal subcarriers.

[0036] In some implementations, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 222 to UEs 210, and uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid (e.g., a resource grid or time-frequency resource grid) that represents the physical resource for downlink in each slot. Such a timefrequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest timefrequency unit in a resource grid is denoted as a resource element. Each resource grid comprises resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block can comprise a collection of resource elements (REs); in the frequency domain, this can represent the smallest quantity of resources that currently can be allocated. There are several different physical downlink channels that are conveyed using such resource blocks.

[0037] Further, RAN nodes 222 can be configured to wirelessly communicate with UEs 210, and / or one another, over a licensed medium (also referred to as the “licensed spectrum” and / or the “licensed band”), an unlicensed shared medium (also referred to as the “unlicensed spectrum” and / or the “unlicensed band”), or combination thereof. A licensed spectrum can correspond to channels or frequency bands selected, reserved, regulated, etc., for certain types of wireless activity (e.g., wireless telecommunication network activity), whereas an unlicensed spectrum can correspond to one or more frequency bands that are not restricted for certain types of wireless activity. Whether a particular frequency band corresponds to a licensed medium or an unlicensed medium can depend on one or more factors, such as frequency allocations determined by a public-sector organization (e.g., a government agency, regulatory body, etc.) or frequency84903-6717-3736, v. 1Attorney Docket No.: 106842241940 (P69626WO1) allocations determined by a private-sector organization involved in developing wireless communication standards and protocols, etc.

[0038] The PDSCH can carry user data and higher layer signaling to UEs 210. The physical downlink control channel (PDSCH) can carry information about the transport format and resource allocations related to the PDSCH channel, among other things. The PDSCH can also inform UEs 210 about the transport format, resource allocation, and hybrid automatic repeat request (HARQ) information related to the uplink shared channel. Typically, downlink scheduling (e.g., assigning control and shared channel resource blocks to UE 210 within a cell) can be performed at any of the RAN nodes 222 based on channel quality information fed back from any of UEs 210. The downlink resource assignment information can be sent on the PDSCH used for (e.g., assigned to) each of UEs 210.

[0039] One or more of the techniques, described herein, can enable UE 210 to communicate with multiple base stations 222, or cells, using multiple PUSCHs / PDSCHs scheduled by a single DCI. These and many other features and aspects of the techniques described herein are presented below with reference to remaining Figures.

[0040] The RAN nodes 222 can be configured to communicate with one another via interface 223. In implementations where the system is an LTE system, interface 223 can be an X2 interface. In NR systems, interface 223 can be an Xn interface. The X2 interface can be defined between two or more RAN nodes 222 (e.g., two or more eNBs / gNBs or a combination thereof) that connect to evolved packet core (EPC) or CN 230, or between two eNBs connecting to an EPC. The RAN nodes 222 can be configured to communicate with the CN 230 via various interfaces, such as physical interfaces, including interface 224, interface 226, and interface 228.

[0041] In some implementations, the X2 interface can include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U can provide flow control mechanisms for user data packets transferred over the X2 interface and can be used to communicate information about the delivery of user data between eNBs or gNBs. For example, the X2-U can provide specific sequence number information for user data transferred from a master eNB (MeNB) to a secondary eNB (SeNB); information about successful in sequence delivery of PDCP packet data units (PDUs) to a UE 210 from an SeNB for user data; information of PDCP PDUs that were not delivered to a UE 210; information about a current minimum desired buffer size at the SeNB for transmitting to the UE user data; and the like. The X2-C can provide intra-LTE access mobility functionality (e.g., including context transfers from source to4903-6717-3736, v. 1Attorney Docket No.: 106842241940 (P69626WO1) target eNBs, user plane transport control, etc.), load management functionality, and inter-cell interference coordination functionality.

[0042] As shown, RAN 220 can be connected (e.g., communicatively coupled) to CN 230. CN 230 can comprise a plurality of network elements 232, which are configured to offer various data and telecommunications services to customers / subscribers (e.g., users of UEs 210) who are connected to the CN 230 via the RAN 220. In some implementations, CN 230 can include an evolved packet core (EPC), a 5G CN, and / or one or more additional or alternative types of CNs. The components of the CN 230 can be implemented in one physical node or separate physical nodes including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some implementations, network function virtualization (NFV) can be utilized to virtualize any or all the above-described network node roles or functions via executable instructions stored in one or more computer-readable storage mediums (described in further detail below). A logical instantiation of the CN 230 can be referred to as a network slice, and a logical instantiation of a portion of the CN 230 can be referred to as a network sub-slice. Network Function Virtualization (NFV) architectures and infrastructures can be used to virtualize one or more network functions, alternatively performed by proprietary hardware, onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches. In other words, NFV systems can be used to execute virtual or reconfigurable implementations of one or more EPC components / functions.

[0043] As shown, CN 230, application servers 240, and external networks 250 can be connected to one another via interfaces 234, 236, and 238, which can include IP network interfaces. Application servers 240 can include one or more server devices or network elements (e.g., virtual network functions (VNFs) offering applications that use IP bearer resources with CN 230 (e.g., universal mobile telecommunications system packet services (UMTS PS) domain, LTE PS data services, etc.). Application servers 240 can also, or alternatively, be configured to support one or more communication services (e.g., voice over IP (VoIP) sessions, push-to-talk (PTT) sessions, group communication sessions, social networking services, etc.) for UEs 210 via the CN 230. Similarly, external networks 250 can include one or more of a variety of networks, including the Internet, thereby providing the mobile communication network and UEs 210 of the network access to a variety of additional services, information, interconnectivity, and other network features.

[0044] Figure 3 is a diagram of an example of process 300 for signaling enhancements for DCI-based multi-cell scheduling according to one or more implementations described herein. UE104903-6717-3736, v. 1Attorney Docket No.: 106842241940 (P69626WO1)210 can receive multi-cell and multi-channel scheduling DCI 320 (e.g., DCI 320) from primary base station 222-1, which can be an example of a serving or source base station. Each base station 222 can be an example of a cell, include multiple cells, or a combination thereof. DCI 320 can include scheduling information for multiple PUSCHs / PDSCHs, and UE 210 can communicate PUSCH / PDSCH messages 330 with varying SCSs based on DCI 320.

[0045] For example, DCI 320 can be a first format (e.g., 0 3) that schedules multiple PUSCHs (e.g., PUSCH messages) for multiple cells (e.g., base stations 222), or can be a second format (e.g., 1 3) that schedule multiple PDSCHs (e.g., PDSCH messages) for multiple cells. In some examples, DCI 320 can include multiple fields 340. For example, DCI 320 can include field 340-1 that describes a scheduled cell set indicator field, field 340-2 that describes a scheduled cells indicator field, field 340-3 that describes a TDRA field, field 340-4 that describes a new data indicator field, field 340-5 that describes a redundancy version field, or a combination thereof.

[0046] Each field 340 can include information for scheduling multiple PUSCHs / PDSCHs. For example, fields 340 can include parameters that indicate information for communicating PUSCHs / PDSCHs. In some examples, DCI 320 can include multiple SCSs (e.g., 15khz, 30 khz, etc.) and carrier types (frequency division duplex (FDD), time division duplex (TDD)) for multiple base stations 222 being co-scheduled by DCI 320. For example, DCI 320 can configure an SCS of 15khz for secondary base station 222-2, and an SCS of 30khz for secondary base station 222-3. In another example, DCI 320 can configure an SCS of 15khz for a first PUSCH of a secondary base station 222-2, and an SCS of 30khz for a second PUSCH of a secondary base station 222-2.

[0047] UE 210 can communicate PUSCH / PDSCH messages 330 with base stations 222 according to DCI 320. For example, UE 110 can communicate PUSCH / PDSCH messages 330-1 with primary base station 222-1, PUSCH / PDSCH messages 330-2 with secondary base station 222-2, and PUSCH / PDSCH messages 330-3 with secondary base station 222-3.

[0048] Fig. 4 is a diagram of an example of process 400 for signaling enhancements for DCI- based multi-cell scheduling according to one or more implementations described herein. Process 400 can be implemented by UE 210, primary base station 222-1, secondary base station 222-2, secondary base station 222-3, or a combination thereof. Base stations 222 can be examples of cells, include multiple cells, or both. In some implementations, some or all of process 400 can be performed by one or more other systems or devices, including one or more of the devices of Fig. 2. Additionally, process 400 can include one or more fewer, additional, differently ordered and / or arranged operations than those shown in Fig. 4. In some implementations, some or all of114903-6717-3736, v. 1Attorney Docket No.: 106842241940 (P69626WO1) the operations of process 400 can be performed independently, successively, simultaneously, etc., of one or more of the other operations of process 400. As such, the techniques described herein are not limited to a number, sequence, arrangement, timing, etc., of the operations or processes depicted in Fig. 4.

[0049] Process 400 can include an RRC message (at 410). For example, primary base station 222-1 can transmit the RRC message to UE 210. In some examples, the RRC message can be a semi-static message that schedules monitoring occasions for UE 210. The monitoring occasions can include time intervals for monitoring for DCI. In some examples, the RRC message can include scheduling information for channels, messages, etc. In some examples, DCI can further define the scheduling information of the RRC message.

[0050] In some examples, the RRC message, or another message, can indicate SCS and band types (e.g., as part of configuration information). For example, one or more SCSs, band types, or both, can be associated with one or more sets of a cells. The SCSs and band types can be the same or different for the cells of the cell sets. For example, cells of a first set can have different SCSs / band types, and cells of a second set can have the same SCSs / band types. Process 400 can include monitoring for DCI (at 420). For example, UE 210 can monitor for DCI (e.g., multi-cell and multi-channel scheduling DCI) during the monitoring occasions schedule by the RRC message.

[0051] Process 400 can include indicating multi-cell and multi-message scheduling DCI (e.g., DCI) (at 430). For example, primary base station 222-1 can transmit DCI to UE 210. DCI can include information (e.g., scheduling information) for multi-channel (e.g., PUSCH / PSCCH) scheduling for multiple base stations 222 (e.g., cells). In some examples, DCI (e.g., of format 0 3) can schedule multiple PUSCH message for UE 210 and primary base station 222-1, secondary base station 222-2, and secondary base station 222-3. In some examples, DCI (e.g., of format 1 3) can schedule multiple PDSCH messages for UE 210 and base stations 222.

[0052] Multi-cell and multi-channel scheduling DCI can include multiple fields with multiple parameters. For example, a scheduling cell set indicator field can indicate one or more sets of cells (e.g., base stations 222). Each set can include one or more cells, and each set, each cell of a set, and each channel can be associated with a SCS and band type (e.g., TDD, FDD). The SCS and band type associated with each set, cell, or channel can be the same or different than the SCS and band type of another set, cell, or channel. In some examples, SCS and band type for each PDSCH / PDSCH for each cell can be the same or different.

[0053] In some examples, SCS and band type can be different for different sets. For example, secondary base station 222-2 and secondary base station 222-3 can be in the same set124903-6717-3736, v. 1Attorney Docket No.: 106842241940 (P69626WO1) or different sets. When in the same set, secondary base station 222-2 and secondary base station 222-3 can be associated with the same SCS and band type. When in different sets, secondary base station 222-2 and secondary base station 222-3 can have the same or different SCS and band type.

[0054] In some examples, when the SCS / band type for a first set are the same, and the SCS / band type for a second set are different, UE 210 can be scheduled with either the first set or the second set. In some examples, UE 210 can be scheduled with the second set, where the SBS / band type are different for one or more cells of the set.

[0055] DCI can include a scheduled cell indicator field that indicates which cells of the one or more sets indicated by the scheduling cell set indicator field are scheduled. For example, the scheduling cell set indicator field can indicate a set that includes base stations 222, primary base station 222-1, secondary base station 222-2. The scheduling cell indicator can indicate that of base stations 222 of the set, primary base station 222-1, secondary base station 222-2 are part of the cell set. In some examples, the scheduling cell indicator can indicate that primary base station 222-1, secondary base station 222-2 are scheduled. In this way, a single DCI can schedule multiple SCSs and band types for multiple base stations 222.

[0056] In some examples, DCI can include a TDRA field that describes one or more entries of a table. Each entry can provide a time domain resource assignment for each bandwidth part of each cell of the scheduled cell set. Each bandwidth part of each cell (e.g., base station 222) can be associate with the same or different SCS and band type.

[0057] DCI can include a new data indictor field, which can indicate whether each PUSCH / PDSCH of each scheduled cell can include new data or repeated data. For example, if primary base station 222-1 and secondary base station 222-2 are scheduled cells indicated by the scheduled cell indicator field, the new data indicator field can indicate information about each PUSCH / PDSCH. In some examples, DCI can include a redundancy version indicator that indicates the redundancy version of each PUSCH / PDSCH of each scheduled cell.

[0058] Process 400 can include determining channel scheduling (at 440). For example, UE 210 can determine, based on the multi-cell and multi-channel scheduling DCI, which PUSCH / PDSCH channels have been scheduled for one or more base stations 222.

[0059] Process 400 can include communicating PUSCH / PDSCH messages (e.g., communications, signaling) according to the DCI. For example, UE 210 can communicate PUSCH / PDSCH signaling (e.g., one or more PUSCH / PDSCH messages) with primary base station 222-1 (at 450), secondary base station 222-2 (at 460), secondary base station 222-3, or a combination thereof (at 470). Each PUSCH / PDSCH message can be transmitted with different or134903-6717-3736, v. 1Attorney Docket No.: 106842241940 (P69626WO1) the same SCS and band type according to the DCI. The PUSCH / PDSCH messages can be scheduled for multiple base stations 222 by a single multi-cell and multi-channel scheduling DCI.

[0060] Fig. 5 is a diagram of an example of process 500 for signaling enhancements for DCI- based multi-cell scheduling according to one or more implementations described herein. Fig. 5 can describe DCI 560 indicated from primary base station 222-1 to UE 210. In some examples, DCI 560 can include fields for scheduling multiple PUSCHs / PDSCHs for multiple base stations 222 (e.g., cells, RAN nodes). Fields can include scheduling cell set indicator 510, scheduled cells indicator 520, time-domain resource allocation (TDRA) 530, new data indicator 540, and redundancy version indicator 550. Fig. 5 can be an example of other Figs., such as Fig. 1 and Fig. 3. In some examples, DCI 560 can include different, more, or fewer fields than described.

[0061] Scheduling cell set indicator 510 can indicate one or more cell sets that include one or more cells (e.g., base stations 222). One or more parameters, which can be higher-layer parameters, can be included as part of scheduling cell set indication 510 for multiple PUSCH / PDSCH and multiple cell scheduling. For example, scheduling cell set indicator 510 can include a first parameter (e.g., MC-DCI-SetofCellsToAddModList-R19), a second parameter (e.g., MC-DCI-SetofCellsToAddModList), or both.

[0062] Scheduling cell set indicator 510 can schedule UE 210 with the first parameter if UE 210 is capable of supporting multiple slot PDSCH / PUSCH scheduling for multiple cells. In some examples, UE 210 can be scheduled with a single parameter. For example, scheduling cell set indicator 510 can include the first parameter or the second parameter. When configured with one parameter, UE 210 may not be configured to decode or receive another parameter. For example, UE 210 can be configured with the first parameter and not the second parameter or can be configured with the second parameter and not the first parameter.

[0063] In some examples, scheduling cell set indicator 510 can include both the first parameter and the second parameter. In such an example, the DCI can indicate a cell set of the first parameter. That is, when both parameters are included, the first parameter can be the implemented as the default. UE 210 can interpret and be configured by the first parameter, and may not be configured by the second parameter.

[0064] Scheduling cell set indicator 510 can be interpreted (e.g., by UE 210), as a set of bits (log2Nset). The number of bits can be determined by the number of cells (Nset). The number of cells can be configured by the first parameter, or when the first parameter is not present, the second parameter. The bits can identify one or more scheduled cell sets according to a table. The table can include one or more entries, where each entry indicates an ID associated with each144903-6717-3736, v. 1Attorney Docket No.: 106842241940 (P69626WO1) candidate cell set. The bits can identify one or more IDs of the scheduled cell sets of the list of candidate cell sets. UE 210 can communicate with the identified cells of the cell sets.

[0065] DCI 560 can include scheduled cells indicator 520, which can indicate scheduled cells (e.g., base stations 222) of the cell sets included in scheduling cell set indicator 510. One or more parameters, which can be higher-layer parameters, can be included as part of scheduled cells indicator 520 for multiple PUSCH / PDSCH and multiple cell scheduling. For example, scheduled cells indicator 520 can include a first parameter (e.g., scheduledCellComboList- DCI-0-3-R19, scheduledCellComboList-DCI-l-3-R19), a second parameter (e.g., scheduledCellComboList-DCI-0-3, scheduledCellComboList-DCI-1-3), or both.

[0066] UE 210 can be scheduled with the first parameter of scheduled cells indicator 520 if UE 210 is capable of supporting multiple slot PDSCH / PUSCH scheduling for multiple cells. In some examples, UE 210 can be scheduled with a single param eter-either the first parameter or the second parameter. When configured with one parameter, UE 210 may not be configured to decode or receive another parameter.

[0067] In some examples, scheduled cells indicator 520 can include both the first parameter and the second parameter. In such an example, the scheduled cells indicator 520 can indicate cells according to the first parameter and may not indicate cells according to the second parameter. That is, when both parameters are included, the first parameter can be the implemented as the default. When scheduled cells indicator 520 includes the first parameter of scheduled cells indicator 520, the scheduled cells indicated can be associated with thee scheduled cell sets of the first parameter of scheduling cell set indicator 510.

[0068] In some examples, UE 210 can interpret scheduled cells indicator 520, when the second parameter is configured, as 0 bits. When the first parameter is configured, a set of bits (log2lur) can indicate the scheduled cells of the scheduled set according to a table. The table can include one or more entries, where each entry is associated with a cell set. The entries, or records, can be associated with identifiers (IDs). Each entry can indicate a cell combination associated with the configured cell set.

[0069] The number of bits (log2li r ) can depend on the number of entries (IUL) of the first parameter. The entries of the table can indicate a cell combination associated with the configured cell set. The bits of the first parameter can identify a table entry, which identifies the scheduled cells. In some examples, a single entry may be configured. In such examples, the first parameter and second parameter can indicate the singular entry using the same number of bits.

[0070] DCI 560 can include time-domain resource allocation (TDRA) 530. TDRA 530 can identify resource assignments associated with one or more cells. One or more parameters, which154903-6717-3736, v. 1Attorney Docket No.: 106842241940 (P69626WO1) can be higher-layer parameters, can be included as part of TDRA 530 for multiple PUSCH / PDSCH and multiple cell scheduling. For example, TDRA 530 can include a first parameter (e.g., tdra-Field!ndexListDCI-0-3-R19, FieldIndexListDCI-l-3-R19), a second parameter (e.g., FieldIndexListDCI-0-3, FieldIndexListDCI-1-3), or both.

[0071] UE 210 can be scheduled with the first parameter of TDRA 530 if UE 210 is capable of supporting multiple slot PDSCH / PUSCH scheduling for multiple cells. In some examples, UE 210 can be scheduled with a single param eter-either the first parameter or the second parameter. When configured with one parameter, UE 210 may not be configured to decode or receive another parameter. In some examples, when scheduling cell set indicator 510 includes the first parameter, TDRA 530 can include the first parameter.

[0072] In some examples, scheduled cells indicator 520 can include both the first parameter and the second parameter. In such an example, the scheduled cells indicator 520 can indicate cells according to the first parameter and may not indicate cells according to the second parameter. That is, when both parameters are included, the first parameter can be the implemented as the default.

[0073] When the first parameter is configured, a set of bits (log2(lTDRA)) can indicate one or more entries of a table. The number of bits (log2(lTDRA)) can depend on the number of entries (ITDRA) of the first parameter. The table can include one or more entries, where each entry indicates TDRA for each scheduled cell combination. Each entry of the table can include a TDRA index for each bandwidth part of each cell of the scheduled cell set. Within the table, TDRA indexes for all cells are ordered according to an ascending order of a serving cell index (e.g., serving primary base station 222-1), and TDRA indexes for all bandwidth parts of a cell are ordered according to an ascending order of the bandwidth part IDs. In some examples, the bandwidth part IDs can be associated with the first parameter.

[0074] DCI 560 can include new data indicator 540, which indicates whether each PUSCH / PDSCH includes new data. Aspects of new data indicator 540 can be applied when UE 210 supports multiple PUSCH / PDSCH scheduling for multiple cells. In some examples, new data indicator 540 can include a parameter (e.g., puschTimeDomainAllocationListForMultiPUSCH), which can be a higher-layer parameter.

[0075] In some examples, new data indicator 540 can include a number of bits divided into blocks. Each block can correspond to a cell and can be ordered according to the serving cell index in ascending order. The first block can correspond to the new data indicator 540 for the cell with the smallest serving cell index.

[0076] Each block be comprised of a number of bits that corresponds to the number of164903-6717-3736, v. 1Attorney Docket No.: 106842241940 (P69626WO1) scheduled PUSCH / PDSCH messages scheduled per cell. For example, if 8 PUSCHs are scheduled for a cell, the associated block can include 8 bits. Each bit can correspond to a scheduled PUSCH / PDSCH. For example, a bit with a first bit value (e.g., 0) can indicate that the corresponding PUSCH (or PDSCH) is not new data, but is data that has been previously transmitted and is being retransmitted. A bit with a second bits value (e.g., 1) can indicate that the corresponding PUSCH (or PDSCH) is new data.

[0077] DCI 560 can include redundancy version indicator 550, which can indicate the number of redundant versions of each PUSCH / PDSCH for each scheduled cell. In some examples, redundancy version indicator 550 can include a first parameter (e.g., numberOfBitsForRV-DCI-0-3-R19, numberOfBitsForRV-DCI-l-3-R19), or a second parameter (e.g., numberOfBitsForRV-DCI-1-3, numberOfBitsForRV-DCI-0-3), which can be higher-layer parameters. Aspects of redundancy version indicator 550, such as the first parameter, can be applied when UE 210 supports multiple PUSCH / PDSCH scheduling for multiple cells.

[0078] In some examples, redundancy version indicator 550 can include a number of bits divided into blocks. Each block can correspond to a cell and can be ordered according to the serving cell index in ascending order. The first block can correspond to the redundancy version indicator 550 for the cell with the smallest serving cell index.

[0079] Each block can include a set of bits (e.g., 0, 1, or 2 bits) indicating the number of redundant versions scheduled for each PUSCH / PDSCH. As each cell, which corresponds to a block, can include multiple PUSCHs / PDSCHs, each block can include multiple sets of bits that correspond to each PUSCH / PDSCH. For example, if each PUSCH / PDSCH is scheduled to have 4 redundant versions, and there are 8 PUSCHs / PDSCHs scheduled for the cell, the block can have 16 bits. In another example, if a cell has 4 PUSCHs / PDSCHs, each scheduled with 2 redundancy versions, and 2 PUSCHs / PDSCHs scheduled with 3 redundancy versions each, the block can have 8 bits.

[0080] Figure 6 is a diagram of an example of components of a device according to one or more implementations described herein. In some implementations, the device 600 can include application circuitry 602, baseband circuitry 604, RF circuitry 606, front-end module (FEM) circuitry 608, one or more antennas 610, and power management circuitry (PMC) 612 coupled together at least as shown. In some implementations, device 600 can include fewer elements (e.g., a RAN node may not utilize application circuitry 602, and can instead include a processor / controller to process data received from a core network. In some implementations, device600 can include additional elements such as, for example, memory / storage, display, camera, sensor (including one or more temperature sensors, such as a single temperature sensor,174903-6717-3736, v. 1Attorney Docket No.: 106842241940 (P69626WO1) a plurality of temperature sensors at different locations in device 600, etc.), or input / output (I / O) interface. In other implementations, the components described below can be included in more than one device (e.g., said circuitries can be separately included in more than one device for cloud-RAN (C-RAN) implementations).

[0081] The application circuitry 602 can include one or more application processors. For example, the application circuitry 602 can include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) can include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors can be coupled with or can include memory / storage and can be configured to execute instructions stored in the memory / storage to enable various applications or operating systems to run on the device 600. In some implementations, processors of application circuitry 602 can process data packets received from a core network.

[0082] The baseband circuitry 604 can include circuitry such as, but not limited to, one or more single-core or multi-core processors. Baseband circuitry 604 can include one or more baseband processors or control logic to process baseband signals received from a receive signal path of RF circuitry 606 and to generate baseband signals for a transmit signal path of RF circuitry 606. Baseband circuitry 604 can interface with application circuitry 602 for generation and processing of the baseband signals and for controlling operations of RF circuitry 606. For example, in some implementations, baseband circuitry 604 can include a 3G baseband processor 604A, a 4G baseband processor 604B, a 5G baseband processor 604C, or other baseband processor(s) 604D for other existing generations, generations in development or to be developed in the future (e.g., 5G, 6G, 7G, etc.). Baseband circuitry 604 (e.g., one or more of baseband processors 604A-D) can handle various radio control functions that enable communication with one or more radio networks via RF circuitry 606. In other implementations, some or all of the functionality of baseband processors 604 A-D can be included in modules stored in memory 604G and executed via a central processing unit (CPU) 604E. The radio control functions can include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some implementations, modulation / demodulation circuitry of baseband circuitry 604 can include Fast-Fourier Transform (FFT), precoding, or constellation mapping / de-mapping functionality. In some implementations, encoding / decoding circuitry of baseband circuitry 604 can include convolution, tail-biting convolution, turbo, Viterbi, or low- density parity check (LDPC) encoder / decoder functionality. Implementations of modulation / demodulation and encoder / decoder functionality are not limited to these examples and can include other suitable functionality in other implementations.184903-6717-3736, v. 1Attorney Docket No.: 106842241940 (P69626WO1)

[0083] In some implementations, memory 604G can receive and / or store information and instructions for enabling UE 210, and / or one or more components thereof, to support signaling enhancements for DCI-based multi-cell scheduling. For example, the information and instructions can cause and / or enable UE 210 to receive DCI that scheduled multiple PUSCH / PDSCH messages for multiple cells / base stations 222. In some examples, the DCI can include SCS and band type for each PUSCH / PDSCH. These and many other features and examples are described herein.

[0084] In some implementations, the baseband circuitry 604 can include one or more audio digital signal processor(s) (DSP) 604F. The audio DSPs 604F can include elements for compression / decompression and echo cancellation and can include other suitable processing elements in other implementations. Components of the baseband circuitry can be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some implementations. In some implementations, some or all of the constituent components of the baseband circuitry 604 and the application circuitry 602 can be implemented together such as, for example, on a system on a chip (SOC).

[0085] In some implementations, the baseband circuitry 604 can provide for communication compatible with one or more radio technologies. For example, in some implementations, the baseband circuitry 604 can support communication with a NG-RAN, an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN), etc. Implementations in which the baseband circuitry 604 is configured to support radio communications of more than one wireless protocol can be referred to as multi-mode baseband circuitry.

[0086] RF circuitry 606 can enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various implementations, RF circuitry 806 can include switches, filters, amplifiers, etc., to facilitate the communication with the wireless network. RF circuitry 606 can include a receive signal path which can include circuitry to down-convert RF signals received from FEM circuitry 608 and provide baseband signals to baseband circuitry 604. RF circuitry 606 can also include a transmit signal path which can include circuitry to up-convert baseband signals provided by baseband circuitry 604 and provide RF output signals to FEM circuitry 608 for transmission.

[0087] In some implementations, the receive signal path of the RF circuitry 606 can include mixer circuitry 606A, amplifier circuitry 606B and filter circuitry 606C. In some implementations, the transmit signal path of RF circuitry 606 can include filter circuitry 606C194903-6717-3736, v. 1Attorney Docket No.: 106842241940 (P69626WO1) and mixer circuitry 606 A. RF circuitry 606 can also include synthesizer circuitry 606D for synthesizing a frequency for use by mixer circuitry 606A of the receive signal path and the transmit signal path. In some implementations, mixer circuitry 606A of the receive signal path can be configured to down-convert RF signals received from FEM circuitry 608 based on the synthesized frequency provided by synthesizer circuitry 606D. Amplifier circuitry 606B can be configured to amplify the down-converted signals and filter circuitry 606C can be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down- converted signals to generate output baseband signals. Output baseband signals can be provided to baseband circuitry 604 for further processing. In some implementations, the output baseband signals can be zero-frequency baseband signals, although this may not be a requirement. In some implementations, mixer circuitry 606A of the receive signal path can comprise passive mixers, although the scope of the implementations is not limited in this respect.

[0088] In some implementations, the mixer circuitry 606A of the transmit signal path can be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 606D to generate RF output signals for the FEM circuitry 608. The baseband signals can be provided by the baseband circuitry 604 and can be filtered by filter circuitry 606C.

[0089] In some implementations, mixer circuitry 606A of the transmit signal path can be configured to up-convert input baseband signals based on the synthesized frequency provided by synthesizer circuitry 606D to generate RF output signals for FEM circuitry 608. The baseband signals can be provided by baseband circuitry 604 and can be filtered by filter circuitry 606C. In some implementations, mixer circuitry 606A of the receive signal path and mixer circuitry 606A of the transmit signal path can include two or more mixers and can be arranged for quadrature down conversion and up conversion, respectively. In some implementations, mixer circuitry 606A of the receive signal path and mixer circuitry 606A of the transmit signal path can include two or more mixers and can be arranged for image rejection. In some implementations, mixer circuitry 606A of the receive signal path and mixer circuitry 606A can be arranged for direct down conversion and direct up conversion, respectively. In some implementations, mixer circuitry 606A of the receive signal path and mixer circuitry 606A of the transmit signal path can be configured for super-heterodyne operation.

[0090] In some implementations, the output baseband signals, and the input baseband signals can be analog baseband signals, although the scope of the implementations is not limited in this respect. In some alternate implementations, the output baseband signals, and the input baseband signals can be digital baseband signals. In these alternate implementations, RF circuitry 606 can204903-6717-3736, v. 1Attorney Docket No.: 106842241940 (P69626WO1) include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and baseband circuitry 604 can include a digital baseband interface to communicate with RF circuitry 606.

[0091] In some dual-mode implementations, a separate radio IC circuitry can be provided for processing signals for each spectrum, although the scope of the implementations is not limited in this respect. In some implementations, the synthesizer circuitry 606D can be a fractional-N synthesizer or a fractional N / N+l synthesizer, although the scope of the implementations is not limited in this respect as other types of frequency synthesizers can be suitable. For example, synthesizer circuitry 606D can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[0092] Synthesizer circuitry 606D can be configured to synthesize an output frequency for use by mixer circuitry 606 A of RF circuitry 606 based on a frequency input and a divider control input. In some implementations, synthesizer circuitry 606D can be a fractional N / N+l synthesizer. In some implementations, frequency input can be provided by a voltage-controlled oscillator (VCO). Divider control input can be provided by either baseband circuitry 604 or the applications circuitry 602 depending on the desired output frequency. In some implementations, a divider control input (e.g., N) can be determined from a look-up table based on a channel indicated by the applications circuitry 602.

[0093] Synthesizer circuitry 606D of RF circuitry 606 can include a divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some implementations, the divider can be a dual modulus divider (DMD), and the phase accumulator can be a digital phase accumulator (DPA). In some implementations, the DMD can be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio. In some example implementations, the DLL can include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these implementations, the delay elements can be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0094] In some implementations, synthesizer circuitry 606D can be configured to generate a carrier frequency as the output frequency, while in other implementations, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some implementations, the output frequency can be a LO frequency (fLO). In some214903-6717-3736, v. 1Attorney Docket No.: 106842241940 (P69626WO1) implementations, RF circuitry 606 can include an in-phase / quadrature (I / Q) / polar converter.

[0095] FEM circuitry 608 can include a receive signal path which can include circuitry configured to operate on RF signals received from one or more antennas 610, amplify the received signals and provide the amplified versions of the received signals to RF circuitry 606 for further processing. FEM circuitry608 can also include a transmit signal path which can include circuitry configured to amplify signals for transmission provided by RF circuitry 606 for transmission by one or more of the one or more antennas 610. In various implementations, the amplification through the transmit or receive signal paths can be done solely in RF circuitry 606, solely in FEM circuitry 608, or in both RF circuitry 606 and FEM circuitry 608.

[0096] In some implementations, the FEM circuitry 608 can include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuitry can include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry can include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 606). The transmit signal path of the FEM circuitry 608 can include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 606), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 610).

[0097] In some implementations, the PMC 612 can manage power provided to the baseband circuitry 604. In particular, PMC 612 can control power-source selection, voltage scaling, battery charging, or direct current (DC) to DC (DC-to-DC) conversion. PMC 612 can often be included when device 600 is capable of being powered by a battery, for example, when device 600 is included in a UE. PMC 612 can increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.

[0098] While Fig. 6 shows PMC 612 coupled only with the baseband circuitry 604, in other implementations, PMC 612 can be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 602, RF circuitry 606, or FEM circuitry 608.

[0099] In some implementations, the PMC 612 can control, or otherwise be part of, various power saving mechanisms of device 600. For example, if device 600 is in an RRC Connected state, where device 600 is still connected to the RAN node as device 600 expects to receive traffic shortly, then device 600 can enter a state known as discontinuous reception mode (DRX) after a period of inactivity. During this state, device 600 can power down for brief intervals of time and thus save power.

[0100] If there is no data traffic activity for an extended period of time, then device 600 can224903-6717-3736, v. 1Attorney Docket No.: 106842241940 (P69626WO1) transition off to an RRC Idle state, where device 600 disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. Device 600 can go into a very low power state and device 600 can perform paging where again device 600 periodically can wake up to listen to the network and then power down again. Device 600 may not receive data in this state; in order to receive data, device 600 can transition back to RRC Connected state.

[0101] An additional power saving mode can allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device 600 can be unreachable to the network and can power down completely. Any data sent during this time can incur a large delay and device 600 can assume the delay is acceptable.

[0102] Processors of application circuitry 602 and processors of baseband circuitry 604 can be used to execute elements of one or more instances of a protocol stack. For example, processors of baseband circuitry 604, alone or in combination, can be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of baseband circuitry 604 can utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers). As referred to herein, Layer 3 can comprise a radio resource control layer. As referred to herein, Layer 2 can comprise a medium access control layer, a radio link control layer, and a packet data convergence protocol layer, described in further detail below. As referred to herein, Layer 1 can comprise a physical layer of a UE / RAN node.

[0103] Figure 7 is a diagram of example interfaces 700 of baseband circuitry according to one or more implementations described herein. One or more components or features of example interfaces 700 can correspond to one or more components or features described above or elsewhere. Baseband circuitry 704 can comprise processors 704A, 704B, 704C, 704D, and 704E and a memory 704G utilized by said processors. Each of the processors 704A, 704B, 704C, 704D, and 704E can include a memory interface, 706A, 706B, 706C, 706D, and 706E, respectively, to send / receive data to / from the memory 704G. Baseband circuitry can be a component of a UE and / or another type of device or system capable of transmitting and / or receiving wireless signals.

[0104] In some implementations, memory 704G can receive, store, and / or provide information and instructions for supporting signaling enhancements for DCLbased multi-cell scheduling. For example, the information and instructions can support receiving and implementing DCI that scheduled multiple PUSCH / PDSCH messages for multiple cells / base stations 222.234903-6717-3736, v. 1Attorney Docket No.: 106842241940 (P69626WO1)

[0105] Baseband circuitry 704 can further include one or more interfaces to communicatively couple to other circuitries / devices, such as a memory interface 712 (e.g., an interface to send / receive data to / from memory external to baseband circuitry 704), an application circuitry interface 714 (e.g., an interface to send / receive data to / from the application circuitry as described herein), an RF circuitry interface 716, a wireless hardware connectivity interface 718 (e.g., an interface to send / receive data to / from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components), and a power management interface 720 (e.g., an interface to send / receive power or control signals to / from a PMC)

[0106] Figure 8 is a block diagram illustrating components, according to some example implementations, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, Fig. 8 shows a diagrammatic representation of hardware resources 800 including one or more processors 810 (or processor cores), one or more memory / storage devices 820, and one or more communication resources 830, each of which can be communicatively coupled via a bus 840. For implementations where node virtualization or network function virtualization is utilized, a hypervisor can be executed to provide an execution environment for one or more network slices / sub-slices to utilize hardware resources 800. Hardware resources 800 can interact with hypervisor 802. For example, hypervisor 802 can schedule or otherwise manage hardware resource 800.

[0107] The processors 810 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) such as a baseband processor, an application specific integrated circuit (ASIC), a radio-frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) can include, for example, a processor 812 and a processor 814.

[0108] The memory / storage devices 820 can include main memory, disk storage, or any suitable combination thereof. The memory / storage devices 820 can include, but are not limited to any type of volatile or non-volatile memory such as dynamic random-access memory (DRAM), static random-access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.

[0109] In some implementations, memory / storage devices 820 receive and / or store information and instructions 855 for supporting signaling enhancements for DCI-based multi-244903-6717-3736, v. 1Attorney Docket No.: 106842241940 (P69626WO1) cell scheduling. For example, the information and instructions can support receiving and implementing DCI that scheduled multiple PUSCH / PDSCH messages for multiple cells / base stations 222. These and many other features and examples are discussed herein.

[0110] Communication resources 830 can include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 804 or one or more databases 806 via a network808. For example, communication resources 830 can include wired communication components (e.g., for coupling via a universal serial bus), cellular communication components, near field communication components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components. [OHl] Instructions 850A, 850B, 850C, 850D, and / or 850E can comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of processors 810 to perform any one or more of the methodologies discussed herein. Instructions 850 can reside, completely or partially, within at least one of processors 810 (e.g., within a cache memory), memory / storage devices 820, or any suitable combination thereof. Furthermore, any portion of instructions 850A-E can be transferred to hardware resources 800 from any combination of peripheral devices 804 or databases 806. Accordingly, memory of processors 810, memory / storage devices 820, peripheral devices 804, and databases 806 are examples of computer-readable and machine-readable media.

[0112] Figure 9 is a diagram of an example process for signaling enhancements for DCL based multi-cell scheduling according to one or more implementations described herein. Process 900 can be implemented by UE 210, baseband circuitry, or both. In some implementations, some or all of process 900 can be performed by one or more other systems or devices, including one or more of the devices of Fig. 2. Additionally, process 900 can include one or more fewer, additional, differently ordered and / or arranged operations than those shown in Fig. 9. In some implementations, some or all of the operations of process 900 can be performed independently, successively, simultaneously, etc., of one or more of the other operations of process 900. As such, the techniques described herein are not limited to a number, sequence, arrangement, timing, etc., of the operations or processes depicted in Fig. 9.

[0113] Process 900 can include processing configuration information comprising a first cell set that includes at least one first cell associated with different SCSs, different band types, or both (block 910). Process 900 can include processing DCI comprising: an indication of the first cell set, an indication of the at least one first cell, at least one first TDRA indicating at least one channel of the at least one first cell (block 920). Process 900 can include determining, based on the DCI, multi-cell channel scheduling for the at least one first cell of the first cell set (block254903-6717-3736, v. 1Attorney Docket No.: 106842241940 (P69626WO1)930).

[0114] Figure 10 is a diagram of an example process for signaling enhancements for DCI- based multi-cell scheduling according to one or more implementations described herein. Process 1000 can be implemented by UE 210, baseband circuitry, or both. In some implementations, some or all of process 1000 can be performed by one or more other systems or devices, including one or more of the devices of Fig. 2. Additionally, process 1000 can include one or more fewer, additional, differently ordered and / or arranged operations than those shown in Fig. 10. In some implementations, some or all of the operations of process 1000 can be performed independently, successively, simultaneously, etc., of one or more of the other operations of process 1000. As such, the techniques described herein are not limited to a number, sequence, arrangement, timing, etc., of the operations or processes depicted in Fig. 10.

[0115] Process 1000 can include receiving configuration information comprising a first cell set that includes at least one first cell associated with different SCSs, different band types, or both (block 1010). Process 1000 can include receiving DCI comprising: an indication of the first cell set, an indication of the at least one first cell, at least one first TDRA indicating at least one channel of the at least one first cell (block 1020). Process 1000 can include determining, based on the DCI, multi-cell channel scheduling for the at least one first cell of the first cell set. (block 1030).

[0116] Figure 11 is a diagram of an example process for signaling enhancements for DCI- based multi-cell scheduling according to one or more implementations described herein. Process 1100 can be implemented by UE 210, baseband circuitry, or both. In some implementations, some or all of process 1100 can be performed by one or more other systems or devices, including one or more of the devices of Fig. 2. Additionally, process 1100 can include one or more fewer, additional, differently ordered and / or arranged operations than those shown in Fig. 11. In some implementations, some or all of the operations of process 1100 can be performed independently, successively, simultaneously, etc., of one or more of the other operations of process 1100. As such, the techniques described herein are not limited to a number, sequence, arrangement, timing, etc., of the operations or processes depicted in Fig. 11.

[0117] Process 1100 can include transmitting configuration information comprising a first cell set that includes at least one first cell associated with different SCSs, different band types, or both (block 1110). Process 1100 can include transmitting DCI comprising: an indication of the first cell set, an indication of the at least one first cell, at least one first TDRA indicating at least one channel of the at least one first cell (block 1120).

[0118] Examples and / or implementations herein can include subject matter such as a264903-6717-3736, v. 1Attorney Docket No.: 106842241940 (P69626WO1) method, means for performing acts or blocks of the method, at least one machine-readable medium including executable instructions that, when performed by a machine (e.g., a processor (e.g., processor , etc.) with memory, an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or the like) cause the machine to perform acts of the method or of an apparatus or system for concurrent communication using multiple communication technologies according to implementations and examples described.

[0119] In example 1, which can also include one or more of the examples described herein, baseband circuitry can comprise: a memory; and one or more processors configured to, when executing instructions stored in the memory, cause UE 210 to: process configuration information comprising a first cell set that includes at least one first cell associated with different SCSs, different band types, or both; process DCI comprising: an indication of the first cell set, an indication of the at least one first cell, at least one first TDRA indicating at least one channel of the at least one first cell; determine, based on the DCI, multi-cell channel scheduling for the at least one first cell of the first cell set.

[0120] In example 2, which can also include one or more of the examples described herein, each band type of the different band types comprises a FDD band or a TDD band.

[0121] In example 3, which can also include one or more of the examples described herein, wherein the at least one first cell set corresponds to an entry of a table comprising a plurality of entries, each entry of the plurality of entries corresponding to a cell set associated with a unique cell set identifier.

[0122] In example 4, which can also include one or more of the examples described herein, wherein the at least one first cell comprises at least one combination of cells corresponding to an entry of a table, wherein the table comprises a plurality of entries, each entry of the plurality of entries corresponding to a cell combination associated with a unique cell combination identifier.

[0123] In example 5, which can also include one or more of the examples described herein, wherein the at least one first TDRA corresponding to an entry of a table, wherein the table comprises a plurality of entries, each entry of the plurality of entries corresponding to a TDRA associated with a unique TDRA identifier.

[0124] In example 6, which can also include one or more of the examples described herein, wherein the configuration information further comprises a second cell set that comprises at least one second cell associated with a same SCS, a same band type, or both.

[0125] In example 7, which can also include one or more of the examples described herein, when the indication of the first cell set is received prior to an indication of the second cell set, refrain from receiving the indication of the second cell set.274903-6717-3736, v. 1Attorney Docket No.: 106842241940 (P69626WO1)

[0126] In example 8, which can also include one or more of the examples described herein, when the indication of the second cell set is received prior to an indication of the first cell set, refrain from receiving the indication of the first cell set.

[0127] In example 9, which can also include one or more of the examples described herein, wherein the DCI comprises the indication of the first cell set without an indication of the second cell set.

[0128] In example 10, which can also include one or more of the examples described herein, wherein the one or more processors are configured to: when the indication of the at least one first cell is received prior to an indication of the at least one second cell, refrain from receiving the indication of the at least one second cell.

[0129] In example 11, which can also include one or more of the examples described herein, wherein the DCI comprises the indication of the at least one first cell without an indication of the at least one second cell.

[0130] In example 12, which can also include one or more of the examples described herein, when the indication of the at least one first TDRA is received prior to an indication of at least one second TDRA, wherein the at least one second TDRA is associated with the at least one second cell, refrain from receiving the indication of the at least one second TDRA.

[0131] In example 13, which can also include one or more of the examples described herein, wherein the DCI comprises the indication of the at least one first cell without an indication of at least one second TDRA, wherein the at least one second TDRA is associated with the at least one second cell.

[0132] In example 14, which can also include one or more of the examples described herein, wherein the DCI further comprises a new data indicator (NDI) comprising at least one block associated with the at least one first cell, each block of the at least one block comprising a number of bits based on the at least one first TDRA.

[0133] In example 15, which can also include one or more of the examples described herein, wherein each bit of the number of bits corresponds to a channel associated with the at least one first cell.

[0134] In example 16, which can also include one or more of the examples described herein, wherein the DCI further comprises a redundancy version indicator comprising at least one block associated with the at least one first cell, each block of the at least one block comprising a quantity of bits based on the at least one first TDRA.

[0135] In example 17, which can also include one or more of the examples described herein, wherein at least one value of least one of the quantity of bits is based on a quantity of284903-6717-3736, v. 1Attorney Docket No.: 106842241940 (P69626WO1) redundancy versions associated with the at least one channel.

[0136] In example 18, which can also include one or more of the examples described herein, wherein each bit of the quantity of bits corresponds to the at least one channel associated with the at least one first cell.

[0137] In example 19, which can also include one or more of the examples described herein, a UE (e.g., UE 210) can comprise: a memory; and one or more processors configured to, when executing instructions stored in the memory, cause UE 210 to: receive configuration information comprising a first cell set that includes at least one first cell associated with different SCSs, different band types, or both; receive DCI comprising: an indication of the first cell set, an indication of the at least one first cell, at least one first TDRA indicating at least one channel of the at least one first cell; determine, based on the DCI, multi-cell channel scheduling for the at least one first cell of the first cell set.

[0138] In example 20, which can also include one or more of the examples described herein, base station can comprise: a memory; and one or more processors configured to, when executing instructions stored in the memory, cause UE 210 to: transmit configuration information comprising a first cell set that includes at least one first cell associated with different SCSs, different band types, or both; and transmit DCI comprising: an indication of the first cell set, an indication of the at least one first cell, at least one first TDRA indicating at least one channel of the at least one first cell.

[0139] The examples discussed above also extend to method, computer-readable medium, and means-plus-function claims and implementations, any of which can include one or more of the features or operations of any one or combination of the examples mentioned above.

[0140] The above description of illustrated examples, implementations, aspects, etc., of the subject disclosure, including what is described in the Abstract, is not intended to be exhaustive or to limit the disclosed aspects to the precise forms disclosed. While specific examples, implementations, aspects, etc., are described herein for illustrative purposes, various modifications are possible that are considered within the scope of such examples, implementations, aspects, etc., as those skilled in the relevant art can recognize.

[0141] In this regard, while the disclosed subject matter has been described in connection with various examples, implementations, aspects, etc., and corresponding Figures, where applicable, it is to be understood that other similar aspects can be used or modifications and additions can be made to the disclosed subject matter for performing the same, similar, alternative, or substitute function of the subject matter without deviating therefrom. Therefore, the disclosed subject matter should not be limited to any single example, implementation, or294903-6717-3736, v. 1Attorney Docket No.: 106842241940 (P69626WO1) aspect described herein, but rather should be construed in breadth and scope in accordance with the appended claims below.

[0142] In particular regard to the various functions performed by the above described components or structures (assemblies, devices, circuits, systems, etc.), the terms (including a reference to a “means”) used to describe such components are intended to correspond, unless otherwise indicated, to any component or structure which performs the specified function of the described component (e.g., that is functionally equivalent), even though not structurally equivalent to the disclosed structure which performs the function in the herein illustrated exemplary implementations. In addition, while a particular feature can have been disclosed with respect to only one of several implementations, such feature can be combined with one or more other features of the other implementations as can be desired and advantageous for any given application.

[0143] As used herein, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or”. That is, unless specified otherwise, or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form. Furthermore, to the extent that the terms “including”, “includes”, “having”, “has”, “with”, or variants thereof are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprising.” Additionally, in situations wherein one or more numbered items are discussed (e.g., a “first X”, a “second X”, etc.), in general the one or more numbered items can be distinct, or they can be the same, although in some situations the context can indicate that they are distinct or that they are the same.

[0144] 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 identifiable information data should be managed and handled to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.304903-6717-3736, v. 1

Claims

Attorney Docket No.: 106842241940 (P69626WO1)CLAIMSWhat is claimed is:

1. Baseband circuitry, comprising: one or more processors configured to: process configuration information comprising a first cell set that includes at least one first cell associated with different subcarrier spacings (SCS), different band types, or both; process downlink control information (DCI) comprising: an indication of the first cell set, an indication of the at least one first cell, at least one first time domain resource assignment (TDRA) indicating at least one channel of the at least one first cell; and determine, based on the DCI, multi-cell channel scheduling for the at least one first cell of the first cell set.

2. The baseband circuitry of claim 1, wherein each band type of the different band types comprises a frequency division duplex (FDD) band or a time division duplex (TDD) band.

3. The baseband circuitry of claim 1, wherein the at least one first cell set corresponds to an entry of a table comprising a plurality of entries, each entry of the plurality of entries corresponding to a cell set associated with a unique cell set identifier.

4. The baseband circuitry of claim 1, wherein the at least one first cell comprises at least one combination of cells corresponding to an entry of a table, wherein the table comprises a plurality of entries, each entry of the plurality of entries corresponding to a cell combination associated with a unique cell combination identifier.

5. The baseband circuitry of claim 4, wherein the at least one first TDRA corresponding to an entry of a table, wherein the table comprises a plurality of entries, each entry of the plurality of entries corresponding to a TDRA associated with a unique TDRA identifier.

6. The baseband circuitry of claim 1, wherein the configuration information further comprises a second cell set that comprises at least one second cell associated with a same subcarrier spacing (SCS), a same band type, or both.314903-6717-3736, v. 1Attorney Docket No.: 106842241940 (P69626WO1)7. The baseband circuitry of claim 6, wherein the one or more processors are configured to: when the indication of the first cell set is received prior to an indication of the second cell set, refrain from receiving the indication of the second cell set.

8. The baseband circuitry of claim 6, wherein the one or more processors are configured to: when the indication of the second cell set is received prior to an indication of the first cell set, refrain from receiving the indication of the first cell set.

9. The baseband circuitry of claim 6, wherein the DCI comprises the indication of the first cell set without an indication of the second cell set.

10. The baseband circuitry of claim 6, wherein the one or more processors are configured to: when the indication of the at least one first cell is received prior to an indication of the at least one second cell, refrain from receiving the indication of the at least one second cell.

11. The baseband circuitry of claim 6, wherein the DCI comprises the indication of the at least one first cell without an indication of the at least one second cell.

12. The baseband circuitry of claim 6, wherein the one or more processors are configured to: when the indication of the at least one first TDRA is received prior to an indication of at least one second TDRA, wherein the at least one second TDRA is associated with the at least one second cell, refrain from receiving the indication of the at least one second TDRA.

13. The baseband circuitry of claim 6, wherein the DCI comprises the indication of the at least one first cell without an indication of at least one second TDRA, wherein the at least one second TDRA is associated with the at least one second cell.

14. The baseband circuitry of claim 1, wherein the DCI further comprises a new data indicator (NDI) comprising at least one block associated with the at least one first cell, each block of the at least one block comprising a number of bits based on the at least one first TDRA.324903-6717-3736, v. 1Attorney Docket No.: 106842241940 (P69626WO1)15. The baseband circuitry of claim 14, wherein each bit of the number of bits corresponds to a channel associated with the at least one first cell.

16. The baseband circuitry of claim 1, wherein the DCI further comprises a redundancy version indicator comprising at least one block associated with the at least one first cell, each block of the at least one block comprising a quantity of bits based on the at least one first TDRA.

17. The baseband circuitry of claim 16, wherein at least one value of least one of the quantity of bits is based on a quantity of redundancy versions associated with the at least one channel.

18. The baseband circuitry of claim 16, wherein each bit of the quantity of bits corresponds to the at least one channel associated with the at least one first cell.

19. A user equipment (UE), comprising: a memory; and one or more processors configured to, when executing instructions stored in the memory, cause the UE to: receive configuration information comprising a first cell set that includes at least one first cell associated with different subcarrier spacings (SCS), different band types, or both; receive downlink control information (DCI) comprising: an indication of the first cell set, an indication of the at least one first cell, at least one first time domain resource assignment (TDRA) of the at least one first cell; and determine, based on the DCI, multi-cell PUSCH scheduling for the at least one first cell of the first cell set.

20. A base station, comprising: a memory; and one or more processors configured to, when executing instructions stored in the memory, cause the base station to:334903-6717-3736, v. 1Attorney Docket No.: 106842241940 (P69626WO1) transmit configuration information comprising a first cell set that includes at least one first cell associated with different subcarrier spacings (SCS), different band types, or both; and transmit downlink control information (DCI) comprising: an indication of the first cell set, an indication of the at least one first cell, at least one first time domain resource assignment (TDRA) of the at least one first cell.4903-6717-3736, v. 1

Images