WO2023205293A1

WO2023205293A1 - Physical downlink control channel (pdcch) transmission with multi-cell scheduling

Info

Publication number: WO2023205293A1
Application number: PCT/US2023/019196
Authority: WO
Inventors: Yingyang Li; Yi Wang; Gang Xiong
Original assignee: Intel Corporation
Priority date: 2022-04-22
Filing date: 2023-04-20
Publication date: 2023-10-26

Abstract

An apparatus of a New Radio (NR) Node B (gNB), a method, and a storage medium. One or more processors of the apparatus are to identify scheduling information for a plurality of cells and related to one or more SCH (SCH) transmissions, the one or more SCH transmissions including one or more physical uplink SCH (PUSCH) transmissions or one or more physical downlink SCH (PDSCH) transmissions; generate a physical downlink control channel (PDCCH) based on the scheduling information; and send the PDCCH for transmission to a user equipment (UE) on a single scheduling cell of the plurality of cells.

Description

PHYSICAL DOWNLINK CONTROL CHANNEL (PDCCH) TRANSMISSION WITH MULTI-CELL SCHEDULING

CROSS REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of and priority from U.S. Provisional Patent Application No. 63/333,762 entitled "PHYSICAL DOWNLINK CONTROL CHANNEL (PDCCH) TRANSMISSION WITH MULTI-CELL SCHEDULING,” filed April 22, 2022, from U.S Provisional Patent Application No. 63/336,050 entitled "PHYSICAL DOWNLINK CONTROL CHANNEL (PDCCH) TRANSMISSION WITH MULTI-CELL SCHEDULING” filed April 28, 2022, from U.S. Provisional Patent Application No. 63/352,914 entitled "PHYSICAL DOWNLINK CONTROL CHANNEL (PDCCH) TRANSMISSION WITH MULTI-CELL SCHEDULING” filed June 16, 2022, and from U.S. Provisional Patent Application No. 63/421,373 entitled "PHYSICAL DOWNLINK CONTROL CHANNEL (PDCCH) TRANSMISSION WITH MULTI-CELL SCHEDULING” filed November 1, 2022.

FIELD

[0002] Various embodiments generally may relate to the field of wireless communications in a cellular network.

BACKGROUND

[0003] Various embodiments generally may relate to the field of wireless communications, and especially to the scheduling of shared channel transmissions through a physical downlink control channel (PDCCH).

BRIEF DESCRIPTION OF THE DRAWINGS

[0004] Fig. 1 shows a communication network according to some embodiments.

[0005] Fig. 2 shows a cellular wireless network between a UE and an access node (AN) according to some embodiments.

[0006] Fig. 3 shows components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium.

[0007] Fig. 4 is a flow chart of an example procedure of adaptive inter-frequency RSTD measurement gap pattern configuration according to one embodiment. [0008] Fig 5 illustrates a signaling diagram for multi-cell scheduling according to a first example.

[0009] Fig. 6 illustrates a signaling diagram for multi-cell scheduling according to a second example.

[0010] Fig. 7 illustrates a signaling diagram for multi-cell scheduling according to a third example.

[0011] Fig. 8 illustrates a signaling diagram for multi-cell scheduling according to a fourth example.

[0012] Fig. 9 illustrates a signaling diagram for multi-cell scheduling according to a fifth example.

[0013] Fig. 10 illustrates a signaling diagram for multi-cell scheduling according to a sixth example.

[0014] Fig. 11 is a flow chart of a first process according to an embodiment.

[0015] Fig. 12 is a flow chart of a second process according to another embodiment.

DETAILED DESCRIPTION

[0016] The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well -known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present document, the phrases “A or B” and “A/B” mean (A), (B), or (A and B).

[0017] In some embodiments, the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of Figs 1-3, or some other figure herein, may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof. One such process is depicted in Figs. 1 -3. Tn some embodiments, the process may be performed by a New Radio (NR) Node B (gNB) or by a NR User Equipment (UE).

[0018] An apparatus of a New Radio (NR) Node B (gNB), a method, and a storage medium. One or more processors of the apparatus are to identify scheduling information for a plurality of cells and related to one or more SCH (SCH) transmissions, the one or more SCH transmissions including one or more physical uplink SCH (PUSCH) transmissions or one or more physical downlink SCH (PDSCH) transmissions; generate a physical downlink control channel (PDCCH) based on the scheduling information; and send the PDCCH for transmission to a user equipment (UE) on a single scheduling cell of the plurality of cells.

[0019] SYSTEMS AND IMPLEMENTATIONS

[0020] Figs. 1-4 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.

[0021] Fig. 1 illustrates a network 100 in accordance with various embodiments. The network 100 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems. However, the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3 GPP systems, or the like.

[0022] The network 100 may include a UE 102, which may include any mobile or non- mobile computing device designed to communicate with a RAN 104 via an over-the-air connection. The UE 102 may be communicatively coupled with the RAN 104 by a Uu interface. The UE 102 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electron! c/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, ToT device, etc.

[0023] In some embodiments, the network 100 may include a plurality of UEs coupled directly with one another via a sidelink interface. The UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc. [0024] In some embodiments, the UE 102 may additionally communicate with an AP 106 via an over-the-air connection. The AP 106 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 104. The connection between the UE 102 and the AP 106 may be consistent with any IEEE 802.11 protocol, wherein the AP 106 could be a wireless fidelity (Wi-Fi®) router. In some embodiments, the UE 102, RAN 104, and AP 106 may utilize cellular-WLAN aggregation (for example, LWA/LWIP). Cellular-WLAN aggregation may involve the UE 102 being configured by the RAN 104 to utilize both cellular radio resources and WLAN resources.

[0025] The RAN 104 may include one or more access nodes, for example, AN 108. AN 108 may terminate air-interface protocols for the UE 102 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and LI protocols. In this manner, the AN 108 may enable data/voice connectivity between CN 120 and the UE 102. In some embodiments, the AN 108 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool. The AN 108 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 108 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

[0026] In embodiments in which the RAN 104 includes a plurality of ANs, they may be coupled with one another via an X2 interface (if the RAN 104 is an LTE RAN) or an Xn interface (if the RAN 104 is a 5G RAN). The X2/Xn interfaces, which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc.

[0027] The ANs of the RAN 104 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 102 with an air interface for network access. The UE 102 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 104. For example, the UE 102 and RAN 104 may use carrier aggregation to allow the UE 102 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell. In dual connectivity scenarios, a first AN may be a master node that provides an MCG and a second AN may be secondary node that provides an SCG. The first/second ANs may be any combination of eNB, gNB, ng-eNB, etc. [0028] The RAN 104 may provide the air interface over a licensed spectrum or an unlicensed spectrum. To operate in the unlicensed spectrum, the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells. Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.

[0029] In V2X scenarios the UE 102 or AN 108 may be or act as a RSU, which may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like. In one example, an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communications services. The components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.

[0030] In some embodiments, the RAN 104 may be an LTE RAN 110 with eNBs, for example, eNB 112. The LTE RAN 110 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc. The LTE air interface may rely on CSLRS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE. The LTE air interface may operate on sub-6 GHz bands.

[0031] In some embodiments, the RAN 104 may be an NG-RAN 114 with gNBs, for example, gNB 116, or ng-eNBs, for example, ng-eNB 118. The gNB 116 may connect with 5G- enabled UEs using a 5G NR interface. The gNB 116 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 1 18 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface. The gNB 116 and the ng-eNB 118 may connect with each other over an Xn interface.

[0032] In some embodiments, the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 114 and a UPF 148 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN114 and an AMF 144 (e.g., N2 interface).

[0033] The NG-RAN 114 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data. The 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface. The 5G- NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking. The 5G-NR air interface may operate on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH.

[0034] In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWP can be used for dynamic adaptation of the SCS. For example, the UE 102 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 102, the SCS of the transmission is changed as well. Another use case example of BWP is related to power saving. In particular, multiple BWPs can be configured for the UE 102 with different amount of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 102 and in some cases at the gNB 116. A BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.

[0035] The RAN 104 is communicatively coupled to CN 120 that includes network elements to provide various functions to support data and telecommunications services to customers/subscribers (for example, users of UE 102). The components of the CN 120 may be implemented in one physical node or separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 120 onto physical compute/storage resources in servers, switches, etc. A logical instantiation of the CN 120 may be referred to as a network slice, and a logical instantiation of a portion of the CN 120 may be referred to as a network sub-slice.

[0036] In some embodiments, the CN 120 may be an LTE CN 122, which may also be referred to as an EPC. The LTE CN 122 may include MME 124, SGW 126, SGSN 128, HSS 130, PGW 132, and PCRF 134 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 122 may be briefly introduced as follows.

[0037] The MME 124 may implement mobility management functions to track a current location of the UE 102 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.

[0038] The SGW 126 may terminate an SI interface toward the RAN and route data packets between the RAN and the LTE CN 122. The SGW 126 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.

[0039] The SGSN 128 may track a location of the UE 102 and perform security functions and access control. In addition, the SGSN 128 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 124; MME selection for handovers; etc. The S3 reference point between the MME 124 and the SGSN 128 may enable user and bearer information exchange for inter-3 GPP access network mobility in idle/active states.

[0040] The HSS 130 may include a database for network users, including subscription- related information to support the network entities’ handling of communication sessions. The HSS 130 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc. An S6a reference point between the HSS 130 and the MME 124 may enable transfer of subscription and authentication data for authenticating/authorizing user access to the LTE CN 120.

[0041] The PGW 132 may terminate an SGi interface toward a data network (DN) 136 that may include an application/content server 138. The PGW 132 may route data packets between the LTE CN 122 and the data network 136. The PGW 132 may be coupled with the SGW 126 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 132 may further include a node for policy enforcement and charging data collection (for example, PCEF). Additionally, the SGi reference point between the PGW 132 and the data network 1 36 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services. The PGW 132 may be coupled with a PCRF 134 via a Gx reference point.

[0042] The PCRF 134 is the policy and charging control element of the LTE CN 122. The PCRF 134 may be communicatively coupled to the app/content server 138 to determine appropriate QoS and charging parameters for service flows. The PCRF 132 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.

[0043] In some embodiments, the CN 120 may be a 5GC 140. The 5GC 140 may include an AUSF 142, AMF 144, SMF 146, UPF 148, NSSF 150, NEF 152, NRF 154, PCF 156, UDM 158, and AF 160 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the 5GC 140 may be briefly introduced as follows.

[0044] The AUSF 142 may store data for authentication of UE 102 and handle authentication-related functionality. The AUSF 142 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 140 over reference points as shown, the AUSF 142 may exhibit an Nausf service-based interface. [0045] The AMF 144 may allow other functions of the 5GC 140 to communicate with the UE 102 and the RAN 104 and to subscribe to notifications about mobility events with respect to the UE 102. The AMF 144 may be responsible for registration management (for example, for registering UE 102), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 144 may provide transport for SM messages between the UE 102 and the SMF 146, and act as a transparent proxy for routing SM messages. AMF 144 may also provide transport for SMS messages between UE 102 and an SMSF. AMF 144 may interact with the AUSF 142 and the UE 102 to perform various security anchor and context management functions. Furthermore, AMF 144 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 104 and the AMF 144; and the AMF 144 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection. AMF 144 may also support NAS signaling with the UE 102 over an N3 IWF interface.

[0046] The SMF 146 may be responsible for SM (for example, session establishment, tunnel management between UPF 148 and AN 108); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 148 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 144 over N2 to AN 108; and determining SSC mode of a session. SM may refer to management of a PDU session, and a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 102 and the data network 136.

[0047] The UPF 148 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 136, and a branching point to support multi-homed PDU session. The UPF 148 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF- to-QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 148 may include an uplink classifier to support routing traffic flows to a data network.

[0048] The NSSF 150 may select a set of network slice instances serving the UE 102. The NSSF 150 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed. The NSSF 150 may also determine the AMF set to be used to serve the UE 102, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 154. The selection of a set of network slice instances for the UE 102 may be triggered by the AMF 144 with which the UE 102 is registered by interacting with the NSSF 150, which may lead to a change of AMF. The NSSF 150 may interact with the AMF 144 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 150 may exhibit an Nnssf service-based interface.

[0049] The NEF 152 may securely expose services and capabilities provided by 3GPP network functions for third party, internal exposure/re-exposure, AFs (e g., AF 160), edge computing or fog computing systems, etc. In such embodiments, the NEF 152 may authenticate, authorize, or throttle the AFs. NEF 152 may also translate information exchanged with the AF 160 and information exchanged with internal network functions. For example, the NEF 152 may translate between an AF- Service-Identifier and an internal 5GC information. NEF 152 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 152 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 152 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 152 may exhibit an Nnef service-based interface.

[0050] The NRF 154 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 154 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 154 may exhibit the Nnrf service-based interface.

[0051] The PCF 156 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior. The PCF 156 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 158. In addition to communicating with functions over reference points as shown, the PCF 156 exhibit an Npcf service-based interface.

[0052] The UDM 158 may handle subscription-related information to support the network entities’ handling of communication sessions, and may store subscription data of UE 102. For example, subscription data may be communicated via an N8 reference point between the UDM 158 and the AMF 144. The UDM 158 may include two parts, an application front end and aUDR. The UDR may store subscription data and policy data for the UDM 158 and the PCF 156, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 102) for the NEF 152. The Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 158, PCF 156, and NEF 152 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM may include a UDM-FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM- FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management. In addition to communicating with other NFs over reference points as shown, the UDM 158 may exhibit the Nudm service-based interface.

[0053] The AF 160 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control.

[0054] In some embodiments, the 5GC 140 may enable edge computing by selecting operator/3^rd party services to be geographically close to a point that the UE 102 is attached to the network. This may reduce latency and load on the network. To provide edge-computing implementations, the 5GC 140 may select a UPF 148 close to the UE 102 and execute traffic steering from the UPF 148 to data network 136 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 160. In this way, the AF 160 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 160 is considered to be a trusted entity, the network operator may permit AF 160 to interact directly with relevant NFs. Additionally, the AF 160 may exhibit an Naf service-based interface.

[0055] The data network 136 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application/content server 138.

[0056] Fig. 2 schematically illustrates a wireless network 200 in accordance with various embodiments. The wireless network 200 may include a UE 202 in wireless communication with an AN 204. The UE 202 and AN 204 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein.

[0057] The UE 202 may be communicatively coupled with the AN 204 via connection 206. The connection 206 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5GNR protocol operating at mmWave or sub-6GHz frequencies.

[0058] The UE 202 may include a host platform 208 coupled with a modem platform 210. The host platform 208 may include application processing circuitry 212, which may be coupled with protocol processing circuitry 214 of the modem platform 210. The application processing circuitry 212 may run various applications for the UE 202 that source/sink application data. The application processing circuitry 212 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations .

[0059] The protocol processing circuitry 214 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 206. The layer operations implemented by the protocol processing circuitry 214 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.

[0060] The modem platform 210 may further include digital baseband circuitry 216 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 214 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.

[0061] The modem platform 210 may further include transmit circuitry 218, receive circuitry 220, RF circuitry 222, and RF front end (RFFE) 224, which may include or connect to one or more antenna panels 226. Briefly, the transmit circuitry 218 may include a digital-to- analog converter, mixer, intermediate frequency (IF) components, etc.; the receive circuitry 220 may include an analog-to-digital converter, mixer, IF components, etc.; the RF circuitry 222 may include a low-noise amplifier, a power amplifier, power tracking components, etc.; RFFE 224 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc. The selection and arrangement of the components of the transmit circuitry 218, receive circuitry 220, RF circuitry 222, RFFE 224, and antenna panels 226 (referred generically as “transmit/receive components”) may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc. Tn some embodiments, the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc. [0062] In some embodiments, the protocol processing circuitry 214 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components.

[0063] A UE reception may be established by and via the antenna panels 226, RFFE 224, RF circuitry 222, receive circuitry 220, digital baseband circuitry 216, and protocol processing circuitry 214. In some embodiments, the antenna panels 226 may receive a transmission from the AN 204 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 226.

[0064] A UE transmission may be established by and via the protocol processing circuitry 214, digital baseband circuitry 216, transmit circuitry 218, RF circuitry 222, RFFE 224, and antenna panels 226. In some embodiments, the transmit components of the UE 204 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 226.

[0065] Similar to the UE 202, the AN 204 may include a host platform 228 coupled with a modem platform 230. The host platform 228 may include application processing circuitry 232 coupled with protocol processing circuitry 234 of the modem platform 230. The modem platform may further include digital baseband circuitry 236, transmit circuitry 238, receive circuitry 240, RF circuitry 242, RFFE circuitry 244, and antenna panels 246. The components of the AN 204 may be similar to and substantially interchangeable with like-named components of the UE 202. In addition to performing data transmission/reception as described above, the components of the AN 208 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

[0066] Fig. 3 is a block diagram illustrating components, according to some example embodiments, 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. 3 shows a diagrammatic representation of hardware resources 300 including one or more processors (or processor cores) 310, one or more memory/storage devices 320, and one or more communication resources 330, each of which may be communicatively coupled via a bus 340 or other interface circuitry. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 302 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources

300.

[0067] The processors 310 may include, for example, a processor 312 and a processor 314. The processors 310 may be, for example, 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 DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

[0068] The memory/storage devices 320 may include main memory, disk storage, or any suitable combination thereof. The memory/storage devices 320 may include, but are not limited to, any type of volatile, non-volatile, or semi-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.

[0069] The communication resources 330 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 304 or one or more databases 306 or other network elements via a network 308. For example, the communication resources 330 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.

[0070] Instructions 350 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 310 to perform any one or more of the methodologies discussed herein. The instructions 350 may reside, completely or partially, within at least one of the processors 310 (e.g., within the processor’s cache memory), the memory/storage devices 320, or any suitable combination thereof. Furthermore, any portion of the instructions 350 may be transferred to the hardware resources 300 from any combination of the peripheral devices 304 or the databases 306. Accordingly, the memory of processors 310, the memory/storage devices 320, the peripheral devices 304, and the databases 306 are examples of computer-readable and machine-readable media.

[0071] Fig. 4 illustrates a network 400 in accordance with various embodiments. The network 400 may operate in a matter consistent with 3GPP technical specifications or technical reports for 6G systems. In some embodiments, the network 400 may operate concurrently with network 100. For example, in some embodiments, the network 400 may share one or more frequency or bandwidth resources with network 100. As one specific example, a UE (e.g., UE 402) may be configured to operate in both network 400 and network 100. Such configuration may be based on a UE including circuitry configured for communication with frequency and bandwidth resources of both networks 100 and 400. In general, several elements of network 400 may share one or more characteristics with elements of network 100. For the sake of brevity and clarity, such elements may not be repeated in the description of network 400.

[0072] The network 400 may include a UE 402, which may include any mobile or non- mobile computing device designed to communicate with a RAN 408 via an over-the-air connection. The UE 402 may be similar to, for example, UE 102. The UE 402 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, loT device, etc. [0073] Although not specifically shown in Fig. 4, in some embodiments the network 400 may include a plurality of UEs coupled directly with one another via a sidelink interface. The UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc. Similarly, although not specifically shown in Fig. 4, the UE 402 may be communicatively coupled with an AP such as AP 106 as described with respect to Fig. 1. Additionally, although not specifically shown in Fig. 4, in some embodiments the RAN 408 may include one or more ANss such as AN 108 as described with respect to Fig. 1. The RAN 408 and/or the AN of the RAN 408 may be referred to as a base station (BS), a RAN node, or using some other term or name.

[0074] The UE 402 and the RAN 408 may be configured to communicate via an air interface that may be referred to as a sixth generation (6G) air interface. The 6G air interface may include one or more features such as communication in a terahertz (THz) or sub-THz bandwidth, or joint communication and sensing. As used herein, the term “joint communication and sensing” may refer to a system that allows for wireless communication as well as radar-based sensing via various types of multiplexing. As used herein, THz or sub-THz bandwidths may refer to communication in the 80 GHz and above frequency ranges. Such frequency ranges may additionally or alternatively be referred to as “millimeter wave” or “mmWave” frequency ranges. [0075] The RAN 408 may allow for communication between the UE 402 and a 6G core network (CN) 410. Specifically, the RAN 408 may facilitate the transmission and reception of data between the UE 402 and the 6G CN 410. The 6G CN 410 may include various functions such as NSSF 150, NEF 152, NRF 154, PCF 156, UDM 158, AF 160, SMF 146, and AUSF 142. The 6G CN 410 may additional include UPF 148 and DN 136 as shown in Fig. 4.

[0076] Additionally, the RAN 408 may include various additional functions that are in addition to, or alternative to, functions of a legacy cellular network such as a 4G or 5G network. Two such functions may include a Compute Control Function (Comp CF) 424 and a Compute Service Function (Comp SF) 436. The Comp CF 424 and the Comp SF 436 may be parts or functions of the Computing Service Plane. Comp CF 424 may be a control plane function that provides functionalities such as management of the Comp SF 436, computing task context generation and management (e g., create, read, modify, delete), interaction with the underlaying computing infrastructure for computing resource management, etc.. Comp SF 436 may be a user plane function that serves as the gateway to interface computing service users (such as UE 402) and computing nodes behind a Comp SF instance. Some functionalities of the Comp SF 436 may include: parse computing service data received from users to compute tasks executable by computing nodes; hold service mesh ingress gateway or service API gateway; service and charging policies enforcement; performance monitoring and telemetry collection, etc. In some embodiments, a Comp SF 436 instance may serve as the user plane gateway for a cluster of computing nodes. A Comp CF 424 instance may control one or more Comp SF 436 instances.

[0077] Two other such functions may include a Communication Control Function (Comm CF) 428 and a Communication Service Function (Comm SF) 438, which may be parts of the Communication Service Plane. The Comm CF 428 may be the control plane function for managing the Comm SF 438, communication sessions creation/configuration/releasing, and managing communication session context. The Comm SF 438 may be a user plane function for data transport. Comm CF 428 and Comm SF 438 may be considered as upgrades of SMF 146 and UPF 148, which were described with respect to a 5G system in Fig. 1. The upgrades provided by the Comm CF 428 and the Comm SF 438 may enable service-aware transport. For legacy (e g., 4G or 5G) data transport, SMF 146 and UPF 148 may still be used.

[0078] Two other such functions may include a Data Control Function (Data CF) 422 and Data Service Function (Data SF) 432 may be parts of the Data Service Plane. Data CF 422 may be a control plane function and provides functionalities such as Data SF 432 management, Data service creation/configuration/releasing, Data service context management, etc. Data SF 432 may be a user plane function and serve as the gateway between data service users (such as UE 402 and the various functions of the 6G CN 410) and data service endpoints behind the gateway. Specific functionalities may include: parse data service user data and forward to corresponding data service endpoints, generate charging data, report data service status.

[0079] Another such function may be the Service Orchestration and Chaining Function (SOCF) 420, which may discover, orchestrate and chain up communication/computing/data services provided by functions in the network. Upon receiving service requests from users, SOCF 420 may interact with one or more of Comp CF 424, Comm CF 428, and Data CF 422 to identify Comp SF 436, Comm SF 438, and Data SF 432 instances, configure service resources, and generate the service chain, which could contain multiple Comp SF 436, Comm SF 438, and Data SF 432 instances and their associated computing endpoints. Workload processing and data movement may then be conducted within the generated service chain. The SOCF 420 may also responsible for maintaining, updating, and releasing a created service chain.

[0080] Another such function may be the service registration function (SRF) 414, which may act as a registry for system services provided in the user plane such as services provided by service endpoints behind Comp SF 436 and Data SF 432 gateways and services provided by the UE 402. The SRF 414 may be considered a counterpart of NRF 154, which may act as the registry for network functions.

[0081] Other such functions may include an evolved service communication proxy (eSCP) and service infrastructure control function (SICF) 426, which may provide service communication infrastructure for control plane services and user plane services. The eSCP may be related to the service communication proxy (SCP) of 5G with user plane service communication proxy capabilities being added. The eSCP is therefore expressed in two parts: eCSP-C 412 and eSCP-U 434, for control plane service communication proxy and user plane service communication proxy, respectively. The SICF 426 may control and configure eCSP instances in terms of service traffic routing policies, access rules, load balancing configurations, performance monitoring, etc

[0082] Another such function is the AMF 444. The AMF 444 may be similar to 144, but with additional functionality. Specifically, the AMF 444 may include potential functional repartition, such as move the message forwarding functionality from the AMF 444 to the RAN 408.

[0083] Another such function is the service orchestration exposure function (SOEF) 418. The SOEF may be configured to expose service orchestration and chaining services to external users such as applications.

[0084] The UE 402 may include an additional function that is referred to as a computing client service function (comp CSF) 404. The comp CSF 404 may have both the control plane functionalities and user plane functionalities, and may interact with corresponding network side functions such as SOCF 420, Comp CF 424, Comp SF 436, Data CF 422, and/or Data SF 432 for service discovery, request/response, compute task workload exchange, etc. The Comp CSF 404 may also work with network side functions to decide on whether a computing task should be run on the UE 402, the RAN 408, and/or an element of the 6G CN 410.

[0085] The UE 402 and/or the Comp CSF 404 may include a service mesh proxy 406. The service mesh proxy 406 may act as a proxy for service-to-service communication in the user plane. Capabilities of the service mesh proxy 406 may include one or more of addressing, security, load balancing, etc.

[0086] Introduction

[0087] Mobile communication has evolved significantly from early voice systems to today’s highly sophisticated integrated communication platform. The next generation wireless communication system, 5G, or new radio (NR) will provide access to information and sharing of data anywhere, anytime by various users and applications. NR is expected to be a unified network/system that target to meet vastly different and sometime conflicting performance dimensions and services. Such diverse multi-dimensional requirements are driven by different services and applications. In general, NR will evolve based on 3GPP LTE-Advanced with additional potential new Radio Access Technologies (RATs) to enrich people lives with better, simple, and seamless wireless connectivity solutions. NR will enable everything connected by wireless and deliver fast, rich contents and services.

[0088] NR supports a wide range of spectrum in different frequency ranges. It is expected that there will be increasing availability of spectrum in the market for 5G Advanced possibly due to re-farming from the bands originally used for previous cellular generation networks. Especially for frequency range (FR1) bands, the available spectrum blocks tend to be more fragmented and scattered with narrower bandwidths. For FR2 bands and some FR1 bands, the available spectrum can be wider such that intra-band multi-carrier operation is necessary. To meet different spectrum needs, it is important to ensure that these scattered spectrum bands or wider bandwidth spectrum can be utilized in a more spectral/power efficient and flexible manner, thus providing higher throughput and decent coverage in the network.

[0089] One motivation is to increase flexibility and spectral/power efficiency on scheduling data over multiple cells including intra-band cells and inter-band cells. The current scheduling mechanism only allows scheduling of single cell physical uplink shared channel (PUSCH) or physical downlink shared channel (PDSCH) per a scheduling downlink control information (DCI). With more available scattered spectrum bands or wider bandwidth spectrum, the need of simultaneous scheduling of multiple cells is expected to be increasing. To reduce the control overhead, it is beneficial to extend from single-cell scheduling to multi-cell PUSCH/PDSCH scheduling with a single scheduling DCI. More specifically, a DCI is used to schedule PDSCH or PUSCH transmissions in more than one cell or component carrier (CC), where each PDSCH or PUSCH is scheduled in one cell or CC.

[0090] Fig. 5 illustrates a signaling diagram 500 in the time domain one example of multicell scheduling for PDSCHs according to some embodiments. In the example, one physical downlink control channel (PDCCH) is used to schedule two PDSCHs in two different cells, i.e., PDSCH#0 in CC0 and PDSCH# 1 in CC1.

[0091] Some embodiments herein relate to mechanisms for PDCCH transmission using the DCI formats for multi-cell scheduling. In particular, embodiments may include one or more of the following:

• One or multiple DCI formats for multi-cell scheduling;

• Total number of PDSCHs under processing for a UE; or

• Hashing function to map a Search space (SS) set to CCEs.

[0092] The configured serving cells for carrier aggregation (CA) or dual connectivity (DC) operations can be divided into multiple sets. The PDSCH and PUSCH transmissions on a cell in a set of cells are only scheduled by a PDCCH on the same cell or other cell(s) in the same set of cells. For a set of cells containing PCell or PSCell, the PCell or PSCell is the scheduling cell, except for the case that a DL or UL transmission on PCell could be scheduled by a scheduling SCell. In the latter case, the DCI for multi-cell scheduling could be configured on the scheduling SCell. In the following embodiments, the DCI formats for PDSCH scheduling and PUSCH scheduling can be configured separately. A DCI format for multi-cell scheduling may be defined by the extension of existing DCI format 0 1 or 1 1. Alternatively, a DCI format for multi-cell scheduling may be defined as a new DCI format, e.g., DCI format 0 3 or 1 3.

[0093] In one embodiment, only one cell is configured as the scheduling cell for the cells in a set of cells for multi-cell scheduling, and the PDSCH or PUSCH transmissions on all cells in the set of cells can be scheduled by the scheduling cell.

[0094] In one option, one DCI format for multi-cell PDSCH or PUSCH scheduling from the scheduling cell can be configured to schedule all the cells in the set of cells. It is up to gNB to schedule a subset of or all the set of cells for a PDCCH with the DCI format. The subset of cells scheduled by different PDCCHs of the DCI format can be different in time. For example, the subset of cells that are scheduled can be indicated by a field for co-scheduled cells indication in the DCI format.

[0095] In another option, one DCI format for multi-cell PDSCH or PUSCH scheduling from the scheduling cell can be configured to only schedule a subset of the set of cells. For a cell that is not schedulable by the DCI format for multi-cell scheduling, a DCI format for single-cell scheduling may be configured on the scheduling cell. The subset of cells scheduled by different PDCCHs of the DCI format for multi-cell scheduling can be different in time. For example, the subset of cells that are scheduled can be indicated by a field for co-scheduled cells indication in the DCI format.

[0096] In another option, multiple DCI formats for multi-cell PDSCH or PUSCH scheduling from the scheduling cell can be configured. Note: The multiple DCI formats for multicell scheduling may be generated by the different configurations of a DCI format defined in the relevant 3GPP specifications for PDSCH or PUSCH scheduling. For example, a single DCI format 0 1 or 1 1 for multi-cell scheduling may be defined in the specification, then, multiple sets of parameters of the DCI fields of the DCI format 0 1 or 1 1 may be configured to generate the multiple DCI formats for multi-cell scheduling. The multiple DCI formats for multi-cell scheduling may be associated with same or different search space sets. Each DCI format of the multiple DCT formats may only schedule a subset of the set of cells. The different DCT format may be able to schedule same or different subset of cells. It is up to gNB to schedule one or more cells in the subset of the set of cells for a PDCCH with a DCI format. For example, the one or more cells that are scheduled can be indicated by a field for co-scheduled cells indication in the DCI format. Particularly, one of the multiple DCI formats may be able to schedule PDSCH or PUSCH on all the set of cells. The scheduled cells by the PDCCHs of a DCI format may be different in time. Two or more DCI formats of the multiple DCI formats may be able to schedule PDSCH or PUSCH transmission on a same cell. Alternatively, the PDSCH or PUSCH transmission on any cell in the set of cells can only be scheduled by at most one DCI format for multi-cell PDSCH or PUSCH scheduling. For a cell that is not schedulable by any DCI format for multi -cell scheduling, a DCI format for single-cell scheduling may be configured on the scheduling cell. Alternatively, UE expects that a cell in the set of cells can be scheduled by at least one DCI format for multi-cell scheduling from the scheduling cell.

[0097] In the above options, for a cell that can be scheduled by a DCI format for multi-cell scheduling, a DCI format for single-cell scheduling in addition to the DCI format for multi-cell scheduling may be configured on the scheduling cell. For example, if DCI format 0 1 or 1 1 for multi-cell scheduling is configured for a cell, it is possible to configure another DCI format 0 2 or 1 2 for single-cell scheduling for the cell. In another example, if DCI format 0 3 or 1 3 for multicell scheduling is configured for a cell, it is possible to configure another DCI format 0 1 or 1 1 for single-cell scheduling for the cell. Alternatively, for a cell that can be scheduled by a DCI format for multi-cell scheduling, UE does not expect to be additionally configured with a singlecell DCI format on the scheduling cell for cross-carrier scheduling. Particularly, a single-cell DCI format for self-scheduling of the scheduling cell may be still configured on the scheduling cell. Alternatively, for a cell that can be scheduled by a DCI format for multi-cell scheduling, UE does not expect to be additionally configured with a single-cell DCI format on the scheduling cell for the cell. Note: it is not precluded that DCI format 0 0, 1 0 or DCI format 2_x can be configured on the scheduling cell.

[0098] In the above options, for a cell in the set of cells that can be scheduled by the DCI format for multi-cell scheduling, a DCI format for single-cell scheduling may be configured on the cell for self-scheduling. Alternatively, UE does not expect to be configured with a single-cell DCI format for self-scheduling on a cell other than the scheduling cell. Specifically, the UE is not expected to be configured for a cell with a DCT format for single-cell cross-carrier scheduling from a scheduling cell and a single-cell DCI format for self-scheduling on the cell if the cell is not the scheduling cell.

[0099]

[0100] Fig. 6 illustrates a signaling diagram 600 in the time domain showing one example of multi-cell scheduling from the scheduling cell CC0. In Fig. 2, in one alternative, the DCI format for multi-cell scheduling can schedule three cells, i.e., CC0, CC1 and CC2 (see solid arrows from PDCCH in scheduling cell CC0. On the other hand, in another alternative, where a CC, such CC3, is not schedulable by multi-cell scheduling, a single-cell DCI format on CC0 can be configured to cross-carrier schedule CC3 according to some embodiments (see arrow in broken lines for single cell scheduling from PDCCH in CC0). In Fig. 2, a single-cell DCI format on the scheduling cell CC0 can be additionally for self-scheduling of CC0 as shown for the first alternative of multi-cell scheduling. Further, a single-cell DCI format on the scheduling cell CC0 can be additionally (that is, in the alternative) configured to cross-carrier schedule CC1. In Fig. 2, a single-cell DCI format for self-scheduling of CC2 may be supported or forbidden (see PDCCH in CC2).

[0101] Fig. 7 illustrates a signaling diagram 700 showing one example of multiple DCI formats for multi-cell scheduling from the scheduling cell CC0. In Fig. 7, a first DCI format for multi-cell scheduling can schedule CC0 & CC3, while a second alternative DCI format for multicell scheduling can be used to schedule CC0, CC1 & CC2. In Fig. 7, both the two DCI formats for multi-cell scheduling can schedule CC0. If CC4 is not schedulable by multi-cell scheduling. Consequently, a single-cell DCI format on the scheduling cell CC0 may be configured to crosscarrier schedule CC4. In Fig. 7, a single-cell DCI format on the scheduling cell CC0 can be additionally configured for self-scheduling of CC0. Further, a single-cell DCI format on the scheduling cell CC0 can be additionally configured to cross-carrier schedule CC1.

[0102] Fig. 8 illustrates a signaling diagram 800 showing another example of multiple DCI formats for multi-cell scheduling from the scheduling cell CC0. In Fig. 8, a first DCI format for multi-cell scheduling can schedule CC3 & CC4, while a second DCI format for multi-cell scheduling can be schedule CC0, CC1 & CC2. In Fig. 8, each cell can only be scheduled by _oneDci format for multi-cell scheduling from the scheduling cell.

[0103] In the above options of Figs. 5-8, for a cell in the set of cells that can be scheduled by the DCI format for multi -cell scheduling on one scheduling cell, a DCI format for single-cell cross-carrier scheduling may be configured on another scheduling cell. Alternatively, UE does not expect to be configured with a DCI format for single-cell cross-carrier scheduling on another scheduling cell.

[0104] Fig. 9 illustrates a signaling diagram 900 showing one example for the configuration of PDCCH monitoring from two scheduling cells. In Fig. 9, CC1 can be scheduled by a DCI format for multi-cell scheduling from CCO and a DCI format for single-cell cross-carrier scheduling from CC2. CC2 can be scheduled by a DCI format for multi-cell scheduling from CCO and a single-cell DCI format for self-scheduling on CC2.

[0105] In one embodiment, two or more cells can be configured as the scheduling cells for the cells in a set of cells for multi-cell scheduling, and multiple DCI formats for multi-cell PDSCH or PUSCH scheduling from the two or more scheduling cells can be configured. The multiple DCI formats for multi-cell scheduling may be generated by the different configurations of a DCI format defined in the relevant 3GPP specifications for PDSCH or PUSCH scheduling. For example, a single DCI format 0 1 or 1 1 for multi -cell scheduling may be defined in the specification, then, multiple sets of parameters of the DCI fields of the DCI format 0 1 or 1-1 may be configured to generate the multiple DCI formats for multi-cell scheduling. The multiple DCI formats for multicell scheduling may be associated with same or different search space sets. Only one DCI format for multi-cell PDSCH or PUSCH scheduling can be configured on one scheduling cell. Alternatively, multiple DCI formats for multi-cell PDSCH or PUSCH scheduling can be configured on one scheduling cell. Each DCI format of the multiple DCI formats may only schedule a subset of the set of cells. The different DCI format may be able to schedule different, same, or different subset of cells. Alternatively, a DCI format for multi-cell scheduling may be able to schedule PDSCH or PUSCH on all the set of cells. A cell may be scheduled by the DCI formats for multi-cell scheduling from one or more scheduling cells. Two or more DCI formats of the multiple DCI formats on the same scheduling cell may be able to schedule PDSCH or PUSCH transmission on a same cell. Alternatively, the PDSCH or PUSCH transmission on any cell in the set of cells can only be scheduled by at most one DCI format for multi-cell PDSCH or PUSCH scheduling or nonscheduling cell.

[0106] For a cell that is not schedulable by any DCI format for multi-cell scheduling, a DCI format for single-cell scheduling may be configured on one scheduling cell. Alternatively, UE expects that a cell in the set of cells can be scheduled by at least one DCI format for multi-cell scheduling from at least one scheduling cell.

[0107] Fora cell that can be scheduled by at least one DCI format for multi-cell scheduling, a DCI format for single-cell scheduling in addition to the DCI format(s) for multi-cell scheduling may be configured on one scheduling cell. Alternatively, for a cell that can be scheduled by a DCI format for multi-cell scheduling, UE does not expect to be additionally configured with a singlecell DCI format on the scheduling cell for cross-carrier scheduling. Particularly, a single-cell DCI format for self-scheduling of the scheduling cell may be still configured on the scheduling cell. Alternatively, for a cell that can be scheduled by a DCI format for multi-cell scheduling, UE does not expect to be additionally configured with a single-cell DCI format on the scheduling cell for the cell. Note: it is not precluded that DCI format 0 0, 1 0 or DCI format 2_x can be configured on a scheduling cell.

[0108] For a cell in the set of cells that can be scheduled by a DCI format for multi-cell scheduling, a DCI format for single-cell scheduling may be configured on the cell for selfscheduling. Alternatively, UE does not expect to be configured with a single-cell DCI format for self-scheduling on a cell other than the scheduling cell. Specifically, the UE is not expected to be configured for a cell with a DCI format for single-cell cross-carrier scheduling from a scheduling cell and a DCI format for self-scheduling on the cell if the cell is not the scheduling cell.

[0109] Fig. 10 illustrates one example of multiple DCI formats for multi-cell scheduling from two scheduling cells CC0 & CC1. In Fig. 10, a first DCI format for multi-cell scheduling from CC0 can schedule CC0 & CC3, while a second DCI format for multi-cell scheduling from CC1 can schedule CC0, CC1 & CC2. In Fig. 10, both the two DCI formats for multi -cell scheduling can schedule CC0. CC4 is not schedulable by multi-cell scheduling. Consequently, a single-cell DCI format on CC0 can be configured to cross-carrier schedule CC4.

[0110] In one embodiment, for a cell that can be scheduled by a DCI format for multi -cell PDSCH or PUSCH scheduling and by a DCI format for single-cell PDSCH or PUSCH scheduling from a scheduling cell, there could be a limitation on the PDCCH monitoring of the two kinds of DCI formats. The above DCI format for single-cell scheduling may be limited to a UE specific search space (USS) set. On the other hand, there is no limitation for a DCI format for single-cell scheduling that is configured in a common search space (CSS) set. Alternatively, the above DCI format for single-cell scheduling may be limited to a USS set or a Type3 CSS set. On the other hand, there is no limitation for a DCI format for single-cell scheduling in TypeO/OA/1/2 CSS sets. Alternatively, the above DCT format for single-cell scheduling may be in any USS and CSS sets. For example, the above limitation also applies to the Type 0/0A/1/2/CSS sets for DCI formats with CRC scrambled by C-RNTI/MCS-C-RNTI/CS-RNTI.

[0111] In one option, for a scheduled cell, a UE may be capable to monitor a DCI format for multi-cell scheduling and a DCI format for single-cell scheduling in the same OFDM symbol(s) on the scheduling cell. In this case, there is no limitation for the configuration of the two kinds of DCI formats, e.g., the two kinds of DCI formats can be in the same PDCCH MO.

[0112] In another option, for a scheduled cell, a UE may be capable to monitor a DCI format for multi-cell scheduling and a DCT format for single-cell scheduling in the different OFDM symbols in the same slot. Then, for the UE without capability of monitoring the two kinds of DCI formats in the same OFDM symbol or in the same PDCCH MO, the UE is not expected to be configured to monitor the two kinds of DCI formats in PDCCH MOs overlapping in time domain, or UE is not expected to be configured to monitor the two kinds of DCI formats in the same PDCCH MO. Alternatively, if the two kinds of DCI formats are configured in the same OFDM symbol or in the same PDCCH MO, a priority rule is defined so that UE only needs to monitor one kind of DCI format. For example, only the DCI format for multi-cell scheduling is monitored. [0113] In another option, for a scheduled cell, a UE may be only capable to monitor a DCI format for multi-cell scheduling and a DCI format for single-cell scheduling in the different slots. Then, the UE is not expected to be configured to monitor the two kinds of DCI formats in the same slot. Alternatively, if the two kinds of DCI formats are configured in the same slot, a priority rule is defined so that UE only needs to monitor one kind of DCI format. For example, only the DCI format for multi-cell scheduling is monitored.

[0114] In another option, for a cell using slot-group based PDCCH monitoring capability, e.g., FR2-2, a UE may be capable of monitoring a DCI format for multi-cell scheduling and a DCI format for single-cell scheduling in the same slot group of Xs slots, which is determined by the combination (Xs, Ys) of the multi-slot PDCCH monitoring capability, but not in the same slot. Then, for such UE, the UE is not expected to be configured to monitor the two kinds of DCI formats in the same slot in a slot group of Xs slots. Alternatively, if the two kinds of DCI formats are configured in the same slot group of Xs slots, a priority rule is defined so that the UE only needs to monitor one kind of DCI format. For example, only the DCI format for multi-cell scheduling is monitored. [0115] In another option, for a cell using slot-group based PDCCH monitoring capability, a UE may only be capable of monitoring a DCI format for multi-cell scheduling and a DCI format for single-cell scheduling in different slot groups of Xs slots. Then, for such a UE, the UE is not expected to be configured to monitor the two kinds of DCI formats in the same slot group of Xs slots. Alternatively, if the two kinds of DCI formats are configured in the same slot group, a priority rule is defined so that the UE only needs to monitor one kind of DCI format. For example, only the DCI format for multi-cell scheduling is monitored.

[0116] In the above options, the restriction may be applied to any cell that can be scheduled by a DCI format for multi-cell scheduling and a DCI format for single-cell scheduling. Alternatively, the restriction may be applied to a subset of the cells that can be scheduled by a DCI format for multi-cell scheduling and a DCI format for single-cell scheduling. Alternatively, the restriction may only apply to a reference cell in the cells that can be scheduled by a DCI format for multi-cell scheduling. In one example, the reference cell may be the cell with the lowest cell index that can be scheduled by the DCI format for multi-cell scheduling and a DCI format for single-cell scheduling. In another example, the reference cell may be the cell with the lowest cell index that can be scheduled by the DCI format for multi-cell scheduling. In this case, if the reference cell is not configured with a DCI format for single-cell scheduling, the restriction in the above options doesn’t apply.

[0117] In one embodiment, a cell may be scheduled by multiple DCI formats for multicell scheduling and by the DCI formats for single-cell PDSCH or PUSCH scheduling from a scheduling cell. A UE may only monitor one or more of the multiple DCI formats for multi-cell scheduling and the DCI formats for single-cell scheduling in a time unit (TU). The time unit may be a symbol, a CORESET, a slot, or a slot group of Xs slots.

[0118] In one option, the UE is not expected to be configured with more than one DCI format for multi-cell scheduling in a TU or a DCI format for multi -cell scheduling and any DCI format for single-cell scheduling in a TU. Alternatively, if such a configuration of DCI formats happens, a priority rule is defined so that the UE only needs to monitor one DCI format for multicell scheduling or the DCI formats for single-cell scheduling.

[0119] In another option, the UE is not expected to be configured with more than one DCI format for multi-cell scheduling in a TU if any DCI format for single-cell scheduling is also configured in the TU. Alternatively, if such configuration of DCI formats happens, a priority rule is defined so that the UE only needs to monitor one DCT format for multi-cell scheduling as well as the DCI formats for single-cell scheduling.

[0120] In one embodiment, for a cell that can be scheduled by DCI formats on two scheduling cells, there could be a limitation on the PDCCH monitoring on the two scheduling cells. This limitation may only apply to the USS sets on the two scheduling cells. On the other hand, there is no limitation for the CSS sets on the two scheduling cells. Alternatively, this limitation may only apply to the USS sets or Type3 CSS sets on the two scheduling cells. On the other hand, there is no limitation for TypeO/OA/1/2 CSS sets on the two scheduling cells. Alternatively, the above DCI format for single-cell scheduling may be in any USS and CSS sets.

[0121] In one option, a UE may be capable of performing PDCCH detection on the two scheduling cells in the overlapped OFDM symbols. In this case, there is no limitation for the configuration of the search space sets on the two scheduling cells.

[0122] In another option, a UE may be capable of performing PDCCH detection on the two scheduling cells in the non-overlapped OFDM symbols in the overlapped slot(s). Then, for such a UE, the UE is not expected to be configured with PDCCH monitoring on the two scheduling cells in the overlapped OFDM symbols in the overlapped slot(s). Alternatively, if the PDCCH monitoring is configured on the two scheduling cells in the overlapped OFDM symbols in the overlapped slot(s), a priority rule is defined so that the UE only needs to monitor PDCCH in one scheduling cell.

[0123] In another option, a UE may only be capable of performing PDCCH detection on the two scheduling cells in the non-overlapped slots. Then, for such a UE, the UE is not expected to be configured with PDCCH monitoring on the two scheduling cells in the overlapped slot(s). Alternatively, if the PDCCH monitoring is configured on the two scheduling cells in the overlapped slot(s), a priority rule is defined so that the UE only needs to monitor PDCCH in one scheduling cell.

[0124] In another option, for a cell using slot-group based PDCCH monitoring capability (e.g., FR2-2), a UE may be capable of performing PDCCH detection on the two scheduling cells in the non-overlapping slots in the overlapped slot group of Xs slots, which is determined by the combination (Xs, Ys) of the multi-slot PDCCH monitoring capability. The value Xs may be the same or different for the two scheduling cells. For such a UE, it is not expected to be configured with PDCCH monitoring on the two scheduling cells in the overlapped slot(s) in the overlapped slot groups of Xs slots. Alternatively, if PDCCH monitoring is configured on the two scheduling cells in the overlapped slot groups of Xs slots, a priority rule is defined so that the UE only needs to monitor PDCCH in one scheduling cell.

[0125] In another option, for a cell using slot-group based PDCCH monitoring capability, a UE may only be capable of doing PDCCH detection on the two scheduling cells in the nonoverlapping slot groups of Xs slots. For such a UE, it is not expected to be configured with PDCCH monitoring on the two scheduling cells in the overlapped slot groups of Xs slots. Alternatively, if PDCCH monitoring is configured on the two scheduling cells in the overlapped slot groups of Xs slots, a priority rule is defined so that the UE only needs to monitor PDCCH in one scheduling cell.

[0126] In the above options, if the absolute duration of the slot groups of the two scheduling cells is different, one reference slot group (e.g., the slot group with smaller absolute duration) can be used in the above restriction. Alternatively, the above restriction is respectively checked based on the slot group of each scheduling cell. If one of the scheduling cells uses slotbased PDCCH monitoring capability, it can be considered that a slot group on the scheduling cell includes only one slot.

[0127] In the above options, the restriction may be applied to any cell that can be scheduled by a DCI format for multi-cell scheduling on a scheduling cell and a DCI format for single-cell scheduling from a different scheduling cell. Alternatively, the restriction may be applied to a subset of the cells that can be scheduled by a DCI format for multi-cell scheduling on a scheduling cell and a DCI format for single-cell scheduling from a different scheduling cell. Alternatively, the restriction may only be applied to a reference cell in the cells that can be scheduled by a DCI format for multi-cell scheduling on a scheduling cell. In one example, the reference cell may be the cell with the lowest cell index that can be scheduled by the DCI format for multi-cell scheduling on a scheduling cell and a DCI format for single-cell scheduling on a different scheduling cell. In another example, the reference cell may be the cell with the lowest cell index that can be scheduled by the DCI format for multi-cell scheduling on a scheduling cell. In this case, if the reference cell is not configured with a DCI format for single-cell scheduling on a different scheduling cell, the restriction in the above options does not apply. [0128] Search space set configuration.

[0129] In one embodiment, all necessary parameters in the SS set configuration of an SS set with a searchSpaceld for a DCI format of multi-cell scheduling can be configured in the configuration of one cell of the cells that can be scheduled by the DCI format. Alternatively, all necessary parameters in the SS set configuration of an SS set with a searchSpaceld for a DCI format of multi-cell scheduling can be configured in the configuration of the scheduling cell or in the configuration of one cell of the cells that can be scheduled by the DCI format. For example, the one cell may be the cell with the lowest cell index in the cells that can be scheduled by the DCI format. Alternatively, the one cell can be selected by the gNB implementation. Tn another option, the one cell can be configured by higher layers for multi -cell scheduling, which can be one of the cells configured for multi -cell scheduling or indicated in the carrier indication table. Further, the one cell may or may not be the scheduling cell.

[0130] In this scheme, if the above one cell is not the scheduling cell, an SS set with the same searchSpaceld is not configured on the scheduling cell. Alternatively, if the above one cell is not the scheduling cell, an SS set with the same searchSpaceld can still be configured on the scheduling cell. However, the DCI format is only monitored on the scheduling cell following the SS set configuration configured for the above one cell. Specifically, in the latter option, the SS set with the same searchSpaceld that is configured on the scheduling cell must be for a DCI format of multi-cell scheduling. Alternatively, the SS set with the same searchSpaceld that is configured on the scheduling cell may be configured with any DCI format for single-cell or multi-cell scheduling.

[0131] In one example, the DCI format for multi-cell scheduling may be configured to schedule two sets of cells respectively. The scheduling cell is included in the first set of cells. In this case, all necessary parameters in the SS set configuration of an SS set for a DCI format for multi-cell scheduling of the first set of cells can be configured in the configuration of the scheduling cell. Further, all necessary parameters in the SS set configuration of an SS set for a DCI format for multi-cell scheduling of the second set of cells can be configured in the configuration of one cell of the second set of cells The above two SS sets may or may not have the same searchSpaceld.

[0132] In one embodiment, all necessary parameters in the SS set configuration of an SS set with a searchSpaceld for a DCI format of multi-cell scheduling can be configured in the configuration of the scheduling cell. An SS set with the same searchSpaceld is not configured on a cell of the cells that can be scheduled by the DCI format if the cell is not the scheduling cell. This scheme may only be used for the case that the scheduling cell can also be scheduled by the DCI format. Alternatively, this scheme may only be used for the case that the scheduling cell cannot be scheduled by the DCI format. Alternatively, this scheme can be used no matter whether the scheduling cell can be scheduled by the DCI format or not.

[0133] In one embodiment, all necessary parameters in the SS set configuration of a SS set with a searchSpaceld for a DCI format of multi-cell scheduling, except for the parameter nrojCandidates, can be configured in the configuration of the scheduling cell. Alternatively, the parameter nrojCandidates can still be configured in the SS set configuration, but the number of PDCCH candidates for each aggregation level is set to 0. Alternatively, the parameter nrojCandidates can still be configured in the SS set configuration, but it is neglected by the UE. Specifically, all necessary parameters in the SS set configuration, except for nrojCandidates of the SS set, can be configured in the configuration of the scheduling cell.

[0134] Furthermore, a SS set with the same searchSpaceld and with the parameter nrojCandidates can be configured on one cell of the cells that can be configured or scheduled by the DCI format. This one cell is not the scheduling cell. In this way, the UE can monitor the SS set with the searchSpaceld on the scheduling cell with the number of PDCCH candidates obtained by nrojCandidates that is configured on the above one cell. The above one cell may be the cell with the lowest cell index in the cells that can be scheduled by the DCI format. Alternatively, the one cell can be selected by gNB implementation. In another option, the one cell can be configured by higher layers for multi-cell scheduling, which can be one of the cells configured for multi-cell scheduling or indicated in the carrier indication table. Furthermore, the one cell may or may not be the scheduling cell.

[0135] This scheme may only be used in the case that the scheduling cell can also be scheduled by the DCI format. Alternatively, this scheme may only be used in the case that the scheduling cell cannot be scheduled by the DCI format. Alternatively, this scheme can be used regardless of whether the scheduling cell can be scheduled by the DCI format or not.

[0136] In one embodiment, all necessary parameters in the SS set configuration including nrojCandidates of a SS set with a searchSpaceld for a DCI format of multi-cell scheduling can be configured in the configuration of scheduling cell. The SS set is only configured with the DCI format for multi-cell scheduling.

[0137] In one option, if the scheduling cell can be scheduled by the DCI format, a SS set with same searchSpaceld is not configured on a cell of the cells that can be configured or scheduled by the DCI format if the cell is not the scheduling cell. Therefore, UE can monitor the SS set with the searchSpaceld for the DCI format of multi-cell scheduling on the scheduling cell following the SS set configuration of the SS set of scheduling cell. Otherwise, if the scheduling cell cannot be scheduled by a DCI format for multi-cell scheduling, a SS set with the same searchSpaceld and with parameter nrofCandidates can be configured on one cell of the cells that can be scheduled by the DCI format. Consequently, UE can monitor the SS set with the searchSpaceld on the scheduling cell with number of PDCCH candidates obtained by nrofCandidates that is configured on the above one cell. The above one cell may be the cell with lowest cell index in the cells that can be scheduled by the DCI format. Alternatively, the one cell can be selected by gNB implementation. In another option, the one cell can be configured by higher layers for multi-cell scheduling, which can be one of the cells configured for multi-cell scheduling or indicated in the carrier indication table. Further, the one cell may or may not be the scheduling cell.

[0138] In another option, if a SS set with the same searchSpaceld and with parameter nrofCandidates is configured on one cell of the cells that can be configured or scheduled by a DCI format for multi-cell scheduling, a UE can monitor the SS set with the searchSpaceld on the scheduling cell with number of PDCCH candidates obtained by nrofCandidates that is configured on the one cell. The above one cell is not the scheduling cell. Otherwise, UE can monitor the SS set with the searchSpaceld on the scheduling cell following the SS set configuration of the SS set of scheduling cell. The above one cell may be the cell with lowest cell index in the cells that can be scheduled by the DCI format. Alternatively, the one cell can be selected by gNB implementation. In another option, the one cell can be configured by higher layers for multi-cell scheduling, which can be one of the cells configured for multi-cell scheduling or indicated in the carrier indication table. Further, the one cell may or may not be the scheduling cell.

[0139] In one embodiment, all necessary parameters in the SS set configuration including nrofCandidates of a SS set with a searchSpaceld for a DCI format of multi-cell scheduling can be configured in the configuration of scheduling cell. A SS set with same searchSpaceld can be still configured on other cells that can be scheduled by the scheduling cell. The SS set may be only configured with a DCI format for multi-cell scheduling. Alternatively, the SS set may be configured with both DCT format for multi-cell scheduling and DCT format for single-cell scheduling.

[0140] In one option, UE can monitor the SS set with the searchSpaceld for a DCI format of multi-cell scheduling on the scheduling cell following the SS set configuration of the SS set of scheduling cell. The parameter nrofCandidates of the SS set with same searchSpaceld that is configured on a cell other than the scheduling cell is used for single-cell scheduling of the cell.

[0141] In another option, the parameter nrofCandidates of the SS set with the same searchSpaceld that is configured on one cell that can be scheduled by the DCI format is used to determine the number of PDCCH candidates for the DCT format. The parameter nrofCandidates of the SS set with same searchSpaceld that is configured on other cells is used for single-cell scheduling. The above one cell may be the cell with lowest cell index in the above one or more cells. Alternatively, the one cell can be selected by gNB implementation. In another option, the one cell can be configured by higher layers for multi-cell scheduling, which can be one of the cells configured for multi-cell scheduling or indicated in the carrier indication table. Further, the one cell may or may not be the scheduling cell.

[0142] In another option, if the scheduling cell can be scheduled by the DCI format, UE can monitor the SS set with the searchSpaceld on the scheduling cell following the SS set configuration of the SS set of scheduling cell. The parameter nrofCandidates in the SS set with the same searchSpaceld that is configured on other cells is used for single-cell scheduling.

[0143] If the scheduling cell cannot be scheduled by the DCI format, the parameter nrofCandidates of the SS set with the same searchSpaceld that, is configured on one cell that can be scheduled by the DCI format is used to determine the number of PDCCH candidates for the DCI format. The parameter nrofCandidates of the SS set with same searchSpaceld that is configured on other cells is used for single-cell scheduling. The above one cell may be the cell with lowest cell index in the above one or more cells. Alternatively, the one cell can be selected by gNB implementation. In another option, the one cell can be configured by higher layers for multi-cell scheduling, which can be one of the cells configured for multi-cell scheduling or indicated in the carrier indication table. Further, the one cell may or may not be the scheduling cell.

[0144] In one example, if the SS set with a searchSpaceld can be used with both DCI format for multi-cell scheduling and DCI format for single-cell scheduling, the configuration of the SS set with same searchSpaceld in the configuration of a cell may include an indication on whether the configured nr of Candidates of the SS set is only for the DCI format for multi -cell scheduling, or only for the DCI format for single-cell scheduling of the cell, or for both.

[0145] In one example, if the SS set with a searchSpaceld can be used with both DCI format for multi-cell scheduling and DCI format for single-cell scheduling, the configuration of the SS set may include up to two nrofCandidates parameters. A first nrofCandidates parameter, if configured, is to indicate the number of PDCCH candidates for the DCI format for single-cell scheduling. A second nrofCandidates parameter, if configured, is to indicate the number of PDCCH candidates for the DCI format for multi-cell scheduling. Note: For the SS set with same searchSpaceld, the second nrofCandidates parameter may be only configured on one of the cells that can be scheduled by a DCI format for multi-cells scheduling.

[0146] In the above embodiments and options, if the parameter nrofCandidates for the SS set with a searchSpaceld for a DCI format of multi-cell scheduling is configured in the configuration of cell A, cell A could be referred as the reference cell for the DCI format.

[0147] In one option, if multiple DCI formats for multi-cell scheduling are configured on the scheduling cell, the multiple DCI formats may have the same reference cell. Alternatively, the reference cell can be separately determined for each cell of the multiple DCI formats.

[0148] In another option, a DCI format for multi-cell PDSCH scheduling and a DCI format for multi-cell PUSCH scheduling must have the same reference cell. Alternatively, the reference cell can be separately determined for a DCI format for multi-cell PDSCH scheduling and a DCI format for multi-cell PUSCH scheduling.

[0149] In another option, if the same set of cells can be scheduled by a DCI format for multi-cell PDSCH scheduling and a DCI format for multi -cell PUSCH scheduling, the two DCI formats must have the same reference cell. Alternatively, the reference cell can be separately determined for the two DCI formats.

[0150] Hashing function to map a SS set to CCEs

[0151] In NR, for a search space set s associated with CORESET p, the CCE indexes for aggregation level L corresponding to PDCCH candidate m_{s nci} of the search space set in slot

for an active DL BWP of a serving cell corresponding to carrier indicator field value n_CI are given by

where for any CSS,

for a USS, modD ,

for

pmod3 = 0 , A_p = 39829 for pmod3 = 1 , A_p = 39839 for pmod3 = 2 , and D = 65537; i = 0, -,L - 1;

N_CCE,P is the number of CCEs, numbered from 0 to N_{CCE p} — 1, in CORESET p and, if any, per RB set; n_CI is the carrier indicator field value if the UE is configured with a carrier indicator field by CrossCarrierSchedulingConfig for the serving cell on which PDCCH is monitored; otherwise, including for any CSS, n_CI = 0; is the number of PDCCH candidates the UE is

configured to monitor for aggregation level L of a search space set s for a serving cell corresponding to n_CI; for any CSS,

for a USS, is the maximum of over all configured n_CI values for a CCE

aggregation level L of search space set s ; the RNTI value used for n_RNTI is the C-RNTI.

[0152] For a SS set with DCI format for multi-cell scheduling, the parameter n_CI may be still defined as a index of a particular cell. Alternatively, the parameter n_cl may be a value configured for the cells that can be scheduled by the DCI format. For example, if a cell which is schedulable by multi -cell scheduling is also configured with single-cell scheduling, the parameter n_CI for multi-cell scheduling and for single-cell scheduling may be separately configured/d etermined .

[0153] In one embodiment, n_CI = 0 is assumed in the determination of CCE indexes for a SS set configured with a DCI format for multi-cell scheduling. is the number of PDCCH

candidates the UE is configured to monitor for aggregation level L for the DCI format for multi- cell scheduling of a search space set s;

[0154] In another embodiment, the value of n_cl can be configured by high layer in the determination of CCE indexes for a SS set configured with a DCI format for multi -cell scheduling. For example, the value of n_CI for the DCI format for multi-cell scheduling can be configured via CrossCarrierSchedulingConfig. is the number of PDCCH candidates the UE is configured

to monitor for aggregation level L for the DCI format for multi-cell scheduling of a search space set s;

[0155] In another embodiment, if n_CI and are configured for each cell that can be

scheduled by a DCI format for multi-cell scheduling, a PDCCH with the DCI format can be transmitted in any PDCCH candidate that is determined by the above formula with n_CI and

respectively.

[0156] In another embodiment, for a DCI format of multi-cell scheduling, the CCE indexes of the search space of the DCI format is determined by a value n_CI that is configured for a reference cell. For example, the reference cell may be the cell with lowest index that can be scheduled by the DCI format. Alternatively, the reference cell may be the scheduling cell on which the DCI format of multi-cell scheduling is transmitted. Alternatively, the reference cell may be the scheduling cell if the scheduling cell can be scheduled by the DCI format, otherwise, a scheduled cell, e.g., the cell with lowest index that can be scheduled by the DCI format. Alternatively, the reference cell may be the cell with lowest index other than the scheduling cell that can be scheduled by the DCI format. Alternatively, the reference cell can be configured by high layer signaling, e g., in the configuration of CrossCarrierSchedulingConfig or SearchSpace. Correspondingly,

may be configured for the reference cell too.

[0157] In another option, if the SS set of a DCI format for multi-cell scheduling is configured on a cell X of the cells that can be configured or scheduled by the DCI format, the above reference cell can be the cell X.

[0158] In another option, the above reference cell can be same as the reference cell A that is configured or determined in the SS set configuration of the SS set of the DCI format that is disclosed in aforementioned embodiments in the disclosure. Specifically, the configuration of the reference cell A includes the parameter nrofCandidates which configures the number of PDCCH candidates for the SS set. [0159] In the above options, if multiple DCI formats for multi-cell scheduling are configured on the scheduling cell, the above reference cell can be separately determined for each cell of the multiple DCI formats. Alternatively, the multiple DCI format may have the same reference cell.

[0160] In the above options, the above reference cell can be separately determined for a DCI format for multi-cell PDSCH scheduling and a DCI format for multi -cell PUSCH scheduling. For example, a cell can be defined as the reference cell for the DCI format for multi-cell PDSCH scheduling or the DCI format for multi-cell PUSCH scheduling, but not both. Alternatively, a DCI format for multi -cell PDSCH scheduling and a DCI format for multi -cell PUSCH scheduling must have the same reference cell.

[0161] In the above options, if the same set of cells can be scheduled by a DCI format for multi-cell PDSCH scheduling and a DCI format for multi-cell PUSCH scheduling, the above reference cell can be separately configured or determined for the two DCI formats. For example, a cell can be defined as the reference for only one of the two the DCI formats. Alternatively, the two DCI formats must have the same reference cell.

[0162] Total number of PDSCHs/PUSCHs under processing for a UE

[0163] In NR, for a scheduled cell and at any time, a UE expects to have received at most 16 PDCCHs for DCI formats with CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI scheduling 16 PDSCH receptions for which the UE has not received any corresponding PDSCH symbol and at most 16 PDCCHs for DCI formats with CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI scheduling 16 PUSCH transmissions for which the UE has not transmitted any corresponding PUSCH symbol.

[0164] In one option, if a DCI format for multi-cell scheduling is supported, a PDCCH with the DCI format can be counted as one PDCCH for each cell that is scheduled by the PDCCH. Consequently, for a scheduled cell and at any time, a UE expects to have received at most 16 PDCCHs for DCI formats with CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI scheduling 16 PDSCH receptions for which the UE has not received any corresponding PDSCH symbol and at most 16 PDCCHs for DCI formats with CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI scheduling 16 PUSCH transmissions for which the UE has not transmitted any corresponding PUSCH symbol.

[0165] In another option, if a DCI format for multi-cell scheduling is supported, a PDCCH with the DCT format can be counted as one PDCCH for each cell that is scheduled by the PDCCH. Consequently, the UE expects to have respectively received at most 16 ■

PDCCHs for

• DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or an MCS-C-RNTI scheduling 16 ■ N^ns PDSCH receptions for which the UE has not received any corresponding PDSCH symbol over all

downlink cells

• DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or an MCS-C-RNTI scheduling 16 ■

PUSCH transmissions for which the UE has not transmitted any corresponding PUSCH symbol over all N^_ls uplink cells where is the number of downlink cells which determines the capability for PDCCH monitoring over a group of cells.

[0166] In the above options, for a cell that is scheduled by a PDCCH with a DCI format for multi-cell scheduling, if the scheduled PDSCH or PUSCH on the cell by the PDCCH is invalid, e.g., due to overlap with a UL or DL symbol configured by the semi-static TDD configuration or SSB symbols, the PDCCH and the corresponding invalid PDSCH/PUSCH is not counted toward the limitation of 16 PDCCHs or 16 PDSCHs/PUSCHs for the cell. Alternatively, in the above condition, the PDCCH and the corresponding invalid PDSCH/PUSCH is still counted toward the limitation of 16 PDCCHs and 16 PDSCHs/PUSCHs for the cell.

[0167] Example Procedures

[0168] In some embodiments, the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of Figs. 1-3, or some other figure herein, may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof.

[0169] According to an embodiment, a process to be performed at an apparatus of a NR UE includes identifying a received physical downlink control channel (PDCCH) transmission, identifying that the PDCCH transmission includes scheduling information related to one or more physical uplink shared channel (PUSCH) transmissions and/or one or more physical downlink shared channel (PDSCH) transmissions in more than one cell, and transmitting one or more PUSCH transmissions and/or processing one or more PDSCH transmissions based on the scheduling information. [0170] According to an embodiment, a process to be performed at an apparatus of a NR gNB includes: identifying scheduling information related to one or more physical uplink shared channel (PUSCH) transmissions and/or one or more physical downlink shared channel (PDSCH) transmissions in more than one cell, generating a physical downlink control channel (PDCCH) based on the scheduling information, and transmitting the PDCCH transmission to a user equipment (UE).

[0171] In some embodiments, the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of Figs. 1-4, or some other figure herein, may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof.

[0172] One such process is depicted in Fig. 11. Specifically, Fig. 11 relates to a method to be performed by a base station, one or more elements of a base station, and/or an electronic device that includes a base station. The process may include, at operation 1102, identifying scheduling information for a plurality of cells and related to one or more shared channel (SCH) transmissions, the one or more SCH transmissions including one or more physical uplink shared channel (PUSCH) transmissions or one or more physical downlink shared channel (PDSCH) transmissions; at operation 1104 generating a physical downlink control channel (PDCCH) based on the scheduling information, at operation 1106, sending the PDCCH for transmission to a user equipment (UE) on a single scheduling cell of the plurality of cells.

[0173] Another such process is depicted in Fig. 12. Specifically, Figure 12 relates to a method to be performed by a user equipment (UE), one or more elements of a UE, and/or an electronic device that includes a UE. The process may include, at operation 1202, identifying a physical downlink control channel (PDCCH) transmission from a NR Node B (gNB); at operation 1204, determining, from the PDCCH, scheduling information for a plurality of cells and related to one or more shared channel (SCH) transmissions, the one or more SCH transmissions including one or more physical uplink shared channel (PUSCH) transmissions or one or more physical downlink shared channel (PDSCH) transmissions’ at operation 1206, receiving the one or more PDSCH transmissions or sending for transmission the one or more PUSCH transmissions based on the scheduling information.

[0174] For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.

[0175] For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.

[0176] Examples:

[0177] Example 1 includes an apparatus of a New Radio (NR) Node B (gNB) including a memory storing instructions, and one or more processors coupled to the memory to execute the instructions to perform operations including: identifying scheduling information for a plurality of cells and related to one or more SCH (SCH) transmissions, the one or more SCH transmissions including one or more physical uplink SCH (PUSCH) transmissions or one or more physical downlink SCH (PDSCH) transmissions; generating a physical downlink control channel (PDCCH) based on the scheduling information; and sending the PDCCH for transmission to a user equipment (UE) on a single scheduling cell of the plurality of cells.

[0178] Example 2 includes the subject matter of Example 1, wherein generating the PDCCH includes generating a single DCI format for multi -cell scheduling.

[0179] Example 2.5 includes the subject matter of Example 2, wherein the plurality of cells are divided into multiple sets and each set has its own DCI format for multi-cell scheduling.

[0180] Example 3 includes the subject matter of Example 2, wherein the scheduling information is a first scheduling information, the one or more SCHs are one or more first SCHs, the PDCCH is a first PDCCH , the operations further including: identifying second scheduling information for a single cell of the plurality of cells, and related to a second CH transmission; generating a second PDCCH based on the second scheduling information; and sending the second PDCCH for transmission to the UE on the scheduling cell, the second PDCCH including a DCI format for single-cell scheduling.

[0181] Example 4 includes the subject matter of Example 3, the operations further including: generating a downlink control information (DCI) configuration message to the UE to configure the UE to monitor, on the scheduling cell, for a DCI format for multi -cell scheduling and for a DCI format for single-cell scheduling; and sending the DCI configuration message for transmission to the UE.

[0182] Example 5 includes the subject matter of Example 4, wherein the DCI configuration message is to configure the UE to monitor, in a same OFDM symbol or in a same set of OFDM symbols, for the DCI format for multi -cell scheduling and for the DCI format for single-cell scheduling.

[0183] Example 6 includes the subject matter of Example 5, wherein the DCI configuration message to the UE further includes information for search space (SS) set configuration of the scheduling cell, the information for SS set configuration including a number of candidates (rirofcandidates)' parameter and a SS identification (searchSpaceld) parameter for the DCI format for multi-cell scheduling.

[0184] Example 7 includes the subject matter of Example 6, wherein the operations include generating the DCI configuration message that includes the SS set configuration of the scheduling cell only with DCI format configuration for the DCI format for multi-cell scheduling. [0185] Example 8 includes the subject matter of Example 6, wherein the nrofcandidates parameter corresponds to a number of PDCCH candidates that the UE is to be configured to monitor for.

[0186] Example 9 includes the subject matter of any one of Examples 6-8, the operations further including configuration a SS set configuration of a non-scheduling cell of the plurality of cells for multi-cell scheduling using higher-layer signaling.

[0187] Example 10 includes the subject matter of any one of Examples 6-8, wherein: the information for SS set configuration of the scheduling cell is first information for SS set configuration; the nrofcandidates parameter is a first nrofcandidates parameter; and the SS set configuration of the scheduling cell includes second information, the second information being for SS set configuration for a non-scheduling cell of the plurality of cells and including a same searchSpaceld parameter as in the first information.

[0188] Example 11 includes the subject matter of any one of Examples 6-8, wherein: the information for SS set configuration of the scheduling cell is first information for SS set configuration; the nr of candidates parameter is a first nr of candidates parameter; and the SS set configuration of the scheduling cell includes second information, the second information being for SS set configuration for a non-scheduling cell of the plurality of cells and including a different searchSpaceld parameter from the first information.

[0189] Example 12 includes the subject matter of any one of Examples 6-8, wherein, in response to a determination that the UE is configured with a carrier indicator field for the serving cell, the one or more processors are to generate the DCI configuration message to include information for search space (SS) set configuration for the UE, the information for SS set configuration based on a carrier indicator field value _na that is greater than zero and that is configured for the plurality of cells.

[0190] Example 13 includes the subject matter of any one of Examples 6-8, further including a Radio Frequency (RF) interface, and a front end module coupled to the RF interface. [0191] Example 14 includes the subject matter of Example 13, further including one or more antennas coupled to the front end module to transmit the PDCCH.

[0192] Example 15 includes a method to be performed at a device of a New Radio (NR) Node B (gNB), the method including: identifying scheduling information for a plurality of cells and related to one or more shared channel (SCEI) transmissions, the one or more SCH transmissions including one or more physical uplink shared channel (PUSCH) transmissions or one or more physical downlink shared channel (PDSCH) transmissions; generating a physical downlink control channel (PDCCH) based on the scheduling information; and sending the PDCCH for transmission to a user equipment (UE) on a single scheduling cell of the plurality of cells.

[0193] Example 16 includes the subject matter of Example 15, wherein generating the PDCCH includes generating a single DCI format for multi -cell scheduling.

[0194] Example 16.5 includes the subject matter of Example 16, wherein the plurality of cells are divided into multiple sets and each set has its own DCI format for multi-cell scheduling. [0195] Example 17 includes the subject matter of Example 16, wherein the scheduling information is a first scheduling information, the one or more SCH transmissions are one or more first SCH transmissions, the PDCCH is a first PDCCH , the method further including: identifying second scheduling information for a single cell of the plurality of cells, and related to one or more second shared channel transmissions; generating a second PDCCH based on the second scheduling information; and sending the second PDCCH for transmission to the UE on the scheduling cell, the second PDCCH including a DCI format for single-cell scheduling.

[0196] Example 18 includes the subject matter of Example 17, the method further including: generating a downlink control information (DCI) configuration message to the UE to configure the UE to monitor, on the scheduling cell, for a DCI format for multi -cell scheduling and for a DCI format for single-cell scheduling; and sending the DCI configuration message for transmission to the UE.

[0197] Example 19 includes the subject matter of Example 18, wherein the DCI configuration message is to configure the UE to monitor, in a same OFDM symbol or in a same set of OFDM symbols, for the DCI format for multi -cell scheduling and for the DCI format for single-cell scheduling.

[0198] Example 20 includes the subject matter of Example 19, wherein the DCI configuration message to the UE further includes information for search space (SS) set configuration of the scheduling cell, the information for SS set configuration including a number of candidates (profcandidates) parameter and a SS identification (searchSpaceld) parameter for the DCI format for multi-cell scheduling.

[0199] Example 21 includes the subject matter of Example 20, further including generating the DCI configuration message that includes the SS set configuration of the scheduling cell only with DCI format configuration for the DCI format for multi -cell scheduling. [0200] Example 22 includes the subject matter of Example 20, wherein the nrofcandidates parameter corresponds to a number of PDCCH candidates that the UE is to be configured to monitor for.

[0201] Example 23 includes the subject matter of any one of Examples 20-22, further including configuration a SS set configuration of a non-scheduling cell of the plurality of cells for multi-cell scheduling using higher-layer signaling. [0202] Example 24 includes the subject matter of any one of Examples 20-22, wherein: the information for SS set configuration of the scheduling cell is first information for SS set configuration; the nrofcandidates parameter is a first nrofcandidates parameter; and the SS set configuration of the scheduling cell includes second information, the second information being for SS set configuration for a non-scheduling cell of the plurality of cells and including a same searchSpaceld parameter as in the first information.

[0203] Example 25 includes the subject matter of any one of Examples 20-22, wherein: the information for SS set configuration of the scheduling cell is first information for SS set configuration; the nrofcandidates parameter is a first nrofcandidates parameter; and the SS set configuration of the scheduling cell includes second information, the second information being for SS set configuration for a non-scheduling cell of the plurality of cells and including a different searchSpaceld parameter from the first information.

[0204] Example 26 includes the subject matter of any one of Examples 20-22, the method including, in response to a determination that the UE is configured with a carrier indicator field for the serving cell, generating the DCI configuration message to include information for search space (SS) set configuration for the UE, the information for SS set configuration based on a carrier indicator field value _nci that is greater than zero and that is configured for the plurality of cells.

[0205] Example 27 includes one or more non-transitory computer-readable media comprising instructions to cause one or more processors of a New Radio (NR) Node B (gNB), upon execution of the instructions by to perform operations including: identifying scheduling information for a plurality of cells and related to one or more shared channel (SCH) transmissions, the one or more SCH transmissions including one or more physical uplink shared channel (PUSCH) transmissions or one or more physical downlink shared channel (PDSCH) transmissions; generating a physical downlink control channel (PDCCH) based on the scheduling information; and sending the PDCCH for transmission to a user equipment (UE) on a single scheduling cell of the plurality of cells.

[0206] Example 28 includes the subject matter of Example 27, wherein generating the PDCCH includes generating a single DCI format for multi -cell scheduling.

[0207] Example 28.5 includes the subject matter of Example 28, wherein the plurality of cells are divided into multiple sets and each set has its own DCI format for multi-cell scheduling. [0208] Example 29 includes the subject matter of Example 28, wherein the scheduling information is a first scheduling information, the one or more SCH transmissions are one or more first SCH transmissions, the PDCCH is a first PDCCH , the operations further including: identifying second scheduling information for a single cell of the plurality of cells, and related to one or more second shared channel transmissions; generating a second PDCCH based on the second scheduling information; and sending the second PDCCH for transmission to the UE on the scheduling cell, the second PDCCH including a DCI format for single-cell scheduling.

[0209] Example 30 includes the subject matter of Example 29, the operations further including: generating a downlink control information (DCT) configuration message to the UE to configure the UE to monitor, on the scheduling cell, for a DCI format for multi-cell scheduling and for a DCI format for single-cell scheduling; and sending the DCI configuration message for transmission to the UE.

[0210] Example 31 includes the subject matter of Example 30, wherein the DCI configuration message is to configure the UE to monitor, in a same OFDM symbol or in a same set of OFDM symbols, for the DCI format for multi -cell scheduling and for the DCI format for single-cell scheduling.

[0211] Example 32 includes the subject matter of Example 31, wherein the DCI configuration message to the UE further includes information for search space (SS) set configuration of the scheduling cell, the information for SS set configuration including a number of candidates (profcandidates) parameter and a SS identification (searchSpaceld) parameter for the DCI format for multi-cell scheduling.

[0212] Example 33 includes the subject matter of Example 32, further including generating the DCI configuration message that includes the SS set configuration of the scheduling cell only with DCI format configuration for the DCI format for multi -cell scheduling. [0213] Example 34 includes the subject matter of Example 32, wherein the nrofcandidates parameter corresponds to a number of PDCCH candidates that the UE is to be configured to monitor for.

[0214] Example 35 includes the subject matter of any one of Examples 32-34, further including configuration a SS set configuration of a non-scheduling cell of the plurality of cells for multi-cell scheduling using higher-layer signaling. [0215] Example 36 includes the subject matter of any one of Examples 32-34, wherein: the information for SS set configuration of the scheduling cell is first information for SS set configuration; the nrofcandidates parameter is a first nrofcandidates parameter; and the SS set configuration of the scheduling cell includes second information, the second information being for SS set configuration for a non-scheduling cell of the plurality of cells and including a same searchSpaceld parameter as in the first information.

[0216] Example 37 includes the subject matter of any one of Examples 32-34, wherein: the information for SS set configuration of the scheduling cell is first information for SS set configuration; the nrofcandidates parameter is a first nrofcandidates parameter; and the SS set configuration of the scheduling cell includes second information, the second information being for SS set configuration for a non-scheduling cell of the plurality of cells and including a different searchSpaceld parameter from the first information.

[0217] Example 38 includes the subject matter of any one of Examples 32-34, the operations including, in response to a determination that the UE is configured with a carrier indicator field for the serving cell, generating the DCI configuration message to include information for search space (SS) set configuration for the UE, the information for SS set configuration based on a carrier indicator field value _nci that is greater than zero and that is configured for the plurality of cells.

[0218] Example 39 includes an apparatus of a New Radio (NR) User Equipment (UE) including a memory storing instructions, and one or more processors coupled to the memory to execute the instructions to perform operations including: identifying a physical downlink control channel (PDCCH) transmission from a NR Node B (gNB); determining, from the PDCCH, scheduling information for a plurality of cells and related to one or more shared channel (SCH) transmissions, the one or more SCH transmissions including one or more physical uplink shared channel (PUSCH) transmissions or one or more physical downlink shared channel (PDSCH) transmissions; and receiving the one or more PDSCH transmissions or sending for transmission the one or more PUSCH transmissions based on the scheduling information.

[0219] Example 40 includes the subject matter of Example 39, wherein the PDCCH includes a single DCI format for multi-cell scheduling.

[0220] Example 40.1 includes the subject matter of Example 40, wherein the plurality of cells are divided into multiple sets and each set has its own DCI format for multi-cell scheduling. [0221] Example 41 includes the subject matter of Example 40, wherein the scheduling information is a first scheduling information, the one or more SCH transmissions are one or more first SCH transmissions, the PDCCH is a first PDCCH , the operations further including: identifying a second PDCCH transmission on the scheduling cell, the second PDCCH transmission related to a second CH transmission; determining, from the second PDCCH, second scheduling information for a single cell of the plurality of cells and related to one or more second shared channel transmissions; and receiving one or more second PDSCH transmissions or sending for transmission the one or more PUSCH transmissions based on the scheduling information.

[0222] Example 42 includes the subject matter of Example 41, the operations further including, prior to accessing the first PDCCH: accessing a downlink control information (DCI) configuration message from the gNB; and configuring the UE to monitor, based on the DCI configuration and on the scheduling cell, for a DCI format for multi-cell scheduling and for a DCI format for single-cell scheduling.

[0223] Example 43 includes the subject matter of Example 42, wherein configuring the UE includes using the DCI configuration message to configure the UE to monitor, in a same OFDM symbol or in a same set of OFDM symbols, for the DCI format for multi -cell scheduling and for the DCI format for single-cell scheduling.

[0224] Example 44 includes the subject matter of Example 43, wherein configuring the UE further includes configuring the UE based on accessing information in the DCI configuration message for search space (SS) set configuration of the scheduling cell, the information for SS set configuration including a number of candidates (profcandidates) parameter and a SS identification (searchSpaceld) parameter for the DCI format for multi-cell scheduling.

[0225] Example 45 includes the subject mater of Example 44, wherein the SS set configuration of the scheduling cell corresponds only to DCI format configuration for the DCI format for multi-cell scheduling.

[0226] Example 46 includes the subject matter of Example 44, wherein the nrofcandidates parameter corresponds to a number of PDCCH candidates that the UE is to be configured to monitor for. [0227] Example 47 includes the subject matter of any one of Examples 44-46, wherein configuring the UE further includes configuration a SS set configuration of a non-scheduling cell of the plurality of cells for multi-cell scheduling by accessing higher-layer signaling.

[0228] Example 48 includes the subject matter of any one of Examples 44-46, wherein: the information for SS set configuration of the scheduling cell is first information for SS set configuration; the nrofcandidates parameter is a first nrofcandidates parameter; and the SS set configuration of the scheduling cell includes second information, the second information being for SS set configuration for a non-scheduling cell of the plurality of cells and including a same searchSpaceld parameter as in the first information.

[0229] Example 49 includes the subject matter of any one of Examples 44-46, wherein: the information for SS set configuration of the scheduling cell is first information for SS set configuration; the nrofcandidates parameter is a first nrofcandidates parameter; and the SS set configuration of the scheduling cell includes second information, the second information being for SS set configuration for a non-scheduling cell of the plurality of cells and including a different searchSpaceld parameter from the first information.

[0230] Example 50 includes the subject matter of any one of Examples 44-46, wherein the UE is configured with a carrier indicator field for the serving cell, and wherein configuring the UE further includes configuring the UE based on the DCI configuration message including information for search space (SS) set configuration for the UE, the information for SS set configuration based on a carrier indicator field value _nci that is greater than zero and that is configured for the plurality of cells.

[0231] Example 51 includes the subject matter of any one of Examples 44-46, further including a Radio Frequency (RF) interface, and a front end module coupled to the RF interface. [0232] Example 52 includes the subject matter of Example 51, further including one or more antennas coupled to the front end module to transmit the PDCCH.

[0233] Example 53 includes a method to be implemented at an apparatus of a New Radio (NR) User Equipment (UE), the method including: identifying a physical downlink control channel (PDCCH) transmission from a NR Node B (gNB); determining, from the PDCCH, scheduling information for a plurality of cells and related to one or more shared channel (SCH) transmissions, the one or more SCH transmissions including one or more physical uplink shared channel (PUSCH) transmissions or one or more physical downlink shared channel (PDSCH) transmissions; and receiving the one or more PDSCH transmissions or sending for transmission the one or more PUSCH transmissions based on the scheduling information.

[0234] Example 54 includes the subject matter of Example 53, wherein the PDCCH includes a single DCI format for multi-cell scheduling.

[0235] Example 54.5 includes the subject matter of Example 54, wherein the plurality of cells are divided into multiple sets and each set has its own DCI format for multi-cell scheduling. [0236] Example 55 includes the subject matter of Example 54, wherein the scheduling information is a first scheduling information, the one or more SCH transmissions are one or more first SCH transmissions, the PDCCH is a first PDCCH , the method further including: identifying a second PDCCH transmission on the scheduling cell, the second PDCCH transmission related to a second CH transmission; determining, from the second PDCCH, second scheduling information for a single cell of the plurality of cells and related to one or more second shared channel transmissions; and receiving one or more second PDSCH transmissions or sending for transmission the one or more PUSCH transmissions based on the scheduling information.

[0237] Example 56 includes the subject matter of Example 55, the method further including, prior to accessing the first PDCCH: accessing a downlink control information (DCI) configuration message from the gNB; and configuring the UE to monitor, based on the DCI configuration and on the scheduling cell, for a DCI format for multi-cell scheduling and for a DCI format for single-cell scheduling.

[0238] Example 57 includes the subject matter of Example 56, wherein configuring the UE includes using the DCI configuration message to configure the UE to monitor, in a same OFDM symbol or in a same set of OFDM symbols, for the DCI format for multi -cell scheduling and for the DCI format for single-cell scheduling.

[0239] Example 58 includes the subject matter of Example 57, wherein configuring the UE further includes configuring the UE based on accessing information in the DCI configuration message for search space (SS) set configuration of the scheduling cell, the information for SS set configuration including a number of candidates (profcandidates} parameter and a SS identification (searchSpaceld) parameter for the DCI format for multi-cell scheduling.

[0240] Example 59 includes the subject matter of Example 58, wherein the SS set configuration of the scheduling cell corresponds only to DCI format configuration for the DCI format for multi-cell scheduling. [0241] Example 60 includes the subject matter of Example 58, wherein the nrofcandidates parameter corresponds to a number of PDCCH candidates that the UE is to be configured to monitor for.

[0242] Example 61 includes the subject matter of any one of Examples 58-60, wherein configuring the UE further includes configuration a SS set configuration of a non-scheduling cell of the plurality of cells for multi-cell scheduling by accessing higher-layer signaling.

[0243] Example 62 includes the subject matter of any one of Examples 58-60, wherein: the information for SS set configuration of the scheduling cell is first information for SS set configuration; the nrofcandidates parameter is a first nrofcandidates parameter; and the SS set configuration of the scheduling cell includes second information, the second information being for SS set configuration for a non-scheduling cell of the plurality of cells and including a same searchSpaceld parameter as in the first information.

[0244] Example 63 includes the subject matter of any one of Examples 58-60, wherein: the information for SS set configuration of the scheduling cell is first information for SS set configuration; the nrofcandidates parameter is a first nrofcandidates parameter; and the SS set configuration of the scheduling cell includes second information, the second information being for SS set configuration for a non-scheduling cell of the plurality of cells and including a different searchSpaceld parameter from the first information.

[0245] Example 64 includes the subject matter of any one of Examples 58-60, wherein the UE is configured with a carrier indicator field for the serving cell, and wherein configuring the UE further includes configuring the UE based on the DCI configuration message including information for search space (SS) set configuration for the UE, the information for SS set configuration based on a carrier indicator field value „CL that is greater than zero and that is configured for the plurality of cells.

[0246] Example 65 includes one or more non-transitory computer-readable media comprising instructions to cause one or more processors of a New Radio (NR) User Equipment (UE), upon execution of the instructions by to perform operations including: identifying a physical downlink control channel (PDCCH) transmission from a NR Node B (gNB); determining, from the PDCCH, scheduling information for a plurality of cells and related to one or more shared channel (SCH) transmissions, the one or more SCH transmissions including one or more physical uplink shared channel (PUSCH) transmissions or one or more physical downlink shared channel (PDSCH) transmissions; and receiving the one or more PDSCH transmissions or sending for transmission the one or more PUSCH transmissions based on the scheduling information.

[0247] Example 66 includes the subject matter of Example 65, wherein the PDCCH includes a single DCI format for multi-cell scheduling.

[0248] Example 66.5 includes the subject matter of Example 66, wherein the plurality of cells are divided into multiple sets and each set has its own DCI format for multi-cell scheduling. [0249] Example 67 includes the subject matter of Example 66, wherein the scheduling information is a first scheduling information, the one or more SCH transmissions are one or more first SCH transmissions, the PDCCH is a first PDCCH , the operations further including: identifying a second PDCCH transmission on the scheduling cell, the second PDCCH transmission related to a second CH transmission; determining, from the second PDCCH, second scheduling information for a single cell of the plurality of cells and related to one or more second shared channel transmissions; and receiving one or more second PDSCH transmissions or sending for transmission the one or more PUSCH transmissions based on the scheduling information.

[0250] Example 68 includes the subject matter of Example 67, the operations further including, prior to accessing the first PDCCH: accessing a downlink control information (DCI) configuration message from the gNB; and configuring the UE to monitor, based on the DCI configuration and on the scheduling cell, for a DCI format for multi-cell scheduling and for a DCI format for single-cell scheduling.

[0251] Example 69 includes the subject matter of Example 68, wherein configuring the UE includes using the DCI configuration message to configure the UE to monitor, in a same OFDM symbol or in a same set of OFDM symbols, for the DCI format for multi -cell scheduling and for the DCI format for single-cell scheduling.

[0252] Example 70 includes the subject matter of Example 69, wherein configuring the UE further includes configuring the UE based on accessing information in the DCI configuration message for search space (SS) set configuration of the scheduling cell, the information for SS set configuration including a number of candidates (nrofcandidales) parameter and a SS identification (searchSpaceld) parameter for the DCI format for multi-cell scheduling. [0253] Example 71 includes the subject matter of Example 70, wherein the SS set configuration of the scheduling cell corresponds only to DCI format configuration for the DCI format for multi-cell scheduling.

[0254] Example 72 includes the subject matter of Example 70, wherein the nrofcandidates parameter corresponds to a number of PDCCH candidates that the UE is to be configured to monitor for.

[0255] Example 73 includes the subject matter of any one of Examples 70-72, wherein configuring the UE further includes configuration a SS set configuration of a non-scheduling cell of the plurality of cells for multi-cell scheduling by accessing higher-layer signaling

[0256] Example 74 includes the subject matter of any one of Examples 70-72, wherein: the information for SS set configuration of the scheduling cell is first information for SS set configuration; the nrofcandidates parameter is a first nrofcandidates parameter; and the SS set configuration of the scheduling cell includes second information, the second information being for SS set configuration for a non-scheduling cell of the plurality of cells and including a same searchSpaceld parameter as in the first information.

[0257] Example 75 includes the subject matter of any one of Examples 70-72, wherein: the information for SS set configuration of the scheduling cell is first information for SS set configuration; the nrofcandidates parameter is a first nrofcandidates parameter; and the SS set configuration of the scheduling cell includes second information, the second information being for SS set configuration for a non-scheduling cell of the plurality of cells and including a different searchSpaceld parameter from the first information.

[0258] Example 76 includes the subject matter of any one of Examples 70-72, wherein the UE is configured with a carrier indicator field for the serving cell, and wherein configuring the UE further includes configuring the UE based on the DCI configuration message including information for search space (SS) set configuration for the UE, the information for SS set configuration based on a carrier indicator field value _ncL that is greater than zero and that is configured for the plurality of cells.

[0259] Example 77 includes a machine-readable medium including code which, when executed, is to cause a machine to perform Example X includes the subject matter of any one of Examples 15-26 or 53-64. [0260] Example 78 includes an apparatus including means to perform Example X includes the subject matter of any one of Examples 15-26 or 53-64.

[0261] Example Al includes the system and method of wireless communication for PDCCH transmission with multi-cell scheduling: receiving, by UE, the configuration on the physical downlink control channel (PDCCH) monitoring; and detecting, by UE, a PDCCH that is used schedule physical uplink shared channel (PUSCH) or physical downlink shared channel (PDSCH) in more than one cell.

[0262] Example A2 includes the method of example 1, and/or some other example herein, wherein one DC1 format for multi-cell PDSCH or PUSCH scheduling from the scheduling cell is configured to schedule all the cells in a set of cells.

[0263] Example A3 includes the method of example 1, and/or some other example herein, wherein one DCI format for multi-cell PDSCH or PUSCH scheduling from the scheduling cell is configured to only schedule a subset of a set of cells.

[0264] Example A4 includes the method of example 1, and/or some other example herein, wherein for a set of configured serving cells, multiple DCI formats for multi-cell PDSCH or PUSCH scheduling from the scheduling cell are configured, with each of the multiple DCI formats schedules a subset of the set of cells

[0265] Example A4.5 includes the method of example 1, and/or some other example herein, wherein multiple DCI formats for multi-cell PDSCH or PUSCH scheduling from the scheduling cell are configured based on different configurations a DCI format defined in the relevant 3 GPP specifications.

[0266] Example A5 includes the method of examples 3 or 4, and/or some other example herein, wherein for a cell that is not schedulable by the DCI format for multi-cell scheduling, a DCI format for single-cell scheduling is configured on the scheduling cell

[0267] Example A6 includes the method of examples 3 or 4, and/or some other example herein, wherein for a cell that is schedulable by a DCI format for multi-cell scheduling, a DCI format for single-cell scheduling is configured on the scheduling cell.

[0268] Example A7 includes the method of examples 3 or 4, and/or some other example herein, wherein UE expects that a cell in the set of cells is scheduled by at least one DCI format for multi-cell scheduling from the scheduling cell. [0269] Example A8 includes the method of examples 3 or 4, and/or some other example herein, wherein for a cell that is schedulable by a DCI format for multi-cell scheduling, the UE does not expect to be configured with a DCI format for single-cell scheduling is configured on the scheduling cell.

[0270] Example A9 includes the method of example 6 or some other example herein, wherein the DCI format for multi-cell scheduling and the DCI format for single-cell cross-carrier scheduling are configured on different scheduling cell(s).

[0271] Example A10 includes the method of example 9 or some other example herein, wherein a limitation applies for the PDCCH monitoring for a cell that can be scheduled by a DCI format for multi-cell PDSCH or PUSCH scheduling and by a DCI format for single-cell PDSCH or PUSCH scheduling from a scheduling cell.

[0272] Example Al 1 includes the method of example 9 or some other example herein, wherein a limitation applies for the PDCCH monitoring for a cell that can be scheduled by DCI formats on two scheduling cells.

[0273] Example A12 includes the method of example 1 or some other example herein, wherein all necessary parameters in the SS set configuration of a SS set for a DCI format of multicell scheduling are configured in the configuration of one cell that is schedulable by the DCI format.

[0274] Example Al 3 includes the method of example 1 or some other example herein, wherein all necessary parameters in the SS set configuration of a SS set for a DCI format of multicell scheduling are configured in the configuration of scheduling cell.

[0275] Example A14 includes the method of example 1 or some other example herein, wherein the SS set configuration except for the parameter nrofCandidates of a SS set for a DCI format of multi-cell scheduling is configured in the configuration of scheduling cell.

[0276] Example Al 5 includes the method of example 1 or some other example herein, wherein if the scheduling cell is schedulable by the DCI format for multi-cell scheduling, a UE monitors the SS set for the DCI format on the scheduling cell following the SS set configuration of the SS set of scheduling cell. Otherwise, the UE monitors the SS set with the searchSpaceld on the scheduling cell with number of PDCCH candidates obtained by nrofCandidates that is configured on one cell that is schedulable by the DCI format. [0277] Example Al 6 includes the method of example 1 or some other example herein, wherein if a SS set with a searchSpaceld and with parameter nrofCandidates for a DCI format of multi-cell scheduling is configured on one cell that is schedulable by the DCI format, a UE monitors the SS set with the searchSpaceld on the scheduling cell with number of PDCCH candidates obtained by nrofCandidates that is configured on the one cell.

[0278] Example A17 includes the method of examples 15 or 16 or some other example herein, wherein the configuration of the SS set includes an indication on whether the configured nrofCandidates of the SS set is only for the DCI format for multi-cell scheduling, or only for the DCI format for single-cell scheduling of the cell, or for both.

[0279] Example Al 8 includes the method of examples 15 or 16 or some other example herein, wherein the configuration of the SS set includes up to two nrofCandidates parameters.

[0280] The method of claim 1, in the determination

[0281] Example Al 9 includes the method of example 1, and/or some other example herein, wherein in the determination of CCE indexes for a SS set configured with a DCI format for multicell scheduling, the parameter n_cl = 0.

[0282] Example A20 includes the method of example 1 , and/or some other example herein, wherein in the determination of CCE indexes for a SS set configured with a DCI format for multicell scheduling, the parameter n_CI is configured by high layer.

[0283] Example A21 includes the method of example 1 or some other example herein, wherein the determination of CCE indexes for a SS set configured with a DCI format for multicell scheduling, the parameter n_CI is configured for a reference cell.

[0284] Example A22 includes the method of example 21 or some other example herein, wherein the reference cell is configured with the parameter nrofCandidates which configures the number of PDCCH candidates for the SS set.

[0285] Example A23 includes the method of example 1, and/or some other example herein, wherein a PDCCH with a DCI format for multi-cell scheduling is counted as one PDCCH for each cell that is scheduled by the PDCCH when counting the number of PDCCHs and the scheduled PDSCHs.

[0286] Example A24 includes a method to be performed by a user equipment (UE), one or more elements of a UE, and/or an electronic device that includes a UE, wherein the method comprises: identifying a received physical downlink control channel (PDCCH) transmission; identifying that the PDCCH transmission includes scheduling information related to one or more physical uplink shared channel (PUSCH) transmissions and/or one or more physical downlink shared channel (PDSCH) transmissions in more than one cell; and transmitting one or more PUSCH transmissions and/or processing one or more PDSCH transmissions based on the scheduling information.

[0287] Example Bl may include an apparatus comprising means to perform one or more elements of a method described in or related to any of the method Examples above, or any other method or process described herein.

[0288] Example B2 may include one or more non -transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of the method Examples above, or any other method or process described herein. [0289] Example B3 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of the method Examples above, or any other method or process described herein.

[0290] Example B4 may include a method, technique, or process as described in or related to any of the method Examples above, or portions or parts thereof.

[0291] Example B5 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of the method Examples above, or portions thereof.

[0292] Example B6 may include a signal as described in or related to any of the method Examples above, or portions or parts thereof.

[0293] Example B7 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of the method Examples above, or portions or parts thereof, or otherwise described in the present disclosure.

[0294] Example B8 may include a signal encoded with data as described in or related to any of the method Examples above, or portions or parts thereof, or otherwise described in the present disclosure. [0295] Example B9 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of the method Examples above, or portions or parts thereof, or otherwise described in the present disclosure.

[0296] Example BIO may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of the method Examples above, or portions thereof.

[0297] Example Bl l may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of the method Examples above, or portions thereof.

[0298] Example B12 may include a signal in a wireless network as shown and described herein.

[0299] Example B13 may include a method of communicating in a wireless network as shown and described herein.

[0300] Example B14 may include a system for providing wireless communication as shown and described herein.

[0301] Example B 15 may include a device for providing wireless communication as shown and described herein.

[0302] Any of the above-described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0303] Terminology

[0304] For the purposes of the present document, the following terms and definitions are applicable to the examples and embodiments discussed herein.

[0305] The term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

[0306] The term “processor circuitry” as used herein refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data. Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store program and data information. The term “processor circuitry” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a singlecore processor, a dual-core processor, a triple-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and/or functional processes. Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, orthe like. The one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators. The terms “application circuitry” and/or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.” [0307] The term “interface circuitry” as used herein refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “interface circuitry” may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, and/or the like.

[0308] The term “user equipment” or “UE” as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network. The term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.

[0309] The term “network element” as used herein refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services. The term “network element” may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and/or the like.

[0310] The term “computer system” as used herein refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled with one another and configured to share computing and/or networking resources.

[0311] The term “appliance,” “computer appliance,” or the like, as used herein refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource. A “virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource.

[0312] The term “resource” as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, and/or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, and/or the like. A “hardware resource” may refer to compute, storage, and/or network resources provided by physical hardware element(s). A “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devices/sy stems via a communications network. The term “system resources” may refer to any kind of shared entities to provide services, and may include computing and/or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a multiple hosts and are clearly identifiable.

[0313] The term “channel” as used herein refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “channel” may be synonymous with and/or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term “link” as used herein refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.

[0314] The terms “instantiate,” “instantiation,” and the like as used herein refers to the creation of an instance. An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.

[0315] The terms “coupled,” “communicatively coupled,” along with derivatives thereof are used herein. The term “coupled” may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact each other but still cooperate or interact with each other, and/or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other. The term “directly coupled” may mean that two or more elements are in direct contact with one another. The term “communicatively coupled” may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or link, and/or the like.

Claims

What is Claimed Is:

1. An apparatus of a New Radio (NR) Node B (gNB) including a memory storing instructions, and one or more processors coupled to the memory to execute the instructions to perform operations including: identifying scheduling information for a plurality of cells and related to one or more SCH (SCH) transmissions, the one or more SCH transmissions including one or more physical uplink SCH (PUSCH) transmissions or one or more physical downlink SCH (PDSCH) transmissions; generating a physical downlink control channel (PDCCH) based on the scheduling information; and sending the PDCCH for transmission to a user equipment (UE) on a single scheduling cell of the plurality of cells.

2. The apparatus of claim 1, wherein generating the PDCCH includes generating a single DCI format for multi-cell scheduling.

3. The apparatus of claim 2, wherein the plurality of cells are divided into multiple sets and each set has its own DCI format for multi-cell scheduling.

4. The apparatus of claim 2, wherein the scheduling information is a first scheduling information, the one or more SCHs are one or more first SCHs, the PDCCH is a first PDCCH , the operations further including: identifying second scheduling information for a single cell of the plurality of cells, and related to a second SCH transmission; generating a second PDCCH based on the second scheduling information; and sending the second PDCCH for transmission to the UE on the scheduling cell, the second PDCCH including a DCI format for single-cell scheduling.

5. The apparatus of claim 4, the operations further including: generating a downlink control information (DCT) configuration message to the UE to configure the UE to monitor, on the scheduling cell, for a DCI format for multi-cell scheduling and for a DCI format for single-cell scheduling; and sending the DCI configuration message for transmission to the UE.

6. The apparatus of claim 5, wherein the DCI configuration message is to configure the UE to monitor, in a same OFDM symbol or in a same set of OFDM symbols, for the DCI format for multi-cell scheduling and for the DCI format for single-cell scheduling.

7. The apparatus of claim 6, wherein the DCI configuration message to the UE further includes information for search space (SS) set configuration of the scheduling cell, the information for SS set configuration including a number of candidates (nrofcandi dates) parameter and a SS identification (searchSpaceld) parameter for the DCI format for multi-cell scheduling.

8. The apparatus of claim 7, wherein the operations include generating the DCI configuration message that includes the SS set configuration of the scheduling cell only with DCI format configuration for the DCI format for multi-cell scheduling.

9. The apparatus of claim 7, wherein the nr of candidates parameter corresponds to a number of PDCCH candidates that the UE is to be configured to monitor for.

10. The apparatus of any one of claims 7-9, the operations further including configuring SS set configuration of a non-scheduling cell of the plurality of cells for multi-cell scheduling using higher-layer signaling.

11. The apparatus of any one of claims 7-9, wherein: the information for SS set configuration of the scheduling cell is first information for SS set configuration; the nrofcandidates parameter is a first nrofcandidates parameter; and the SS set configuration of the non-scheduling cell is a second information, including a same searchSpaceld parameter as in the first information, and a second nrofcandidates parameter.

12. The apparatus of any one of claims 7-9, wherein, in response to a determination that the UE is configured with a carrier indicator field for the serving cell, the one or more processors are to generate the DCI configuration message to include information for search space (SS) set configuration for the UE, the information for SS set configuration based on a carrier indicator field value _nCL that is configured for the plurality of cells.

13. The apparatus of any one of claims 7-9, further including a Radio Frequency (RF) interface, and a front end module coupled to the RF interface.

14. The apparatus of claim 13, further including one or more antennas coupled to the front end module to transmit the PDCCH.

15. A method to be performed at a device of a New Radio (NR) Node B (gNB), the method including: identifying scheduling information for a plurality of cells and related to one or more shared channel (SCH) transmissions, the one or more SCH transmissions including one or more physical uplink shared channel (PUSCH) transmissions or one or more physical downlink shared channel (PDSCH) transmissions; generating a physical downlink control channel (PDCCH) based on the scheduling information; and sending the PDCCH for transmission to a user equipment (UE) on a single scheduling cell of the plurality of cells.

16. The method of claim 15, wherein generating the PDCCH includes generating a single DCI format for multi-cell scheduling.

17. The method of claim 16, wherein the scheduling information is a first scheduling information, the one or more SCH transmissions are one or more first SCH transmissions, the PDCCH is a first PDCCH , the method further including: identifying second scheduling information for a single cell of the plurality of cells, and related to one or more second shared channel transmissions; generating a second PDCCH based on the second scheduling information; and sending the second PDCCH for transmission to the UE on the scheduling cell, the second PDCCH including a DCI format for single-cell scheduling.

18. The method of claim 17, the method further including: generating a downlink control information (DCI) configuration message to the UE to configure the UE to monitor, on the scheduling cell, for a DCI format for multi -cell scheduling and for a DCI format for single-cell scheduling; and sending the DCI configuration message for transmission to the UE.

19. A method to be implemented at an apparatus of a New Radio (NR) User Equipment (UE), the method including: identifying a physical downlink control channel (PDCCH) transmission from a NR Node B (gNB); determining, from the PDCCH, scheduling information for a plurality of cells and related to one or more shared channel (SCH) transmissions, the one or more SCH transmissions including one or more physical uplink shared channel (PUSCH) transmissions or one or more physical downlink shared channel (PDSCH) transmissions; and receiving the one or more PDSCH transmissions or sending for transmission the one or more PUSCH transmissions based on the scheduling information.

20. The method of claim 19, wherein the PDCCH includes a single DCI format for multi -cell scheduling.

21 . The method of claim 20, wherein the scheduling information is a first scheduling information, the one or more SCH transmissions are one or more first SCH transmissions, the PDCCH is a first PDCCH , the method further including: identifying a second PDCCH transmission on the scheduling cell, the second PDCCH transmission related to a second CH transmission; determining, from the second PDCCH, second scheduling information for a single cell of the plurality of cells and related to one or more second shared channel transmissions; and receiving one or more second PDSCH transmissions or sending for transmission the one or more PUSCH transmissions based on the scheduling information.

22. The method of claim 21, the method further including, prior to accessing the first PDCCH: accessing a downlink control information (DCI) configuration message from the gNB; and configuring the UE to monitor, based on the DCI configuration and on the scheduling cell, for a DCI format for multi-cell scheduling and for a DCI format for single-cell scheduling.

23. The method of claim 22, wherein configuring the UE includes using the DCI configuration message to configure the UE to monitor, in a same OFDM symbol or in a same set of OFDM symbols, for the DCI format for multi-cell scheduling and for the DCI format for single-cell scheduling.

24. A machine-readable medium including code which, when executed, is to cause a machine to perform the method of any one of claims 15-23.

25. An apparatus including means to perform the method of any one of claims 15-23.