Cross-carrier scheduling in the presence of multiple transmission reception points (MTRP) based on multiple downlink control information (DCI) (multi-DCI)

Abstract

Embodiments include systems and methods for implementing cross-carrier scheduling in the presence of multiple transmission reception points (MTRPs) based on multiple downlink control information (DCI) (multi-DCI). Various aspects include a method for managing cross-carrier scheduling performed by a processor of a wireless device. Various aspects may include determining whether a scheduling cell is configured to perform cross-carrier scheduling on a scheduled cell, determining a control resource set (CORESET) pool index (CORESETPoolIndex) value of the scheduling cell in response to determining that the scheduling cell is configured to perform cross-carrier scheduling on the scheduled cell, and associating the scheduled cell with the determined CORESETPoolIndex value of the scheduling cell.

Description

[0001] background

[0002] This application claims the benefit of priority to U.S. Provisional Application No. 63 / 025,824, filed on May 15, 2020, entitled “Cross-Carrier Scheduling In The Presence Of Multi-DCI Based MTRP,” the entire contents of which are incorporated herein by reference for all purposes.

[0003] background

[0004] Long Term Evolution (LTE), fifth generation (5G) New Radio (NR) (5GNR), and other recently developed communication technologies allow wireless devices to communicate information at data rates (e.g., in gigabits per second, etc.) orders of magnitude greater than those available just a few years ago. Today's communication systems are also more secure, resilient to multipath fading, allow for lower network traffic latency, and provide better communication efficiency (e.g., in bits used per second per unit of bandwidth, etc.). These and other recent improvements have enabled the emergence of the Internet of Things (IoT), massive machine-to-machine (M2M) communication systems, autonomous vehicles, and other technologies that rely on continuous and secure communications.

[0005] The communication system can be configured to employ carrier aggregation (CA) to provide sufficient bandwidth to support high data rate communications. CA systems combine bandwidth from different frequency bands, each of which is called a component carrier. Each component carrier can be scheduled differently. For example, component carriers for downlink control information, downlink data, uplink control information, and uplink data can each be independently scheduled, which is called cross-carrier scheduling.

[0006] Overview

[0007] Various aspects include systems and methods for managing cross-carrier scheduling in the presence of multiple transmission reception points (MTRPs) based on multiple downlink control information (DCI) (multi-DCI). Various aspects include methods for managing cross-carrier scheduling performed by a processor of a wireless device. Various aspects may include receiving a DCI from a scheduling cell that schedules a communication on a scheduled cell, transmitting the communication or monitoring the communication on the scheduled cell based on the DCI, and performing a Type-1 hybrid automatic repeat request (HARQ) acknowledgment (HARQ-ACK) operation for the communication based on one or more control resource sets (CORESET) pools configured for the scheduled cell.

[0008] Some aspects may further include receiving a cross-carrier scheduling configuration of the scheduler cell, the cross-carrier scheduling configuration indicating the one or more CORESET pools.

[0009] In some aspects, in response to the cross-carrier scheduling configuration indicating two CORESET pools, performing a Type 1 HARQ-ACK operation for the communication based on one or more CORESET pools configured for the scheduled cell may include: based on the CORESET pool of the scheduler cell being indicated as a first CORESET pool, performing a Type 1 HARQ-ACK operation for the communication on the first CORESET pool including the scheduled cell, or based on the CORESET pool of the scheduler cell being indicated as a second CORESET pool, performing a Type 1 HARQ-ACK operation for the communication on the second CORESET pool including the scheduled cell.

[0010] In some aspects, in response to the cross-carrier scheduling configuration indicating two CORESET pools of the scheduling cell, performing type 1 HARQ-ACK operations for the communication based on the one or more CORESET pools configured for the scheduled cell may include: a first CORESET pool based on the two CORESET pools is a default CORESET pool, and type 1 HARQ-ACK operations are performed for the communication on the first CORESET pool, and the first CORESET pool includes the scheduled cell.

[0011] In some aspects, in response to the cross-carrier scheduling configuration indicating two CORESET pools of the scheduling cell and a selected CORESET pool of the two CORESET pools being associated with the scheduled cell, performing a Type 1 HARQ-ACK operation for the communication based on the one or more CORESET pools configured for the scheduled cell may include: performing a Type 1 HARQ-ACK operation for the communication on the selected CORESET pool based on the indication in the cross-carrier scheduling configuration, the selected CORESET pool including the scheduled cell.

[0012] In some aspects, in response to the cross-carrier scheduling configuration indicating two CORESET pools of the scheduling cell and the association of the scheduled cell with the two CORESET pools, performing Type 1 HARQ-ACK operations for the communication based on the one or more CORESET pools configured for the scheduled cell may include: performing Type 1 HARQ-ACK operations for the communication on the two CORESET pools based on the indication of the association with the two CORESET pools in the cross-carrier scheduling configuration, the two CORESET pools including the scheduled cell.

[0013] Some aspects may further include handling the scheduled cell as a multi-DCI mode cell in wireless device operation based on the indication of association with the two CORESET pools in the cross-carrier scheduling configuration.

[0014] In some aspects, handling the scheduled cell as a multi-DCI mode cell in wireless device operation may include counting the scheduled cell as two serving cells to generate a Type 2 HARQ-ACK codebook for the scheduled cell.

[0015] In some aspects, handling the scheduled cell as a multi-DCI mode cell in wireless device operation may include initializing two scrambling identifiers of a physical downlink shared channel (PDSCH) in the scheduled cell.

[0016] In some aspects, handling the scheduled cell as a multi-DCI mode cell in wireless device operation may include configuring two cell-specific reference signal (CRS) rate matching pattern lists in the scheduled cell.

[0017] In some aspects, handling the scheduled cell as a multiple DCI mode cell in wireless device operation may include supporting out-of-order operation of the scheduled cell.

[0018] In some aspects, handling the scheduled cell as a multi-DCI mode cell in wireless device operation may include associating two active transmission configuration indicator (TCI) state lists with the scheduled cell.

[0019] In some aspects, handling the scheduled cell as a multi-DCI mode cell in wireless device operation may include including the scheduled cell in a serving cell list provided with both CORESETPoolIndex values ​​of 0 and 1 for calculating physical downlink control channel (PDDCH) candidates and / or non-overlapping control channel element (CCE) restrictions.

[0020] In some aspects, the cross-carrier scheduling configuration may be received in a radio resource control (RRC) message.

[0021] In some aspects, the one or more CORESET pools may be indicated by one or more control resource set (CORESET) pool index (CORESETPoolIndex) values.

[0022] Various aspects include a method for managing cross-carrier scheduling performed by a processor of a network computing device. Various aspects may include transmitting a cross-carrier scheduling configuration of a scheduled cell to a wireless device. In some aspects, the cross-carrier scheduling configuration may indicate one or more associated CORESET pools of a scheduling cell configured to schedule the scheduled cell. Some aspects may include transmitting DCI for the scheduled cell from the scheduling cell to the wireless device, and receiving joint feedback for type 1 HARQ-ACK operations for communications associated with the scheduled cell from the wireless device.

[0023] In some aspects, the one or more associated CORESET pools may be indicated by one or more CORESETPoolIndex values.

[0024] In some aspects, the cross-carrier scheduling configuration may indicate that a single CORESET pool of the one or more associated CORESET pools of the scheduler cell is the CORESET pool of the scheduled cell.

[0025] In some aspects, the cross-carrier scheduling configuration may indicate that two of the one or more associated CORESET pools of the scheduler cell are CORESET pools of the scheduled cell.

[0026] In some aspects, the cross-carrier scheduling configuration may be communicated to the wireless device in a radio resource control (RRC) message.

[0027] A further aspect includes a wireless device having a processor configured with processor-executable instructions for performing the operations of any of the methods outlined above. A further aspect includes a processor configured for use in a wireless device and configured with processor-executable instructions for performing the operations of any of the methods outlined above. A further aspect includes a wireless device having means for performing the functions of any of the methods outlined above. A further aspect includes a non-transitory processor-readable storage medium having processor-executable instructions stored thereon, the processor-executable instructions configured to cause a wireless device processor to perform the operations of any of the methods outlined above.

[0028] A further aspect may include a network computing device having a processor configured to perform one or more operations of any of the methods outlined above. A further aspect may include a non-transitory processor-readable storage medium having processor-executable instructions stored thereon, the processor-executable instructions being configured to cause a processor of the network computing device to perform the operations of any of the methods outlined above. A further aspect includes a network computing device having means for performing the functions of any of the methods outlined above. A further aspect includes a system-on-chip for use in a network computing device, the system-on-chip including a processor configured to perform one or more operations of any of the methods outlined above. A further aspect includes a system-in-package including two systems-on-chip for use in a network computing device, the system-on-chip including a processor configured to perform one or more operations of any of the methods outlined above. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate exemplary embodiments of the claims and, together with the general description given above and the detailed description given below, serve to explain features of the claims.

[0031] Figure 1 is a system block diagram illustrating an example communication system suitable for implementing any of the various embodiments.

[0032] Figure 2 is a component block diagram illustrating an example computing and wireless modem system suitable for implementing any of the various embodiments.

[0033] Figure 3 is a component block diagram illustrating a software architecture including a radio protocol stack for a user plane and a control plane in wireless communications suitable for implementing any of the various embodiments.

[0034] Figure 4 is a component block diagram of an example system configured to manage cross-carrier scheduling by a processor of a wireless device.

[0035] Figure 5A and 5B Two examples of cross-carrier scheduling are explained.

[0036] Figure 5C is a process flow diagram illustrating a method for managing cross-carrier scheduling that may be performed by a processor of a wireless device in accordance with various embodiments.

[0037] Figure 5D is a process flow diagram illustrating a method for managing cross-carrier scheduling that may be performed by a processor of a network computing device in accordance with various embodiments.

[0038] Fig. 6Ais a process flow diagram illustrating a method for managing cross-carrier scheduling that may be performed by a processor of a wireless device in accordance with various embodiments.

[0039] Figure 6B is a process flow diagram illustrating a method for managing cross-carrier scheduling that may be performed by a processor of a wireless device in accordance with various embodiments.

[0040] Figure 7 An example of cross-carrier scheduling supporting joint semi-persistent hybrid automatic repeat request (HARQ) acknowledgment (HARQ-ACK) in accordance with various embodiments is illustrated.

[0041] Fig. 8A is a process flow diagram illustrating a method for managing cross-carrier scheduling that may be performed by a processor of a wireless device in accordance with various embodiments.

[0042] Figure 8B is a process flow diagram illustrating a method for managing cross-carrier scheduling that may be performed by a processor of a wireless device in accordance with various embodiments.

[0043] Figure 8C is a process flow diagram illustrating a method for managing cross-carrier scheduling that may be performed by a processor of a wireless device in accordance with various embodiments.

[0044] Fig.8D is a process flow diagram illustrating a method for managing cross-carrier scheduling that may be performed by a processor of a wireless device in accordance with various embodiments.

[0045] Fig. 9A is a process flow diagram illustrating a method for managing cross-carrier scheduling that may be performed by a processor of a network computing device in accordance with various embodiments.

[0046] Fig. 9B An example cross-carrier scheduling scheme in accordance with various embodiments is illustrated.

[0047] Fig. 10A is a process flow diagram illustrating a method for managing cross-carrier scheduling that may be performed by a processor of a wireless device in accordance with various embodiments.

[0048] Fig. 10B is a process flow diagram illustrating a method for managing cross-carrier scheduling that may be performed by a processor of a wireless device in accordance with various embodiments.

[0049] Fig. 10C is a process flow diagram illustrating a method for managing cross-carrier scheduling that may be performed by a processor of a wireless device in accordance with various embodiments.

[0050] Fig. 10Dis a process flow diagram illustrating a method for managing cross-carrier scheduling that may be performed by a processor of a wireless device in accordance with various embodiments.

[0051] Fig.11 An example of cross-carrier scheduling supporting joint semi-static HARQ-ACK according to various embodiments is illustrated.

[0052] Fig.12 is a process flow diagram illustrating a method for managing cross-carrier scheduling that may be performed by a processor of a wireless device in accordance with various embodiments.

[0053] Fig.13 is a component block diagram of an example network computing device.

[0054] Fig.14 is a component block diagram of an example wireless device.

[0055] Detailed Description

[0056] Various embodiments will be described in detail with reference to the accompanying drawings. Wherever possible, the same reference numerals will be used throughout the drawings to refer to the same or similar parts. References to specific examples and embodiments are for illustrative purposes and are not intended to limit the scope of the claims.

[0057] Embodiments include systems and methods for implementing cross-carrier scheduling in the presence of multiple transmission reception points (MTRPs) based on multiple downlink control information (DCI) (multi-DCI). Embodiments may enable a wireless device to manage cross-carrier scheduling. Embodiments may enable a wireless device to determine a control resource set (CORESET) pool index (CORESETPoolIndex) value for a cross-carrier scheduled serving cell (sometimes also referred to as a component carrier (CC)). Embodiments may enable a wireless device to handle a serving cell (or CC), which is a scheduled cell scheduled by a scheduler cell across carriers, as a multi-DCI mode cell in wireless device operation. In various embodiments, a serving cell (or CC) (which is a scheduled cell scheduled by a scheduling cell across carriers) is handled as a multi-DCI mode cell in wireless device operation to support hybrid automatic repeat request (HARQ) acknowledgement (HARQ-ACK) operations of the serving cell, physical downlink shared channel (PDSCH) scrambling operations of the serving cell, cell-specific reference signal (CRS) rate matching operations of the serving cell, out-of-order operations of the serving cell, PDSCH active transmission configuration indicator (TCI) state operations of the serving cell, physical downlink control channel (PDDCH) candidate calculation operations of the serving cell, and / or non-overlapping control channel element (CCE) restriction calculation operations of the serving cell. Various embodiments may enable a wireless device to manage cross-carrier scheduling with a scheduling cell and a scheduled cell. Cross-carrier scheduling may help reduce signal interference in heterogeneous network deployments employing carrier aggregation, especially when a heterogeneous combination of macro cells, small cells, relays, etc. is used. Cross-carrier scheduling can also be used to balance the load from traffic and scheduling across different component carriers.

[0058] The term "wireless device" is used herein to refer to any or all of the following: cellular telephones, smart phones, portable computing devices, personal or mobile multimedia players, laptop computers, tablet computers, smartbooks, ultrabooks, handheld computers, wireless email receivers, Internet-enabled multimedia cellular telephones, medical devices and equipment, biosensors / devices, wearable devices (including smart watches, smart clothing, smart glasses, smart wristbands, smart jewelry (e.g., smart rings, smart bracelets, etc.)), entertainment devices (e.g., wireless game controllers, music and video players, satellite radios, etc.), wireless network-enabled Internet of Things (IoT) devices (including smart meters / sensors, industrial manufacturing equipment, large and small machines and appliances for home or business use), wireless communication elements within autonomous and semi-autonomous vehicles, wireless devices attached to or incorporated into various mobile platforms, and similar electronic devices that include memory, wireless communication components and programmable processors.

[0059] The term "system on chip" (SOC) is used herein to refer to a single integrated circuit (IC) chip that includes multiple resources and / or processors integrated on a single substrate. A single SOC may include circuit systems for digital, analog, mixed signal, and radio frequency functions. A single SOC may also include any number of general and / or special processors (digital signal processors, modem processors, video processors, etc.), memory blocks (e.g., ROM, RAM, flash memory, etc.), and resources (e.g., timers, voltage regulators, oscillators, etc.). Each SOC may also include software for controlling the integrated resources and processors, and for controlling peripheral devices.

[0060] The term "system-in-package" (SIP) may be used herein to refer to a single module or package that contains multiple resources, computing units, cores and / or processors on two or more IC chips, substrates, or SOCs. For example, a SIP may include a single substrate on which multiple IC chips or semiconductor dies are stacked in a vertical configuration. Similarly, a SIP may include one or more multi-chip modules (MCMs) on which multiple ICs or semiconductor dies are packaged into a unified substrate. A SIP may also include multiple independent SOCs that are coupled together via high-speed communication circuitry and packaged together in close proximity (such as on a single motherboard or in a single wireless device). The proximity of the SOCs facilitates high-speed communication and sharing of memory and resources.

[0061] The term "radio resources" is used herein to refer to hardware (such as modems, radios, processors, transceivers, transmitters, receivers, timers, voltage regulators, oscillators, amplifiers, filters, antennas, circuits, encoders, decoders, etc.) and / or software operating alone or in any combination for sending and / or receiving electromagnetic radiation to provide wireless communication services, such as cellular and mobile communication services.

[0062] The embodiments described herein use the term "server" to refer to any computing device that can function as a server, such as a primary exchange server, a web server, a mail server, a document server, a content server, or any other type of server. A server can be a dedicated computing device or a computing device that includes a server module (e.g., running an application that causes the computing device to function as a server). A server module (e.g., a server application) can be a full-featured server module, or a light server module or sub-server module (e.g., a light server application or sub-server application) configured to provide synchronization services between dynamic databases on a receiver device. A light server or sub-server can be a stripped-down version of server-type functionality that can be implemented on a receiver device so that the receiver device can function as an Internet server (e.g., a corporate email server) only to the extent necessary to provide the functionality described herein.

[0063] As used herein, the terms "network", "system", "wireless network", "cellular network" and "wireless communication network" may interchangeably refer to a portion or all of an operator's wireless network associated with a wireless device and / or a subscription on a wireless device. The techniques described herein may be used in various wireless communication networks, such as code division multiple access (CDMA), time division multiple access (TDMA), FDMA, orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), and other networks. In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support at least one radio access technology that may operate on one or more frequencies or frequency ranges. For example, a CDMA network may implement Universal Terrestrial Radio Access (UTRA) (including Wideband Code Division Multiple Access (WCDMA) standards), CDMA2000 (including IS-2000, IS-95 and / or IS-856 standards), and the like. In another example, a TDMA network may implement GSM Enhanced Data Rates for GSM Evolution (EDGE). In another example, an OFDMA network may implement Evolved DURA (E-DURA) (including LTE standards), IEEE 802.11 (WiFi), IEEE 802.16 (WiMAX), IEEE 802.20, Etc. References may be made to wireless networks using the LTE standard, and thus the terms "Evolved Universal Terrestrial Radio Access," "E-UTRAN," and "NodeB" may also be used interchangeably herein to refer to the wireless network. However, such references are provided merely as examples and are not intended to exclude wireless networks using other communication standards.

[0064] In cross-carrier scheduling, a first cell (a "scheduling cell", such as a primary cell or "PCell") may provide scheduling information in a downlink control information (DCI) of a physical downlink control channel (PDCCH) for a second cell (a "scheduled cell", such as a secondary cell or "SCell"). The scheduling cell PDCCH provides DCI for scheduling downlink and uplink data channels (i.e., a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH)) of the scheduled cell (e.g., DCI format 1_1 for scheduling of PDSCH and DCI format 0_1 ​​for scheduling of PUSCH). The scheduling cell PDCCH also includes a carrier indicator field (CIF) that identifies the component carrier on which resources are scheduled. The CIF in the DCI is used to indicate the scheduled serving cell (or CC). The number of bits of the CIF may be from 0 bits to 3 bits. When there are no bits configured for the CIF (e.g., there are no CIF bits, or another way of saying there is no CIF), the lack of a CIF indicates that only self-scheduling is possible. If the CIF value is set to 0, the cell performs self-scheduling and schedules DCI for the same serving cell (or CC). If the CIF value is set to a non-zero value (e.g., an integer value from 1 to 7), the serving cell may be scheduling the scheduled cell. In some embodiments, the configuration may be provided as "CrossCarrierSchedulingConfig" in RRC. Two different scheduling cells cannot schedule the same scheduled cell. In addition, when another cell uses the corresponding CIF value to schedule the scheduled cell, the scheduled cell generally does not monitor the PDCCH.

[0065] The cell may be configured for multi-transmit receive point (multi-TRP) (MTRP) operation. The term "transmit receive point" (TRP) is used herein to refer to any 5G New Radio (NR) entity capable of transmitting and receiving signals, and may include macro cells, small cells, pico cells, femto cells, remote radio heads, relay nodes, panels, radio frequency (RF) modules in a cell, and other similar devices.

[0066] MTRP operation may be defined for a given serving cell (e.g., a given component carrier (CC)). A first DCI transmitted from a first TRP may schedule a first PDSCH transmitted from the first TRP. A second DCI transmitted from a second TRP may schedule a second PDSCH transmitted from the second TRP. In some embodiments, in order to enable a wireless device to monitor first and second DCI transmitted from first and second TRPs, different control resource sets (CORESETs) may be used. In some embodiments, the maximum permitted number of CORESETs may be 3 or more, such as, for example, 3, 4, 5, etc. In order to enable a wireless device to distinguish TRPs based on CORESET groups, a higher layer signaling index (such as a control resource set (CORESET) pool index (CORESETPoolIndex)) may be defined per CORESET, which may allow CORESETs to be grouped into two groups. Each CORESET group may be indicated by a CORESETPoolIndex value (e.g., CORESETPoolIndex=0 and CORESETPoolIndex=1). In some embodiments, any distinction between TRPs may be transparent to the wireless device. In some embodiments, the wireless device may be configured by a higher layer parameter PDDCH-Config that contains two different values ​​of CORESETPoolIndex in the CORESET of the active bandwidth part (BWP) of the serving cell. For example, CORESETPoolIndex=0 may be associated with CORESET identifier (ID) 1 and CORESET ID 2, while CORESETPoolIndex=1 may be associated with CORESET ID 3 and CORESET ID 4. In various embodiments, a multi-DCI based MTRP may be defined in a given serving cell (or CC), and only some serving cells (or CCs) may be configured with two CORESETPoolIndex values.

[0067] In order to implement MTRP communication based on multiple DCIs, it may be determined whether the scheduling cell is able to schedule the serving cell (the scheduled cell). In some cases, the scheduling cell may not be configured to perform MTRP communication based on multiple DCIs. In some embodiments, it may be determined whether the serving cell can schedule a specific scheduled cell. In some cases, the scheduled cell may not be configured to perform MTRP communication based on multiple DCIs. In addition, it may be necessary to make determinations about how to perform various communication operations, which depend on the CORESETPoolIndex of the received DCI, such as HARQ-Ack feedback, PDSCH scrambling, rate matching of PDSCH, etc.

[0068] In current networks, multi-DCI based MTRP may be supported only when the serving cell is self-scheduling. In current networks, CORESET may not be configured for cells scheduled across carriers. The failure of the current network to configure CORESET for cells scheduled across carriers prevents the implementation of multi-DCI based MTRP for cells scheduled across carriers in the current network. The failure of the current network to configure CORESET for cells scheduled across carriers prevents the implementation of joint type 1 (i.e., semi-static) hybrid automatic repeat request (HARQ) acknowledgment (HARQ-ACK) for cells scheduled across carriers in the current network.

[0069] In type 1 (i.e., semi-static) HARQ-ACK, for each CC, a set of candidate PDSCH reception timings is determined. For each CC, if a PDSCH is received during the candidate PDSCH reception timing, a HARQ-ACK for the PDSCH is inserted at the corresponding position. Otherwise, a negative acknowledgement (NACK) is inserted. This operation is completed across all configured downlink (DL) CCs. For multiple DCIs and when joint feedback is configured, type 1 (i.e., semi-static) HARQ-ACK includes defining two CC lists associated with the two values ​​of CORESETPoolIndex. CCs configured with multiple DCIs appear once in the first list (referred to as list or set "S0") and another time in the second list (referred to as list or set "S1"). The procedure for generating HARQ-ACK is then performed twice, once for the first set S0 and the other for the second set S1. The joint feedback is transmitted in the same physical uplink control channel (PUCCH) resource after concatenating the two codebooks (i.e., two type 1 HARQ-ACK codebooks) generated from the two lists (i.e., S0 and S1). Since a CORESET may not be configured for a cross-carrier scheduled cell in the current network, the lack of a configured CORESET prevents the cross-carrier scheduled cell in the current network from being correctly associated with the set for type 1 HARQ-ACK (i.e., S0 and S1).

[0070] Embodiments include systems and methods for implementing cross-carrier scheduling in the presence of multi-DCI based MTRP. Embodiments may enable the CORESETPoolIndex value of a scheduling cell to be associated with a scheduled cell scheduled across carriers by the scheduling cell. Embodiments may implement joint type 1 (i.e., semi-static) HARQ-ACK for cells scheduled across carriers.

[0071] In various embodiments, the wireless device may determine whether a CORESET in a first CC (or serving cell) is configured with a CORESETPoolIndex value and whether the first CC (or serving cell) schedules a second CC (or serving cell) (i.e., the first CC is a scheduling cell and the second CC is a scheduled cell). In response to determining that a CORESET in a first CC (or serving cell) is configured with a CORESETPoolIndex value and the first CC (or serving cell) is scheduling the second CC (or serving cell) (i.e., the first CC is a scheduling cell and the second CC is a scheduled cell), the wireless device may associate the second CC (or serving cell) with the same CORESETPoolIndex value as the first CC (or serving cell).

[0072] In various embodiments, the wireless device may determine whether at least one CC (or serving cell) is configured with two CORESETPoolIndex values ​​and whether joint feedback and type 1 HARQ-ACK are set for the wireless device. For example, the wireless device may determine whether to set joint type 1 HARQ-ACK for the wireless device by determining whether joint feedback and type 1 HARQ-ACK codebooks are configured by RRC on the wireless device. In response to determining that at least one CC (or serving cell) is configured with two CORESETPoolIndex values ​​and joint feedback and type 1 HARQ-ACK are set for the wireless device, the wireless device may place (or assign to) a CC (or serving cell) cross-carrier scheduled by another CC (or serving cell) (scheduler CC or scheduler cell) in a first list (S0) in response to only CORESETPoolIndex=0 being configured in the scheduler CC (or scheduler cell) or CORESETPoolIndex not being configured (e.g., not present in the CIF). In response to determining that at least one CC (or serving cell) is configured with two CORESETPoolIndex values ​​and joint feedback and type 1 HARQ-ACK are set for the wireless device, the wireless device may place (or assign) one CC (or serving cell) scheduled by another CC (or serving cell) (scheduler CC or scheduler cell) across carriers in the second list (S1) in response to only CORESETPoolIndex=1 being configured in the scheduler CC (or scheduler cell). The procedure for generating HARQ-ACK may then be performed twice; once for set S0 and once for set S1, and after concatenating two codebooks generated from the two lists (i.e., the codebook of S0 is concatenated with the codebook of S1), the joint feedback is transmitted in the same PUCCH resource.

[0073] In various embodiments, the network computing device may generate a cross-carrier scheduling configuration for a scheduled cell (or scheduled CC), the cross-carrier scheduling configuration indicating an associated CORESETPoolIndex value of a scheduling cell (or scheduling CC) configured to schedule the scheduled cell (or scheduled CC). The cross-carrier scheduling configuration may be transmitted to a wireless device served by the scheduling cell (or scheduling CC). For example, the cross-carrier scheduling configuration may be transmitted to the wireless device in an RRC message (such as part of "CrossCarrierSchedulingConfig" in RRC). In various embodiments, the associated CORESETPoolIndex value may correspond to the CORESETPoolIndex value of the scheduling cell (or scheduling CC). In some embodiments, the associated CORESETPoolIndex value may be 0 or 1. In some embodiments, the associated CORESETPoolIndex value may indicate that the scheduling cell (or scheduling CC) has both a CORESETPoolIndex value of 0 and a CORESETPoolIndex value of 1. In this way, the associated CORESETPoolIndex value may indicate that the scheduler cell (or scheduler CC) is a multi-DCI mode cell, such as a multi-DCI mode based cell supporting MTRP. In various embodiments, the associated CORESETPoolIndex value may be 2.

[0074] In various embodiments, a scheduling CC (or scheduling cell) configured with two CORESETPoolIndex values ​​in different CORESETs may schedule a second CC (or second serving cell) (i.e., a scheduled CC or a scheduled cell), and the second CC (or second serving cell) (i.e., a scheduled CC or a scheduled cell) may always be associated with CORESETPoolIndex = 0. In such embodiments, only a CORESET with CORESETPoolIndex = 0 in the scheduling CC (or scheduling cell) may schedule the second CC (or second serving cell) (i.e., a scheduled CC or a scheduled cell).

[0075] In various embodiments, a scheduler CC (or scheduler cell) configured with two CORESETPoolIndex values ​​in different CORESETs may schedule a second CC (or second serving cell) (i.e., a scheduled CC or a scheduled cell), and the second CC (or second serving cell) (i.e., a scheduled CC or a scheduled cell) may be associated with one CORESETPoolIndex value. In such embodiments, the CORESETPoolIndex value may be configured as part of a cross-carrier scheduling configuration via RRC. In such embodiments, only a CORESET in a scheduler CC (or scheduler cell) with the CORESETPoolIndex value may schedule a second CC (or second serving cell) (i.e., a scheduled CC or a scheduled cell).

[0076] In various embodiments, a scheduling CC (or scheduling cell) configured with two CORESETPoolIndex values ​​in different CORESETs may schedule a second CC (or second serving cell) (i.e., a scheduled CC or a scheduled cell), and the second CC (or second serving cell) (i.e., a scheduled CC or a scheduled cell) may be associated with a CORESETPoolIndex value of 0, a value of 1, or both values ​​of 0 and 1. The CORESETPoolIndex value may be configured as part of a cross-carrier scheduling configuration via RRC. Both values ​​of CORESETPoolIndex being configured (i.e., both 0 and 1 being configured) may indicate that the second CC (or second serving cell) (i.e., a scheduled CC or a scheduled cell) is operating in a multi-DCI mode. In some embodiments, a third integer value of the associated CORESETPoolIndex (such as a value of 2) may indicate that two values ​​of CORESETPoolIndex (i.e., 0 and 1) are configured for the second CC (or second serving cell) (scheduled CC or a scheduled cell).

[0077] In various embodiments, the wireless device may determine whether a scheduler CC (or scheduler cell) is configured with two CORESETPoolIndex values ​​in different CORESETs, and whether the scheduler CC (or scheduler cell) schedules a second CC (or second serving cell) (i.e., a scheduled CC or a scheduled cell), and whether joint feedback and type 1 HARQ-ACK are set for the wireless device. For example, the wireless device may determine whether to set joint type 1 HARQ-ACK for the wireless device by determining whether a joint feedback and type 1 HARQ-ACK codebook is configured by RRC on the wireless device. In response to determining that a scheduling CC (or scheduling cell) is configured with two CORESETPoolIndex values ​​in different CORESETs, and the scheduling CC (or scheduling cell) schedules a second CC (or a second serving cell) (i.e., a scheduled CC or a scheduled cell), while setting joint feedback and Type 1 HARQ-ACK for the wireless device, the wireless device may place (or assign to) the second CC (or a second serving cell) (i.e., a scheduled CC or a scheduled cell) in the first list (S0) in response to the second CC (or a second serving cell) (i.e., a scheduled CC or a scheduled cell) being associated with CORESETPoolIndex=0 (e.g., scheduled by a CORESET in the scheduling cell having CORESETPoolIndex=0).

[0078] In response to determining that a scheduling CC (or scheduling cell) is configured with two CORESETPoolIndex values ​​in different CORESETs, and the scheduling CC (or scheduling cell) schedules a second CC (or a second serving cell) (i.e., a scheduled CC or a scheduled cell), while setting joint feedback and Type 1 HARQ-ACK for the wireless device, the wireless device may place (or assign to) the second CC (or a second serving cell) (i.e., a scheduled CC or a scheduled cell) in a second list (S1) in response to the second CC (or a second serving cell) (i.e., a scheduled CC or a scheduled cell) being associated with CORESETPoolIndex=1 (e.g., being scheduled by a CORESET in the scheduling cell having CORESETPoolIndex=1).

[0079] In response to determining that a scheduling CC (or scheduling cell) is configured with two CORESETPoolIndex values ​​in different CORESETs, and the scheduling CC (or scheduling cell) schedules a second CC (or second serving cell) (i.e., a scheduled CC or a scheduled cell), while setting joint feedback and Type 1 HARQ-ACK for the wireless device, the wireless device may place (or assign to) both the first list (S0) and the second list (S1) in response to the second CC (or second serving cell) (i.e., the scheduled CC or the scheduled cell) being associated with both CORESETPoolIndex values ​​(e.g., the second CC (or second serving cell) (i.e., the scheduled CC or the scheduled cell) being scheduled by a CORESET in the scheduling cell having CORESETPoolIndex=0 and CORESETPoolIndex=0).

[0080] In various embodiments, in response to the assignment of a scheduled cell (or a scheduled CC) to one or both lists (e.g., S0 and / or S1), a procedure for generating HARQ-ACK may then be performed twice; once for set S0 and another time for set S1, and after concatenating two codebooks generated from the two lists (i.e., the codebook of S0 is concatenated with the codebook of S1), joint feedback is transmitted in the same PUCCH resource.

[0081] Embodiments may include determining whether a serving cell is cross-carrier scheduled by a scheduling cell (e.g., determining whether the serving cell is a scheduled cell (or scheduled CC) or not a scheduled cell (or not a scheduled CC)). Embodiments may include determining whether a scheduling cell (or scheduling CC) is associated with two CORESETPoolIndex values ​​(e.g., associated with CORESETPoolIndex value=0 and CORESETPoolIndex value=1) based on a cross-carrier scheduling configuration of a scheduled cell (or scheduled CC) in response to determining that the serving cell is cross-carrier scheduled by a scheduling cell (e.g., determining that the serving cell is a scheduled cell (or scheduled CC)). In various embodiments, a scheduled CC (or a scheduled cell) being cross-carrier scheduled by a scheduler CC (or a scheduler cell) associated with two CORESETPoolIndex values ​​(e.g., 0 and 1) may indicate that in addition to the scheduler CC (or the scheduler cell) being an MTRP CC (or an MTRP cell), the scheduled CC (or the scheduled cell) is also an MTRP CC (or an MTRP cell). In various embodiments, a scheduled CC (or a scheduled cell) being cross-carrier scheduled by a scheduler CC (or a scheduler cell) associated with two CORESETPoolIndex values ​​(e.g., 0 and 1) may indicate to a wireless device that the scheduled CC (or the scheduled cell) is handled as a serving cell of a multi-DCI mode cell in wireless device operation.

[0082] In various embodiments, handling a serving cell (e.g., a scheduled CC (or a scheduled cell)) being cross-carrier scheduled by a scheduler CC (or a scheduler cell) associated with two CORESETPoolIndex values ​​(e.g., 0 and 1) as a multi-DCI mode cell in wireless device operation may include one or more of: performing HARQ-ACK operations for the serving cell (e.g., the scheduled CC (or the scheduled cell)), performing physical downlink shared channel (PDSCH) scrambling operations for the serving cell (e.g., the scheduled CC (or the scheduled cell)), performing scrambling operations for the serving cell (e.g., the scheduled CC (or the scheduled cell)), performing scrambling operations for the serving cell (e.g., the scheduled CC (or the scheduled cell)), performing scrambling operations for the serving cell (e.g., the scheduled CC (or the scheduled cell)), performing scrambling operations for the serving cell (e.g., the scheduled CC (or the scheduled cell)), performing scrambling operations for the serving cell (e.g., the scheduled CC ( or a scheduled cell)), performs a cell-specific reference signal (CRS) rate matching operation for a serving cell (e.g., a scheduled CC (or a scheduled cell)), performs a shuffling operation for a serving cell (e.g., a scheduled CC (or a scheduled cell)), performs a PDSCH active transmission configuration indicator (TCI) state operation for a serving cell (e.g., a scheduled CC (or a scheduled cell)), performs a physical downlink control channel (PDDCH) candidate calculation operation for a serving cell (e.g., a scheduled CC (or a scheduled cell)), performs a non-overlapping control channel element (CCE) restriction calculation operation for a serving cell (e.g., a scheduled CC (or a scheduled cell)), and the like.

[0083] In various embodiments, handling a serving cell (e.g., a scheduled CC (or a scheduled cell)) being cross-carrier scheduled by a scheduler CC (or a scheduler cell) associated with two CORESETPoolIndex values ​​(e.g., 0 and 1) in wireless device operation as a multi-DCI mode cell may include: adding the serving cell to 2 HARQ-ACK codebooks. In various embodiments, handling a serving cell (e.g., a scheduled CC (or a scheduled cell)) being cross-carrier scheduled by a scheduler CC (or a scheduler cell) associated with two CORESETPoolIndex values ​​(e.g., 0 and 1) in wireless device operation as a multi-DCI mode cell may include: counting the serving cell as two serving cells to generate a type 2 HARQ-ACK codebook for the serving cell. In various embodiments, for joint HARQ-ACK for a dynamic codebook, a serving cell (e.g., a scheduled CC (or scheduled cell)) being cross-carrier scheduled by a scheduler CC (or scheduler cell) associated with two CORESETPoolIndex values ​​(e.g., 0 and 1) may be counted twice for creating a HARQ-ACK codebook, once corresponding to CORESETPoolIndex=0 and another time corresponding to CORESETPoolIndex=1. In such embodiments, a counter downlink assignment index (DAI) and a total DAI corresponding to the serving cell (e.g., the scheduled CC (or scheduled cell)) may be considered a first time for CORESETPoolIndex=0 and a second time for CORESETPoolIndex=1.

[0084] In various embodiments, handling a serving cell (e.g., a scheduled CC (or a scheduled cell)) being cross-carrier scheduled by a scheduler CC (or a scheduler cell) associated with two CORESETPoolIndex values ​​(e.g., 0 and 1) as a multi-DCI mode cell in wireless device operation may include initializing two scrambling identifiers for a PDSCH in the serving cell. In various embodiments, for PDSCH scrambling, two scrambling initialization identifiers (IDs) may be configured for a PDSCH in a serving cell (e.g., a scheduled CC (or a scheduled cell)) being cross-carrier scheduled by a scheduler CC (or a scheduler cell) associated with two CORESETPoolIndex values ​​(e.g., 0 and 1). In such embodiments, a PDSCH associated with CORESETPoolIndex=0 may use a first ID and a PDSCH associated with CORESETPoolIndex=1 may use a second ID.

[0085] In various embodiments, handling a serving cell (e.g., a scheduled CC (or a scheduled cell)) being cross-carrier scheduled by a scheduler CC (or a scheduler cell) associated with two CORESETPoolIndex values ​​(e.g., 0 and 1) as a multi-DCI mode cell in wireless device operation may include configuring two cell-specific reference signal (CRS) rate matching pattern lists in the serving cell. In various embodiments, for CRS rate matching, two CRS pattern lists may be configured in a serving cell (e.g., a scheduled CC (or a scheduled cell)) being cross-carrier scheduled by a scheduler CC (or a scheduler cell) associated with two CORESETPoolIndex values ​​(e.g., 0 and 1). In such embodiments, a PDSCH associated with CORESETPoolIndex=0 may use the list for rate matching and a PDSCH associated with CORESETPoolIndex=1 may use the second list for rate matching.

[0086] In various embodiments, handling a serving cell (e.g., a scheduled CC (or a scheduled cell)) being cross-carrier scheduled by a scheduler CC (or a scheduler cell) associated with two CORESETPoolIndex values ​​(e.g., 0 and 1) as a multi-DCI mode cell in wireless device operation may include supporting out-of-order operation for the serving cell. In various embodiments, out-of-order operation may be allowed in a serving cell (e.g., a scheduled CC (or a scheduled cell)) being cross-carrier scheduled by a scheduler CC (or a scheduler cell) associated with two CORESETPoolIndex values ​​(e.g., 0 and 1) so that PDCCH to PDSCH, PDSCH to HARQ-ACK, and / or PDCCH to PUSCH may be supported. .

[0087] In various embodiments, handling a serving cell (e.g., a scheduled CC (or a scheduled cell)) being cross-carrier scheduled by a scheduler CC (or a scheduler cell) associated with two CORESETPoolIndex values ​​(e.g., 0 and 1) as a multi-DCI mode cell in wireless device operation may include associating two active transmission configuration indicator (TCI) state lists with the serving cell. In various embodiments, for PDSCH active TCI states, the two active TCI state lists may be received via two separate medium access control (MAC)-control elements (CEs) (MAC-CEs) for a serving cell (e.g., a scheduled CC (or a scheduled cell)) being cross-carrier scheduled by a scheduler CC (or a scheduler cell) associated with two CORESETPoolIndex values ​​(e.g., 0 and 1), and the two lists may be associated with the two values ​​of CORESETPoolIndex (e.g., 0 and 1).

[0088] In various embodiments, handling a serving cell (e.g., a scheduled CC (or a scheduled cell)) being cross-carrier scheduled by a scheduler CC (or a scheduler cell) associated with two CORESETPoolIndex values ​​(e.g., 0 and 1) as a multi-DCI mode cell in wireless device operation may include including the serving cell in a serving cell list provided with two CORESETPoolIndex values ​​of 0 and 1 for calculating physical downlink control channel (PDDCH) candidates and / or non-overlapping control channel element (CCE) restrictions. In various embodiments, there may be restrictions on the number of PDCCH candidates and / or the number of non-overlapping CCEs. In various embodiments, a serving cell (e.g., a scheduled CC (or a scheduled cell)) being cross-carrier scheduled by a scheduler CC (or a scheduler cell) associated with two CORESETPoolIndex values ​​(e.g., 0 and 1) may be counted as part of a serving cell list or set provided with two CORESETPoolIndex values ​​of 0 and 1 (e.g., a second DL CC set). ) for calculating PDCCH blind decoding and / or non-overlapping CCE restrictions.

[0089] Figure 1 An example of a communication system 100 suitable for implementing various embodiments is illustrated. The communication system 100 may be a 5G NR network, or any other suitable network such as an LTE network. Figure 1 A 5G NR network is described, but later generations of networks may include the same or similar elements. Therefore, references to a 5G NR network and 5G NR network elements in the following description are for illustrative purposes and are not intended to be limiting.

[0090] The communication system 100 may include a heterogeneous network architecture including a core network 140 supporting one or more wireless networks 102a and various mobile devices (illustrated as wireless devices 120a-120e). The communication system 100 may also include several base stations (illustrated as BS 110a, BS 110b, BS 110c and BS 110d) and other network entities. A base station is an entity that communicates with a wireless device (mobile device) and may also be referred to as a NodeB, a B node, an LTE evolved B node (eNB), an access point (AP), a radio head, a transmission reception point (TRP), a new radio base station (NR BS), a 5G NodeB (NB), a next generation NodeB (gNB), and the like. Each base station may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to a coverage area of ​​a base station, or a base station subsystem serving the coverage area, or a combination thereof, depending on the context in which the term is used.

[0091] Base stations 110a-110d may provide communication coverage for a macro cell, a pico cell, a femto cell, another type of cell, or a combination thereof. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by mobile devices with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by mobile devices with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by mobile devices associated with the femto cell (e.g., mobile devices in a closed subscriber group (CSG)). A base station for a macro cell may be referred to as a macro BS. A base station for a pico cell may be referred to as a pico BS. A base station for a femto cell may be referred to as a femto BS or a home BS. In Figure 1 In the example illustrated in , base station 110a may be a macro BS for macro cell 102a, base station 110b may be a pico BS for pico cell 102b, and base station 110c may be a femto BS for femto cell 102c. Base stations 110a-110d may support one or more (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “AP,” “B node,” “5G NB,” and “cell” may be used interchangeably herein.

[0092] In some examples, the cell may not be stationary, and the geographic area of ​​the cell may move depending on the location of the mobile base station. In some examples, the base stations 110a-110d may be interconnected to each other and to one or more other base stations or network nodes (not illustrated) in the communication system 100 via various types of backhaul interfaces (such as direct physical connections, virtual networks, or combinations thereof) using any suitable transport network.

[0093] The communication system 100 may also include a relay station (e.g., relay BS 110d). A relay station is an entity that can receive a data transmission from an upstream station (e.g., a base station or a mobile device) and send the data transmission to a downstream station (e.g., a wireless device or a base station). A relay station may also be a wireless device that can relay transmissions for other mobile devices. Figure 1 In the example illustrated in FIG. 1 , a relay station 110d may communicate with the macro base station 110a and the wireless device 120d to facilitate communication between the base station 110a and the wireless device 120d. A relay station may also be referred to as a relay base station, a relay base station, a relay, or the like.

[0094] The communication system 100 may be a heterogeneous network including different types of base stations (e.g., macro base stations, pico base stations, femto base stations, relay base stations, etc.). These different types of base stations may have different transmit power levels, different coverage areas, and different impacts on interference in the communication system 100. For example, a macro base station may have a high transmit power level (e.g., 5 to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 to 2 watts).

[0095] A network controller 130 may be coupled to a set of base stations and may provide coordination and control of these base stations. The network controller 130 may communicate with the base stations via a backhaul. The base stations may also communicate with each other directly or indirectly, for example, via a wireless or wired backhaul.

[0096] Wireless devices 120a, 120b, 120c may be dispersed throughout communication system 100, and each wireless device may be stationary or mobile. Wireless devices may also be referred to as access terminals, terminals, mobile stations, mobile devices, subscriber units, stations, user equipment (UE), etc.

[0097] The macro base station 110a may communicate with the core network 140 over a wired or wireless communication link. The wireless devices 120a, 120b, 120c may communicate with the base stations 110a-110d over a wireless communication link 122.

[0098] Wired communication links may use various wired networks (e.g., Ethernet, TV cable, telephone, fiber optic, and other forms of physical network connections) that may use one or more wired communication protocols, such as Ethernet, Point-to-Point Protocol, High-Level Data Link Control (HDLC), Advanced Data Communications Control Protocol (ADCCP), and Transmission Control Protocol / Internet Protocol (TCP / IP).

[0099] The wireless communication link may include multiple carrier signals, frequencies, or frequency bands, each of which may include multiple logical channels. The wireless communication link may utilize one or more radio access technologies (RATs). Examples of RATs that may be used in the wireless communication link include: 3GPP LTE, 3G, 4G, 5G (e.g., NR), GSM, Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMAX), Time Division Multiple Access (TDMA), and other mobile phone communication technology cellular RATs. Other examples of RATs that may be used in one or more of the various wireless communication links within the communication system 100 include medium-range protocols (such as Wi-Fi, LTE-U, LTE-Direct, LAA, MuLTEfire) and relatively short-range RATs (such as ZigBee, Bluetooth, and Bluetooth Low Energy (LE)).

[0100] Some wireless networks (e.g., LTE) utilize orthogonal frequency division multiplexing (OFDM) on the downlink and single carrier frequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also often referred to as frequency modulation, frequency bins, etc. Each subcarrier can be modulated with data. In general, modulation symbols are sent in the frequency domain for OFDM and in the time domain for SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the spacing of the subcarriers can be 15kHz, and the minimum resource allocation (called a "resource block") can be 12 subcarriers (or 180kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), the nominal fast Fourier transform (FFT) size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth may be further divided into subbands. For example, a subband may cover 1.08 MHz (ie, 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, respectively.

[0101] Although the description of some embodiments may use terms and examples associated with LTE technology, some embodiments may be applicable to other wireless communication systems (such as new radio (NR) or 5G networks). NR may utilize OFDM with a cyclic prefix (CP) on the uplink (UL) and downlink (DL), and include support for half-duplex operation using time division duplex (TDD). A single component carrier bandwidth of 100 MHz may be supported. NR resource blocks may span 12 subcarriers with a subcarrier bandwidth of 75 kHz over a duration of 0.1 milliseconds (ms). Each radio frame may include 50 subframes with a length of 10 ms. Therefore, each subframe may have a length of 0.2 ms. Each subframe may indicate a link direction (i.e., DL or UL) for data transmission, and the link direction of each subframe may be dynamically switched. Each subframe may include DL / UL data and DL / UL control data. Beamforming may be supported and the beam direction may be dynamically configured. Multiple-input multiple-output (MIMO) transmission with precoding may also be supported. MIMO configurations in the DL may support up to 8 transmit antennas (with multi-layer DL transmissions of up to 8 streams) and up to 2 streams per wireless device. Multi-layer transmissions of up to 2 streams per wireless device may be supported. Aggregation of multiple cells may be supported using up to 8 serving cells. Alternatively, NR may support different air interfaces other than OFDM-based air interfaces.

[0102] Some mobile devices may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) mobile devices. MTC and eMTC mobile devices include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which can communicate with a base station, another device (e.g., a remote device), or some other entity. A wireless node may provide connectivity to or to a network (e.g., a wide area network (such as the Internet) or a cellular network), for example, via a wired or wireless communication link. Some mobile devices may be considered as Internet of Things (IoT) devices, or may be implemented as NB-IoT (narrowband Internet of Things) devices. Wireless devices 120a-120e may be included inside a housing that houses components of the device, such as a processor component, a memory component, a similar component, or a combination thereof.

[0103] In general, any number of communication systems and any number of wireless networks may be deployed in a given geographic area. Each communication system and wireless network may support a specific RAT and may operate on one or more frequencies. RAT may also be referred to as radio technology, air interface, etc. Frequency may also be referred to as carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between communication systems of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0104] In some examples, access to the air interface may be scheduled, wherein a scheduling entity (e.g., a base station) allocates resources for communication among some or all devices and equipment within a service area or cell of the scheduling entity. The scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communications, the subordinate entities utilize resources allocated by the scheduling entity.

[0105] A base station is not the only entity that can be used as a scheduling entity. In some examples, a wireless device can be used as a scheduling entity, thereby scheduling resources for one or more subordinate entities (e.g., one or more other mobile devices). In this example, the wireless device is acting as a scheduling entity, and other mobile devices utilize resources scheduled by the wireless device for wireless communication. The wireless device can be used as a scheduling entity in a peer-to-peer (P2P) network, in a mesh network, or in another type of network. In the mesh network example, mobile devices can optionally communicate directly with each other in addition to communicating with the scheduling entity.

[0106] Thus, in a wireless communication network having scheduled access to time-frequency resources and having a cellular configuration, a P2P configuration, and a mesh configuration, a scheduling entity and one or more subordinate entities may communicate using the scheduled resources.

[0107] In some embodiments, two or more mobile devices (e.g., illustrated as wireless device 120a and wireless device 120e) may communicate directly (e.g., without using base stations 110a-110d as an intermediary to communicate with each other) using one or more side link channels. For example, wireless devices 120a, 120e may communicate using peer-to-peer (P2P) communication 124, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or similar protocols), mesh networks, or similar networks, or a combination thereof. In this case, wireless device 120a may perform scheduling operations, resource selection operations, and other operations described elsewhere herein as being performed by base station 110d.

[0108] Some embodiments may be implemented on a number of single-processor and multi-processor computer systems, including system-on-a-chip (SOC) or system-in-package (SIP).

[0109] Figure 2 is a component block diagram illustrating an example computing and wireless modem system 200 suitable for implementing any of the various embodiments. The various embodiments may be implemented on a number of single-processor and multi-processor computer systems, including systems on a chip (SOC) or systems in packages (SIP).

[0110] Reference Figure 1 and Figure 2 , the illustrated example wireless device 200 (which may be a SIP in some embodiments) includes two SOCs 202, 204 coupled to a clock 206, a voltage regulator 208, and a wireless transceiver 266, which is configured to send and receive wireless communications to / from a network wireless device (such as a base station 110a) via an antenna (not shown). In some embodiments, the first SOC 202 operates as a central processing unit (CPU) of the wireless device, which executes the instructions of the software application by performing arithmetic, logic, control, and input / output (I / O) operations specified by the instructions of the software application. In some embodiments, the second SOC 204 may operate as a dedicated processing unit. For example, the second SOC 204 may operate as a dedicated 5G processing unit responsible for managing high-capacity, high-speed (e.g., 5Gbps, etc.) or ultra-high frequency short-wave length (e.g., 28GHz millimeter wave (mmWave) spectrum, etc.) communications.

[0111] The first SOC 202 may include a digital signal processor (DSP) 210, a modem processor 212, a graphics processor 214, an application processor 216, one or more coprocessors 218 (e.g., vector coprocessors) connected to one or more of these processors, memory 220, custom circuitry 222, system components and resources 224, an interconnect / bus module 226, one or more temperature sensors 230, a thermal management unit 232, and a thermal power envelope (TPE) component 234. The second SOC 204 may include a 5G modem processor 252, a power management unit 254, an interconnect / bus module 264, a plurality of millimeter wave transceivers 256, a memory 258, and various additional processors 260 (such as an application processor, a packet processor, etc.).

[0112] Each processor 210, 212, 214, 216, 218, 252, 260 may include one or more cores, and each processor / core may perform operations independently of other processors / cores. For example, the first SOC 202 may include a processor that executes a first type of operating system (e.g., FreeBSD, LINUX, OS X, etc.) and a processor that executes a second type of operating system (e.g., MICROSOFT WINDOWS 10). In addition, any or all of the processors 210, 212, 214, 216, 218, 252, 260 may be included as part of a processor cluster architecture (e.g., a synchronous processor cluster architecture, an asynchronous or heterogeneous processor cluster architecture, etc.).

[0113] The first and second SOCs 202, 204 may include various system components, resources, and custom circuitry for managing sensor data, analog-to-digital conversion, wireless data transmission, and for performing other specialized operations (such as decoding data packets and processing encoded audio and video signals for display in a web browser). For example, the system components and resources 224 of the first SOC 202 may include power amplifiers, voltage regulators, oscillators, phase-locked loops, peripheral bridges, data controllers, memory controllers, system controllers, access ports, timers, and other similar components used to support processors and software clients running on wireless devices. The system components and resources 224 or custom circuitry 222 may also include circuitry for docking with peripheral devices (such as cameras, electronic displays, wireless communication devices, external memory chips, etc.).

[0114] The first and second SOCs 202, 204 may communicate via an interconnect / bus module 250. The various processors 210, 212, 214, 216, 218 may be interconnected to one or more memory elements 220, system components and resources 224, and custom circuitry 222, and a thermal management unit 232 via an interconnect / bus module 226. Similarly, the processor 252 may be interconnected to a power management unit 254, a millimeter wave transceiver 256, a memory 258, and various additional processors 260 via an interconnect / bus module 264. The interconnect / bus modules 226, 250, 264 may include an array of reconfigurable logic gates or implement a bus architecture (e.g., CoreConnect, AMBA, etc.). Communications may be provided by an advanced interconnect such as a high-performance network on chip (NoC).

[0115] The first or second SOC 202, 204 may further include an input / output module (not illustrated) for communicating with resources external to the SOC, such as a clock 206 and a voltage regulator 208. Resources external to the SOC (eg, clock 206, voltage regulator 208) may be shared by two or more internal SOC processors / cores.

[0116] In addition to the example SIP 200 discussed above, some embodiments may be implemented in a variety of computing systems that may include a single processor, multiple processors, multi-core processors, or any combination thereof.

[0117] Figure 3 An example of a software architecture 300 is illustrated that includes a radio protocol stack for a user plane and a control plane in wireless communications between a base station 350 (e.g., base stations 110a-110d) and a wireless device 320 (e.g., any of wireless devices 120a-120e). Figure 1-3, the wireless device 320 may implement the software architecture 300 to communicate with a base station 350 of a communication system (e.g., 100). In various embodiments, the layers in the software architecture 300 may form a logical connection with the corresponding layers in the software of the base station 350. The software architecture 300 may be distributed between one or more processors (e.g., processors 212, 214, 216, 218, 252, 260). Although explained with respect to one radio protocol stack, in a multi-SIM (subscriber identity module) wireless device, the software architecture 300 may include multiple protocol stacks, each of which may be associated with a different SIM (e.g., in a dual SIM wireless communication device, two protocol stacks are associated with two SIMs, respectively). Although described below with reference to LTE communication layers, the software architecture 300 may support any of a variety of standards and protocols for wireless communication, or may include additional protocol stacks that support any of a variety of standards and protocols for wireless communication.

[0118] Software architecture 300 may include a non-access stratum (NAS) 302 and an access stratum (AS) 304. NAS 302 may include functions and protocols to support packet filtering, security management, mobility control, session management, and traffic and signaling between SIM(s) of a wireless device (e.g., SIM(s) 204) and its core network. AS 304 may include functions and protocols to support communications between SIM(s) (e.g., SIM(s) 204) and entities (e.g., base stations) of a supported access network. Specifically, AS 304 may include at least three layers (Layer 1, Layer 2, and Layer 3), each of which may include various sublayers.

[0119] In the user plane and control plane, layer 1 (L1) of AS 304 may be a physical layer (PHY) 306, which may oversee functions that enable transmission or reception on an air interface. Examples of such physical layer 306 functions may include cyclic redundancy check (CRC) attachment, decoding blocks, scrambling and descrambling, modulation and demodulation, signal measurement, MIMO, etc. The physical layer may include various logical channels, including PDCCH and PDSCH.

[0120] In the user plane and the control plane, layer 2 (L2) of AS 304 may be responsible for the link between wireless device 320 and base station 350 on physical layer 306. In some embodiments, layer 2 may include a medium access control (MAC) sublayer 308, a radio link control (RLC) sublayer 310, and a packet data convergence protocol (PDCP) 312 sublayer, each of which forms a logical connection terminated at base station 350.

[0121] In the control plane, layer 3 (L3) of AS 304 may include a radio resource control (RRC) sublayer 3. Although not shown, software architecture 300 may include additional layer 3 sublayers, as well as various upper layers above layer 3. In some embodiments, RRC sublayer 313 may provide functionality including broadcasting system information, paging, and establishing and releasing RRC signaling connections between wireless device 320 and base station 350.

[0122] In some embodiments, the PDCP sublayer 312 may provide uplink functions including multiplexing between different radio bearers and logical channels, sequence number addition, handover data handling, integrity protection, encryption, and header compression. In the downlink, the PDCP sublayer 312 may provide functions including in-sequence delivery of data packets, duplicate data packet detection, integrity verification, cipher decoding, and header decompression.

[0123] In the uplink, the RLC sublayer 310 may provide segmentation and concatenation of upper layer data packets, retransmission of lost data packets, and automatic repeat request (ARQ). In the downlink, while the RLC sublayer 310 functions may include reordering of data packets to compensate for out-of-order reception, reassembly of upper layer data packets, and ARQ.

[0124] In the uplink, the MAC sublayer 308 may provide functions including multiplexing between logical and transport channels, random access procedures, logical channel priorities, and hybrid ARQ (HARQ) operations. In the downlink, MAC layer functions may include channel mapping within a cell, demultiplexing, discontinuous reception (DRX), and HARQ operations.

[0125] While the software architecture 300 may provide functionality for transferring data over a physical medium, the software architecture 300 may further include at least one host layer 314 that provides data transfer services to various applications in the wireless device 320. In some embodiments, the application-specific functionality provided by the at least one host layer 314 may provide an interface between the software architecture and a general-purpose processor, such as the application processor 216.

[0126] In some other embodiments, the software architecture 300 may include one or more higher logical layers (e.g., transport, session, presentation, application, etc.) that provide host layer functionality. For example, in some embodiments, the software architecture 300 may include a network layer (e.g., an Internet Protocol (IP) layer) where the logical connection terminates at a packet data network (PDN) gateway (PGW). In some embodiments, the software architecture 300 may include an application layer where the logical connection terminates at another device (e.g., an end-user device, a server, etc.). In some embodiments, the software architecture 300 may further include a hardware interface 316 between the physical layer 306 and communication hardware (e.g., one or more RF transceivers) in the AS 304.

[0127] Figure 4 4 is a component block diagram illustrating a communication system 400 configured for wireless communication according to various embodiments. Figure 1-4 , the communication system 400 may include a wireless device 120 (e.g., wireless devices 120a-e, 200, 320), and one or more base stations 110 (e.g., base stations 110a-e, 350) forming a wireless communication network 450 (e.g., communication system 100), which may provide connectivity to external resources 434. The external resources 434 may include information sources external to the system 400, external entities participating with the system 400, and / or other resources.

[0128] The wireless device 120 may include a wireless transceiver 266 and a processor 438 configured by machine-readable instructions 406 stored in an electronic memory 436. The machine-readable instructions 406 may include one or more instruction modules. The instruction modules may include computer program modules. The instruction modules may include one or more of a cell determination module 408, a DCI reception module 410, a DCI determination module 412, a CORESETPoolIndex module 414, an association determination module 416, an indication determination module 418, a scheduler cell determination module 420, a data communication operation module 422, and / or other instruction modules.

[0129] The cell determination module 408 may be configured to determine whether the scheduling cell or the scheduled cell is configured to perform MTRP communication based on multiple DCIs. The cell determination module 408 may be configured to determine whether the scheduling cell is configured to perform cross-carrier scheduling for the scheduled cell. The cell determination module 408 may be configured to determine whether the scheduling cell is configured to perform cross-carrier scheduling for the scheduled cell based on the RRC configuration and / or DCI of the scheduling cell. The cell determination module 408 may be configured to determine whether at least one serving cell is configured with two control resource sets (CORESET) pool index (CORESETPoolIndex) values ​​and whether a joint type 1 hybrid automatic repeat request (HARQ) acknowledgment (HARQ-ACK) is set for the wireless device. The cell determination module 408 may be configured to determine whether the serving cell is cross-carrier scheduled by the scheduling cell.

[0130] The DCI receiving module 410 may be configured to receive downlink control information from a scheduling cell. For example, the DCI may be received in a PDCCH or extracted from a PDCCH.

[0131] The DCI determination module 412 may be configured to determine a control resource set (CORESET) pool index (CORESETPoolIndex) value of the scheduling cell. The DCI determination module 412 may be configured to determine a control resource set (CORESET) pool index (CORESETPoolIndex) value of the scheduling cell based on the RRC configuration and / or DCI of the scheduling cell. The DCI determination module 412 may be configured to determine the CORESETPoolIndex value of the scheduling cell as 0 in response to the CORESETPoolIndex value of the scheduling cell being indicated as 0 in the RRC configuration and / or DCI of the scheduling cell or the CORESETPoolIndex value being not configured in the RRC configuration and / or DCI of the scheduling cell. The DCI determination module 412 may be configured to determine the CORESETPoolIndex value of the scheduling cell as 0 in response to the CORESETPoolIndex value of the scheduling cell being indicated as 1 in the RRC configuration and / or DCI of the scheduling cell. The DCI determination module 412 may be configured to, in response to the CORESETPoolIndex value configured for the CORESET in the scheduling cell being indicated as 0 or the CORESETPoolIndex value not being configured for the CORESET in the scheduling cell, determine the CORESETPoolIndex value of the scheduling cell as 0. The DCI determination module 412 may be configured to, in response to the CORESETPoolIndex value configured for the CORESET in the scheduling cell being indicated as 1, determine the CORESETPoolIndex value of the scheduling cell as 1.

[0132] The CORESETPoolIndex module 414 may be configured to associate the scheduled cell with the determined CORESETPoolIndex value of the scheduler cell. The CORESETPoolIndex module 414 may be configured to assign the serving cell scheduled by the scheduler cell across carriers to the serving cell set for generating the type 1 HARQ-ACK codebook based on the determined CORESETPoolIndex value of the scheduler cell. The CORESETPoolIndex module 414 may be configured to assign the serving cell scheduled by the scheduler cell across carriers to the first serving cell set for generating the first type 1 HARQ-ACK codebook based on the determined CORESETPoolIndex value of the scheduler cell being 0. The CORESETPoolIndex module 414 may be configured to assign the serving cell scheduled by the scheduler cell across carriers to the second serving cell set for generating the second type 1 HARQ-ACK codebook based on the determined CORESETPoolIndex value of the scheduler cell being 1. The CORESETPoolIndex module 414 may be configured to assign a CORESETPoolIndex value of 0 to the serving cell in response to determining that the serving cell is cross-carrier scheduled by the scheduling cell. The CORESETPoolIndex module 414 may be configured to assign the determined CORESETPoolIndex value of the scheduling cell to the serving cell. In various embodiments, the determined CORESETPoolIndex value of the scheduling cell may be a value of 0 or a value of 1. The CORESETPoolIndex module 414 may be configured to assign a CORESETPoolIndex value of 0 to the serving cell in response to determining that the associated CORESETPoolIndex value is 0. The CORESETPoolIndex module 414 may be configured to assign a CORESETPoolIndex value of 1 to the serving cell in response to determining that the associated CORESETPoolIndex value is 1. The CORESETPoolIndex module 414 may be configured to assign both a CORESETPoolIndex value of 0 and a CORESETPoolIndex value of 1 to the serving cell in response to determining that the associated CORESETPoolIndex value is 2.The CORESETPoolIndex module 414 may be configured to assign serving cells scheduled by the scheduler cell across carriers to a first set of serving cells for generating a type 1 HARQ-ACK codebook in response to determining that at least one serving cell is configured with two CORESETPoolIndex values ​​and a joint type 1 HARQ-ACK is set for the wireless device, wherein the first set of serving cells is a serving cell associated with a CORESETPoolIndex value of 0. The CORESETPoolIndex module 414 may be configured to assign serving cells scheduled by the scheduler cell across carriers to one or more sets of serving cells for generating one or more type 1 HARQ-ACK codebooks based on the determined one or more CORESETPoolIndex values ​​of the scheduler cell in response to determining that at least one serving cell is configured with two CORESETPoolIndex values ​​and a joint type 1 HARQ-ACK is set for the wireless device. The CORESETPoolIndex module 414 may be configured to assign the serving cells scheduled by the scheduler cell across carriers to a first set of serving cells for generating a first type 1 HARQ-ACK codebook based on a determined single CORESETPoolIndex value of 0. The CORESETPoolIndex module 414 may be configured to assign the serving cells scheduled by the scheduler cell across carriers to a second set of serving cells for generating a second type 1 HARQ-ACK codebook based on a determined single CORESETPoolIndex value of 1. The CORESETPoolIndex module 414 may be configured to assign the serving cells scheduled by the scheduler cell across carriers to a first set of serving cells for generating a first type 1 HARQ-ACK codebook based on a determined associated CORESETPoolIndex value of 0. The CORESETPoolIndex module 414 may be configured to assign the serving cells scheduled by the scheduler cell across carriers to the second serving cell set for generating the second type 1 HARQ-ACK codebook based on the determined associated CORESETPoolIndex value of 1. The CORESETPoolIndex module 414 may be configured to assign the serving cells scheduled by the scheduler cell across carriers to both the first serving cell set for generating the first type 1 HARQ-ACK codebook and the second serving cell set for generating the second type 1 HARQ-ACK codebook based on the determined associated CORESETPoolIndex value of 2.

[0133] The association determination module 416 may be configured to determine the association of the DCI and the index based on a field in the payload of the DCI. The association determination module 416 may be configured to determine one or more control resource set (CORESET) pool index (CORESETPoolIndex) values ​​of the scheduling cell based on the cross-carrier scheduling configuration of the serving cell in response to determining that the serving cell is cross-carrier scheduled by the scheduling cell. The association determination module 416 may be configured to determine the CORESETPoolIndex value of the scheduling cell indicated in the cross-carrier scheduling configuration. The association determination module 416 may be configured to determine the associated CORESETPoolIndex value of the scheduling cell indicated in the cross-carrier scheduling configuration. The association determination module 416 may be configured to determine one or more CORESETPoolIndex values ​​of the scheduling cell based on the cross-carrier scheduling configuration of the serving cell scheduled by the scheduling cell across carriers in response to determining that at least one serving cell is configured with two CORESETPoolIndex values ​​and a joint type 1 HARQ-ACK is set for the wireless device.

[0134] The indication determination module 418 may be configured to determine whether the scheduling cell has an associated CORESETPoolIndex value of 0, 1, or 2 in the cross-carrier scheduling configuration of the serving cell.

[0135] The dispatcher cell determination module 420 may be configured to determine whether the dispatcher cell is configured with two or more CORESET groups. The dispatcher cell determination module 420 may be configured to determine whether the dispatcher cell is configured to perform multi-DCI based MTRP operation. In some embodiments, the associated CORESETPoolIndex value may correspond to the CORESETPoolIndex value of the dispatcher cell. In some embodiments, the associated CORESETPoolIndex value may be 0 or 1. In some embodiments, the associated CORESETPoolIndex value may indicate that the dispatcher cell has both a CORESETPoolIndex value of 0 and a CORESETPoolIndex value of 1. In some embodiments, the associated CORESETPoolIndex value may be 2.

[0136] The data communication operation module 422 may be configured to perform data communication operations according to the CORESETPoolIndex and / or the associated CORESETPoolIndex. The data communication operation module 422 may be configured to handle the serving cell as a multi-DCI mode cell in the wireless device operation in response to determining that the scheduling party cell is associated with two CORESETPoolIndex values ​​based on the cross-carrier scheduling configuration of the serving cell. The data communication operation module 422 may be configured to handle the serving cell as a multi-DCI mode cell in the wireless device operation by adding the serving cell to two HARQ-ACK codebooks. The data communication operation module 422 may be configured to handle the serving cell as a multi-DCI mode cell in the wireless device operation by initializing two scrambling identifiers of a physical downlink shared channel (PDSCH) in the serving cell. The data communication operation module 422 may be configured to handle the serving cell as a multi-DCI mode cell in the wireless device operation by configuring two cell-specific reference signal (CRS) rate matching pattern lists in the serving cell. The data communications operation module 422 may be configured to handle the serving cell as a multi-DCI mode cell in the wireless device operation by supporting out-of-order operation of the serving cell. The data communications operation module 422 may be configured to handle the serving cell as a multi-DCI mode cell in the wireless device operation by associating two active transmission configuration indicator (TCI) state lists with the serving cell. The data communications operation module 422 may be configured to handle the serving cell as a multi-DCI mode cell in the wireless device operation by including the serving cell in a serving cell list provided with both CORESETPoolIndex values ​​0 and 1 for calculating physical downlink control channel (PDDCH) candidates and / or non-overlapping control channel element (CCE) restrictions.

[0137] Figure 5A and 5B Two examples of cross-carrier scheduling are explained. Figure 1-5B , Figure 5A The first case is explained in , where CC1 is the scheduling cell of CC3 (the scheduled cell of CC1 ), and CC2 is the scheduling cell of CC4 (the scheduled cell of CC2 ). Figure 5AIt is explained that although CC1 may be associated with CORESETPoolIndex=0, when the scheduled cell (CC3) of CC1 is cross-carrier scheduled, CC3 may not have a CORESET configured for it. Similarly, although CC2 may be associated with CORESETPoolIndex=1, when the scheduled cell (CC4) of CC2 is cross-carrier scheduled, CC4 may not have a CORESET configured for it. Figure 5A , illustrated as a multi-DCI MTRP cell with two CORESETPoolIndex values ​​configured, CORESETPoolIndex=0 is associated with TRP0 and CORESETPoolIndex=1 is associated with TRP1. CC0 is Figure 5A Not explained as a scheduling cell.

[0138] Figure 5B The second case is illustrated in , where CC0 is a multi-DCI MTRP cell with two CORESETPoolIndex values ​​configured, where CORESETPoolIndex=0 is associated with TRP0 and CORESETPoolIndex=1 is associated with TRP1, and CC0 is a scheduler cell of another CC1 (ie, CC1 is a scheduled cell). Figure 5B It is explained that although CC0 may be associated with both CORESETPoolIndex=1 and CORESETPoolIndex=2, when the scheduled party cell (CC1) of CC0 is cross-carrier scheduled, CC1 may not have a CORESET configured therefor.

[0139] Figure 5C is a process flow diagram illustrating a method 500 for managing cross-carrier scheduling that may be performed by a processor of a wireless device according to various embodiments. Figure 1-5C The method 500 may be implemented by a processor (e.g., 212, 216, 252, or 260) of a wireless device (e.g., wireless devices 120a-120e, 120, 200, 320). Figure 1-5C , the means for performing each operation of the method 500 may be one or more processors of a wireless device (eg, wireless devices 120a-120e, 120, 200, 320), such as one or more of the processors 212, 216, 252, or 260.

[0140] In block 502, the processor may perform operations including receiving DCI from a scheduling cell that schedules communications on a scheduled cell. In some embodiments, receiving the DCI may include receiving the DCI on a PDCCH. In various embodiments, the DCI may be received after receiving one or more RRC messages indicating that at least one serving cell is configured with two CORESETPoolIndex values ​​and indicating that at least one serving cell that is not configured with a CORESETPoolIndex value is cross-carrier scheduled.

[0141] In block 504, the processor may perform operations including transmitting the communication or monitoring the communication on the scheduled cell based on the DCI. For example, the communication may be transmitted when the communication is an uplink communication, and may be monitored when the communication is a downlink communication.

[0142] In block 506, the processor may perform operations including performing a type 1 HARQ-ACK operation for the communication based on one or more CORESET pools configured for the scheduled party cell. For example, the processor may perform a type 1 HARQ-ACK operation for a first serving cell set associated with a first CORESETPoolIndex value of two CORESETPoolIndex values ​​to generate a first codebook and perform a type 1 HARQ-ACK operation for a second serving cell set associated with a second CORESETPoolIndex value of the two CORESETPoolIndex values ​​to generate a second codebook. In various embodiments, performing the type 1 HARQ-ACK operation may include transmitting joint feedback for the type 1 HARQ-ACK operation on the same PUCCH resource after concatenating the first codebook and the second codebook.

[0143] Figure 5D is a process flow diagram illustrating a method 550 for managing cross-carrier scheduling that may be performed by a processor of a network computing device according to various embodiments. Figure 1-5D , method 550 may be implemented by a processor of a network computing device (e.g., base stations 110a-e, 110, 350). In some embodiments, the operations of method 550 may be combined with the operations of method 500 ( Figure 5C ) operation to execute. Figure 1-5D , the means for performing each operation of the method 550 may be one or more processors of a network computing device (eg, base stations 110a - e , 110 , 350 ).

[0144] In block 552, the processor may perform operations including transmitting a cross-carrier scheduling configuration of a scheduled cell to a wireless device. In some embodiments, the cross-carrier scheduling configuration may indicate an associated CORESETPoolIndex value of a scheduling cell configured to schedule the scheduled cell. In some embodiments, the cross-carrier scheduling configuration may be sent to the wireless device as an RRC message. As an example, the processor may generate a cross-carrier scheduling configuration of the scheduled cell based on a scheduling setting set by a network operator for the cell. In various embodiments, the cross-carrier scheduling configuration may indicate that at least one serving cell is configured with two CORESETPoolIndex and that the CORESETPoolIndex value of the scheduled cell is not configured.

[0145] In block 554, the processor may perform operations including transmitting DCI for the scheduled cell from the scheduling cell to the wireless device. In some embodiments, transmitting the DCI for the scheduled cell from the scheduling cell to the wireless device may include transmitting the DCI to the wireless device on the PDCCH. As an example, the transmitted DCI may be DCI received by the wireless device, as described with reference to method 500 ( Figure 5C ) as discussed in box 502 of ).

[0146] In block 556, the processor may perform operations including receiving joint feedback from the wireless device for type 1 HARQ-ACK operations for communications associated with the scheduled party cell. In some embodiments, the joint feedback from the wireless device may be received from the wireless device on a PUCCH resource. As an example, the joint feedback may be joint feedback transmitted by the wireless device, as described with reference to method 500 ( Figure 5C ) as discussed in box 506 of ).

[0147] Fig. 6A 6 is a process flow diagram illustrating a method 600 for managing cross-carrier scheduling that may be performed by a processor of a wireless device according to various embodiments. Figure 1-6A , method 600 may be implemented by a processor (e.g., 212, 216, 252, or 260) of a wireless device (e.g., wireless devices 120a-120e, 120, 200, 320). In various embodiments, the operations of method 600 may be combined with method 500 ( Figure 5C ) and / or 550( Figure 5D ) is performed. As an example, the operation of method 600 may be the operation of method 500 ( Figure 5C ) to support Type 1 HARQ-ACK operations. Figure 1-6A, the means for performing each operation of method 600 may be one or more processors of a wireless device (eg, wireless devices 120a-120e, 120, 200, 320), such as one or more of processors 212, 216, 252, or 260, etc.

[0148] In block 601, the processor may perform operations including receiving DCI of a scheduling cell. In various embodiments, the DCI may be transmitted by the scheduling cell to the wireless device. The DCI may indicate whether the cell is self-scheduling and / or whether the cell is scheduling other cells or being scheduled by other cells.

[0149] In determination block 602, the processor may perform operations including determining whether the scheduling cell is configured to perform cross-carrier scheduling for the scheduled cell. The processor may perform operations including determining whether the scheduling cell is configured to perform cross-carrier scheduling for the scheduled cell based on the RRC configuration and / or DCI of the scheduling cell. For example, the processor may parse the cross-carrier scheduling configuration element (e.g., CrossCarrierSchedulingConfig, etc.) in the RRC configuration and / or the cross-carrier scheduling configuration element (e.g., CIF) in the DCI to determine whether the scheduling cell is configured to perform cross-carrier scheduling for the scheduled cell. As a specific example, the determination of whether the scheduling cell is configured to perform cross-carrier scheduling for the scheduled cell may be based on the RRC configuration (e.g., CrossCarrierSchedulingConfig). The DCI then indicates (e.g., via the CIF field) whether the DCI is for the scheduled cell (or for another cell).

[0150] In response to determining that the scheduling cell is not configured to perform cross-carrier scheduling for the scheduled cell (ie, determination block 602 = "No"), the processor may perform the operations of block 601 to receive DCI of the scheduling cell.

[0151] In response to determining that the scheduling cell is configured to perform cross-carrier scheduling for the scheduled cell (i.e., determination block 602 = "Yes"), the processor may perform operations including determining a CORESETPoolIndex value for the scheduling cell in block 604. In some embodiments, determining the CORESETPoolIndex value for the scheduling cell may be based on an RRC configuration and / or DCI of the scheduling cell. In some embodiments, determining the CORESETPoolIndex value for the scheduling cell may include determining the CORESETPoolIndex value for the scheduling cell to be 0 in response to the CORESETPoolIndex value for the scheduling cell being indicated as 0 in the RRC configuration and / or DCI of the scheduling cell or the CORESETPoolIndex value not being configured in the DCI of the scheduling cell. In some embodiments, determining the CORESETPoolIndex value for the scheduling cell may include determining the CORESETPoolIndex value for the scheduling cell as 1 in response to the CORESETPoolIndex value for the scheduling cell being indicated as 1 in the RRC configuration and / or DCI of the scheduling cell. In some embodiments, determining the CORESETPoolIndex value for the scheduling cell may include determining the CORESETPoolIndex value for the scheduling cell as 0 in response to the CORESETPoolIndex value for the CORESET configuration in the scheduling cell being indicated as 0 or there being no CORESETPoolIndex value for the CORESET configuration in the scheduling cell. In some embodiments, determining the CORESETPoolIndex value for the scheduling cell may include determining the CORESETPoolIndex value for the scheduling cell as 1 in response to the CORESETPoolIndex value for the CORESET configuration in the scheduling cell being indicated as 1.

[0152] In block 606, the processor may perform operations including associating the scheduled cell with the determined CORESETPoolIndex value of the scheduling cell. In this manner, the scheduled cell may be associated with the same CORESETPoolIndex value as its corresponding scheduling cell.

[0153] Figure 6B 6 is a process flow diagram illustrating a method 610 for managing cross-carrier scheduling that may be performed by a processor of a wireless device according to various embodiments. Figure 1-6B, method 610 may be implemented by a processor (e.g., 212, 216, 252, or 260) of a wireless device (e.g., wireless devices 120a-120e, 120, 200, 320). In various embodiments, the operations of method 610 may be combined with method 500 ( Figure 5C )、Method 550( Figure 5D ) and / or method 600( Fig. 6A ) operation. As an example, the operation of method 610 may be performed in method 500 ( Figure 5C ) to support Type 1 HARQ-ACK operations. Figure 1-6B , the means for performing each operation of method 610 may be one or more processors of a wireless device (eg, wireless devices 120a-120e, 120, 200, 320), such as one or more of processors 212, 216, 252, or 260, etc.

[0154] In determination block 612, the processor may perform operations including determining whether at least one serving cell is configured with two CORESETPoolIndex values ​​and whether a joint Type 1 HARQ-ACK is set for the wireless device.

[0155] In response to determining that no serving cell is configured with two CORESETPoolIndex values ​​or that a joint type 1 HARQ-ACK is not set for the wireless device (i.e., determination block 612 = "No"), the processor may continue to perform operations including determining in determination block 612 whether at least one serving cell is configured with two CORESETPoolIndex values ​​and whether a joint type 1 HARQ-ACK is set for the wireless device.

[0156] In response to determining that at least one serving cell is configured with two CORESETPoolIndex values ​​and a joint type 1 HARQ-ACK is set for the wireless device (i.e., determination block 612 = "Yes"), the processor may perform operations including determining the CORESETPoolIndex value of the scheduling cell in block 604, as described with reference to method 600 ( Fig. 6A In some embodiments, the operations of block 604 may be performed for each serving cell scheduled across carriers by a scheduling cell.

[0157] In block 614, the processor may perform operations including assigning serving cells scheduled by the scheduler cell across carriers to a serving cell set for generating a type 1 HARQ-ACK codebook based on the determined CORESETPoolIndex value of the scheduler cell. In some embodiments, assigning serving cells scheduled by the scheduler cell across carriers to a serving cell set for generating a type 1 HARQ-ACK codebook based on the determined CORESETPoolIndex value of the scheduler cell may include assigning serving cells scheduled by the scheduler cell across carriers to a first serving cell set (e.g., S0) for generating a first type 1 HARQ-ACK codebook based on the determined CORESETPoolIndex value of the scheduler cell being 0, and assigning serving cells scheduled by the scheduler cell across carriers to a second serving cell set (e.g., S1) for generating a second type 1 HARQ-ACK codebook based on the determined CORESETPoolIndex value of the scheduler cell being 1.

[0158] Figure 7 An example of cross-carrier scheduling supporting joint semi-static HARQ-ACK according to various embodiments is illustrated. Figure 1-7 , Figure 7 Explain the method 610 ( Figure 6B ) operation example joint semi-static HARQ-ACK operation. For example, according to method 610 ( Figure 6B ), CC3 may be determined to be scheduled by CC1, and since the CORESETPoolIndex value of CC1 is 0, CC3 may be added to list S0 for HARQ-ACK. Similarly, CC4 may be determined to be scheduled by CC2, and since the CORESETPoolIndex value of CC2 is 1, CC4 may be added to list S1 for HARQ-ACK.

[0159] Fig. 8A 8 is a process flow diagram illustrating a method 800 for managing cross-carrier scheduling that may be performed by a processor of a wireless device according to various embodiments. Figure 1-8A , method 800 may be implemented by a processor (e.g., 212, 216, 252, or 260) of a wireless device (e.g., wireless devices 120a-120e, 120, 200, 320). In various embodiments, the operations of method 800 may be combined with method 500 ( Figure 5C )、Method 550( Figure 5D ), Method 600( Fig. 6A ) and / or method 610( Figure 6B) operation. As an example, the operation of method 800 may be performed in method 500 ( Figure 5C ) to support Type 1 HARQ-ACK operations. Figure 1-8A , the means for performing each operation of method 800 may be one or more processors of a wireless device (eg, wireless devices 120a-120e, 120, 200, 320), such as one or more of processors 212, 216, 252, or 260, etc.

[0160] In determination block 802, the processor may perform operations including determining whether the serving cell is cross-carrier scheduled by the scheduling cell. For example, the processor may parse a cross-carrier scheduling configuration element in the DCI and / or a cross-carrier scheduling configuration element received via the RRC to determine whether the serving cell is cross-carrier scheduled by the scheduling cell. For example, a value in a CIF and / or an associated CORESETPoolIndexValue element in the cross-carrier scheduling configuration may indicate whether the serving cell is cross-carrier scheduled by the scheduling cell.

[0161] In response to determining that the serving cell is not cross-carrier scheduled by the scheduling cell (ie, determination block 802 = "No"), the processor may continue to perform operations including determining at determination block 802 whether the serving cell is cross-carrier scheduled by the scheduling cell.

[0162] In response to determining that the serving cell is cross-carrier scheduled by the scheduling cell (i.e., determination block 802 = "Yes"), the processor may perform operations including assigning a CORESETPoolIndex value of 0 to the serving cell in response to determining that the serving cell is cross-carrier scheduled by the scheduling cell at block 804.

[0163] Figure 8B 8 is a process flow diagram illustrating a method 810 for managing cross-carrier scheduling that may be performed by a processor of a wireless device in accordance with various embodiments. Figure 1-8B , method 810 may be implemented by a processor (e.g., 212, 216, 252, or 260) of a wireless device (e.g., wireless devices 120a-120e, 120, 200, 320). In various embodiments, the operations of method 810 may be combined with method 500 ( Figure 5C )、Method 550( Figure 5D ), Method 600( Fig. 6A ) and / or method 610( Figure 6B ) operation. As an example, the operation of method 810 may be performed in method 500 ( Figure 5C ) to support Type 1 HARQ-ACK operations. Figure 1-8B , the means for performing each operation of method 810 may be one or more processors of a wireless device (eg, wireless devices 120a-120e, 120, 200, 320), such as one or more of processors 212, 216, 252, or 260, etc.

[0164] In block 801, the processor may perform operations including receiving one or more RRC messages including one or more cross-carrier scheduling configurations. In some embodiments, the cross-carrier scheduling configuration element may indicate whether the serving cell is cross-carrier scheduled by the scheduling cell. For example, the value in the CIF and / or the associated CORESETPoolIndexValue element in the cross-carrier scheduling configuration may indicate whether the serving cell is cross-carrier scheduled by the scheduling cell. In various embodiments, one or more RRC messages including one or more cross-carrier scheduling configurations may be received from a network computing device.

[0165] In determination block 802, the processor may perform operations including determining whether the serving cell is cross-carrier scheduled by the scheduling cell, as described with reference to method 800 ( Fig. 8A ) discussed.

[0166] In response to determining that the serving cell is not cross-carrier scheduled by the scheduling cell (i.e., determination block 802 = "No"), the processor may continue to perform operations, including determining whether the serving cell is cross-carrier scheduled by the scheduling cell at determination block 802, as described with reference to method 800 ( Fig. 8A ) discussed.

[0167] In response to determining that the serving cell is cross-carrier scheduled by the scheduling cell (i.e., determination block 802 = "Yes"), the processor may perform operations including determining one or more CORESETPoolIndex values ​​for the scheduling cell based on the cross-carrier scheduling configuration of the serving cell in block 812. As examples, the processor may determine whether the CORESETPoolIndex value is 0, the processor may determine whether the CORESETPoolIndex value is 1, and / or the processor may determine whether the CORESETPoolIndex value is both 0 and 1.

[0168] Figure 8C is a process flow diagram illustrating a method 820 for managing cross-carrier scheduling that may be performed by a processor of a wireless device according to various embodiments. Figure 1-8C, method 820 may be implemented by a processor (e.g., 212, 216, 252, or 260) of a wireless device (e.g., wireless devices 120a-120e, 120, 200, 320). In various embodiments, the operations of method 820 may be combined with method 500 ( Figure 5C )、Method 550( Figure 5D ), Method 600( Fig. 6A ), method 610( Figure 6B ) and / or method 810( Figure 8B As a specific example, method 820 may be performed in response to determining that the serving cell is scheduled by the scheduled cell across carriers (ie, determining block 802 ( Figure 8B )=“Yes”) to determine one or more CORESETPoolIndex values ​​of the scheduling party cell based on the cross-carrier scheduling configuration of the serving cell. As another example, the operation of method 820 can be performed in method 500 ( Figure 5C ) to support Type 1 HARQ-ACK operations. Figure 1-8C , the means for performing each operation of method 820 may be one or more processors of a wireless device (eg, wireless devices 120a-120e, 120, 200, 320), such as one or more of processors 212, 216, 252, or 260, etc.

[0169] In block 822, the processor may perform operations including determining a CORESETPoolIndex value for a scheduling cell indicated in a cross-carrier scheduling configuration. In some embodiments, the determined CORESETPoolIndex value for the scheduling cell may be a value of 0 or a value of 1.

[0170] In block 824, the processor may perform operations including assigning the determined CORESETPoolIndex value of the scheduler cell to the serving cell.

[0171] Fig.8D 8 is a process flow diagram illustrating a method 830 for managing cross-carrier scheduling that may be performed by a processor of a wireless device according to various embodiments. Figure 1-8D , method 830 may be implemented by a processor (e.g., 212, 216, 252, or 260) of a wireless device (e.g., wireless devices 120a-120e, 120, 200, 320). In various embodiments, the operations of method 830 may be combined with method 500 ( Figure 5C )、Method 550( Figure 5D ), Method 600( Fig. 6A ), method 610( Figure 6B ) and / or method 810( Figure 8B As a specific example, method 830 may be performed in response to determining that the serving cell is scheduled by the scheduled cell across carriers (ie, determining block 802 ( Figure 8B )=“Yes”) to determine one or more CORESETPoolIndex values ​​of the scheduling party cell based on the cross-carrier scheduling configuration of the serving cell. As another example, the operation of method 830 can be performed in method 500 ( Figure 5C ) to support Type 1 HARQ-ACK operations. Figure 1-8D , the means for performing each operation of method 830 may be one or more processors of a wireless device (eg, wireless devices 120a-120e, 120, 200, 320), such as one or more of processors 212, 216, 252, or 260, etc.

[0172] In block 832, the processor may perform operations including determining an associated CORESETPoolIndex value for a scheduling party cell indicated in a cross-carrier scheduling configuration. For example, the processor may determine whether the associated CORESETPoolIndex value is 0, the processor may determine whether the associated CORESETPoolIndex value is 1, and / or the processor may determine whether the associated CORESETPoolIndex value is 2.

[0173] In block 834 , the processor may perform operations including assigning a CORESETPoolIndex value of 0 to the serving cell in response to determining that the associated CORESETPoolIndex value is 0.

[0174] In block 836 , the processor may perform operations including assigning a CORESETPoolIndex value of 1 to the serving cell in response to determining that the associated CORESETPoolIndex value is 1.

[0175] In block 838 , the processor may perform operations including assigning both a CORESETPoolIndex value of 0 and a CORESETPoolIndex value of 1 to the serving cell in response to determining that the associated CORESETPoolIndex value is 2.

[0176] Fig. 9A 9 is a process flow diagram illustrating a method 900 for managing cross-carrier scheduling that may be performed by a processor of a network computing device according to various embodiments. Figure 1-9A, method 900 may be implemented by a processor of a network computing device (e.g., base stations 110a-e, 110, 350). In various embodiments, the operations of method 900 may be combined with method 500 ( Figure 5B )、Method 550( Figure 5C ), Method 600( Fig. 6A ), method 610( Figure 6B ), Method 800( Fig. 8A ), method 810( Figure 8B ), method 820( Figure 8C ) and / or method 830( Fig.8D ) operation. As an example, the operation of method 900 may be performed in method 550 ( Figure 5D ) to implement the transmission of cross-carrier scheduling configuration. Figure 1-9A , the means for performing each operation of the method 900 may be one or more processors of a network computing device (eg, base stations 110a - e , 110 , 350 ).

[0177] In block 902, the processor may perform operations including generating a cross-carrier scheduling configuration for a scheduled cell, the cross-carrier scheduling configuration indicating an associated CORESETPoolIndex value of a scheduling cell configured to schedule the scheduled cell. For example, the processor may generate a cross-carrier scheduling configuration for the scheduled cell based on a scheduling setting set by a network operator for the cell.

[0178] In block 904, the processor may perform operations including sending the cross-carrier scheduling configuration to the wireless device. In various embodiments, sending the cross-carrier scheduling configuration to the wireless device may include sending the cross-carrier scheduling configuration in an RRC message to the wireless device.

[0179] Fig. 9B An example cross-carrier scheduling scheme 950 is illustrated in accordance with various embodiments. Figure 1-9B , according to method 900( Fig. 9A) to generate scheme 950. Scheme 950 illustrates an information element (IE) associatedCORESETPoolIndexValue (associated CORESET pool index value) 952. associatedCORESETPoolIndexValue 952 may indicate and / or correspond to a CORESETPoolIndex value of a scheduling cell that is scheduling a scheduled cell. In some embodiments, associatedCORESETPoolIndexValue 952 may be an integer value of 0, which indicates that the CORESETPoolIndex value of the scheduling cell is 0. In some embodiments, associatedCORESETPoolIndexValue 952 may be an integer value of 0, which indicates that the CORESETPoolIndex value of the scheduling cell is 1. In some embodiments, associatedCORESETPoolIndexValue 952 may be an integer value of 2, which indicates that the CORESETPoolIndex value of the scheduling cell is both 0 and 1 (e.g., when the scheduling cell is a multi-DCI mode cell implementing MTRP).

[0180] Fig. 10A 1 is a process flow diagram illustrating a method 1000 for managing cross-carrier scheduling that may be performed by a processor of a wireless device according to various embodiments. Figure 1-10A , method 1000 may be implemented by a processor (e.g., 212, 216, 252, or 260) of a wireless device (e.g., wireless devices 120a-120e, 120, 200, 320). In various embodiments, the operations of method 1000 may be combined with method 500 ( Figure 5C )、Method 550( Figure 5D ), Method 600( Fig. 6A ), method 610( Figure 6B ), Method 800( Fig. 8A ) and / or method 900( Fig. 9A ) operations. As an example, the operations of method 1000 may be performed in method 500 ( Figure 5C ) to support type 1 HARQ-ACK operations. Figure 1-10A , the means for performing each operation of method 1000 may be one or more processors of a wireless device (eg, wireless devices 120a-120e, 120, 200, 320), such as one or more of processors 212, 216, 252, or 260, etc.

[0181] In determination block 612, the processor may perform operations including determining whether at least one serving cell is configured with two CORESETPoolIndex values ​​and whether a joint type 1 HARQ-ACK is set for the wireless device, as described with reference to method 610 ( Figure 6B ) discussed.

[0182] In response to determining that no serving cell is configured with two CORESETPoolIndex values ​​or that a joint type 1 HARQ-ACK is not set for the wireless device (i.e., determination block 612 = "No"), the processor may continue to perform operations including determining in block 612 whether at least one serving cell is configured with two CORESETPoolIndex values ​​and whether a joint type 1 HARQ-ACK is set for the wireless device, as described with reference to method 610 ( Figure 6B ) discussed.

[0183] In response to determining that at least one serving cell is configured with two CORESETPoolIndex values ​​and a joint type 1 HARQ-ACK is set for the wireless device (i.e., determination block 612 = "Yes"), the processor may perform operations including assigning, in block 1002, serving cells scheduled by the scheduler cell across carriers to a first serving cell set for generating a type 1 HARQ-ACK codebook, wherein the first serving cell set is a serving cell associated with a CORESETPoolIndex value of 0. In various embodiments, assigning serving cells scheduled by the scheduler cell across carriers to a first serving cell set for generating a type 1 HARQ-ACK codebook may be performed for each serving cell scheduled by the scheduler cell across carriers.

[0184] Fig. 10B 1 is a process flow diagram illustrating a method 1010 for managing cross-carrier scheduling that may be performed by a processor of a wireless device according to various embodiments. Figure 1-10B , method 1010 may be implemented by a processor (e.g., 212, 216, 252, or 260) of a wireless device (e.g., wireless devices 120a-120e, 120, 200, 320). In various embodiments, the operations of method 1010 may be combined with method 500 ( Figure 5C )、Method 550( Figure 5D ), Method 600( Fig. 6A ), method 610( Figure 6B ), method 810( Figure 8B ), method 820( Figure 8C ), Method 830( Fig.8D ) and / or method 900( Fig. 9A) operation. As an example, the operation of method 1010 may be performed in method 500 ( Figure 5C ) to support type 1 HARQ-ACK operations. Figure 1-10B , the means for performing each operation of method 1010 may be one or more processors of a wireless device (eg, wireless devices 120a-120e, 120, 200, 320), such as one or more of processors 212, 216, 252, or 260, etc.

[0185] In determination block 612, the processor may perform operations including determining whether at least one serving cell is configured with two CORESETPoolIndex values ​​and whether a joint type 1 HARQ-ACK is set for the wireless device, as described with reference to method 610 ( Figure 6B ) discussed.

[0186] In response to determining that no serving cell is configured with two CORESETPoolIndex values ​​or that a joint type 1 HARQ-ACK is not set for the wireless device (i.e., determination block 612 = "No"), the processor may continue to perform operations including determining in block 612 whether at least one serving cell is configured with two CORESETPoolIndex values ​​and whether a joint type 1 HARQ-ACK is set for the wireless device, as described with reference to method 610 ( Figure 6B ) discussed.

[0187] In response to determining that at least one serving cell is configured with two CORESETPoolIndex values ​​and a joint type 1 HARQ-ACK is set for the wireless device (i.e., determination block 612 = "Yes"), the processor may perform operations including determining one or more CORESETPoolIndex values ​​for the scheduling cell based on the cross-carrier scheduling configuration of the serving cell scheduled by the scheduling cell across carriers in block 1012. In various embodiments, determining one or more CORESETPoolIndex values ​​for the scheduling cell based on the cross-carrier scheduling configuration of the serving cell scheduled by the scheduling cell across carriers may be performed for each serving cell scheduled by the scheduling cell across carriers.

[0188] In block 1014, the processor may perform operations including assigning serving cells scheduled by the scheduling cell across carriers to one or more serving cell sets for generating one or more Type 1 HARQ-ACK codebooks based on the determined one or more CORESETPoolIndex values ​​of the scheduling cell.

[0189] Fig. 10Cis a process flow diagram illustrating a method 1020 for managing cross-carrier scheduling that may be performed by a processor of a wireless device according to various embodiments. Figure 1-10C , method 1020 may be implemented by a processor (e.g., 212, 216, 252, or 260) of a wireless device (e.g., wireless devices 120a-120e, 120, 200, 320). In various embodiments, the operations of method 1020 may be combined with method 500 ( Figure 5C )、Method 550( Figure 5D ), Method 600( Fig. 6A ), method 610( Figure 6B ), method 810( Figure 8B ), method 820( Figure 8C ), Method 900( Fig. 9A ) and / or method 1010( Fig. 10B ) operation. For example, method 1020 may be performed as part of the following operations: In block 1014 ( Fig. 10B ), assigning serving cells scheduled by the scheduling cell across carriers to one or more serving cell sets for generating one or more type 1 HARQ-ACK codebooks based on the one or more CORESETPoolIndex values ​​determined for the scheduling cell. In some embodiments, the one or more CORESETPoolIndex values ​​determined for the scheduling cell may be a single CORESETPoolIndex value: a value of 0 or a value of 1. As another example, the operations of method 1020 may be performed in method 500( Figure 5C ) to support type 1 HARQ-ACK operations. Figure 1-10C , the device for performing each operation of method 1020 can be one or more processors of a wireless device (e.g., wireless devices 120a-120e, 120, 200, 320), such as one or more of processors 212, 216, 252 or 260, etc.

[0190] In block 1022, the processor may perform operations including assigning serving cells scheduled by the scheduler cell across carriers to a first serving cell set for generating a first type 1 HARQ-ACK codebook based on the determined single CORESETPoolIndex value being 0.

[0191] In block 1024, the processor may perform operations including assigning serving cells scheduled by the scheduler cell across carriers to a second serving cell set for generating a second type 1 HARQ-ACK codebook based on the determined single CORESETPoolIndex value being 1.

[0192] Fig. 10D 1040 is a process flow diagram illustrating a method 1040 for managing cross-carrier scheduling that may be performed by a processor of a wireless device according to various embodiments. Figure 1-10D , method 1040 may be implemented by a processor (e.g., 212, 216, 252, or 260) of a wireless device (e.g., wireless devices 120a-120e, 120, 200, 320). In various embodiments, the operations of method 1040 may be combined with method 500 ( Figure 5C )、Method 550( Figure 5D ), Method 600( Fig. 6A ), method 610( Figure 6B ), method 810( Figure 8B ), method 820( Figure 8C ), Method 830( Fig.8D ), Method 900( Fig. 9A ) and / or method 1010( Fig. 10B For example, the method 1040 may be performed in response to determining that at least one serving cell is configured with two CORESETPoolIndex values ​​and a joint type 1 HARQ-ACK is set for the wireless device (i.e., determination block 612 ( Fig. 10B )=“Yes”). In some embodiments, the operation of method 1040 may be performed to determine the one or more CORESETPoolIndex values ​​of the scheduling cell based on the cross-carrier scheduling configuration of the serving cell scheduled by the scheduling cell across carriers and assign the serving cell scheduled by the scheduling cell across carriers to the one or more serving cell sets for generating the one or more type 1 HARQ-ACK codebooks based on the one or more CORESETPoolIndex values ​​determined for the scheduling cell. As another example, the operation of method 1040 may be performed in method 500( Figure 5C ) to support type 1 HARQ-ACK operations. Figure 1-10D , the device for performing each operation of method 1040 can be one or more processors of a wireless device (e.g., wireless devices 120a-120e, 120, 200, 320), such as one or more of processors 212, 216, 252 or 260, etc.

[0193] In block 1042 , the processor may perform operations including determining an associated CORESETPoolIndex value of a scheduling cell indicated in a cross-carrier scheduling configuration of a serving cell that is cross-carrier scheduled by the scheduling cell.

[0194] In block 1044, the processor may perform operations including assigning serving cells scheduled by the scheduler cell across carriers to a first serving cell set for generating a first type 1 HARQ-ACK codebook based on the determined associated CORESETPoolIndex value being 0.

[0195] In block 1046 , the processor may perform operations including assigning the serving cells scheduled by the scheduler cell across carriers to a second serving cell set for generating a second type 1 HARQ-ACK codebook based on the determined associated CORESETPoolIndex value being 1.

[0196] In block 1048, the processor may perform operations including assigning the serving cells scheduled by the scheduler cell across carriers to both a first serving cell set for generating a first type 1 HARQ-ACK codebook and a second serving cell set for generating a second type 1 HARQ-ACK codebook based on the determined associated CORESETPoolIndex value being 2.

[0197] Fig.11 An example of cross-carrier scheduling supporting joint semi-static HARQ-ACK according to various embodiments is illustrated. Figure 1-11 , Fig.11 Explain the method 1010 ( Fig. 10B )、1020( Fig. 10C ) and 1040( Fig. 10D ) operation example joint semi-static HARQ-ACK operation. Fig.11 In the method 1010 ( Fig. 10B )、1020( Fig. 10C ) and 1040( Fig. 10D), CC1 is associated with CORESETPoolIndex=0, CC2 is associated with CORESETPoolIndex=1, and CC3 is associated with CORESETPoolIndex=0 and CORESETPoolIndex=1. CC1 may be added to list S0 for HARQ-ACK because CC1 is associated with CORESETPoolIndex=0. CC2 may be added to list S1 for HARQ-ACK because CC2 is associated with CORESETPoolIndex=1. CC3 may be added to list S0 and list S1 for HARQ-ACK because CC3 is associated with both CORESETPoolIndex=0 and CORESETPoolIndex=1. In this way, CC3 may be handled as a multi-DCI (such as a multi-DCI MTRP cell).

[0198] Fig.12 1 is a process flow diagram illustrating a method 1200 for managing cross-carrier scheduling that may be performed by a processor of a wireless device according to various embodiments. Figure 1-12 , method 1200 may be implemented by a processor (e.g., 212, 216, 252, or 260) of a wireless device (e.g., wireless devices 120a-120e, 120, 200, 320). In various embodiments, the operations of method 1200 may be combined with method 500 ( Figure 5C )、Method 550( Figure 5D ), Method 600( Fig. 6A ), method 610( Figure 6B ), method 810( Figure 8B ), method 820( Figure 8C ), Method 830( Fig.8D ), Method 900( Fig. 9A )、Method 1010( Fig. 10B )Method 1020( Fig. 10C ) and / or method 1040( Fig. 10D As another example, the operation of method 1200 may be performed in method 500 ( Figure 5C ) to support type 1 HARQ-ACK operations. Figure 1-12 , the device for performing each operation of method 1200 can be one or more processors of a wireless device (e.g., wireless devices 120a-120e, 120, 200, 320), such as one or more of processors 212, 216, 252 or 260, etc.

[0199] In block 1201, the processor may perform operations including receiving a cross-carrier scheduling configuration for a serving cell. In some embodiments, the cross-carrier scheduling configuration for the serving cell may be received in an RRC message. In some embodiments, the cross-carrier scheduling configuration element may indicate whether the serving cell is cross-carrier scheduled by the scheduling cell. For example, the value in the CIF and / or associated CORESETPoolIndexValue element in the cross-carrier scheduling configuration may indicate whether the serving cell is cross-carrier scheduled by the scheduling cell. In various embodiments, one or more RRC messages including one or more cross-carrier scheduling configurations may be received from a network computing device.

[0200] In determination block 802, the processor may perform operations including determining whether the serving cell is cross-carrier scheduled by the scheduling cell, as described with reference to method 800 ( Fig. 8A ) discussed.

[0201] In response to determining that the serving cell is not cross-carrier scheduled by the scheduling cell (i.e., determination block 802 = "No"), the processor may continue to perform operations, including determining whether the serving cell is cross-carrier scheduled by the scheduling cell at determination block 802, as described with reference to method 800 ( Fig. 8A ) discussed.

[0202] In response to determining that the serving cell is cross-carrier scheduled by the scheduling cell (i.e., determination block 802 = "Yes"), the processor may perform operations including determining whether the scheduled cell is associated with both CORESETPoolIndex values ​​based on the cross-carrier scheduling configuration of the serving cell in block 1202. For example, the processor may determine whether the scheduled cell is associated with both a CORESETPoolIndex value of 0 and a CORESETPoolIndex value of 1. In various embodiments, determining whether the scheduled cell is associated with both CORESETPoolIndex values ​​based on the cross-carrier scheduling configuration of the serving cell may include determining whether the scheduled cell has an associated CORESETPoolIndex value of 2 in the cross-carrier scheduling configuration of the serving cell.

[0203] In block 1204, the processor may perform operations including handling the serving cell as a multi-DCI mode cell in wireless device operation. In various embodiments, handling the serving cell as a multi-DCI mode cell in wireless device operation may include adding the serving cell to two HARQ-ACK codebooks. In various embodiments, handling the serving cell as a multi-DCI mode cell in wireless device operation may include counting the serving cell as two serving cells to generate a type 2 HARQ-ACK codebook for the serving cell. In various embodiments, handling the serving cell as a multi-DCI mode cell in wireless device operation may include initializing two scrambling identifiers of a physical downlink shared channel (PDSCH) in the serving cell. In various embodiments, handling the serving cell as a multi-DCI mode cell in wireless device operation may include configuring two cell-specific reference signal (CRS) rate matching pattern lists in the serving cell. In various embodiments, handling the serving cell as a multi-DCI mode cell in wireless device operation may include supporting out-of-order operation of the serving cell. In various embodiments, handling a serving cell as a multi-DCI mode cell in wireless device operation may include associating two active transmission configuration indicator (TCI) state lists with the serving cell. In various embodiments, handling a serving cell as a multi-DCI mode cell in wireless device operation may include including the serving cell in a serving cell list provided with both CORESETPoolIndex values ​​of 0 and 1 for calculating physical downlink control channel (PDDCH) candidates and / or non-overlapping control channel element (CCE) restrictions.

[0204] Fig.13 1 shows a component block diagram of an example network computing device 1300. In some embodiments, the wireless network computing device 1300 may be used as a network element of a communication network, such as a base station (e.g., base stations 110a-e, 110, 350). The network computing device 1300 may include at least Fig.13 Components explained in . Figure 1-13, the network computing device 1300 may generally include a processor 1301 coupled to a volatile memory 1302 and a large capacity non-volatile memory such as a disk drive 1303. The network computing device 1300 may also include a peripheral memory access device such as a floppy disk drive, a compact disk (CD) or a digital video disk (DVD) drive 1306 coupled to the processor 1301. The network computing device 1300 may also include a network access port 1304 (or interface) coupled to the processor 1301 for establishing a data connection with a network such as the Internet or a local area network coupled to other system computers and servers. The network computing device 1300 may include one or more antennas 1307 for sending and receiving electromagnetic radiation, which may be connected to a wireless communication link. The network computing device 1300 may include additional access ports (such as USB, Firewire, Thunderbolt, etc.) for coupling to peripherals, external memory or other devices.

[0205] Fig.14 1 shows a component block diagram of an example wireless device. In some embodiments, the wireless device can be implemented as various wireless devices (e.g., wireless devices 120a-120e, 120, 200, 320), examples of which are shown in FIG. Fig.14 1400 is illustrated in the form of a smartphone 1400. The smartphone 1400 may include: a first SOC 202 (e.g., SOC-CPU) coupled to a second SOC 204 (e.g., a 5G-capable SOC). The first and second SOCs 202, 204 may be coupled to internal memory 1406, 1416, a display 1412, and a speaker 1414. Additionally, the smartphone 1400 may include an antenna 1404 for sending and receiving electromagnetic radiation that may be connected to a wireless data link, or a wireless transceiver 266 (e.g., a cellular telephone transceiver, etc.) coupled to one or more processors in the first or second SOC 202, 204. The smartphone 1400 typically also includes a menu selection button or rocker switch 1420 for receiving user input.

[0206] The typical smart phone 1400 also includes a sound coding / decoding (CODEC) circuit 1410, which digitizes the sound received from the microphone into a data packet suitable for wireless transmission and decodes the received sound data packet to generate an analog signal provided to the speaker to produce sound. In addition, one or more of the processors in the first and second SOCs 202, 204, the wireless transceiver 266, and the CODEC 1410 may include a digital signal processor (DSP) circuit (not shown separately).

[0207] The processors of the wireless network computing device 1300 and the smart phone 1400 may be any programmable microprocessor, microcomputer, or one or more multi-processor chips that can be configured by software instructions (applications) to perform various functions including the functions of the various embodiments described below. In some mobile devices, multiple processors may be provided (such as one processor dedicated to wireless communication functions within SOC 204 and one processor dedicated to running other applications within SOC 202). Software applications may be stored in memory and then accessed and loaded into the processor. The processor may include internal memory sufficient to store application software instructions.

[0208] As used in this application, the terms "component", "module", "system" and similar terms are intended to include computer-related entities, such as but not limited to hardware, firmware, a combination of hardware and software, software, or software in execution that is configured to perform a specific operation or function. For example, a component can be, but is not limited to, a process, a processor, an object, an executable, a thread of execution, a program, and / or a computer running on a processor. As an illustration, both an application running on a wireless device and a wireless device can be referred to as a component. One or more components may reside within a process and / or a thread of execution, and a component may be localized on a processor or core and / or distributed between two or more processors or cores. In addition, these components may be executed from various non-transient computer-readable media having various instructions and / or data structures stored thereon. Each component may communicate via local and / or remote processes, function or procedure calls, electronic signals, data packets, memory read / writes, and other known networks, computers, processors, and / or communication methodologies associated with processes.

[0209] Several different cellular and mobile communication services and standards are available and are contemplated in the future, all of which can be implemented and benefit from various embodiments. Such services and standards include, for example, the Third Generation Partnership Project (3GPP), LTE systems, third generation wireless mobile communication technology (3G), fourth generation wireless mobile communication technology (4G), fifth generation wireless mobile communication technology (5G), global system for mobile communications (GSM), universal mobile telecommunications system (UMTS), 3GSM, general packet radio service (GPRS), code division multiple access (CDMA) systems (e.g., cdmaOne, CDMA1020TM), enhanced data rates for GSM evolution (EDGE), advanced mobile phone system (AMPS), digital AMPS (IS-136 / TDMA), evolution data optimized (EV-DO), digital enhanced cordless telecommunications (DECT), worldwide interoperability for microwave access (WiMAX), wireless local area network (WLAN), Wi-Fi protected access I and II (WPA, WPA2), and integrated digital enhanced network (iDEN). Each of these technologies involves, for example, the transmission and reception of voice, data, signaling and / or content messages. It should be understood that any reference to terminology and / or technical details related to individual telecommunication standards or technologies is for illustrative purposes only and is not intended to limit the scope of the claims to a particular communication system or technology unless specifically stated in the claim language.

[0210] The various embodiments illustrated and described are provided only as examples of the various features of the claims. However, the features shown and described for any given embodiment are not necessarily limited to the associated embodiments, and may be used in conjunction with or combined with other embodiments shown and described. In addition, the claims are not intended to be limited to any one of the example embodiments. For example, one or more operations of methods 500, 550, 610, 600, 610, 800, 810, 820, 830, 900, 1000, 1010, 1020, 1240, and / or 1200 may replace or be combined with one or more operations of methods 500, 550, 610, 600, 610, 800, 810, 820, 830, 900, 1000, 1010, 1020, 1240, and / or 1200.

[0211] Various implementation examples are described in the following paragraphs. Although some of the following implementation examples are described in the form of example methods, further example implementations may include: the example methods discussed in the following paragraphs are implemented by a wireless device including a processor configured to perform the operations of the example methods; the example methods discussed in the following paragraphs are implemented by a wireless device including means for performing the functions of the example methods; and the example methods discussed in the following paragraphs are implemented as a non-transitory processor-readable storage medium having processor-executable instructions stored thereon, the processor-executable instructions being configured to cause the processor of the wireless device to perform the operations of the example methods.

[0212] Example 1: A method for managing cross-carrier scheduling by a processor of a wireless device, comprising: receiving downlink control information (DCI) for scheduling communications on a scheduled cell from a scheduling cell; transmitting or monitoring the communications on the scheduled cell based on the DCI; and performing a type 1 hybrid automatic repeat request (HARQ) acknowledgment (HARQ-ACK) operation for the communications based on one or more control resource set (CORESET) pools configured for the scheduled cell.

[0213] Example 2: The method as described in Example 1 further includes receiving a cross-carrier scheduling configuration of the scheduling cell, the cross-carrier scheduling configuration indicating the one or more CORESET pools.

[0214] Example 3: A method as described in any of Examples 1-2, wherein in response to the cross-carrier scheduling configuration indicating two CORESET pools, performing a type 1 HARQ-ACK operation for the communication based on one or more CORESET pools configured for the scheduled cell includes: based on the CORESET pool of the scheduling cell being indicated as a first CORESET pool, performing a type 1 HARQ-ACK operation for the communication on the first CORESET pool including the scheduled cell; or based on the CORESET pool of the scheduling cell being indicated as a second CORESET pool, performing a type 1 HARQ-ACK operation for the communication on the second CORESET pool including the scheduled cell.

[0215] Example 4: A method as described in any of Examples 1-2, wherein, in response to the cross-carrier scheduling configuration indicating two CORESET pools of the scheduling party cell, performing a type 1 HARQ-ACK operation for the communication based on the one or more CORESET pools configured for the scheduled party cell includes: based on the first CORESET pool of the two CORESET pools being a default CORESET pool, performing a type 1 HARQ-ACK operation for the communication on the first CORESET pool, the first CORESET pool including the scheduled party cell.

[0216] Example 5: A method as described in any of Examples 1-2, wherein, in response to the cross-carrier scheduling configuration indicating two CORESET pools of the scheduling cell and a selected CORESET pool of the two CORESET pools being associated with the scheduled cell, performing a type 1 HARQ-ACK operation for the communication based on the one or more CORESET pools configured for the scheduled cell includes: performing a type 1 HARQ-ACK operation for the communication on the selected CORESET pool based on the indication in the cross-carrier scheduling configuration, the selected CORESET pool including the scheduled cell.

[0217] Example 6: A method as described in any of Examples 1-2, wherein, in response to the cross-carrier scheduling configuration indicating two CORESET pools of the scheduling cell and the association of the scheduled cell with the two CORESET pools, performing a type 1 HARQ-ACK operation for the communication based on the one or more CORESET pools configured for the scheduled cell includes: performing a type 1 HARQ-ACK operation for the communication on the two CORESET pools based on the indication of the association with the two CORESET pools in the cross-carrier scheduling configuration, the two CORESET pools including the scheduled cell.

[0218] Example 7: The method as described in any of Examples 1-6 further includes: based on the indication of the association with the two CORESET pools in the cross-carrier scheduling configuration, handling the scheduled cell as a multiple downlink control information (DCI) (multi-DCI) mode cell in the wireless device operation.

[0219] Example 8: The method of Example 7, wherein handling the scheduled cell as a multi-DCI mode cell in wireless device operation includes counting the scheduled cell as two serving cells to generate a type 2 HARQ-ACK codebook for the scheduled cell.

[0220] Example 9: A method as described in any of Examples 7-8, wherein handling the scheduled cell as a multi-DCI mode cell in wireless device operation includes initializing two scrambling identifiers of a physical downlink shared channel (PDSCH) in the scheduled cell.

[0221] Example 10: A method as described in any of Examples 7-9, wherein handling the scheduled cell as a multi-DCI mode cell in wireless device operation includes configuring two cell-specific reference signal (CRS) rate matching mode lists in the scheduled cell.

[0222] Example 11: The method of any of Examples 7-10, wherein handling the scheduled cell as a multi-DCI mode cell in wireless device operation includes supporting out-of-order operation of the scheduled cell.

[0223] Example 12: A method as described in any of Examples 7-11, wherein handling the scheduled cell as a multi-DCI mode cell in wireless device operation includes associating two active transmission configuration indicator (TCI) state lists with the scheduled cell.

[0224] Example 13: A method as described in any of Examples 7-12, wherein handling the scheduled cell as a multi-DCI mode cell in wireless device operation includes including the scheduled cell in a serving cell list provided with a CORESETPoolIndex value of both 0 and 1 for calculating physical downlink control channel (PDDCH) candidates and / or non-overlapping control channel element (CCE) restrictions.

[0225] Example 14: A method as described in any of Examples 1-13, wherein the cross-carrier scheduling configuration is received in a radio resource control (RRC) message.

[0226] Example 15: The method of Example 14, wherein the one or more CORESET pools are indicated by one or more control resource set (CORESET) pool index (CORESETPoolIndex) values.

[0227] Example 16: A method for managing cross-carrier scheduling by a processor of a network computing device, comprising: transmitting a cross-carrier scheduling configuration of a scheduled cell to a wireless device, wherein the cross-carrier scheduling configuration indicates one or more associated control resource set (CORESET) pools of a scheduling cell configured to schedule the scheduled cell; transmitting downlink control information (DCI) for the scheduled cell from the scheduling cell to the wireless device; and receiving joint feedback from the wireless device for a type 1 hybrid automatic repeat request (HARQ) acknowledgment (HARQ-ACK) operation for communications associated with the scheduled cell.

[0228] Example 17: The method of Example 16, wherein the one or more associated CORESET pools are indicated by one or more CORESETPoolIndex values.

[0229] Example 18: The method of any of Examples 16-17, wherein the cross-carrier scheduling configuration indicates that a single CORESET pool of the one or more associated CORESET pools of the scheduler cell is a CORESET pool of the scheduled cell.

[0230] Example 19: The method of any one of Examples 16-18, wherein the cross-carrier scheduling configuration indicates that two of the one or more associated CORESET pools of the scheduling cell are both CORESET pools of the scheduled cell.

[0231] Example 20: The method of any of Examples 16-19, wherein the cross-carrier scheduling configuration is transmitted to the wireless device in a radio resource control (RRC) message.

[0232] The foregoing method descriptions and process flow charts are provided only as illustrative examples and are not intended to require or imply that the operations of the various embodiments must be performed in the order given. As will be appreciated by those skilled in the art, the order of operations in the foregoing embodiments may be performed in any order. Phrases such as "thereafter," "subsequently," and "next" are not intended to limit the order of operations; these phrases are used to guide the reader through the description of the method. Further, any reference to a claim element in singular form (e.g., a reference using the article "a," "a," or "the") should not be interpreted as limiting the element to the singular.

[0233] The various illustrative logic blocks, modules, components, circuits, and algorithmic operations described in conjunction with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or a combination of the two. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and operations are generally described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. The technician may implement the described functionality in different ways for each specific application, but such embodiment decisions should not be interpreted as causing a departure from the scope of the claims.

[0234] The hardware used to implement the various illustrative logics, logic blocks, modules, and circuits described in conjunction with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device designed to perform the functions described herein, discrete gate or transistor logic, discrete hardware components, or any combination thereof. The general purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of receiver smart objects, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Alternatively, some operations or methods may be performed by a circuit system dedicated to a given function.

[0235] In one or more embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, these functions may be stored as one or more instructions or codes on a non-transient computer-readable storage medium or a non-transient processor-readable storage medium. The operation of the method or algorithm disclosed herein may be implemented in a processor-executable software module or a processor-executable instruction, which may reside on a non-transient computer-readable or processor-readable storage medium. A non-transient computer-readable or processor-readable storage medium may be any storage medium that can be accessed by a computer or processor. As an example and not limitation, such non-transient computer-readable or processor-readable storage media may include RAM, ROM, EEPROM, flash memory, CD-ROM or other optical disk storage, disk storage or other magnetic storage smart objects, or any other medium that can be used to store desired program codes in the form of instructions or data structures and can be accessed by a computer. Disk and disc as used herein include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, wherein disk often reproduces data magnetically and disc reproduces data optically with lasers. Combinations of the above are also included within the scope of non-transitory computer-readable and processor-readable media. Additionally, the operations of a method or algorithm may reside as one or any combination or set of codes and / or instructions on a non-transitory processor-readable storage medium and / or computer-readable storage medium that may be incorporated into a computer program product.

[0236] The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present claims. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments without departing from the scope of the claims. Thus, the present disclosure is not intended to be limited to the embodiments shown herein, but should be accorded the broadest scope consistent with the appended claims and the principles and novel features disclosed herein.

Claims

1. A method for managing cross-carrier scheduling by a processor of a wireless device, comprising: receiving a cross-carrier scheduling configuration of a scheduling party cellular cell, where the cross-carrier scheduling configuration indicates two control resource set (CORESET) pools configured for a scheduled party cellular cell; receiving downlink control information (DCI) from the scheduling cell that schedules communications on the scheduled cell; transmitting the communication or monitoring the communication on the scheduled cell based on the DCI; as well as A type 1 hybrid automatic repeat request (HARQ) acknowledgement (HARQ-ACK) operation is performed for the communication on two CORESET pools, the two CORESET pools including the scheduled party cell.

2. The method of claim 1, further comprising: Based on the indication of association with the two CORESET pools in the cross-carrier scheduling configuration, the scheduled party cell is handled in wireless device operation as a multiple downlink control information (DCI) (multi-DCI) mode cell.

3. The method of claim 2, wherein handling the scheduled cell as a multi-DCI mode cell in wireless device operation comprises counting the scheduled cell as two serving cells to generate a type 2 HARQ-ACK codebook for the scheduled cell.

4. The method of claim 2, wherein handling the scheduled cell as a multi-DCI mode cell in wireless device operation comprises initializing two scrambling identifiers of a physical downlink shared channel (PDSCH) in the scheduled cell.

5. The method of claim 2, wherein handling the scheduled cell as a multi-DCI mode cell in wireless device operation comprises configuring two cell-specific reference signal (CRS) rate matching pattern lists in the scheduled cell.

6. The method of claim 2, wherein handling the scheduled cell as a multi-DCI mode cell in wireless device operation comprises supporting out-of-order operation of the scheduled cell.

7. The method of claim 2, wherein handling the scheduled cell as a multi-DCI mode cell in wireless device operation comprises associating two active transmission configuration indicator (TCI) state lists with the scheduled cell.

8. The method of claim 2, wherein handling the scheduled cell as a multi-DCI mode cell in wireless device operation comprises: The scheduled cell is included in a serving cell list provided with both CORESET pool index values ​​0 and 1 for calculating physical downlink control channel (PDDCH) candidates and / or non-overlapping control channel element (CCE) restrictions.

9. The method of claim 1, wherein the cross-carrier scheduling configuration is received in a radio resource control (RRC) message.

10. The method of claim 9, wherein the two CORESET pools are indicated by corresponding control resource set (CORESET) pool index (CORESETPoolIndex) values.

11. A method for managing cross-carrier scheduling by a processor of a network computing device, comprising: transmitting a cross-carrier scheduling configuration of a scheduled cell to a wireless device, wherein the cross-carrier scheduling configuration indicates one or more associated control resource set (CORESET) pools of a scheduling cell configured to schedule the scheduled cell, wherein the cross-carrier scheduling configuration indicates that two of the one or more associated CORESET pools of the scheduling cell are both CORESET pools of the scheduled cell; transmitting, from the scheduling cell to the wireless device, downlink control information (DCI) for the scheduled cell; as well as Joint feedback is received from the wireless device for a type 1 hybrid automatic repeat request (HARQ) acknowledgement (HARQ-ACK) operation for communications associated with the scheduled cell.

12. The method of claim 11, wherein the one or more associated CORESET pools are indicated by one or more CORESETPoolIndex values.

13. The method of claim 11, wherein the cross-carrier scheduling configuration is transmitted to the wireless device in a radio resource control (RRC) message.

14. A wireless device comprising: Radio resources; as well as a processor connected to the radio resource, the processor being configured to: receiving a cross-carrier scheduling configuration of a scheduling party cellular cell, where the cross-carrier scheduling configuration indicates two control resource set (CORESET) pools configured for a scheduled party cellular cell; receiving downlink control information (DCI) from the scheduling cell that schedules communications on the scheduled cell; transmitting the communication or monitoring the communication on the scheduled cell based on the DCI; as well as A type 1 hybrid automatic repeat request (HARQ) acknowledgement (HARQ-ACK) operation is performed for the communication on the two CORESET pools, the two CORESET pools including the scheduled party cell.

15. The wireless device of claim 14, wherein the processor is further configured to handle the scheduled party cell as a multiple downlink control information (DCI) (multi-DCI) mode cell in wireless device operation based on the indication of association with the two CORESET pools in the cross-carrier scheduling configuration.

16. The wireless device of claim 15, wherein the processor configured to handle the scheduled cell as a multi-DCI mode cell in wireless device operation is further configured to count the scheduled cell as two serving cells to generate a Type 2 HARQ-ACK codebook for the scheduled cell.

17. The wireless device of claim 15, wherein the processor configured to handle the scheduled cell as a multi-DCI mode cell in wireless device operation is further configured to initialize two scrambling identifiers of a physical downlink shared channel (PDSCH) in the scheduled cell.

18. The wireless device of claim 15, wherein the processor configured to handle the scheduled cell as a multi-DCI mode cell in wireless device operation is further configured to configure two cell-specific reference signal (CRS) rate matching pattern lists in the scheduled cell.

19. The wireless device of claim 15, wherein the processor configured to handle the scheduled cell as a multi-DCI mode cell in wireless device operation is further configured to support out-of-order operation of the scheduled cell.

20. The wireless device of claim 15, wherein the processor configured to handle the scheduled cell as a multi-DCI mode cell in wireless device operation is further configured to associate two active transmission configuration indicator (TCI) state lists with the scheduled cell.

21. A wireless device as described in claim 15, wherein the processor configured to handle the scheduled cellular cell as a multi-DCI mode cellular cell in wireless device operation is further configured to: include the scheduled cellular cell in a serving cellular cell list provided with both CORESET pool index values ​​0 and 1 for calculating physical downlink control channel (PDDCH) candidates and / or non-overlapping control channel elements (CCE) restrictions.

22. The wireless device of claim 14, wherein the cross-carrier scheduling configuration is received in a radio resource control (RRC) message.

23. The wireless device of claim 22, wherein the two CORESET pools are indicated by corresponding control resource set (CORESET) pool index (CORESETPoolIndex) values.

24. A network computing device comprising: Radio resources; as well as a processor connected to the radio resource, the processor being configured to: transmitting a cross-carrier scheduling configuration of a scheduled cell to a wireless device, wherein the cross-carrier scheduling configuration indicates one or more associated control resource set (CORESET) pools of a scheduling cell configured to schedule the scheduled cell, wherein the cross-carrier scheduling configuration indicates that two of the one or more associated CORESET pools of the scheduling cell are both CORESET pools of the scheduled cell; transmitting, from the scheduling cell to the wireless device, downlink control information (DCI) for the scheduled cell; as well as Joint feedback is received from the wireless device for a type 1 hybrid automatic repeat request (HARQ) acknowledgement (HARQ-ACK) operation for communications associated with the scheduled cell.

25. The network computing device of claim 24, wherein: The one or more associated CORESET pools are indicated by one or more CORESET pool index (CORESETPoolIndex) values.

26. The network computing device of claim 24, wherein the cross-carrier scheduling configuration is transmitted to the wireless device in a radio resource control (RRC) message.

Images