DCI design for supporting single DCI scheduling multiple cells
By designing a single DCI for multiple cells, using the new DCI format and field configuration, the problem that a single DCI can only schedule one cell is solved, and PUSCH scheduling flexibility and PDCCH overhead are achieved between multiple cells.
Patent Information
- Application Number
- CN202280095423.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-04-29
- Publication Date
- 2024-12-06
AI Technical Summary
In the current new radio (NR), a single DCI can only be used to schedule PUSCH on one cell, resulting in limited scheduling flexibility between multiple cells and high PDCCH overhead.
By designing a single DCI that can schedule PUSCHs on multiple cells at the same time, the new DCI format, uplink indicator, frequency domain resource allocation, time domain resource allocation, detection reference signal resource indicator, channel status information request etc fields to configure DCI, reduce DCI size and maintain scheduling flexibility.
The PUSCH scheduling flexibility and the PDCCH overhead are achieved across multiple cells, and the efficiency and flexibility of the system are improved.
Smart Images

Figure CN119096502A_ABST
Abstract
Description
Technical Field
[0001] Embodiments of the present disclosure relate generally to the field of telecommunications, and in particular to a single downlink control information (DCI) design for supporting scheduling of a physical uplink shared channel (PUSCH) on multiple cells. Background Art
[0002] In current New Radio (NR) including 3GPP Rel-15 / 16 / 17, a single DCI can be used to schedule PUSCH on only one cell. Summary of the invention
[0003] Generally speaking, exemplary embodiments of the present disclosure provide a solution for supporting a single DCI that schedules PUSCH on multiple cells.
[0004] In a first aspect, a processor of a base station (BS) is provided. The processor is configured to perform operations including configuring a single DCI to schedule PUSCHs on multiple cells simultaneously; and sending the single DCI to a user equipment (UE) through a physical downlink control channel (PDCCH).
[0005] In a second aspect, a base station is provided. The base station includes a transceiver and a processor. The transceiver is configured to communicate with a user equipment. The processor is communicatively coupled to the transceiver and configured to perform operations including configuring a single DCI to simultaneously schedule PUSCHs on multiple cells; and sending the single DCI to the user equipment via a PDCCH.
[0006] In a third aspect, a processor of a user equipment is provided. The processor is configured to perform operations including receiving a single DCI from a network through a PDCCH; and transmitting in a PUSCH on multiple cells based on configuration information included in the single DCI.
[0007] In a fourth aspect, a user equipment is provided. The user equipment includes a transceiver and a processor. The transceiver is configured to communicate with a network. The processor is communicatively coupled to the transceiver and configured to perform operations including receiving a single DCI from the network via a PDCCH; and sending in a PUSCH on multiple cells based on configuration information included in the single DCI.
[0008] It should be understood that the invention summary is not intended to indicate the key or essential features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS
[0009] The above and other objects, features and advantages of the present disclosure will become more apparent through a more detailed description of some embodiments of the present disclosure in the accompanying drawings, in which:
[0010] Figure 1 An exemplary communication network is shown in which exemplary embodiments of the present disclosure may be implemented;
[0011] Figure 2 The signaling flow for implementing scheduling of multiple cells using a single DCI according to some embodiments of the present disclosure is illustrated;
[0012] Figure 3 A schematic diagram illustrating an offset of a starting symbol of a scheduled cell when a mapping type and a duration of a PUSCH are the same for the scheduled cells according to some embodiments of the present disclosure;
[0013] Figure 4 A flow chart illustrating an exemplary method performed by a BS to support a single DCI for scheduling PUSCH on multiple cells according to some embodiments of the present disclosure;
[0014] Figure 5 A flowchart illustrating an exemplary method performed by a UE to support a single DCI for scheduling PUSCH on multiple cells according to some embodiments of the present disclosure; and
[0015] Figure 6 A simplified block diagram of a device suitable for implementing embodiments of the present disclosure is illustrated.
[0016] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION
[0017] The principle of the present disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are described only for illustrative purposes, and are helpful for those skilled in the art to understand and implement the present disclosure, without indicating any limitation to the scope of the present disclosure. In addition to the methods described below, the disclosure described herein can be implemented in various ways.
[0018] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.
[0019] The terms used herein are only for describing specific embodiments and are not intended to limit the exemplary embodiments. For example, as used herein, the singular forms "a", "a kind of" and "the" are intended to include the plural forms as well, unless the context otherwise indicates. The terms "include", "have", "include" when used herein specify the presence of stated features, elements and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components and / or combinations thereof. In addition, when describing specific features, structures or characteristics in conjunction with some embodiments, it is considered that it is within the knowledge of those skilled in the art to implement such features, structures or characteristics in conjunction with other embodiments that are explicitly or not explicitly described.
[0020] It should also be understood that, although the terms "first", "second", etc. may be used to describe various elements in this article, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, the first element can be named as the second element and similarly the second element can be named as the first element without departing from the scope of the exemplary embodiment. As used herein, the term "and / or" includes any combination and all combinations of one or more of the listed terms.
[0021] As mentioned above, in current NRs including Rel-15 / 16 / 17, a single DCI can only be used to schedule PUSCH on one cell. The scheduled cell can be indicated by the "carrier indicator" field in the DCI. The mapping of the "carrier indicator" to the actual cell can be configured by the radio resource control (RRC) via CrossCarrierSchedulingConfig, and the configuration can be performed per scheduled cell.
[0022] In the upcoming Rel-18, in the approved work item description (WID) (ie, RP-213577), an agreement was reached on multi-carrier enhancements to support a single DCI that schedules physical downlink shared channels (PDSCH) / PUSCH from multiple cells.
[0023] The driving factor for scheduling multiple cells with a single DCI is to reduce PDCCH overhead, i.e., reduce DCI size. However, except for a few DCI fields such as cyclic redundancy check (CRC), this is a trade-off between scheduling flexibility and DCI size reduction. Multiple uplink DCI fields may be considered, such as the DCI fields of DCI formats 0_1 and 0_2 of TS38.212.
[0024] Embodiments of the present disclosure propose design options for a single DCI for scheduling PUSCH in multiple cells, including designs for at least the following items: a new DCI / DCI format, an uplink (UL) or normal uplink (NUL) / supplemental uplink (SUL) indicator, a frequency domain resource allocation (FDRA), a time domain resource allocation (TDRA), a sounding reference signal (SRS) resource indicator, a channel state information (CSI) request, a UL shared channel (UL-SCH) indicator, and other items such as any one or more fields of DCI formats 0_1, 0_2.
[0025] In the solution, a processor of a base station is configured to configure a single DCI to schedule PUSCH on multiple cells simultaneously, and send the single DCI to a user equipment through a PDCCH. The single DCI can be configured using one or more designs of a DCI field or format. The processor of the user equipment is configured to receive the single DCI from a network (e.g., the base station) through a PDCCH, and send it in a PUSCH on multiple cells based on the configuration information included in the configured single DCI.
[0026] According to an embodiment of the present disclosure, the DCI is designed to support a single DCI that schedules PUSCH in multiple cells. In this way, the DCI size is reduced, and thus the PDCCH overhead is reduced accordingly. At the same time, scheduling flexibility can be maintained through the proposed various DCI designs.
[0027] The following will refer to Figures 1 to 6 The principles and specific implementations of the present disclosure are described in detail. Figure 1 An exemplary communication network 100 is shown in which embodiments of the present disclosure may be implemented. The network 100 includes a base station (BS) 110 and a user equipment (UE) 120 served by the BS 110. The network 100 may provide a plurality of serving cells 131-133 to serve the UE 120.
[0028] It should be understood that the number of BSs 110, UEs 120, and serving cells 131-133 is for illustration purposes only and does not imply any limitation. Network 100 may include any suitable number of BSs, UEs, and serving cells suitable for implementing embodiments of the present disclosure.
[0029] In communication network 100, BS 110 may transmit data and control information to UE 120, and UE 120 may also transmit data and control information to BS 110. The link from BS 110 to UE 120 is called a downlink (DL) or forward link, and the link from UE 120 to BS 110 is called an uplink (UL) or reverse link.
[0030] Further, in the communication network 100, the BS 110 may send a single DCI to the UE 120 via the PDCCH to schedule the PUSCH on multiple cells 131-133. The DCI may be configured by the BS 110 using one or more designs of DCI fields or formats. The UE 120 may receive the single DCI via the PDCCH and transmit in the PUSCH on multiple cells based on the configuration information included in the configured single DCI.
[0031] Reference Figure 2 The process of the present disclosure is described. Figure 2 The signaling flow 200 for implementing scheduling of multiple cells using a single DCI according to some embodiments of the present disclosure is illustrated. For the purpose of discussion, reference will be made to Figure 1 A signaling flow 200 is described. The signaling flow 200 may involve a BS 110, a UE 120, and a plurality of cells 131-133 to be scheduled.
[0032] In signaling flow 200, BS 110 configures 210 a single DCI to schedule PUSCH on multiple cells. The single DCI may be configured using one or more designs of DCI fields or formats.
[0033] In some embodiments, a new DCI may be defined based on a new radio network temporary identifier (RNTI), i.e., BS 110 may configure a new RNTI via RRC. Specifically, BS 110 may define a new RNTI, such as a multi-cell RNTI (MC-RNTI), to scramble the CRC of a single DCI that schedules multiple cells simultaneously.
[0034] In some implementations, a new DCI format for uplink scheduling, namely, DCI format 0_3, may be defined. Each DCI field of the new DCI format 0_3 may be designed to simultaneously indicate scheduling information of multiple scheduled cells.
[0035] In some embodiments, an existing DCI format may be used. For example, DCI format 0_1 or 0_2 may be concatenated to form a new DCI. In this case, when multiple cells 131-133 may be scheduled by a single DCI, the corresponding DCI field size may be independently configured for each scheduled cell. Then, the DCIs from multiple cells may be concatenated to form a final DCI.
[0036] Alternatively or additionally, the UL indicator field in the DCI may be configured for scheduling uplink channels such as but not limited to PUSCH on multiple cells.
[0037] In some embodiments, a single "UL / SUL indicator" field may be included in a single DCI. On each scheduled cell, based on a single "UL / SUL indicator" field, UL (i.e., NUL) or SUL may be used for all scheduled cells 131-133 based on a single "UL / SUL indicator" field.
[0038] In some embodiments, multiple "UL / SUL indicator" fields may be included in a single DCI. In this case, the number of bits of the "UL / SUL indicator" field may be the maximum number of cells that a single DCI can schedule. Alternatively, the number of bits of the "UL / SUL indicator" field may be the maximum number of SULs that a single DCI can schedule. Alternatively, for each "carrier indicator", the number of bits of the "UL / SUL indicator" field may be the number of SULs that a single DCI can schedule.
[0039] For example, assuming that component carrier (CC) 0 (CC0) and CC1 have both NUL and SUL, and CC2 and CC3 have only NUL, if "carrier indicator" = 0 represents CC0 + CC1, "carrier indicator" = 1 represents CC2 + CC3, "carrier indicator" = 2 represents CC0 + CC2, and "carrier indicator" = 3 represents CC0 + CC1 + CC2 + CC3, then: In the case where the number of bits of the "UL / SUL indicator" field is the maximum number of cells that can be scheduled by a single DCI, the "UL / SUL indicator" field can be is 4 bits; in the case where the number of bits of the "UL / SUL indicator" field is the maximum number of SULs that can be scheduled by a single DCI, the "UL / SUL indicator" field can be 2 bits; and in the case where the number of bits of the "UL / SUL indicator" field is the number of SULs that can be scheduled by a single DCI for each "carrier indicator", the "UL / SUL indicator" field can be 2 bits for "carrier indicator" = 0, 0 bits for "carrier indicator" = 1, 1 bit for "carrier indicator" = 2, and 2 bits for "carrier indicator" = 3.
[0040] Alternatively or additionally, a frequency domain resource allocation (FDRA) field in the DCI may be configured for scheduling uplink channels such as but not limited to PUSCH on multiple cells.
[0041] In some embodiments, for all cells 131-133 scheduled simultaneously by BS 110 via a single DCI, all cells 131-133 may be configured with the same resource allocation type, i.e., one of resourceAllocation ENUMERATED{resourceAllocationType0, resourceAllocationType1, dynamicSwitch}, where resourceAllocationType0 represents a bitmap, resourceAllocationType1 represents a range length, which is used to tell UE 120 which physical resource block (PRB) to start from and how many PRBs to send, and dynamicSwitch may trigger a dynamic switch between resourceAllocationType0 and resourceAllocationType1. Alternatively, different resource allocation types may be configured by BS 110 for each cell.
[0042] In some embodiments, a single FDRA field may be included in a single DCI. In this case, the UE 120 may assume that it is scheduled to have the same FDRA for the PUSCH in each cell that is scheduled simultaneously. When the size of the effective bandwidth part (BWP) of different CCs is different, the DCI size may be aligned. For example, if the second CC requires fewer bits in terms of FDRA than the current CC, truncation may be applied, for example, the most significant bit (MSB) of the FDRA field may be discarded. Alternatively or in addition, if the second CC requires more bits in terms of FDRA than the current CC, appending may be applied, for example, appending zeros to the MSB of the FDRA field.
[0043] In some embodiments, multiple FDRA fields may be included in a single DCI.Each FDRA may be used for a PUSCH corresponding to a different scheduled cell 131-133.
[0044] Alternatively or additionally, a time domain resource allocation (TDRA) field in the DCI may be configured for scheduling uplink channels such as but not limited to PUSCH on multiple cells.
[0045] In some embodiments, a single TDRA field may be included in a single DCI. In this case, UE 120 may assume to be scheduled to have the same TDRA for PUSCH in each cell that is scheduled simultaneously.
[0046] In some embodiments, multiple TDRA fields may be included in a single DCI.Each TDRA may be used for a PUSCH corresponding to a different scheduled cell 131-133.
[0047] Reference now Figure 3 . Figure 3 A schematic diagram 300 illustrates an offset of a starting symbol between a first cell 131 and a second cell 132 in a scheduled cell. The symbol may be an Orthogonal Frequency Division Multiplexing (OFDM) symbol.
[0048] In some embodiments, where a single TDRA field is included in a single DCI, BS 110 may configure via RRC how to derive a second TDRA (eg, for second cell 132) from a first TDRA (eg, for first cell 131). Figure 3 In , it is assumed that the following information is the same among all CCs scheduled simultaneously: (1) the mapping type, i.e., mappingType ENUMERATED{typeA,typeB}, and (2) the duration of the PUSCH, i.e., the number of symbols. For example, Figure 3 The duration of the PUSCH for both the first cell 131 and the second cell 132 is shown to be 7 symbols. This is for illustrative purposes and does not imply any limitation. Figure 3 As shown, the offset of the starting symbol between the first cell 131 and the second cell 132 is 6 symbols. Therefore, the second TDRA may have the same mapping type, 7 symbol duration, and 6 symbol offset relative to the starting symbol of the first TDRA as the first TDRA. In this way, the UE 120 may derive the second TDRA of the second cell 132 from the first TDRA of the first cell 131.
[0049] In some embodiments, the network (NW) (eg, BS 110) may configure a TDRA table. In the TDRA table, for each TDRA code point, the NW may configure the TDRA of each scheduled cell. A specific example of the TDRA table is shown in Table 1 below.
[0050] Table 1
[0051]
[0052] For TDRA, it may contain 3 pieces of information. The first piece of information may be the mapping type. The second piece of information may be the duration, which is part of the startSymbolAndLength in the table. The third piece of information may be the offset, which is divided into two parts. One part may be K0 in the table, which represents the slot offset. For example, the BS 110 may tell the UE 120 the number of slots it can wait before transmitting in the PUSCH. The other part of the offset may be the symbol offset within the slot, which is another part of the startSymbolAndLength in the table.
[0053] Therefore, the mapping type of TDRA can be configured by mappingType in the table. The duration of TDRA can be configured by the length portion of startSymbolAndLength in the table. The offset of TDRA can be configured by K0 and the startSymbol portion of startSymbolAndLength in the table. In some embodiments, the TDRA table can be configured by BS 110 through RRC, and BS 110 can inform UE 120 through RRC to schedule PUSCH transmission on multiple cells 131-133.
[0054] It should be noted that the number of scheduled cells and fields in Table 1 is shown for illustrative purposes only and does not imply any limitation. BS110 may configure a larger TDRA table to achieve greater scheduling flexibility. Alternatively, BS110 may configure a smaller TDRA table to reduce scheduling flexibility while also reducing DCI overhead. Such modifications, variations, and alternative configurations will be consistent with the spirit and scope of the embodiments of the present disclosure.
[0055] Alternatively or additionally, a sounding reference signal (SRS) resource indicator field in the DCI may be configured for scheduling uplink channels such as, but not limited to, PUSCH on multiple cells.
[0056] In some embodiments, for all cells 131-133 scheduled by the same UL DCI, all cells may be configured with codebook PUSCH operation, or all cells may be configured with non-codebook PUSCH operation. Alternatively, some of the scheduled cells 131-133 may be configured with codebook PUSCH operation, and other cells may be configured with non-codebook PUSCH operation.
[0057] In some embodiments, multiple SRS resource indicator fields may be included in a single DCI.Each SRS resource indicator may correspond to one scheduled cell.
[0058] In some embodiments, in frequency range 2 (FR2), when multiple SRS resource indicators corresponding to different scheduled cells 131-133 may be indicated, it may be necessary to ensure spatial relationship consistency when sending PUSCH at the same time. For example, different SRS resource indicators in the same DCI corresponding to different scheduled cells 131-133 may have the same spatial filter (simulated beam) for UL transmission of all scheduled cells in at least the same frequency band (i.e., intra-band carrier aggregation (CA)). Alternatively, when UE 120 indicates that it only supports common beam management (CBM) for the corresponding frequency band combination, different SRS resource indicators corresponding to different scheduled cells 131-133 may have the same spatial filter for UL transmission of scheduled cells in different frequency bands (i.e., inter-band CA).
[0059] Alternatively or additionally, a channel state information (CSI) request field in the DCI may be configured for scheduling uplink channels such as, but not limited to, PUSCH on multiple cells.
[0060] In some embodiments, a single CSI request field may be included in a single DCI. In some embodiments, multiple CSI request fields may be included in a single DCI. UE 120 may transmit in PUSCH on multiple cells 131-133 based on the CSI request field in a single DCI, as described below.
[0061] Alternatively or additionally, a UL shared channel (UL-SCH) indicator field in the DCI may be configured for scheduling uplink channels such as, but not limited to, PUSCH on multiple cells.
[0062] In some embodiments, when a single DCI is used to schedule PUSCH transmissions on multiple cells 131-133, a UL-SCH indicator field with 0 bits may be configured. Alternatively, when a single DCI is used to schedule PUSCH transmissions on multiple cells 131-133, a UL-SCH indicator field with more than 0 bits may be configured. For example, the UL-SCH indicator field may be 1 bit, and the same UL-SCH indicator may be applied to all scheduled cells 131-133. Alternatively, the UL-SCH indicator field may be N bits, where 1 of the N bits may be used for each scheduled cell 131-133, and N may be the maximum number of cells that may be scheduled by a single DCI, or N may be the number of cells corresponding to the "carrier indicator" field.
[0063] Generally speaking, there are two ways to trade off scheduling flexibility with DCI size reduction. One method may be to use a single DCI field, assuming that UE 120 applies the same field to all scheduled cells 131-133. Another method may be to use multiple DCI fields, each for each scheduled cell. In some embodiments, these two methods may be configured independently for each of the following fields: frequency hopping flag, modulation and coding scheme, new data indicator, redundancy version, hybrid automatic repeat request (HARQ) process number, transmit power control (TPC) command for PUSCH, pre-coding information and number of layers, antenna port, SRS request, phase tracking reference signal-demodulation reference signal (PTRS-DMRS) association, DMRS sequence initialization, code block group (CBG) transmission information (CBGTI), priority, invalid symbol mode indicator, primary cell (SCell) sleep indication, etc.
[0064] It should be noted that the above fields are listed for illustrative purposes only and do not imply any limitation. Any other suitable fields of DCI formats 0_1 and 0_2 or any suitable new fields may also be used to design a DCI for supporting a single DCI for scheduling uplink channels (such as but not limited to PUSCH on multiple cells). Such modifications, variations, and alternative configurations will be consistent with the spirit and scope of the embodiments of the present disclosure.
[0065] Still refer to Figure 2 In the signaling flow 200, the BS 110 transmits the configured single DCI to the UE 120 through the PDCCH. After receiving the configured DCI, the UE 120 transmits 230 in the PUSCH on the multiple cells 131-133 based on the configuration information included in the single DCI.
[0066] In some implementations, UE 120 may transmit in PUSCH on multiple cells 131-133 based on new DCI, which may be defined based on a new RNTI (eg, MC-RNTI). For example, the CRC of the new DCI may be scrambled by the MC-RNTI.
[0067] In some embodiments, UE 120 may transmit in PUSCH on multiple cells 131-133 based on a new DCI format (e.g., DCI format 0_3). By defining DCI format 0_3, each DCI field of the DCI format may be designed to simultaneously indicate scheduling information of multiple scheduled cells. In this way, UE 120 may transmit in PUSCH on multiple cells 131-133 based on scheduling information of multiple cells indicated by each field of a single DCI.
[0068] In some implementations, UE 120 transmits in PUSCH on multiple cells 131-133 based on a single DCI, which may be formed by concatenating DCIs from multiple cells.
[0069] Alternatively or additionally, UE 120 may transmit in PUSCH on multiple cells 131 - 133 based on the UL indicator field in a single DCI.
[0070] In some embodiments, a single DCI may include a single "UL / SUL indicator" field. A single "UL / SUL indicator" field may include a NUL indicator or a SUL indicator. Based on the NUL indicator in the UL indicator field, the UE 120 may transmit via NUL on multiple cells 131-133. Alternatively, based on the SUL indicator in the UL indicator field, the UE 120 may transmit via SUL on multiple cells 131-133. Alternatively, for a scheduling cell that is not configured with SUL, if the "UL / SUL indicator" field is indicated as SUL, the UE 120 may still transmit via NUL, or alternatively, the UE 120 may discard PUSCH transmission.
[0071] In some embodiments, a single DCI may include multiple "UL / SUL indicator" fields. Each UL / SUL indicator may be used for a PUSCH corresponding to a different scheduled cell 131-133. In this case, the number of bits of the "UL / SUL indicator" field may be configured as described above.
[0072] Alternatively or additionally, UE 120 may transmit in PUSCH on multiple cells 131 - 133 based on the FDRA field in a single DCI.
[0073] In some embodiments, the UE 120 may transmit in PUSCH on all of the multiple cells 131-133 with the same resource allocation type indicated by a single FDRA field in a single DCI. For example, the same resource allocation type may be one of resourceAllocation ENUMERATED{resourceAllocationType0,resourceAllocationType1,dynamicSwitch}, where resourceAllocationType0 represents a bitmap, resourceAllocationType1 represents a range length that tells the UE 120 which physical resource block (PRB) to start with and how many PRBs to send, and dynamicSwitch may trigger a dynamic switch between resourceAllocationType0 and resourceAllocationType1. Alternatively, the UE 120 may transmit in PUSCH on each of the multiple cells 131-133 with a resource allocation type indicated by one of the multiple FDRA fields in a single DCI.
[0074] In some embodiments, where a single FDRA field is included in a single DCI, UE 120 may assume that the same FDRA is scheduled for PUSCH in each cell that is scheduled simultaneously. When the effective BWP for different CCs is of different sizes, the DCI sizes may be aligned as described above.
[0075] Alternatively or additionally, UE 120 may transmit in PUSCH on multiple cells 131 - 133 based on the TDRA field in a single DCI.
[0076] In some embodiments, a single DCI may include a single TDRA field. In this case, the UE 120 may transmit in a PUSCH on multiple cells 131-133 with the same TDRA indicated by the single TDRA field. Alternatively, a single DCI may include multiple TDRA fields, and each TDRA may be used for a PUSCH corresponding to a different scheduled cell 131-133.
[0077] In some embodiments, where a single DCI includes a single TDRA field, UE 120 may determine an offset of a starting symbol that may be configured by BS 110 via RRC, such as Figure 3By assuming that the mapping type and the duration of the PUSCH are the same among all CCs scheduled simultaneously, the UE 120 may derive the second TDRA for the second cell 132 from the first TDRA for the first cell 131 based on the determined offset of the starting symbol.
[0078] In some implementations, UE 120 may transmit in PUSCH on multiple cells 131-133 with TDRAs configured from a TDRA table, as described above with reference to Table 1.
[0079] Alternatively or additionally, UE 120 may transmit in PUSCH on multiple cells 131 - 133 based on the SRS resource indicator field in a single DCI.
[0080] In some embodiments, the UE 120 may transmit on all of the plurality of cells 131-133 with codebook PUSCH operation or non-codebook PUSCH operation indicated by a single SRS resource indicator field in a single DCI. Alternatively, the UE 120 may transmit on some of the plurality of cells 131-133 with codebook PUSCH operation and on some of the plurality of cells 131-133 with non-codebook PUSCH operation based on multiple SRS resource indicator fields in a single DCI. Each SRS resource indicator in the multiple SRS resource indicator fields may correspond to one scheduled cell.
[0081] In some embodiments, when UE 120 determines to transmit PUSCH simultaneously, it may be necessary to ensure spatial relationship consistency. In some embodiments, UE 120 may transmit in PUSCH with the same spatial filter (simulated beam) for at least all scheduled cells in the same frequency band (i.e., intra-band CA). Alternatively, when UE 120 indicates that it only supports common beam management (CBM) for the corresponding frequency band combination, UE 120 may transmit in PUSCH with the same spatial filter for scheduled cells in different frequency bands (i.e., inter-band CA).
[0082] Alternatively or additionally, UE 120 may transmit in PUSCH on multiple cells 131 - 133 based on the CSI request field in a single DCI.
[0083] In some embodiments, a single DCI may include a single CSI request field. In this case, when UE 120 is scheduled to transmit in multiple PUSCHs, UE 120 may transmit aperiodic CSI in all PUSCHs on all scheduled cells 131-133. Alternatively, UE 120 may transmit aperiodic CSI in only a PUSCH on one of the scheduling cells 131-133.
[0084] In some embodiments, when a single DCI includes a single CSI request field, when UE 120 sends aperiodic CSI in PUSCH on only one of the scheduling cells 131-133, UE 120 may determine which cell to use to send the aperiodic CSI. For example, UE 120 may determine the single cell to be sent based on the cell with the lowest frequency. Alternatively, UE 120 may determine the single cell to be sent based on the cell whose PUSCH transmission (e.g., due to duplex direction conflict, UL preemption, etc.) is not canceled. Alternatively, UE 120 may determine the single cell to be sent based on a cell with a higher priority. Alternatively, UE 120 may determine the single cell to be sent based on a serving cell ID. Alternatively, UE 120 may determine the single cell to be sent based on the relative timing of PUSCH. For example, UE 120 may determine a cell in which PUSCH is scheduled to be transmitted earliest, or alternatively, UE 120 may determine a cell in which PUSCH meets the aperiodic CSI processing time requirement.
[0085] Alternatively or additionally, UE 120 may transmit in PUSCH on multiple cells 131 - 133 based on the UL-SCH indicator field in a single DCI.
[0086] In some embodiments, when a single DCI is used for scheduled UL data in PUSCH transmissions on multiple cells 131-133, and the data in the UE buffer of UE 120 is insufficient to fill all PUSCHs in all scheduled cells 131-133, UE 120 may append dummy data (e.g., all "0"s or "1"s) and still transmit on all scheduled cells 131-133. Alternatively, for a scheduled cell for which UE 120 has no data, UE 120 may choose not to transmit at all in the PUSCH for that cell.
[0087] In some embodiments, when UE 120 chooses not to transmit in the PUSCH for that cell at all, UE 120 may select which cell to transmit the PUSCH based on the UE specific implementation. Alternatively, UE 120 may omit PUSCH transmission on a cell with a lower priority. In some embodiments, the priority of each cell may be configured by the network (e.g., BS 110) via RRC. Alternatively, the priority of each cell may depend on one or more factors, such as a serving cell ID, a time division duplex (TDD) or frequency division duplex (FDD) band, a frequency of each of the multiple cells, a PUSCH priority, and a time of scheduled PUSCH transmission.
[0088] In general, assuming that the UE 120 applies the same field to all scheduled cells 131-133, a single DCI may include a single DCI field, or alternatively, a single DCI may include multiple DCI fields, one for each scheduled cell. The DCI field may be independently configured according to one or more of the following fields: frequency hopping flag, modulation and coding scheme, new data indicator, redundancy version, hybrid automatic repeat request (HARQ) process number, transmit power control (TPC) command for PUSCH, pre-coding information and number of layers, antenna port, SRS request, phase tracking reference signal-demodulation reference signal (PTRS-DMRS) association, DMRS sequence initialization, code block group (CBG) transmission information (CBGTI), priority, invalid symbol pattern indicator, primary cell (SCell) sleep indication, etc.
[0089] As noted above, these fields are listed for illustration purposes only and no limitation is implied.
[0090] Figure 4 4. Flowchart 400 illustrates an exemplary method performed by BS 110 to support a single DCI for scheduling uplink channels such as, but not limited to, PUSCH on multiple cells 131-133 in accordance with some embodiments of the present disclosure. For discussion purposes, reference will be made to Figures 1 to 3 Method 400 is described. Method 400 may involve Figure 1 It should be understood that method 400 may include additional blocks not shown and / or some of the shown blocks may be omitted, and the scope of the present disclosure is not limited in this regard.
[0091] At block 410 , the BS 110 configures a single DCI to schedule PUSCH on multiple cells simultaneously.
[0092] In some implementations, BS 110 may define a MC-RNTI via RRC and use the defined MC-RNTI to scramble the CRC of a single DCI.
[0093] In some embodiments, BS 110 may define a DCI format in which each field of a single DCI is designed to indicate scheduling information for multiple cells 131 - 133 .
[0094] In some embodiments, BS 110 may configure a field of a single DCI for each of the multiple cells. The size of the field may be independently configured for each of the multiple cells. In addition, BS 110 may concatenate the fields for each of the multiple cells to form a single DCI.
[0095] In some embodiments, BS 110 may configure the UL indicator field in a single DCI to schedule PUSCH on multiple cells. The UL indicator field may include a NUL indicator and / or a SUL indicator.
[0096] In some implementations, the number of bits of the UL indicator field may be determined based on one of the number of multiple cells indicated by the carrier indicator in a single DCI, the number of SULs on the multiple cells, or the number of SULs on a cell in the multiple cells.
[0097] In some implementations, BS 110 may configure a single FDRA field in the DCI for scheduling PUSCH on multiple cells. The single FDRA field may indicate the same resource allocation type for all multiple cells.
[0098] In some implementations, BS 110 may align the size of a single DCI by applying truncation or appending to the FDRA field.
[0099] In some embodiments, BS 110 may configure multiple TDRA fields in a single DCI for scheduling PUSCH on multiple cells. Each of the multiple TDRA fields may indicate a corresponding time domain resource for one of the multiple cells.
[0100] In some implementations, BS 110 may configure a single TDRA field in a single DCI for scheduling PUSCH on multiple cells. The single TDRA field may indicate the same time domain resources for all multiple cells.
[0101] In some embodiments, BS 110 may configure an offset of a starting symbol between a first cell and a second cell in the plurality of cells based on determining that the following information is the same: a mapping type of the first cell and the second cell and a duration of a PUSCH on the first cell and the second cell.
[0102] In some embodiments, BS110 may configure the TDRA table by determining at least the following information at each TDRA code point: a time slot offset, a mapping type for each of the multiple cells, and a StartSymbolAndLength including a duration and a start symbol of a PUSCH on each of the multiple cells. In addition, BS110 may configure each of the multiple TDRA fields for a cell in the multiple cells based on the TDRA table.
[0103] In some implementations, BS 110 may configure a single SRS resource indicator field in a single DCI.The single SRS resource indicator field may indicate that all of the multiple cells are configured with codebook PUSCH operation or non-codebook PUSCH operation.
[0104] In some embodiments, BS 110 may configure multiple SRS resource indicator fields in a single DCI. Each of the multiple SRS resource indicator fields may be used for one of the multiple cells to indicate codebook PUSCH operation or non-codebook PUSCH operation.
[0105] In some embodiments, BS 110 may configure a UL-SCH indicator field in a single DCI. The UL-SCH indicator field may be configured with one of the following bit numbers: 0; 1, for indicating whether UL data transmission is scheduled for all cells in a plurality of cells; the number of a plurality of cells, where each bit may indicate whether UL data transmission is scheduled for a corresponding cell in a plurality of cells; and the number of cells in a plurality of cells corresponding to a carrier indicator in a single DCI, where 1 bit may indicate whether UL data transmission is scheduled for each cell in a plurality of cells.
[0106] In some embodiments, BS110 may configure one or more fields in a single DCI for each of the multiple cells. The one or more fields may be determined based on at least the following fields: frequency hopping flag, modulation and coding scheme, new data indicator, redundancy version, hybrid automatic repeat request (HARQ) process number, transmit power control (TPC) command for PUSCH, pre-coding information and number of layers, antenna port, SRS request, phase tracking reference signal-demodulation reference signal (PTRS-DMRS) association, DMRS sequence initialization, code block group (CBG) transmission information (CBGTI), priority, invalid symbol mode indicator, primary cell (SCell) sleep indication, etc.
[0107] At block 420 , the BS 110 transmits the configured single DCI to the UE 120 via the PDCCH.
[0108] Figure 5Flowchart 500 illustrates an exemplary method performed by UE 120 to support a single DCI for scheduling uplink channels such as, but not limited to, PUSCH on multiple cells 131-133 in accordance with some embodiments of the present disclosure. For discussion purposes, reference will be made to Figures 1 to 3 Method 500 is described. Method 500 may involve Figure 1 It should be understood that method 500 may include additional blocks not shown and / or some of the shown blocks may be omitted, and the scope of the present disclosure is not limited in this regard.
[0109] At block 510, UE 120 receives a single DCI from the network (eg, BS 110) via the PDCCH.
[0110] At block 520, the UE 120 transmits in the PUSCH on multiple cells based on the configuration information included in the single DCI.
[0111] In some implementations, UE 120 may transmit in PUSCH on multiple cells based on scheduling information for the multiple cells indicated by each field of a single DCI.
[0112] In some embodiments, a single DCI may include one UL indicator field. The UL indicator field may include a NUL indicator and / or a SUL indicator. In addition, the UE 120 may send via NUL on multiple cells based on the NUL indicator in the UL indicator field. Alternatively, the UE 120 may send via SUL on multiple cells based on the SUL indicator in the UL indicator field. Alternatively, the UE 120 may send via NUL on a cell in the multiple cells indicated by the NUL indicator, and send via SUL on a cell in the multiple cells indicated by the SUL indicator.
[0113] In some embodiments, for a cell in the plurality of cells that is not configured with SUL, UE 120 may transmit via NUL in response to determining that the cell is indicated by the SUL indicator in the UL indicator field, or alternatively, UE 120 may drop PUSCH transmission.
[0114] In some embodiments, UE 120 may transmit in PUSCH on multiple cells with the same resource allocation type indicated by a single FDRA field in a single DCI. Alternatively, UE 120 may transmit in PUSCH on each of multiple cells with a resource allocation type indicated by one FDRA field in multiple FDRA fields in a single DCI.
[0115] In some implementations, UE 120 may transmit in a PUSCH on each of the multiple cells with corresponding time domain resources indicated by one of the multiple TDRA fields in a single DCI.
[0116] In some embodiments, UE 120 may determine the offset of the starting symbol between the first cell and the second cell in the plurality of cells based on the configuration information included in the single DCI. In addition, UE 120 may derive the second time domain resource for the second cell from the first time domain resource for the first cell based on the determined offset.
[0117] In some implementations, UE 120 may receive a TDRA table from the network via RRC and may configure multiple TDRA fields in a single DCI based on the TDRA table.
[0118] In some implementations, the UE 120 may transmit on all of the multiple cells 131-133 with either codebook PUSCH operation or non-codebook PUSCH operation indicated by a single SRS resource indicator field in a single DCI.
[0119] In some implementations, UE 120 may transmit on each of the multiple cells with codebook PUSCH operation or non-codebook PUSCH operation based on one SRS resource indicator field in multiple SRS resource indicator fields in a single DCI.
[0120] In some embodiments, UE 120 may determine to transmit in PUSCH on multiple cells simultaneously. In addition, UE 120 may transmit in PUSCH on multiple cells in the same frequency band or in different frequency bands with the same spatial filter to ensure spatial relationship consistency.
[0121] In some implementations, UE 120 may send aperiodic CSI in the PUSCH on all multiple cells based on a single CSI request field in a single DCI.
[0122] In some implementations, UE 120 may send aperiodic CSI in a PUSCH on one of the multiple cells based on a single CSI request field in a single DCI.
[0123] In some embodiments, UE 120 may determine one of the multiple cells from at least one of a cell with the lowest frequency, a cell where PUSCH transmission is not canceled, a cell with a higher priority, a cell with a serving cell ID, a cell where PUSCH is scheduled to be transmitted earliest, and a cell where PUSCH meets the non-periodic CSI processing time requirement.
[0124] In some implementations, UE 120 may transmit in PUSCH on multiple cells based on the UL-SCH indicator field in a single DCI.
[0125] In some embodiments, based on determining that the data in the UE buffer is insufficient to fill the PUSCH on all multiple cells, the UE 120 may append dummy data and still transmit in the PUSCH on all multiple cells. Alternatively, the UE 120 may not transmit in the PUSCH on the cell in the multiple cells where the UE has no data.
[0126] In some embodiments, in response to not transmitting in a PUSCH on a cell among the multiple cells for which the UE has no data, the UE 120 may select a cell for PUSCH transmission from the multiple cells based on UE specific implementation. Alternatively, the UE 120 may omit PUSCH transmission on a cell with a lower priority among the multiple cells.
[0127] In some embodiments, the priority of each of the multiple cells may be configured by the network via RRC. Alternatively, the priority of each of the multiple cells depends on at least one of the following factors: serving cell ID, time division duplex (TDD) or frequency division duplex (FDD) band, frequency of each of the multiple cells, PUSCH priority, and time of scheduled PUSCH transmission.
[0128] In some embodiments, UE 120 may transmit in PUSCH on multiple cells based on one or more fields in a single DCI. The one or more fields may be determined based on at least the following fields: frequency hopping flag, modulation and coding scheme, new data indicator, redundancy version, hybrid automatic repeat request (HARQ) process number, transmit power control (TPC) command for PUSCH, precoding information and number of layers, antenna port, SRS request, phase tracking reference signal-demodulation reference signal (PTRS-DMRS) association, DMRS sequence initialization, code block group (CBG) transmission information (CBGTI), priority, invalid symbol pattern indicator, primary cell (SCell) sleep indication, etc.
[0129] Figure 6 6 is a simplified block diagram of a device 600 suitable for implementing embodiments of the present disclosure. For example, BS 110 and UE 120 may be implemented by device 600. As shown, device 600 includes a processor 610, a memory 620 coupled to processor 610, and a transceiver 640 coupled to processor 610.
[0130] The transceiver 640 is used for bidirectional communication. The transceiver 640 is coupled to at least one antenna to facilitate communication. The transceiver 640 may include a transmitter circuit system (e.g., associated with one or more transmit chains) and / or a receiver circuit system (e.g., associated with one or more receive chains). The transmitter circuit system and the receiver circuit system may employ common circuit elements, different circuit elements, or a combination thereof.
[0131] Processor 610 may be of any type suitable for the local technology network and may include one or more of the following: as non-limiting examples, a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 600 may have multiple processors, such as application specific integrated circuit chips, which are time-constrained by a clock that synchronizes a main processor.
[0132] The memory 620 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 624, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disk (CD), digital video disk (DVD), and other magnetic storage devices and / or optical storage devices. Examples of volatile memories include, but are not limited to, random access memory (RAM) 622 and other volatile memories that do not persist during power-off time.
[0133] Computer program 630 includes computer executable instructions that are executed by associated processor 610. Program 630 may be stored in ROM 624. Processor 610 may perform any suitable operations and processes by loading program 630 into RAM 622.
[0134] The embodiments of the present disclosure can be implemented with the aid of program 630, so that the device 600 can execute the following steps: Figures 4 to 5 Any process of the present disclosure discussed. The embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.
[0135] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions (such as those included in a program module) that are executed in a device on a target real or virtual processor to perform the above-referenced Figure 4 The method 400 described and / or as described above with reference to Figure 5 The method 500 is described.
[0136] Further, although the operations are shown in a particular order, this should not be understood as requiring such operations to be performed in a sequential order or in the particular order shown, or requiring the execution of all the operations shown to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Although the above discussion includes several specific implementation details, these details should not be understood as limitations on the scope of the present disclosure, but should be considered as descriptions of features that may be peculiar to a particular embodiment. Certain features described in the context of different embodiments may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in the form of any suitable sub-combination.
[0137] Although the disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims
1. A processor of a base station (BS), the processor being configured to perform operations, the operations comprising: Configuring a single downlink control information (DCI) to schedule the physical uplink shared channel (PUSCH) on multiple cells simultaneously; and The single DCI is transmitted to a user equipment (UE) through a physical downlink control channel (PDCCH).
2. The processor of claim 1 , wherein configuring the single DCI comprises: defining a multi-cell radio network temporary identifier (MC-RNTI) via radio resource control (RRC); and A cyclic redundancy check (CRC) of the single DCI is scrambled using the defined MC-RNTI.
3. The processor of claim 1 , wherein configuring the single DCI comprises: A DCI format is defined, wherein each field of the single DCI is designed to indicate scheduling information of the multiple cells.
4. The processor of claim 1 , wherein configuring the single DCI comprises: configuring a field of the single DCI for each of the plurality of cells, wherein a size of the field is independently configured for each of the plurality of cells; and The fields for each cell of the plurality of cells are concatenated to form the single DCI.
5. The processor of claim 1 , wherein configuring the single DCI comprises: An uplink (UL) indicator field in the single DCI is configured to schedule the PUSCH on the multiple cells, wherein the UL indicator field includes a normal uplink (NUL) indicator and / or a supplemental uplink (SUL) indicator.
6. The processor of claim 5, wherein the number of bits of the UL indicator field is determined based on one of: the number of the plurality of cells; The number of SULs on the multiple cells; or The number of SULs on a cell in the plurality of cells is indicated by a carrier indicator in the single DCI.
7. The processor of claim 1 , wherein configuring the single DCI comprises: A single frequency domain resource allocation (FDRA) field for scheduling the PUSCH on the multiple cells is configured in the DCI, wherein the single FDRA field indicates a same resource allocation type for all the multiple cells.
8. The processor of claim 7, wherein configuring the single DCI further comprises: The size of the single DCI is aligned by applying truncation or appending to the FDRA field.
9. The processor of claim 1 , wherein configuring the single DCI comprises: A plurality of FDRA fields for scheduling the PUSCH on the plurality of cells are configured in the single DCI, wherein each of the plurality of FDRA fields indicates a corresponding resource allocation type for one of the plurality of cells.
10. The processor of claim 1 , wherein configuring the single DCI comprises: A plurality of TDRA fields for scheduling the PUSCH on the plurality of cells are configured in the single DCI, wherein each TDRA field of the plurality of TDRA fields indicates a corresponding time domain resource used for one cell among the plurality of cells.
11. The processor of claim 1 , wherein configuring the single DCI comprises: A single time domain resource allocation (TDRA) field for scheduling the PUSCH on the multiple cells is configured in the single DCI, wherein the single TDRA field indicates the same time domain resources for all the multiple cells.
12. The processor of claim 11, wherein configuring the single DCI further comprises: An offset of a starting symbol between a first cell and a second cell in the plurality of cells is configured based on determining that the following information is the same: A mapping type of the first cell and the second cell; and Duration of the PUSCH on the first cell and the second cell.
13. The processor of claim 11, wherein configuring the single DCI further comprises: The TDRA table is configured by determining at least the following information at each TDRA code point: Time slot offset, a mapping type for each cell in the plurality of cells, and a StartSymbolAndLength comprising a duration and a start symbol of the PUSCH on each of the plurality of cells; and Each of the plurality of TDRA fields is configured for a cell among the plurality of cells based on the TDRA table.
14. The processor of claim 1 , wherein configuring the single DCI comprises: A single sounding reference signal (SRS) resource indicator field is configured in the single DCI, wherein the single SRS resource indicator field indicates that all of the plurality of cells are configured with codebook PUSCH operation or non-codebook PUSCH operation.
15. The processor of claim 1 , wherein configuring the single DCI comprises: A plurality of SRS resource indicator fields are configured in the single DCI, wherein each of the plurality of SRS resource indicator fields is used for one cell among the plurality of cells to indicate a codebook PUSCH operation or a non-codebook PUSCH operation.
16. The processor of claim 1 , wherein configuring the single DCI comprises: A UL shared channel (UL-SCH) indicator field is configured in the single DCI, wherein the UL-SCH indicator field is configured with one of the following number of bits: 0, 1, indicating whether UL data transmission is scheduled for all cells in the plurality of cells, a number of the plurality of cells, wherein each bit indicates whether UL data transmission is scheduled for a corresponding cell in the plurality of cells, and The number of cells in the plurality of cells corresponds to the carrier indicator in the single DCI, wherein 1 bit indicates whether UL data transmission is scheduled for each cell in the plurality of cells.
17. The processor of claim 1 , wherein configuring the single DCI comprises: One or more fields in the single DCI are configured for each cell in the plurality of cells, wherein the one or more fields are determined from at least the following fields: Channel State Information (CSI) request, Frequency hopping marker, modulation and coding schemes, New data indicator, Redundant version, Hybrid Automatic Repeat Request (HARQ) process number, a transmit power control (TPC) command for the PUSCH, Pre-coding information and number of layers, Antenna port, SRS request, Phase Tracking Reference Signal-Demodulation Reference Signal (PTRS-DMRS) association, DMRS sequence initialization, Code Block Group (CBG) Transmit Information (CBGTI), Priority, invalid symbol mode indicator, and Primary cell (SCell) sleep indication.
18. A base station (BS), comprising: A processor according to any one of claims 1 to 17, and A transceiver is communicatively coupled to the processor and configured to communicate with a user equipment (UE).
19. A processor of a user equipment (UE), the processor being configured to perform operations comprising: receiving a single downlink control information (DCI) from the network via a physical downlink control channel (PDCCH); and The DCI is transmitted in a physical uplink shared channel (PUSCH) on multiple cells based on the configuration information included in the single DCI.
20. The processor of claim 19, wherein transmitting in the PUSCH on the multiple cells based on the configuration information included in the single DCI comprises: Transmitting in the PUSCHs on the multiple cells is performed based on scheduling information of the multiple cells indicated by each field of the single DCI.
21. The processor of claim 19, wherein the single DCI includes an uplink (UL) indicator field, the uplink (UL) indicator field including a normal uplink (NUL) indicator and / or a supplemental uplink (SUL) indicator, and wherein transmitting in the PUSCH on multiple cells based on the configuration information included in the single DCI comprises one of: transmitting via the NUL over the plurality of cells based on the NUL indicator in the UL indicator field; transmitting via the SUL over the plurality of cells based on the SUL indicator in the UL indicator field; or Transmission is performed by the NUL on a cell among the plurality of cells indicated by the NUL indicator, and transmission is performed by the SUL on a cell among the plurality of cells indicated by the SUL indicator.
22. The processor of claim 21, wherein, for a cell in the plurality of cells that is not configured with the SUL, in response to determining that the cell is indicated by the SUL indicator in the UL indicator field, transmitting in the PUSCH on the cell comprises one of: Send via the NUL; or The PUSCH transmission is discarded.
23. The processor of claim 19, wherein transmitting in the PUSCH on the multiple cells based on the configuration information included in the single DCI comprises one of: transmitting in the PUSCH on the multiple cells with the same resource allocation type indicated by a single frequency domain resource allocation (FDRA) field in the single DCI; or The transmission is performed in a PUSCH on each of the plurality of cells having a resource allocation type indicated by one of the plurality of FDRA fields in the single DCI.
24. The processor of claim 19, wherein transmitting in the PUSCH on the multiple cells based on the configuration information included in the single DCI comprises: The PUSCHs on the multiple cells are transmitted with the same time domain resources indicated by a single time domain resource allocation (TDRA) field in the single DCI.
25. The processor of claim 19, wherein transmitting in the PUSCH on the multiple cells based on the configuration information included in the single DCI comprises: The transmission is performed in a PUSCH on each of the plurality of cells having a corresponding time domain resource indicated by one of the plurality of TDRA fields in the single DCI.
26. The processor of claim 25, wherein transmitting in the PUSCH on the multiple cells based on the configuration information included in the single DCI further comprises: determining an offset of a starting symbol between a first cell and a second cell among the plurality of cells based on the configuration information included in the single DCI; and Second time domain resources for the second cell are derived from first time domain resources for the first cell based on the determined offset.
27. The processor of claim 25, wherein receiving the single DCI comprises receiving a TDRA table from the network via RRC, and wherein the plurality of TDRA fields in the single DCI are configured based on the TDRA table.
28. The processor of claim 19, wherein transmitting in the PUSCH on the multiple cells based on the configuration information included in the single DCI comprises: Transmitting on all of the plurality of cells with codebook PUSCH operation or non-codebook PUSCH operation indicated by a single sounding reference signal (SRS) resource indicator field in the single DCI.
29. The processor of claim 19, wherein transmitting in the PUSCH on the multiple cells based on the configuration information included in the single DCI comprises: Transmitting on each of the plurality of cells with codebook PUSCH operation or non-codebook PUSCH operation based on one SRS resource indicator field among the plurality of SRS resource indicator fields in the single DCI.
30. The processor of claim 29, wherein transmitting in the PUSCH on the multiple cells based on the configuration information included in the single DCI further comprises: Determine to send the PUSCH on the multiple cells simultaneously; and Transmission is performed in the PUSCHs on the multiple cells in the same frequency band or in different frequency bands with the same spatial filter to ensure spatial relationship consistency.
31. The processor of claim 19, wherein transmitting in the PUSCH on the multiple cells based on the configuration information included in the single DCI comprises: Aperiodic channel state information (CSI) is sent in the PUSCH on all of the plurality of cells based on a single CSI request field in the single DCI.
32. The processor of claim 19, wherein transmitting in the PUSCH on the multiple cells based on the configuration information included in the single DCI comprises: Aperiodic CSI is sent in a PUSCH on one of the plurality of cells based on the single CSI request field in the single DCI.
33. The processor of claim 32, wherein the processor is configured to determine the one of the plurality of cells according to at least one of: The cell with the lowest frequency, PUSCH transmission is not cancelled in the cell, The cell with higher priority, The cell with the smallest serving cell ID, PUSCH is scheduled as the earliest cell to transmit, and The cell where PUSCH meets the aperiodic CSI processing time requirement.
34. The processor of claim 19, wherein transmitting in the PUSCH on the multiple cells based on the configuration information included in the single DCI comprises: The PUSCH on the multiple cells is transmitted based on a UL shared channel (UL-SCH) indicator field in the single DCI.
35. The processor of claim 34, based on determining that the data in the UE buffer is insufficient to fill the PUSCH on all of the plurality of cells, the processor is configured to perform transmission in the PUSCH on the plurality of cells by one of the following operations: append dummy data and still transmit in the PUSCH on all the multiple cells; or The PUSCH of a cell in the plurality of cells where the UE has no data is not transmitted.
36. The processor of claim 35, in response to the UE not being in the plurality of cells transmitting in the PUSCH on the cell for which there is no data, the processor is configured to further perform one of the following operations: selecting a cell from the plurality of cells for PUSCH transmission based on UE specific implementation; or PUSCH transmission on a cell having a lower priority among the plurality of cells is omitted.
37. The processor of claim 36, wherein: The priority of each of the plurality of cells is configured by the network via RRC; or The priority of each of the plurality of cells depends on at least one of the following factors: Serving cell ID, Time Division Duplex (TDD) or Frequency Division Duplex (FDD) bands, a frequency of each cell of the plurality of cells, PUSCH priority, and The time of scheduled PUSCH transmission.
38. The processor of claim 19, wherein transmitting in the PUSCH on the multiple cells based on the configuration information included in the single DCI comprises: The DCI on multiple cells based on one or more fields in the single DCI The PUSCH is transmitted, wherein the one or more fields are determined from at least the following fields: Channel State Information (CSI) Request Frequency hopping marker, modulation and coding schemes, New data indicator, Redundant version, Hybrid Automatic Repeat Request (HARQ) process number, a transmit power control (TPC) command for the PUSCH, Pre-coding information and number of layers, Antenna port, SRS request, Phase Tracking Reference Signal-Demodulation Reference Signal (PTRS-DMRS) association, DMRS sequence initialization, Code Block Group (CBG) Transmit Information (CBGTI), Priority, invalid symbol mode indicator, and Primary cell (SCell) sleep indication.
39. A user equipment (UE), comprising: A processor according to any one of claims 19 to 38, and A transceiver is communicatively coupled to the processor and is configured to communicate with a network.
Citation Information
Cited By
Method and apparatus for allocating resource blocks to cell group in vran
WO2026160515A1
