Cross-carrier scheduling managed by wireless devices

Abstract

The present disclosure provides systems, methods, and apparatus for managing cross-carrier scheduling by a processor of a wireless device, and a computer program encoded on a computer storage medium. In one aspect, the wireless device may determine that a scheduled cell is configured to be scheduled by a scheduling cell. The wireless device may receive downlink control information (DCI) from the scheduling cell. The wireless device may determine an association of the DCI with an index based on the received DCI. The wireless device may perform cross-carrier scheduling of communications with a first transmit receive point (TRP) or a second TRP based on the DCI and the associated index.

Description

[0001] Related Applications

[0002] This application claims priority to U.S. Provisional Application No. 62 / 881,645, filed on August 1, 2019, entitled “MANAGING CROSS-CARRIER SCHEDULING BY A WIRELESS DEVICE,” the entire contents of which are incorporated herein by reference for all purposes. Technical Field

[0003] The present disclosure relates generally to wireless devices, and more particularly to managing wireless devices to perform cross-carrier scheduling. Background Art

[0004] The communication system can be configured to use 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 be scheduled independently, which is called cross-carrier scheduling. Summary of the invention

[0005] The systems, methods and devices of the present disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.

[0006] One innovative aspect of the subject matter described in the present disclosure can be implemented in a wireless device. Some implementations may include: determining that a scheduled cell is configured to be scheduled by a scheduling cell; receiving downlink control information (DCI) from the scheduling cell; determining an association between the DCI and an index based on the received DCI; and performing cross-carrier scheduling of communications with a first transmit-receive point (TRP) or a second TRP based on the DCI and the associated index.

[0007] In some implementations, the index may include one of a first TRP and a second TRP. In some implementations, determining the association of the DCI with the index based on the received DCI may include determining the association of the DCI with the index based on a field in a payload of the DCI. In some implementations, determining the association of the DCI with the index based on a field in a payload of the DCI may include determining an indication of the index from a field added to the payload of the DCI.

[0008] In some implementations, determining the association of the DCI with an index based on a field in a payload of the DCI may include: determining an indication of the index from a carrier indicator field (CIF) in the DCI. In some implementations, the CIF may indicate one of a first higher layer parameter and a second higher layer parameter, each parameter being associated with a value of the index. In some implementations, the first higher layer parameter may include a CORESET pool index of 0, and the second higher layer parameter may include a control resource set (CORESET) pool index of 1. In some implementations, performing cross-carrier scheduling of communications with a first TRP and a second TRP based on the association of the DCI with the index may include: performing cross-carrier scheduling of communications with a first TRP and a second TRP based on the determined index. In some implementations, the scheduling cell may be configured by a PDCCH-configuration (Config) parameter, which includes two CORESET pool index values ​​in a CORESET for an active bandwidth portion (BWP) of a scheduled cell. In some implementations, the index may include a CORESET pool index of a control resource set (CORESET) carrying the DCI. In some implementations, the scheduling cell may be configured to perform multi-PDSCH multi-TRP communication. In some implementations, the scheduling cell may be configured by a PDCCH-configuration parameter that includes a CORESET pool index value for all CORESETs of the active bandwidth part (BWP) of the scheduled cell, or is not configured with a CORESET pool index value.

[0009] In some implementations, the scheduled cell may be configured by a PDCCH-configuration parameter including two CORESET pool index values ​​in a CORESET for an active bandwidth portion (BWP) of the scheduled cell. Such an implementation may also include: receiving a second DCI from a second scheduling cell, and determining an association of the second DCI with a second index based on the received second DCI. In such an implementation, performing cross-carrier scheduling of communications with a first TRP or a second TRP based on the DCI and the associated index may include: performing cross-carrier scheduling of communications with a first TRP based on the DCI and the associated index, and performing cross-carrier scheduling of communications with a second TRP based on the second DCI and the associated second index.

[0010] In some implementations, the CIF may correspond to a first value indicating a scheduled cell, and the second DCI may include a second CIF corresponding to a second value indicating the scheduled cell. Some implementations may also include: determining that the scheduling cell is configured with two or more CORESET pool index values, and performing data communication operations of the scheduled cell according to the two or more CORESET pool index values. Some implementations may also include: ignoring the CORESET pool index of the CORESET in which the DCI is received, and performing data communication operations of the scheduled cell without reference to the CORESET pool index in which the DCI is received. In some implementations, performing cross-carrier scheduling of communications with the first TRP or the second TRP based on the DCI and the associated index may also include: performing data communication operations of the scheduled cell with the first TRP or the second TRP, wherein the data communication operations may include at least one of the following: hybrid automatic repeat request (HARQ)-ACK feedback, physical downlink shared channel (PDSCH) scrambling, and PDSCH rate matching.

[0011] In some implementations, determining the association of the DCI with the index based on the received DCI may include: determining a CORESET pool index of the CORESET in which the DCI is received, and performing data communication operations of the scheduled cell according to the CORESET pool index of the CORESET in which the DCI is received. Some implementations may also include: determining that the scheduling cell is configured by a PDCCH-configuration parameter, which includes two CORESET pool index values ​​in a CORESET for an active bandwidth part (BWP) of the scheduled cell; determining the two CORESET pool index values; and performing data communication operations of the scheduled cell with the first TRP or the second TRP according to the determined two CORESET pool index values.

[0012] Some implementations may also include: determining whether the scheduled cell is configured by a PDCCH-configuration parameter, the PDCCH-configuration parameter including two CORESET pool index values ​​in a CORESET for an active BWP of the scheduled cell; ignoring the CORESET pool index in which the DCI is received in response to determining that the scheduled cell is not configured by the PDCCH-configuration parameter, the PDCCH-configuration parameter including two CORESET pool index values ​​in a CORESET for an active BWP of the scheduled cell; and performing data communication operations for the scheduled cell without reference to the CORESET pool index of the CORESET in which the DCI is received. In some implementations, the index may include a first CORESET index value configured for all CORESETs in the scheduling cell, and the second index may include a second CORESET pool index value configured for all CORESETs in the second scheduling cell. This implementation may also include: performing cross-carrier scheduling of communications with a first TRP according to a communication link scheduling from a scheduling cell associated with the index, and performing cross-carrier scheduling of communications with a second TRP according to a communication link scheduling from a second scheduling cell associated with the second index. Some implementations may also include determining a DCI to schedule the scheduled cell.

[0013] Another innovative aspect of the subject matter described in the present disclosure can be implemented in an apparatus of a wireless device. Some implementations may include: a first interface configured to obtain a serving cell signal from a scheduled cell and receive downlink control information (DCI) from a scheduling cell; and a processing system coupled to the first interface and configured to: determine that the scheduled cell is configured to be scheduled by the scheduling cell; determine an association of the DCI with an index based on the received DCI; and initiate cross-carrier scheduling of communication with a first transmit-receive point (TRP) or a second TRP based on the DCI and the associated index.

[0014] In some implementations, the processing system may be configured such that the index includes one of a first TRP and a second TRP. In some implementations, the processing system may also be configured to determine the association of the DCI with the index based on a field in the payload of the DCI. In some implementations, the processing system may also be configured to determine an indication of the index from a field added to the payload of the DCI. In some implementations, the processing system may also be configured to determine an indication of the index from a carrier indicator field (CIF) in the DCI. In some implementations, the processing system may be configured such that the CIF indicates one of a first higher layer parameter and a second higher layer parameter, each parameter being associated with a value of the index.

[0015] Another innovative aspect of the subject matter described in the present disclosure can be implemented in a non-transitory processor-readable medium having processor-executable instructions stored thereon, the processor-executable instructions being configured to cause a wireless device processor to perform various operations, some implementations of which may include: determining that a scheduled cell is configured to be scheduled by a scheduling cell; receiving downlink control information (DCI) from the scheduling cell; determining an association of the DCI with an index based on the received DCI, and performing cross-carrier scheduling of communications with a first transmit-receive point (TRP) or a second TRP based on the DCI and the associated index.

[0016] Another innovative aspect of the subject matter described in the present disclosure can be implemented in a wireless device. Some implementations may include: a component for determining that a scheduled cell is configured to be scheduled by a scheduling cell; a component for receiving downlink control information (DCI) from the scheduling cell; a component for determining an association of the DCI and an index based on the received DCI; and a component for performing cross-carrier scheduling of communications with a first transmit-receive point (TRP) or a second TRP based on the DCI and the associated index.

[0017] Details of one or more implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and the following description. Other features, aspects, and advantages will become apparent from the description, drawings, and claims. Please note that the relative sizes of the following drawings may not be drawn to scale. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 A block diagram illustrating an example communication system is shown.

[0019] Figure 2 A component block diagram of an example computing system is shown.

[0020] Figure 3 A component block diagram of an example software architecture including a radio protocol stack for user and control planes in wireless communications is shown.

[0021] Figure 4 A component block diagram of an example system configured for managing paging monitoring by a processor of a wireless device is shown.

[0022] Figure 5A A process flow chart is shown, and Figure 5B-Figure 5I A schematic diagram of an example method for managing cross-carrier scheduling by a processor of a wireless device is shown.

[0023] Figure 6A-6J A process flow diagram of example operations that may be performed as part of a method for managing cross-carrier scheduling by a processor of a wireless device is shown.

[0024] Figure 7A component block diagram of an example network computing device is shown.

[0025] Figure 8 A component block diagram of an example wireless device is shown.

[0026] Like reference numbers and symbols in different drawings indicate like elements. DETAILED DESCRIPTION

[0027] The following description is directed to certain implementations for the purpose of describing the innovative aspects of the present disclosure. However, one of ordinary skill in the art will readily appreciate that the teachings herein can be applied in many different ways.

[0028] The described implementations may be implemented in any device, system, or network capable of transmitting and receiving radio frequency (RF) signals in accordance with any of the following: any Institute of Electrical and Electronics Engineers (IEEE) 16.11 standard, or any IEEE 802.11 standard, Bluetooth Standard, Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Global System for Mobile Communications (GSM), GSM / General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), Terrestrial Trunked Radio (TETRA), Wideband CDMA (W-CDMA), Evolution Data Optimized (EV-DO), 1xEV-DO, EV-DO Rev A, EV-DO Rev B, High Speed ​​Packet Access (HSPA), High Speed ​​Downlink Packet Access (HSDPA), High Speed ​​Uplink Packet Access (HSUPA), Evolved High Speed ​​Packet Access (HSPA+), Long Term Evolution (LTE), AMPS, or other signals or further implementations thereof for communication within a wireless, cellular or Internet of Things (IoT) network (such as a system utilizing 3G, 4G or 5G technology).

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

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

[0031] Multi-TRP operation may be defined for a given serving cell (e.g., a given component carrier). A first DCI sent from a first TRP may schedule a first PDSCH sent from the first TRP. A second DCI sent from a second TRP may schedule a second PDSCH sent from a second TRP. In some implementations, in order to enable a wireless device to monitor the first DCI and the second DCI sent from the first TRP and the second TRP, different control resource sets (CORESETs) may be used. In some implementations, the maximum allowed number of CORESETs may be 3 or more, such as 3, 4, 5, and the like. 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 for each CORESET, which may group the CORESETs into two groups. Each CORESET group may be indicated by a CORESET pool index value (e.g., CORESETPoolIndex=0 and CORESETPoolIndex=1). In some implementations, any distinction between TRPs is transparent to the wireless device. In some implementations, the wireless device may be configured by a higher layer parameter PDDCH-Configuration containing two different CORESETPoolIndex values ​​in a CORESET for an active bandwidth part (BWP) of a serving cell. For example, CORESETPoolIndex=0 may be associated with a CORESET identifier (ID) of 1 and a CORESET ID of 2, and CORESETPoolIndex=1 may be associated with a CORESET ID of 3 and a CORESET ID of 4. In some implementations, 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.

[0032] In the current network, multi-DCI based MTRP is supported only when the serving cell is self-scheduled. In the current network, CORESET may not be configured for cells scheduled across carriers. The current network fails to configure CORESET for cells scheduled across carriers, which prevents the implementation of multi-DCI based MTRP for cells scheduled across carriers in the current network. The current network's failure to configure CORESET for cells scheduled across carriers also 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.

[0033] In Type 1 (i.e., semi-static) HARQ-ACK, for each CC, a set of opportunities for candidate PDSCH reception is determined. For each CC, if a PDSCH is received during the opportunity for candidate PDSCH reception, the HARQ-ACK for the PDSCH is inserted at the corresponding position. Otherwise, a negative acknowledgement (NACK) is inserted. This is done on all configured downlink (DL) CCs. For multiple DCI, when joint feedback is configured, Type 1 (i.e., semi-static) HARQ-ACK includes defining two CC lists associated with two CORESETPoolIndex values. CCs configured with multiple DCI 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"). Then, the HARQ-ACK generation process is completed twice, once for the first set S0 and another time for the second set S1. After concatenating the two codebooks (i.e., two types of HARQ-ACK codebooks) generated from the two lists (i.e., S0 and S1), the joint feedback is sent in the same physical uplink control channel (PUCCH) resource. Since there is no CORESET configured for the 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 properly associated with the set of type 1 HARQ-ACK (i.e., S0 and S1).

[0034] In some implementations, communication operation options may be enabled, such as HARQ-ACK feedback corresponding to the PDSCH scheduled by each TRP. In some implementations, joint ACK-NACK feedback may be carried on the same PUCCH. In such an implementation, the position of the ACK-NACK bits in the joint HARQ-ACK codebook may be implemented as a function of the CORESET pool index in which the DCI scheduling the PDSCH is received. In some implementations, separate ACK-NACK feedback may be carried on separate PUCCHs. In such an implementation, if the ACK-NACK feedback is sent in the same timeslot, the separate codebook may be determined based on the CORESET pool index in which the DCI scheduling the PDSCH is received.

[0035] In some implementations, the wireless device may also determine certain communication operations (such as PDSCH scrambling or rate matching of PDSCH) based on the CORESET pool index. In some implementations, other communication operations may be determined based on the CORESET pool index, such as the interpretation of the Transmission Configuration Indicator (TCI) field (such as in a downlink DCI) or the Sounding Reference Signal (SRS) Resource Indicator (SRI) field (such as in an uplink DCI), the interpretation of the PUCCH Resource Indicator (PRI) / HARQ Process Number field, and other communication operations.

[0036] In some implementations where two PDSCHs completely or partially overlap (e.g., in time or frequency), different demodulation reference signal (DMRS) ports in different code division multiplexing (CDM) groups may be used for the two PDSCHs. In such implementations, the total number of layers should not exceed the number of layers supported by a given wireless device.

[0037] In some implementations, in order to support multi-PDCCH-based multi-TRP / plane transmission with intra-cell (same cell ID) and inter-cell (different cell IDs), certain RRC configurations can be used to link multiple PDCCH / PDSCH pairs with multiple TRPs. For example, one CORESET in a "PDCCH-configuration" can be configured to correspond to one TRP. In some implementations, for separate ACK / NACK feedback for PDSCH received from different TRPs, if the index is configured and applied to all component carriers, the wireless device can be configured to generate separate ACK / NACK codebooks identified by the index. In some implementations, the index used to generate the separate ACK / NACK codebook can be a higher layer signaling index for each CORESET.

[0038] In some implementations, if a higher layer signaling index for each CORESET is configured when generating separate ACK / NACK codebooks for CCs across all component carriers for M-DCI-based multi-TRP / plane transmission, the higher layer signaling index corresponding to different ACK / NACK codebooks may have different values. For example, for a dynamic codebook, counting the downlink allocation indicator (DAI) for DCI may be independent of CORESETs with different values ​​of the configured higher layer signaling index. As another example, for a semi-static codebook, for DCI / PDSCH, determining candidate PDSCH reception timings and HARQ-ACK information bits may be independent of CORESETs with different values ​​of the configured higher layer signaling index. In some implementations, at least for enhanced mobile broadband (eMBB) with multi-DCI non-coherent joint transmission (NCJT), in order to generate different PDSCH scrambling sequences, the RRC configuration may be enhanced to configure multiple data scrambling identities PDSCH (dataScramblingIdentityPDSCH).

[0039] In order to implement multi-TRP communication based on multiple DCIs, a determination may be made as to whether the scheduling cell can schedule the serving cell (scheduled cell). In some cases, the scheduling cell may not be configured to perform multi-TRP communication based on multiple DCIs. In some cases, two serving cells may be configured to schedule one scheduled cell. Such an implementation may reflect a relaxation of standard requirements (such as the standard requirements of 3GPP 5GNR Release 15), but may allow one of the scheduling DCIs to schedule only a subset of the layers. In some implementations, a determination may be made as to whether the serving cell can schedule a specific scheduled cell. In some cases, the scheduled cell may not be configured to perform multi-TRP communication based on multiple DCIs. In addition, it may be necessary to determine how to perform various communication operations that depend on the CORESET pool index in which the DCI is received, such as HARQ-Ack feedback, PDSCH scrambling, rate matching of PDSCH, and the like.

[0040] The implementation described herein provides a method for managing a wireless device to perform multi-TRP communications based on multiple DCIs. In some implementations, the DCI may be configured with additional information that can be used to associate the DCI with an index (such as a higher layer index, a CORESET pool index, or a TRP) when the DCI is received and cross-carrier signaling is enabled. In some implementations, the additional information may include separate fields in the DCI. In some implementations, the additional information may be indicated as part of the CIF. For example, a CIF value in a scheduling cell may indicate a first TRP of a scheduled cell, while another value of the CIF in the scheduling cell may indicate a second TRP of the same scheduled cell. In some implementations, the additional information may be used for a scheduled cell configured to perform multi-TRP operations based on multiple DCIs (such as determining communication operations such as HARQ-Ack, scrambling, rate matching operations, and other suitable communication operations).

[0041] In some implementations, a scheduled cell may be scheduled by two different scheduling cells. For example, when the scheduled cell is configured to perform multi-TRP operation based on multiple DCIs, and the two scheduling cells schedule data channels (such as PDSCH or PUSCH) that may be associated with different higher layer indices, different CORESET pool indices, or different TRPs. Such an implementation may reflect a relaxation of standard requirements (such as 3GPP 5G NR Release 15). In some implementations, if the scheduling cell is configured with two CORESET pool indices, the CORESET pool index in which the DCI is received may be ignored for cross-carrier scheduling. In some implementations, the wireless device may determine the communication operation based on additional information in the DCI. In some implementations, a TRP or CORSET group may not be required to determine the communication operation.

[0042] In some implementations, when the scheduled cell is configured to perform multi-TRP operation based on multiple DCI, the wireless device may determine communication operations (such as HARQ-Ack, scrambling, rate matching, etc.) using the CORESET pool index in which the DCI is received in the scheduling cell. In such an implementation, the DCI may not be configured with additional information. In some implementations, if the DCI is received in a CORESET having a higher layer index (such as a first or second CORESET pool index) with a first value or a second value in the scheduling cell, the wireless device may perform communication operations associated with the first TRP or the second TRP according to the first value or the second value. In some implementations, if the scheduled cell is not configured to perform multi-TRP operation based on multiple DCI, the wireless device may ignore the TRP or CORESET pool index used for communication operations. In some implementations, even if the scheduling cell is not configured with two CORESET pool indexes, the CORESET pool index may be configured with (or associated with) a higher layer index having a first value or a second value, all of which belong to the first CORESET pool index or the second CORESET pool index. In such an implementation, one scheduling cell cannot schedule both the CORESET pool index or TRP of a scheduled cell alone. In some implementations, a scheduled cell configured to perform multi-DCI based multi-TRP operation may be scheduled by two different scheduling cells configured to schedule data channels (such as PDSCH or PUSCH) associated with different indices (such as different higher layer indices, different CORESET pool indices, or different TRPs). Such an implementation may reflect a relaxation of standard requirements (such as 3GPP 5G NR Release 15).

[0043] Specific implementations of the subject matter described in the present disclosure may be implemented to achieve one or more of the following potential advantages. Some implementations enable wireless devices to manage cross-carrier scheduling with scheduling cells and scheduled cells. Cross-carrier scheduling can be used to reduce signal interference in heterogeneous network deployments using carrier aggregation, particularly 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 services and scheduling across different component carriers. In addition, cross-carrier scheduling allows wireless devices to be flexibly configured to monitor PDCCH in one or more component carriers, while data communications can be configured for more component carriers, which in turn can reduce wireless device complexity and increase network flexibility. In addition, when cross-carrier scheduling technology is combined with multi-TRP technology, different use cases can be enabled, such as one or more component carriers in FR1 scheduling PDSCH / PUSCH for component carriers in FR2, where PDSCH / PUSCH is received / transmitted using different beams corresponding to the two TRP directions.

[0044] The term "wireless device" is used herein to refer to any or all of the following: wireless router devices, wireless home appliances, cellular phones, smart phones, portable computing devices, personal or mobile multimedia players, laptop computers, tablet computers, smartbooks, ultrabooks, PDAs, wireless email receivers, multimedia Internet-enabled cellular phones, medical devices and equipment, biometric sensors / devices, wearable devices (including smart watches, smart clothing, smart glasses, smart wristbands, smart jewelry (e.g., smart rings and smart bracelets)), 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 machinery and appliances used in homes or businesses), wireless communication elements within autonomous and semi-autonomous vehicles, wireless devices fixed to or incorporated into various mobile platforms, global positioning system devices, and similar electronic devices that include memory, wireless communication components, and programmable processors.

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

[0046] 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, 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 circuits and tightly packaged (such as on a single motherboard or in a single wireless device). The proximity of the SOCs facilitates high-speed communication and the sharing of memory and resources.

[0047] Figure 1 A block diagram illustrating an example communication system 100 is shown. The communication system 100 may be a 5G NR network, or any other suitable network, such as an LTE network.

[0048] The communication system 100 may include a heterogeneous network architecture including a core network 140 and various wireless devices (in Figure 1 120a-120e). The communication system 100 may also include multiple base stations (shown 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 and may also be referred to as a NodeB, NodeB, LTE evolved NodeB (eNB), access point (AP), radio head, transmit receive point (TRP), new radio base station (NR BS), 5G NodeB (NB), next generation NodeB (gNB), etc. Each base station may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​a base station, a BS subsystem serving the coverage area, or a combination thereof, depending on the context in which the term is used.

[0049] 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., a radius of several kilometers) and may allow unrestricted access to wireless devices with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access to wireless devices with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access to wireless devices associated with the femto cell (e.g., wireless 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 shown, 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. In this document, the terms "eNB", "base station", "NR BS", "gNB", "TRP", "AP", "Node B", "gNodeB", "5G NR" and "cell" may be used interchangeably.

[0050] In some examples, the cell may not be fixed, and the geographic area of ​​the cell may move according to the location of the mobile base station. In some instances, the base stations 110a-110d may be interconnected with each other and to one or more other base stations or network nodes (not shown) 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).

[0051] The base stations 110a-110d may communicate with the core network 140 via a wired or wireless communication link 126. The wireless devices 120a-120e may communicate with the base stations 110a-110d via a wireless communication link 122.

[0052] The wired communication link 126 can use various wired networks (such as Ethernet, TV cable, telephone, fiber optic, and other forms of physical network connections), which can 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).

[0053] 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 wireless 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 of other wireless devices. Figure 1 In the example shown, a relay station 110d may communicate with the macro base station 110a and the wireless device 120d to facilitate communication between the macro base station 110a and the wireless device 120d. A relay station may also be referred to as a relay base station, relay base station, relay, etc.

[0054] The communication system 100 may be a heterogeneous network including different types of base stations, such as 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 higher 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).

[0055] A network controller 130 may be coupled to a set of base stations and may provide coordination and control for 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.

[0056] Wireless devices 120a, 120b, 120c may be dispersed throughout communication system 100, and each wireless device may be fixed or mobile. A wireless device may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, or the like.

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

[0058] The wireless communication links 122 and 124 may include multiple carrier signals, frequencies or frequency bands, each of which may include multiple logical channels. The wireless communication links may utilize one or more radio access technologies (RATs). Examples of RATs that may be used in the wireless communication links include 3GPP LTE, 3G, 4G, 5G (such as 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. Further examples of RATs that may be used in one or more wireless links 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).

[0059] Some wireless networks, such as LTE, use 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 commonly referred to as tones, bins, etc. Each subcarrier can be modulated with data. In general, modulation symbols are sent in the frequency domain using OFDM and in the time domain using 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 file transfer (FFT) size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth can also be 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.

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

[0061] Aggregation of multiple cells can support up to eight serving cells.Alternatively, NR can support a different air interface instead of the OFDM-based air interface.

[0062] Some wireless devices may be considered machine type communication (MTC), or evolved or enhanced machine type communication (eMTC) wireless devices. MTC and eMTC wireless 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, for example, a connection for or to a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link. Some wireless devices may be considered Internet of Things (IoT) devices, or may be implemented as NB-IoT (narrowband Internet of Things) devices. The wireless devices 120a-120e may be included in a housing that houses components of the wireless devices 120a-120e (such as a processor component, a memory component, a similar component, or a combination thereof).

[0063] Generally, any number of communication systems and any number of wireless networks can be deployed in a given geographic area. Each communication system and wireless network can support a specific radio access technology (RAT) and can operate on one or more frequencies. RAT can also be referred to as radio technology, air interface, etc. Frequency can also be referred to as carrier, frequency channel, etc. Each frequency can 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 can be deployed.

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

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

[0066] Therefore, in a wireless communication network that employs scheduled access to time-frequency resources and has a cellular configuration, a P2P configuration, and a mesh configuration, a scheduling entity and one or more slave entities may communicate using the scheduled resources.

[0067] In some implementations, two or more wireless devices (e.g., shown as wireless device 120a and wireless device 120e) may communicate directly (e.g., without using base stations 110-110d as an intermediary for communicating with each other) using one or more edge link (sidelink) channels. For example, the wireless devices 120a-120e may communicate using peer-to-peer (P2P) communication, 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 combinations thereof. In this case, the wireless devices 120a-120e may perform scheduling operations, resource selection operations, and other operations performed by base stations 110a-110d described elsewhere herein.

[0068] The base station and the wireless device may also communicate on a shared channel in a frequency band where the wireless communication network does not schedule access to time-frequency resources. Known as an unlicensed channel or unlicensed band, multiple communication devices may transmit at any time when other devices are not using the channel / band. To avoid interfering with other wireless devices using the channel / band, the base station or wireless device follows a listen before talk (LBT) procedure to monitor the channel / band for signals transmitted by other devices for a period of time, and may transmit if no other signals are detected during the LBT monitoring period.

[0069] In some implementations, the base station 110a-110d or the wireless device 120a-120e may be configured to perform one or more techniques associated with a channel occupancy time (COT) structure indication in an idle state or a connected state. For example, a processor in the wireless device 120a-120e may be configured to receive a COT structure indicator set (COT-SI) identifying a parameter set of a COT of the wireless device from the base station 110a-110d, decode at least one COT-SI of the COT-SI set to determine at least one parameter of the parameter set of the COT, and communicate with the base station 110a-110d according to the at least one parameter or based on the decoding of at least one COT-SI.

[0070] In some implementations, the wireless device 120a-120e may receive COT table configuration information. For example, the wireless device 120a-120e may receive a Remaining Minimum System Information (RMSI) message that identifies one or more small-sized COT tables for obtaining partial COT structure information. In this case, the small-sized COT table may be associated with less than a threshold size, such as less than a threshold number of entries, less than a threshold amount of bits, etc. In this case, the RMSI message may include configuration information for configuring the one or more COT tables, such as information identifying entries of the one or more COT tables, information identifying a concatenation of rows of the one or more COT tables, etc. Additionally or alternatively, the RMSI may also include a PDCCH monitoring configuration, a DCI format for monitoring COT-SI, a size of a COT-SI PDCCH or DCI, a bit position of information identifying row concatenation in the DCI, information identifying the number of bits for each row index, information identifying the number of concatenated row indexes, other bit indicators of other signaled parameters, a COT end symbol indicator, a COT pause start symbol indicator, a COT pause end symbol indicator, information related to triggering a random access channel (RACH) procedure, CG-UL information, service class information, LBT information, COT acquisition information, etc. For example, the wireless device 120a-120e may determine a control resource set (CORESET), a subband, a wideband, a search space set, an aggregation level set and a corresponding number of candidates, a radio network temporary identifier (RNTI), a time domain, a monitoring period, a monitoring offset, a length of the DCI, or similar parameters for monitoring COT-SI, a slot format indicator (SFI) DCI, etc. In this case, as described in more detail herein, the idle mode wireless device 120a-120e may be able to decode the COT-SI bits to indicate one or more ordered entries of the first COT table and the second COT table. Conversely, the connected mode wireless device 120a-120e may be able to decode the COT-SI bits of the first COT table, the second COT table, and the third COT table.

[0071] Additionally or alternatively, the wireless devices 120a-120e may determine other information about the COT structure. For example, when operating in an unlicensed band, the wireless devices 120a-120e may determine the COT duration. Additionally or alternatively, as described in more detail herein, the wireless devices 120a-120e may determine the concatenation of one or more rows of the COT table, the CG-UL behavior, etc.

[0072] In some implementations, the wireless device 120a-120e may receive and decode a set of COT-SIs. For example, the wireless device 120a-120e may receive a first COT-SI identifying an index value of a first COT table, a second COT-SI identifying an index value of a second COT table, a third COT-SI identifying an index value of a third COT table, and so on. In this case, the COT-SI may be a bit indicator of a DCI received when monitoring the PDCCH. In some implementations, the wireless device 120a-120e may determine one or more parameters for communicating with the BS 110a-110d based on the set of COT-SIs. For example, the wireless device 120a-120e may determine the LBT type based on whether the transmission opportunity is inside or outside the acquired COT. In another example, the COT-SI may trigger or enable a RACH opportunity within the acquired COT so that the idle mode wireless device 120a-120e transmits a RACH. In some implementations, the first COT-SI may include information identifying a COT end symbol, a COT duration (which may be implemented as a remaining COT duration indicator), a first COT pause start symbol, a first COT pause end symbol, a second COT pause start symbol, a second COT pause end symbol, etc. In this case, the first COT-SI may explicitly identify the remaining COT duration and the COT pause indicator in the DCI. In some cases, information identifying symbol positions, such as a COT end symbol identifier, a first COT pause start symbol identifier, a first COT pause end symbol identifier, a second COT pause start symbol identifier, a second COT pause end symbol identifier, etc., may be indicated as an offset from a current position.

[0073] In some implementations, the wireless device 120a-120e may receive and decode a set of COT-SIs based on the state of the wireless device. For example, an idle mode wireless device 120a-120e may decode the COT-SIs of a first COT table and a second COT table, and a connected mode wireless device 120a-120e may decode the COT-SIs of a first COT table, a second COT table, and a third COT table. In some implementations, the wireless device 120a-120e may receive the COT-SI via a single PDCCH. For example, the wireless device 120a-120e may receive multiple bit indicators in a single PDCCH for multiple COT tables. Additionally or alternatively, the wireless device 120a-120e may receive multiple bit indicators via multiple PDCCHs associated with different frequency resources, time resources, monitoring cycles, monitoring configurations, and the like.

[0074] In some implementations, the COT-SI and the corresponding COT tables may be arranged in layers. For example, the wireless devices 120a-120e may receive multiple indicators related to multiple COT tables (such as a set of three COT tables). In this case, the wireless devices 120a-120e may receive more and more information about the COT structure as additional resources become available, rather than using a relatively large single resource to signal all information about the COT structure.

[0075] In some implementations, the wireless device 120a-120e may receive multiple COT tables in different incremental phases. For example, the wireless device may receive a first COT table and a second COT table via RMSI, and may receive a third COT table after connection and via a wireless device-specific RRC message. In another example, the first COT table may be stored, and the wireless device 120a-120e may receive a first portion of a third COT table in the RMSI, and receive a second portion of the third COT table in a wireless device-specific RRC message after connection. In this case, the first portion of the third COT table may be the second COT table.

[0076] In some implementations, the wireless device 120a-120e may determine a specific set of information about the COT structure based on the first COT table. For example, with respect to the first COT table, the wireless device 120a-120e may determine whether each symbol in a time slot is within or outside the COT without indicating whether the symbol is for UL or DL. In this case, the number of rows and entries of the first COT table may be relatively short, such as a set of 8 rows and a set of 14 columns, because the first COT table is configured through RMSI, and the size of the RMSI may be limited; however, the wireless device 120a-120e may receive an indicator via DCI to concatenate a set of row index levels. In this way, the wireless device 120a-120e is able to receive a single COT-SI index of the first COT table that identifies the COT structure of multiple upcoming time slots. As another example, the first COT table may indicate whether multiple time slots or symbols are within or outside the COT via a single row.

[0077] In some implementations, the wireless device 120a-120e may combine COT-SI information about the first COT table with other COT information received through the COT-SI or separately from the COT-SI to determine the COT structure. For example, the wireless device 120a-120e may receive a COT duration indicator (which may be indicated using a remaining COT duration indicator), a COT pause indicator, etc. in the DCI to be combined with information about whether a particular symbol or time slot is inside or outside the COT. In some implementations, the COT pause indicator may indicate the start of a COT pause, the length of a COT pause, the end of a COT pause, etc. In some implementations, the COT pause indicator may use a specific identifier. For example, the wireless device 120a-120e may interpret a COT outside indication ("O" or "Out") arranged between multiple COT inside indications ("I's" or "In's") as a COT pause indicator. Additionally or alternatively, the wireless devices 120a-120e may receive an explicit COT pause indicator (which may be denoted as "P" or "Pause"), COT start symbol and end symbol identifiers from which the wireless devices 120a-120e may derive a COT pause, or the like.

[0078] In some implementations, the wireless device 120a-120e may receive a first COT-SI that explicitly includes a COT end symbol or a COT duration indicator (which may be a remaining COT duration indicator), a COT pause start symbol, and a COT end symbol. In this case, the wireless device 120a-120e may not receive the first COT table.

[0079] Additionally or alternatively, with respect to the second COT table, the wireless device 120a-120e may determine whether a timeslot is allocated to a downlink ("D"), allocated to an uplink ("U"), flexibly allocated ("F"), included in a COT pause ("O" or "P"), etc. In this case, the second COT table provides partial timeslot information, such as providing one of a timeslot level indication, a mini-slot level indication, a symbol group level indication, etc., rather than a multi-level indication, thereby reducing resource utilization. In some implementations, the second COT table may identify timeslot allocations for multiple timeslots per index, but less than the entirety of the COT. In this case, the wireless device 120a-120e may receive a COT-SI DCI to concatenate multiple row indices to allow signaling of a larger portion of the COT or the entirety of the COT.

[0080] In some implementations, the second COT table may be a truncation of the third COT table. For example, the second COT table may include a subset of the rows of the third COT table (such as the first row or the first few rows). In this way, the size limit of the table configured by the RMSI may be observed. In some implementations, the wireless device 120a-120e may receive a COT-SI DCI of the second COT table, which identifies a row not included in the second COT table (such as an index greater than the maximum index of the second COT table). In this case, the wireless device 120a-120e may determine that a set of time slots is associated with a default configured allocation (such as an unknown allocation), and the wireless device may communicate according to the default configured allocation. As another example, each row in the second COT table may include information identifying the length of the COT duration, the number of DL time slots, the number of DL symbols, the number of flexible symbols, the number of UL symbols, the number of UL time slots, etc.

[0081] Additionally or alternatively, with respect to the third COT table, the wireless device 120a-120e may determine the entirety of the COT structure at the symbol level. For example, the third COT table may include information identifying whether each symbol is allocated as a DL symbol, a UL symbol, a flexible symbol, etc. In some implementations, the third COT table may be a slot format combination table that identifies the slot format of the symbol for the indicated number of consecutive slots. In some implementations, the information derived from the third COT table may override the information derived from the second COT table. For example, when a symbol is identified as a flexible allocation based on the second COT table, the wireless device 120a-120e may determine that the flexible allocation will be a UL allocation based on the third COT table.

[0082] In some implementations, the wireless device 120a-120e may receive other information related to the COT-SI. For example, the wireless device 120a-120e may receive information identifying the size of the DCI, information identifying the position of a bit identifying a COT table index within the DCI, the number of concatenated rows of the COT table, etc. Additionally or alternatively, the wireless device 120a-120e may receive information identifying the current position of the start of the COT, the service priority category of the COT, whether the base station 110a-110d or another wireless device 120a-120e has acquired the COT, dynamically triggered physical RACH (PRACH) resource information, dynamically triggered PRACH enablement or triggering message, LBT type of the COT, CG-UL parameters, two-stage grant resources and triggering information, etc.

[0083] In some implementations, the wireless device 120a-120e may determine specific CG-UL behavior based on CG-UL parameters. For example, if a Category Type 4 LBT process is configured and a COT start has not been detected, the wireless device 120a-120e may determine that the CG-UL is allowed. Additionally or alternatively, the wireless device 120a-120e may cancel the CG-UL when a COT start is detected but a COT-SI has not been received or has not been processed, etc. Additionally or alternatively, the wireless device 120a-120e may avoid canceling the CG-UL if a scheduled grant is not detected. Additionally or alternatively, the wireless device 120a-120e may cancel the CG-UL when a time slot is allocated for the DL at a time within the COT-SI and when the COT-SI is detected and processed by the wireless device 120a-120c. Additionally or alternatively, the wireless devices 120a-120e may avoid canceling the CG-UL when allocating the time slot to the UL and may observe the behavior of the signaling notification associated with the CG-UL parameters when allocating the time slot as a flexible time slot.

[0084] In some implementations, the wireless device 120a-120e may receive an explicit SFI for each time slot of the COT instead of receiving a COT-SI. For example, the wireless device 120a-120e may receive a DCI based on a stored table associated with an unlicensed spectrum frame structure, the DCI conveying an explicit SFI indicating the time slot format of the entirety of the COT. Based on the fact that the stored table is smaller than the time slot format combination table, such as based on the unlicensed spectrum associated with the maximum COT size less than a threshold, the number of bits used to signal the COT structure in the DCI is reduced. In this case, the wireless device 120a-120e may determine that the DCI conveys an explicit SFI based on a bit indicator in the DCI indicating that the DCI conveys an explicit SFI instead of one or more COT-SIs. In some implementations, the DCI may signal a COT table that includes symbols representing time slots that are not within the COT. In some implementations, the DCI may include an explicit COT duration indicator to enable the wireless device 120a-120e to determine the length of the COT.

[0085] In some implementations, the wireless devices 120a-120e may decode one or more COT-SIs and may communicate according to the COT structures identified by the one or more COT-SIs. Each COT-SI may include information about the TXOP, such as the remaining COT duration, the start and length of a pause within the TXOP, a DL or UL slot indication of a slot in the TXOP, an indication of subband usage of the TXOP, etc.

[0086] Figure 2 A component block diagram of an example computing system 200 is shown. Figure 1 and Figure 2 , the computing system 200 can be implemented on multiple single-processor and multi-processor computer systems, including systems on a chip (SOC) or system-in-package (SIP). The computing system 200 may include 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 wireless device such as a base station 110a via an antenna (not shown). In some implementations, the first SOC 202 operates as a central processing unit (CPU) of the wireless device, which executes instructions of a software application by performing arithmetic, logic, control, and input / output (I / O) operations specified by the instructions. In some implementations, the second SOC 204 can operate as a dedicated processing unit. For example, the second SOC 204 can operate as a dedicated 5G processing unit, which is responsible for managing large-capacity, high-speed (e.g., 5Gbps, etc.) or very high frequency short wavelength (such as 28GHz millimeter wave spectrum, etc.) communications.

[0087] 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 (such as a vector coprocessor) connected to one or more processors, memory 220, custom circuits 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, multiple millimeter wave (mmWave) transceivers 256, memory 258, and various additional processors 260 (such as an application processor, a packet processor, etc.).

[0088] Each processor 210, processor 212, processor 214, processor 216, processor 218, processor 252, processor 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 (such as FreeBSD, LINUX, OS X, etc.) and a processor that executes a second type of operating system (such as MICROSOFT WINDOWS 10). In addition, any one or all of the processors 210, processor 212, processor 214, processor 216, processor 218, processor 252, processor 260 may be included as part of a processor cluster architecture (such as a synchronous processor cluster architecture, an asynchronous or heterogeneous processor cluster architecture, etc.).

[0089] The first SOC 202 and the second SOC 204 may include various system components, resources, and custom circuits 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 presentation 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 for supporting processors and software clients running on wireless devices. The system components and resources 224 or custom circuits 222 may also include circuits for interfacing with peripheral devices such as cameras, electronic displays, wireless communication devices, external memory chips, and the like.

[0090] The first SOC 202 and the second SOC 204 can communicate via an interconnect / bus module 250. Various processors 210, processor 212, processor 214, processor 216, processor 218 can be interconnected to one or more memory elements 220, system components and resources 224, custom circuits 222, and thermal management units 232 via interconnect / bus modules 226. Similarly, processor 252 can be interconnected to power management units 254, millimeter wave transceivers 256, memory 258, and various additional processors 260 via interconnect / bus modules 264. The interconnect / bus modules 226, 250, 264 can include reconfigurable logic gate arrays or implement bus architectures (e.g., CoreConnect, AMBA, etc.). Communications can be provided by advanced interconnects such as high-performance networks on chips (NoCs).

[0091] The first SOC 202 and the second SOC 204 may also include input / output modules (not shown) for communicating with SOC external resources such as clock 206 and voltage regulator 208. Resources external to the SOC such as clock 206, voltage regulator 208 may be shared by two or more internal SOC processors / cores.

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

[0093] Figure 3 A component block diagram of an example software architecture 300 is shown, which includes a radio protocol stack for user and control planes in wireless communications. Figure 1-Figure 3, the software architecture 300 may include wireless protocol stacks for user and control planes in wireless communications between a base station 350 (such as base stations 110a-110d) and a wireless device 320 (such as wireless devices 120a-120e, 200). The wireless device 320 may implement the software architecture 300 to communicate with a base station 350 of a communication system (such as the communication system 100). In some implementations, the layers in the software architecture 300 may form logical connections with corresponding layers in the software of the base station 350. The software architecture 300 may be distributed between one or more processors (such as processor 212, processor 214, processor 216, processor 218, processor 252, processor 260). Although shown 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 (such as two protocol stacks associated with two SIMs, respectively, in a dual SIM wireless communication device). 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 communications, or may include additional protocol stacks that support any of a variety of standards and protocols for wireless communications.

[0094] The software architecture 300 may include a non-access stratum (NAS) 302 and an access stratum (AS) 304. The NAS 302 may include functions and protocols for supporting packet filtering, security management, mobility control, session management, and services and signaling between (one or more) SIMs (such as SIM 204) of a wireless device and its core network 110. The AS 304 may include functions and protocols for supporting communication between (one or more) SIMs (such as SIM 204) and supported access network entities (such as base stations). Specifically, the AS 304 may include at least three layers (Layer 1, Layer 2, and Layer 3), each of which may include various sublayers.

[0095] In the user and control planes, layer 1 (L1) of the AS 304 may be a physical layer (PHY) 306, which may oversee functions that allow transmission or reception over an air interface via a wireless transceiver (e.g., 266). Examples of such physical layer 306 functions may include cyclic redundancy check (CRC) appending, coding blocks, scrambling and descrambling, modulation and demodulation, signal measurement, MIMO, etc. The physical layer may include various logical channels, including a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH).

[0096] In the user and control planes, 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 implementations, 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 that terminates at base station 350.

[0097] 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 implementations, RRC sublayer 313 may provide functionality including broadcasting system information, paging, and establishing and releasing RRC signaling connections between wireless devices 320 and base stations 350.

[0098] In some implementations, 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, ciphering, 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, decryption, and header decompression.

[0099] 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, the functions of the RLC sublayer 310 may include reordering of data packets to compensate for out-of-order reception, reassembly of upper layer data packets, and ARQ.

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

[0101] While the software architecture 300 may provide functionality for sending data over a physical medium, the software architecture 300 may also include at least one host layer 314 to provide data transmission services to various applications in the wireless device 320. In some implementations, the application-specific functionality provided by the at least one host layer 314 may provide an interface between the software architecture and the general purpose processor 206.

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

[0103] Figure 4 A component block diagram of an example system 400 configured for managing paging monitoring by a processor of a wireless device is shown. Figure 1-Figure 4 In some implementations, the system 400 may include a wireless device 402 (eg, wireless devices 120a - 120e , wireless device 200 , wireless device 320 ) and a base station 404 (eg, base stations 110a - 110d , base station 350 ).

[0104] The wireless device 402 may include one or more processors 428 coupled to an electronic memory 426 and a wireless transceiver 266. The wireless transceiver 266 may be configured to receive messages to be sent in uplink transmissions from the one or more processors 438 and transmit the messages to the wireless communication network via the base station 404 via an antenna (not shown). Similarly, the wireless transceiver 266 may be configured to receive messages from the base station 404 and pass the messages (such as via a modem that demodulates the messages) to the one or more processors 438. The wireless device 402 may be configured by machine-readable instructions 406. 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 the following: a cell determination module 408, a DCI reception module 410, a DCI determination module 412, a scheduling performance module 414, an association determination module 416, an indication determination module 418, a scheduling cell determination module 420, a data communication operation performance module 422, a group determination module 424, a group value determination module 426, or other instruction modules.

[0105] The cell determination module 408 may be configured to determine whether a scheduling cell or a scheduled cell is configured to perform multi-TRP communication based on multi-DCI.

[0106] 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.

[0107] The DCI determination module 412 may be configured to determine an association of the DCI with an index based on the received DCI. In some implementations, the index may include a CORESET pool index. In some implementations, the index may include one of a first TRP and a second TRP. In some implementations, each CORESET or TRP may be associated with a value of the index.

[0108] The scheduling performance module 414 may be configured to perform cross-carrier scheduling of communications with the first TRP or the second TRP based on the DCI and the associated index. In some implementations, the scheduling performance module 414 may be configured to perform cross-carrier scheduling of communications with the first TRP and the second TRP based on the determined index. In some implementations, the scheduling performance module 414 may be configured to perform cross-carrier scheduling of communications with the first TRP based on the DCI and the associated index, and to perform cross-carrier scheduling of communications with the second TRP based on the second DCI and the associated second index. In some implementations, the scheduling performance module 414 may be configured to perform cross-carrier scheduling of communications with the first TRP and the second TRP based on the higher layer index value of the CORESET pool index. In some implementations, the scheduling performance module 414 may be configured to perform cross-carrier scheduling of communications with the first TRP according to the communication link scheduling from the scheduling cell associated with the index, and to perform cross-carrier scheduling of communications with the second TRP according to the communication link scheduling from the second scheduling cell associated with the second index.

[0109] The association determination block 416 may be configured to determine the association of the DCI with the index based on a field in the payload of the DCI.

[0110] The indication determination block 418 may be configured to determine the indication of the index from a field added to the payload of the DCI. In some implementations, the indication determination module 418 may be configured to determine the indication of the index from a CIF in the DCI. In some implementations, the indication determination module 418 may be configured to determine whether the CIF corresponds to a value indicating a scheduled cell.

[0111] The scheduling cell determination module 420 may be configured to determine whether the scheduling cell is configured with two or more CORESET pool indexes. The scheduling cell determination module 420 may be configured to determine whether the scheduling cell is configured to perform multi-TRP operation based on multi-DCI.

[0112] The data communication operation module 422 may be configured to perform a data communication operation according to the index. In some implementations, the data communication operation module 422 may be configured to perform a data communication operation with the first TRP or the second TRP. As a non-limiting example, the data communication operation may include at least one of: HARQ-ACK feedback, PDSCH scrambling, and PDSCH rate matching.

[0113] In some implementations, the data communication operation module 422 may be configured to perform data communication operations according to the CORESET pool index in which the DCI is received. In some implementations, the data communication operation module 422 may be configured to perform data communication operations between the scheduled cell and the first TRP or the second TRP according to the determined CORESET pool index value. In some implementations, the data communication operation module 422 may be configured to perform data communication operations without reference to the CORESET pool index in which the DCI is received.

[0114] The group determination module 424 may be configured to determine the CORESET pool index in which the DCI is received. The group value determination module 426 may be configured to determine a CORESET pool index value associated with each of the two CORESET pool indexes.

[0115] The wireless device 402 may include electronic memory 436, one or more processors 438, and other components. The wireless device 402 may include communication links or ports to enable information to be exchanged with a network or other computing platform. Figure 4 The illustration of the wireless device 402 in FIG. 4 is not intended to be limiting. The wireless device 402 may include multiple hardware, software, or firmware components that operate together to provide the functionality attributed to the wireless device 402 herein.

[0116] Electronic storage 436 may include non-transitory storage media that electronically stores information. The electronic storage media of electronic storage 436 may include one or both of system memory that is provided integrally with wireless device 402 (i.e., substantially non-removable) or removable memory that is removably connected to wireless device 402 via, for example, a port (such as a universal serial bus (USB) port, a firewire port, etc.) or a drive (such as a disk drive, etc.). Electronic storage 436 may include one or more of the following: optically readable storage media (such as optical disks, etc.), magnetically readable storage media (such as magnetic tape, magnetic hard drives, floppy disk drives, etc.), charge-based storage media (such as EEPROM, RAM, etc.), solid-state storage media (such as flash drives, etc.), or other electronically readable storage media. Electronic storage 436 may include one or more virtual storage resources (such as cloud storage, virtual private networks, or other virtual storage resources). Electronic storage 436 may store software algorithms, information determined by processor(s) 438, information received from wireless device 402, or other information that enables wireless device 402 to operate as described herein.

[0117] The processor(s) 438 may be configured to provide information processing capabilities in the wireless device 402. Thus, the processor(s) 438 may include one or more of a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, or other mechanism for electronically processing information. Figure 4 Processor(s) 438 are shown as a single entity, but this is for illustration purposes only. In some implementations, processor(s) 438 may include multiple processing units. These processing units may be physically located within the same device, or processor(s) 438 may represent processing functions of multiple devices operating in coordination. Processor(s) 438 may be configured to execute modules 408-426 or other modules. Processor(s) 438 may be configured to execute modules 408-426 or other modules through software; hardware; firmware; some combination of software, hardware, or firmware; or other mechanisms for configuring processing capabilities on processor(s) 438. As used herein, the term "module" may refer to any component or collection of components that perform the functions attributed to a module. This may include one or more physical processors during the execution of processor-readable instructions, processor-readable instructions, circuits, hardware, storage media, or any other component.

[0118] The description of the functionality provided by the different modules 408-426 described below is for illustrative purposes and not for limitation, as any of the modules 408-426 may provide more or less functionality than described. For example, one or more of the modules 408-426 may be eliminated, and some or all of their functionality may be provided by other modules in the modules 408-426. As another example, the processor(s) 438 may be configured to execute one or more additional modules that may perform some or all of the functionality attributed below to one of the modules 408-426.

[0119] Figure 5A A process flow chart is shown, and Figure 5B-Figure 5I A schematic diagram of an example method 500 for managing cross-carrier scheduling by a processor of a wireless device is shown. Figure 1-Figure 5I , the method 500 may be implemented by a processor (such as 212, 216, 252, or 260) of a wireless device (such as the wireless devices 120a-120e, the wireless device 200, the wireless device 320).

[0120] In block 502, the processor may determine that the scheduled cell is configured to be scheduled by the scheduling cell. In some implementations, the processor may obtain or receive a serving cell signal from the scheduled cell.

[0121] In block 504, the processor may receive downlink control information (DCI) from the scheduling cell. In some implementations, the scheduling cell may be configured to perform multi-DCI based multi-TRP communications. In some implementations, the scheduling cell may not be configured to perform multi-DCI based multi-TRP communications. In some implementations, the scheduling cell may be configured by a parameter PDCCH-configuration including two (possibly different) CORESET pool index values ​​in a CORESET for an active bandwidth portion (BWP) of the scheduling cell. In some implementations, the scheduled cell may be configured to perform multi-PDSCH multi-TRP communications.

[0122] In block 506, the processor may determine that the DCI schedules the scheduled cell.

[0123] In block 508, the processor may determine an association of downlink control information with an index based on the received DCI. In some implementations, the index may include a CORESET pool index. In some implementations, the index may include one of a first TRP and a second TRP.

[0124] In box 510, the processor may perform cross-carrier scheduling of communications with the first TRP or the second TRP based on the DCI and the associated index. In some implementations, the processor may initiate cross-carrier scheduling of communications with the first TRP or the second TRP based on the DCI and the associated index. In some implementations, performing cross-carrier scheduling of communications with the first TRP or the second TRP based on the DCI and the associated index may also include: performing data communication operations between the scheduled cell and the first TRP or the second TRP, wherein the data communication operations include at least one of the following: hybrid automatic repeat request (HARQ)-ACK feedback, physical downlink shared channel (PDSCH) scrambling, and PDSCH rate matching.

[0125] In some implementations, the scheduling cell may be configured by a PDCCH-configuration parameter including two CORESET pool index values ​​in a CORESET for an active bandwidth portion (BWP) of the scheduling cell. In some implementations, the scheduled cell may be configured to perform multi-PDSCH multi-TRP communication. In some implementations, the scheduling cell may be configured by a PDCCH-configuration parameter including one CORESET pool index value in all CORESETs for an active bandwidth portion (BWP) of the scheduled cell, or may not be configured with a CORESET pool index value.

[0126] Method 500 can be implemented in various scenarios. Figure 5B , the scheduling cell and the scheduled cell may each be configured by a PDCCH-configuration parameter including two CORESET pool index values ​​(such as a first CORESET pool index value and a second CORESET pool index value) in a CORESET for an active bandwidth part (BWP) of the scheduled cell. In some implementations, the scheduling cell may be configured to perform multi-TRP operation based on multi-DCI, where some CORESETs may be associated with a first CORESET pool index value and other CORESETs may be associated with a second CORESET pool index value. In some implementations, the scheduled cell may be configured to perform multi-PDSCH (or multi-PUSCH) multi-TRP communication.

[0127] As another example, refer to Figure 5C , the scheduling cell may be configured to perform multi-DCI based multi-TRP operation, where some CORESETs may be associated with a first CORESET pool index value and other CORESETs may be associated with a second CORESET pool index value. The scheduled cell may not be configured to perform multi-PDSCH (or multi-PUSCH) multi-TRP operation.

[0128] As another example, refer to Figure 5D , the scheduling cell may not be configured to perform multi-DCI based multi-TRP operation, where one or more CORESETs are not associated with a CORESET pool index value, or all CORESETs are associated with the same CORESET pool index value. The scheduled cell may be configured to perform multi-PDSCH (or multi-PUSCH) multi-TRP operation.

[0129] refer to Figure 5E In some implementations, a scheduling cell may be configured to schedule a scheduled cell (i.e., provide scheduling information to the scheduled cell), and the scheduled cell is configured to perform multi-PDSCH (or multi-PUSCH) multi-TRP operations. In some implementations, the scheduling cell may be configured to perform multi-DCI-based multi-TRP operations. In some implementations, the scheduling cell may not be configured to perform multi-DCI-based multi-TRP operations. For example, as part of a cross-carrier configuration, a scheduled cell may be configured to be scheduled by a scheduling cell with a cell ID=1. In addition, two CIF values ​​may be provided as part of the cross-carrier configuration. The first CIF value (corresponding to the first TRP or the first index) may be equal to a value of 3, and the second CIF value (corresponding to the second TRP or the second index) may be equal to a value of 5. Once a user equipment (UE) is configured with such a cross-carrier configuration, the UE may determine the association between the DCI received in the scheduling cell and the index (such as TRP) in the scheduled cell based on the value of the CIF. For example, if the CIF in the DCI in the scheduling cell is equal to 3, it is associated with the first TRP in the scheduled cell, and if it is equal to 5, it is associated with the second TRP in the scheduled cell.

[0130] refer to Fig. 5F In some implementations, two scheduling cells, each configured with a different cell ID, may be configured to schedule a scheduled cell configured to perform multi-TRP operations based on multiple PDSCHs (or multiple PUSCHs). In this case, the cross-carrier configuration in the scheduled cell may consist of two cell IDs as scheduling cells, whose corresponding CIF values ​​are included in the configuration. In this example, the DCI received in the cell with ID=1 (CIF value of 3) is associated with the first TRP in the scheduled cell, and the DCI received in the cell with ID=4 (CIF value of 5) is associated with the second TRP.

[0131] refer to Figure 5GIn some implementations, a scheduling cell configured with two TRPs or CORESET pool indices may be configured to schedule a scheduled cell configured to perform multiple TRPs based on multiple PDSCHs (or multiple PUSCHs). The arrow indicates the association of the CORESET pool index in the scheduling cell with the index or TRP in the scheduled cell.

[0132] refer to Figure 5H In some implementations, two scheduling cells each configured with two TRPs or CORESET pool indices may be configured to schedule a scheduled cell configured to perform multiple TRPs based on multiple PDSCHs (or multiple PUSCHs). The arrow indicates the association of the CORESET pool index in the corresponding scheduling cell with the index or TRP in the scheduled cell.

[0133] refer to Fig.5I In some implementations, two scheduling cells each configured with a different TRP or CORESET pool index may be configured to schedule a scheduled cell configured to perform multiple TRPs based on multiple PDSCHs (or multiple PUSCHs). In some implementations, in a first scheduling cell, all CORESETs may be associated with a first value of the CORESET pool index, and in a second scheduling cell, all CORESETs may be associated with a second value of the CORESET pool index. The arrows indicate the association of the CORESET pool index in the respective scheduling cells with the index or TRP in the scheduled cell.

[0134] Figure 6A-6J A process flow diagram illustrating example operations that may be performed as part of a method 500 for managing cross-carrier scheduling by a processor of a wireless device. Figure 1-6J , the example operations may be implemented by a processor of a wireless device (such as wireless devices 120a - 120e , wireless device 200 , wireless device 320 ).

[0135] refer to Fig. 6A , in block 506 ( Figure 5A In some implementations following the operation of ), the processor may determine, in block 602, the association of the DCI with the index based on a field in the payload of the DCI.

[0136] The processor may then execute block 510 ( Figure 5A ) operation.

[0137] refer to Figure 6B , in block 506 ( Figure 5A ) in some implementations following the operation of , the processor may determine, in block 604, an indication of the index from a field added to the payload of the DCI.

[0138] The processor may then execute block 510 ( Figure 5A ) operation.

[0139] refer to Figure 6C , in block 506 ( Figure 5A ), the processor may perform, in block 606, an indication of determining an index from a carrier indicator field (CIF) in the DCI. In some implementations, the CIF may indicate one of a first higher layer parameter and a second higher layer parameter, each parameter being associated with a value of an index in the CIF. In some implementations, the CIF may correspond to a first value indicating a scheduled cell, and the second DCI includes a second CIF corresponding to a second value indicating the scheduled cell. In some implementations, the first higher layer parameter may correspond to a CORESET pool index of 0, and the second higher layer parameter may correspond to a CORESET pool index of 1. In some implementations, the scheduled cell may be configured by a PDCCH-configuration parameter including two CORESET pool index values ​​in a CORESET for an active bandwidth portion (BWP) of the scheduled cell.

[0140] In block 608, the processor may perform cross-carrier scheduling of communications with the first TRP or the second TRP based on the determined index.

[0141] refer to Fig.6D , in block 606 ( Figure 6C ), the processor may receive a second DCI from a second scheduling cell in block 610. For example, in some implementations, the scheduled cell may be configured by a PDCCH-configuration parameter including two CORESET pool index values ​​in a CORESET for an active bandwidth part (BWP) of the scheduling cell.

[0142] In block 612, the processor may determine an association of the second DCI with a second index based on the received second DCI.

[0143] In box 614, the processor can perform cross-carrier scheduling of communications with the first TRP based on the DCI and the associated index, and perform cross-carrier scheduling of communications with the second TRP based on the second DCI and the associated second index.

[0144] refer to Fig. 6E , in block 602 ( Fig. 6A ), the processor may determine in block 616 that the scheduling cell is configured with two or more CORESET pool indexes.

[0145] In block 618, the processor may perform data communication operations for the scheduled cells according to the two or more CORESET pool indexes.

[0146] refer to Fig. 6F , in block 618 ( Fig. 6E ), the processor may, in block 620, ignore the CORESET pool index in which the DCI was received.

[0147] In block 622, the processor may perform data communication operations for the scheduled cell without reference to the CORESET pool index in which the DCI was received.

[0148] refer to Figure 6G , in block 508 ( Figure 5A ), the processor may determine in block 624 the CORESET pool index in which the DCI was received.

[0149] In block 626, the processor may perform a data communication operation according to the CORESET pool index in which the DCI was received.

[0150] refer to Figure 6H , in block 626 ( Figure 6G ), the processor may determine in block 628 that the scheduled cell is configured by a PDCCH-configuration parameter including two CORESET pool index values ​​in a CORESET for an active bandwidth portion (BWP) of the scheduled cell.

[0151] In block 630 , the processor may perform operations including determining two CORESET pool index values.

[0152] In box 632, the processor can perform operations including performing data communication operations between the scheduled cell and the first TRP or the second TRP based on the determined CORESET pool index value.

[0153] refer to Fig.6I , in block 626 ( Figure 6G ), the processor may determine in block 634 whether the scheduled cell is configured by a PDCCH-configuration parameter including two CORESET pool index values ​​in a CORESET for an active bandwidth part (BWP) of the scheduled cell.

[0154] In block 635, the processor may ignore the CORESET pool index in which the DCI is received in response to determining that the scheduled cell is not configured by a PDCCH-configuration parameter including two CORESET pool index values ​​in a CORESET for an active bandwidth part (BWP) of the scheduled cell.

[0155] In block 636, the processor may perform operations including performing data communication operations for the scheduled cell without reference to the CORESET pool index in which the DCI was received.

[0156] refer to Figure 6J In some implementations, the index may include a first CORESET index value for all CORESET configurations in the scheduled cell, and the second index may include a second CORESET pool index value for all CORESET configurations in the second scheduling cell. In some implementations, at block 626 ( Figure 6G ), the processor may perform cross-carrier scheduling of communication with the first TRP according to the communication link scheduling from the scheduling cell associated with the index in box 640, and perform cross-carrier scheduling of communication with the second TRP according to the communication link scheduling from the second scheduling cell associated with the second index.

[0157] Figure 7 Component block diagram of an example network computing device 700 is shown. In some implementations, the wireless network computing device 700 can be used as a network element of a communication network, such as a base station. The network computing device 700 can include at least Figure 7 Components shown. Reference Figure 1-Figure 7 , the network computing device 700 may typically include a processor 701 coupled to a volatile memory 702 and a large capacity non-volatile memory such as a disk drive 703. The network computing device 700 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 706 coupled to the processor 701. The network computing device 700 may also include a network access port 704 (or interface) coupled to the processor 701 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 700 may include one or more antennas 707 for sending and receiving electromagnetic radiation, which may be connected to a wireless communication link. The network computing device 700 may include additional access ports such as USB, Firewire, Thunderbolt, etc. for coupling to peripherals, external memory or other devices.

[0158] Figure 81 shows a component block diagram of an example wireless device. In some implementations, the wireless device can be implemented as various wireless devices (e.g., wireless device 102, wireless device 200, wireless device 320), examples of which are shown in FIG. Figure 8 800 is shown in the form of a smart phone 800. The smart phone 800 may include a first SOC 202 (e.g., SOC-CPU) coupled to a second SOC 204 (e.g., a 5G-enabled SOC). The first SOC 202 and the second SOC 204 may be coupled to internal memory 806, 816, a display 812, and a speaker 814. Additionally, the smart phone 800 may include an antenna 804 for sending and receiving electromagnetic radiation, which may be connected to a wireless data link or cellular phone transceiver 808, which is coupled to one or more processors in the first SOC 202 or the second SOC 204. The smart phone 800 typically also includes a menu selection button or rocker switch 820 for receiving user input.

[0159] The typical smart phone 800 also includes a sound coding / decoding (CODEC) circuit 810, 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 generate sound. In addition, one or more processors in the first SOC 202 and the second SOC 204, the wireless transceiver 808 and the codec 810 may include a digital signal processor (DSP) circuit (not shown separately).

[0160] The processors of the wireless network computing device 700 and the smart phone 800 may be any programmable microprocessor, microcomputer, or multiple processor chips or chipsets that can be configured by software instructions (applications) to perform various functions, including the functions of various implementations. In some wireless devices, multiple processors may be provided, such as one processor within the SOC 204 dedicated to wireless communication functions and one processor within the SoC 202 dedicated to running other applications. Typically, software applications may be stored in the memory 806, memory 816 before being accessed and loaded into the processor. The processor may include internal memory sufficient to store the application software instructions.

[0161] As used in this application, the terms "component", "module", "system", etc. 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, which are configured to perform specific operations or functions. For example, a component can be but not limited to a process, a processor, an object, an executable file, an execution thread, a program, 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 can reside within an executing process or thread, and a component can be located on a processor or core, or distributed between two or more processors or cores. In addition, these components can be executed from various non-temporary computer-readable media having various instructions or data structures stored thereon. Components can communicate via local or remote processes, function or procedure calls, electronic signals, data packets, memory read / write, and other known network, computer, processor, or process-related communication methods.

[0162] Many different cellular and mobile communications services and standards are available or contemplated in the future, all of which can enable and benefit from various implementations. Such services and standards include, for example, the Third Generation Partnership Project (3GPP), Long Term Evolution (LTE) systems, third generation wireless mobile communications technology (3G), fourth generation wireless mobile communications technology (4G), fifth generation wireless mobile communications 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 Networks (WLAN), Wi-Fi Protected Access I & II (WPA, WPA2), and Integrated Digital Enhanced Network (iDEN). For example, each of these technologies involves the transmission and reception of voice, data, signaling or content messages. It should be understood that references to terminology or technical details related to individual communication standards or technologies are for illustrative purposes only and are not intended to limit the scope of the claims to a particular communication system or technology unless specifically set forth in the claims.

[0163] As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items, including individual components. For example, "at least one of a, b, or c" is intended to cover: a, b, c, ab, ac, bc, and abc.

[0164] The various illustrative logics, logic blocks, modules, circuits, and algorithmic processes described in conjunction with the implementations disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. The interchangeability of hardware and software has been generally described in terms of functionality and illustrated in the various illustrative components, blocks, modules, circuits, and processes described above. Whether such functionality is implemented in hardware or software depends on the specific application and design constraints imposed on the overall system.

[0165] The hardware and data processing apparatus for implementing the various illustrative logics, logic blocks, modules, and circuits described in conjunction with the aspects disclosed herein may be implemented or executed with a general purpose single-chip or multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. A general purpose processor may be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration). In some implementations, specific processes and methods may be performed by circuits dedicated to a given function.

[0166] In one or more aspects, the functions described may be implemented in hardware, digital electronic circuitry, computer software, firmware (including the structures disclosed in this specification and their equivalents), or any combination thereof. Implementations of the subject matter described in this specification may also be implemented as one or more computer programs, i.e., one or more computer program instruction modules encoded on a non-transitory processor-readable storage medium for execution by a data processing device or for controlling the operation of the data processing device.

[0167] If implemented in software, the function can be stored or transmitted as one or more instructions or codes on a computer-readable medium. The process of the method or algorithm disclosed herein can be implemented in a processor executable software module residing on a computer-readable medium. Computer-readable media include both computer storage media and communication media, and the communication media include any medium capable of transmitting a computer program from one place to another. The storage medium can be any available non-temporary storage medium that a computer can access. As an example and not limitation, such a computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage device, or any other medium that can be used to store the required program code in the form of an instruction or data structure and can be accessed by a computer. Moreover, any connection can be properly referred to as a computer-readable medium. As used herein, disks and optical disks include compact disks (CDs), laser optical disks, optical optical disks, digital versatile disks (DVDs), floppy disks, and blue-ray disks, wherein disks generally reproduce data magnetically, and optical disks reproduce data optically with lasers. The above combination should also be included in the scope of computer-readable media. Additionally, the operations of a method or algorithm may reside as one or any combination or set of codes and instructions on a machine-readable medium and a computer-readable medium, which codes and instructions may be incorporated into a computer program product.

[0168] In one or more aspects, the described functionality may be implemented by a processor, which may be coupled to a memory. The memory may be a non-transitory computer-readable storage medium storing processor-executable instructions. The memory may store an operating system, user application software, or other executable instructions. The memory may also store application data, such as an array data structure. The processor may write information to the memory and read information from the memory. The memory may also store instructions associated with one or more protocol stacks. A protocol stack generally includes computer-executable instructions to allow communication using a radio access protocol or a communication protocol.

[0169] Various modifications to the implementations described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other implementations without departing from the scope of this disclosure. Therefore, the claims are not intended to be limited to the implementations shown herein, but are to be consistent with the broadest scope consistent with the disclosure, principles, and novel features disclosed herein.

[0170] Certain features described in this specification in the context of separate implementations may also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation may also be implemented individually in multiple implementations or in any suitable subcombination. Furthermore, although features may be described above as functioning in certain combinations, and even initially claimed as such, in some cases one or more features from a claimed combination may be deleted from that combination, and a claimed combination may refer to a subcombination or a variation of a subcombination.

[0171] Similarly, although operations are depicted in a particular order in the accompanying drawings, this should not be understood as requiring these operations to be performed in the particular order shown or in a serialized order, or performing all the operations shown to obtain the desired result. In addition, the accompanying drawings can schematically depict more than one example process in the form of a flow chart. However, other operations not described can be incorporated in the schematically illustrated example process. For example, one or more additional operations can be performed before, after, simultaneously or between any illustrated operations. In some cases, multitasking and parallel processing may be advantageous. In addition, the separation of various system components in the above implementations should not be understood as requiring such separation in all implementations, and it should be understood that the described program components and systems can generally be integrated in a single software product or packaged into multiple software products. In addition, other implementations are within the scope of the following claims. In some cases, the actions described in the claims can be performed in different orders, and the desired results can still be obtained.

Claims

1. A method for managing cross-carrier scheduling at a wireless device, comprising: Receive downlink control information (DCI) carried by a control resource set (CORESET) from the scheduling cell; Associating the DCI with a CORESET pool index of the CORESET carrying the DCI; as well as Cross-carrier scheduling of data communication operations with a first transmission reception point (TRP) or a second TRP is performed based on the DCI and the associated CORESET pool index.

2. The method according to claim 1, wherein: The CORESET pool index includes an indication of one of the first TRP and the second TRP.

3. The method according to claim 1, wherein: Associating the DCI with the CORESET pool index of the CORESET carrying the DCI comprises: The DCI is associated with the CORESET pool index using information from a field in the payload of the DCI.

4. The method according to claim 3, wherein: Associating the DCI with the CORESET pool index using information from a field in the payload of the DCI comprises: An indication of the CORESET pool index is selected from a field added to the payload of the DCI.

5. The method according to claim 3, wherein: Associating the DCI with the CORESET pool index using information from a field in the payload of the DCI comprises: An indication of the CORESET pool index is selected from a carrier indicator field (CIF) in the DCI.

6. The method according to claim 5, wherein: The CIF indicates one of a first higher layer parameter and a second higher layer parameter, each of the first higher layer parameter and the second higher layer parameter being associated with a value of the CORESET pool index.

7. The method according to claim 6, wherein: The first higher layer parameter includes a control resource set (CORESET) pool index of 0, and the second higher layer parameter includes a CORESET pool index of 1.

8. The method according to claim 5, wherein: The cross-carrier scheduling of performing the data communication operation with the first TRP or the second TRP based on the DCI and the associated CORESET pool index includes: The cross-carrier scheduling of the data communication operation with the first TRP or the second TRP is performed in response to selecting the indication of the CORESET pool index.

9. The method of claim 1 , further comprising receiving a radio resource control (RRC) configuration indicating that the scheduled cell is configured by a physical downlink control channel (PDCCH)-configuration parameter, the PDCCH-configuration parameter including two CORESET pool index values ​​in a CORESET for an active bandwidth part (BWP) of the scheduled cell.

10. The method according to claim 9, wherein: The associated CORESET pool index includes one of the two CORESET pool index values.

11. The method according to claim 1 further includes receiving an RRC configuration, wherein the RRC configuration indicates that the scheduled cell is configured to perform multiple physical downlink shared channel (PDSCH)-multiple TRP communication.

12. The method of claim 1 , further comprising receiving an RRC configuration indicating that the scheduled cell is configured by a PDCCH-configuration parameter including a CORESET pool index value in all CORESETs for an active bandwidth part (BWP) of the scheduled cell, or is not configured with a CORESET pool index value.

13. The method according to claim 1, further comprising: receiving an RRC configuration indicating that a scheduled cell is configured by a PDCCH-configuration parameter, the PDCCH-configuration parameter including two CORESET pool index values ​​in a CORESET for an active bandwidth part (BWP) of the scheduled cell, receiving a second DCI from a second scheduling cell; as well as In response to receiving the second DCI, associating the second DCI with a second CORESET pool index; Among them, performing the cross-carrier scheduling of the data communication operation with the first TRP or the second TRP based on the DCI and the associated CORESET pool index includes: performing the cross-carrier scheduling of the data communication operation with the first TRP based on the DCI and the first of the two CORESET pool index values, and performing the cross-carrier scheduling of the data communication operation with the second TRP based on the second DCI and the second of the two CORESET pool index values.

14. The method according to claim 13, wherein: The CIF in the DCI from the scheduling cell corresponds to a first value indicating the scheduled cell, and the second DCI from the second scheduling cell includes a second CIF corresponding to a second value indicating the scheduled cell.

15. The method according to claim 1, further comprising: Receiving an RRC configuration, the RRC configuration indicating that the scheduling cell is configured with two or more CORESET pool index values; as well as A data communication operation of the scheduled cell is performed according to the two or more CORESET pool index values.

16. The method according to claim 15, further comprising: Receiving an RRC configuration, the RRC configuration indicating that the scheduled cell is not configured with two or more CORESET pool index values; as well as Independently of the CORESET pool index of the CORESET carrying the DCI, a data communication operation of the scheduled cell is performed.

17. The method according to claim 1, wherein: Associating the DCI with the CORESET pool index of the CORESET carrying the DCI comprises: Selecting the CORESET pool index of the CORESET that carries the DCI; and The method further includes performing a data communication operation of a scheduled cell according to the CORESET pool index of the CORESET.

18. The method according to claim 17, further comprising: receiving an RRC configuration indicating that the scheduled cell is configured by a PDCCH-configuration parameter, the PDCCH-configuration parameter including two CORESET pool index values ​​in a CORESET for an active bandwidth part (BWP) of the scheduled cell; as well as Select the two CORESET pool index values; Among them, performing the data communication operation of the scheduled cell according to the CORESET pool index of the CORESET carrying the DCI includes performing the data communication operation between the scheduled cell and the first TRP or the second TRP according to the two selected CORESET pool index values.

19. The method according to claim 17, further comprising: Receiving an RRC configuration indicating that the scheduled cell is not configured with two CORESET pool index values ​​in a CORESET for an active bandwidth part (BWP) of the scheduled cell; Wherein, performing the data communication operation of the scheduled cell according to the CORESET pool index of the CORESET carrying the DCI includes performing the data communication operation of the scheduled cell independently of the selected CORESET pool index of the CORESET carrying the DCI after receiving two CORESET pool index values ​​in the CORESET indicating that the scheduled cell is not configured with the active bandwidth part BWP for the scheduled cell.

20. The method according to claim 17, wherein: The CORESET pool index includes a first CORESET pool index value configured for all CORESETs in the scheduling cell, and a second CORESET pool index value configured for all CORESETs in the second scheduling cell, Performing cross-carrier scheduling of data communication operations with a first TRP or a second TRP based on the DCI and the associated CORESET pool index includes performing cross-carrier scheduling of communications with the first TRP according to a communication link scheduling from the scheduling cell associated with the first CORESET pool index value, and performing cross-carrier scheduling of communications with the second TRP according to a communication link scheduling from the second scheduling cell associated with the second CORESET pool index value.

21. The method of claim 1, wherein: The received DCI schedules the scheduled cell; and Performing cross-carrier scheduling of data communication operations with the first TRP or the second TRP based on the DCI and the associated CORESET pool index includes performing cross-carrier scheduling of data communication operations with the first TRP or the second TRP in response to receiving the DCI that schedules the scheduled cell.

22. A wireless communication device, comprising: The first interface is configured as: Obtain downlink control information (DCI) carried by the control resource set (CORESET) from the scheduling cell; a processing system coupled to the first interface and configured to: Associating the DCI with a CORESET pool index of the CORESET carrying the DCI; as well as Cross-carrier scheduling of data communication operations with a first transmission reception point (TRP) or a second TRP is initiated based on the DCI and the associated CORESET pool index.

23. The device according to claim 22, wherein: The CORESET pool index includes an indication of one of the first TRP and the second TRP.

24. The device according to claim 22, wherein: The processing system is also configured to: The DCI is associated with the CORESET pool index using information from a field in the payload of the DCI.

25. The device according to claim 24, wherein: The processing system is also configured to: An indication of the CORESET pool index is selected from a field added to the payload of the DCI.

26. The device according to claim 24, wherein The processing system is also configured to: An indication of the CORESET pool index is selected from a carrier indicator field (CIF) in the DCI.

27. The device according to claim 26, wherein: The CIF indicates one of a first higher layer parameter and a second higher layer parameter, each of the first higher layer parameter and the second higher layer parameter being associated with a value of the CORESET pool index.

28. A non-transitory processor-readable medium having stored thereon processor-executable instructions configured to cause a wireless device processor to perform operations comprising: Receive downlink control information (DCI) carried by a control resource set (CORESET) from the scheduling cell; Associating the DCI with a CORESET pool index of the CORESET carrying the DCI; as well as Cross-carrier scheduling of data communication operations with a first transmission reception point (TRP) or a second TRP is performed based on the DCI and the associated CORESET pool index.

29. A wireless device comprising: A component for receiving downlink control information (DCI) carried by a control resource set (CORESET) from a scheduling cell; means for associating the DCI with a CORESET pool index of the CORESET carrying the DCI; as well as Means for performing cross-carrier scheduling of data communication operations with a first transmission reception point (TRP) or a second TRP based on the DCI and an associated CORESET pool index.

Images