Apparatus and method for cross-carrier scheduling in wireless communication network

Abstract

The invention relates to an apparatus and method for cross-carrier scheduling in a wireless communication network. The apparatus comprises: a transceiver configured to communicate with a UE using a first carrier comprising a first set of parameters and a second carrier comprising a second set of parameters smaller than the first set of parameters; one or more processors coupled to the transceiver and configured to: configure the UE to use a predetermined minimum timing between the first carrier and the second carrier; generating scheduling information that schedules transmission of a plurality of data transmissions with the UE over a plurality of scheduled time slots of the first carrier, each of the plurality of data transmissions corresponding to a respective one of the plurality of scheduled time slots; and transmitting scheduling information in a scheduling slot of the second carrier to schedule the UE to transmit the plurality of data transmissions according to the predetermined minimum timing that is longer in duration than a minimum delay between the grant on the PDCCH of the second carrier and the plurality of data transmissions on the PDSCH scheduled by the grant on the first carrier.

Description

[0001] This application is a divisional application of the Chinese invention patent application with application date of November 7, 2020 and application number 202080075089.1.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This patent application claims priority to and the benefit of co-pending non-provisional application No. 17 / 091,918 filed in the U.S. Patent Office on November 6, 2020, and provisional application No. 62 / 933,243 filed in the U.S. Patent Office on November 8, 2019, which applications are assigned to the assignee of this application and are expressly incorporated herein by reference as if fully set forth herein in their entirety for all applicable purposes. Technical Field

[0004] The techniques discussed below relate generally to wireless communication systems, and more particularly, to cross-carrier scheduling in wireless communications. Background Art

[0005] In a fifth generation (5G) new radio (NR) network, a base station and a user equipment (UE) may communicate over a carrier, which may be time-divided into multiple frames, subframes, time slots, and symbols. The base station may schedule data transmissions to and / or from the UE within one or more time slots of the carrier, and use downlink control information (DCI) to send scheduling information indicating resources (e.g., time-frequency resources) scheduled for data transmission. The UE may detect the DCI in a predetermined search space.

[0006] In some wireless communication networks, user equipment (UE) can be configured to combine multiple carriers to increase the transmission bandwidth beyond a single carrier. One such method is known as carrier aggregation (CA), where multiple carriers are aggregated, bundled or combined to provide a wider transmission bandwidth, which facilitates higher peak data rates and / or overall capacity.

[0007] Each carrier waveform can use the same or different numerology. The numerology of a waveform refers to the subcarrier spacing and cyclic prefix (CP) overhead of the waveform. Different subcarrier spacings can be associated with different symbol durations, including CP lengths. For example, an extensible numerology can support subcarrier spacings ranging from 15kHz to 480kHz. Summary of the invention

[0008] An overview of one or more aspects of the present disclosure is given below to provide a basic understanding of these aspects. This overview is not an extensive review of all expected features of the present disclosure, and is neither intended to identify key or important elements of all aspects of the present disclosure, nor is it intended to describe the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in some form as a preface to a more detailed description presented later.

[0009] In one example, a method of wireless communication at a scheduling entity in a wireless communication network is disclosed. The method may include generating scheduling information that schedules transmission of multiple data transmissions with a user equipment (UE) on multiple time slots of a first carrier including a first parameter set. Each of the multiple data transmissions may correspond to a respective one of the multiple time slots. The method may also include sending the scheduling information within a control resource allocated based on a time slot index of the multiple time slots on a second carrier, the second carrier including a second parameter set that is less than the first parameter set.

[0010] Another example provides a method for wireless communication at a user equipment (UE) in a wireless communication network. The method may include receiving scheduling information on a first carrier including a first parameter set. The scheduling information may schedule the transmission of multiple data transmissions with the UE on multiple time slots of a second carrier including a second parameter set greater than the first parameter set. Each of the multiple data transmissions may correspond to a respective one of the multiple time slots. The method may also include determining a relative timing position of the multiple time slots based on an association between the multiple time slots and a control resource allocated to the scheduling information, and decoding the scheduling information based on an order of the relative timing positions of the multiple time slots.

[0011] Another aspect of the present disclosure provides an apparatus for cross-carrier scheduling in a wireless communication network. The apparatus includes a transceiver configured to communicate with a user equipment (UE) using a first carrier including a first parameter set and a second carrier including a second parameter set that is smaller than the first parameter set. The apparatus also includes a memory and a processor coupled to the transceiver and the memory. The processor and the memory may be configured to generate scheduling information that schedules the transmission of multiple data transmissions with the UE on multiple time slots of the first carrier. Each of the multiple data transmissions may correspond to a corresponding one of the multiple time slots. The processor and the memory may also be configured to send scheduling information within a control resource allocated based on a time slot index of multiple time slots on the second carrier.

[0012] Another aspect of the present disclosure provides a user equipment (UE) for wireless communication. The UE includes a transceiver configured to communicate with a scheduling entity using a first carrier including a first parameter set and a second carrier including a second parameter set greater than the first parameter set. The UE also includes a memory and a processor coupled to the transceiver and the memory. The processor and the memory may be configured to receive scheduling information on the first carrier. The scheduling information may schedule the transmission of multiple data transmissions with the UE on multiple time slots of the second carrier. Each of the multiple data transmissions may correspond to a corresponding one of the multiple time slots. The processor and the memory may also be configured to determine the relative timing positions of the multiple time slots based on an association between the multiple time slots and the control resources allocated to the scheduling information, and decode the scheduling information in an order based on the relative timing positions of the multiple time slots.

[0013] Another aspect of the present disclosure provides an apparatus for cross-carrier scheduling in a wireless communication network, comprising: a transceiver configured to communicate with a user equipment (UE) using a first carrier including a first parameter set and a second carrier including a second parameter set smaller than the first parameter set; one or more processors coupled to the transceiver, wherein the one or more processors and are configured to: configure the UE to use a predetermined minimum timing between the first carrier and the second carrier; generate scheduling information, the scheduling information scheduling the transmission of multiple data transmissions with the UE on multiple scheduled time slots of the first carrier, each of the multiple data transmissions corresponding to a corresponding one of the multiple scheduled time slots; and send the scheduling information in a scheduled time slot of the second carrier to schedule the UE to transmit the multiple data transmissions according to the predetermined minimum timing between the first carrier and the second carrier, the predetermined minimum timing being greater in duration than a minimum delay between a grant on a physical downlink control channel (PDCCH) of the second carrier and multiple data transmissions on a physical downlink shared channel (PDSCH) on the first carrier scheduled by the grant.

[0014] Another aspect of the present disclosure provides a method for cross-carrier scheduling in a wireless communication network, comprising: configuring a user equipment UE to use a predetermined minimum timing between a first carrier configured with a first parameter set and a second carrier configured with a second parameter set smaller than the first parameter set; generating scheduling information, the scheduling information scheduling the transmission of multiple data transmissions with the UE on multiple scheduled time slots of the first carrier, each of the multiple data transmissions corresponding to a corresponding one of the multiple scheduled time slots; and sending the scheduling information in a scheduled time slot of the second carrier to schedule the UE to transmit the multiple data transmissions according to the predetermined minimum timing between the first carrier and the second carrier, the predetermined minimum timing being greater in duration than a minimum delay between a grant on a physical downlink control channel PDCCH of the second carrier and multiple data transmissions on a physical downlink shared channel PDSCH of the first carrier scheduled by the grant.

[0015] Another aspect of the present disclosure provides a user equipment UE for wireless communication, comprising: a transceiver, configured to communicate with a scheduling entity using a first carrier including a first parameter set and a second carrier including a second parameter set larger than the first parameter set; one or more processors, coupled to the transceiver, wherein the one or more processors and are configured to: receive scheduling information in a scheduling time slot of the first carrier, the scheduling information scheduling the transmission of multiple data transmissions on multiple scheduled time slots of the second carrier, each of the multiple data transmissions corresponding to a corresponding one of the multiple scheduled time slots; and transmit the multiple data transmissions in the multiple scheduled time slots according to a predetermined minimum timing between a control resource of the first carrier and the multiple scheduled time slots of the second carrier, the predetermined minimum timing being greater in duration than a minimum delay between a grant on a physical downlink control channel PDCCH of the second carrier and multiple data transmissions on a physical downlink shared channel PDSCH of the first carrier scheduled by the grant.

[0016] Another aspect of the present disclosure provides a method for wireless communication at a user equipment UE, including: receiving scheduling information in a scheduled time slot of a first carrier configured with a first parameter set, the scheduling information scheduling the transmission of multiple data transmissions on multiple scheduled time slots of a second carrier configured with a second parameter set larger than the first parameter set, each of the multiple data transmissions corresponding to a corresponding one of the multiple scheduled time slots; and transmitting the multiple data transmissions in the multiple scheduled time slots according to a predetermined minimum timing between a control resource of the first carrier and the multiple scheduled time slots of the second carrier, the predetermined minimum timing being greater in duration than a minimum delay between a grant on a physical downlink control channel PDCCH of the second carrier and multiple data transmissions on a physical downlink shared channel PDSCH of the first carrier scheduled by the grant.

[0017] By reading the following detailed description, these and other aspects of the present invention will become more comprehensive. After reading the following description of specific exemplary examples in conjunction with the accompanying drawings, it will be apparent to those of ordinary skill in the art that other aspects, features and examples are provided. Although features can be discussed relative to some of the following examples and the accompanying drawings, all examples can include one or more advantageous features discussed herein. In other words, although one or more examples can be discussed as having certain advantageous features, one or more such features can also be used according to the various examples discussed herein. In a similar manner, although exemplary examples can be discussed below as device, system or method examples, it should be understood that such exemplary examples can be implemented in various devices, systems and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 is a schematic diagram of a wireless communication system according to some aspects.

[0019] Figure 2 is a conceptual diagram of an example of a radio access network in accordance with some aspects.

[0020] Figure 3 is a schematic diagram of the organization of radio resources in an air interface utilizing orthogonal frequency division multiplexing (OFDM) according to some aspects.

[0021] Figure 4 is a diagram of an OFDM air interface utilizing scalable numerologies in accordance with some aspects.

[0022] Figure 5 is a diagram of an exemplary CCE structure in a DL control portion of a slot in accordance with some aspects.

[0023] Figure 6is a diagram of multiple example control resource sets (COREETs) for a DL control portion of a timeslot in accordance with some aspects.

[0024] Figure 7 is a diagram illustrating a multi-cell transmission environment according to some aspects.

[0025] Figure 8 is a diagram conceptually illustrating an example of cross-carrier scheduling in accordance with some aspects.

[0026] Fig. 9 is a diagram conceptually illustrating a first exemplary control resource in a time slot of a scheduling cell in accordance with some aspects.

[0027] Fig.10 is a diagram conceptually illustrating a second exemplary control resource in a time slot of a scheduling cell in accordance with some aspects.

[0028] Fig.11 is a diagram conceptually illustrating a third exemplary control resource in a time slot in a scheduling cell in accordance with some aspects.

[0029] Fig.12 is a diagram conceptually illustrating an exemplary minimum delay between a scheduling cell and a scheduled cell according to some aspects.

[0030] Fig.13 is a block diagram conceptually illustrating an example of a hardware implementation of a scheduling entity in accordance with some aspects.

[0031] Fig.14 is a flow chart illustrating an example process for cross-carrier scheduling according to some aspects.

[0032] Fig.15 is a flow chart illustrating an example process for cross-carrier scheduling according to some aspects.

[0033] Fig.16 is a block diagram conceptually illustrating an example of a hardware implementation of a scheduled entity in accordance with some aspects.

[0034] Fig.17 is a flow chart illustrating an example process for decoding control information used in cross-carrier scheduling according to some aspects.

[0035] Fig.18 is a flow chart illustrating an example process for decoding control information used in cross-carrier scheduling according to some aspects. DETAILED DESCRIPTION

[0036] The detailed description given below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it is apparent to those skilled in the art that these concepts can be practiced without these specific details. In some cases, in order to avoid confusing these concepts, well-known structures and components are shown in block diagram form.

[0037] Although various aspects and examples are described in this application by describing some examples, it will be understood by those skilled in the art that additional implementations and use cases may occur in many different arrangements and scenarios. The innovations described here can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, examples and / or uses can be implemented by integrated chip examples and other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / procurement equipment, medical equipment, AI-enabled devices, etc.). Although some examples may or may not be specifically targeted at use cases or applications, the wide applicability of the described innovations may occur. The scope of implementation can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or OEM devices or systems that incorporate one or more aspects of the innovation. In some practical settings, the device incorporating the described aspects and features may also have to include additional components and features for implementing and practicing the claimed and described examples. For example, the transmission and reception of wireless signals must include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). It is intended that the innovations described herein can be implemented in a variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc., of varying sizes, shapes, and configurations.

[0038] The various concepts presented in this disclosure may be implemented in a variety of telecommunication systems, network architectures and communication standards. Figure 1 , various aspects of the present disclosure are described with reference to a wireless communication system 100 as a non-limiting illustrative example. The wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. With the aid of the wireless communication system 100, the UE 106 can achieve data communication with an external data network 110 (such as (but not limited to) the Internet).

[0039] The RAN 104 may implement any suitable one or more wireless communication technologies to provide radio access to the UE 106. As an example, the RAN 104 may operate in accordance with the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification, commonly referred to as 5G. As another example, the RAN 104 may operate under a mix of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, commonly referred to as LTE. 3GPP refers to such a hybrid RAN as the Next Generation RAN, or NG-RAN. Of course, many other examples may be utilized within the scope of the present disclosure.

[0040] As shown, RAN 104 includes multiple base stations 108. In a broad sense, a base station is a network element in a radio access network, responsible for radio transmission and reception to or from a UE in one or more cells. In different technologies, standards or contexts, a base station may be referred to as a base transceiver station (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), a node B (NB), an eNode B (eNB), a gNode B (gNB), a transmission and reception point (TRP) or some other suitable terminology by those skilled in the art. In some examples, a base station may include two or more TRPs, which may be collocated or non-collocated. Each TRP may communicate on the same or different carrier frequencies in the same or different frequency bands.

[0041] The radio access network 104 is further shown as supporting wireless communications for multiple mobile devices. In the 3GPP standards, a mobile device may be referred to as a user equipment (UE), but may also be referred to as a mobile station (MS), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology by those skilled in the art. A UE may be a device (e.g., a mobile device) that provides a user with access to network services.

[0042] In this document, a "mobile" device does not necessarily have the ability to move, but can also be stationary. The term mobile device or mobile device refers to a wide range of devices and technologies. A UE may include multiple hardware structural components whose size, shape, and arrangement facilitate communication; these components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. that are electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile phones, cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smartbooks, tablets, personal digital assistants (PDAs), and various embedded systems, such as corresponding to the "Internet of Things" (IoT). A mobile device may also be a car or other means of transportation, a remote sensor or actuator, a robot or robotic device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-rotor aircraft, a quadcopter, a remote control device, a consumer and / or wearable device, such as glasses, a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., an MP3 player), a camera, a game console, etc. The mobile device may also be a digital home or smart home device, such as home audio, video and / or multimedia devices, appliances, vending machines, smart lighting, home security systems, smart meters, etc. The mobile device may also be a smart energy device, a security device, a solar panel or solar array, municipal infrastructure equipment that controls power (e.g., smart grid), lighting, water, etc., industrial automation and enterprise equipment, logistics controllers, agricultural equipment, etc. In addition, the mobile device may provide connected medical or telemedicine support, such as remote health care. Telehealth devices may include remote health monitoring devices and remote health management devices, whose communications may be given priority treatment or priority access over other types of information, for example, in terms of priority access to critical service data transmission and / or associated QoS for critical service data transmission.

[0043] Wireless communication between RAN 104 and UE 106 can be described as utilizing an air interface. Transmissions from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) over an air interface can be referred to as downlink (DL) transmissions. According to certain aspects of the present disclosure, the term downlink can refer to point-to-multipoint transmissions initiated at a scheduling entity (further described below; e.g., base station 108). Another way to describe the scheme can be to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) can be referred to as uplink (UL) transmissions. According to other aspects of the present disclosure, the term uplink can refer to point-to-point transmissions initiated at a scheduled entity (further described below; e.g., UE 106).

[0044] In some examples, access to the air interface may be scheduled, wherein a scheduling entity (e.g., a base station 108) allocates resources for communications between some or all devices and apparatuses within its service area or cell. In the present disclosure, as discussed further below, a scheduling entity may be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communications, a UE 106, which may be a scheduled entity, may utilize resources allocated by the scheduling entity 108.

[0045] Base station 108 is not the only entity that can act as a scheduling entity. That is, in some examples, a UE can act as a scheduling entity to schedule resources for one or more scheduled entities (eg, one or more other UEs).

[0046] like Figure 1 As shown, the scheduling entity 108 can broadcast downlink traffic 112 to one or more scheduled entities 106. In a broad sense, the scheduling entity 108 is a node or device responsible for scheduling traffic in the wireless communication network, including downlink traffic 112 and, in some examples, uplink traffic 116 from one or more scheduled entities 106 to the scheduling entity 108. On the other hand, the scheduled entity 106 is a node or device that receives downlink control information 114, which includes but is not limited to scheduling information (e.g., grants), synchronization or timing information, or other control information from another entity in the wireless communication network (e.g., the scheduling entity 108).

[0047] In general, the base stations 108 may include a backhaul interface for communicating with a backhaul portion 120 of the wireless communication system. The backhaul 120 may provide a link between the base stations 108 and the core network 102. Additionally, in some examples, the backhaul network may provide interconnections between the various base stations 108. Various types of backhaul interfaces may be used, such as a direct physical connection using any suitable transport network, a virtual network, etc.

[0048] The core network 102 may be part of the wireless communication system 100 and may be independent of the radio access technology used in the RAN 104. In some examples, the core network 102 may be configured according to a 5G standard (e.g., 5GC). In other examples, the core network 102 may be configured according to a 4G Evolved Packet Core (EPC) or any other suitable standard or configuration.

[0049] Reference now Figure 2 , a schematic diagram of RAN 200 is provided as an example and not a limitation. In some examples, RAN 200 may be similar to the ones described above and Figure 11. In some examples, RAN 200 may be a 5G NRRAN. The geographic area covered by RAN 200 may be divided into cellular areas (cells), which may be uniquely identified by a user equipment (UE) based on an identity broadcast from an access point or base station. Figure 2 Macro cells 202, 204, and 206 and small cells 208 are shown, each of which may include one or more sectors (not shown). A sector is a sub-area of ​​a cell. All sectors within a cell are served by the same base station. A radio link within a sector may be identified by a single logical identifier belonging to the sector. In a cell divided into sectors, multiple sectors within a cell may be formed by antenna groups, each antenna being responsible for communicating with a UE in a portion of the cell.

[0050] exist Figure 2 , two base stations 210 and 212 are shown in cells 202 and 204; and a third base station 214 is shown as controlling a remote radio head (RRH) 216 in cell 206. That is, the base station may have an integrated antenna, or may be connected to an antenna or RRH by a feeder cable. In the example shown, cells 202, 204, and 206 may be referred to as macro cells because base stations 210, 212, and 214 support cells with large sizes. In addition, a base station 218 is shown in a small cell 208 (e.g., a micro cell, a pico cell, a femto cell, a home base station, a home node B, a home eNode B, etc.) that may overlap with one or more macro cells. In this example, cell 208 may be referred to as a small cell because base station 218 supports a cell with a relatively small size. The cell size may be determined based on system design and component constraints.

[0051] It should be understood that the radio access network 200 may include any number of wireless base stations and cells. In addition, relay nodes may be deployed to extend the size or coverage area of ​​a given cell. Base stations 210, 212, 214, 218 provide wireless access points to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, and / or 218 may be similar to those described above and described in detail in the accompanying drawings. Figure 1 The base station / scheduling entity 108 shown in FIG.

[0052] Figure 2 Also included is a quadcopter or drone 220 that can be configured to function as a base station. That is, in some examples, the cell is not necessarily stationary, and the geographic area of ​​the cell can move depending on the location of a mobile base station such as a quadcopter 220.

[0053] Within the RAN 200, cells may include UEs that may communicate with one or more sectors of each cell. In addition, each base station 210, 212, 214, 218, and 220 may be configured to provide access to the core network 102 (see FIG. 1 ) for all UEs in the respective cells. Figure 1 ) access point. For example, UEs 222 and 224 may communicate with base station 210; UEs 226 and 228 may communicate with base station 212; UEs 230 and 232 may communicate with base station 214 via RRH 216; UE 234 may communicate with base station 218; and UE 236 may communicate with mobile base station 220. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 may communicate with the base stations described above and in Figure 1 The UE / scheduled entity 106 shown in FIG. 1 is the same as that shown in FIG.

[0054] In some examples, a mobile network node (e.g., quadcopter 220) can be configured to act as a UE. For example, quadcopter 220 can operate within cell 202 by communicating with base station 210.

[0055] In another aspect of the RAN 200, sidelink signals may be used between UEs without having to rely on scheduling or control information from a base station. For example, two or more UEs (e.g., UEs 238, 240, and 242) may communicate with each other using peer-to-peer (P2P) or sidelink signals 237 without relaying the communication through a base station. In some examples, UEs 238, 240, and 242 may each serve as a scheduling entity or transmitting sidelink device and / or a scheduled entity or receiving sidelink device to schedule resources and transmit sidelink signals 237 between them. In other examples, two or more UEs (e.g., UEs 226 and 228) within the coverage area of ​​a base station (e.g., base station 212) may also transmit sidelink signals 227 via a direct link (sidelink) without transmitting the communication through base station 212. In this example, base station 212 may allocate resources to UEs 226 and 228 for sidelink communication. In either case, such sidelink signaling 227 and 237 may be implemented in a P2P network, a device-to-device (D2D) network, a vehicle-to-vehicle (V2V) network, a vehicle-to-everything (V2X), a mesh network, or other suitable direct link network.

[0056] In the radio access network 200, the ability of a UE to communicate independently of its location while moving is called mobility. The various physical channels between the UE and the radio access network are usually managed by an access and mobility management function (AMF, not shown). Figure 1The function may include establishing, maintaining and releasing the security context of the control plane and user plane functions under the control of the core network 102, which may include a security context management function (SCMF) that manages the security context of the control plane and user plane functions, and a security anchor function (SEAF) that performs authentication.

[0057] In various aspects of the present disclosure, the radio access network 200 can utilize DL-based mobility or UL-based mobility to implement mobility and handover (i.e., transferring the UE's connection from one radio channel to another). In a network configured for DL-based mobility, during a call with a scheduling entity, or at any other time, the UE can monitor various parameters of the signal from its serving cell and various parameters of neighboring cells. Based on the quality of these parameters, the UE can maintain communication with one or more neighboring cells. During this period, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell for a given amount of time, the UE can perform a handover or handover from the serving cell to the neighboring (target) cell. For example, a UE 224 (illustrated as a vehicle, although any suitable form of UE can be used) can move from a geographic area corresponding to its serving cell 202 to a geographic area corresponding to a neighboring cell 206. When the signal strength or quality from a neighboring cell 206 exceeds the signal strength or quality of its serving cell 202 for a given amount of time, the UE 224 can send a report message to its serving base station 210 indicating this situation. In response, UE 224 may receive a handover command, and the UE may perform a handover to cell 206 .

[0058] In a network configured for UL-based mobility, the UL reference signal from each UE can be used by the network to select a serving cell for each UE. In some examples, base stations 210, 212, and 214 / 216 can broadcast a unified synchronization signal (e.g., a unified primary synchronization signal (PSS), a unified secondary synchronization signal (SSS), and a unified physical broadcast channel (PBCH)). UE 222, 224, 226, 228, 230, and 232 can receive the unified synchronization signal, derive carrier frequency and slot timing from the synchronization signal, and send an uplink pilot or reference signal in response to the derived timing. The uplink pilot signal sent by a UE (e.g., UE 224) can be received simultaneously by two or more cells (e.g., base stations 210 and 214 / 216) within the radio access network 200. Each cell can measure the strength of the pilot signal, and the radio access network (e.g., one or more of base stations 210 and 214 / 216 and / or a central node within the core network) can determine the serving cell of UE 224. As UE 224 moves through radio access network 200, the network may continue to monitor uplink pilot signals sent by UE 224. When the signal strength or quality of the pilot signals measured by the neighboring cell exceeds the signal strength or quality measured by the serving cell, network 200 may handover UE 224 from the serving cell to the neighboring cell, with or without notifying UE 224.

[0059] Although the synchronization signals transmitted by base stations 210, 212 and 214 / 216 may be uniform, the synchronization signals may not identify a specific cell, but may identify a region of multiple cells operating on the same frequency and / or the same timing. The use of regions in a 5G network or other next generation communication network implements an uplink-based mobility framework and improves the efficiency of the UE and the network because the number of mobility messages that need to be exchanged between the UE and the network can be reduced.

[0060] The air interface in the radio access network 200 may utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link in which two endpoints can communicate with each other bidirectionally. Full-duplex means that two endpoints can communicate with each other at the same time. Half-duplex means that only one endpoint can send information to the other endpoint at a time. Wireless links utilizing time division duplex (TDD) often implement half-duplex emulation. In TDD, transmissions in different directions on a given channel are separated from each other using time division multiplexing. That is, at certain times, the channel is dedicated to transmissions in one direction, and at other times, the channel is dedicated to transmissions in another direction, where the direction can change very quickly, such as several times per time slot. In wireless links, full-duplex channels generally rely on physical isolation of the transmitter and receiver, as well as appropriate interference cancellation techniques. Wireless links often use frequency division duplex (FDD) or space division duplex (SDD) to implement full-duplex emulation. In FDD, transmissions in different directions can operate on different carrier frequencies (e.g., within paired spectrum). In SDD, transmissions in different directions on a given channel are separated from each other using space division multiplexing (SDM). In other examples, full-duplex communication can be implemented within an unpaired spectrum (e.g., within a single carrier bandwidth), where transmissions in different directions occur within different sub-bands of the carrier bandwidth. This type of full-duplex communication may be referred to herein as sub-band full-duplex (SBFD), also known as flexible duplex.

[0061] The air interface in the radio access network 200 may utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification utilizes orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) to provide multiple access for UL transmissions from UEs 222 and 224 to the base station 210, and multiplexing for DL ​​transmissions from the base station 210 to one or more UEs 222 and 224. In addition, for UL transmissions, the 5G NR specification provides support for discrete Fourier transform-spread spectrum-OFDM (DFT-s-OFDM) through CP (also known as single carrier FDMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes, and may be provided using time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource extension multiple access (RSMA), or other suitable multiple access schemes. In addition, multiplexed DL transmissions from base station 210 to UEs 222 and 224 may be provided using time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes.

[0062] Will refer to Figure 3Various aspects of the present disclosure are described with reference to the OFDM waveforms schematically shown in FIG. It will be appreciated by those skilled in the art that various aspects of the present disclosure may be applied to DFT-s-OFDMA waveforms in substantially the same manner as described below. That is, although some examples of the present disclosure may focus on OFDM links for clarity, it will be appreciated that the same principles may also be applied to DFT-s-OFDMA waveforms.

[0063] In this disclosure, a frame refers to a duration of 10 ms for wireless transmission, each frame includes 10 subframes, each subframe is 1 ms. On a given carrier, there may be one set of frames in UL and another set of frames in DL. Now refer to Figure 3 , shows an expanded view of an exemplary DL subframe 302, showing an OFDM resource grid 304. However, as will be readily appreciated by those skilled in the art, the PHY transmission structure for any particular application may differ from the examples described herein, depending on many factors. Here, time is in the horizontal direction, in units of OFDM symbols; frequency is in the vertical direction, in units of subcarriers or tones.

[0064] Resource grid 304 can be used to schematically represent the time-frequency resources of a given antenna port. That is, in a multiple-input multiple-output (MIMO) implementation with multiple available antenna ports, corresponding multiple resource grids 304 can be used for communication. Resource grid 304 is divided into multiple resource elements (REs) 306. RE is 1 subcarrier × 1 symbol, which is the smallest discrete part of the time-frequency grid and contains a single complex value representing data from a physical channel or signal. Depending on the modulation used in a specific implementation, each RE can represent one or more information bits. In some examples, a block of REs can be referred to as a physical resource block (PRB) or more simply a resource block (RB) 308, which contains any suitable number of consecutive subcarriers in the frequency domain. In one example, an RB can include 12 subcarriers, which number is independent of the parameter set used. In some examples, depending on the parameter set, an RB can include any suitable number of consecutive OFDM symbols in the time domain. In the present disclosure, it is assumed that a single RB such as RB 308 corresponds entirely to a single communication direction (either sending or receiving for a given device).

[0065] UE scheduling for downlink, uplink, or sidelink transmissions typically involves scheduling one or more REs 306 within one or more subbands or bandwidth parts (BWPs). Thus, a UE typically utilizes only a subset of a resource grid 304. In some examples, an RB may be the smallest resource unit that may be allocated to a UE. Thus, the more RBs scheduled for a UE, the higher the modulation scheme selected for the air interface, and the higher the data rate for the UE. The RBs may be scheduled by a base station (e.g., gNB, eNB, etc.) or may be self-scheduled by a UE / sidelink device implementing D2D sidelink communications.

[0066] In this illustration, RB 308 is shown as occupying less than the entire bandwidth of subframe 302, with some subcarriers shown above and below RB 308. In a given implementation, subframe 302 may have a bandwidth corresponding to any number of one or more RBs 308. Additionally, in this illustration, RB 308 is shown as occupying less than the entire duration of subframe 302, although this is merely one possible example.

[0067] Each subframe 302 (eg, a 1 ms subframe) may include one or more adjacent time slots. Figure 3 In the example shown, as an illustrative example, a subframe 302 includes four time slots 310. In some examples, a time slot can be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot can include 7 or 14 OFDM symbols with a nominal CP. Other examples may include mini-slots with shorter durations (e.g., 1, 2, 4, or 7 OFDM symbols). In some cases, these mini-slots can be sent by occupying resources scheduled for ongoing time slot transmissions of the same or different UEs.

[0068] The expanded diagram of one time slot 310 illustrates the time slot 310 including a control region 312 and a data region 314. In general, the control region 312 may carry a control channel (e.g., PDCCH) and the data region 314 may carry a data channel (e.g., PDSCH or PUSCH). Of course, one time slot may contain all DL, all UL, or at least one DL portion and at least one UL portion. Figure 3 The simple structure shown is merely exemplary in nature, and different slot structures may be utilized and may include one or more of each of the control region and the data region.

[0069] Although Figure 3Although not shown in the figure, each RE 306 within the RB 308 can be scheduled to carry one or more physical channels, including a control channel, a shared channel, a data channel, etc. Other REs 306 within the RB 308 can also carry pilot or reference signals. These pilot or reference signals can provide a channel estimate of the corresponding channel for the receiving device, which can achieve coherent demodulation / detection of the control and / or data channels within the RB 308.

[0070] In a DL transmission, a transmitting device (e.g., a scheduling entity 108) may allocate one or more REs 306 (e.g., within a control region 312) to carry DL control information 114 including one or more DL control channels, which typically carry information originating from higher layers, such as a physical broadcast channel (PBCH), a physical downlink control channel (PDCCH), etc., to one or more scheduled entities 106. In addition, DL REs may be allocated to carry DL physical signals, which typically do not carry information originating from higher layers. These DL physical signals may include a primary synchronization signal (PSS); a secondary synchronization signal (SSS); a demodulation reference signal (DM-RS); a phase tracking reference signal (PT-RS); a channel state information reference signal (CSI-RS), etc.

[0071] The PDCCH may carry downlink control information (DCI) for one or more UEs in the cell. This may include, but is not limited to, power control commands, scheduling information, grants, and / or RE allocations for DL ​​and UL transmissions.

[0072] In UL transmission, a transmitting device (e.g., scheduled entity 106) may utilize one or more REs 306 to carry UL control information 118 (UCI). The UCI may be initiated from a higher layer and sent to the scheduling entity 108 via one or more UL control channels, such as a physical uplink control channel (PUCCH), a physical random access channel (PRACH), etc. In addition, the UL REs may carry UL physical signals that typically do not carry information originating from higher layers, such as a demodulation reference signal (DM-RS), a phase tracking reference signal (PT-RS), a sounding reference signal (SRS), etc. In some examples, the control information 118 may include a scheduling request (SR), i.e., a request to the scheduling entity 108 to schedule an uplink transmission. Here, in response to the SR sent on the control channel 118, the scheduling entity 108 may send downlink control information 114, which may schedule resources for uplink packet transmission.

[0073] The UL control information may also include hybrid automatic repeat request (HARQ) feedback, such as an acknowledgement (ACK) or negative acknowledgement (NACK), channel state information (CSI), or any other suitable UL control information. HARQ is a technique known to those of ordinary skill in the art, in which the integrity of packet transmissions may be checked on the receiving side to ensure accuracy, for example, using any suitable integrity check mechanism, such as a checksum or cyclic redundancy check (CRC). If the integrity of the transmission is confirmed, an ACK may be sent, and if it is not confirmed, a NACK may be sent. In response to the NACK, the transmitting device may send a HARQ retransmission, which may enable tracking merging, incremental redundancy, and the like.

[0074] In addition to control information, one or more REs 306 may be allocated for user data or traffic data (e.g., within data region 314). Such traffic may be carried on one or more traffic channels, such as a physical downlink shared channel (PDSCH) for DL ​​transmissions or a physical uplink shared channel (PUSCH) for UL transmissions. In some examples, in cross-carrier scheduling applications, a base station may use a PDCCH on one subcarrier to schedule a PDSCH or PUSCH on one or more other subcarriers.

[0075] Described above and Figure 1 and Figure 3 The channels or carriers shown in are not necessarily all channels or carriers that can be used between the scheduling entity 108 and the scheduled entity 106. A person skilled in the art will recognize that other channels or carriers may be used in addition to those shown, such as other business, control and feedback channels.

[0076] These physical channels are usually multiplexed and mapped to transport channels for processing at the medium access control (MAC) layer. Transport channels carry information blocks called transport blocks (TBs). Based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission, the transport block size (TBS), which may correspond to the number of information bits, may be a controlled parameter.

[0077] In OFDM, in order to maintain the orthogonality of the subcarriers or tones, the subcarrier spacing can be equal to the inverse of the symbol period. The parameter set of an OFDM waveform refers to its specific subcarrier spacing and cyclic prefix (CP) overhead. The scalable parameter set refers to the ability of the network to select different subcarrier spacings, and accordingly, for each spacing, the corresponding symbol duration, including the CP length, is selected. With a scalable parameter set, the nominal subcarrier spacing (SCS) can be scaled up or down by integer multiples. In this way, regardless of the CP overhead and the selected SCS, the symbol boundaries can be aligned at certain common multiples of the symbols (for example, at the boundaries of each 1ms subframe). The range of SCSs can include any suitable SCS. For example, a scalable parameter set can support an SCS ranging from 15kHz to 480kHz.

[0078] To illustrate the concept of scalable parameter sets, Figure 4 A first RB 402 having a nominal parameter set and a second RB 404 having a scaling parameter set are shown. As an example, the first RB 402 may have a "nominal" subcarrier spacing (SCS) of 30 kHz. n ) and a "nominal" symbol duration of 333 μs n Here, in the second RB 404, the scaling parameter set includes a scaled SCS of twice the nominal SCS, or 2×SCS n =60kHz. Because this provides twice the bandwidth for each symbol, it shortens the symbol duration carrying the same information. Therefore, in the second RB 404, the scaling parameter set includes a scaled symbol duration of half the nominal symbol duration, or (symbol duration n )÷2=167μs.

[0079] In 5G NR, a control resource set (CORESET) is a set of physical resources (e.g., a set of RBs or REs) configured to carry a PDCCH. Each PDCCH carries one DCI and can be identified by a radio network temporary identifier (RNTI). In some examples, a CORESET can be limited to a certain area in the frequency domain (e.g., a bandwidth part (BWP)). A CORESET can be configured with multiple parameters, including RE, resource element group (REG), REG packet, control channel element (CCE), and aggregation level. A REG can include one RB and one OFDM symbol in the time domain. A REG packet contains multiple REGs, and a CCE contains multiple REGs. The number of REG packets in a CCE may vary. The aggregation level indicates how many CCEs are allocated for the PDCCH. The search space indicates a set of CCE locations in which a UE can find a PDCCH (e.g., a PDCCH candidate) for the UE. There are two types of search spaces: a common search space (CSS) and a UE-specific search space (USS). The UE monitors both the CSS and USS of the PDCCH.

[0080] Figure 5 is a diagram of an example CCE 500 structure in a DL control portion 506 of a time slot according to some aspects. The time slot may correspond to, for example, Figure 3 The time slots shown. Figure 5 The CCE 500 structure of 500 represents a portion of a DL control portion 506, including a plurality of REs 502 that may be grouped into REGs 504. Each REG 504 may typically include, for example, twelve consecutive REs 502 (or nine REs 502 and three DMRS REs) within the same OFDM symbol and the same RB. In this example, the CCE structure 500 includes at least six REGs 504 distributed over three OFDM symbols. However, as will be readily appreciated by those skilled in the art, the CCE 500 structure for any particular application may vary based on the examples described herein according to any number of factors. For example, the CCE 500 structure may include any suitable number of REGs.

[0081] In some examples, a PDCCH may be constructed from a variable number of CCEs, depending on the PDCCH format (or aggregation level). Each PDCCH format (or aggregation level) supports a different DCI length. In some examples, PDCCH aggregation levels of 1, 2, 4, 8, and 16 may be supported, corresponding to 1, 2, 4, 8, or 16 consecutive CCEs, respectively.

[0082] Since the UE does not know the specific aggregation level of the PDCCH, nor does it know whether there may be multiple PDCCHs for the UE in the time slot, the UE can blindly decode various PDCCH candidates within the first N control OFDM symbols (as indicated by the time slot format of the time slot) based on the expected RNTI (e.g., UE-specific RNTI or group RNTI). Based on the assumed DCI length (e.g., PDCCH aggregation level), each PDCCH candidate includes a set of one or more consecutive CCEs. In order to limit the number of blind decodings, a search space defining a UE-specific search space (USS) and a common search space (CSS) can be defined. The search space set (e.g., USS and CSS) configured for the UE limits the number of blind decodings performed by the UE for each PDCCH format combination. The common search space set includes CCEs used to send control information common to a group of UEs or all UEs. Therefore, the common search space set is monitored by multiple UEs in the cell. The starting point (offset or index) of the search space set for group common control information may be the same for all UEs in the group, and there may be multiple search space sets defined for group common control information (e.g., one search space set for each configured aggregation level for the UE group).

[0083] Figure 6 is a diagram of multiple example CORESETs 600 of a DL control portion 602 of a time slot according to some aspects. For example, the DL control portion 602 may correspond to Figure 3 DL control part shown. CORESET 600 can be configured for group common control information or UE specific control information and can be used to transmit a PDCCH including group common control information or UE specific control information to a group of one or more UEs. A UE can monitor one or more CORESETs 600, which the UE is configured to monitor for UE specific or group common control information.

[0084] Each CORESET 600 represents a portion of the DL control portion 602, including multiple subcarriers in the frequency domain and one or more symbols in the time domain. Figure 6 In the example of , each CORESET 600 includes at least one CCE 604 having frequency and time dimensions and a size spanning at least three OFDM symbols. A CORESET having a size spanning two or more OFDM symbols may be beneficial for use on a relatively small system bandwidth (e.g., 5 MHz). However, a single symbol CORESET is also possible.

[0085] A plurality of CORESETs 600 indexed as CORESET#1-CORESET#N are shown to occur during three OFDM symbols in the time domain and occupy a first frequency resource region in the frequency domain of a DL control portion 602. Figure 6 In the example shown, each CORESET 600 includes four CCEs 604. It should be noted that this is just an example. In another example, each CORESET 600 may include any suitable number of CCEs 604. The number of CCEs 604 of each CORESET 600 and the configuration of CCEs 604 may depend on, for example, the aggregation level applied to the PDCCH.

[0086] The search space for a UE is indicated by a set of consecutive CCEs that the UE should monitor for downlink assignments and uplink grants associated with a specific component carrier for that UE. Figure 6 In the example shown, multiple CORESETs 600 may form a search space 606, which may be a USS or a CSS. Within a USS, the aggregation level of the PDCCH may be, for example, 1, 2, 4, or 8 consecutive CCEs, and within a CSS, the aggregation level of the PDCCH may be, for example, 4 or 8 consecutive CCEs. In addition, the number of PDCCH candidates within each search space may vary depending on the aggregation level used. For example, for a USS with aggregation level 1 or 2, the number of PDCCH candidates may be 6. In this example, the number of CCEs in the USS search space 606 with aggregation level 1 may be 6, and the number of CCEs in the USS search space 606 with aggregation level 2 may be 12. However, for a USS with aggregation level 4 or 8, the number of PDCCH candidates may be 2. In this example, the number of CCEs in the USS search space 606 with aggregation level 4 may be 8, and the number of CCEs in the USS search space 606 with aggregation level 8 may be 16. For the CSS search space 606, the number of CCEs in the search space 606 may be 16 regardless of the aggregation level.

[0087] 5G-NR networks can further support carrier aggregation of component carriers transmitted from different transmission and reception points (TRPs) in a multi-cell transmission environment. Figure 7An example of a multi-cell transmission environment 700 is shown in FIG. The multi-cell transmission environment 700 includes a primary serving cell (PCell) 702 and one or more secondary serving cells (SCells) 706a, 706b, 706c, and 706d. The PCell 702 may be referred to as an anchor cell, which provides a radio resource control (RRC) connection to a UE 710. In some examples, the PCell and one or more SCells may be collocated (e.g., different transmit receive points (TRPs) may be in the same location).

[0088] When carrier aggregation is configured, one or more of the SCells 706a-706d may be activated or added to the PCell 702 to form a serving cell serving the UE 710. Each serving cell corresponds to a component carrier (CC). The CC of the PCell 702 may be referred to as a primary CC, and the CC of the SCells 706a-706d may be referred to as a secondary CC. The PCell 702 and one or more SCells 706 may be served by respective TRPs 704 and 708a-708c. Each TRP 704 and 708a-708c may be a base station (e.g., a gNB), a remote radio head of a gNB, or a similar TRP. Figure 1 or Figure 2 In some examples, a base station may include multiple TRPs, each TRP corresponding to one of multiple collocated or non-collocated antenna arrays, each TRP supporting a different component carrier. Figure 7 In the example shown, SCells 706a-706c are served by respective non-collocated TRPs 708a-708c. In addition, SCell 706d and PCell 702 are collocated and served by respective collocated TRPs 704 (only one of which is shown for convenience). Here, each TRP serving cells 702 and 706d may be associated with a single base station 704. The coverage of PCell 702 and SCell 706d may be different because component carriers in different frequency bands may experience different path losses.

[0089] PCell 702 may add or remove one or more SCells 706a-706d to improve the reliability of the connection to UE 710 and / or to increase the data rate. However, PCell 702 may only change when switching to another PCell. In some examples, PCell 702 may utilize a first radio access technology (RAT), such as LTE, and one or more SCells 706 may utilize a second RAT, such as 5G-NR. In this example, the multi-cell transmission environment may be referred to as a multi-RAT dual connection (MR-DC) environment. In some examples, PCell 702 may be a low-band cell and SCell 706 may be a high-band cell. Low-band (LB) cells use CCs in frequency bands lower than high-band cells. For example, high-band cells may each use a corresponding millimeter wave CC (e.g., FR2 or higher), and low-band cells may use CCs in lower frequency bands (e.g., frequency bands below 6 GHz or FR1). In general, cells using FR2 or higher CCs may provide greater bandwidth than cells using FR1 CCs. In addition, when using carriers with frequencies above -6 GHz (e.g., millimeter waves), beamforming can be used to send and receive signals.

[0090] The PCell 702 is not only responsible for connection establishment, but also for radio resource management (RRM) and radio link monitoring (RLM) of the connection with the UE 710. For example, the PCell 702 can activate one or more SCells (e.g., SCell 706a) to perform multi-cell communication with the UE 710. In some examples, when the SCell 706a is not used for data transmission / reception, the PCell can activate the SCell 706a as needed instead of keeping the SCell activated to reduce the power consumption of the UE 710.

[0091] In some examples, a scheduling entity (e.g., base station 704) can use a carrier (e.g., component carrier) of one cell (e.g., PCell 702) to schedule transmission of downlink and / or uplink data traffic on another carrier (e.g., another component carrier) of another cell (e.g., SCell 706d). Each carrier can utilize the same or different subcarrier spacing.

[0092] Figure 8is a diagram conceptually illustrating an example of cross-carrier scheduling according to some aspects. A scheduling entity (e.g., a base station) may use a first carrier 802 of a first cell (scheduling cell) having a lower subcarrier spacing (SCS) to schedule a UE to use a second carrier 804 of a second cell (scheduled cell) having a higher SCS to send or receive user data traffic (e.g., PDSCH or PUSCH). The first carrier 802 may be time-divided into a plurality of first time slots 806, and the second carrier may be time-divided into a plurality of second time slots 808. In some examples, the first carrier may have an SCS of 15 kHz, and the second carrier may have an SCS higher than 15 kHz (e.g., 120 kHz or higher). Thus, the second carrier 804 may include a plurality of second time slots 808 that may be transmitted within the duration of a single first time slot 806 of the first carrier 802.

[0093] In the PDCCH region 810 of the first time slot (e.g., time slot 0) 806 of the first carrier 802, the scheduling entity may send multiple unicast DCIs (scheduling information) for several second time slots 808 of the scheduled cell (e.g., time slots 2 to 7 of the first subframe and time slots 0 and 1 of the second subframe). The UE needs to decode these DCIs in time to send PUSCH or receive PDSCH data on the second carrier 804 while meeting the applicable PDCCH to PDSCH or PDCCH to PUSCH delay requirements.

[0094] Various aspects of the present disclosure improve the decoding timeline of scheduling information (e.g., DCI) for cross-carrier scheduling involving a lower SCS cell scheduling a higher SCS cell. In one aspect of the present disclosure, a scheduling entity may associate a PDCCH candidate with a slot index and / or symbol index of a PDSCH / PUSCH on a scheduled carrier. In this way, before the UE processes the PDCCH, the UE can determine whether the PDCCH candidate is associated with an earlier PDSCH / PUSCH slot or a later PDSCH / PUSCH slot.

[0095] Fig. 9 is a diagram conceptually illustrating control resources in a time slot 900 of a scheduling cell. For example, time slot 900 may be Figure 8 Timeslot 0 806 of carrier 802 is shown. Fig. 9An exemplary CORESET 902 is shown in FIG. 900 . In other examples, multiple CORESETs may be defined for timeslot 900 . CORESET 902 includes multiple PDCCH candidates where the UE may find DCI for a scheduled cell. Each PDCCH candidate may be associated with a timeslot index and / or a starting symbol index of a corresponding PDSCH / PUSCH on a scheduled carrier. Thus, before the UE processes a PDCCH, the UE may determine, based on the association, whether the PDCCH candidate is associated with an earlier PDSCH / PUSCH timeslot or a later PDSCH / PUSCH timeslot. Fig. 9 In the example shown, the first PDCCH candidate 904 is associated with time slot 0 of the scheduled carrier, the second PDCCH candidate 906 is associated with time slot 4 of the scheduled carrier, the third PDCCH candidate 908 is associated with time slot 2 of the scheduled carrier, the fourth PDCCH candidate 910 is associated with time slot 3 of the scheduled carrier, the fifth PDCCH candidate 912 is associated with time slot 1 of the scheduled carrier, and the sixth PDCCH candidate 914 is associated with time slot 5 of the scheduled carrier. In some examples, the time slot index can be a related PDSCH time slot relative to the PDCCH time slot. In some examples, the time slot index can be a related PDSCH time slot relative to the frame or subframe that includes the PDCCH time slot. In other examples, other associations between the PDCCH candidates and the time slot index / starting symbol index of the PDSCH / PUSCH can be used.

[0096] Fig.10 is a diagram conceptually illustrating control resources in a time slot 1000 of a scheduled cell according to some aspects. For example, time slot 1000 may be Figure 8 Timeslot 0 806 of the first carrier 802 is shown. Fig.10Two exemplary CCE allocations (CCE allocation 1002 and CCE allocation 1004) are shown in FIG. 1 . In other examples, time slot 1000 may have other CCE configurations. CCE allocations 1002 and 1004 may belong to the same CORESET or different CORESETs. The scheduling entity may use each CCE allocation to carry multiple PDCCH candidates, where the UE may find the DCI of the scheduled cell. In one aspect of the present disclosure, in addition to the existing dependency on PDCCH candidates and cell indexes, the CCE allocations of PDCCH candidates may also depend on the time slot index of the scheduled PDSCH / PUSCH. In other words, the association is between the CCE allocations of the PDCCH candidates and the time slot (and / or symbol) index. In one example, the first CCE allocation 1002 is associated with time slot 0 and the second CCE allocation 1004 is associated with time slot 1. The first CCE allocation 1002 may include a first PDCCH candidate 1006, a second PDCCH candidate 1008, and a third PDCCH candidate 1010, where the UE can find the DCI for the PDSCH / PUSCH in slot 0. The second CCE allocation 1004 may include a fourth PDCCH candidate 1012, a fifth PDCCH candidate 1014, and a sixth PDCCH candidate 1016, where the UE can find the DCI for the PDSCH / PUSCH in slot 1. In some examples, the slot index may be a related PDSCH / PUSCH slot relative to a PDCCH slot. In some examples, the slot index may be a related PDSCH / PUSCH slot relative to a frame or subframe that includes the PDCCH slot.

[0097] In some aspects of the present disclosure, a scheduling entity (e.g., a base station) may use radio resource control (RRC) or semi-static signaling to configure an association between control resources (e.g., CCE allocations or PDCCH candidates) in a scheduling cell and a time slot / symbol index for PDSCH / PUSCH transmissions in a scheduled cell. In some aspects of the present disclosure, a scheduling entity may use a MAC control element (CE) to signal the association. In some aspects of the present disclosure, a scheduling entity may use a DCI to dynamically signal the association. In some aspects of the present disclosure, the association may be specified in a standard that defines a network. For example, a standard may provide an equation for determining CCE allocations for PDCCH candidates based on time slots and / or symbol indices of scheduled PDSCH / PUSCH.

[0098] Fig.11 is a diagram conceptually illustrating control resources in a time slot 1100 of a scheduled cell according to some aspects. For example, time slot 1100 may be Figure 8Timeslot 0 806 of the first carrier 802 is shown. The scheduling entity may configure multiple search spaces (SS) and / or CORESETs in one timeslot. Fig.11 100 and 101. Two exemplary SSs or CORESETs for scheduling cells are shown in FIG. Each SS / CORESET provides scheduling information for the corresponding PDSCH / PUSCH of the scheduled cell. In one example, a first SS / CORESET 1102 is associated with a first group of time slots and a second SS / CORESET 1104 is associated with a second group of time slots later than the first group of time slots. For example, the first SS / CORESET 1102 is associated with time slots 0, 1, and 2 and the second SS / CORESET 1104 is associated with time slots 3, 4, and 5. The UE can determine the relative timing of the scheduled time slots by the SS / CORESET assigned to the time slots.

[0099] In one example, the scheduling entity may configure eight PDCCH candidates in a search space set. For example, at the search space set timing (e.g., within the control / PDCCH region of a single time slot), PDCCH candidate 0 carries the DCI for time slot 0, PDCCH candidate 1 carries the DCI for time slot 1, PDCCH candidate 2 carries the DCI for time slot 2, PDCCH candidate 3 carries the DCI for time slot 3, PDCCH candidate 4 carries the DCI for time slot 4, PDCCH candidate 5 carries the DCI for time slot 5, PDCCH candidate 6 carries the DCI for time slot 6, and PDCCH candidate 7 carries the DCI for time slot 7.

[0100] In one example, the scheduling entity may configure four PDCCH candidates in one search space set. At the first search space set time, PDCCH candidate 0 carries the DCI of time slot 0, PDCCH candidate 1 carries the DCI of time slot 1, PDCCH candidate 2 carries the DCI of time slot 2, and PDCCH candidate 3 carries the DCI of time slot 3. At the second search space set time, PDCCH candidate 4 carries the DCI of time slot 4, PDCCH candidate 5 carries the DCI of time slot 5, PDCCH candidate 6 carries the DCI of time slot 6, and PDCCH candidate 7 carries the DCI of time slot 7.

[0101] In one example, the scheduling entity may configure eight PDCCH candidates in a search space set. At the search space set timing, PDCCH candidates 0 and 1 carry DCI for time slot 0, PDCCH candidates 2 and 3 carry DCI for time slot 1, PDCCH candidates 4 and 5 carry DCI for time slot 2, and PDCCH candidates 6 and 7 carry DCI for time slot 3.

[0102] In one example, the scheduling entity may configure eight PDCCH candidates in a search space set. At the search space set timing, the first group of PDCCH candidates (e.g., 0 to 3) carries the DCI for time slot 0, the second group of PDCCH candidates (e.g., 2 to 5) carries the DCI for time slot 1, the third group of PDCCH candidates (e.g., 4 to 7) carries the DCI for time slot 2, and the fourth group of PDCCH candidates (e.g., 0, 1, 6, and 7) carries the DCI for time slot 3.

[0103] When a scheduling entity (e.g., a base station) sends scheduling information (e.g., PDCCH / DCI) to schedule PDSCH / PUSCH across carriers, the scheduled entity (e.g., UE) needs sufficient time to process the DCI. The 5G NR standard may specify a minimum PDCCH to PDSCH delay and a minimum PDCCH to PUSCH delay for cross-carrier scheduling. The minimum PDCCH to PDSCH delay (Δ PDCCH -to-PDSCH) refers to the minimum time gap between the end of PDCCH and the start of PDSCH. Minimum PDCCH to PUSCH delay (Δ PDCCH-to-PUSCH ) refers to the minimum time gap between the end of PDCCH and the start of PUSCH. The scheduling entity needs to ensure that the scheduled PDSCH / PUSCH does not violate the minimum Δ PDCCH-to-PDSCH and Δ PDCCH-to-PUSCH That is, the scheduling entity should not schedule the smallest Δ PDCCH-to-PDSCH / Δ PDCCH-to-PUSCH PDSCH / PUSCH started earlier.

[0104] In some aspects of the present disclosure, when the UE is as described above with respect to Figure 8-11 When decoding the cross-carrier PDCCH, the UE may consider the minimum Δ PDCCH-to-PDSCH / Δ PDCCH-to-PUSCH For example, the UE may determine that the minimum Δ PDCCH-to-PDSCH / Δ PDCCH-to-PUSCH The UE can then select the earliest time slot with the smallest Δ PDCCH-to-PDSCH / Δ PDCCH-to-PUSCH The earliest allowed PDSCH / PUSCH slot associated with the PDCCH candidate starts PDCCH decoding, which can be specified in symbols. If the scheduled PDSCH / PUSCH does not meet the minimum Δ PDCCH-to-PDSCH / Δ PDCCH-to-PUSCH , the UE can ignore the corresponding DCI.

[0105] In some aspects of the present disclosure, the scheduling entity may configure the UE to schedule PDSCH / PUSCH on a carrier using a minimum DL grant to DL data (PDSCH) timing (K0) and a minimum UL grant to UL data (PUSCH) timing (K2). For example, K0 / K2 may be specified in units of time slots. In some examples, the configured minimum value K0 / K2 may be greater than the minimum value Δ in duration. PDCCH-to-PDSCH / Δ PDCCH-to-PUSCH When the minimum value K0 / K2 is configured, the UE starts decoding the PDCCH from the PDCCH candidate associated with the earliest scheduled time slot based on the configured minimum value K0 / K2. In some examples, the scheduling entity may send an RRC message to configure the minimum K0 / K2.

[0106] Fig.12 is a diagram conceptually illustrating an exemplary minimum delay between a scheduling cell and a scheduled cell according to some aspects. Figure 8 In the example shown in , a scheduling entity (e.g., a base station) may use a first carrier 1202 of a first cell (scheduling cell) having a lower subcarrier spacing (SCS) to schedule a UE to use a second carrier 1204 of a second cell (scheduled cell) having a higher SCS to send or receive user data services (e.g., PDSCH or PUSCH). The first carrier 1202 may be time-divided into a plurality of first time slots 1206, and the second carrier may be time-divided into a plurality of second time slots 1208. In addition, the first carrier may have an SCS of 15 kHz, and the second carrier may have an SCS higher than 15 kHz (e.g., 120 kHz or higher). Therefore, the second carrier 1204 may include a plurality of second time slots 1208 that may be transmitted within the duration of a single first time slot 1206 of the first carrier 1202.

[0107] exist Fig.12 In the example shown, the minimum value K0 / K2 1214 is configured in time slot 4 of the second time slot 1208, which is later than the minimum value Δ PDCCH-to-PDSCH / Δ PDCCH-to-PUSCH 1212. In this case, the scheduling entity should not schedule PDSCH / PUSCH in a time slot earlier than K0 / K2 1214. In addition, the UE may ignore DCI that schedules PDSCH / PUSCH in a time slot earlier than K0 / K2 1214. As a result, in the PDCCH region 1210 of the first time slot (e.g., time slot 0) 1206 of the first carrier 1202, the scheduling entity may send multiple unicast DCIs (scheduling information) for several second time slots 1208 (e.g., time slots 4 to 7 of the first subframe and time slots 0 and 1 of the second subframe) of the scheduled cells not earlier than K0 / K2 1214.

[0108] In some aspects of the present disclosure, in a scheduled cell, a time domain resource allocation (TDRA) table for PDSCH and PUSCH may be configured for the UE, respectively. Each row in the TDRA table may contain a K0 / K2 value. When the scheduling entity schedules PDSCH / PUSCH, the scheduling entity sends control information (e.g., DCI / PDCCH) to indicate the row index of the TDRA table. In some examples, the scheduling entity may send an RRC message to indicate the row index. Based on the index, the scheduled entity (e.g., UE) may determine the K0 / K2 value from the table. In one example, when a minimum value K0 / K2 is configured, the UE may treat any TDRA entry whose K0 / K2 value is less than the configured minimum value K0 / K2 as invalid. In this case, the UE may ignore the scheduling information of the invalid time slot. In another example, the UE may treat the K0 / K2 value in the TDRA table as a delta value, which is added to the configured minimum value K0 / K2 to determine the actual or effective K0 / K2. In one example, if the minimum configured K0 is 4 slots, and in the exemplary TDRA row of the TDRA table, the K0 value is 2 slots, the UE determines that the PDSCH / PUSCH is scheduled in slot 6, as shown in FIG. Fig.12 shown.

[0109] Fig.13 13 is a block diagram illustrating an example of a hardware implementation of a scheduling entity 1300 employing a processing system 1314. For example, the scheduling entity 1300 may be such as Figure 1 and / or Figure 2 Any one or more of the base stations shown.

[0110] The scheduling entity 1300 may be implemented with a processing system 1314 including one or more processors 1304. Examples of processors 1304 include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described in the present disclosure. In various examples, the scheduling entity 1300 may be configured to perform any one or more of the functions described herein. That is, the processor 1304 used in the scheduling entity 1300 may be used to implement the following and Figure 8-12 , 14 and 15.

[0111] In this example, the processing system 1314 may be implemented via a bus architecture, generally represented by bus 1302. Depending on the specific application and overall design constraints of the processing system 1314, the bus 1302 may include any number of interconnecting buses and bridges. The bus 1302 communicatively couples various circuits together, including one or more processors (generally represented by processor 1304), memory 1305, and computer-readable media (generally represented by computer-readable media 1306). The bus 1302 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described. The bus interface 1308 provides an interface between the bus 1302 and the transceiver 1310. The transceiver 1310 provides a communication interface or device for communicating with various other devices via a transmission medium. Depending on the nature of the device, a user interface 1312 (e.g., keyboard, display, speaker, microphone, joystick) may also be provided. Of course, such a user interface 1312 is optional and may be omitted in some examples, such as a base station.

[0112] In some aspects of the present disclosure, the processor 1304 may include circuits configured for various functions, including, for example, cross-carrier scheduling in wireless communications. For example, the circuits may be configured to implement Figure 8-12 , 14 and 15 described one or more functions. For example, the processor 1304 may include a scheduling circuit 1340 and a DL / UL communication circuit 1342. The scheduling circuit 1340 may be configured to perform various functions of cross-carrier scheduling. For example, the scheduling circuit 1340 may be configured to determine scheduling information to configure the scheduled entity (e.g., UE) to send or receive data. The scheduling information may be a PDCCH / DCI to be sent on the first carrier for scheduling one or more PDSCH / PUSCH transmissions on the second carrier. The first carrier and the second carrier may have different parameter sets.

[0113] The DL / UL communication circuit 1342 may be configured to perform various functions to send and receive data via the transceiver 1310 using the first carrier and / or the second carrier. In one example, the DL / UL communication circuit 1342 may be configured to send scheduling information to the UE using the first carrier of the first parameter set so that the UE is configured to send or receive data using the second carrier of the second parameter set. The DL / UL communication circuit 1342 may be configured to send scheduling information using control resources allocated, for example, by the scheduling circuit 1340 based on slot indices of multiple PDSCH / PUSCH slots on the second carrier, the multiple PDSCH / PUSCH slots being configured to send or receive data on the second carrier. The control resources may include, for example, search spaces, CORESETs, CCEs, and PDCCH candidates.

[0114] The processor 1304 is responsible for managing the bus 1302 and general processing, including executing software stored on the computer-readable medium 1306. When executed by the processor 1304, the software causes the processing system 1314 to perform the various functions described below for any particular device. The computer-readable medium 1306 and the memory 1305 can also be used to store data that is manipulated by the processor 1304 when executing the software.

[0115] One or more processors 1304 in the processing system can execute software. Software should be broadly interpreted as instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable programs, execution threads, processes, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language or other. The software can reside on a computer-readable medium 1306. The computer-readable medium 1306 can be a non-transitory computer-readable medium. As an example, a non-transitory computer-readable medium includes a magnetic storage device (e.g., a hard disk, a floppy disk, a magnetic strip), an optical disk (e.g., a compact disk (CD) or a digital versatile disk (DVD)), a smart card, a flash memory device (e.g., a card, a stick or a key drive), a random access memory (RAM), a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), a register, a removable disk, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. Computer readable medium 1306 may reside in processing system 1314, external to processing system 1314, or distributed among multiple entities including processing system 1314. Computer readable medium 1306 may be embodied in a computer program product. For example, a computer program product may include a computer readable medium in packaging materials. Those skilled in the art will recognize that how best to implement the described functionality presented throughout this disclosure depends on the specific application and the overall design constraints imposed on the entire system.

[0116] In one or more examples, the computer-readable storage medium 1306 may include software configured for various functions, including, for example, cross-carrier scheduling. For example, the software may be configured to implement the above Figure 8-12 , 14 and 15. For example, the software may include scheduling instructions 1350 and DL / UL communication instructions 1352.

[0117] The scheduling instructions 1350 may configure the scheduling entity 1300 to perform various functions for cross-carrier scheduling. For example, the scheduling instructions 1350 may configure the scheduling entity 1300 to determine scheduling information to configure the scheduled entity (e.g., UE) to send or receive data in the PDSCH / PUSCH time slot. The scheduling information may be a PDCCH / DCI to be sent on a first carrier for scheduling one or more PDSCH / PUSCH transmissions on a second carrier. The first carrier and the second carrier may have different parameter sets. The scheduling instructions 1350 may also be executed by the scheduling circuit 1340.

[0118] The DL / UL communication instructions 1352 may configure the scheduling entity to perform various functions to send and receive data via the transceiver 1310 using the first carrier and / or the second carrier. In one example, the DL / UL communication instructions 1352 may configure the scheduling entity 1300 to send scheduling information to the UE using the first carrier of the first parameter set, so that the UE is configured to send or receive data using the second carrier of the second parameter set. The DL / UL communication instructions 1352 may configure the scheduling entity to send scheduling information using control resources allocated, for example, by the scheduling circuit 1340 based on a slot index of a plurality of slots on the second carrier, the plurality of slots being configured to send or receive data on the second carrier. The control resources may include, for example, search spaces, CORESETs, CCEs, and PDCCH candidates. The DL / UL communication instructions 1352 may also be executed by the DL / UL communication circuit 1342.

[0119] Fig.14 1400 is a flow chart illustrating an exemplary process 1400 for cross-carrier scheduling according to some aspects. As described below, in certain implementations within the scope of the present disclosure, some or all of the illustrated features may be omitted, and some of the illustrated features may not be necessary for all example implementations. In some examples, the process 1400 may be performed by Fig.13 In some examples, process 1400 may be performed by any suitable device or means for performing the functions or algorithms described below.

[0120] At block 1402, a scheduling entity may generate scheduling information that schedules transmission of a plurality of data transmissions with a user equipment (UE) over a plurality of time slots of a first carrier having a first parameter set, each of the plurality of data transmissions corresponding to a respective one of the plurality of time slots. Fig.13 The illustrated and described scheduling circuitry 1340 may provide a means for generating scheduling information (eg, PDCCH / DCI) that schedules communication of multiple PDSCHs and / or PUSCHs for a UE.

[0121] At block 1404, the scheduling entity may send scheduling information to the UE within a control resource allocated based on a time slot index of a plurality of time slots on a second carrier, the second carrier having a second parameter set that is smaller than the first parameter set. In an example, the first carrier and the second carrier may be the first carrier 802 and the second carrier 804, respectively, which are described above with respect to Figure 8 Described.

[0122] In some examples, the control resource includes a plurality of physical downlink control channel (PDCCH) candidates associated with time slot indexes of a plurality of time slots, respectively. In some examples, the plurality of PDCCH candidates include a first PDCCH candidate associated with a first time slot in the plurality of time slots, and a second PDCCH candidate associated with a second time slot in the plurality of time slots, and the first time slot is earlier in time than the second time slot. In some examples, each time slot index is configured to indicate a corresponding time slot in a plurality of time slots including a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) relative to an initial time slot on a second carrier including the plurality of PDCCH candidates. In other examples, each time slot index is configured to indicate a corresponding time slot in a plurality of time slots including a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) relative to a frame or subframe on a second carrier including the plurality of PDCCH candidates.

[0123] In some examples, the control resources include multiple physical downlink control channel (PDCCH) candidates, and the control channel element (CCE) allocation of the PDCCH candidates depends on the time slot index of the multiple time slots. In some examples, the scheduling entity can use a first set of control resources associated with a first time slot in the multiple time slots to send a first part of the scheduling information, and use a second set of control resources associated with a second time slot in the multiple time slots to send a second part of the scheduling information. In some examples, each of the first set of control resources and the second set of control resources includes a search space or a control resource set.

[0124] In some examples, the scheduling entity may also send control information using at least one of radio resource control signaling, media access control (MAC) control element (MAC-CE), or downlink control information to indicate an association between the control resource and the plurality of time slots. Fig.13 The DL / UL communication circuitry 1342 and transceiver 1310 shown and described may provide a means for transmitting scheduling information to the UE.

[0125] In one example, the scheduling information may be one or more DCIs, each DCI including a downlink (DL) grant for the PDSCH and / or an uplink (UL) grant for the PUSCH. In one example, the control resource may be a time-frequency resource allocated to a PDCCH candidate based on a time slot index and / or a symbol index of the scheduled PDSCH / PUSCH. In one example, the control resource may be a CCE allocation for a PDCCH candidate configured based on a time slot index of the scheduled PDSCH / PUSCH. In one example, the control resource may be a search space or a CORESET, and the search space / CORESET may be associated with different time slots, respectively. For example, a first search space / CORESET may be associated with one or more first time slots, and a second search space / CORESET may be associated with one or more second time slots.

[0126] Fig.15 1 is a flow chart illustrating an exemplary process 1500 for cross-carrier scheduling according to some aspects. As described below, in certain implementations within the scope of the present disclosure, some or all of the illustrated features may be omitted, and some of the illustrated features may not be necessary for all example implementations. In some examples, process 1500 may be performed by Fig.13 The process 1500 is performed by the scheduling entity 1300 shown. In some examples, the process 1500 can be performed by any suitable device or means for performing the functions or algorithms described below.

[0127] At block 1502, a scheduling entity may configure a user equipment (UE) to transmit a plurality of data transmissions based on a predetermined minimum delay between a control resource of a second carrier scheduling the plurality of data transmissions and a plurality of time slots of a first carrier, the first carrier having a different set of parameters than the second carrier on which the plurality of data transmissions are to be transmitted. In some examples, the second carrier may have a smaller set of parameters than the first carrier. In some examples, the scheduling entity may configure the UE by sending the predetermined minimum delay to the UE in a radio resource control message. In some examples, the scheduling entity may configure the UE by sending downlink control information including a table index identifying the predetermined minimum delay in a table including a plurality of time delays. For example, in conjunction with Fig.13 The DL / UL communication circuit 1342 and transceiver 1310 shown and described may provide a means to configure the UE.

[0128] At block 1504, the scheduling entity may generate scheduling information that schedules transmission of a plurality of data transmissions with the UE over a plurality of time slots of the first carrier, each of the plurality of data transmissions corresponding to a respective one of the plurality of time slots. Fig.13The illustrated and described scheduling circuitry 1340 may provide a means for generating scheduling information (eg, PDCCH / DCI) that schedules communication of multiple PDSCHs and / or PUSCHs for a UE.

[0129] At block 1506, the scheduling entity may send scheduling information to the UE within the control resources allocated based on the time slot index of the plurality of time slots on the second carrier. In an example, the first carrier and the second carrier may be the first carrier 802 and the second carrier 804, respectively, which are described above with respect to Figure 8 Described.

[0130] In some examples, the control resource includes a plurality of physical downlink control channel (PDCCH) candidates associated with time slot indexes of a plurality of time slots, respectively. In some examples, the plurality of PDCCH candidates include a first PDCCH candidate associated with a first time slot in the plurality of time slots, and a second PDCCH candidate associated with a second time slot in the plurality of time slots, and the first time slot is earlier in time than the second time slot. In some examples, each time slot index is configured to indicate a corresponding time slot in a plurality of time slots including a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) relative to an initial time slot on a second carrier including the plurality of PDCCH candidates. In other examples, each time slot index is configured to indicate a corresponding time slot in a plurality of time slots including a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) relative to a frame or subframe on a second carrier including the plurality of PDCCH candidates.

[0131] In some examples, the control resources include multiple physical downlink control channel (PDCCH) candidates, and the control channel element (CCE) allocation of the PDCCH candidates depends on the time slot index of the multiple time slots. In some examples, the scheduling entity can use a first set of control resources associated with a first time slot in the multiple time slots to send a first part of the scheduling information, and use a second set of control resources associated with a second time slot in the multiple time slots to send a second part of the scheduling information. In some examples, each of the first set of control resources and the second set of control resources includes a search space or a control resource set.

[0132] In some examples, the scheduling entity may also send control information using at least one of radio resource control signaling, media access control (MAC) control element (MAC-CE), or downlink control information to indicate an association between the control resource and the plurality of time slots. Fig.13 The DL / UL communication circuitry 1342 and transceiver 1310 shown and described may provide a means for transmitting scheduling information to the UE.

[0133] Fig.16 1604. 1604 is a conceptual diagram illustrating an example of a hardware implementation of an exemplary scheduled entity 1600 using a processing system 1614. According to various aspects of the present disclosure, an element or any portion of an element or any combination of elements may be implemented using a processing system 1614 including one or more processors 1604. For example, the scheduled entity 1600 may be such as Figure 1 and / or Figure 2 Any one or more of the user equipments (UEs) shown in .

[0134] Processing system 1614 may be used with Fig.13 The processing system 1314 shown is substantially the same, including a bus interface 1608, a bus 1602, a memory 1605, a processor 1604, and a computer readable medium 1606. In addition, the scheduled entity 1600 may include a user interface 1612 and a transceiver 1610, substantially similar to the above in Fig.13 That is, the processor 1604 used in the scheduled entity 1600 can be used to implement Figure 8-12 , 17 and 18.

[0135] In some aspects of the present disclosure, processor 1604 may include circuits configured for various functions, including, for example, cross-carrier scheduling. For example, the circuits may be configured to implement Figure 8-12 , 17 and 18. For example, the processor 1604 may include a DL / UL communication circuit 1640, a scheduling circuit 1642 and a decoding circuit 1644.

[0136] The DL / UL communication circuit 1640 may be configured to perform various functions to send and receive data via the transceiver 1610 using the first carrier and / or the second carrier. The first carrier and the second carrier may have different parameter sets. In an example, the DL / UL communication circuit 1640 may be configured to receive scheduling information from a scheduling entity (e.g., a base station) on the first carrier. The scheduling information may configure the scheduled entity (e.g., UE) to use multiple PDSCH / PUSCH time slots on the second carrier to send or receive data (e.g., transmit data transmission). For example, the scheduling information may be a PDCCH / DCI sent on the first carrier for scheduling one or more PDSCH / PUSCH transmissions on the second carrier in multiple time slots.

[0137] The scheduling circuit 1642 may be configured to perform various functions of cross-carrier scheduling. For example, the scheduling circuit 1642 may be configured to determine the relative timing positions of multiple time slots based on the association between multiple time slots and control resources allocated to the scheduling information. Control resources may include, for example, search spaces, CORESETs, CCEs, and PDCCH candidates. The scheduling circuit 1642 may also be configured to access a table 1620 of scheduled cells (e.g., a time domain resource allocation (TDRA) table for PDSCH and PUSCH, respectively). Each row in the TDRA table may contain a K0 / K2 value. In some examples, the DL / UL communication circuit 1640 may receive an RRC message indicating a row index from a scheduling entity. Based on the index, the scheduling circuit 1642 may determine the K0 / K2 value from the table 1620.

[0138] The decoding circuit 1644 may be configured to perform various functions for decoding the scheduling information. For example, the decoding circuit 1644 may be configured to decode the scheduling information in an order based on the relative timing positions of the plurality of time slots determined by the scheduling circuit 1642.

[0139] In one or more examples, the computer-readable storage medium 1606 may include software configured for various functions, including, for example, cross-carrier scheduling. For example, the software may be configured to implement the above Figure 8-12 , 17 and 18. For example, the software may include DL / UL communication instructions 1650, scheduling instructions 1652 and decoding instructions 1654.

[0140] The DL / UL communication instructions 1650 may configure the scheduled entity 1600 to perform various functions to send and receive data via the transceiver 1610 using the first carrier and / or the second carrier. The first carrier and the second carrier may have different parameter sets. In an example, the DL / UL communication instructions 1650 may configure the scheduled entity 1600 to receive scheduling information from the scheduling entity (e.g., a base station) on the first carrier. The scheduling information may configure the scheduled entity (e.g., a UE) to send or receive data (e.g., transmit data transmissions) using multiple PDSCH / PUSCH time slots on the second carrier. For example, the scheduling information may be a PDCCH / DCI sent on the first carrier for scheduling one or more PDSCH / PUSCH transmissions on the second carrier in multiple time slots. The DL / UL communication instructions 1650 may be executed by the DL / UL communication circuit 1640.

[0141] The scheduling instructions 1652 may configure the scheduled entity 1600 to perform various functions of cross-carrier scheduling. For example, the scheduling instructions 1652 may configure the scheduled entity 1600 to determine the relative timing positions of the multiple time slots based on the association between the multiple time slots and the control resources allocated to the scheduling information. The control resources may include, for example, search spaces, CORESETs, CCEs, and PDCCH candidates. The scheduling instructions 1652 may further configure the scheduled entity 1600 to access the table 1620 for the scheduled cell. For example, based on the row index received from the scheduling entity, the scheduling instructions 1652 may configure the scheduled entity 1600 to determine the K0 / K2 value from the table 1620. The scheduling instructions 1652 may be executed by the scheduling circuit 1642.

[0142] The decoding instructions 1654 may configure the scheduled entity 1600 to perform various functions for decoding the scheduling information. For example, the decoding instructions 1654 may configure the scheduled entity 1600 to decode the scheduling information based on the order of the relative timing positions of the plurality of time slots determined by the scheduling circuit 1642. The decoding instructions 1654 may be executed by the decoding circuit 1644.

[0143] Fig.17 1 is a flow chart illustrating an exemplary process 1700 for decoding control information used in cross-carrier scheduling according to some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be necessary for all example implementations. In some examples, process 1700 may be performed by Fig.16 In some examples, process 1700 may be performed by any suitable device or means for performing the functions or algorithms described below.

[0144] At block 1702, a scheduled entity (e.g., a UE) receives scheduling information on a first carrier including a first parameter set. The scheduling information is configured to schedule the scheduled entity to transmit a plurality of data transmissions using a plurality of time slots on a second carrier, the second carrier including a second parameter set greater than the first parameter set. Each of the plurality of data transmissions may correspond to a respective one of the plurality of time slots. In one example, the scheduling information may be included in a PDCCH transmission of the first carrier. In one example, the first carrier and the second carrier may be the first carrier 802 and the second carrier 804, respectively, which are described above with respect to Figure 8 Described.

[0145] In some examples, the scheduled entity may receive a first portion of the scheduling information using a first set of control resources associated with a first time slot in the plurality of time slots, and receive a second portion of the scheduling information using a second set of control resources associated with a second time slot in the plurality of time slots. In some examples, each of the first set of control resources and the second set of control resources includes a search space or a set of control resources. For example, in combination with Fig.16 The DL / UL communication circuit 1640 and transceiver 1610 shown and described may provide a means for receiving scheduling information.

[0146] In box 1704, the scheduled entity can determine the relative timing position of multiple time slots based on the association between the multiple time slots and the control resources allocated to the scheduling information. The control resources may include PDCCH candidates, CCEs, search spaces, and CORESETs. In one example, the scheduled entity can determine the relative timing position of the time slots based on the association between the PDCCH candidates and the time slot index and / or the starting symbol index of the PDSCH / PUSCH on the scheduled carrier. In one example, the scheduled entity 1100 can determine the relative timing position of the time slot based on the association between the CCE allocation of the PDCCH candidates and the time slot index on the scheduled carrier. The relative timing position indicates a time-based order of multiple time slots including PDSCH / PUSCH. The multiple time slots may be related to the above Figure 8 The time slots of the second carrier 804 are described to be the same. For example, time slots 0 to 7 of the second carrier 804 appear at different timing positions.

[0147] In some examples, the control resource includes a plurality of physical downlink control channel (PDCCH) candidates associated with time slot indexes of a plurality of time slots, respectively. In some examples, the plurality of PDCCH candidates include a first PDCCH candidate associated with a first time slot in the plurality of time slots, and a second PDCCH candidate associated with a second time slot in the plurality of time slots, and the first time slot is earlier in time than the second time slot. In some examples, each time slot index is configured to indicate a corresponding time slot in a plurality of time slots including a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) relative to an initial time slot on a first carrier including the plurality of PDCCH candidates. In some examples, each time slot index is configured to indicate a corresponding time slot in a plurality of time slots including a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) relative to a frame or subframe on a second carrier including the plurality of PDCCH candidates.

[0148] In some examples, the control resource includes a plurality of physical downlink control channel (PDCCH) candidates, and a control channel element (CCE) allocation of the PDCCH candidates depends on a time slot index of the plurality of time slots. In some examples, the scheduled entity may also receive control information indicating an association between the control resource and the plurality of time slots using at least one of radio resource control signaling, a media access control (MAC) control element (MAC-CE), or downlink control information. For example, in combination with Fig.16 The scheduling circuit 1642 shown and described may provide a means for determining the relative timing positions of multiple time slots.

[0149] At block 1706, the scheduled entity may decode the scheduling information in an order based on the relative timing positions of the plurality of time slots. For example, the scheduled entity may decode the scheduling information that schedules a plurality of PDSCH and / or PUSCH transmissions in the plurality of time slots. Based on the relative timing positions, the scheduled entity prioritizes (e.g., decodes) scheduling information for a first time slot that is earlier than a second time slot.

[0150] For example, the control resources may include multiple PDCCH candidates associated with time slot indices and / or symbol indices of the scheduled PDSCH / PUSCH, respectively. The scheduled entity may decode a first PDCCH candidate associated with a first time slot before decoding a second PDCCH candidate associated with a second time slot that is later than the first time slot. In some examples, the CCE allocation of the PDCCH candidate may depend on the time slot index. In this case, the scheduled entity may decode the PDCCH candidates in the first CCE allocation associated with the first time slot before decoding the PDCCH candidates in the second CCE allocation associated with the second time slot that is later than the first time slot. In some examples, the search space (SS) or CORESET may depend on the time slot index. In this case, the scheduled entity may decode the PDCCH candidates in the first SS / CORESET associated with the first time slot before decoding the PDCCH candidates in the second SS / CORESET associated with the second time slot that is later than the first time slot. For example, the above in combination Fig.16 The decoding circuitry 1644 shown and described may provide a means for decoding the scheduling information.

[0151] Fig.18 1 is a flow chart illustrating an exemplary process 1800 for decoding control information used in cross-carrier scheduling according to some aspects of the present disclosure. As described below, in certain implementations within the scope of the present disclosure, some or all of the illustrated features may be omitted, and some of the illustrated features may not be necessary for all example implementations. In some examples, process 1800 may be performed by Fig.16In some examples, process 1800 may be performed by any suitable device or means for performing the functions or algorithms described below.

[0152] At block 1802, a scheduled entity (e.g., a UE) receives scheduling information on a first carrier including a first parameter set. The scheduling information is configured to schedule the scheduled entity to transmit a plurality of data transmissions using a plurality of time slots on a second carrier, the second carrier including a second parameter set greater than the first parameter set. Each of the plurality of data transmissions may correspond to a respective one of the plurality of time slots. In one example, the scheduling information may be included in a PDCCH transmission of the first carrier. In one example, the first carrier and the second carrier may be first carrier 802 and second carrier 804, respectively, as described above with respect to Figure 8 Described.

[0153] In some examples, the scheduled entity may receive a first portion of the scheduling information using a first set of control resources associated with a first time slot in the plurality of time slots, and receive a second portion of the scheduling information using a second set of control resources associated with a second time slot in the plurality of time slots. In some examples, each of the first set of control resources and the second set of control resources includes a search space or a set of control resources. For example, in combination with Fig.16 The DL / UL communication circuit 1640 and transceiver 1610 shown and described may provide a means for receiving scheduling information.

[0154] In box 1804, the scheduled entity can determine the relative timing position of multiple time slots based on the association between the multiple time slots and the control resources allocated to the scheduling information. The control resources may include PDCCH candidates, CCEs, search spaces, and CORESETs. In one example, the scheduled entity can determine the relative timing position of the time slots based on the association between the PDCCH candidates and the time slot index and / or the starting symbol index of the PDSCH / PUSCH on the scheduled carrier. In one example, the scheduled entity 1100 can determine the relative timing position of the time slot based on the association between the CCE allocation of the PDCCH candidates and the time slot index on the scheduled carrier. The relative timing position indicates a time-based order of multiple time slots including PDSCH / PUSCH. The multiple time slots may be related to the above Figure 8 The time slots of the second carrier 804 are described to be the same. For example, time slots 0 to 7 of the second carrier 804 appear at different timing positions.

[0155] In some examples, the control resource includes a plurality of physical downlink control channel (PDCCH) candidates associated with time slot indexes of a plurality of time slots, respectively. In some examples, the plurality of PDCCH candidates include a first PDCCH candidate associated with a first time slot in the plurality of time slots, and a second PDCCH candidate associated with a second time slot in the plurality of time slots, and the first time slot is earlier in time than the second time slot. In some examples, each time slot index is configured to indicate a corresponding time slot in a plurality of time slots including a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) relative to an initial time slot on a first carrier including the plurality of PDCCH candidates. In some examples, each time slot index is configured to indicate a corresponding time slot in a plurality of time slots including a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) relative to a frame or subframe on a second carrier including the plurality of PDCCH candidates.

[0156] In some examples, the control resource includes a plurality of physical downlink control channel (PDCCH) candidates, and a control channel element (CCE) allocation of the PDCCH candidates depends on a time slot index of the plurality of time slots. In some examples, the scheduled entity may also receive control information indicating an association between the control resource and the plurality of time slots using at least one of radio resource control signaling, a media access control (MAC) control element (MAC-CE), or downlink control information. For example, in combination with Fig.16 The scheduling circuit 1642 shown and described may provide a means for determining the relative timing positions of multiple time slots.

[0157] At block 1806, the scheduled entity may decode the scheduling information in an order based on the relative timing positions of the plurality of time slots. For example, the scheduled entity may decode the scheduling information that schedules a plurality of PDSCH and / or PUSCH transmissions in the plurality of time slots. Based on the relative timing positions, the scheduled entity prioritizes (e.g., decodes) scheduling information for a first time slot that is earlier than a second time slot.

[0158] For example, the control resources may include multiple PDCCH candidates associated with time slot indices and / or symbol indices of the scheduled PDSCH / PUSCH, respectively. The scheduled entity may decode a first PDCCH candidate associated with a first time slot before decoding a second PDCCH candidate associated with a second time slot that is later than the first time slot. In some examples, the CCE allocation of the PDCCH candidate may depend on the time slot index. In this case, the scheduled entity may decode a PDCCH candidate in a first CCE allocation associated with a first time slot before decoding a PDCCH candidate in a second CCE allocation associated with a second time slot that is later than the first time slot. In some examples, a search space (SS) or CORESET may depend on the time slot index. In this case, the scheduled entity may decode a PDCCH candidate in a first SS / CORESET associated with a first time slot before decoding a PDCCH candidate in a second SS / CORESET associated with a second time slot that is later than the first time slot. For example, the above in combination Fig.16 The decoding circuitry 1644 shown and described may provide a means for decoding the scheduling information.

[0159] At block 1808, the scheduled entity may transmit a plurality of data transmissions (e.g., PDSCH and / or PUSCH) based on a predetermined minimum delay between a control resource of the first carrier and a plurality of time slots of the second carrier. In some examples, the scheduled entity may receive the predetermined minimum delay in a radio resource control message. In some examples, the scheduled entity may receive downlink control information including a table index for looking up the predetermined minimum delay in a table including a plurality of time delays. For example, the above in conjunction with Fig.16 The scheduling circuitry 1642 and DL / UL communication circuitry 1640 and transceiver 1610 shown and described may provide a means for communicating multiple data transmissions.

[0160] In one configuration, the apparatus 1300 for wireless communication includes a method for performing Figure 8-12 , 14 and 15. For example, the apparatus 1300 may include: a module for generating scheduling information, the scheduling information scheduling the transmission of multiple data transmissions with a user equipment (UE) on multiple time slots of a first carrier including a first parameter set, each of the multiple data transmissions corresponding to a corresponding one of the multiple time slots; and a module for sending the scheduling information within a control resource allocated based on a time slot index of multiple time slots on a second carrier including a second parameter set that is smaller than the first parameter set. In one aspect, the aforementioned module may be Fig.13 The processor 1304 shown in is configured to perform the functions described in the aforementioned modules. On the other hand, the aforementioned modules may be a circuit or any device configured to perform the functions described in the aforementioned modules.

[0161] In one configuration, the apparatus 1600 for wireless communication includes a method for performing Figure 8-12 , 17 and 18. For example, the apparatus 1600 may include a module for receiving scheduling information on a first carrier including a first parameter set, the scheduling information scheduling the transmission of multiple data transmissions with the UE on multiple time slots of a second carrier including a second parameter set greater than the first parameter set, each of the multiple data transmissions corresponding to a corresponding one of the multiple time slots. The apparatus may also include a module for determining the relative timing positions of the multiple time slots based on an association between the time slot indices of the multiple time slots and the control resources allocated to the scheduling information. The apparatus may also include a module for decoding the scheduling information in an order based on the relative timing positions of the multiple time slots. In one aspect, the aforementioned modules may be Fig.16 The processor 1604 shown in is configured to perform the functions described in the aforementioned modules. On the other hand, the aforementioned modules may be a circuit or any device configured to perform the functions described in the aforementioned modules.

[0162] Of course, in the above examples, the circuits included in the processor 1304 / 1604 are provided only as examples, and other devices for performing the functions may be included in various aspects of the present disclosure, including but not limited to instructions stored in the computer-readable storage medium 1306 / 1606, or Figure 1 and / or Figure 2 any other suitable means or methods described in any of the foregoing, and utilizing, for example, Figure 8-12 , Fig.12 Describe the process and / or algorithm.

[0163] The following provides an overview of examples of the present disclosure.

[0164] Example 1: A method for performing wireless communications at a scheduling entity in a wireless communication network, comprising: generating scheduling information that schedules transmission of multiple data transmissions with a user equipment (UE) on multiple time slots of a first carrier including a first parameter set, each of the multiple data transmissions corresponding to a corresponding one of the multiple time slots; and sending the scheduling information within a control resource allocated based on a time slot index of the multiple time slots on a second carrier, the second carrier including a second parameter set that is smaller than the first parameter set.

[0165] Example 2: The method according to Example 1, wherein the control resources include a plurality of physical downlink control channel (PDCCH) candidates respectively associated with time slot indices of the plurality of time slots.

[0166] Example 3: A method according to Example 2, wherein: the multiple PDCCH candidates include a first PDCCH candidate associated with a first time slot among the multiple time slots, and a second PDCCH candidate associated with a second time slot among the multiple time slots, and the first time slot is earlier in time than the second time slot.

[0167] Example 4: A method according to Example 2 or 3, wherein each time slot index is configured to indicate a corresponding time slot among multiple time slots including a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) relative to an initial time slot on a second carrier including multiple PDCCH candidates.

[0168] Example 5: A method according to Example 2 or 3, wherein each time slot index is configured to indicate a corresponding time slot of a plurality of time slots including a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) relative to a frame or subframe on a second carrier including a plurality of PDCCH candidates.

[0169] Example 6: A method according to any one of Examples 1 to 5, wherein the control resources include multiple physical downlink control channel (PDCCH) candidates, and the allocation of control channel elements (CCE) of the PDCCH candidates depends on the time slot index of the multiple time slots.

[0170] Example 7: A method according to any one of Examples 1 to 6, wherein sending the scheduling information includes: using a first set of control resources associated with a first time slot among the multiple time slots to send a first part of the scheduling information; and using a second set of control resources associated with a second time slot among the multiple time slots to send a second part of the scheduling information.

[0171] Example 8: The method of Example 7, wherein each of the first set of control resources and the second set of control resources comprises a search space or a control resource set.

[0172] Example 9: According to any one of Examples 1 to 8, the method further includes: using at least one of the following to send control information to indicate the association between control resources and multiple time slots: radio resource control signaling; media access control (MAC) control element (MAC-CE); or downlink control information.

[0173] Example 10: The method according to any one of Examples 1 to 9 further includes: configuring the UE to transmit the multiple data transmissions according to a predetermined minimum delay between a control resource of the second carrier and multiple time slots of the first carrier.

[0174] Example 11: The method of Example 10 further includes: sending a predetermined minimum delay in a radio resource control message.

[0175] Example 12: The method according to Example 10 or 11 also includes: sending downlink control information, the downlink control information including a table index, the table index identifying the time delay included in a corresponding row in a table of multiple time delays.

[0176] Example 13: The method of Example 12, wherein the time delay is effective when the time delay is greater than or equal to a predetermined minimum delay.

[0177] Example 14: The method of Example 12, wherein the time delay is a delta value to be added by the UE to the predetermined minimum time delay.

[0178] Example 15: An apparatus configured for wireless communication, comprising a processor and a memory coupled to the processor, the processor and the memory configured to perform a method according to any one of Examples 1 to 14.

[0179] Example 16: An apparatus configured for wireless communication, comprising at least one apparatus for performing a method according to any one of Examples 1 to 14.

[0180] Example 17: A non-transitory computer readable medium storing computer executable code, comprising code for causing an apparatus to perform a method according to any one of Examples 1 to 14.

[0181] Example 18: A method for performing wireless communications at a user equipment (UE) in a wireless communication network, comprising: receiving scheduling information on a first carrier including a first parameter set, the scheduling information scheduling the transmission of multiple data transmissions with the UE on multiple time slots of a second carrier including a second parameter set greater than the first parameter set, each of the multiple data transmissions corresponding to a corresponding one of the multiple time slots; determining relative timing positions of the multiple time slots based on an association between the multiple time slots and control resources allocated to the scheduling information; and decoding the scheduling information in an order based on the relative timing positions of the multiple time slots.

[0182] Example 19: A method according to Example 18, wherein the control resources include a plurality of physical downlink control channel (PDCCH) candidates respectively associated with time slot indices of the plurality of time slots.

[0183] Example 20: A method according to Example 19, wherein: the multiple PDCCH candidates include a first PDCCH candidate associated with a first time slot among the multiple time slots, and a second PDCCH candidate associated with a second time slot among the multiple time slots, and the first time slot is earlier in time than the second time slot.

[0184] Example 21: A method according to Example 19, wherein each of the time slot indices is configured to indicate a corresponding time slot among the multiple time slots including a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) relative to an initial time slot on the first carrier including the multiple PDCCH candidates.

[0185] Example 22: A method according to Example 19, wherein each of the time slot indices is configured to indicate a corresponding time slot of the multiple time slots including a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) relative to a frame or subframe on a second carrier including the multiple PDCCH candidates.

[0186] Example 23: A method according to any one of Examples 18 to 22, wherein the control resources include multiple physical downlink control channel (PDCCH) candidates, and the control channel element (CCE) allocation of the PDCCH candidates depends on the time slot index of the multiple time slots.

[0187] Example 24: A method according to any one of Examples 18 to 23, wherein receiving scheduling information includes: receiving a first part of the scheduling information using a first set of control resources associated with a first time slot among a plurality of time slots; and receiving a second part of the scheduling information using a second set of control resources associated with a second time slot among the plurality of time slots.

[0188] Example 25: The method of Example 24, wherein each of the first set of control resources and the second set of control resources comprises a search space or a set of control resources.

[0189] Example 26: According to any one of Examples 18 to 25, the method further includes: using at least one of: radio resource control signaling; a media access control (MAC) control element (MAC-CE); or downlink control information to receive control information indicating an association between a control resource and a plurality of time slots.

[0190] Example 27: The method of any one of Examples 18 to 26, further comprising transmitting a plurality of data transmissions according to a predetermined minimum delay between a control resource of the first carrier and a plurality of time slots of the second carrier.

[0191] Example 28: The method of Example 27 further comprising: receiving a predetermined minimum delay in a radio resource control message.

[0192] Example 29: According to the method described in Example 27 or 28, the method also includes: receiving downlink control information, the downlink control information including scheduling information and a corresponding table index, which table index identifies a corresponding time delay for each data transmission in a plurality of data transmissions included in a corresponding row in a table including a plurality of time delays.

[0193] Example 30: The method according to Example 29 further includes: considering each corresponding time delay as valid when the corresponding time delay is greater than or equal to a predetermined minimum delay; and ignoring the scheduling information of each of multiple data transmissions whose corresponding time delay is less than the predetermined minimum delay.

[0194] Example 31: The method of Example 29 further includes: adding the corresponding time delay of each of the multiple data transmissions to a predetermined minimum time delay to identify the corresponding actual time delay of each of the multiple data transmissions.

[0195] Example 32: A user equipment (UE) configured for wireless communication, comprising a processor and a memory coupled to the processor, the processor and the memory configured to perform a method according to any one of Examples 18 to 31.

[0196] Example 33: An apparatus configured for wireless communication, comprising at least one apparatus for performing a method according to any one of Examples 18 to 31.

[0197] Example 34: A non-transitory computer readable medium storing computer executable code, comprising code for causing an apparatus to perform a method according to any one of Examples 18 to 31.

[0198] Several aspects of a wireless communication network have been described with reference to exemplary embodiments. As those skilled in the art will readily appreciate, various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures, and communication standards.

[0199] As an example, various aspects may be implemented in other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile Communications (GSM). Various aspects may also be extended to systems defined by the Third Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolution Data Optimized (EV-DO). Other examples may be implemented in systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunication standard, network architecture, and / or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.

[0200] In this disclosure, the word "exemplary" is used to mean "serving as an example, instance, or illustration." Any implementation or aspect described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects of the disclosure. Likewise, the term "aspect" does not require that all aspects of the disclosure include the discussed features, advantages, or modes of operation. The term "coupled" as used herein refers to a direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, then objects A and C can still be considered to be coupled to each other - even if they are not in direct physical contact with each other. For example, a first object can be coupled to a second object even if the first object has never been in direct physical contact with the second object. The terms "circuit" and "circuitry" are used broadly and are intended to include hardware implementations of electrical devices and conductors that, when connected and configured, implement the performance of the functions described in this disclosure, without limitation to types of electronic circuits, as well as software implementations of information and instructions that, when executed by a processor, implement the performance of the functions described in this disclosure.

[0201] Figure 1-18 One or more components, steps, features and / or functions shown in the drawings may be rearranged and / or combined into a single component, step, feature or function, or may be embodied in several components, steps or functions. Additional elements, components, steps and / or functions may also be added without departing from the novel features disclosed herein. Figure 1-18 The devices, apparatuses and / or components shown in the can be configured to perform one or more methods, features or steps described herein. The novel algorithms described herein can also be effectively implemented in software and / or embedded in hardware.

[0202] It should be understood that the specific order or hierarchy of steps in the disclosed methods is an illustration of an exemplary process. Based on design preferences, it should be understood that the specific order or hierarchy of steps in the methods may be rearranged. The accompanying method claims present elements of the various steps in an example order, and are not meant to be limited to the specific order or hierarchy presented unless specifically stated therein.

[0203] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. It will be readily apparent to those skilled in the art that various modifications to these aspects are to be made, and the general principles defined herein may be applicable to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but to conform to the full scope consistent with the language of the claims, wherein, unless otherwise stated, elements in the singular form are not intended to mean "one and only one", but rather "one or more". Unless otherwise stated, the term "some" refers to one or more. Phrases referring to "at least one" of a series of items refer to any combination of these items, including single members. For example, "at least one of a, b, or c" is intended to cover a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents of the elements of the various aspects described in this disclosure that are known or will be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be included in the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims.

Claims

1. A device for cross-carrier scheduling in a wireless communication network, comprising: A transceiver configured to communicate with a user equipment UE using a first carrier including a first parameter set and a second carrier including a second parameter set smaller than the first parameter set; One or more processors, coupled to the transceiver, the one or more processors configured to: configuring the UE to use a predetermined minimum timing between the first carrier and the second carrier; generating scheduling information that schedules transmission of a plurality of data transmissions with the UE over a plurality of scheduled time slots of the first carrier, each of the plurality of data transmissions corresponding to a respective one of the plurality of scheduled time slots; as well as The scheduling information is sent in a scheduling time slot of the second carrier to schedule the UE to transmit the multiple data transmissions according to the predetermined minimum timing between the first carrier and the second carrier, wherein the predetermined minimum timing is greater in duration than a minimum delay between a grant on a physical downlink control channel (PDCCH) of the second carrier and a multiple data transmission on a physical downlink shared channel (PDSCH) of the first carrier scheduled by the grant.

2. The device according to claim 1, wherein: To configure the UE, the one or more processors are further configured to: The predetermined minimum timing is sent to the UE in a radio resource control message.

3. The device according to claim 2, wherein: To configure the UE, the one or more processors are further configured to: sending downlink control information, the downlink control information comprising a table index for identifying a scheduling timing in a table, the table comprising a plurality of scheduling timings between a grant on the second carrier and a physical downlink shared channel PDSCH or a physical uplink shared channel PUSCH on the first carrier, When the identified scheduling timing is greater than or equal to the predetermined minimum timing, the scheduling timing is valid.

4. The device according to claim 2, wherein: To configure the UE, the one or more processors are further configured to: sending downlink control information, the downlink control information comprising a table index for identifying a scheduling timing in a table, the table comprising a plurality of scheduling timings between a grant on the second carrier and a physical downlink shared channel PDSCH or a physical uplink shared channel PUSCH on the first carrier, The scheduling timing is a delta value to be added to the predetermined minimum timing to configure the timing of the multiple data transmissions.

5. The device according to claim 1, wherein: To send the scheduling information, the one or more processors are further configured to: transmitting a first portion of the scheduling information using a first set of control resources associated with a first time slot of the plurality of scheduled time slots; as well as A second portion of the scheduling information is sent using a second set of control resources associated with a second time slot of the plurality of scheduled time slots.

6. The device according to claim 5, wherein: Each of the first set of control resources and the second set of control resources comprises a search space or a set of control resources.

7. A method for cross-carrier scheduling in a wireless communication network, comprising: Configuring a user equipment UE to use a predetermined minimum timing between a first carrier configured with a first parameter set and a second carrier configured with a second parameter set smaller than the first parameter set; generating scheduling information that schedules transmission of a plurality of data transmissions with the UE over a plurality of scheduled time slots of the first carrier, each of the plurality of data transmissions corresponding to a respective one of the plurality of scheduled time slots; as well as The scheduling information is sent in a scheduling time slot of the second carrier to schedule the UE to transmit the multiple data transmissions according to the predetermined minimum timing between the first carrier and the second carrier, wherein the predetermined minimum timing is greater in duration than a minimum delay between a grant on a physical downlink control channel (PDCCH) of the second carrier and a multiple data transmission on a physical downlink shared channel (PDSCH) of the first carrier scheduled by the grant.

8. The method according to claim 7, wherein: The configuring the UE comprises: The predetermined minimum timing is sent to the UE in a radio resource control message.

9. The method according to claim 8, wherein: The configuring the UE comprises: sending downlink control information, the downlink control information comprising a table index for identifying a scheduling timing in a table, the table comprising a plurality of scheduling timings between a grant on the second carrier and a physical downlink shared channel PDSCH or a physical uplink shared channel PUSCH on the first carrier, When the identified scheduling timing is greater than or equal to the predetermined minimum timing, the scheduling timing is valid.

10. The method according to claim 8, wherein: The configuring the UE comprises: sending downlink control information, the downlink control information comprising a table index for identifying a scheduling timing in a table, the table comprising a plurality of scheduling timings between a grant on the second carrier and a physical downlink shared channel PDSCH or a physical uplink shared channel PUSCH on the first carrier, The scheduling timing is a delta value to be added to the predetermined minimum timing to configure the timing of the multiple data transmissions.

11. A user equipment UE for wireless communication, comprising: a transceiver configured to communicate with a scheduling entity using a first carrier including a first set of parameters and a second carrier including a second set of parameters greater than the first set of parameters; One or more processors, coupled to the transceiver, the one or more processors configured to: receiving scheduling information in a scheduled time slot of the first carrier, the scheduling information scheduling transmission of a plurality of data transmissions over a plurality of scheduled time slots of the second carrier, each of the plurality of data transmissions corresponding to a respective one of the plurality of scheduled time slots; as well as The multiple data transmissions are transmitted in the multiple scheduled time slots according to a predetermined minimum timing between the control resources of the first carrier and the multiple scheduled time slots of the second carrier, wherein the predetermined minimum timing is greater in duration than a minimum delay between a grant on a physical downlink control channel (PDCCH) of the second carrier and multiple data transmissions on a physical downlink shared channel (PDSCH) of the first carrier scheduled by the grant.

12. The UE according to claim 11, wherein: The one or more processors are further configured to: The predetermined minimum timing is received from the scheduling entity in a radio resource control message.

13. The UE according to claim 12, wherein: The one or more processors are further configured to: receiving downlink control information, the downlink control information comprising a table index for identifying a scheduling timing in a table, the table comprising a plurality of scheduling timings between a grant on the second carrier and a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) on the first carrier, When the identified scheduling timing is greater than or equal to the predetermined minimum timing, the scheduling timing is valid.

14. The UE according to claim 12, wherein: The one or more processors are further configured to: receiving downlink control information, the downlink control information comprising a table index for identifying a scheduling timing in a table, the table comprising a plurality of scheduling timings between a grant on the second carrier and a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) on the first carrier, The scheduling timing is a delta value to be added to the predetermined minimum timing to configure the timing of the multiple data transmissions.

15. The UE according to claim 11, wherein: To receive the scheduling information, the one or more processors are further configured to: receiving a first portion of the scheduling information using a first set of control resources associated with a first time slot of the plurality of scheduled time slots; as well as A second portion of the scheduling information is received using a second set of control resources associated with a second time slot of the plurality of scheduled time slots.

16. The UE according to claim 15, wherein: Each of the first set of control resources and the second set of control resources comprises a search space or a set of control resources.

17. A method for wireless communication at a user equipment UE, comprising: receiving scheduling information in a scheduled time slot of a first carrier configured with a first parameter set, the scheduling information scheduling transmission of a plurality of data transmissions on a plurality of scheduled time slots of a second carrier configured with a second parameter set greater than the first parameter set, each of the plurality of data transmissions corresponding to a respective one of the plurality of scheduled time slots; as well as The multiple data transmissions are transmitted in the multiple scheduled time slots according to a predetermined minimum timing between the control resources of the first carrier and the multiple scheduled time slots of the second carrier, wherein the predetermined minimum timing is greater in duration than a minimum delay between a grant on a physical downlink control channel (PDCCH) of the second carrier and multiple data transmissions on a physical downlink shared channel (PDSCH) of the first carrier scheduled by the grant.

18. The method according to claim 17, further comprising: The predetermined minimum timing is received in a radio resource control message from a scheduling entity.

19. The method according to claim 18, further comprising: receiving downlink control information, the downlink control information comprising a table index for identifying a scheduling timing in a table, the table comprising a plurality of scheduling timings between a grant on the second carrier and a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) on the first carrier, When the identified scheduling timing is greater than or equal to the predetermined minimum timing, the scheduling timing is valid.

20. The method of claim 18, further comprising: receiving downlink control information, the downlink control information comprising a table index for identifying a scheduling timing in a table, the table comprising a plurality of scheduling timings between a grant on the second carrier and a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) on the first carrier, The scheduling timing is a delta value to be added to the predetermined minimum timing to configure the timing of the multiple data transmissions.

Images