Apparatus and method for configuring multi-cell scheduling for NR operations

Abstract

This disclosure provides apparatus and method for configuring multi-cell scheduling for New Radio (NR) operation. An apparatus for a User Equipment (UE) includes: a radio frequency (RF) interface; and processing circuitry coupled to the RF interface, the processing circuitry being configured to: decode downlink control information (DCI) received via the RF interface on a physical downlink channel (PDCCH) of a scheduling cell, wherein the DCI is configured to schedule a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) of more than one cell; and perform communication on the PDSCH or PUSCH of more than one cell according to the instructions of the DCI.

Description

[0001] Priority Statement

[0002] This application claims priority to International Application No. PCT / CN2020 / 082136, filed March 30, 2020; International Application No. PCT / CN2020 / 082368, filed March 31, 2020; and International Application No. PCT / CN2020 / 121459, filed October 16, 2020, the entire contents of which are incorporated herein by reference. Technical Field

[0003] Embodiments of this disclosure generally relate to the field of wireless communication, and more specifically, to apparatus and methods for configuring multi-cell scheduling for New Radio (NR) operation. Background Technology

[0004] The 3rd Generation Partnership Project (3GPP) introduces 5G or NR systems as an evolution of 4G or LTE systems. Compared to 4G / LTE systems, 5G / NR systems will offer wider bandwidth and support larger volumes of traffic, extremely high reliability, and extremely low latency. While 5G networks are expected to eventually replace 4G networks, 5G and 4G systems will coexist for some time. In this scenario, 5G carriers may be adjacent to 4G carriers; alternatively, 5G carriers may partially or completely overlap with 4G carriers in the frequency domain. Therefore, when deploying 5G / NR systems, effective support for coexistence between 5G and 4G systems (i.e., Dynamic Spectrum Sharing (DSS)) should be considered.

[0005] Since 5G NR Release 15 (Rel-15), DSS has been taken into account. For example, a cell-specific reference signal (CRS) mode can be configured for NR user equipment (UE) to enable rate matching of NR carrier physical downlink shared channel (PDSCH) transmissions around resource elements (REs) potentially used for LTE CRS. This mitigates the impact on LTE channel estimation for better LTE downlink (DL) performance. In another example, NR transmissions on resources used by the LTE physical downlink control channel (PDCCH) should be avoided. The consideration of LTE CRS / PDCCH imposes limitations on NR PDCCH transmission. Summary of the Invention

[0006] One aspect of this disclosure provides an apparatus for a user equipment (UE), comprising: a radio frequency (RF) interface; and processing circuitry coupled to the RF interface, the processing circuitry being configured to: decode downlink control information (DCI) received via the RF interface on a physical downlink channel (PDCCH) of a scheduling cell, wherein the DCI is configured to schedule a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) of more than one cell; and to perform communication on the PDSCH or PUSCH of more than one cell according to the instructions of the DCI.

[0007] Another aspect of this disclosure provides a computer-readable storage medium having instructions stored thereon that, when executed by a user equipment (UE), cause the UE to: receive downlink control information (DCI) on a physical downlink channel (PDCCH) of a scheduling cell, wherein the DCI is configured to schedule a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) of more than one cell; and perform communication on the PDSCH or PUSCH of more than one cell according to the instructions of the DCI.

[0008] Other aspects of this disclosure may provide other methods, apparatus or computer-readable storage media in connection with the foregoing aspects. Attached Figure Description

[0009] In the accompanying drawings, embodiments of the present disclosure will be illustrated by way of example rather than limitation, wherein like reference numerals refer to similar elements.

[0010] Figure 1 Example systems according to some embodiments of the present disclosure are shown, in which downlink control information (DCI) for multi-cell scheduling is employed.

[0011] Figure 2 Examples of two-cell scheduling as an extension of self-scheduling, according to some embodiments of this disclosure, are shown.

[0012] Figure 3 Another example of two-cell scheduling as an extension of self-scheduling, according to some embodiments of this disclosure, is shown.

[0013] Figure 4 Another example of two-cell scheduling as an extension of self-scheduling, according to some embodiments of this disclosure, is shown.

[0014] Figure 5Examples of two-cell scheduling as an extension of cross-carrier scheduling are shown according to some embodiments of this disclosure.

[0015] Figure 6 Another example of two-cell scheduling as an extension of cross-carrier scheduling is shown according to some embodiments of this disclosure.

[0016] Figure 7 An example case is shown of joint size determination of two fields in a DCI used for two-cell scheduling, according to some embodiments of the present disclosure.

[0017] Figure 8 Another example of joint size determination of two fields in a DCI used for two-cell scheduling is shown according to some embodiments of the present disclosure.

[0018] Figure 9 A flowchart of an example process for reducing the number of DCI sizes according to some embodiments of this disclosure is shown.

[0019] Figure 10 A flowchart is shown as another example process for reducing the number of DCI sizes according to some embodiments of this disclosure.

[0020] Figure 11 A flowchart is shown as another example process for reducing the number of DCI sizes according to some embodiments of this disclosure.

[0021] Figure 12 The flowchart illustrates a process for PDSCH / PUSCH scheduling according to some embodiments of the present disclosure.

[0022] Figure 13 Illustrations of networks according to various embodiments of the present disclosure are shown.

[0023] Figure 14 Wireless networks according to various embodiments of this disclosure are illustrated schematically.

[0024] Figure 15 This is a block diagram illustrating a component capable of reading instructions from a machine-readable or computer-readable medium and performing any one or more methods discussed herein, according to some example embodiments. Detailed Implementation

[0025] Various aspects of the illustrative embodiments will be described using terminology commonly employed by those skilled in the art to convey the essence of this disclosure to others skilled in the art. However, it will be readily understood by those skilled in the art that many alternative embodiments can be practiced using portions of the described aspects. Specific figures, materials, and configurations are set forth for illustrative purposes to provide a thorough understanding of the illustrative embodiments. However, it will be readily understood by those skilled in the art that alternative embodiments can be practiced without these specific details. In other instances, well-known features may be omitted or simplified to avoid obscuring the illustrative embodiments.

[0026] Furthermore, the various operations will be described as multiple discrete operations in a manner most conducive to understanding the illustrative embodiments; however, the order of description should not be construed as implying that these operations must depend on the order. In particular, these operations do not need to be performed in the order presented.

[0027] The phrases “in an embodiment,” “in one embodiment,” and “in some embodiments” are used repeatedly throughout this document. These phrases do not typically refer to the same embodiment; however, they may refer to the same embodiment. Unless the context otherwise specifies, the terms “comprising,” “having,” and “including” are synonyms. The phrases “A or B” and “A / B” mean “(A), (B), or (A and B).”

[0028] This paper proposes a PDCCH that supports secondary cells (SCells) and can schedule PDSCH or Physical Uplink Shared Channel (PUSCH) transmissions in the primary cell (PCell). Furthermore, the PDCCH can schedule PDSCH or PUSCH transmissions in both cells. Therefore, effective PDCCH design is a key issue to consider for DSS enhancement.

[0029] In existing NR systems, a UE can be configured to have up to four DL / UL bandwidth portions (BWPs) within the carrier bandwidth. At most one DL / UL BWP is active at any given time. As defined in NR Rel-15, for each DL / UL BWP, up to three control resource sets (CORESETs) for PDCCH transmission can be configured, and up to ten search space sets can be configured. For self-scheduling of the serving cell, CORESETs and search space sets are configured on the serving cell. On the other hand, for cross-carrier scheduling, the CORESETs and search space sets for the scheduled cell are located on the scheduling cell. Therefore, only a limited number of parameters specific to the scheduled cell need to be configured. For example, the only parameter that needs to be configured for the scheduled cell is the number of PDCCH candidates per aggregation level for the scheduled cell, i.e., nrofCandidates.

[0030] Conditions for multi-cell dispatch

[0031] In existing NR systems, a single downlink control information (DCI) format is used to schedule DL / UL transmissions on a single cell; this is defined in this paper as a DCI for self-scheduling. In carrier aggregation (CA) scenarios, cross-cell scheduling is considered, where DL / UL transmissions on the scheduled cell are scheduled by a DCI on the physical downlink control channel (PDCCH) of the scheduling cell, and DL / UL transmissions on the electroplating cell are scheduled by another DCI on the PDCCH of the scheduling cell.

[0032] This disclosure proposes that more than one cell can be scheduled using a single DCI format, which may be referred to herein as DCI for multi-cell scheduling. DCI for multi-cell scheduling should be designed to provide a gain in PDCCH resource efficiency.

[0033] In this embodiment of the disclosure, for the purpose of simplification and clarity, the example is a DCI used to schedule two cells, but it can be directly extended to a DCI used to schedule more cells.

[0034] For example, the size of the DCI used for two-cell scheduling should not be twice the size of the DCI used for self-scheduling. It is expected that certain factors of the two active BWPs on the two cells should be common or similar to potentially reduce the size of the DCI used for two-cell scheduling.

[0035] In embodiments of this disclosure, DCI format 0_0 / 1_0 is used for fallback operations and does not support multi-cell scheduling. On the other hand, other DCI formats that can be configured for unicast scheduling, such as DCI formats 0_1 / 1_1 and / or 0_2 / 1_2, can be extended for multi-cell scheduling. For example, the format of a DCI configured to schedule a Physical Downlink Shared Channel (PDSCH) for more than one cell (e.g., two cells) can be defined as DCI format 1_3, and the format of a DCI configured to schedule a Physical Uplink Shared Channel (PUSCH) for more than one cell (e.g., two cells) can be defined as DCI format 0_3. Other formats are also possible.

[0036] In embodiments of this disclosure, the UE-specific search space set can be configured with one of the following: DCI formats 0_0 and 1_0 only; DCI formats 0_1 and 1_1 only; DCI formats 0_3 and 1_3 only; other DCI formats, such as DCI formats 0_2 and 1_2.

[0037] In another embodiment of this disclosure, the UE-specific search space set may be configured with one of the following: DCI formats 0_0 and 1_0 only; DCI formats 0_1 and 1_1 only; DCI format 0_3 or DCI format 1_3; other DCI formats, such as DCI formats 0_2 and 1_2.

[0038] In another embodiment of this disclosure, in addition to other DCI formats already configured for the search space set, a UE-specific search space set may be configured with a DCI format for multi-cell scheduling. For example, a UE-specific search space set may be configured with DCI formats 0_0 and 1_0, or DCI formats 0_1 and 1_1, or DCI formats 0_3 and 1_3.

[0039] In another embodiment of this disclosure, in addition to other DCI formats(s) already configured for the search space set, a UE-specific search space set may be configured with a DCI format for multi-cell scheduling. For example, a UE-specific search space set may be configured with DCI formats 0_0 and 1_0 or DCI formats 0_1 and 1_1, or DCI format 0_3 or DCI format 1_3.

[0040] In embodiments of this disclosure, cells scheduled by DCI for multi-cell scheduling may have the same carrier bandwidth.

[0041] In embodiments of this disclosure, active BWPs on cells scheduled by DCI for multi-cell scheduling can have the same size. Since the BWP sizes are the same, the PRB groups used for PDSCH or PUSCH resource allocation are also the same size. Therefore, this helps simplify frequency resource allocation.

[0042] In embodiments of this disclosure, the PDSCH / PUSCH on cells scheduled by DCI for multi-cell scheduling can be configured with the same number of transport blocks (TB). Alternatively, the number of TBs on the active BWP of cells scheduled by DCI for multi-cell scheduling can be the same. This allows cells scheduled by DCI for multi-cell scheduling to be configured with the same number of fields, such as bit fields for modulation and coding scheme (MCS), redundancy version (RV), or new data indicator (NDI), which may be helpful for DCI format design.

[0043] In embodiments of this disclosure, the PDSCH / PUSCH on cells scheduled by DCI for multi-cell scheduling can be configured to have the same number of code block groups (CBGs). The configuration of the same number of CBGs facilitates efficient utilization of the Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) transmission function.

[0044] In embodiments of this disclosure, for example, the DCI used for two-cell scheduling can be used to schedule PDSCH transmissions on one cell and PUSCH transmissions on the same cell. Alternatively, the DCI used for two-cell scheduling can be used to schedule PDSCH transmissions on a first cell and PUSCH transmissions on a second cell.

[0045] In embodiments of this disclosure, the design of a DCI for multi-cell scheduling considers both UL carriers and supplementary UL (SUL) carriers. For example, a DCI for two-cell scheduling can be configured to schedule two UL carriers from two cells. Alternatively, a DCI for two-cell scheduling can be configured to schedule two SUL carriers from two cells. Alternatively, a DCI for two-cell scheduling can be configured to schedule the UL carrier of one cell and the SUL carrier of the other cell.

[0046] Figure 1 An example system 100 according to some embodiments of the present disclosure is shown, in which DCI for multi-cell scheduling may be employed. The following description is provided for example system 100 operating in combination with the Long Term Evolution (LTE) system standard provided by the 3GPP Technical Specification (TS) and the 5G or New Radio (NR) system standard. However, the example embodiments are not limited in this respect, and the described embodiments can be applied to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., sixth generation (6G)) systems, IEEE 802.16 protocols (e.g., Wireless Metropolitan Area Network (MAN), Global Microwave Access Interoperability (WiMAX), etc.).

[0047] like Figure 1As shown, system 100 may include user equipment (UE) 101. As used herein, the term "user equipment" or "UE" may refer to a device with radio communication capabilities and may describe a remote user of network resources in a communication network. The term "user equipment" or "UE" may be considered synonymous and may refer to a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device including a wireless communication interface. In this example, UE101 is shown as a smartphone (e.g., a handheld touchscreen mobile computing device that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as consumer electronics, cellular phones, smartphones, feature phones, tablets, wearable computing devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptops, in-vehicle infotainment systems (IVI), in-vehicle entertainment (ICE) devices, instrument clusters (ICs), head-up displays (HUDs), on-board diagnostics (OBD) devices, dashboard mobile devices (DMEs), mobile data terminals (MDTs), electronic engine management systems (EEMS), electronic / engine control units (ECUs), electronic / engine control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or “smart” devices, machine-type communication (MTC) devices, machine-to-machine (M2M) devices, Internet of Things (IoT) devices, and / or the like.

[0048] In some embodiments, UE 101 may include an IoT UE, which may include a network access layer designed for low-power IoT applications utilizing short-lived UE connections. The IoT UE may utilize technologies such as M2M or MTC to exchange data with an MTC server or device via a PLMN, Proximity-Based Service (ProSe) or Device-to-Device (D2D) communication, sensor networks, or an IoT network. M2M or MTC data exchange may be machine-initiated. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UE may execute background applications (e.g., keeping messages active, state updates, etc.) to facilitate connectivity within the IoT network.

[0049] UE 101 can be configured to connect to (e.g., communicatively coupled to) a RAN. In embodiments, the RAN can be a next-generation (NG) RAN or a 5G RAN, an evolved Universal Mobile Telecommunications System (UMTS) terrestrial radio access network (E-UTRAN), or a traditional RAN, such as UTRAN (UMTS Terrestrial Radio Access Network) or GERAN (GSM (Global System for Mobile Communications or Groupe Spécial Mobile) EDGE (GSM Evolution) Radio Access Network). As used herein, the term "NG RAN," etc., can refer to a RAN operating in an NR or 5G system. UE 101 utilizes a connection or channel to send or receive information. As used herein, the term "channel" can refer to any tangible or intangible transmission medium used to transmit data or data streams. The term "channel" can be synonymous and / or equivalent to "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," and / or any other similar terms that indicate a path or medium through which data is transmitted. Additionally, the term "link" can refer to a connection between two devices for the purpose of sending and receiving information via radio access technology (RAT).

[0050] To illustrate the principle of this technology and simplify the explanation, in Figure 1 Only one UE 101 and three cells 103, 104 and 105 associated with the next-generation node B (gNB) 102 are described, but it should be noted that system 100 may include any number and type of UEs and base stations and associated cells.

[0051] like Figure 1 As shown, UE 101 can communicate with gNB 102 on the first cell (i.e., cell 1) 103, the second cell (i.e., cell 2) 104, and the third cell (i.e., cell 3) 105. In the context of this specification, the term "cell" may have the same meaning as the term "carrier".

[0052] In an NR system, the Physical Downlink Control Channel (PDCCH) can carry information about the transmission format and resource allocation related to the Physical Downlink Shared Channel (PDSCH) or Physical Uplink Shared Channel (PUSCH). The PDSCH can deliver user data and higher-layer signaling to UE 101. The PUSCH can deliver user-related information or requests to gNB 102. As mentioned above, in existing NR systems, the DCI carried on the cell's PDCCH is used for self-scheduling, that is, scheduling the cell's own PDSCH or PUSCH. For example, the PDCCH of the first cell 103 can carry a DCI to schedule its own PDSCH or PUSCH, the PDCCH of the second cell 104 can carry a DCI to schedule its own PDSCH or PUSCH, and the PDCCH of the third cell 105 can carry a DCI to schedule its own PDSCH or PUSCH. In CA, the PDCCH of the first cell 103 can carry the first DCI to schedule its own PDSCH or PUSCH, the second DCI to schedule the PDSCH or PUSCH of the second cell 104, or the third DCI to schedule the PDSCH or PUSCH of the third cell 105; the same applies to the second cell 104 and the third cell 105.

[0053] In this disclosure, a DCI for multi-cell scheduling is proposed and applied to system 100. In this example, for simplicity and clarity, a DCI for two-cell scheduling is described.

[0054] UE 101 can monitor PDCCHs on the search resource set allocated by gNB 102 to discover DCIs. When a DCI is received on one of the PDCCHs, UE 101 can determine the DCI format and decode the DCI based on the DCI format. In one embodiment, a DCI can be configured to schedule the PDSCH or PUSCH of more than one cell (e.g., two cells). In this document, the cell hosting the PDCCH on which the DCI is received is considered the scheduling cell. The two cells scheduled by the DCI may or may not include the scheduling cell. UE 101 can perform downlink communication on the PDSCH of the two cells or uplink communication on the PUSCH as indicated by the DCI.

[0055] For example, each of the first cell 103, the second cell 104, and the third cell 105 can act as a scheduling cell, and the two cells to be scheduled can include any two of the following: the first cell 103, the second cell 104, and the third cell 105.

[0056] Configuration of self-scheduled two-cell scheduling

[0057] When self-scheduling is configured for single-cell scheduling, a DCI for two-cell scheduling without a carrier indicator field (CIF) can be configured on either of the two cells scheduled by that DCI.

[0058] In one embodiment, two-cell scheduling can be configured on the first cell 103 via higher-layer signaling. The first cell 103 and the second cell 104 can be scheduled by a DCI for two-cell scheduling. The second cell 104 can be configured via higher-layer signaling. In this case, a CIF is not required in the DCI. The first cell 103 can be used as a reference cell to define other behaviors of the DCI for two-cell scheduling.

[0059] Figure 2 Examples of two-cell scheduling as an extension of self-scheduling, according to some embodiments of the present disclosure, are shown. For example, such as... Figure 2 As shown, self-scheduling still applies to the existing DCI format on each cell. On the other hand, DCI for two-cell scheduling can be sent on cell 1, which schedules the PDSCH / PUSCH on both cell 1 and cell 2. If configured, DCI for two-cell scheduling can also be sent on cell 2, which schedules the PDSCH / PUSCH on both cell 2 and cell 3.

[0060] like Figure 2 As shown, in this embodiment, the scheduling cell is one of two cells scheduled by a DCI used for two-cell scheduling. In one embodiment, the other cell scheduled by the DCI for two-cell scheduling can be configured via higher-layer signaling. If another cell is configured for the scheduling cell, a search space set for the DCI for two-cell scheduling can be configured on that scheduling cell.

[0061] For example, another cell can be configured for scheduling by a DCI used for two-cell scheduling for each DL / UL BWP of a scheduled cell via higher-layer signaling. If another cell is configured for the DL / UL BWP of that scheduled cell, a search space set for the DCI used for two-cell scheduling can be configured on the DL / UL BWP of that scheduled cell.

[0062] For example, another cell can be configured for each CORESET of a scheduled cell via higher-layer signaling, using a DCI for two-cell scheduling. If another cell is configured for a CORESET of a scheduled cell, a search space set for a DCI for two-cell scheduling can be configured on that CORESET.

[0063] For example, another cell can be configured for two-cell scheduling using DCI for each search space set of the scheduled cell via higher-layer signaling. If another cell is configured for the search space set of the scheduled cell, then DCI for two-cell scheduling can be configured on the search space set of that scheduled cell.

[0064] In one embodiment, for two cells that can be scheduled by a DCI for two-cell scheduling, only one of the two cells can carry the DCI for two-cell scheduling. The cell carrying the DCI for two-cell scheduling can be determined by fixed rules, such as the cell with the lower serving cell index. Alternatively, the cell carrying the DCI for two-cell scheduling can be specified by higher-layer signaling. In another embodiment, the DCI for two-cell scheduling can be configured on either of the two cells.

[0065] In one embodiment, if the two cells for two-cell scheduling by a single DCI include a primary cell (PCell), a secondary cell (SCell), or a primary-secondary cell group cell (PSCell), then the DCI for two-cell scheduling is configured on the PCell or PSCell. Alternatively, the DCI for two-cell scheduling can be configured on the SCell. The advantage of transmitting the DCI for two-cell scheduling on the SCell is that the PDCCH overhead can be offloaded from the PCell or PSCell. Alternatively, the DCI for two-cell scheduling can be configured on either the PCell or PSCell or on the SCell.

[0066] Self-scheduling for single-cell scheduling and cross-carrier scheduling for two-cell scheduling

[0067] Assuming multiple cells perform self-scheduling for single-cell scheduling, one of these cells, such as Cell 1 or Cell 1, can act as the scheduling cell to schedule PDSCH / PUSCH on one or more other cells through two-cell scheduling. In other words, the scheduling mode, whether self-scheduling or cross-carrier scheduling, can be configured separately for single-cell and two-cell scheduling via higher-layer signaling.

[0068] In one embodiment, two-cell scheduling can be configured on a first cell via higher-layer signaling, and the first cell thus acts as the scheduling cell. Multiple other cells can act as second cells scheduled via two-cell scheduling. The first and second cells can be scheduled by a DCI used for two-cell scheduling. In this case, since the second cell can be selected from multiple cells, a CIF (Cellular Information Framework) must be included in the DCI used for two-cell scheduling to distinguish between different second cells. The first cell can act as a reference cell to define other behaviors of the DCI used for two-cell scheduling.

[0069] Figure 3Another example of two-cell scheduling as an extension of self-scheduling, according to some embodiments of this disclosure, is shown. For example, such as Figure 3 As shown, self-scheduling still applies to the existing DCI format on each cell. On the other hand, DCI for two-cell scheduling is sent only on cell 1, which can schedule PDSCH / PUSCH on cell 1 and cell 2, or schedule PDSCH / PUSCH on cell 1 and cell 3.

[0070] In one embodiment, when two-cell scheduling is configured on the first cell, one or more pairs of cells that can be scheduled by the DCI used for two-cell scheduling can be configured via higher-layer signaling. There is no restriction on whether the first cell is included in this pair. A CIF must be present in the DCI to distinguish the two cells scheduled by that DCI. The first cell can act as a reference cell to define other behaviors of the DCI used for two-cell scheduling.

[0071] Figure 4 Another example of two-cell scheduling as an extension of self-scheduling, according to some embodiments of this disclosure, is shown. For example, such as Figure 4 As shown, self-scheduling still applies to the existing DCI format on each cell. On the other hand, DCI for two-cell scheduling is sent only on cell 1, which can schedule PDSCH / PUSCH on cell 1 and cell 2, or schedule PDSCH / PUSCH on cell 2 and cell 3.

[0072] In one embodiment, CIF values ​​for two-cell scheduling can be configured via higher-layer signaling. The CrossCarrierSchedulingConfig information element (IE) in the higher-layer signaling can be used to indicate the configuration for two-cell scheduling. In the scheduling cell used for two-cell scheduling, the cif-presence in the CrossCarrierSchedulingConfig IE is set to true. On the other hand, for the scheduled cell, the scheduleCellId IE can indicate the serving cell index of the scheduling cell, and the cif-InSchedulingCell IE can indicate one or more CIF values ​​in the scheduling cell that indicate the DCI used for two-cell scheduling applies to the scheduled cell.

[0073] In one embodiment, if the scheduling cell is always one of two cells scheduled via two-cell scheduling, the CIF value can be configured only for the other scheduled cell using cif-InSchedulingCell. The value of cif-InSchedulingCell can range from 1 to 7. The DCI used for two-cell scheduling can schedule PDSCH / PUSCH on the scheduling cell and the other scheduled cell indicated by the CIF value in the DCI.

[0074] In another embodiment, the CIF value can be configured to indicate two cells scheduled by a DCI used for two-cell scheduling. The two scheduled cells may or may not include the scheduling cell. Multiple CIF values ​​can be configured in the configuration of the serving cell. For example, in the CrossCarrierSchedulingConfig IE, the cif-InSchedulingCell can be expanded to indicate multiple CIF values. Then, based on the CIF configurations of all serving cells in CA operations, UE 101 can identify the exact behavior corresponding to the CIF value. That is, two serving cells configured with a uniform CIF are scheduled by a DCI used for two-cell scheduling that indicates the same CIF value.

[0075] Two-cell scheduling configuration based on cross-carrier scheduling

[0076] In existing LTE / NR systems, a single DCI format schedules DL or UL transmissions on only a single cell. In cross-carrier scheduling, DL or UL transmissions on the scheduled cell are scheduled via the PDCCH transmitted on the scheduling cell. DL or UL transmissions on the scheduling cell itself are also scheduled by the DCI transmitted on the PDCCH of the scheduling cell. Cross-carrier scheduling used for single-cell scheduling in existing LTE / NR systems can also be extended to support two-cell scheduling.

[0077] In one embodiment, a DCI for two-cell scheduling can be configured in the scheduling cell configuration via higher-layer signaling. Specifically, if DL / UL transmissions on the PCell can be scheduled by the SCell (i.e., the SCell acts as the scheduling cell), a DCI for two-cell scheduling can be configured on the SCell to schedule DL / UL transmissions on both the PCell and the SCell itself.

[0078] In one embodiment, the scheduling cell can be one of two cells scheduled by a DCI used for two-cell scheduling, and the other of these two cells can be configured via higher-layer signaling. Therefore, the other of the two cells can be dynamically indicated by the CIF in the DCI used for two-cell scheduling.

[0079] Figure 5Examples of two-cell scheduling as an extension of cross-carrier scheduling are shown according to some embodiments of this disclosure. For example, such as Figure 5 As shown, cross-carrier scheduling still applies to the existing DCI format on each cell. On the other hand, DCI for two-cell scheduling can be transmitted on the scheduling cell (i.e., cell 1), which can schedule PDSCH / PUSCH on cell 1 and cell 2, or schedule PDSCH / PUSCH on cell 1 and cell 3.

[0080] In one embodiment, one or more pairs of cells for two-cell scheduling can be configured via higher-layer signaling. A pair of cells can then be dynamically indicated by the CIF in the DCI used for two-cell scheduling. There is no restriction on whether the scheduling cell is included in the cells scheduled by the DCI used for two-cell scheduling.

[0081] Figure 6 Examples of two-cell scheduling as an extension of cross-carrier scheduling are shown according to some embodiments of this disclosure. For example, such as Figure 6 As shown, cross-carrier scheduling still applies to the existing DCI format on each cell. On the other hand, a DCI for two-cell scheduling can be transmitted on the scheduling cell (i.e., cell 1), which can schedule PDSCH / PUSCH on cell 1 and cell 2, or schedule PDSCH / PUSCH on cell 2 and cell 3.

[0082] In one embodiment, two-cell scheduling can be configured for a scheduling cell specifically using a single DCI via higher-layer signaling. If two-cell scheduling is configured for a scheduling cell, a search space set for the DCI used for two-cell scheduling can be configured on the scheduling cell.

[0083] In another embodiment, two-cell scheduling can be configured for each DL / UL BWP of the scheduling cell via higher-layer signaling using a single DCI. If two-cell scheduling is configured for the DL / UL BWP of the scheduling cell, a search space set for the DCI used for two-cell scheduling can be configured on the DL / UL BWP of the scheduling cell.

[0084] In another embodiment, two-cell scheduling can be configured for each CORESET of the scheduling cell using a single DCI via higher-layer signaling. If two-cell scheduling is configured for a CORESET of the scheduling cell, a search space set for the DCI used for two-cell scheduling can be configured on the CORESET of the scheduling cell.

[0085] In another embodiment, two-cell scheduling can be configured by a single DCI for each search space set of the scheduled cells via higher-layer signaling. If two-cell scheduling is configured for the search space set of the scheduled cells, a DCI for two-cell scheduling can be configured on the search space set of the scheduled cells.

[0086] In one embodiment, a single-value space for the CIF can be shared between single-cell and two-cell scheduling. That is, different values ​​of the CIF can indicate scheduling for a single cell or two cells. The CIF can still have a maximum of 3 bits. Alternatively, more bits (one or more) can be configured for the CIF. For example, as shown in Table 1, a 4-bit CIF can indicate all cases of single-cell scheduling as well as some combinations of two-cell scheduling. Note that the combinations of two-cell scheduling shown in Table 1 are merely examples and are not intended to limit the potential combinations of serving cells.

[0087] CIF Index of Serving Cells under Scheduling 0 0 1 1 2 2 3 3 4 4 5 5 6 6 7 7 8 0,1 9 0,2 10 0,3 11 0,4 12 0,5 13 2,3 14 4,5 15 6,7 15 6,7

[0088] Table 1. Joint CIF for single-cell scheduling and two-cell scheduling

[0089] In one embodiment, the potential information indicated by the CIF value may include the following: The CIF value may indicate that only DL or UL transmissions on the scheduling cell are scheduled, for example, CIF = 0. The CIF value may indicate that only DL or UL transmissions on the scheduled cell are scheduled. The CIF value may indicate that both cells are scheduled, for example, DL or UL transmissions on the scheduled cell are scheduled in addition to those on the scheduling cell.

[0090] In another embodiment, for flexibility, the potential information indicated by the CIF value may include the following: The CIF value may indicate that only DL or UL transmissions are scheduled on the scheduling cell, for example, CIF = 0. The CIF value may indicate that only DL or UL transmissions are scheduled on the scheduled cell. The CIF value may indicate that two cells are scheduled, for example, DL or UL transmissions are scheduled on two cells within a set of cells that can be scheduled by the scheduling cell. The two scheduled cells may or may not include the scheduling cell.

[0091] In another embodiment, another bit in the DCI can be used to explicitly indicate two-cell scheduling. For example, bit "1" can be used to indicate that the DCI is used for two-cell scheduling, while bit "0" can be used to indicate that the DCI is not used for two-cell scheduling. When dual-cell scheduling is enabled and the scheduled cell includes the scheduling cell, the CIF value can indicate another scheduled cell besides the scheduling cell.

[0092] In one embodiment, the CIF value for single-cell scheduling and the CIF value for two-cell scheduling can be defined independently. It is assumed that the DCI for two-cell scheduling can have a different DCI size than the DCI for single-cell scheduling. Therefore, the DCI size can be used to distinguish between the DCI for single-cell scheduling and the DCI for two-cell scheduling. Consequently, the CIF in the DCI for single-cell scheduling and the CIF in the DCI for two-cell scheduling will never affect each other.

[0093] In one embodiment, for two-cell scheduling, the CIF value can be configured to indicate one or more scheduled cells in addition to the scheduling cell. Since the scheduling cell is always one of the two cells scheduled through two-cell scheduling, the CIF can effectively indicate only the cells scheduled by two-cell scheduling other than the scheduling cell. Therefore, the same CIF configuration for single-cell scheduling can be reused for two-cell scheduling. For example, as shown in Table 2, a single mapping between the CIF and the scheduled cell index is configured. It can be directly used for single-cell scheduling DCI. On the other hand, for DCI used for two-cell scheduling, the CIF value can be used to derive another scheduled cell besides the scheduling cell.

[0094] CIF Index of Serving Cells under Scheduling 0 0 1 1 2 2 3 3 4 4 5 5 6 6 7 7

[0095] Table 2. Identical CIF configurations for single-cell and two-cell scheduling

[0096] In another embodiment, for two-cell scheduling, the CIF value can be configured to indicate two cells from a set of cells that can be scheduled by the scheduling cell. These two cells may or may not include the scheduling cell itself. For single-cell scheduling, the CIF can be configured by reusing existing RRC signaling in the NR. On the other hand, for two-cell scheduling, the CIF can be configured separately using another RRC signaling. For example, as shown in Table 3, a 3-bit CIF can be used in the DCI for single-cell scheduling, and the CIF value can indicate one of eight cells that can be scheduled by the scheduling cell. A 3-bit CIF can also be used in the DCI for two-cell scheduling, and the CIF value can indicate one pair of cells from eight pairs of cells that can be scheduled by the scheduling cell.

[0097]

[0098] Table 3. Separate CIF configurations for single-cell scheduling and two-cell scheduling

[0099] If the DCI used for two-cell scheduling is designed to have the same size as the DCI used for single-cell scheduling, one or more padding bits can be added to the DCI format used for two-cell scheduling. Alternatively, one or more padding bits can be added to the DCI format used for single-cell scheduling. Alternatively, UE 101 may not be intended to be configured to monitor one or more DCI formats for single-cell scheduling and one or more DCI formats for two-cell scheduling with the same DCI format size.

[0100] In one embodiment, if there are only two cells in the system—one scheduling cell and one scheduled cell—the DCI used for two-cell scheduling may not include a CIF. Typically, the DCI used for two-cell scheduling may have a different size than the DCI used for single-cell scheduling. In this case, it is possible to distinguish the DCI format by its size, thus eliminating the need for a CIF in the DCI used for two-cell scheduling.

[0101] In one embodiment, a CIF value can be configured on the scheduling cell used for single-cell scheduling or two-cell scheduling. In existing NR systems, to support cross-carrier scheduling, one or only one CIF value is assigned to the serving cell. The CIF value is used to identify the cell in cross-carrier scheduling. When two-cell scheduling is configured, multiple CIF values ​​can be configured for the serving cell used for single-cell scheduling or two-cell scheduling. The CrossCarrierSchedulingConfig IE can be used to indicate the configuration of two-cell scheduling. In the scheduling cell used for two-cell scheduling, cif-presence in the CrossCarrierSchedulingConfig IE can be set to true. On the other hand, for the scheduled cell, scheduleCellId can indicate the serving cell index of the scheduling cell, and cif-InSchedulingCell can indicate one or more CIF values ​​used in the scheduling cell to indicate that the DCI for two-cell scheduling applies to the scheduled cell.

[0102] In one embodiment, to support two-cell scheduling, one or more pairs of cells can be configured on a cell via higher-layer signaling to be scheduled by a DCI used for two-cell scheduling. The cell can be a cell that transmits the DCI for two-cell scheduling. For example, the cell is a scheduling cell.

[0103] In one embodiment, multiple CIF values ​​can be configured in the serving cell configuration. For example, in the CrossCarrierSchedulingConfig IE, the cif-InSchedulingCell can be expanded to indicate multiple CIF values. Then, based on the CIF configurations of all serving cells in CA operations, UE 101 can identify the exact behavior corresponding to a specific CIF value. If a CIF value is configured for only one serving cell, that serving cell can be scheduled by a DCI for single-cell scheduling with that CIF value. On the other hand, if a CIF value is configured for at least two serving cells, both serving cells can be scheduled by a DCI for two-cell scheduling with that CIF value. In this way, a single value space for the CIF field can be used to indicate both single-cell and two-cell scheduling.

[0104] In one embodiment, if a CIF value can be independently indicated for single-cell scheduling and two-cell scheduling, then a CIF can be defined separately for two-cell scheduling. Multiple CIF values ​​can be configured in the serving cell's configuration. For example, in the CrossCarrierSchedulingConfig IE, the cif-InSchedulingCell can be expanded to indicate multiple CIF values. Then, based on the CIF configurations of all serving cells in CA operations, UE 101 can identify the exact behavior of a specific CIF value. That is, two serving cells configured with the same CIF value can be scheduled by a DCI indicating that same CIF value for two-cell scheduling.

[0105] Size of the DCI format used for two-cell scheduling

[0106] To support scheduling of more than one cell (e.g., two cells) via a single DCI, the size of the DCI used for multi-cell scheduling may be larger than the size of the existing DCI used for single-cell scheduling. When designing the size of the DCI for multi-cell scheduling, efficient scheduling of more than one cell should be considered.

[0107] In this embodiment of the disclosure, for the sake of simplicity and clarity, a DCI for scheduling two cells is used as an example for illustration, but it can be directly extended to a DCI for scheduling more cells.

[0108] In one embodiment, two reference configurations can be configured and applied to two cells that can be scheduled by a DCI for two-cell scheduling. Therefore, the size of the field in the DCI for two-cell scheduling can be determined by applying the two reference configurations to these two cells.

[0109] In another embodiment, a general reference configuration can be configured and applied to two cells that can be scheduled by a DCI used for two-cell scheduling. Therefore, the size of fields in the DCI used for two-cell scheduling can be determined by applying the general reference configuration to the two cells. For example, the general reference configuration can be determined by the current active BWP of a reference cell from both cells.

[0110] In one embodiment, the size of fields in the DCI used for two-cell scheduling can be configured via higher-layer signaling.

[0111] In another embodiment, the size of the field in the DCI used for two-cell scheduling can be determined by the configuration of the current active BWPs of the two cells. Alternatively, the size of the field in the DCI used for two-cell scheduling can be determined by the configuration of the active BWP of a reference cell, which is applicable to both cells. For example, the reference cell can be configured via higher-layer signaling. Alternatively, the reference cell can be the scheduling cell. Alternatively, the reference cell can be the fixed cell of the two cells, for example, the cell with the lower cell index.

[0112] Size alignment of DCI format for two-cell scheduling

[0113] In some embodiments, for a cell scheduled by a DCI for two-cell scheduling, the fields in the DCI have a size that is not significantly different from the same fields of the active BWP of the cell scheduled by the DCI for two-cell scheduling. In an example, the size of the field determined by the reference configuration may differ from the size of the corresponding field of the active BWP on the cell on which PDSCH / PUSCH will be scheduled. In another example, if a BWP handover is triggered by a DCI for two-cell scheduling, the size of the field in the DCI may differ from the size of the corresponding field of the new active BWP of that cell (i.e., the active BWP to which it is to be handed over).

[0114] In one embodiment, a certain Layer 1 control information can be represented by a single field in the DCI used for two-cell scheduling, which can be applied to both cells. For example, it can be assumed that the size of the field in the DCI used for two-cell scheduling is represented as size_A, and the size of the same field of the active BWP of the scheduled cell above it, according to PDSCH / PUSCH, is represented as size_B. If size_A is less than size_B, zero-padding can be applied to the field in the DCI to match size_A with size_B. If size_A is greater than size_B, truncation can be applied to the field in the DCI to match size_A with size_B.

[0115] In another embodiment, a certain Layer 1 control information can be represented separately by two fields in the DCI used for two-cell scheduling, and these two fields can be applied to the two cells respectively. The size alignment of the two fields used for the same control information can be performed separately or jointly.

[0116] As an example, for a DCI used for two-cell scheduling that carries two fields carrying the same control information for both cells, either of these fields can be aligned with the corresponding field of the active BWP of the scheduled cell to which that field will be applied. That is, the size of either of the two fields is checked independently for each cell. For example, it can be assumed that the size of one of the two fields in the DCI used for two-cell scheduling is represented as size_A, and the size of the same field of the active BWP of the scheduled cell to be scheduled by this DCI according to its PDSCH / PUSCH is represented as size_B. If size_A is less than size_B, zero-padding can be applied to that field in the DCI to match size_A with size_B. If size_A is greater than size_B, truncation can be applied to that field in the DCI to match size_A with size_B.

[0117] As another example, for two fields in a DCI used for two-cell scheduling that carry the same control information for both cells, the sizes of the two fields can be jointly determined. For instance, it can be assumed that the sizes of the two fields in the DCI used for two-cell scheduling are represented as size_A, and the sum of the sizes of the same field of the active BWPs of the two scheduled cells to be scheduled by this DCI according to the PDSCH / PUSCH is represented as size_B. If size_A is less than size_B, zero-padding can be applied to the two fields in the DCI to match size_A with size_B. If size_A is greater than size_B, truncation can be applied to the two fields in the DCI to match size_A with size_B.

[0118] Where zero-padding should be applied, both fields in the DCI can be zero-padding applied; alternatively, one of these fields can be resized to equal the size of the same field based on the active BWP of the corresponding cell, and zero-padding should be applied to the other field in the DCI. Priority rules can be defined to give priority to one of the two cells, and the corresponding field in the DCI for that cell will not be zero-padding. For example, the preferred cell can be specified via higher-layer signaling; alternatively, one of the two cells can be determined as the preferred cell, for example, the cell with the lower cell index; alternatively, the scheduled cell is always prioritized.

[0119] Figure 7 An example case is shown where the joint size of two fields in a DCI used for two-cell scheduling is determined according to some embodiments of this disclosure. For example... Figure 7 As shown, suppose two fields in the DCI used for two-cell scheduling are used to carry specific information about the two cells on which PDSCH / PUSCH will be scheduled, and these two fields are represented as fields A1 and A2. Based on the active BWP of the two cells, the required size of field A1 is smaller than the size of field A1 in the DCI, while the required size of field A2 is larger than the size of field A2 in the DCI. Similarly... Figure 7 As shown, the total size of fields A1 and A2 in the DCI is greater than the total size required for the same fields based on the active BWPs of the two cells. Therefore, fields A1 and A2, which have sizes derived from the active BWPs of the two cells, can both be included in the DCI.

[0120] Figure 8 Another example of jointly determining the size of two fields in a DCI used for two-cell scheduling, according to some embodiments of this disclosure, is shown. For example... Figure 8 As shown, it is further assumed that two fields in the DCI used for two-cell scheduling are used to carry specific information about the two cells on which PDSCH / PUSCH will be scheduled, and these two fields are represented as fields A1 and A2. Based on the active BWP of the two cells, the required size of field A1 is larger than the size of field A1 in the DCI, while the required size of field A2 is smaller than the size of field A2 in the DCI. Similarly... Figure 8 As shown, the total size of fields A1 and A2 in the DCI is less than the total size required for the same fields based on the active BWPs of the two cells. Therefore, the size of field A1 can be truncated to be equal to the size determined by the active BWP of the preferred cell, while the size of field A2 can be padded with zeros to be equal to the size determined by the active BWP of the other of the two cells.

[0121] In one embodiment, on the gNB side, to generate a DCI for two-cell scheduling, the size alignment of the DCI fields can be performed in two steps. First, the total size of all fields in the DCI for two-cell scheduling can be checked relative to the total size of these fields based on the active BWPs on the two cells scheduled by the DCI. If the total size of all fields in the DCI is greater than or equal to the total size of these fields based on the active BWPs on the two cells, the size of each field in the DCI can be determined based on the active BWPs on the two cells. In this case, zero-padding can be applied to the total size derived from the active BWPs to match the size of the DCI. If the total size of all fields in the DCI is less than the total size of these fields based on the active BWPs on the two cells, a second step (e.g., truncation) can be used to match the size of the DCI. For example, truncation can be applied only to the fields with larger sizes derived from the active BWPs.

[0122] Number of DCI sizes for different DCI formats

[0123] In existing NR systems, the maximum number of DCI sizes a UE can detect is limited. In NR Rel-15, for each serving cell, the UE is expected to monitor PDCCH candidates to discover up to four DCI sizes for all DCI formats, and up to three DCI sizes for DCI formats with Cyclic Redundancy Check (CRC) scrambled by Cell Radio Network Temporary Identity (C-RNTI), Configuration Scheduling (CS)-RNTI, or MCS-RNTI. The UE can count the DCI sizes of DCI formats per serving cell based on the set of DCI formats configured to be monitored in each search space set of the corresponding active DL / UL BWP. A potential problem may be how to count the DCI sizes used for two-cell scheduling.

[0124] For example, the maximum number of DCI sizes for all DCI formats in each serving cell can be represented as M, and the maximum number of DCI sizes for each serving cell with a C-RNTI-scrambled CRC DCI format can be represented as N. When applying a DCI format for two-cell scheduling in one cell, the maximum values ​​of M and N can remain unchanged with existing NR operations, for example, in an existing NR system, M equals 4 and N equals 3. Alternatively, the maximum values ​​of M and N can be increased. The value N can be increased under the constraint that N ≤ M. For example, N can be increased by 1, so that M and N equal 4. Alternatively, the values ​​of both M and N can be increased under the constraint that N ≤ M. For example, both M and N can be increased by 1, so that M equals 5 and N equals 4.

[0125] In one embodiment, if the scheduling cell is one of the scheduled cells in a two-cell scheduling, then the DCI used for two-cell scheduling can be counted as the DCI belonging to that scheduling cell. Therefore, the number of DCI sizes with respect to the scheduling cell, including the size of the DCI used for two-cell scheduling, should not exceed the maximum number of DCI sizes M and / or N.

[0126] Specifically, if DL / UL transmissions on the PCell can be scheduled by the SCell, then a DCI for two-cell scheduling can be configured on the SCell to schedule DL / UL transmissions on both the PCell and the SCell. In this case, the DCI for two-cell scheduling can be counted as a DCI belonging to the SCell. Therefore, the number of DCI sizes for the SCell, including the DCI size for two-cell scheduling, should not exceed the maximum number of DCI sizes.

[0127] In one embodiment, if the scheduled cell is one of two cells scheduled for two-cell scheduling using a DCI, then the DCI used for two-cell scheduling can be counted as a DCI belonging to the other scheduled cell. Therefore, the number of DCI sizes with respect to the other scheduled cells, including the DCI size used for two-cell scheduling, should not exceed the maximum number of DCI sizes M and / or N. For example, the DCI used for two-cell scheduling can be configured in the search space set configuration of the other scheduled cell. DCIs can be sent on search space sets with the same search space set index on the active DL / UL BWP of the scheduled cell.

[0128] In one embodiment, the DCI used for two-cell scheduling can be counted as the DCI belonging to the reference cell of the two cells scheduled by the DCI used for two-cell scheduling. Therefore, the number of reference cell DCI sizes, including the DCI size used for two-cell scheduling, should not exceed the maximum number of DCI sizes M and / or N. For example, the two scheduled reference cells can be specified by higher-layer signaling. Alternatively, one of the two scheduled cells can be identified as the reference cell. For example, the reference cell is the cell with the lower cell index. Alternatively, the cell with the smaller number of DCI sizes among the two cells can be identified as the reference cell.

[0129] In the above embodiments, after aligning the DCI sizes for DCI formats 0_0, 1_0, 0_1, 1_1, 0_2, and 1_2 (e.g., the step defined in section 7.3.1.0 of TS 38.212), if the number of DCI sizes for the cell's DCI format, including the DCI size for two-cell scheduling, exceeds the maximum number of DCI sizes M and / or N, certain procedures can be performed until the number of DCI sizes does not exceed the maximum number of DCI sizes M and N. As mentioned above, the UL DCI for two-cell scheduling can be represented as DCI format 0_3, and the DL DCI for two-cell scheduling can be represented as DCI format 1_3.

[0130] In an embodiment, the number of DCI sizes used for DCI formats 0_0, 1_0, 0_1, 1_1, 0_2, 1_2, 0_3, and 1_3 can be reduced.

[0131] Figure 9 A flowchart of an example process 900 for reducing the number of DCI sizes according to some embodiments of the present disclosure is shown. As shown, process 900 may include, in 910, aligning the DCI sizes for DCI formats 0_3 and 1_3 if the number of DCI sizes exceeds a maximum number M and / or N of DCI sizes. If the number of DCI sizes still exceeds the maximum number M and / or N of DCI sizes, process 900 may include, in 920, aligning the DCI sizes for DCI formats 0_2 and 1_2 (if applicable). If the number of DCI sizes still exceeds the maximum number M and / or N of DCI sizes, process 900 may include, in 930, aligning the DCI sizes for DCI formats 0_1 and 1_1 (if applicable).

[0132] Figure 10A flowchart of another example process 1000 for reducing the number of DCI sizes according to some embodiments of this disclosure is shown. As shown, process 1000 may include, in 1010, aligning the DCI sizes for DCI formats 0_3 and 1_3 if the number of DCI sizes exceeds the maximum number of DCI sizes M and / or N. If the maximum number of DCI sizes M and / or N is still exceeded, process 1000 may include, in 1020, aligning the DCI sizes for DCI formats 0_3 and 1_3 to a cell-general or group-general DCI format (if applicable). The cell-general or group-general DCI format may be predefined or configured by a higher layer. To enable such size alignment, in embodiments, the higher layer provides the UE with the size to which DCI format 0_3 or 1_3 is to be aligned, in the form of a number of bits. In another embodiment, the UE can be provided with an indication via a higher layer regarding whether to align the size of DCI format 0_3 or 1_3 with a specific DCI format, such as DCI format 0_0 / 1_0, 0_1 / 1_1, or 0_2 / 1_2, or one or more UE group common DCI formats, such as a DCI format having CRC bits scrambled by interrupt RNTI (INT-RNTI), slot format indication RNTI (SFI-RNTI), transmit power control-PUSCH-RNTI (TPC-PUSCH-RNTI), transmit power control-PUCCH-RNTI (TPC-PUCCH-RNTI), transmit power control-listen reference symbol-RNTI (TPCSRS-RNTI), cancel indication-RNTI (CI-RNTI), or power saving-RNTI (PS-RNTI).

[0133] Figure 11A flowchart of another example process 1100 for reducing the number of DCI sizes according to some embodiments of the present disclosure is shown. As shown, process 1100 may include, in 1110, aligning the DCI sizes for DCI formats 0_3 and 1_3 if the number of DCI sizes exceeds the maximum number of DCI sizes M and / or N. If it still exceeds the maximum number of DCI sizes M and / or N, process 1100 may include, in 1120, aligning the DCI sizes for DCI formats 0_2 and 1_2 (if applicable). If it still exceeds the maximum number of DCI sizes M and / or N, process 1100 may include, in 1130, aligning the DCI sizes for DCI formats 0_1 and 1_1 (if applicable). If the maximum number of DCI sizes M and / or N is still exceeded, then process 1100 may include, in 1140, aligning the DCI sizes for DCI formats 0_3 and 1_3 to a cell-wide or group-wide DCI format (if applicable). The cell-wide or group-wide DCI format may be predefined or configured by higher layers.

[0134] In another example, in addition to the above-described process of attempting to manage the DCI size for DCI formats 0_3 and / or 1_3, to ensure that the maximum DCI size M / N is not exceeded, the gNB can configure the DCI size for the UE group common DCI format (e.g., a DCI format with CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPCSRS-RNTI, CI-RNTI, or PS-RNTI) to be the same as the DCI size for one or more of the following: DCI formats 0_0 / 1_0, 0_1 / 1_1, 0_2 / 1_2, or 0_3 / 1_3. The PDCCH candidates and non-overlapping control channel elements (CCEs) to be monitored. Maximum quantity

[0135] In NR operations, UE capabilities for blind PDCCH detection are defined. Specifically, for each serving cell, the maximum number of PDCCH candidates and non-overlapping CCEs to be monitored is defined. In CA operations, PCells support PDCCH overbooking. If the number of PDCCH candidates and non-overlapping CCEs configured for a PCell to monitor exceeds the maximum, priority rules are defined to select valid PDCCH candidates. On the other hand, for one or more SCells with a certain numbering (e.g., subcarrier spacing), it is assumed that the gNB can guarantee that the configured number of PDCCH candidates and non-overlapping CCEs to be monitored does not exceed the maximum. For cross-carrier scheduling with different numbers, the limit on the number of PDCCH candidates and non-overlapping CCEs to be monitored can be derived from the numbering of the scheduling cells. A potential problem might be how to count the number of PDCCH candidates and non-overlapping CCEs to be monitored for the DCI used for two-cell scheduling.

[0136] In one embodiment, if the scheduling cell is one of two cells scheduled by a two-cell scheduling mechanism, the DCI used for two-cell scheduling can be included in the scheduling cell count. Therefore, the number of PDCCH candidates and non-overlapping CCEs to be monitored in the scheduling cell, including the search space set for DCIs used for cell scheduling, should not exceed the maximum number of PDCCH candidates and non-overlapping CCEs to be monitored.

[0137] In one embodiment, if the scheduling cell is one of two cells scheduled by a two-cell scheduling mechanism, the DCI used for the two-cell scheduling can be counted in the other cell scheduled by that DCI. Therefore, the number of PDCCH candidates and non-overlapping CCEs to be monitored in that other cell, including the search space set for the DCI used for two-cell scheduling, should not exceed the maximum number of PDCCH candidates and non-overlapping CCEs to be monitored. For example, the DCI for two-cell scheduling can be configured on the search space set of the other cell. The DCI can be transmitted on a search space set with the same search space set index on the active DL / UL BWP of the scheduling cell.

[0138] In one embodiment, for two-cell scheduling, the DCI used for two-cell scheduling can be counted in the scheduling cell, regardless of whether the scheduling cell is one of the two cells being scheduled by the DCI. Therefore, the number of PDCCH candidates and non-overlapping CCEs to be monitored in the scheduling cell, including the search space set for the DCI used for two-cell scheduling, should not exceed the maximum number of PDCCH candidates and non-overlapping CCEs to be monitored.

[0139] In one embodiment, for two cells that can be scheduled by two-cell scheduling, the DCI for two-cell scheduling can be included in the reference cell. Therefore, the number of PDCCH candidates to be monitored and non-overlapping CCEs in the reference cell, including the search space set for the DCI for two-cell scheduling, should not exceed the maximum number of PDCCH candidates to be monitored and non-overlapping CCEs. The reference cell can be specified from these two cells by higher-layer signaling. Alternatively, one of the two cells can be determined as the reference cell based on the specification. Alternatively, the reference cell can be the cell scheduled by the DCI for two-cell scheduling rather than the scheduling cell. In addition, if neither of the two cells scheduled by the DCI is the scheduling cell, the blind detection of the PDCCH can be partitioned and counted for the two cells. For example, it can be counted as 0.5 PDCCH candidates and AL / 2 non-overlapping CCEs for each of the two cells, where AL is the aggregation level of the PDCCH candidate.

[0140] Specifically, if the DL / UL transmission on the PCell can be scheduled by the SCell, the DCI for two-cell scheduling can be configured on the SCell. In this case, the DCI for two-cell scheduling can be included in the SCell, i.e., the scheduling cell. Therefore, the number of PDCCH candidates to be monitored and non-overlapping CCEs for scheduling the SCell, including the search space set for the DCI for two-cell scheduling, should not exceed the maximum number of PDCCH candidates to be monitored and non-overlapping CCEs to be monitored.

[0141] In one embodiment, for two cells that can be scheduled by the DCI for two-cell scheduling, the blind detection of the DCI for two-cell scheduling can be counted as (x1, x2) PDCCH candidates and (y1·AL, y2·AL) non-overlapping CCEs for the two cells respectively. x1, x2, y1, y2 are scaling factors that can be predefined or configured by higher-layer signaling, where 0 < x1 < 1, 0 < x2 < 1, 0 < y1 < 1, 0 < y2 < 1. For example, x1 = x2 = y1 = y2 = 0.5. For example, for the DCI scheduling the PCell and the SCell, assuming that x1, y1 are configured for the PCell and x2, y2 are configured for the SCell, allowing the detection of more PDCCHs transmitted on the PCell or scheduling transmissions on the PCell by assigning smaller values to x1, y1 than to x2, y2.

[0142] In one embodiment, for two cells that can be scheduled via two-cell scheduling, the total number of PDCCH candidates and non-overlapping CCEs to be monitored in the two cells, including the search space set for DCI used for two-cell scheduling, should not exceed the maximum total number of PDCCH candidates and non-overlapping CCEs to be monitored in the two cells. Furthermore, without considering DCI used for two-cell scheduling, the number of PDCCH candidates and non-overlapping CCEs to be monitored in one of the two cells should not exceed the maximum number of PDCCH candidates and non-overlapping CCEs to be monitored in that cell.

[0143] In one embodiment, support for the DCI format used for two-cell scheduling and support for PDCCH search space sharing for cross-carrier scheduling of the UE can be coupled together. In one example, it is anticipated that a UE supporting the DCI format used for two-cell scheduling will also support search space sharing via searchSpaceSharingCA-UL or searchSpaceSharingCA-DL.

[0144] Generally, the DCI format used for two-cell scheduling can be configured for monitoring in the primary cell (e.g., PCell or PSCell) or in the SCell. Furthermore, as mentioned above, according to NR Releases 15 and 16 specifications, the total number of candidates that can be configured for monitoring in the primary cell can exceed the non-CA limit of the primary cell, while the PDCCH candidates configured for the SCell can be ensured by the network not to exceed the CA limit. This is referred to as "over-subscription of PDCCH monitoring capability," and in such cases, once the non-CA limit is exceeded, the UE can discard monitoring of certain search space sets in the time slot based on the search space set index. A search space set configured with the DCI format for two-cell scheduling can be prioritized over another search space set without having to configure the DCI format for two-cell scheduling for the active DL / UL BWP on the cell. Here, the non-CA limit can correspond to the minimum requirement for PDCCH monitoring in the time slot of the serving cell in non-CA operation, while the CA limit is defined as the sum of BDs or non-overlapping CCEs across all scheduled cells for a given subcarrier spacing (SCS).

[0145] With the introduction of DCI formats for two-cell scheduling, certain PDCCH candidates and non-overlapping CCEs will carry the following DCI formats: (i) for scheduling in both SCells, or (ii) for scheduling in the primary cell (PCell or PSCell) and the SCell. For the first case, the gNB may need to ensure that the configured PDCCH candidates used for scheduling PDSCH / PUSCH in the SCell do not exceed the BD / CCE capabilities determined for a specific CA configuration and the UE's reporting capabilities. On the other hand, for the second case, a different approach can be considered, as described below.

[0146] In one embodiment, if one or more DCI formats for two-cell scheduling are configured to be monitored in the SCell, and one or more DCI formats for two-cell scheduling are configured to schedule PDSCH / PUSCH on the primary cell (and secondary cell), the UE will not expect to be configured with multiple PDCCH candidates that would cause the number of BD or non-overlapping CCEs to exceed the BD / CCE limit for the primary cell, respectively. In this case, PDCCH oversubscription can be applied to the secondary cell on which monitoring of the DCI for two-cell scheduling is configured.

[0147] In another embodiment, if one or more DCI formats for two-cell scheduling are configured to be monitored in the primary cell, and one or more DCI formats for two-cell scheduling are configured to schedule PDSCH / PUSCH on the primary cell (and secondary cell), then the UE will not expect to be configured with multiple PDCCH candidates that would cause the number of BD or non-overlapping CCEs to exceed the BD / CCE limit for the primary cell, respectively.

[0148] In the above scenario, a search space set(s) of DCI(s) used for two-cell scheduling (although monitored in the primary cell) can be configured as part of the serving cell configuration of either the primary or secondary cell. The following description further categorizes the case of monitoring (one or more) DCI(s) used for two-cell scheduling in the primary cell by determining whether oversubscription is permitted on the primary cell.

[0149] Therefore, in one embodiment, if one or more DCI formats for two-cell scheduling are configured to be monitored in the primary cell, one or more DCI formats for two-cell scheduling are configured to schedule PDSCH / PUSCH on the primary cell (and secondary cell), and if one or more search space sets having DCI for two-cell scheduling are also configured as part of the serving cell configuration of the secondary cell (similar to the case of cross-carrier scheduling), for example, BD and non-overlapping CCE corresponding to the DCI format for two-cell scheduling can be budgeted as "another scheduled cell" (in this case, the secondary cell), then the UE will not expect to be configured with multiple PDCCH candidates that would cause the number of BD or non-overlapping CCE to exceed the BD / CCE limit for the primary cell, respectively.

[0150] In another embodiment, if one or more DCI formats for two-cell scheduling are configured to be monitored in the primary cell, and one or more DCI formats for two-cell scheduling are configured to schedule PDSCH / PUSCH on the primary cell (and secondary cell), and if the search space set having one or more DCIs for two-cell scheduling is not configured as part of the serving cell configuration of the secondary cell (similar to the case of cross-carrier scheduling), for example, BDs and non-overlapping CCEs corresponding to the DCI formats for two-cell scheduling can be budgeted as the "scheduling cell" (in this case, the primary cell), then the UE will not expect to be configured with multiple PDCCH candidates that would cause the number of BDs or non-overlapping CCEs to exceed the BD / CCE limit for the primary cell, respectively. Furthermore, over-subscription on the primary cell can be performed only with respect to the single-cell limit on the primary cell.

[0151] One or more DCI formats used for two-cell scheduling will be configured for use between the serving cells. The aforementioned differences can be used to determine the n used in the hash function. CI The value of this hash function is used to determine the starting CCE index for the PDCCH candidates of the configuration to be monitored. Specifically, in one option (regardless of whether to semi-statically determine the pair of cells to be scheduled via the DCI format for two-cell scheduling and whether to use the CIF field in the DCI format for two-cell scheduling), the CIF value can be provided as part of the serving cell configuration via CrossCarrierSchedulingConfig, and this value can be used in the hash function for n CI Values. In addition, the range of CIF values ​​can be extended beyond the current range {1, ..., 7}. For example, the range of values ​​can be extended to {1, ..., 7, 8, ..., 16}, so that values ​​greater than seven are only available when the UE is scheduled using the DCI format (one or more) for two-cell scheduling of the serving cell.

[0152] Total number of PDSCH / PUSCH pending processing by UE

[0153] In NR Rel-15, for a scheduled cell, at any given time, the UE may expect to receive up to 16 PDCCHs with DCI format 1_0 or 1_1 of CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI for 16 scheduled PDSCH receptions (for which the UE has not yet received any corresponding PDSCH symbols), and up to 16 PDCCHs with DCI format 0_0 or 0_1 of CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI for 16 scheduled PUSCH transmissions (for which the UE has not yet transmitted any corresponding PUSCH symbols).

[0154] If DCI for two-cell scheduling is supported, DCI can schedule 2 PDSCHs on two cells. In this case, when checking the maximum 16 PDCCHs for each cell, the DCI for two-cell scheduling can be counted for both cells. For a scheduled cell, at any time, the UE may expect to receive up to 16 PDCCHs with DCI format 1_0 or 1_1 or 1_2 or 1_3 with CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI for scheduled 16 PDSCH receptions (for which the UE has not yet received any corresponding PDSCH symbols), and up to 16 PDCCHs with DCI format 0_0 or 0_1 or 0_2 or 0_3 with CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI for scheduled 16 PUSCH transmissions (for which the UE has not yet transmitted any corresponding PUSCH symbols).

[0155] Figure 12 The following is a flowchart illustrating a process 1200 for PDSCH / PUSCH scheduling according to some embodiments of the present disclosure. Process 1200 may be, for example... Figure 1 UE 101 is used to execute.

[0156] Process 1200 may include, at 1210, decoding a DCI received on the PDCCH of a scheduling cell, wherein the DCI is configured to schedule the PDSCH or PUSCH of more than one cell. As mentioned above, the DCI may be a DCI for multi-cell scheduling, and more specifically, a DCI for two-cell scheduling.

[0157] Process 1200 may include, at 1220, performing communication on the PDSCH or PUSCH of more than one cell (e.g., two cells) according to the instructions of the DCI.

[0158] In addition, in order to implement procedure 1200 in the UE, a procedure can be performed by the access node (AN) to generate a DCI for scheduling PDSCH or PUSCH on more than one cell; and transmit the DCI on the PDCCH.

[0159] More specifically, Figure 9 The process 900 Figure 10 Process 1000 Figure 11 Process 1100 and Figure 12 The process 1200 can be implemented in one or more modules as a set of logic instructions stored in a machine or computer-readable storage medium such as random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), firmware, flash memory; in configurable logic such as programmable logic array (PLA), field-programmable gate array (FPGA), complex programmable logic device (CPLD); in fixed-function logic hardware using circuit technologies such as application-specific integrated circuit (ASIC), complementary metal-oxide-semiconductor (CMOS) or transistor-transistor logic (TTL); or in any combination thereof.

[0160] For example, used to execute Figure 9 The process 900 Figure 10 Process 1000 Figure 11 Process 1100 and Figure 12 The computer program code for the operations shown in process 1200 can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as JAVA, SMALLTALK, C++, etc., and conventional procedural programming languages ​​such as the "C" programming language or similar programming languages. Additionally, the logic instructions can include assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, state setting data, integrated circuit configuration data, and state information that personalizes hardware-local electronic circuits and / or other structural components (e.g., main processor, central processing unit / CPU, microcontroller, etc.).

[0161] System and Implementation

[0162] Figure 13-14 Various systems, devices, and components are shown that can implement multiple aspects of the disclosed embodiments.

[0163] Figure 13Illustrations of a network 1300 according to various embodiments of the present disclosure are shown. Network 1300 can operate in a manner consistent with 3GPP technical specifications for LTE or 5G / NR systems. However, the exemplary embodiments are not limited in this respect, and the described embodiments can be applied to other networks that benefit from the principles described herein, such as future 3GPP systems, etc.

[0164] Network 1300 may include UE 1302, which may include any mobile or non-mobile computing device designed to communicate with RAN 1304 via an over-the-air connection. UE 1302 may be, but is not limited to, smartphones, tablets, wearable computing devices, desktop computers, laptops, in-vehicle infotainment devices, in-vehicle entertainment devices, instrument clusters, head-up displays, in-vehicle diagnostic devices, dashboard mobile devices, mobile data terminals, electronic engine management systems, electronic / engine control units, electronic / engine control modules, embedded systems, sensors, microcontrollers, control modules, engine management systems, networked appliances, machine-type communication devices, M2M or D2D devices, Internet of Things devices, etc.

[0165] In some embodiments, network 1300 may include multiple UEs that are directly coupled to each other via sidelink interfaces. The UEs may be M2M / D2D devices that communicate using physical sidelink channels (e.g., but not limited to, physical sidelink broadcast channel (PSBCH), physical sidelink discovery channel (PSDCH), physical sidelink shared channel (PSSCH), physical sidelink control channel (PSCCH), physical sidelink basic channel (PSFCH), etc.).

[0166] In some embodiments, UE 1302 can also communicate with AP 1306 via an over-the-air connection. AP 1306 manages WLAN connections and can be used to offload some / all network traffic from RAN 1304. The connection between UE 1302 and AP 1306 can be consistent with any IEEE 802.13 protocol, wherein AP 1306 can be Wireless Fibre. Router. In some embodiments, UE1302, RAN 1304, and AP 1306 may utilize cellular WLAN aggregation (e.g., LTE-WLAN aggregation (LWA) / Lightweight IP (LWIP)). Cellular WLAN aggregation may involve UE 1302, configured by RAN 1304, utilizing both cellular radio resources and WLAN resources.

[0167] RAN 1304 may include one or more access nodes, such as AN 1308. AN 1308 can terminate the air interface protocol of UE 1302 by providing access layer protocols including RRC, Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), Media Access Control (MAC), and L1 protocol. In this way, AN 1308 enables data / voice connectivity between CN 1320 and UE 1302. In some embodiments, AN 1308 may be implemented in a discrete device or as one or more software entities running on a server computer as part of, for example, a virtual network, which may be referred to as CRAN or a virtual baseband unit pool. AN 1308 may be referred to as a base station (BS), gNB, RAN node, evolved Node B (eNB), next-generation eNB (ng-eNB), Node B (NodeB), roadside unit (RSU), TRxP, TRP, etc. AN 1308 can be a macro cell base station or a low-power base station, used to provide microcells, picocells, or other similar cells with smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

[0168] In embodiments where RAN 1304 includes multiple ANs, they can be coupled to each other via an X2 interface (in the case of RAN 1304 being an LTE RAN) or an Xn interface (in the case of RAN 1304 being a 5G RAN). In some embodiments, the X2 / Xn interfaces, which can be separated into a control plane interface and a user plane interface, can allow ANs to transmit and handover, data / context transfer, mobility, load management, interference coordination, and other related information.

[0169] The AN of RAN 1304 can manage one or more cells, cell groups, component carriers, etc., to provide an air interface for network access to UE 1302. UE 1302 can simultaneously connect to multiple cells provided by the same or different ANs of RAN 1304. For example, UE 1302 and RAN 1304 can use carrier aggregation to allow UE 1302 to connect to multiple component carriers, each component carrier corresponding to a primary cell (Pcell) or a secondary cell (Scell). In dual connectivity scenarios, the first AN can be the primary node providing the primary cell group (MCG), and the second AN can be the secondary node providing the secondary cell group (SCG). The first / second AN can be any combination of eNB, gNB, ng-eNB, etc.

[0170] RAN 1304 can provide an air interface on either licensed or unlicensed spectrum. For operation in unlicensed spectrum, nodes can use Licensed Assisted Access (LAA), Enhanced LAA (eLAA), and / or further enhanced LAA (feLAA) mechanisms based on carrier aggregation (CA) technology with PCell / Scell. Before accessing unlicensed spectrum, nodes can perform medium / carrier sensing operations based on, for example, a Listen-Before-Speak (LBT) protocol.

[0171] In a vehicle-to-everything (V2X) scenario, UE 1302 or AN 1308 can be or act as a roadside unit (RSU), which can refer to any transportation infrastructure entity used for V2X communication. An RSU can be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by a UE can be referred to as a "UE-type RSU"; an RSU implemented in or by an eNB can be referred to as an "eNB-type RSU"; an RSU implemented in or by a next-generation NodeB (gNB) can be referred to as a "gNB-type RSU"; and so on. In one example, the RSU is a computing device coupled to radio frequency circuitry located on the roadside, providing connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU can provide very low-latency communication required for high-speed events, such as collision avoidance, traffic warnings, etc. Alternatively or additionally, the RSU can provide other cellular / WLAN communication services. RSU components can be enclosed in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller to provide wired connectivity (e.g., Ethernet) to traffic signal controllers or backhaul networks.

[0172] In some embodiments, RAN 1304 may be LTE RAN 1310, which includes an evolved Node B (eNB), such as eNB 1312. LTE RAN 1310 can provide an LTE air interface with the following characteristics: 15kHz SCS; CP-OFDM waveforms for DL ​​and SC-FDMA waveforms for UL; turbo codes for data and TBCC for control, etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management; rely on PDSCH / PDCCH demodulation reference signals (DMRS) for PDSCH / PDCCH demodulation; and rely on CRS for cell search and initial acquisition, channel quality measurement, and channel estimation for coherent demodulation / detection at the UE. The LTE air interface can operate in the sub-6GHz band.

[0173] In some embodiments, RAN 1304 may be a next-generation (NG)-RAN 1314 with a gNB (e.g., gNB 1316) or a gn-eNB (e.g., ng-eNB 1318). gNB 1316 can connect to a 5G-enabled UE using a 5G NR interface. gNB 1316 can connect to the 5G core via an NG interface, which may include an N2 interface or an N3 interface. ng-eNB 1318 can also connect to the 5G core via an NG interface, but can connect to the UE via an LTE air interface. gNB 1316 and ng-eNB 1318 can connect to each other via an Xn interface.

[0174] In some embodiments, the NG interface can be divided into two parts: the NG user plane (NG-U) interface and the NG control plane (NG-C) interface. The former carries traffic data between the nodes of NG-RAN 1314 and UPF 1348, while the latter is the signaling interface (e.g., the N2 interface) between NG-RAN 1314 and the nodes of Access and Mobility Management Function (AMF) 1344.

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

[0176] In some embodiments, the 5G-NR air interface can use BWPs for various purposes. For example, BWPs can be used for dynamic adaptation of SCS. For instance, UE 1302 can be configured with multiple BWPs, each configured with a different SCS. When a BWP is indicated to UE 1302 for a change, the transmitted SCS also changes. Another use case for BWPs relates to power saving. Specifically, multiple BWPs with different numbers of frequency resources (e.g., PRBs) can be configured for UE 1302 to support data transmission under different traffic load scenarios. A BWP containing fewer PRBs can be used for data transmission with lower traffic loads, while allowing power saving at UE 1302 and, in some cases, at gNB 1316. A BWP containing more PRBs can be used for scenarios with higher traffic loads.

[0177] RAN 1304 is communicatively coupled to CN 1320, which includes network elements, to provide various functions supporting data and telecommunications services to customers / subscribers (e.g., users of UE 1302). Components of CN 1320 may be implemented in a single physical node or in different physical nodes. In some embodiments, NFV may be used to virtualize any or all of the functionality provided by the network elements of CN 1320 onto physical compute / storage resources such as servers, switches, etc. A logical instance of CN 1320 may be referred to as a network slice, and a logical instantiation of a portion of CN 1320 may be referred to as a network subslice.

[0178] In some embodiments, CN 1320 may be LTE CN 1322, which may also be referred to as the Evolved Packet Core (EPC). LTE CN 1322 may include a Mobility Management Entity (MME) 1324, a Serving Gateway (SGW) 1326, a Serving GPRS Support Node (SGSN) 1328, a Home Subscriber Server (HSS) 1330, a Proxy Gateway (PGW) 1332, and a Policy Control and Charging Rules Function (PCRF) 1334, as shown in the figure. These components are coupled to each other through interfaces (or "reference points"). The functions of the elements of LTE CN 1322 can be briefly described below.

[0179] MME 1324 can implement mobility management functions to track the current location of UE 1302, thereby facilitating patrol, bearer activation / deactivation, handover, gateway selection, authentication, etc.

[0180] The SGW 1326 can terminate the S1 interface toward the RAN and route data packets between the RAN and the LTE CN 1322. The SGW 1326 can serve as a local mobility anchor for handover between RAN nodes and can also provide anchoring for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and some policy enforcement.

[0181] SGSN 1328 can track the location of UE 1302 and perform security functions and access control. Additionally, SGSN 1328 can perform EPC inter-node signaling for mobility between different RAT networks; PDN and S-GW selection specified by MME 1324; MME selection for handover, etc. The S3 reference point between MME 1324 and SGSN 1328 enables the exchange of user and bearer information for 3GPP indirect network access mobility in idle / active states.

[0182] The HSS 1330 may include a database for network users, containing subscription-related information that supports network entities in handling communication sessions. The HSS 1330 can provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependencies, etc. An S6a reference point between the HSS 1330 and the MME 1324 enables the transmission of subscription and authentication data to authenticate / authorize user access to the LTE CN 1320.

[0183] PGW 1332 can terminate the SGi interface toward a data network (DN) 1336, which may include an application / content server 1338. PGW 1332 can route data packets between the LTE CN 1322 and the data network 1336. PGW 1332 can be coupled to SGW 1326 via an S5 reference point to facilitate user plane tunneling and tunnel management. PGW 1332 may also include nodes for policy enforcement and charging data collection (e.g., PCEF). Additionally, the SGi reference point between PGW 1332 and the data network 1336 can be, for example, an external public or private PDN or an internal packet data network for providing IMS services. PGW 1332 can be coupled to PCRF 1334 via a Gx reference point.

[0184] PCRF 1334 is the policy and charging control element of LTE CN 1322. PCRF 1334 can be communicatively coupled to application / content server 1338 to determine appropriate QoS and charging parameters for service flows. PCRF 1332 can provide the associated rules to PCEF (via Gx reference point) with appropriate TFT and QCI.

[0185] In some embodiments, CN 1320 may be a 5G core network (5GC) 1340. 5GC 1340 may include Authentication Server Function (AUSF) 1342, Access and Mobility Management Function (AMF) 1344, Session Management Function (SMF) 1346, User Plane Function (UPF) 1348, Network Slice Selection Function (NSSF) 1350, Network Open Function (NEF) 1352, NF Storage Function (NRF) 1354, Policy Control Function (PCF) 1356, Unified Data Management (UDM) 1358, and Application Function (AF) 1360, as shown in the figure. These functions are coupled to each other through interfaces (or "reference points"). The functions of the components of 5GC 1340 can be briefly described below.

[0186] The AUSF 1342 can store data for UE 1302 authentication and handle authentication-related functions. The AUSF 1342 facilitates a common authentication framework for various access types. In addition to communicating with other components of the 5GC 1340 via a reference point, as shown in the figure, the AUSF 1342 can also demonstrate an interface based on Nausf services.

[0187] The AMF 1344 allows the 5GC 1340 to communicate with UE 1302 and RAN 1304, and subscribe to notifications regarding mobility events for UE 1302. The AMF 1344 can handle registration management (e.g., registering UE 1302), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 1344 can provide the transmission of Session Management (SM) messages between UE 1302 and SMF 1346, and acts as a transparent broker for routing SM messages. The AMF 1344 can also provide the transmission of SMS messages between UE 1302 and the SMSF. The AMF 1344 can interact with AUSF 1342 and UE 1302 to perform various security anchoring and context management functions. Furthermore, AMF 1344 can be the termination point of the RAN CP interface, which may include or be the N2 reference point between RAN 1304 and AMF 1344; AMF 1344 can serve as the termination point for NAS (N1) signaling and perform NAS encryption and integrity protection. AMF 1344 can also support NAS signaling with UE 1302 via the N3IWF interface.

[0188] SMF 1346 can be responsible for SM (e.g., session establishment, tunnel management between UPF 1348 and AN 1308); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuring flow control at UPF 1348 to route traffic to appropriate destinations; termination of interfaces to policy control functions; control of policy enforcement, charging, and QoS as a part; lawful interception (for SM events and interfaces to the LI system); termination of the SM portion of NAS messages; downlink data notification; initiating AN-specific SM information (sent to AN 1308 on N2 via AMF 1344); and determining the SSC mode of the session. SM can refer to the management of PDU sessions, and a PDU session or "session" can refer to the PDU connectivity service that provides or enables PDU exchange between UE 1302 and data network 1336.

[0189] The UPF 1348 can be used as an anchor point for mobility within and between RATs, an external PDU session point interconnecting with the data network 1336, and a branch point supporting multi-homed PDU sessions. The UPF 1348 can also perform packet routing and forwarding, packet inspection, user plane portion of policy rules, lawful packet interception (UP collection), traffic usage reporting, QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), uplink traffic authentication (e.g., SDF-to-QoS flow mapping), transport-level packet marking in uplink and downlink, and downlink packet buffering and downlink data notification triggering. The UPF 1348 may include an uplink classifier to support traffic flow routing to the data network.

[0190] NSSF 1350 can select a set of network slice instances to serve UE 1302. If needed, NSSF 1350 can also determine the allowed network slice selection assistance information (NSSAI) and the mapping to the subscribed individual NSSAI (S-NSSAI). NSSF 1350 can also determine the set of AMFs to be used to serve UE 1302 based on appropriate configuration and possibly by querying NRF 1354, or determine a list of candidate AMFs. The selection of a set of network slice instances for UE 1302 can be triggered by AMF 1344 (to which UE 1302 registers by interacting with NSSF 1350), resulting in a change of AMF. NSSF 1350 can interact with AMF 1344 via reference point N22; and can communicate with another NSSF in the visited network via reference point N31 (not shown). Furthermore, NSSF 1350 can expose an interface based on NNSSF services.

[0191] The NEF 1352 can securely disclose services and capabilities provided by 3GPP network functions for third parties, internal disclosure / redisclosure, AFs (e.g., AF 1360), edge computing, or fog computing systems. In these embodiments, the NEF 1352 can authenticate, authorize, or suppress AFs. The NEF 1352 can also translate information exchanged with AF 1360 and information exchanged with internal network functions. For example, the NEF 1352 can translate between AF service identifiers and internal 5GC information. The NEF 1352 can also receive information from other NFs based on their public capabilities. This information can be stored as structured data at the NEF 1352 or stored at a data storage NF using a standardized interface. The NEF 1352 can then redistribute the stored information to other NFs and AFs, or use it for other purposes such as analytics. Additionally, the NEF 1352 can expose interfaces based on Nnef services.

[0192] NRF 1354 supports service discovery, receiving NF discovery requests from NF instances and providing information about discovered NF instances to those instances. NRF 1354 also maintains information about available NF instances and the services they support. As used herein, the terms "instantiation," "instance," etc., can refer to the creation of an instance, and an "instance" can refer to the concrete occurrence of an object, such as during program code execution. Furthermore, NRF 1354 can demonstrate interfaces based on NRF services.

[0193] PCF 1356 can provide policy rules to control plane functions to enforce them, and can also support a unified policy framework to manage network behavior. PCF 1356 can also implement a frontend to access subscription information related to policy decisions in the UDR of UDM 1358. In addition to communicating with functions via reference points as shown in the figure, PCF 1356 also demonstrates an interface based on Npcf services.

[0194] UDM 1358 can process subscription-related information to support network entities in handling communication sessions and can store subscription data for UE 1302. For example, subscription data can be transmitted via the N8 reference point between UDM 1358 and AMF 1344. UDM 1358 can include two parts: an application front-end and a UDR. The UDR can store policy data and subscription data for UDM 1358 and PCF 1356, and / or structured data and application data for disclosure (including PFD for application detection and application request information for multiple UEs 1302) for NEF 1352. UDR 221 can expose a Nudr service-based interface to allow UDM 1358, PCF 1356, and NEF 1352 to access specific sets of stored data, as well as to read, update (e.g., add, modify), delete, and notify of relevant data changes in the subscription UDR. UDM may include UDM-FE, which is responsible for handling credentials, location management, subscription management, etc. Several different front-ends can provide services to the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification processing, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs via reference points as shown in the figure, the UDM 1358 can also demonstrate interfaces based on Nudm services.

[0195] The AF 1360 can provide application impact on traffic routing, provide access to NEF, and interact with the policy framework for policy control.

[0196] In some embodiments, 5GC 1340 can enable edge computing by selecting an operator / third-party service that is geographically close to the point to which UE 1302 attaches to the network. This can reduce latency and load on the network. To provide edge computing implementation, 5GC 1340 can select a UPF 1348 close to UE 1302 and perform traffic routing from UPF 1348 to data network 1336 via the N6 interface. This can be based on UE subscription data, UE location, and information provided by AF 1360. In this way, AF 1360 can influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 1360 is considered a trusted entity, the network operator can allow AF 1360 to interact directly with the relevant NF. Additionally, AF 1360 can expose interfaces based on Naf services.

[0197] Data network 1336 can represent various network operator services, Internet access, or third-party services that can be provided by one or more servers (including, for example, application / content server 1338).

[0198] Figure 14 A wireless network 1400 according to various embodiments is schematically illustrated. The wireless network 1400 may include a UE 1402 that communicates wirelessly with an AN 1404. The UE 1402 and the AN 1404 may be similar to and substantially interchangeable with equivalent components described elsewhere herein.

[0199] UE 1402 can be communicatively coupled to AN 1404 via connection 1406. Connection 1406 is shown as an air interface to enable communication coupling and can be consistent with cellular communication protocols operating at millimeter wave (mmWave) or sub-6 GHz frequencies, such as LTE or 5G NR protocols.

[0200] UE 1402 may include a host platform 1408 coupled to a modem platform 1410. Host platform 1408 may include application processing circuitry 1412, which may be coupled to protocol processing circuitry 1414 of modem platform 1410. Application processing circuitry 1412 may run various applications for UE 1402 to process source / receive application data. Application processing circuitry 1412 may also implement one or more layer operations to send / receive application data to / from a data network. These layer operations may include transport (e.g., UDP) and Internet (e.g., IP) operations.

[0201] Protocol processing circuitry 1414 can implement one or more layer operations to facilitate the transmission or reception of data via connection 1406. Layer operations implemented by protocol processing circuitry 1414 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

[0202] The modem platform 1410 may further include digital baseband circuitry 1416, which can implement one or more layer operations of "below" layer operations performed by protocol processing circuitry 1414 in the network protocol stack. These operations may include, for example, one or more of the following PHY operations: HARQ-ACK function, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bit metric determination, and multi-antenna port precoding / decoding. These functions may include one or more of the following: space-time, space-frequency, or spatial coding; reference signal generation / detection; preamble sequence generation and / or decoding; synchronization sequence generation / detection; blind decoding of control channel signals; and other related functions.

[0203] The modem platform 1410 may further include transmitting circuitry 1418, receiving circuitry 1420, RF circuitry 1422, and RF front-end (RFFE) circuitry 1424, which may include or be connected to one or more antenna panels 1426. In short, transmitting circuitry 1418 may include a digital-to-analog converter, mixer, intermediate frequency (IF) component, etc.; receiving circuitry 1420 may include an analog-to-digital converter, mixer, IF component, etc.; RF circuitry 1422 may include a low-noise amplifier, power amplifier, power tracking component, etc.; RFFE circuitry 1424 may include filters (e.g., surface acoustic wave filters), switches, antenna tuners, beamforming components (e.g., phased array antenna components), etc. The selection and arrangement of components of transmitting circuitry 1418, receiving circuitry 1420, RF circuitry 1422, RFFE circuitry 1424, and antenna panels 1426 (collectively, the "transmit / receive components") may be specific to the details of a particular implementation, such as whether the communication is TDM or FDM, at mmWave or sub-6 GHz frequencies, etc. In some embodiments, the transmitting / receiving components may be arranged in multiple parallel transmitting / receiving chains, and may be arranged in the same or different chips / modules, etc.

[0204] In some embodiments, the protocol processing circuitry 1414 may include one or more instances of control circuitry (not shown) to provide control functions for the transmitting / receiving components.

[0205] UE reception can be established via and through antenna panel 1426, RFFE circuit 1424, RF circuit 1422, receiving circuit 1420, digital baseband circuit 1416, and protocol processing circuit 1414. In some embodiments, antenna panel 1426 can receive transmissions from AN 1404 by receiving beamforming signals received by a plurality of antennas / antenna elements of one or more antenna panels 1426.

[0206] UE transmission can be established via and through protocol processing circuitry 1414, digital baseband circuitry 1416, transmission circuitry 1418, RF circuitry 1422, RFFE circuitry 1424, and antenna panel 1426. In some embodiments, the transmission components of UE 1404 can apply a spatial filter to the data to be transmitted to form a transmission beam emitted by the antenna elements of antenna panel 1426.

[0207] Similar to UE 1402, AN 1404 may include a host platform 1428 coupled to a modem platform 1430. Host platform 1428 may include application processing circuitry 1432 coupled to protocol processing circuitry 1434 of modem platform 1430. The modem platform may also include digital baseband circuitry 1436, transmitting circuitry 1438, receiving circuitry 1440, RF circuitry 1442, RFFE circuitry 1444, and antenna panel 1446. Components of AN 1404 may be similar to their namesake components in UE 1402 and are substantially interchangeable with those in UE 1402. In addition to performing data transmission / reception as described above, components of AN 1408 may also perform various logical functions, including, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

[0208] Figure 15 This is a block diagram illustrating components, according to some example embodiments, capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more methods discussed herein. Specifically, Figure 15 A schematic representation of hardware resource 1500 is shown, which includes one or more processors (or processor cores) 1510, one or more memory / storage devices 1520, and one or more communication resources 1530, each of which can be communicatively coupled via bus 1540. Hardware resource 1500 may be part of a UE, AN, or LMF. For embodiments utilizing node virtualization (e.g., NFV), a hypervisor 1502 may be executed to provide an execution environment for one or more network slices / subslices to utilize hardware resource 1500.

[0209] Processor 1510 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) such as a baseband processor, an application-specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 1512 and processor 1514.

[0210] The memory / storage device 1520 may include main memory, disk storage devices, or any suitable combination thereof. The memory / storage device 1520 may include, but is not limited to, any type of volatile or non-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage devices, etc.

[0211] Communication resource 1530 may include interconnect or network interface components or other suitable devices for communicating with one or more peripheral devices 1504 or one or more databases 1506 via network 1508. For example, communication resource 1530 may include wired communication components (e.g., for coupling via Universal Serial Bus (USB)), cellular communication components, NFC components, Bluetooth, etc. Components (e.g., Bluetooth Low Energy), Wi-Fi components, and other communication components.

[0212] Instructions 1550 may include software, programs, applications, applets, or other executable code for causing at least any processor 1510 to perform any one or more of the methods discussed herein. Instructions 1550 may reside wholly or partially in at least one of the following: processor 1510 (e.g., within the processor's buffer memory), memory / storage device 1520, or any suitable combination thereof. Furthermore, any portion of instructions 1550 may be transferred to hardware resource 1500 from any combination of peripheral device 1504 or database 1506. Therefore, the memory of processor 1510, memory / storage device 1520, peripheral device 1504, and database 1506 are examples of computer-readable and machine-readable media.

[0213] The following paragraphs describe examples of various embodiments.

[0214] Example 1 includes an apparatus for a user equipment (UE), comprising: a radio frequency (RF) interface; and processing circuitry coupled to the RF interface, the processing circuitry being configured to: decode downlink control information (DCI) received via the RF interface on a physical downlink channel (PDCCH) of a scheduling cell, wherein the DCI is configured to schedule a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) of more than one cell; and perform communication on the PDSCH or PUSCH of the more than one cell according to the indication of the DCI.

[0215] Example 2 includes the apparatus of Example 1, wherein the scheduled cell is one of the following: a cell with a lower serving cell index among the more than one cells scheduled by the DCI; a cell specified by higher-layer signaling; and any one of the more than one cells scheduled by the DCI; and wherein the more than one cell scheduled by the DCI is configured by higher-layer signaling or indicated by a carrier indicator field (CIF) in the DCI.

[0216] Example 3 includes the apparatus of Example 1, wherein when only two cells, including the scheduled cell, are considered and the DCI is configured to schedule the two cells, the DCI is configured to exclude the Carrier Indicator Field (CIF).

[0217] Example 4 includes the apparatus of Example 1, wherein the DCI includes a carrier indicator field (CIF), and the scheduled cell is one of the more than one cells scheduled by the DCI or a cell different from the more than one cell scheduled by the DCI.

[0218] Example 5 includes the apparatus of Example 4, wherein the single-value space of the CIF is shared between the case where the DCI is configured to schedule a single cell and the case where the DCI is configured to schedule more than one cell.

[0219] Example 6 includes the apparatus of Example 5, wherein the CIF includes a bit to indicate whether the DCI is configured to schedule more than one cell.

[0220] Example 7 includes the apparatus of Example 4, wherein when the more than one cell scheduled by a DCI configured to schedule more than one cell includes only the scheduling cell and another scheduled cell, an existing CIF configuration for a DCI configured to schedule a single cell is reused in the DCI configured to schedule more than one cell to indicate the scheduled cell.

[0221] Example 8 includes the apparatus of Example 4, wherein an existing CIF configuration for a DCI configured for scheduling a single cell is used in a DCI configured for scheduling more than one cell to indicate the more than one cell in the form of a pair or group, wherein the pair or group is configured by higher-layer signaling.

[0222] Example 9 includes the apparatus of Example 1, wherein, for a serving cell, a CrossCarrierSchedulingConfig information element (IE) is used to indicate that the DCI is configured to schedule more than one cell, the cif-presence in the CrossCarrierSchedulingConfig IE is set to true, and the cif-InSchedulingCell in the CrossCarrierSchedulingConfig IE is expanded to indicate one or more carrier indicator field (CIF) values.

[0223] Example 10 includes the apparatus of Example 1, wherein, for each of the more than one cells scheduled by the DCI, a schedulingCellId information element (IE) in higher-layer signaling is used to indicate the serving cell index of the scheduled cell, and a cif-InSchedulingCell IE in higher-layer signaling is used to indicate one or more carrier indicator field (CIF) values ​​to indicate that the DCI configured for scheduling more than one cell applies to that cell.

[0224] Example 11 includes the apparatus of Example 10, wherein the processing circuitry is configured to: if a CIF value is configured for a single serving cell, identify the single serving cell as being scheduled by a DCI with the CIF value for scheduling a single cell; or if a CIF value is configured for more than one serving cell, identify the more than one serving cell as being scheduled by a DCI with the CIF value for scheduling more than one cell.

[0225] Example 12 includes the apparatus of Example 1, wherein the processing circuitry is configured to determine the field size of one or more fields in the DCI based on a reference configuration associated with the more than one cell, each of the reference configurations being determined by the active bandwidth portion (BWP) of the corresponding cell.

[0226] Example 13 includes the apparatus of Example 1, wherein the processing circuitry is configured to determine the field size of one or more fields in the DCI based on a general reference configuration of the more than one cell, the general reference configuration being determined by the active bandwidth portion (BWP) of a reference cell, wherein the reference cell is one of: the scheduled cell; a cell instructed by higher-layer signaling; and a fixed cell among the more than one cells scheduled by the DCI.

[0227] Example 14 includes the apparatus of Example 1, wherein the processing circuitry is configured to: determine whether the size of a field in the DCI is different from the size of the same field according to the active bandwidth portion (BWP) of the corresponding cell in the more than one cell; and if the size of the field in the DCI is different from the size of the same field according to the active BWP of the corresponding cell in the more than one cell, perform size alignment for the field in the DCI with the same field according to the active BWP of the corresponding cell in the more than one cell.

[0228] Example 15 includes the apparatus of Example 14, wherein the processing circuitry is configured to: when specific control information is indicated by a single field in the DCI that is generally applicable to the more than one cell, perform size alignment for that single field in the DCI and the same field of the active BWP according to each of the more than one cell.

[0229] Example 16 includes the apparatus of Example 14, wherein the processing circuitry is configured to: perform size alignment individually or jointly for the individual fields in the DCI when specific control information is indicated by individual fields in the DCI for each of the more than one cell.

[0230] Example 17 includes the apparatus of Example 1, wherein the DCI configured to schedule more than one cell has a different size than the DCI configured to schedule a single cell.

[0231] Example 18 includes the apparatus of Example 1, wherein, for each of the scheduled cell and the more than one scheduled cell, the total number of DCI sizes, including the DCI size for scheduling the PDSCH of the more than one cell and the DCI size for scheduling the PUSCH of the more than one cell, shall not exceed the maximum number of DCI sizes defined for the cell.

[0232] Example 19 includes the apparatus of Example 18, wherein the processing circuitry is configured to: if the total number of DCI sizes exceeds the defined maximum number of DCI sizes, align the DCI sizes for scheduling PDSCHs of more than one cell and the DCI sizes for scheduling PUSCHs of more than one cell with each other; if the total number of DCI sizes still exceeds the defined maximum number of DCI sizes, align the DCI sizes for scheduling a single PDSCH and the DCI sizes for scheduling a single PUSCH with each other; or if the total number of DCI sizes still exceeds the defined maximum number of DCI sizes, align the DCI sizes for scheduling PDSCHs of more than one cell and the DCI sizes for scheduling PUSCHs of more than one cell to cell-wide or group-wide DCI sizes predefined or configured by higher-layer signaling.

[0233] Example 20 includes the apparatus of Example 1, wherein, for each of the scheduled cell and the more than one scheduled cell, the number of PDCCH candidate / non-overlapping CCEs, including PDCCH candidate / non-overlapping control channel elements (CCEs) in the search space of the DCI for scheduling the more than one cell, does not exceed the defined maximum number of PDCCH candidate / non-overlapping CCEs; and the total number of PDCCH candidate / non-overlapping CCEs for the more than one scheduled cell does not exceed the defined maximum number of PDCCH candidate / non-overlapping CCEs for all of the more than one cell.

[0234] Example 21 includes the apparatus of Example 20, wherein, if the scheduling cell is a primary cell (PCell), the number of PDCCH candidate / non-overlapping CCEs of the scheduling cell, including PDCCH candidate / non-overlapping control channel elements (CCEs) in the search space of DCIs used to schedule PDSCH or PUSCH of more than one cell, is allowed to exceed the defined maximum number of PDCCH candidate / non-overlapping CCEs.

[0235] Example 22 includes the apparatus of Example 1, wherein the processing circuitry is configured to: for each scheduled cell, receive up to 16 PDCCHs for all considered DCI formats for scheduling 16 PDSCHs, and receive up to 16 PDCCHs for all considered DCI formats for scheduling 16 PUSCHs, wherein when checking up to 16 PDCCHs, the DCIs for scheduling more than one cell are counted once for each of the more than one cell.

[0236] Example 23 includes a computer-readable storage medium storing instructions that, when executed by a user equipment (UE), cause the UE to: receive downlink control information (DCI) on a physical downlink channel (PDCCH) of a scheduling cell, wherein the DCI is configured to schedule a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) of more than one cell; and perform communication on the PDSCH or PUSCH of the more than one cell according to the instructions of the DCI.

[0237] Example 24 includes the computer-readable storage medium of Example 23, wherein the scheduled cell is one of: a cell with a lower serving cell index among the more than one cells scheduled by the DCI; a cell specified by higher-layer signaling; and any one of the more than one cells scheduled by the DCI; and wherein the more than one cell scheduled by the DCI is configured by higher-layer signaling or indicated by a carrier indicator field (CIF) in the DCI.

[0238] Example 25 includes the computer-readable storage medium of Example 23, wherein, when only two cells, including the scheduled cell, are considered and the DCI is configured to schedule the two cells, the DCI is configured to exclude the Carrier Indicator Field (CIF).

[0239] Example 26 includes the computer-readable storage medium of Example 23, wherein the DCI includes a carrier indicator field (CIF), and the scheduled cell is one of the more than one cells scheduled by the DCI or a cell different from the more than one cell scheduled by the DCI.

[0240] Example 27 includes the computer-readable storage medium of Example 26, wherein the single-value space of the CIF is shared between the case where the DCI is configured to schedule a single cell and the case where the DCI is configured to schedule more than one cell.

[0241] Example 28 includes the computer-readable storage medium of Example 27, wherein the CIF includes one bit to indicate whether the DCI is configured to schedule more than one cell.

[0242] Example 29 includes the computer-readable storage medium of Example 26, wherein when the more than one cell scheduled by a DCI configured to schedule more than one cell includes only the scheduling cell and another scheduled cell, an existing CIF configuration for a DCI configured to schedule a single cell is reused in the DCI configured to schedule more than one cell to indicate the scheduled cell.

[0243] Example 30 includes the computer-readable storage medium of Example 26, wherein an existing CIF configuration for a DCI configured for scheduling a single cell is used in a DCI configured for scheduling more than one cell to indicate the more than one cell in the form of a pair or group, wherein the pair or group is configured by higher-layer signaling.

[0244] Example 31 includes the computer-readable storage medium of Example 23, wherein, for a serving cell, a CrossCarrierSchedulingConfig information element (IE) is used to indicate that the DCI is configured to schedule more than one cell, the cif-presence in the CrossCarrierSchedulingConfig IE of the scheduled cell is set to true, and the cif-InSchedulingCell in the CrossCarrierSchedulingConfig IE is expanded to indicate one or more carrier indicator field (CIF) values.

[0245] Example 32 includes the computer-readable storage medium of Example 23, wherein, for each of the more than one cells scheduled by the DCI, a schedulingCellId information element (IE) in higher-layer signaling is used to indicate the serving cell index of the scheduled cell, and a cif-InSchedulingCell IE in higher-layer signaling is used to indicate one or more carrier indicator field (CIF) values ​​to indicate that the DCI configured for scheduling more than one cell is applicable to that cell.

[0246] Example 33 includes the computer-readable storage medium of Example 32, wherein the instructions further cause the UE to: if a CIF value is configured for a single serving cell, identify the single serving cell as scheduled by a DCI for scheduling a single cell with the CIF value; or if a CIF value is configured for more than one serving cell, identify the more than one serving cell as scheduled by a DCI for scheduling more than one cell with the CIF value.

[0247] Example 34 includes the computer-readable storage medium of Example 23, wherein the instructions further cause the UE to determine the field size of one or more fields in the DCI based on a reference configuration associated with the more than one cell, each of the reference configurations being determined by the active bandwidth portion (BWP) of the corresponding cell.

[0248] Example 35 includes the computer-readable storage medium of Example 23, wherein the instructions further cause the UE to determine the field size of one or more fields in the DCI based on a common reference configuration of the more than one cell, the common reference configuration being determined by the active bandwidth portion (BWP) of a reference cell, wherein the reference cell is one of: the scheduled cell; a cell instructed by higher-layer signaling; and a fixed cell among the more than one cells scheduled by the DCI.

[0249] Example 36 includes the computer-readable storage medium of Example 23, wherein the instructions further cause the UE to: determine whether the size of a field in the DCI is different from the size of the same field according to the active bandwidth portion (BWP) of the corresponding cell in the more than one cell; and if the size of the field in the DCI is different from the size of the same field according to the active BWP of the corresponding cell in the more than one cell, perform size alignment for the field in the DCI with the same field according to the active BWP of the corresponding cell in the more than one cell.

[0250] Example 37 includes the computer-readable storage medium of Example 36, wherein the instructions further cause the UE to: when specific control information is indicated by a single field in the DCI that is generally applicable to the more than one cell, perform size alignment for that single field in the DCI and the same field of the active BWP according to each of the more than one cell.

[0251] Example 38 includes the computer-readable storage medium of Example 36, wherein the instructions further cause the UE to: individually or jointly perform size alignment for the individual fields in the DCI when specific control information is indicated by individual fields in the DCI for each of the more than one cell.

[0252] Example 39 includes the computer-readable storage medium of Example 23, wherein the DCI configured to schedule more than one cell has a different size than the DCI configured to schedule a single cell.

[0253] Example 40 includes the computer-readable storage medium of Example 23, wherein, for each of the scheduled cell and the more than one scheduled cell, the total number of DCI sizes, including the DCI sizes for scheduling the more than one cell's PDSCH and PUSCH, shall not exceed the maximum number of DCI sizes defined for the cell.

[0254] Example 41 includes the computer-readable storage medium of Example 40, wherein the instructions further cause the UE to: align the DCI sizes for scheduling PDSCHs of more than one cell and the DCI sizes for scheduling PUSCHs of more than one cell to each other if the total number of DCI sizes exceeds the defined maximum number of DCI sizes; align the DCI sizes for scheduling a single PDSCH and the DCI sizes for scheduling a single PUSCH to each other if the total number of DCI sizes still exceeds the defined maximum number of DCI sizes; or align the DCI sizes for scheduling PDSCHs of more than one cell and the DCI sizes for scheduling PUSCHs of more than one cell to cell-wide or group-wide DCI sizes predefined or configured by higher-layer signaling if the total number of DCI sizes still exceeds the defined maximum number of DCI sizes.

[0255] Example 42 includes the computer-readable storage medium of Example 23, wherein, for each of the scheduled cell and the more than one scheduled cell, the number of PDCCH candidate / non-overlapping CCEs, including PDCCH candidate / non-overlapping control channel elements (CCEs) in the search space of the DCI for scheduling the PDSCH or PUSCH of the more than one cell, does not exceed the defined maximum number of PDCCH candidate / non-overlapping CCEs; and the total number of PDCCH candidate / non-overlapping CCEs of the more than one scheduled cell does not exceed the defined maximum number of PDCCH candidate / non-overlapping CCEs for all of the more than one cell.

[0256] Example 43 includes a computer-readable storage medium of Example 42, wherein, if the scheduling cell is a primary cell (PCell), the number of PDCCH candidate / non-overlapping CCEs of the scheduling cell, including PDCCH candidate / non-overlapping control channel elements (CCEs) in the search space of DCIs used to schedule PDSCH or PUSCH of more than one cell, is allowed to exceed the defined maximum number of PDCCH candidate / non-overlapping CCEs.

[0257] Example 44 includes the computer-readable storage medium of Example 23, wherein the instructions further cause the UE to: for each scheduled cell, anticipate receiving up to 16 PDCCHs for all considered DCI formats for scheduling 16 PDSCHs, and receiving up to 16 PDCCHs for all considered DCI formats for scheduling 16 PUSCHs, wherein when checking up to 16 PDCCHs, the DCIs for scheduling more than one cell are counted once for each of the more than one cell.

[0258] Example 45 includes a method performed by a user equipment (UE), comprising: receiving downlink control information (DCI) on a physical downlink channel (PDCCH) of a scheduling cell, wherein the DCI is configured to schedule a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) of more than one cell; and performing communication on the PDSCH or PUSCH of the more than one cell according to the indication of the DCI.

[0259] Example 46 includes the method of Example 45, wherein the scheduled cell is one of: a cell with a lower serving cell index among the more than one cells scheduled by the DCI; a cell specified by higher-layer signaling; and any cell among the more than one cells scheduled by the DCI; and wherein the more than one cell scheduled by the DCI is configured by higher-layer signaling or indicated by a carrier indicator field (CIF) in the DCI.

[0260] Example 47 includes the method of Example 45, wherein when only two cells, including the scheduled cell, are considered and the DCI is configured to schedule the two cells, the DCI is configured to exclude the Carrier Indicator Field (CIF).

[0261] Example 48 includes the method of Example 45, wherein the DCI includes a carrier indicator field (CIF), and the scheduled cell is one of the more than one cells scheduled by the DCI or a cell different from the more than one cell scheduled by the DCI.

[0262] Example 49 includes the method of Example 48, wherein the single-value space of the CIF is shared between the case where the DCI is configured to schedule a single cell and the case where the DCI is configured to schedule more than one cell.

[0263] Example 50 includes the method of Example 49, wherein the CIF includes a bit to indicate whether the DCI is configured to schedule more than one cell.

[0264] Example 51 includes the method of Example 48, wherein when the more than one cell scheduled by a DCI configured for scheduling more than one cell includes only the scheduling cell and another scheduled cell, an existing CIF configuration for a DCI configured for scheduling a single cell is reused in the DCI configured for scheduling more than one cell to indicate the scheduled cell.

[0265] Example 52 includes the method of Example 48, wherein an existing CIF configuration for a DCI configured for scheduling a single cell is used in a DCI configured for scheduling more than one cell to indicate the more than one cell in the form of a pair or group, wherein the pair or group is configured by higher-layer signaling.

[0266] Example 53 includes the method of Example 45, wherein, for a serving cell, a CrossCarrierSchedulingConfig information element (IE) is used to indicate that the DCI is configured to schedule more than one cell, the cif-presence in the CrossCarrierSchedulingConfig IE of the scheduled cell is set to true, and the cif-InSchedulingCell in the CrossCarrierSchedulingConfig IE is expanded to indicate one or more carrier indicator field (CIF) values.

[0267] Example 54 includes the method of Example 45, wherein, for each of the more than one cells scheduled by the DCI, a schedulingCellId information element (IE) in higher-layer signaling is used to indicate the serving cell index of the scheduled cell, and a cif-InSchedulingCell IE in higher-layer signaling is used to indicate one or more carrier indicator field (CIF) values ​​to indicate that the DCI configured for scheduling more than one cell is applicable to that cell.

[0268] Example 55 includes the method of Example 54, and further includes: if a CIF value is configured for a single serving cell, then identifying the single serving cell as scheduled by a DCI for scheduling a single cell with the CIF value; or if a CIF value is configured for more than one serving cell, then identifying the more than one serving cell as scheduled by a DCI for scheduling more than one cell with the CIF value.

[0269] Example 56 includes the method of Example 55, and further includes: determining the field size of one or more fields in the DCI based on a reference configuration associated with the more than one cell, each of the reference configurations being determined by the active bandwidth portion (BWP) of the corresponding cell.

[0270] Example 57 includes the method of Example 55, further comprising: determining the field size of one or more fields in the DCI based on a general reference configuration of the more than one cell, the general reference configuration being determined by the active bandwidth portion (BWP) of a reference cell, wherein the reference cell is one of: the scheduled cell; a cell instructed by higher-layer signaling; and a fixed cell among the more than one cells scheduled by the DCI.

[0271] Example 58 includes the method of Example 55, further comprising: determining whether the size of a field in the DCI is different from the size of the same field in the active bandwidth portion (BWP) of the corresponding cell in the more than one cell; and if the size of the field in the DCI is different from the size of the same field in the active BWP of the corresponding cell in the more than one cell, performing size alignment for the field in the DCI with the same field in the active BWP of the corresponding cell in the more than one cell.

[0272] Example 59 includes the method of Example 58, further comprising: when specific control information is indicated by a single field in the DCI that is generally applicable to the more than one cell, performing size alignment for the single field in the DCI and the same field of the active BWP according to each of the more than one cell.

[0273] Example 60 includes the method of Example 58, further comprising: performing size alignment, individually or jointly, for the individual fields in the DCI when specific control information is indicated by individual fields in the DCI for each of the more than one cell.

[0274] Example 61 includes the method of Example 45, wherein the DCI configured to schedule more than one cell has a different DCI size than the DCI configured to schedule a single cell.

[0275] Example 62 includes the method of Example 45, wherein, for each of the scheduled cell and the more than one scheduled cell, the total number of DCI sizes, including the DCI sizes for scheduling the more than one cell's PDSCH and PUSCH, should not exceed the maximum number of DCI sizes defined for the cell.

[0276] Example 63 includes the method of Example 62, further comprising: if the total number of DCI sizes exceeds the defined maximum number of DCI sizes, then aligning the DCI sizes for scheduling PDSCHs of more than one cell and the DCI sizes for scheduling PUSCHs of more than one cell with each other; if the total number of DCI sizes still exceeds the defined maximum number of DCI sizes, then aligning the DCI sizes for scheduling a single PDSCH and the DCI sizes for scheduling a single PUSCH with each other; or if the total number of DCI sizes still exceeds the defined maximum number of DCI sizes, then aligning the DCI sizes for scheduling PDSCHs of more than one cell and the DCI sizes for scheduling PUSCHs of more than one cell to cell-wide or group-wide DCI sizes predefined or configured by higher-layer signaling.

[0277] Example 64 includes the method of Example 45, wherein, for each of the scheduled cell and the more than one scheduled cell, the number of PDCCH candidate / non-overlapping CCEs, including PDCCH candidate / non-overlapping control channel elements (CCEs) in the search space of the DCI for scheduling the PDSCH or PUSCH of the more than one cell, does not exceed the defined maximum number of PDCCH candidate / non-overlapping CCEs; and the total number of PDCCH candidate / non-overlapping CCEs of the more than one scheduled cell does not exceed the defined maximum number of PDCCH candidate / non-overlapping CCEs for all of the more than one cell.

[0278] Example 65 includes the method of Example 64, wherein, if the scheduling cell is a primary cell (PCell), the number of PDCCH candidate / non-overlapping CCEs of the scheduling cell, including PDCCH candidate / non-overlapping control channel elements (CCEs) in the search space of DCIs used to schedule PDSCH or PUSCH of more than one cell, is allowed to exceed the defined maximum number of PDCCH candidate / non-overlapping CCEs.

[0279] Example 66 includes the method of Example 45, further comprising: for each scheduled cell, expecting to receive up to 16 PDCCHs for all considered DCI formats for scheduling 16 PDSCHs, and to receive up to 16 PDCCHs for all considered DCI formats for scheduling 16 PUSCHs, wherein when checking up to 16 PDCCHs, the DCIs for scheduling more than one cell are counted once for each of the more than one cell.

[0280] Example 67 includes an apparatus for a user equipment (UE) including a module for performing the method of any one of Examples 45 to 66.

[0281] Example 68 includes a communication system comprising the means of any one of Examples 1 to 22, and a corresponding access node (AN).

[0282] While certain embodiments have been illustrated and described herein for purposes of description, various alternative and / or equivalent embodiments or implementations devised to achieve the same purpose may replace the illustrated and described embodiments without departing from the scope of this disclosure. This application is intended to cover any adaptations or variations of the embodiments discussed herein. Therefore, it is readily understood that the embodiments described herein are limited only by the appended claims and their equivalents.

Claims

1. An apparatus for a user equipment (UE), comprising: RF interface; as well as A processing circuit coupled to the RF interface, the processing circuit being used for: Decode the downlink control information (DCI) received via the RF interface on the physical downlink channel (PDCCH) of the scheduling cell, wherein the DCI is configured to schedule the physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH) of more than one cell. According to the instructions of the DCI, communication is performed on the PDSCH or PUSCH of the more than one cell; and The field size of one or more fields in the DCI is determined based on a reference configuration associated with the more than one cell or a common reference configuration of the more than one cell. Each of the reference configurations is determined by the active bandwidth portion (BWP) of the corresponding cell, and the general reference configuration is determined by the BWP of the reference cell, wherein the reference cell is one of the following: The scheduling cell; Cells commanded by higher-level signaling; and Fixed cells among the more than one cells scheduled by the DCI.

2. The apparatus of claim 1, wherein, The scheduling cell is one of the following: The cell with a lower serving cell index among the more than one cells scheduled by the DCI; The community designated by high-level signaling; and Any one of the more than one cells scheduled by the DCI; and The multiple cells scheduled by the DCI are configured by higher-layer signaling or indicated by the Carrier Indicator Field (CIF) in the DCI.

3. The apparatus of claim 1, wherein, When only two cells, including the scheduled cell, are considered and the DCI is configured to schedule these two cells, the DCI is configured to exclude the Carrier Indicator Field (CIF).

4. The apparatus of claim 1, wherein, The DCI includes a carrier indicator field (CIF), and the scheduled cell is one of the more than one cells scheduled by the DCI or a cell different from the more than one cell scheduled by the DCI.

5. The apparatus of claim 4, wherein, The single-value space of the CIF is shared between the case where the DCI is configured to schedule a single cell and the case where the DCI is configured to schedule more than one cell.

6. The apparatus of claim 5, wherein, The CIF includes one bit to indicate whether the DCI is configured to schedule more than one cell.

7. The apparatus of claim 4, wherein, When the more than one cell scheduled by a DCI configured to schedule more than one cell includes only the scheduling cell and another scheduled cell, the existing CIF configuration for a DCI configured to schedule a single cell is reused in a DCI configured to schedule more than one cell to indicate the scheduled cell.

8. The apparatus of claim 4, wherein, The existing CIF configuration used for a DCI configured to schedule a single cell is used in a DCI configured to schedule more than one cell to indicate the more than one cell in the form of pairs or groups, wherein the pairs or groups are configured by higher-layer signaling.

9. The apparatus of claim 1, wherein, For the serving cell, the CrossCarrierSchedulingConfig information element IE is used to indicate that the DCI is configured to schedule more than one cell, the cif-presence in the CrossCarrierSchedulingConfig IE of the scheduled cell is set to true, and the cif-InSchedulingCell in the CrossCarrierSchedulingConfig IE is expanded to indicate one or more Carrier Indicator Field CIF values.

10. The apparatus of claim 1, wherein, For each of the more than one cells scheduled by the DCI, the schedulingCellId information element (IE) in the higher-layer signaling is used to indicate the serving cell index of the scheduled cell, and the cif-InSchedulingCell IE in the higher-layer signaling is used to indicate one or more carrier indicator field (CIF) values ​​to indicate that the DCI configured for scheduling more than one cell is applicable to that cell.

11. The apparatus of claim 10, wherein, The processing circuit is configured to: If a CIF value is configured for a single serving cell, that single serving cell is identified as being scheduled by a DCI that has that CIF value for scheduling a single cell. or If a CIF value is configured for more than one serving cell, then that more than one serving cell is identified as being scheduled by DCI with that CIF value for scheduling more than one cell.

12. The apparatus of claim 1, wherein, The processing circuit is used for: Determine whether the size of a field in the DCI differs from the size of the same field based on the active bandwidth portion (BWP) of the corresponding cell in the more than one cell; and If the size of the field in the DCI is different from the size of the same field in the active BWP of the corresponding cell in the more than one cell, then the field in the DCI is size aligned with the same field in the active BWP of the corresponding cell in the more than one cell.

13. The apparatus of claim 12, wherein, The processing circuit is used for: When specific control information is indicated by a single field in the DCI that is generally applicable to the more than one cell, size alignment is performed for that single field in the DCI and the same field based on the active BWP of each of the more than one cell.

14. The apparatus of claim 12, wherein, The processing circuit is used for: When specific control information is indicated by individual fields in the DCI for each of the more than one cell, size alignment is performed individually or jointly for the individual fields in the DCI.

15. The apparatus of claim 1, wherein, The DCI configured to schedule more than one cell has a different DCI size than the DCI configured to schedule a single cell.

16. The apparatus of claim 1, wherein, For each of the scheduled cell and the more than one scheduled cell, the total number of DCI sizes, including the DCI sizes for scheduling the PDSCH of more than one cell and the DCI sizes for scheduling the PUSCH of more than one cell, should not exceed the maximum number of DCI sizes defined for the cell.

17. The apparatus of claim 16, wherein, The processing circuit is used for: If the total number of DCI sizes exceeds the maximum number of defined DCI sizes, then the DCI sizes used for scheduling PDSCH of more than one cell and the DCI sizes used for scheduling PUSCH of more than one cell will be aligned with each other. If the total number of DCI sizes still exceeds the defined maximum number of DCI sizes, then the DCI sizes used for scheduling a single PDSCH and the DCI sizes used for scheduling a single PUSCH will be aligned with each other; or If the total number of DCI sizes still exceeds the maximum number of defined DCI sizes, then the DCI sizes used for scheduling PDSCH of more than one cell and the DCI sizes used for scheduling PUSCH of more than one cell will be aligned to cell-wide or group-wide DCI sizes predefined or configured by higher-layer signaling.

18. The apparatus of claim 1, wherein, For each of the scheduled cell and the more than one scheduled cell, the number of PDCCH candidate / non-overlapping CCEs, including the PDCCH candidate / non-overlapping control channel element CCE in the search space of the DCI used for scheduling the PDSCH or PUSCH of more than one cell, does not exceed the defined maximum number of PDCCH candidate / non-overlapping CCEs; and The total number of PDCCH candidate / non-overlapping CCEs scheduled for the more than one cell does not exceed the maximum number of PDCCH candidate / non-overlapping CCEs defined for all the more than one cell.

19. The apparatus of claim 18, wherein, If the scheduling cell is a primary cell PCell, the number of PDCCH candidate / non-overlapping CCEs of the scheduling cell, including the PDCCH candidate / non-overlapping control channel element CCE in the search space of the DCI used to schedule more than one cell's PDSCH or PUSCH, is allowed to exceed the defined maximum number of PDCCH candidate / non-overlapping CCEs.

20. The apparatus of claim 1, wherein, The processing circuit is used for: For each scheduled cell, it is expected that a maximum of 16 PDCCHs will be received for all considered DCI formats for scheduling 16 PDSCHs, and a maximum of 16 PDCCHs will be received for all considered DCI formats for scheduling 16 PUSCHs, wherein when checking a maximum of 16 PDCCHs, the DCIs for scheduling more than one cell are counted once for each of the more than one cell.

21. A computer-readable storage medium storing instructions thereon, the instructions causing the user equipment (UE) to: Downlink control information (DCI) is received on the physical downlink channel (PDCCH) of the scheduling cell, where, The DCI is configured to schedule the Physical Downlink Shared Channel (PDSCH) or Physical Uplink Shared Channel (PUSCH) for more than one cell. Communication is performed on the PDSCH or PUSCH of more than one cell, according to the instructions of the DCI. as well as The field size of one or more fields in the DCI is determined based on a reference configuration associated with the more than one cell or a common reference configuration of the more than one cell. Each of the reference configurations is determined by the active bandwidth portion (BWP) of the corresponding cell, and the general reference configuration is determined by the BWP of the reference cell, wherein the reference cell is one of the following: The scheduling cell; Cells commanded by higher-level signaling; and Fixed cells among the more than one cells scheduled by the DCI.

22. The computer-readable storage medium of claim 21, wherein, The scheduling cell is one of the following: The cell with a lower serving cell index among the more than one cells scheduled by the DCI; The community designated by high-level signaling; and Any one of the more than one cells scheduled by the DCI; and The multiple cells scheduled by the DCI are configured by higher-layer signaling or indicated by the Carrier Indicator Field (CIF) in the DCI.

Images