DCI Design for Multi-Carrier Scheduling

Abstract

A configuration enabling a base station to use a DCI to schedule cross-carrier scheduling for uplink and / or downlink transmissions. The device sends a PDCCH including cross-carrier scheduling to the UE. The PDCCH includes a DCI configured to schedule uplink or downlink transmissions. The DCI includes at least one FDRA field indicating the RB used for uplink or downlink transmissions. The device communicates with the UE based on the cross-carrier scheduling configured via the DCI.

Description

[0001] Cross-references to related applications

[0002] This application claims priority to U.S. Provisional Application No. 63 / 008,619, filed April 10, 2020, entitled “DCI Design for Multi-Cross Carrier Scheduling”, and U.S. Patent Application No. 17 / 224,011, filed April 6, 2021, both of which are expressly incorporated herein by reference in their entirety. Technical Field

[0003] In general, this disclosure relates to communication systems, and more specifically, to the configuration of downlink control information (DCI) designs for multi-carrier scheduling. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable communication with multiple users by sharing available system resources. Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0005] Such multiple access technologies have been adopted in various telecommunications standards to provide a common protocol enabling different wireless devices to communicate across cities, countries, regions, and even globally. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Mobile Broadband Evolution (CMB) initiative released by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)), and others. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvements to 5G NR technology. These improvements can be applied to other multiple access technologies and telecommunications standards that adopt them. Summary of the Invention

[0006] The following section provides a brief overview of one or more aspects to offer a basic understanding of such aspects. This overview is not an exhaustive summary of all anticipated aspects, nor is it intended to identify key or important elements of all aspects, nor to describe the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simple form as a prelude to the more detailed descriptions that follow.

[0007] In one aspect of this disclosure, methods, computer-readable media, and apparatus are provided. The apparatus may be a device at a base station. The device may be a processor and / or modem at the base station, or the base station itself. The apparatus transmits a Physical Downlink Control Channel (PDCCH) including cross-carrier scheduling to a User Equipment (UE). The PDCCH includes Downlink Control Information (DCI) configured to schedule uplink or downlink transmissions. The DCI includes at least one Frequency Domain Resource Allocation (FDRA) field, which indicates a resource block (RB) for uplink or downlink transmission. The apparatus communicates with the UE based on cross-carrier scheduling configured via the DCI.

[0008] In one aspect of this disclosure, methods, computer-readable media, and apparatus are provided. The apparatus may be a device at a UE. The device may be a processor and / or modem at the UE, or the UE itself. The apparatus receives from a base station a Physical Downlink Control Channel (PDCCH) including cross-carrier scheduling, the PDCCH including Downlink Control Information (DCI) configured to schedule uplink or downlink transmissions. The DCI includes at least one Frequency Domain Resource Allocation (FDRA) field, the FDRA field indicating a resource block (RB) for uplink or downlink transmission. The apparatus communicates with the base station based on cross-carrier scheduling configured via the DCI.

[0009] To achieve the foregoing and related objectives, one or more aspects include the features fully described below and specifically pointed out in the claims. Certain illustrative features of one or more aspects are set forth in detail in the following description and accompanying drawings. However, these features indicate only a few of the various methods by which they can be implemented using the fundamental principles of the aspects, and this specification is intended to include all such aspects and their equivalents. Attached Figure Description

[0010] Figure 1 This is a diagram illustrating an example of a wireless communication system and access network.

[0011] Figure 2A This is a diagram illustrating an example of the first frame of various aspects according to this disclosure.

[0012] Figure 2BThis is a diagram illustrating an example of a DL channel within a subframe according to various aspects of this disclosure.

[0013] Figure 2C This is a diagram illustrating an example of the second frame according to various aspects of this disclosure.

[0014] Figure 2D This is a diagram illustrating an example of a UL channel within a subframe according to various aspects of this disclosure.

[0015] Figure 3 This is a diagram illustrating examples of base stations and user equipment (UEs) in an access network.

[0016] Figures 4A-4B This is a diagram illustrating an example of PDCCH enhancement.

[0017] Figure 5 This is a diagram illustrating examples of cross-carrier scheduling and / or joint scheduling.

[0018] Figures 6A-6D This is a diagram illustrating an example of a DCI design.

[0019] Figure 7 This is a diagram illustrating an example of the DCI format used for scheduling PDSCH.

[0020] Figure 8 This is a diagram illustrating an example of the DCI format used for cross-carrier scheduling.

[0021] Figure 9 This is a diagram illustrating an example of frequency domain resource allocation.

[0022] Figure 10 This is a diagram illustrating an example of the DCI format.

[0023] Figure 11A-11B This is a diagram illustrating an example of resource allocation and DCI format.

[0024] Figure 12A-12B This is a diagram illustrating an example of DCI.

[0025] Figure 13 This is a call flow diagram of signaling between the UE and the base station based on certain aspects of this disclosure.

[0026] Figure 14 This is a flowchart of a wireless communication method.

[0027] Figure 15 This is a diagram illustrating an example of how the hardware implementation of the example device is used.

[0028] Figure 16 This is a flowchart of a wireless communication method.

[0029] Figure 17 This is a diagram illustrating an example of how the hardware implementation of the example device is used. Detailed Implementation

[0030] The specific embodiments described below with reference to the accompanying drawings are intended as a description of various configurations and are not intended to represent the only configurations in which the concepts described herein can be practiced. To provide a thorough understanding of the various concepts, the specific embodiments include particular details. However, it will be apparent to those skilled in the art that these concepts can be implemented without these particular details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0031] Several aspects of a telecommunications system are now described with reference to various apparatuses and methods. These apparatuses and methods will be described in the following detailed embodiments and illustrated in the accompanying drawings through various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such an element is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0032] For example, an element, any part of an element, or any combination of elements can be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuitry, and other suitable hardware configured to perform the various functions described throughout this disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc.

[0033] Therefore, in one or more exemplary embodiments, the functionality described herein can be implemented in hardware, software, or any combination thereof. When implemented in software, these functions can be stored or encoded as one or more instructions or code on a computer-readable medium. A computer-readable medium includes a computer storage medium. The storage medium can be any available medium accessible to a computer. By way of example, and not limitation, such a computer-readable medium can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of computer-readable media of the foregoing types, or any other medium capable of storing computer-executable code in the form of instructions or data structures and accessible to a computer.

[0034] Figure 1 This diagram illustrates an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a user interface unit (UE) 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macro cells include base stations. Small cells include femtocells, picocells, and microcells.

[0035] Base station 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a first backhaul link 132 (e.g., S1 interface). Base station 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) can interface with core network 190 via a second backhaul link 184. Among other functions, base station 102 can perform one or more of the following functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), user and device tracking, RAN information management (RIM), paging, location, and transmission of alarm messages. Base station 102 can communicate with each other directly or indirectly (e.g., via EPC 160 or core network 190) via third backhaul link 134 (e.g., X2 interface). First backhaul link 132, second backhaul link 184 and third backhaul link 134 can be wired or wireless.

[0036] Base station 102 can communicate wirelessly with UE 104. Each base station in base station 102 can provide communication coverage for a corresponding geographic coverage area 110. Overlapping geographic coverage areas 110 may exist. For example, small cell 102' may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network that includes both small cells and macro cells can be referred to as a heterogeneous network. The heterogeneous network may also include evolved home node B (eNB) (HeNB), which can provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link 120 between base station 102 and UE 104 may include uplink (UL) (also referred to as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also referred to as forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be via one or more carriers. Base station 102 / UE 104 may use up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) of bandwidth for each carrier allocated in carrier aggregation for a total of up to Yx MHz (x component carriers) for transmission in each direction. These carriers may be adjacent to each other or may not be adjacent to each other. The allocation of carriers relative to DL and UL may be asymmetric (e.g., more or fewer carriers may be allocated to DL compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell), and the secondary component carriers may be referred to as secondary cells (SCells).

[0037] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL WWAN spectrum. D2D communication link 158 can use one or more sideline channels, such as the Physical Sideline Broadcast Channel (PSBCH), Physical Sideline Discovery Channel (PSDCH), Physical Sideline Shared Channel (PSSCH), and Physical Sideline Control Channel (PSCCH). D2D communication can be via various wireless D2D communication systems, such as WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0038] The wireless communication system may also include a Wi-Fi access point (AP) 150, which communicates with a Wi-Fi station (STA) 152 via a communication link 154 (e.g., in unlicensed 5 GHz spectrum, etc.). When communicating in unlicensed spectrum, the STA 152 / AP 150 may perform a free channel assessment (CCA) to determine whether the channel is available before communication.

[0039] Small cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell 102' can employ NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) as used by Wi-Fi AP 150. Small cell 102' employing NR in unlicensed spectrum can improve the coverage and / or increase the capacity of the access network.

[0040] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency range names FR1 (410MHz-7.125GHz) and FR2 (24.25GHz-52.6GHz). The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is generally (interchangeably) referred to as the "below 6GHz" band. Similar naming issues sometimes arise regarding FR2, although it differs from the extremely high frequency (EHF) band (30GHz-300GHz) designated as the "millimeter wave" band by the International Telecommunication Union (ITU), FR2 is generally (interchangeably) referred to as the "millimeter wave" band in various documents and articles.

[0041] In light of the foregoing, unless otherwise explicitly stated, it should be understood that the terms "below 6 GHz," etc. (if used herein), can broadly refer to frequencies less than 6 GHz, within FR1, or may include intermediate frequency band frequencies. Furthermore, unless otherwise explicitly stated, it should be understood that the terms "millimeter wave," etc. (if used herein), can broadly refer to frequencies that may include intermediate frequency band frequencies, frequencies within FR2, or frequencies within the EHF band.

[0042] Base station 102 (whether a small cell 102' or a large cell (e.g., a macro base station)) may include and / or may be referred to as an eNB, gNodeB (gNB), or another type of base station. Some base stations (such as gNB 180) may operate in conventional sub-6 GHz spectrum, in millimeter wave frequencies, and / or in near-millimeter wave frequencies to communicate with UE 104. When gNB 180 operates at millimeter wave or near-millimeter wave frequencies, gNB 180 may be referred to as a millimeter wave base station. Millimeter wave base station 180 may utilize beamforming 182 with UE 104 to compensate for path loss and short communication distances. Both base station 180 and UE 104 may include multiple antennas (e.g., antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming.

[0043] Base station 180 may transmit beamformed signals to UE 104 in one or more transmit directions 182'. UE 104 may receive beamformed signals from base station 180 in one or more receive directions 182'. UE 104 may also transmit beamformed signals to base station 180 in one or more transmit directions. Base station 180 may receive beamformed signals from UE 104 in one or more receive directions. Base station 180 / UE 104 may perform beam training to determine the optimal receive and transmit directions for each of base station 180 / UE 104. The transmit and receive directions for base station 180 may be the same or different. The transmit and receive directions for UE 104 may be the same or different.

[0044] EPC 160 may include Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, Multimedia Broadcast Multicast Service (MBMS) Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and Packet Data Network (PDN) Gateway 172. MME 162 can communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Typically, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP Service 176. IP Service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services. The BM-SC 170 provides functionality for MBMS user service provisioning and delivery. It can act as an entry point for content provider MBMS transmissions, authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and schedule MBMS transmissions. The MBMS gateway 168 can distribute MBMS services to base stations 102 belonging to Multicast-Broadcast Single Frequency Network (MBSFN) areas belonging to broadcast-specific services, and is responsible for session management (initiation / termination) and collecting billing information related to eMBMS.

[0045] Core network 190 may include Access and Mobility Management Functions (AMF) 192, other AMFs 193, Session Management Functions (SMF) 194, and User Plane Functions (UPF) 195. AMF 192 can communicate with Unified Data Management (UDM) 196. AMF 192 is the control node that handles signaling between UE 104 and core network 190. Typically, AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are transmitted through UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 connects to IP service 197. IP service 197 may include the Internet, intranet, IP Multimedia Subsystem (IMS), Packet Switched (PS) Streaming (PSS) service, and / or other IP services.

[0046] Base stations may include and / or be referred to as gNB, Node B, eNB, access point, base transceiver, radio base station, radio transceiver, transceiver function, Basic Services Set (BSS), Extended Services Set (ESS), Transmitter Receiver Point (TRP), or some other suitable term. Base station 102 provides UE 104 with access to EPC 160 or core network 190. Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radio units, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, medical devices, implants, sensors / actuators, displays, or any other similar functional devices. Some UEs in UE 104 may be referred to as IoT devices (e.g., parking meters, air pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, user station, mobile unit, user unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile user station, access terminal, mobile terminal, radio terminal, remote terminal, handheld device, user agent, mobile client, client, or any other suitable term.

[0047] Refer again Figure 1 In some aspects, UE 104 can be configured to receive cross-carrier scheduling of uplink or downlink transmissions on more than one cell. For example, UE 104 may include a scheduling component 198 configured to receive cross-carrier scheduling of uplink or downlink transmissions on more than one cell. UE 104 receives a PDCCH including cross-carrier scheduling from base station 180. The PDCCH includes a DCI configured to schedule uplink or downlink transmissions on more than one cell. UE 104 communicates with base station 180 based on the cross-carrier scheduling configured via the DCI.

[0048] Refer again Figure 1In some aspects, base station 180 can be configured to configure cross-carrier scheduling for uplink or downlink transmissions on more than one cell. For example, base station 180 may include scheduling component 199, which is configured to configure cross-carrier scheduling for uplink or downlink transmissions on more than one cell. Base station 180 is configured to include a PDCCH including cross-carrier scheduling for uplink or downlink transmissions on more than one cell. Base station 180 sends the PDCCH including cross-carrier scheduling to UE. The PDCCH includes a DCI configured to schedule uplink or downlink transmissions. Base station 180 communicates with UE based on the cross-carrier scheduling configured via the DCI.

[0049] Although the following description may focus on 5G NR, the concepts described in this article can be applied to other similar fields, such as LTE, LTE-A, CDMA, GSM and other wireless technologies.

[0050] Figure 2A Figure 200 shows an example of the first subframe in a 5G NR frame structure. Figure 2B Figure 230 shows an example of a DL channel in a 5G NR subframe. Figure 2C Figure 250 shows an example of the second subframe in a 5G NR frame structure. Figure 2D Figure 280 illustrates an example of a UL channel in a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD) or Time Division Duplex (TDD). In FDD, for a specific set of subcarriers (carrier system bandwidth), subframes within that set are dedicated to either DL or UL. In TDD, for a specific set of subcarriers (carrier system bandwidth), subframes within that set are dedicated to both DL and UL. Figure 2A , 2C In the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (primarily DL), where D is DL, U is UL, and F is used flexibly between DL / UL, and subframe 3 is configured with slot format 1 (all UL). Although subframes 3 and 4 are shown with slot formats 1 and 28 respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and all UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE is configured with a slot format via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). Note that the following description also applies to TDD 5G NR frame structures.

[0051] Other wireless communication technologies may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 subframes (1 ms) of the same size. Each subframe may include one or more time slots. Subframes may also include micro-time slots, which may include 7, 4, or 2 symbols. Depending on the time slot configuration, each time slot may include 7 or 14 symbols. For time slot configuration 0, each time slot may include 14 symbols, while for time slot configuration 1, each time slot may include 7 symbols. Symbols on the DL can be Cyclic Prefix (CP) Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL can be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (also known as Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the time slot configuration and parameter set (numerology). For slot configuration 0, different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For slot configuration 1, different parameter sets 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Therefore, for slot configuration 0 and parameter set μ, there are 14 symbols / slots and 2... μ Each time slot / subframe. Subcarrier spacing and symbol length / duration are functions of a parameter set. Subcarrier spacing can be equal to 2. μ *15kHz, where μ is the parameter set from 0 to 4. Thus, parameter set μ = 0 has a subcarrier spacing of 15kHz, and parameter set μ = 4 has a subcarrier spacing of 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figure 2A-2D A time slot configuration of 0 with 14 symbols per time slot and an example of a parameter set μ=2 based on 4 time slots per subframe are provided. The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within the frame set, one or more different bandwidth portions (BWPs) for frequency division multiplexing can exist (see [link to example]). Figure 2B Each BWP can have a specific set of parameters.

[0052] A resource grid can be used to represent the frame structure. Each time slot consists of a resource block (RB) with 12 consecutive subcarriers (also known as a physical RB (PRB)). The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0053] like Figure 2AAs shown, some of the REs carry reference (pilot) signals (RS) for the UE. RS may include demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. RS may also include beam measurement RS (BRS), beam refinement (BRRS), and phase tracking RS (PT-RS).

[0054] Figure 2B Examples of various DL channels within a subframe of a frame are shown. The PDCCH carries the DCI in one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE groups (REGs), each REG comprising 12 consecutive REs within an OFDM symbol of an RB. The PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during PDCCH monitoring timing on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs can reside at higher and / or lower frequencies spanning the channel bandwidth. The Primary Synchronization Signal (PSS) can be located within symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) can be located within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the physical layer cell identification group number and radio frame timing. Based on the Physical Layer Identifier and Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DM-RS. The Physical Broadcast Channel (PBCH) carrying the Master Information Block (MIB) can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (e.g., System Information Block (SIB)), and paging messages.

[0055] like Figure 2CAs shown, some REs in the REs carry DM-RS for channel estimation at the base station (indicated as R for a specific configuration, but other DMRS configurations are possible). The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). PUSCH DM-RS can be transmitted in the first one or two symbols preceding the PUSCH. PUCCH DM-RS can be transmitted in different configurations depending on whether a short or long PUCCH is transmitted and the specific PUCCH format used. The UE can transmit a Sounding Reference Signal (SRS). SRS can be transmitted in the last symbol of a subframe. SRS can have a comb structure, and the UE can transmit SRS on one of these comb structures. SRS can be used by the base station for channel quality estimation to implement frequency-dependent scheduling on the UL.

[0056] Figure 2D Examples of various UL channels within a subframe of a frame are shown. The PUCCH can be positioned as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) information (ACK / negative ACK / NACK) feedback. The PUCCH carries data and is also used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCI.

[0057] Figure 3This is a block diagram illustrating communication between base station 310 and UE 350 in the access network. In the DL (Data Link Module), IP packets from EPC 160 are provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functions. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Serving Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides: RRC layer functions associated with broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), movement between radio access technologies (RATs), and measurement configuration for UE measurement reporting; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with upper-layer packet data unit (PDU) transmission, error correction via ARQ, connection, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing MAC SDUs onto transport blocks (TBs), demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority processing, and logical channel priority allocation.

[0058] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functions associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection of the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols can then be segmented into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and subsequently combined using an inverse Fourier transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from channel estimator 374 can be used to determine coding and modulation schemes and for spatial processing. Channel estimates can be derived based on reference signals transmitted by UE 350 and / or channel condition feedback. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX can modulate an RF carrier using the corresponding spatial stream for transmission.

[0059] At UE 350, each receiver 354RX receives signals through its corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and RX processor 356 implement Layer 1 functions associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for UE 350. If multiple spatial streams are destined for UE 350, they can be combined by the RX processor 356 into a single OFDM symbol stream. Subsequently, the RX processor 356 uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with the reference signal, are recovered and demodulated by determining the most probable signal constellation points transmitted by base station 310. These soft decisions can be based on a channel estimate calculated by channel estimator 358. These soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 310 on the physical channel. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functions.

[0060] The controller / processor 359 may be associated with a memory 360 that stores program code and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0061] Similar to the functions described in the DL transmission combined with base station 310, controller / processor 359 provides: RRC layer functions associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with upper-layer PDU transmission, error correction via ARQ, RLC SDU connection, segmentation and reassembly, RLC data PDU resegmentation, and RLC data PDU reordering; and MAC layer functions associated with mapping between logical channels and transport channels, MAC SDU multiplexing onto TB, demultiplexing MAC SDU from TB, scheduling information reporting, error correction via HARQ, priority processing, and logical channel priority allocation.

[0062] The channel estimate derived by the channel estimator 358 based on the reference signal or feedback transmitted by the base station 310 can be used by the TX processor 368 to select appropriate coding and modulation schemes and facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via corresponding transmitters 354TX. Each transmitter 354TX can use the corresponding spatial stream to modulate the RF carrier for transmission.

[0063] UL transmission at base station 310 is processed in a manner similar to that described in conjunction with the receiver function at UE 350. Each receiver 318RX receives signals via its corresponding antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides the information to the RX processor 370.

[0064] The controller / processor 375 may be associated with a memory 376 that stores program code and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets from the UE 350. IP packets from the controller / processor 375 can be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0065] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to perform operations with... Figure 1 The 198 related aspects.

[0066] At least one of the TX processor 316, RX processor 370, and controller / processor 375 can be configured to perform operations related to... Figure 1 The 199 related aspects.

[0067] Dynamic Spectrum Sharing (DSS) allows LTE and NR to operate in the same frequency band and is configured to dynamically allocate spectrum resources between LTE and NR based on user demand. In a radio system operating both LTE and NR, LTE carriers can be dynamically shared between LTE and NR UEs, making the LTE carriers known as DSS carriers. NR carriers are not shared with LTE UEs and can be known as non-DSS carriers. NR and LTE carriers can be configured for NR UEs using carrier aggregation. Because LTE carriers are shared between LTE and NR UEs, available resources may be insufficient to meet demand. Therefore, it is desirable to improve the way DSS operates to allow for PDCCH enhancement, thereby improving spectrum efficiency between LTE and NR.

[0068] The aspects provided herein offer configuration options for configuring cross-carrier scheduling of uplink or downlink transmissions across more than one cell. For example, a base station can configure an enhanced PDCCH to include cross-carrier scheduling for uplink or downlink transmissions across more than one cell. In some aspects, an enhanced PDCCH associated with a first cell can be configured to schedule the PDSCH or PUSCH of a second cell. In some aspects, an enhanced PDCCH can use a single DCI to schedule cross-carrier scheduling across more than one cell.

[0069] Figures 4A-4B Examples 400 and 420 are PDCCH enhancements. Example 400 includes PDCCH enhancements with cross-carrier scheduling. Example 420 includes PDCCH enhancements with joint scheduling. Figure 4A and Figure 4B In all aspects, the LTE carrier can be a PCell or a primary secondary cell (PSCell) 404, referred to hereinafter as the combined term P(S)Cell (which is also a DSS carrier), while the NR carrier can be SCell 402 (which is a non-DSS carrier). The terms PSCell and P(S)Cell are used interchangeably. In some aspects, the LTE carrier can be a PCell. The PDCCH 406 of SCell 402 can be configured for cross-carrier scheduling, whereby the PDCCH 406 of SCell 402 is configured to schedule PDSCH or PUSCH 408 on P(S)Cell 404. As used herein, cross-carrier scheduling refers to the following scheduling: a message transmitted on one carrier (e.g., PDCCH 406) is scheduled for transmission on another carrier (e.g., PDSCH / PUSCH 408).

[0070] refer to Figure 4B The PDCCH 406 of the SCell 402 can be configured for joint scheduling, thereby allowing the PDCCH 406 of the SCell 402 to schedule PDSCH 422 and 424 on multiple cells using a single DCI (not shown). The PDCCH 406 can carry a single DCI for scheduling PDSCH 422 and 424 on multiple cells. For example... Figure 4B As shown in the example, joint scheduling is understood to include cross-carrier scheduling because PDCCH 406 schedules PDSCH 424 on a carrier different from the carrier on which PDCCH 406 is scheduled. However, in joint scheduling, in addition to PDSCH 424 on a different carrier, PDCCH 406 also schedules PDSCH 422 on the same carrier. In some aspects, the PDCCH of a P(S)Cell can use a single DCI to schedule PDSCH 422, 424 on multiple cells. Traditionally, a single DCI schedules one data channel, even if there is a specification indicating that multiple data channels can be scheduled by a single DCI (such scheduling can occur within a single carrier). At least one advantage of this disclosure is that a single DCI can schedule data channels on multiple carriers at once, which can improve spectral efficiency. The number of cells that can be scheduled at once can include two cells. Furthermore, the increase in DCI size can be minimized, keeping the total PDCCH blind decoding budget unchanged.

[0071] Figure 5This is another example 500 of cross-carrier scheduling and / or joint scheduling. P(S)Cell 504 can be a DSS carrier, and SCell 502 can be a non-DSS carrier. P(S)Cell 504 can use a 15 kHz subcarrier spacing (SCS), while SCell 502 can use a 30 kHz SCS to accommodate a wider bandwidth. The DSS carrier P(S)Cell 504 can use a 15 kHz SCS to align with SCell 502. However, other SCS combinations are also possible. P(S)Cell 504 can have uplink resources, while SCell 502 may not be configured to have uplink resources (e.g., downlink-only carrier aggregation). For example, the UE can be configured with carrier aggregation in the downlink and a single-carrier configuration for the uplink. In some aspects, both P(S)Cell 504 and SCell 502 can operate in the same frequency range (e.g., frequency range (FR)1). In some aspects, SCell 502, the non-DSS carrier, can be an NR-U carrier. PDCCH 506 can be configured to schedule downlink or uplink transmissions on P(S)Cell 504. PDCCH 506 can be configured to use a single DCI to schedule multiple carriers on multiple cells (e.g., PDSCH), which can improve spectral efficiency by using a single DCI instead of multiple DCIs. This disclosure is not intended to be limited to the aspects disclosed herein. This disclosure includes aspects in which a non-DSS carrier is configured to schedule uplink and / or downlink transmissions on a DSS carrier. However, in some aspects, a DSS carrier can be configured to schedule carriers such that the DSS carrier schedules uplink and / or downlink transmissions on a non-DSS carrier. For example, in some aspects, P(S)Cell can be a DSS carrier and can be configured to schedule uplink and / or downlink transmissions on an SCell (which can be a non-DSS carrier).

[0072] Figures 6A-6D Figures 600, 630, 640, and 650 illustrate examples of DCI design schemes. Figure 6A In Example 600, individual DCIs are configured for individual carriers. For example, DCI 602 for the first component carrier (CC) and DCI 604 for the second CC. Each DCI 602, 604 may have multiple fields internally. Figure 6AExample 600 is simplified such that each DCI 602, 604 includes 5 fields (e.g., 606, 608, 610, 612, 614 for DCI 602; 616, 618, 620, 622, 624 for DCI 604). However, this disclosure is not intended to limit itself to the aspects disclosed herein, such that a DCI may have more than 5 fields or fewer than 5 fields. Figures 6A-6D The aspects shown are simplified examples and are not intended to be limited to such examples.

[0073] exist Figure 6B In Example 630, individual DCIs 602 and 604 can be combined to form DCI 632 for the first CC and the second CC, such that the fields for DCI 602 are first mapped to DCI 632, followed by the mapping of the fields for DCI 604. Figure 6C In Example 640, the individual DCIs 602 and 604 can be combined into DCI 642 for the first CC and the second CC. The fields of DCI 642 can be mapped in an interleaved configuration, such that the first field 606 for the first CC is mapped first, followed by the first field 616 for the second CC, then the second field 608 for the first CC, then the second field 618 for the second CC, and so on. This interleaving pattern continues until the corresponding fields of the combined DCI are mapped. In either case, two sets of Cyclic Redundancy Check (CRC) bits are not required; therefore, the payload can be reduced compared to sending two separate DCI formats for the two CCs 630 and 640, thus improving performance. Figure 6D Example 650 discloses a single DCI 652 for both the first CC and the second CC, such that the DCI 652 is reduced in size compared to a single DCI.

[0074] Figure 7Figure 700 illustrates the DCI format. Figure 700 includes fields that can be included in a single DCI (e.g., DCI 652). Figure 700 illustrates the fields of a single DCI format for a DCI 702 configured for cross-carrier scheduling and a DCI 704 configured for joint scheduling. For each of these fields, two options are possible. The first option (e.g., DCI 702) may include separate fields for different scheduling CCs, such that fields for the first CC and the second CC are included. In some aspects, one or more of these fields may be copied twice in a single DCI 702. This allows DCI 702 to schedule two PDSCHs on two CCs without any limitations. The second option (e.g., DCI 704) may include joint fields, such that some or specific fields of DCI 704 jointly indicate values ​​for the first CC and the second CC, such that DCI 704 may not include duplicate fields. For example, refer to... Figure 8 It shows an example 800 of a field that can be considered as a union field 802. Figure 8 In the example, the Frequency Domain Resource Allocation (FDRA) mapping field and the Virtual Resource Block to Physical Resource Block (VRB-to-PRB) mapping field can be joint fields, such that they indicate the value used for the corresponding CC. This disclosure is not intended to be limited to the aspects disclosed herein. In some aspects, other DCI fields can be joint fields, and this disclosure is not intended to limit the FDRA and VRB-to-PRB mapping fields to being joint fields.

[0075] Figure 9 Figure 900 illustrates an example of FDRA. The field size of FDRA can depend on the type configuration and bandwidth. DCI can support two resource allocation (RA) types (e.g., Type 0 and Type 1), where RA Type 0 can have two configurations. For Type 0, the resource block (RB) group level bitmap can be RA-based, where the resource block group (RBG) granularity is configured by higher layers. When the UE is configured with Configuration 1 or Type 0, the RB group size can depend on the bandwidth portion (BWP) size, for example, as... Figure 9 As shown in the table. A bitmap mapping PDSCH to which RB group to indicate the resource allocation field is used. To reduce the DCI size, a method such as... Figure 9 The configuration shown is 2. Configuration 2 can use coarse granularity, which allows for a reduction in the number of RB groups in the bandwidth and can help reduce the FDRA field size.

[0076] For Type 1, contiguous allocation can be configured using resource indicator values ​​(RIVs) in the frequency domain (e.g., start RB, length). Type 1 allows contiguous allocation in the frequency domain, which can help reduce DCI size. Type 1 can also be configured to support VRB-to-PRB mapping, which can be a 1-bit indicator. If the indicator field indicates that RA Type 1 is used to schedule VRB-to-PRB mapping for PDSCH, then VRB-to-PRB mapping is performed, which allows data interleaving across frequencies.

[0077] Figure 10 Figure 1000 shows an example of the DCI format. Figure 10 In some aspects, the DCI format can be configured for multi-CC scheduling and can include two FDRA fields. A first FDRA field 1002 can correspond to an FDRA field used for the first CC, and a second FDRA field 1004 can correspond to an FDRA field used for the second CC. The number of bits used for FDRA fields 1002 and 1004 can be determined by the RRC higher-level configuration of the PDSCH used in the first and second CCs, respectively. The first CC can have its own configuration, BWP, and RA type. The number of bits used for FDRA field 1002 can be determined based on the higher-level RRC configuration. In some aspects, the order of FDRA fields 1002 and 1004 can be based on the index of the corresponding CC. In some aspects, for RA Type 0, a new configuration (e.g., Type 0 configuration 3) can be defined to attempt to reduce the field size of the FDRA. Compared to configurations 1 and 2, the new Type 0 configuration 3 can have increased coarseness. Figure 10 In some aspects, the value of Configuration 3 is doubled compared to Configuration 2, which can help reduce the size of the DCI. The value of the new Configuration 3 can be configured to increase the coarsening, and it is not intended to be limited to twice the size of Configuration 2. In some aspects, for RA Type 1, the RBG concept can be utilized so that the RIV can indicate the start RBG and length, which can help reduce the size of the FDRA field used for RA Type 1.

[0078] Figure 11A-11BFigures 1100 and 1120 illustrate examples of RA and DCI formats used for union fields. For example, Figure 1100 discloses a table 1102 of a union configuration, where field values ​​of FDRAs (e.g., 1122) for the first CC (e.g., CC1) and the second CC (e.g., CC2) can be linked via RRCs such that the FDRA is a union FDRA. A union FDRA can allow the field values ​​of the FDRA to have three-bit fields with eight different values ​​(e.g., 000, 001, 010, 011, 100, 101, 110, 111), and each of the eight different FDRA values ​​can correspond to an RIV for the first CC and the second CC. Figure 11A The values ​​of the first and second CCs indicated are examples, and this disclosure is not intended to be limited to such examples. Therefore, the RIVs used for the first and second CCs can be different. In some aspects, the first CC or the second CC may not have a RIV corresponding to a three-bit FDRA value; in this case, the first CC or the second CC may have a "null" value for the RIV. Therefore, the FDRA value can still provide a CC resource allocation based on the FDRA value. For example, see reference... Figure 11A An FDRA value of "111" results in an "empty" RIV for the first CC and a "6" RIV for the second CC, where "empty" indicates that data was not scheduled for the first CC but was scheduled for the second CC. The number of FDRA bits can be determined by the maximum number of FDRAs configured for the first CC and the number of FDRAs configured for the second CC. For example, if either the first CC or the second CC has a smaller number of entries in the table, the size can depend on the larger size. Figure 11A Table 1102 shows “RIV”, however, in some respects it is possible to use RA Type 0, in which case each entry in the entry can have a bitmap.

[0079] In some aspects, the common RIV spans two CCs, where the two CCs are treated as if they were consecutive single carriers. The RIV field can indicate the start of the RB within the first and second CCs, as well as the length that can span both CCs. In other aspects, the transport block may not be mapped across two CCs. The transport block size can be calculated based on the obtained FDRA for each CC, and the transport block can be mapped to the first and second CCs separately. For example, as... Figure 11AAs shown, SCell and P(S)Cell are two carriers, but the UE can treat them as a single carrier. Each of SCell and P(S)Cell can have a corresponding RIV indicator and can be considered consecutive. In some respects, SCell and P(S)Cell can use the same or different SCS. Based on the index spanning the first CC and the second CC, the RIV indicator can indicate the scheduled PDCCH.

[0080] In some aspects, a transport block can be mapped across a first CC and a second CC, where the FDRA can be determined by the common RIV across the CCs. In such aspects, some parameters (e.g., SCS) may differ between the first CC and the second CC. The UE can determine an ACK or NACK based on the decoding result of the transport block spanning the first CC and the second CC. The UE can generate ACK / NACK bits and report them to the network. The UE PDSCH processing timeline can be determined based on the maximum required timeline between the first CC and the second CC. In some aspects, the maximum number of RBs that a transport block can span may not exceed 275. In some aspects, the maximum bandwidth that a transport block can span may not exceed 100MHz. In some aspects, if the UE is operating using a single CC, the maximum transport block size may not exceed the maximum transport block size.

[0081] Figure 12A-12B Figures 1200 and 1220 illustrate examples of DCI formats for individual and combined fields. This is based on the assumption that the number of scheduled CCs is 2. Figure 12A Figure 1200 may include up to two bits in the DCI for multi-CC scheduling. The DCI may include a VRB-to-PRB mapping field 1202 for the first CC and may include a VRB-to-PRB mapping field 1204 for the second CC. In some aspects, a 1-bit field may be used for RA Type 1, and interleaved VRB-to-PRB mappings are configured for a specific CC. If one or both CCs are RA Type 1 and are configured with interleaved VRB-to-PRB mappings, then Figure 12B Figure 1220 may include a one-bit VRB-to-PRB mapping field 1222. In some aspects, if both CCs are RA Type 1 and configured with interleaved VRB-to-PRB, the one-bit VRB-to-PRB mapping field may be applied to both CCs. In some aspects, if one of the CCs is RA Type 1 and configured with interleaved VRB-to-PRB, the one-bit VRB-to-PRB mapping field may be applied to the specific CC that is RA Type 1 and configured with interleaved VRB-to-PRB.

[0082] Figure 13 This is a call flow diagram 1300 showing the signaling between UE 1302 and base station 1304. Base station 1304 can be configured to provide at least one cell. UE 1302 can be configured to communicate with base station 1304. For example, in Figure 1 In the context of UE 1304, base station 1304 may correspond to base station 102 / 180, and therefore, a cell may include a geographic coverage area 110 in which communication coverage is provided and / or a small cell 102' having coverage area 110'. Furthermore, UE 1302 may at least correspond to UE 104. In another example, in Figure 3 In this context, base station 1304 can correspond to base station 310, and UE 1302 can correspond to UE 350. Optional aspects are shown with dashed lines.

[0083] As shown at 1306, base station 1304 can be configured with cross-carrier scheduling. The base station can be configured with a PDCCH that includes cross-carrier scheduling. Cross-carrier scheduling can include scheduling of uplink or downlink transmissions on more than one cell.

[0084] In some aspects, such as at 1308, to configure the PDCCH, base station 1304 can schedule PDSCH or PUSCH for PCell or P(S)Cell. For example, this can be performed by scheduling component 1540 of device 1502 1404. In some aspects, at least one cell may include SCell. The DCI of the PDCCH of the SCell can be scheduled for PDSCH or PUSCH for P(S)Cell, for example, as... Figure 4A , 4B and Figure 5 As shown in the image.

[0085] In some aspects, such as at 1310, to configure the PDCCH, base station 1304 can use DCI to schedule PDSCH on multiple cells. In some aspects, more than one cell may include a P(S)Cell. The DCI of the PDCCH of the P(S)Cell can be scheduled for PDSCH used in multiple cells. In some aspects, more than one cell may include an SCell. The DCI of the PDCCH of the SCell can be scheduled for PDSCH used in multiple cells. For example, in Figure 4A , 4B and Figure 5 In this context, PDCCH 406 and 506 can be scheduled for PDSCH of another cell (e.g., 404 and 504).

[0086] As shown at 1312, base station 1304 can send a PDCCH including cross-carrier scheduling to UE 1302. UE 1302 can receive the PDCCH including cross-carrier scheduling from base station 1304. The PDCCH may include a DCI configured to schedule uplink or downlink transmissions. The DCI may include at least one FDRA field indicating the RB used for uplink or downlink transmissions. In some aspects, the DCI may include a separate field for cross-carrier scheduling, for example, such as... Figures 6A-6D As shown in the diagram. The DCI may include fields for the serving cell and fields for another serving cell. In some aspects, the DCI may include joint fields that can be shared between the serving cell and another serving cell. Joint fields may include FDRA fields or VRB-to-PRB mapping fields, for example, such as... Figure 12A-12B As shown in the diagram. The value of the FDRA field can be linked by an RB set, where the scheduled PDSCH can be on multiple carriers, and the RB sets on multiple carriers can be configured via RRC signaling. In some aspects, a VRB-to-PRB mapping field may exist if at least one component carrier of the serving cell or another serving cell is configured with resource allocation (RA) type 1 and interleaved VRB-to-PRB. In some aspects, the DCI may include two bits for cross-carrier scheduling, for example, as... Figure 12A As shown in the diagram. In some aspects, the first bit may be a VRB-to-PRB mapping field for a first carrier, and the second bit may be a VRB-to-PRB mapping field for a second carrier.

[0087] As shown at 1314, base station 1304 and UE 1302 can communicate with each other. Base station 1304 and UE 1302 can communicate with each other based on cross-carrier scheduling configured through DCI.

[0088] Figure 14 This is a flowchart 1400 of a wireless communication method. The method can be performed by a base station or a component of a base station (e.g., base station 102 / 180; device 1502; baseband unit 1504, which may include memory 376, and can be the entire base station 310 or a component of base station 310 (such as TX processor 316, RX processor 370, and / or controller / processor 375). One or more of the operations shown can be omitted, interchanged, and / or performed simultaneously. Optional aspects are shown using dashed lines. The method can allow the base station to use a single DCI to schedule cross-carrier scheduling of uplink and / or downlink transmissions.

[0089] At 1402, the base station can be configured with PDCCH including cross-carrier scheduling. For example, 1402 can be performed by the scheduling component 1540 of device 1502. Cross-carrier scheduling can include scheduling of uplink or downlink transmissions on more than one cell. For example, refer to... Figure 13 At 1306, base station 1304 can be configured with PDCCH including cross-carrier scheduling.

[0090] In some aspects, such as at 1404, to configure the PDCCH, the base station can schedule the PDSCH or PUSCH for the PCell or P(S)Cell. For example, this can be performed by the scheduling component 1540 of device 1502 at 1404. In some aspects, at least one cell may include an SCell. The DCI of the PDCCH of the SCell can be scheduled for the PDSCH or PUSCH for the P(S)Cell, for example, as... Figure 4A , 4B and Figure 5 As shown in the image. Reference Figure 13 For example, base station 1304 at 1308 can schedule PDSCH or PUSCH for PCell or P(S)Cell.

[0091] In some aspects, such as at 1406, to configure the PDCCH, the base station can use the DCI to schedule PDSCHs on multiple cells. For example, 1406 can be performed by the scheduling component 1540 of device 1502. In some aspects, more than one cell may include a P(S)Cell. The DCI of the PDCCH of the P(S)Cell can schedule PDSCHs for multiple cells. In some aspects, more than one cell may include an SCell. The DCI of the PDCCH of the SCell can schedule PDSCHs for multiple cells. For example, in... Figure 4A , 4B and Figure 5 In this context, PDCCH 406 and 506 can be scheduled for PDSCH in another cell (e.g., 404 and 504). (See reference) Figure 13 For example, base station 1304 can schedule PDSCH for multiple cells at 1310.

[0092] At point 1408, the base station may transmit a PDCCH including cross-carrier scheduling. For example, point 1408 may be performed by the PDCCH component 1542 of device 1502. The base station may transmit a PDCCH including cross-carrier scheduling to the UE. The PDCCH may include DCI configured to schedule uplink or downlink transmissions. (See reference) Figure 13Base station 1304 can send PDCCH 1312, which includes cross-carrier scheduling, to UE 1302. The DCI may include at least one FDRA field indicating an RB for uplink or downlink transmission. In some aspects, the DCI may include a separate field for cross-carrier scheduling, for example, such as... Figures 6A-6D As shown in the diagram. The DCI may include fields for the serving cell and fields for another serving cell. In some aspects, the DCI may include joint fields that can be shared between the serving cell and another serving cell. Joint fields may include FDRA fields or VRB-to-PRB mapping fields, for example, such as... Figure 12A-12B As shown in the diagram. The value of the FDRA field can be linked by an RB set, where the scheduled PDSCH can be on multiple carriers, and the RB set on multiple carriers can be configured via RRC signaling. In some aspects, a VRB-to-PRB mapping field may exist if at least one component carrier of the serving cell or another serving cell is configured with resource allocation (RA) type 1 and interleaved VRB-to-PRB. In some aspects, the DCI may include two bits for cross-carrier scheduling, for example, as... Figure 12A As shown in the diagram. In some aspects, the first bit may be a VRB-to-PRB mapping field for a first carrier, and the second bit may be a VRB-to-PRB mapping field for a second carrier.

[0093] At point 1410, the base station can communicate with the UE. For example, 1410 can be performed by the communication component 1544 of device 1502. The base station can communicate with the UE based on cross-carrier scheduling configured via DCI. For example, refer to... Figure 13 At point 1314, base station 1304 and UE 1302 can communicate with each other based on cross-carrier scheduling.

[0094] Figure 15Figure 1500 illustrates an example of a hardware implementation of device 1502. Device 1502 is a BS and includes a baseband unit 1504. Baseband unit 1504 can communicate with UE 104 via cellular radio frequency (RF) transceiver 1522. Baseband unit 1504 may include computer-readable medium / memory. Baseband unit 1504 is responsible for general processing, including executing software stored on computer-readable medium / memory. When executed by baseband unit 1504, the software causes baseband unit 1504 to perform the various functions described above. Computer-readable medium / memory can also be used to store data manipulated by baseband unit 1504 when executing the software. Baseband unit 1504 also includes a receiving component 1530, a communication manager 1532, and a transmitting component 1534. Communication manager 1532 includes one or more of the components shown. Components within communication manager 1532 may be stored in computer-readable medium / memory and / or configured as hardware within baseband unit 1504. Baseband unit 1504 may be Figure 3 The components of BS 310 may include at least one of TX processor 316, RX processor 370 and controller / processor 375, and / or memory 376. Figure 15 The transmission component 1534 of the device 1502 can correspond to Figure 3 The BS 310's TX processor 316. Figure 15 The receiving component 1530 of the device 1502 can correspond to Figure 3 The BS 310's RX processor 370.

[0095] Communication manager 1532 includes scheduling component 1540, which can be configured to include PDCCH with cross-carrier scheduling, for example, as in combination with Figure 14 As described in 1402. Scheduling component 1540 can be configured to schedule PDSCH or PUSCH for PCell or P(S)Cell, for example, as in combination with... Figure 14 As described in section 1404. Scheduling component 1540 can be configured to use DCI to schedule PDSCHs on multiple cells, for example, as in combination with... Figure 14 As described in 1406. The communication manager 1532 also includes a PDCCH component 1542, which can transmit PDCCHs including cross-carrier scheduling, for example, as in combination with... Figure 14 As described in 1408. The communication manager 1532 also includes a communication component 1544 that can communicate with the UE, for example, as in combination with Figure 14 As described in 1410.

[0096] The apparatus may include means for performing Figure 14The other components of each box in the algorithm of the aforementioned flowchart. Therefore, Figure 14 Each block in the aforementioned flowchart can be executed by a component, and the apparatus can include one or more of these components. A component can be one or more hardware components specifically configured to perform the stated process / algorithm, can be implemented by a processor configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0097] In one configuration, apparatus 1502 (and in particular, baseband unit 1504) includes a unit for configuring a PDCCH, which includes cross-carrier scheduling of uplink or downlink transmissions on more than one cell. The apparatus includes a unit for transmitting a PDCCH including cross-carrier scheduling to a UE, the PDCCH including a DCI configured to schedule uplink or downlink transmissions. The apparatus includes a unit for communicating with the UE based on cross-carrier scheduling configured via the DCI. The apparatus further includes a unit for scheduling a PDSCH or PUSCH for a PCell or P(S)Cell. The apparatus further includes a unit for using the DCI to schedule PDSCHs on multiple cells. The aforementioned units may be one or more of the aforementioned components of apparatus 1502 configured to perform the functions described by the aforementioned units. As described above, apparatus 1502 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, the aforementioned units may be TX processor 316, RX processor 370, and controller / processor 375 configured to perform the functions described by the aforementioned units.

[0098] Figure 16 This is a flowchart 1600 of a wireless communication method. The method can be performed by a UE or a component of a UE (e.g., UE 104; device 1702; cellular baseband processor 1704, which may include memory 360, and may be the entire UE 350 or a component of UE 350 (e.g., TX processor 368, RX processor 356, and / or controller / processor 359). One or more of the operations shown can be omitted, interchanged, and / or performed simultaneously. Optional aspects are shown using dashed lines. The method can enable the UE to receive cross-carrier scheduling configured to schedule uplink or downlink transmissions in more than one cell.

[0099] At 1602, the UE can receive a PDCCH including cross-carrier scheduling. For example, 1602 can be performed by the scheduling component 1740 of device 1702. The UE can receive a PDCCH including cross-carrier scheduling from the base station. For example, refer to... Figure 13UE 1302 can receive PDCCH 1312, which includes cross-carrier scheduling, from base station 1304. The PDCCH may include DCI configured to schedule uplink or downlink transmissions on more than one cell. In some aspects, the PDCCH may schedule PDSCH or PUSCH for PCell or P(S)Cell. In some aspects, the PDCCH of SCell may schedule PDSCH or PUSCH for P(S)Cell. In some aspects, the PDCCH may use DCI to schedule PDSCH on multiple cells. In some aspects, the PDCCH of P(S)Cell may schedule PDSCH for multiple cells. In some aspects, the PDCCH of SCell may schedule PDSCH for multiple cells. In some aspects, the DCI may include a separate field for cross-carrier scheduling, such as... Figures 6A-6D As shown in the diagram. The DCI may include fields for the serving cell and fields for another serving cell. The DCI may include joint fields that can be shared between the serving cell and another serving cell. In some aspects, the joint fields may include frequency domain resource allocation (FDRA) fields, for example, such as... Figure 12A-12B As shown in the diagram. In some aspects, the union field may include a VRB-to-PRB mapping field, for example, as... Figure 12A-12B As shown in the diagram. In some aspects, the value of the FDRA field can be linked by a set of resource blocks (RBs), where the scheduled PDSCH is on multiple carriers. The set of RBs on multiple carriers can be configured via RRC signaling. In some aspects, a VRB-to-PRB mapping field can exist if at least one component carrier of the serving cell or another serving cell is configured with resource allocation (RA) type 1 and interleaved VRB-to-PRB. In some aspects, the DCI can include two bits for cross-carrier scheduling, for example, as... Figure 12A As shown in the diagram. For example, the first bit may correspond to the VRB-to-PRB mapping field for the first carrier, and the second bit may correspond to the VRB-to-PRB mapping field for the second carrier.

[0100] At 1604, the UE can communicate with the base station. For example, 1604 can be performed by the communication component 1742 of device 1702. The UE can communicate with the base station based on cross-carrier scheduling configured via DCI. For example, refer to... Figure 13 At 1314, UE 1302 and base station 1304 can communicate with each other based on cross-carrier scheduling.

[0101] Figure 17Figure 1700 illustrates an example of a hardware implementation for device 1702. Device 1702 is a UE and includes: a cellular baseband processor 1704 (also referred to as a modem) coupled to a cellular RF transceiver 1722 and one or more Subscriber Identity Module (SIM) cards 1720; an application processor 1706 coupled to a Secure Digital Card (SD) card 1708 and a screen 1710; a Bluetooth module 1712; a Wireless Local Area Network (WLAN) module 1714; a Global Positioning System (GPS) module 1716; and a power supply 1718. The cellular baseband processor 1704 communicates with UE 104 and / or BS 102 / 1170 via the cellular RF transceiver 1722. The cellular baseband processor 1704 may include computer-readable media / memory. The computer-readable media / memory may be non-transitory. The cellular baseband processor 1704 is responsible for general processing, including executing software stored on the computer-readable media / memory. When the software is executed by the cellular baseband processor 1704, it causes the cellular baseband processor 1704 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1704 during software execution. The cellular baseband processor 1704 also includes a receiving component 1730, a communication manager 1732, and a transmitting component 1734. The communication manager 1732 includes one or more of the components shown. The components within the communication manager 1732 can be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 1704. The cellular baseband processor 1704 can be... Figure 3 The UE 350 is a component of the UE and may include at least one of a TX processor 368, an RX processor 356, and a controller / processor 359, and / or a memory 360. In one configuration, the device 1702 may be a modem chip and may only include a cellular baseband processor 1704, and in another configuration, the device 1702 may be the entire UE (e.g., see [link to relevant documentation]). Figure 3 (350) and includes the aforementioned additional module of device 1702. Figure 17 The transmission component 1734 of the device 1702 can correspond to Figure 3 The UE 350's TX processor 368. Figure 17 The receiving component 1730 of the device 1702 can correspond to Figure 3 The UE350's RX processor 356.

[0102] Communication manager 1732 includes scheduling component 1740, which is configured to receive PDCCH including cross-carrier scheduling, for example, as in combination with Figure 16 As described in 1602. The communication manager 1732 also includes a communication component 1742 configured to communicate with a base station, for example, as in conjunction with... Figure 16 As described in 1604.

[0103] The apparatus may include execution Figure 16 The other components of each box in the algorithm of the aforementioned flowchart. Therefore, Figure 16 Each block in the aforementioned flowchart can be executed by a component, and the apparatus can include one or more of these components. A component can be one or more hardware components specifically configured to perform the stated process / algorithm, can be implemented by a processor configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0104] In one configuration, apparatus 1702 (and in particular, cellular baseband unit 1704) includes: a unit for receiving a PDCCH including cross-carrier scheduling from a base station, the PDCCH including a DCI configured to schedule uplink or downlink transmissions on more than one cell. The apparatus includes: a unit for communicating with the base station based on the cross-carrier scheduling configured via the DCI. The aforementioned unit may be one or more of the aforementioned components of apparatus 1702 configured to perform the functions described herein. As described above, apparatus 1702 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, the aforementioned unit may be the TX processor 368, the RX processor 356, and the controller / processor 359 configured to perform the functions described herein.

[0105] The aspects provided herein offer configurations for configuring cross-carrier scheduling of uplink or downlink transmissions on more than one cell. For example, a base station can configure an enhanced PDCCH to include cross-carrier scheduling for uplink or downlink transmissions on more than one cell. In some aspects, an enhanced PDCCH associated with a first cell can be configured to schedule a PDSCH or PUSCH for a second cell. In some aspects, an enhanced PDCCH can use a single DCI to schedule cross-carrier scheduling on more than one cell. At least one advantage of this disclosure is that a single DCI can schedule data channels on multiple carriers at once, which can improve spectral efficiency.

[0106] It is to be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is illustrative of the example method. It is to be understood that the specific order or hierarchy of the blocks in the process / flowchart may be rearranged based on design preferences. Furthermore, some blocks may be combined or omitted. The appended method claims present the elements of various blocks in the example order and are not intended to be limited to the specific order or hierarchy presented.

[0107] The following examples are merely illustrative and may be combined with, but are not limited to, other embodiments or aspects of the teachings described herein.

[0108] Aspect 1 is a method for wireless communication at a base station, the method comprising: sending a PDCCH including cross-carrier scheduling to a UE, the PDCCH including a DCI configured to schedule uplink transmissions or downlink transmissions, the DCI including at least one FDRA field indicating RBs for uplink transmissions or downlink transmissions for more than one cell; and communicating with the UE based on the cross-carrier scheduling configured via the DCI.

[0109] In aspect 2, the method according to aspect 1 further includes: more than one cell including SCell, wherein configuring PDCCH further includes: using the DCI of the PDCCH of the SCell to schedule the PDSCH or PUSCH for the PSCell.

[0110] In aspect 3, the method according to aspect 1 or 2 further includes: more than one cell including PSCell or SCell, wherein configuring PDCCH further includes: using the DCI of the PDCCH of PSCell to schedule PDSCH on multiple cells, or using the DCI of the PDCCH of SCell to schedule PDSCH on multiple cells.

[0111] In aspect 4, the method described according to any of aspects 1-3 further includes: configuring the PDCCH to include cross-carrier scheduling of uplink or downlink transmissions of more than one cell.

[0112] In aspect 5, the method according to any of aspects 1-4 further includes: the DCI includes a separate FDRA field for cross-carrier scheduling.

[0113] In aspect 6, the method according to any one of aspects 1-5 further includes: the DCI includes at least one FDRA field for the serving cell and at least one FDRA field for another serving cell.

[0114] In aspect 7, the method according to any one of aspects 1-6 further includes: the DCI includes two bits for cross-carrier scheduling.

[0115] In aspect 8, the method according to any one of aspects 1-7 further comprises: a first bit being a VRB-to-PRB mapping field for a first carrier, and a second bit being a VRB-to-PRB mapping field for a second carrier.

[0116] In aspect 9, the method according to any of aspects 1-8 further includes: DCI including a joint FDRA field shared between the serving cell and another serving cell.

[0117] In aspect 10, the method according to any of aspects 1-9 further includes: the combined FDRA field includes a VRB-to-PRB mapping field.

[0118] In aspect 11, the method according to any one of aspects 1-10 further includes: the value of at least one FDRA field is linked by an RB set, wherein the scheduled PDSCH is on multiple carriers, wherein the RB set on the multiple carriers is configured via RRC signaling.

[0119] In aspect 12, the method according to any one of aspects 1-10 further includes: if at least one component carrier of the serving cell or another serving cell is configured to have RA type 1 and interleaved VRB-to-PRB, then a VRB-to-PRB mapping field exists.

[0120] Aspect 13 is an apparatus that includes a transceiver, one or more processors, and one or more memories that communicate electronically with the one or more processors and store instructions that can be executed by the one or more processors to cause the apparatus to implement the methods of any of aspects 1-12.

[0121] Aspect 14 is a system or apparatus that includes units for implementing methods or implementation means of any of aspects 1-12.

[0122] Aspect 15 is a non-transitory computer-readable storage medium that stores instructions which can be executed by one or more processors to cause one or more processors to implement the methods of any of aspects 1-12.

[0123] Aspect 16 is a method of wireless communication at a UE, comprising: receiving from a base station a PDCCH including cross-carrier scheduling, the PDCCH including a DCI configured to schedule uplink transmissions or downlink transmissions, the DCI including at least one FDRA field indicating RBs for uplink transmissions or downlink transmissions on more than one cell; and communicating with the base station based on the cross-carrier scheduling configured via the DCI.

[0124] In aspect 17, the method according to aspect 16 further includes: scheduling the PDCCH of the SCell for the PDSCH or PUSCH of the PSCell.

[0125] In aspect 18, the method according to aspect 16 or 17 further includes: the PDCCH of the PSCell using DCI to schedule PDSCH on multiple cells, or the PDCCH of the SCell using DCI to schedule PDSCH on multiple cells.

[0126] In aspect 19, the method according to any of aspects 16-18, wherein the DCI includes a separate FDRA field for cross-carrier scheduling.

[0127] In aspect 20, the method according to any aspect of aspects 16-19 further includes: the DCI includes at least one FDRA field for the serving cell and at least one FDRA field for another serving cell.

[0128] In aspect 21, the method according to any one of aspects 16-20 further includes: the DCI includes two bits for cross-carrier scheduling.

[0129] In aspect 22, the method according to any one of aspects 16-21 further includes: a first bit being a VRB-to-PRB mapping field for a first carrier, and a second bit being a VRB-to-PRB mapping field for a second carrier.

[0130] In aspect 23, the method according to any aspect of aspects 16-22 further includes: the DCI includes a joint FDRA field shared between the serving cell and another serving cell.

[0131] In aspect 24, the method described according to any of aspects 16-23 further includes: the combined FDRA field includes a VRB-to-PRB mapping field.

[0132] In aspect 25, the method according to any one of aspects 16-24 further includes: the value of at least one FDRA field is linked by an RB set, wherein the scheduled PDSCH is on multiple carriers, and the RB set on the multiple carriers is configured via RRC signaling.

[0133] In aspect 26, the method according to any one of aspects 16-25 further includes: if at least one component carrier of the serving cell or another serving cell is configured to have RA type 1 and interleaved VRB-to-PRB, then a VRB-to-PRB mapping field exists.

[0134] Aspect 27 is an apparatus that includes a transceiver, one or more processors, and one or more memories that communicate electronically with the one or more processors and store instructions that can be executed by the one or more processors to cause the apparatus to implement the methods of any of aspects 16-26.

[0135] Aspect 28 is a system or apparatus comprising units for implementing any aspect of aspects 16-26 or for implementing any aspect of aspects 16-26.

[0136] Aspect 29 is a non-transitory computer-readable storage medium that stores instructions which can be executed by one or more processors to cause one or more processors to implement the methods of any of aspects 16-26.

[0137] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to limit themselves to the aspects shown herein, but rather to impose the full scope consistent with the language of the claims, wherein, unless specifically stated otherwise, references to singular elements are not intended to mean “one and only one,” but rather “one or more.” Terms such as “if,” “when,” and “at…” should be interpreted as meaning “under the condition of,” rather than implying a direct temporal relationship or reaction. That is, these phrases (e.g., “when”) do not imply an action in response to an action or an immediate action during the occurrence of an action, but simply mean that an action will occur if the condition is met, without requiring a specific or immediate temporal constraint on the action to occur. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” should not be construed as preferred or superior to other aspects. Unless otherwise specifically stated, the term “some” refers to one or more. For example, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. In particular, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents of components throughout the various aspects described in this disclosure are expressly incorporated herein by reference and are intended to be covered by the claims, and such structural and functional equivalents are well known or will be known to those skilled in the art. Furthermore, the disclosure herein is not intended to be offered to the public, whether or not such disclosure is explicitly stated in the claims. Terms such as “module,” “apparatus,” “element,” and “device” are not substitutes for the term “unit.” Therefore, no claim element should be interpreted as a functional module unless the element is explicitly stated using the phrase “unit for…”.

Claims

1. A method for wireless communication at a base station, comprising: The system transmits a Physical Downlink Control Channel (PDCCH) including cross-carrier scheduling to a User Equipment (UE). The PDCCH includes a single Downlink Control Information (DCI) configured to schedule uplink or downlink transmissions. The single DCI includes at least one Frequency Domain Resource Allocation (FDRA) field indicating a resource block (RB) for the uplink or downlink transmission on at least a first serving cell and a second serving cell, wherein the FDRA field indicates the cross-carrier scheduling. Alternatively, the single DCI includes a Virtual Resource Block to Physical Resource Block (VRB to PRB) mapping field, wherein the VRB to PRB mapping field includes a first bit for a first carrier and a second bit for a second carrier. as well as Communication with the UE is based on the cross-carrier scheduling configured through the single DCI.

2. The method according to claim 1, wherein, At least the first serving cell or the second serving cell includes a secondary cell (SCell), wherein configuring the PDCCH includes: The single DCI of the PDCCH of the SCell is used to schedule the Physical Downlink Shared Channel (PDSCH) or Physical Uplink Shared Channel (PUSCH) for the Primary Secondary Cell (PSCell).

3. The method according to claim 1, wherein, At least the first serving cell or the second serving cell includes a primary secondary cell (PSCell) or a secondary cell (SCell), wherein configuring the PDCCH includes: Using the single DCI of the PDCCH of the PSCell, schedule the Physical Downlink Shared Channel (PDSCH) on multiple cells, or The PDSCH on multiple cells is scheduled using the single DCI of the PDCCH of the SCell.

4. The method according to claim 1, further comprising: Configuring the PDCCH includes cross-carrier scheduling of the uplink or downlink transmissions on at least the first serving cell or the second serving cell.

5. The method according to claim 1, wherein, The single DCI includes two bits for the cross-carrier scheduling, the two bits being the first bit and the second bit.

6. The method according to claim 1, wherein, The single DCI includes a joint FDRA field shared between the serving cell and another serving cell.

7. The method according to claim 6, wherein, The combined FDRA field includes the VRB to PRB mapping field.

8. A method for wireless communication at a base station, comprising: A Physical Downlink Control Channel (PDCCH) with cross-carrier scheduling is transmitted to a User Equipment (UE). The PDCCH includes a single Downlink Control Information (DCI) configured to schedule uplink or downlink transmissions. The single DCI includes a Joint Frequency Domain Resource Allocation (FDRA) field shared between serving cells and indicating the cross-carrier scheduling. The joint FDRA field includes a Virtual Resource Block to Physical Resource Block (VRB to PRB) mapping field. The values ​​of the joint FDRA field are linked through a set of Resource Blocks (RBs). The scheduled Physical Downlink Shared Channel (PDSCH) is on multiple carriers, and the RB sets on these multiple carriers are configured via Radio Resource Control (RRC) signaling. Communication with the UE is based on the cross-carrier scheduling configured through the single DCI.

9. A method for wireless communication at a base station, comprising: The user equipment (UE) is sent a physical downlink control channel (PDCCH) including cross-carrier scheduling. The PDCCH includes a single downlink control information (DCI) configured to schedule uplink or downlink transmissions. The single DCI includes a joint frequency domain resource allocation (FDRA) field shared between the serving cell and another serving cell and indicating the cross-carrier scheduling. The joint FDRA field includes a virtual resource block to physical resource block (VRB to PRB) mapping field, wherein the VRB to PRB mapping field exists if at least one component carrier of the serving cell or the other serving cell is configured with resource allocation (RA) type 1 and interleaved VRB to PRB. Communication with the UE is based on the cross-carrier scheduling configured through the single DCI.

10. An apparatus for wireless communication at a base station, comprising: Memory; transceiver; as well as At least one processor, coupled to the memory, is configured to: The transceiver transmits a Physical Downlink Control Channel (PDCCH) including cross-carrier scheduling to a User Equipment (UE). The PDCCH includes a single Downlink Control Information (DCI) configured to schedule uplink or downlink transmissions. The single DCI includes at least one Frequency Domain Resource Allocation (FDRA) field indicating a resource block (RB) for the uplink or downlink transmission on at least a first serving cell and a second serving cell, wherein the FDRA field indicates the cross-carrier scheduling. Alternatively, the single DCI includes a Virtual Resource Block to Physical Resource Block (VRB to PRB) mapping field, wherein the VRB to PRB mapping field includes a first bit for a first carrier and a second bit for a second carrier. as well as Based on the cross-carrier scheduling configured through the single DCI, communication is made with the UE via the transceiver.

11. A method for wireless communication at a user equipment (UE), comprising: The base station receives a physical downlink control channel (PDCCH) including cross-carrier scheduling, the PDCCH including a single downlink control information (DCI) configured to schedule uplink or downlink transmissions, the single DCI including at least one frequency domain resource allocation (FDRA) field indicating resource blocks (RBs) for the uplink or downlink transmissions on at least a first serving cell and a second serving cell, wherein the FDRA field indicates the cross-carrier scheduling, or the single DCI includes a virtual resource block to physical resource block (VRB to PRB) mapping field, the VRB to PRB mapping field including a first bit for a first carrier and a second bit for a second carrier; as well as Communication with the base station is based on the cross-carrier scheduling configured through the single DCI.

12. The method according to claim 11, wherein, The PDCCH scheduling of the secondary cell (SCell) is used for the physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH) of the primary secondary cell (PSCell).

13. The method of claim 11, wherein The PDCCH of the primary secondary cell (PSCell) uses the single DCI to schedule the Physical Downlink Shared Channel (PDSCH) on multiple cells, or The PDCCH of the auxiliary cell (SCell) uses the single DCI to schedule the PDSCH on the multiple cells.

14. The method according to claim 11, wherein, The single DCI includes at least one FDRA field for the serving cell and at least one FDRA field for another serving cell.

15. The method according to claim 11, wherein, The single DCI includes two bits for the cross-carrier scheduling, the two bits being the first bit and the second bit.

16. The method according to claim 11, wherein, The single DCI includes a joint FDRA field shared between the serving cell and another serving cell.

17. The method according to claim 16, wherein, The combined FDRA field includes the VRB to PRB mapping field.

18. A method for wireless communication at a user equipment (UE), comprising: The base station receives a Physical Downlink Control Channel (PDCCH) including cross-carrier scheduling, the PDCCH including a single Downlink Control Information (DCI) configured to schedule uplink or downlink transmissions, wherein the single DCI includes a Joint Frequency Domain Resource Allocation (FDRA) field, the joint FDRA field being shared between serving cells and indicating the cross-carrier scheduling, wherein the joint FDRA field includes a Virtual Resource Block to Physical Resource Block (VRB to PRB) mapping field, wherein the values ​​of the joint FDRA field are linked through a set of Resource Blocks (RBs), wherein the scheduled Physical Downlink Shared Channel (PDSCH) is on multiple carriers, and wherein the set of RBs on the multiple carriers is configured via Radio Resource Control (RRC) signaling; and Communication with the base station is based on the cross-carrier scheduling configured through the single DCI.

19. A method for wireless communication at a user equipment (UE), comprising: The base station receives a Physical Downlink Control Channel (PDCCH) including cross-carrier scheduling, the PDCCH including a single Downlink Control Information (DCI) configured to schedule uplink or downlink transmissions, wherein the single DCI includes a Joint Frequency Domain Resource Allocation (FDRA) field, the joint FDRA field being shared between the serving cell and another serving cell and indicating the cross-carrier scheduling, wherein the joint FDRA field includes a Virtual Resource Block to Physical Resource Block (VRB to PRB) mapping field, wherein the VRB to PRB mapping field exists if at least one component carrier of the serving cell or the other serving cell is configured with Resource Allocation (RA) type 1 and interleaved VRB to PRB; and Communication with the base station is based on the cross-carrier scheduling configured through the single DCI.

20. An apparatus for wireless communication at a user equipment (UE), comprising: Memory; transceiver; as well as At least one processor, coupled to the memory, is configured to: The transceiver receives from the base station a physical downlink control channel (PDCCH) including cross-carrier scheduling, the PDCCH including a single downlink control information (DCI) configured to schedule uplink or downlink transmissions, the single DCI including at least one frequency domain resource allocation (FDRA) field indicating resource blocks (RBs) for the uplink or downlink transmissions on at least a first serving cell and a second serving cell, wherein the FDRA field indicates the cross-carrier scheduling, or the single DCI includes a virtual resource block to physical resource block (VRB to PRB) mapping field, the VRB to PRB mapping field including a first bit for a first carrier and a second bit for a second carrier; as well as Based on the cross-carrier scheduling configured through the single DCI, communication is made with the base station via the transceiver.

21. The apparatus according to claim 20, wherein, The PDCCH scheduling of the secondary cell (SCell) is used for the physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH) of the primary secondary cell (PSCell).

22. The apparatus of claim 20, wherein The PDCCH of the primary secondary cell (PSCell) uses the single DCI to schedule the Physical Downlink Shared Channel (PDSCH) on multiple cells, or The PDCCH of the auxiliary cell (SCell) uses the single DCI to schedule the PDSCH on the multiple cells.

23. The apparatus according to claim 20, wherein, The single DCI includes at least one FDRA field for the serving cell and at least one FDRA field for another serving cell.

24. The apparatus according to claim 20, wherein, The single DCI includes a joint FDRA field shared between the serving cell and another serving cell.

Images