Determination of DCI formats for multi-cell scheduling for wireless communications

Abstract

The present disclosure relates to wireless communications, a network device determines a downlink control information (DCI) format for multi-cell scheduling transmissions in a set of cells, where determining the DCI format comprises determining at least one size of at least one DCI field of the DCI format. The network device transmits DCI with the DCI format to schedule transmissions for at least one cell in the set of cells. Furthermore, the user equipment receives a radio resource control (RRC) configuration for determining a DCI format for multi-cell scheduling transmission in the set of cells, and receives DCI having the DCI format for scheduling transmission for at least one cell in the set of cells.

Description

Technical Field

[0001] The present disclosure relates to the determination of scheduling information in wireless communication. Background Art

[0002] The fourth-generation mobile communication technology (4G) Long Term Evolution (LTE) or Long Term Evolution-Advanced (LTE-A), as well as the fifth-generation mobile communication technology (5G), are facing increasing demands. To meet these demands, 4G and 5G systems are developing support for Enhanced Mobile Broadband (eMBB), Ultra Reliable Low Latency Communication (URLLC), and Massive Machine Type Communication (mMTC) capabilities. As part of this development, Carrier Aggregation (CA) can be applied to 4G, 5G, and future communication systems.

[0003] In the current CA process, the scheduling mechanism can only schedule Physical Uplink Shared Channel (PUSCH) transmissions or Physical Downlink Shared Channel (PDSCH) transmissions in a single cell based on scheduling Downlink Control Information (DCI). As more scattered spectrum bands become available, the demand for simultaneously scheduling PUSCH / PDSCH transmissions in multiple cells is expected to increase. Extending from single-cell scheduling to multi-cell PUSCH / PDSCH scheduling using a single scheduling DCI may ideally reduce control overhead. However, when using a single scheduling DCI for multi-cell scheduling, format problems or other configuration problems may occur. Finding solutions to these problems is worthy of consideration. Summary of the Invention

[0004] The present disclosure relates to methods, systems, apparatuses, and devices for wireless communication. In some implementations, a method for wireless communication includes: a network device determining a Downlink Control Information (DCI) format for multi-cell scheduling transmissions in a set of cells, including determining at least one size of at least one DCI field of the DCI format; and the network device sending a DCI having the DCI format to schedule transmissions for at least one cell in the set of cells.

[0005] In some implementations, a method of wireless communication includes: a user equipment receiving a Radio Resource Control (RRC) configuration of a downlink control information (DCI) format for determining multi-cell scheduling transmissions in a set of cells, including determining at least one size of at least one DCI field of the DCI format; and the user equipment receiving a DCI having the DCI format to schedule a transmission for at least one cell in the set of cells.

[0006] In some other implementations, a device such as a network device is disclosed. The device may include one or more processors and one or more memories, wherein the one or more processors are configured to read computer code from the one or more memories to implement any of the above methods.

[0007] In some additional implementations, a computer program product is disclosed. The computer program product may include a non-transitory computer-readable program medium having computer code stored thereon, which when executed by one or more processors, causes the one or more processors to implement any of the above methods.

[0008] The above and other aspects and their implementations will be described in more detail in the drawings, the description, and the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 A block diagram of an example wireless communication system is shown.

[0010] Figure 2 A schematic diagram of an example multi-cell scheduling is shown.

[0011] Figure 3 A flowchart of a method of a wireless communication system is shown.

[0012] Figure 4 A flowchart of a wireless communication system is shown. DETAILED DESCRIPTION

[0013] The present disclosure describes various embodiments of systems, apparatuses, devices, and methods related to the determination of scheduling information in wireless communication.

[0014] Figure 1 A schematic diagram of an exemplary wireless communication system 100 is shown, which includes a plurality of communication nodes (or simply nodes) configured to communicate wirelessly with each other. Generally, the communication nodes include at least one user equipment 102 and at least one network device 104. Figure 1The exemplary wireless communication system 100 therein shows two user equipments 102, namely including the first user equipment 102(1) and the second user equipment 102(2), and a network device 104. However, various other embodiments of the wireless communication system 100 include any combination of one or more user equipments 102 and / or one or more network devices 104.

[0015] Generally speaking, the user equipment (such as the user equipment 102) described in this disclosure may include a single electronic device or apparatus, or multiple electronic devices or apparatuses capable of wireless communication through a network (for example, a network of electronic devices or apparatuses). The user equipment may be included or otherwise referred to as a user terminal, a user terminal device, or a user equipment (User Equipment, UE). In addition, the user equipment may be or may include, but is not limited to, the following devices: mobile devices (such as mobile phones, smart phones, smart watches, tablets, laptops, vehicles, or other means of transportation (human-powered, motorized, or engine-driven means of transportation, such as cars, airplanes, trains, ships, or bicycles, only as non-limiting examples)), or fixed or stationary devices (such as desktop computers or other computing devices that generally do not move for a long time, such as home appliances, other relatively heavy devices (including Internet of Things (IoT) devices), or computing devices used in commercial or industrial environments, only as non-limiting examples)). In various embodiments, the user equipment 102 may include a transceiver 106 coupled to an antenna 108 to enable wireless communication with the network device 104. The transceiver 106 may also be coupled to a processor 110, and the processor 110 may also be coupled to a memory 112 or other storage devices. The memory 112 may store instructions or code, which when read and executed by the processor 110, cause the processor 110 to implement the various methods described in this disclosure.

[0016] In addition, generally speaking, the network device (such as network device 104) described in the present disclosure may include a single electronic device or apparatus, or multiple electronic devices or apparatuses (e.g., a network of electronic devices or apparatuses), and may include one or more wireless access nodes, base stations, or other wireless network access points capable of wirelessly communicating with one or more user devices and / or with one or more other network devices 104 via a network. For example, in various embodiments, network device 104 may include a 4G LTE base station, a 5G NR base station, a 5G central unit base station, a 5G distributed unit base station, a next-generation Node B (gNB), an enhanced Node B (eNB), or other similar base stations or next-generation (e.g., 6G) base stations. Network device 104 may include a transceiver 114 coupled to an antenna 116, which may include an antenna tower 118 in various scenarios to enable wireless communication with user device 102 or another network device 104. Transceiver 114 may also be coupled to one or more processors 120, which may also be coupled to a memory 122 or other storage device. Instructions or code may be stored in memory 122, and when these instructions or code are read and executed by processor 120, they cause processor 120 to implement one or more of the methods described in the present disclosure.

[0017] In various embodiments, two communication nodes in wireless communication system 100 (such as, a user device 102 and a network device 104, two user devices 102 without a network device 104, or two network devices 104 without a user device 102) may be configured to wirelessly communicate with each other in and / or through a mobile network and / or a wireless access network according to one or more standards and / or specifications. Generally speaking, these standards and / or specifications may define the rules or procedures based on which communication nodes can perform wireless communication. In various embodiments, these rules or procedures may include rules or procedures for communicating in the millimeter wave (mm) band, and / or rules or procedures related to multi-antenna schemes and beamforming functions. Additionally or alternatively, these standards and / or specifications are standards and / or specifications that define radio access technologies and / or cellular technologies, such as 4G Long-Term Evolution (LTE), 5G New Radio (NR), or Unlicensed New Radio (NR-U), as non-limiting examples.

[0018] In addition, in the wireless communication system 100, communication nodes are configured to interact wireless communication signals. Generally speaking, the communication between two communication nodes in the wireless communication system 100 can be sending or receiving, and usually includes both, depending on the perspective of a specific node in the communication. For example, for a given communication between a first node and a second node, where the first node sends a signal to the second node and the second node receives the signal from the first node, the first node can be referred to as a source node or a transmitting node or device, the second node can be referred to as a target node or a receiving node or device, and this communication can be regarded as transmission for the first node and reception for the second node. Of course, since the communication nodes in the wireless communication system 100 can both send and receive signals, a single communication node may be both a transmitting node / source node and a receiving node / target node, or switch between the source node / transmitting node and the target node / receiving node.

[0019] In addition, a specific signal can be characterized or defined as an uplink (UL) signal, a downlink (DL) signal, or a side link (SL) signal. An uplink signal is a signal sent from the user equipment 102 to the network equipment 104. A downlink signal is a signal sent from the network equipment 104 to the user equipment 102. A side link signal is a signal sent from one user equipment 102 to another user equipment 102, or a signal sent from one network equipment 104 to another network equipment 104. In addition, for side link transmission, the first user equipment / source user equipment 102 directly sends the side link signal to the second user equipment / target user equipment 102 without forwarding the side link signal to the network equipment 104.

[0020] In addition, the signals transmitted between communication nodes in the wireless communication system 100 can be characterized or defined as data signals or control signals. Generally speaking, a data signal is a signal that contains or carries data (such as multimedia data, e.g., voice and / or image data), while a control signal is a signal that carries control information, and this control information configures communication nodes in a specific way so that they can communicate with each other, or otherwise controls how data signals are transmitted between communication nodes. Moreover, some signals can be defined or characterized by a combination of data / control and uplink / downlink / side link, including uplink control signals, uplink data signals, downlink control signals, downlink data signals, side link control signals, and side link data signals.

[0021] For some specifications, such as 5G NR, data signals and control signals are transmitted and / or carried on physical channels. Generally speaking, a physical channel corresponds to a set of time-frequency resources used for transmitting signals. Different types of physical channels can be used to transmit different types of signals. For example, a physical data channel (or simply referred to as a data channel), also called a traffic channel in this disclosure, is used to transmit data signals, while a physical control channel (or simply referred to as a control channel) is used to transmit control signals. Example types of traffic channels (or physical data channels) include but are not limited to the physical downlink shared channel PDSCH for transmitting downlink data signals, the physical uplink shared channel PUSCH for transmitting uplink data signals, and the physical sidelink shared channel PSSCH for transmitting sidelink data signals. In addition, example types of physical control channels include but are not limited to the physical downlink control channel PDCCH for transmitting downlink control signals, the physical uplink control channel PUCCH for transmitting uplink control signals, and the physical sidelink control channel PSCCH for transmitting sidelink control signals. Unless otherwise specified, for simplicity, a specific type of physical channel in this disclosure is also used to refer to the signal transmitted on that specific type of physical channel, and / or the transmission on that specific type of channel. For example, PDSCH refers to the physical downlink shared channel itself, the downlink data signal transmitted on the PDSCH, or the downlink data transmission. Therefore, a communication node sending or receiving PDSCH means that the communication node is sending or receiving a signal on the PDSCH.

[0022] In addition, for certain specifications, such as 5G NR, and / or for at least some types of control signals, the control signals sent by a communication node may include control information that includes information necessary to enable one or more data signal transmissions between communication nodes, and / or information necessary to schedule one or more data channels (or one or more transmissions on a data channel). For example, such control information may include information necessary for correct reception, decoding, and demodulation of data signals received on a physical data channel during data transmission, and / or may include information for uplink scheduling grants that inform a user equipment of the resources and transmission format for uplink data transmission. In some embodiments, the control information includes downlink control information DCI that is sent from network device 104 to user equipment 102 in the downlink direction. In other embodiments, the control information includes uplink control information (UCI) that is sent from user equipment 102 to network device 104 in the uplink direction, or includes side link control information (SCI) that is sent from one user equipment 102(1) to another user equipment 102(2) in the side link direction.

[0023] In addition, in some implementations of carrier aggregation CA, the scheduling process employed by communication nodes in a wireless communication system may schedule PUSCH or PDSCH transmissions in a single cell based on only one scheduling DCI. In other embodiments, a single scheduling DCI may be used to simultaneously schedule PUSCH or PDSCH transmissions in multiple cells (referred to as multi-cell scheduling). Using only a single scheduling DCI for multi-cell scheduling of PUSCH or PDSCH transmissions may reduce control overhead.

[0024] In addition, for certain embodiments, multi-cell scheduling for a set of cells may be performed using a single scheduling DCI having DCI format 0_X or DCI format 1_X (where X is an integer). Hereafter, for simplicity, the DCI format having the format of DCI format 0_X or DCI format 1_X is referred to as DCI 0_X / 1_X.

[0025] In addition, for some embodiments, the DCI size of DCI format 0_X / 1_X is calculated on one cell in the cell set, the blind decoding (BD) / control channel element (CCE) of DCI format 0_X / 1_X is also calculated on one cell in the cell set, the search space of DCI format 0_X / 1_X is configured on one cell in the cell set, and is associated with the search space of the scheduling cell with the same search space identifier ID. Additionally, each field in DCI format 0_X / 1_X may have an associated field type. For some embodiments, each field type may be one of the following types: type 1A, type 1B, type 1C, or type 2. A field of field type 1A is a single field that indicates common information for all co-scheduled cells. A field of field type 1B is a single field that indicates information for each cell in the co-scheduled cells by joint indication. A field of field type 1C is a single field that indicates information for only one cell in the co-scheduled cells. A field of field type 2 is a field that is individual or unique for each cell in the co-scheduled cells.

[0026] In addition, in some embodiments, the size of the type 1A field in DCI format 0_X / 1_X is determined as the maximum field size of the active bandwidth part (BWP) among all cells in the cell set. However, in some embodiments, the field size of the DCI format of one cell in the co-scheduled cell set may be smaller than the determined field size of the type 1A field in DCI format 0_X / 1_X for multi-cell scheduling, which results in an inconsistency between the DCI format of one cell in the cell set and the DCI format for multi-cell scheduling of the co-scheduled cells of the cell set. This disclosure describes methods for handling such an inconsistent situation. This disclosure also describes methods for determining the size of the type 1C field in DCI format 0_X / 1_X.

[0027] Figure 2 A schematic diagram of an example multi-cell scheduling is shown. In this embodiment of the multi-cell scheduling, the scheduled cell can only be configured with one scheduling cell, and a single multi-cell scheduling DCI (MC-DCI) with DCI format 0_X / 1_X that can be carried by the PDCCH can be used to schedule multiple PxSCHs on multiple cells, one PxSCH per cell, where PxSCH can be PDSCH or PUSCH. As Figure 2As shown, there is only one scheduled cell, and the scheduled cell of the scheduled cell can support MC-DCI and / or SC-DCI (Single Cell Scheduling DCI, that is, the traditional DCI format, for example, DCI format 0_1 / 1_1), and the MC-DCI has DCI format 0_X / 1_X.

[0028] In Figure 2 In embodiments of multi-cell scheduling, the DCI size and / or BD / CCE of the PDCCH carrying the multi-cell scheduling DCI can be calculated on one cell in the cell set. The blind decoding BD may correspond to the maximum number of PDCCH candidates monitored within each time slot / time span by a DL BWP with a subcarrier spacing (SCS) configuration in a single serving cell. In addition, the control channel element CCE may correspond to the maximum number of non-overlapping CCEs within each time slot / time span by a DL BWP with an SCS configuration in a single serving cell.

[0029] In addition, for at least some embodiments, the size of the type 1B field in DCI format 0_X / 1_X may be equal to the upper limit value (log2(N)), where N is the number of rows in the radio resource control (RRC) configuration table, and each row includes multiple indices of all cells within the cell set. Additionally or alternatively, the type 1B field may indicate a row in the configuration table. Additionally or alternatively, the type 1B index of a cell may point to the corresponding index in the RRC configuration table applicable to DCI format 0_1 / 1_1, or the Medium Access Control Element (MAC CE) activation value. Additionally or alternatively, the size of the type 2 field for each cell in DCI format 0_X / 1_X may be determined based on the active BWP of each cell.

[0030] Figure 3 A flowchart of a wireless communication example method 300 involving DCI formats for multi-cell scheduling transmission is shown. In step 302, the network device 104 may determine the DCI format for multi-cell scheduling transmission in the cell set. Determine at least one size of at least one DCI field of the DCI format. In step 304, the network device 104 may send a DCI with the DCI format to schedule transmission for at least one cell in the cell set.

[0031] Figure 4FIG. 400 is a flow chart of another exemplary method for wireless communication involving multi-cell scheduling transmission. In step 402, user equipment 102 may receive a radio resource control (RRC) configuration for determining a downlink control information (DCI) format for multi-cell scheduling transmission in a set of cells. Determining the DCI format may include determining at least one size of at least one DCI field of the DCI format. In step 404, user equipment 102 may receive a DCI having the DCI format to schedule transmission for at least one cell in the set of cells.

[0032] In some embodiments of method 300 and / or method 400, a DCI field of the DCI format is a single field that indicates information for one cell in a co-scheduled cell, and the size of the DCI field is determined by one cell in the set of cells. In some of these embodiments, one cell in the set of cells is determined by a first cell having the largest DCI field size in the active bandwidth part (BWP) of a second cell having the smallest cell index in each subset of the set of cells, where each subset corresponds to a respective combination of co-scheduled cells in the set of cells. In some other embodiments, one cell in the set of cells is determined by a first cell having the largest DCI field size in the active bandwidth part (BWP) of all cells in the set of cells. In some other embodiments, when a table defining a co-scheduled cell combination of the set of cells is configured, one cell of the set of cells is determined by a first cell having the largest first DCI field size in the first active bandwidth part (BWP) of a second cell having the smallest cell index in each subset of the set of cells; and when the table is not configured, one cell of the set of cells is determined by a third cell having the second largest DCI field size in the second active BWP of all cells in the set of cells. In any of these embodiments, any two of the first cell, the second cell, and the third cell may be the same as or different from each other.

[0033] In addition, in some embodiments of method 300 and / or method 400, at least one DCI field includes an open-loop power control (OLPC) field that contains a parameter set indication. The OLPC parameter set indication may be determined by determining a field type of the OLPC field of the DCI format to match a field type of a sounding reference signal resource indicator (SRI).

[0034] In addition, in some embodiments, at least one DCI field includes an OLPC field that contains a parameter set indication, and the size of the OLPC field is determined as the maximum field size of the activated bandwidth part (BWP) among all cells within the cell set. When the size of the OLPC field of a cell in the cell set is smaller than the determined size of the OLPC field in the DCI format, for this cell in the cell set, the parameter set indication of the OLPC field can be re-parsed from 2 bits with a value of "10" to 1 bit with a value of "1". For example, through re-parsing, the user equipment 102 may not use a single 1 bit with a value of '0' (e.g., the least significant bit, LSB), but may represent, transform, or otherwise use a single 1 bit with a value of '1' for the parameter set indication in the OLPC field of a cell that uses only one bit as the OLPC field size.

[0035] In addition, in some embodiments, the DCI field includes an open-loop power control (OLPC) field that contains a parameter set indication, and the size of the OLPC field is configured for each cell set.

[0036] In addition, in some embodiments, the DCI field includes a redundant version (RV) field, and the size of the RV field is configurable. When a 1-bit RV field is configured, two RV values are determined through a default RV table, or are configured in one of two candidate RV tables for each bandwidth part (BWP), each cell, or each cell set.

[0037] Next, some additional details are described in the embodiments, which may be part of method 300 and / or method 400.

[0038] Embodiment 1

[0039] Regarding the DCI formats 0_X / 1_X, there is a consensus on the issue of determining the sizes of type 1A, 1B, and 2 fields. In addition to the remaining issues of type 1A, the issue of determining the size of the type 1C field also needs to be resolved.

[0040] In addition, for some embodiments, the type 1C field is a single field that indicates information for only one cell of the co-scheduled cells. Additionally, in some embodiments, the size of the type 1C field is determined by the cell indicated in the co-scheduled cells. For such embodiments, the DCI formats 0_X / 1_X will have variable sizes. In some cases, it may be desirable to avoid the situation of variable sizes.

[0041] For example, some embodiments for determining the size of a type 1C field may utilize a Channel State Information (CSI) request. To illustrate this, assume that the CSI request field sizes for cell numbers 1, 2, 3, and 4 are 2, 3, 6, and 4 bits, respectively. In one embodiment, further assume that the co-scheduled cells include cell numbers 1, 2, and 3. If the size of the CSI request is derived from the configuration of cell number 1, then the size of the type 1C field is 2 bits. As another example, assume that the co-scheduled cells include cell numbers 2, 3, and 4. If the size of the CSI request is derived from the configuration of cell number 2, then the size of the type 1C field is 3 bits. As shown, using the size of the CSI field request may result in different sizes for the type 1C field of DCI format 0_X, which may cause problems because user equipment 102 may be configured to monitor DCI formats of the same size in an active bandwidth part (BWP).

[0042] In addition, for at least some embodiments, the type 1C field may include at least one CSI request and / or an Uplink Shared Channel (UL-SCH) indicator. In some embodiments, the CSI request may contain 0, 1, 2, 3, 4, 5, or 6 bits and may be determined by the higher layer parameter "reportTriggerSize". Additionally or alternatively, the CSI request in DCI format 0_X may belong to the type 1C field. The type 1C field applies to the cell with the smallest serving cell index among co-scheduled cells. Additionally, the UL-SCH indicator may have a "0" bit value or a "1" bit value as follows. When the number of scheduled PUSCHs indicated by the time domain resource allocation field is greater than 1, the UL-SCH indicator may have a 0 bit value. Otherwise, the UL-SCH indicator may have a "1" bit value. The value "1" indicates that the UL-SCH can be transmitted on the PUSCH, and the value "0" indicates that the UL-SCH cannot be transmitted on the PUSCH. For embodiments where the user equipment 102 does not support triggering the Sounding Reference Signal (SRS) only in DCI (except for DCI format 0_1 that scrambles the Cyclic Redundancy Check (CRC) with a Semi-Persistent (SP)-CSI-Radio Network Temporary Identifier (RNTI)), the user equipment 102 may not be expected to receive a DCI format 0_1 with a UL-SCH indicator of "0" and all CSI requests being zero. Additionally, if the user equipment 102 supports triggering SRS only in DCI (except for DCI format 0_1 that scrambles the CRC with an SP-CSI-RNTI), the user equipment 102 may not be expected to receive a DCI format 0_1 with a UL-SCH indicator of "0", all CSI requests being zero, and all SRS requests being zero.

[0043] In addition, in some embodiments, the UL-SCH indicator in DCI format 0_X may belong to the type 1C field. The type 1C field can be applied to the cell with the smallest serving cell index among co-scheduled cells.

[0044] In addition, in some embodiments, the size of the type 1C field in DCI format 0_X / 1_X can be determined by one of the following schemes.

[0045] In the first scheme (Scheme 1): The size of the type 1C field in the DCI format 0_X / 1_X of the cell set is determined as the maximum field size of the activated bandwidth part BWP in the cell with the smallest serving cell index in each co-scheduled cell combination of the cell set. For example, Table 1 below lists the co-scheduled cell indicators, each corresponding to a respective combination of the co-scheduled cells of the cell set.

[0046] Table 1: Co-scheduled cell combinations of the cell set (cell numbers 0, 1, 2, 3)

[0047] Common scheduling cell indicator Scheduled cell 00 Cell #0 01 Cell #0 / 1 10 Cell #1 / 2 11 Cell #0 / 1 / 2 / 3

[0048] Further referring to Table 1, assume that the sizes of the CSI requests for cell numbers 0, 1, 2, 3 are 2, 3, 4, 5 bits respectively. According to Scheme 1, the smallest serving cell index in each co-scheduled cell combination of the cell set is: cell #0 in three co-scheduled cell combinations, and cell #1 in one co-scheduled cell combination. The size of the CSI request field in the DCI format 0_X is max{2, 3} = 3 bits.

[0049] In the second scheme (Scheme 2), the size of the type 1C field in the DCI format 0_X / 1_X of the cell set is determined as the maximum field size of the activated BWP in all cells of the cell set. For example, Table 1 can be used or configured to derive the co-scheduled cell combinations of the cell set (cell numbers 0, 1, 2, 3). For this embodiment, assume that the sizes of the CSI requests for cell numbers 0, 1, 2, 3 are 2, 3, 4, 5 bits respectively. According to Scheme 2, the size of the CSI request field in the DCI format 0_X is max{2, 3, 4, 5} = 5 bits. For another embodiment, assume that the table defining the co-scheduled cell combinations of the cell set (cell numbers 0, 1, 2, 3) is not configured. Additionally, assume that the sizes of the CSI requests for cell numbers 0, 1, 2, 3 are 2, 3, 4, 5 bits respectively. According to Scheme 2, the size of the CSI request field in the DCI format 0_X is max{2, 3, 4, 5} = 5 bits.

[0050] In the third scheme (Scheme 3), if a table defining the co-scheduled cell combinations of the cell set is configured or available for use, then Scheme 1 is used to determine the size of the type 1C field. Otherwise, Scheme 2 is used to determine the size of the type 1C field.

[0051] In some embodiments, if the field size of the type 1C field of DCI format 0_X / 1_X used for a co-scheduled cell combination (i.e., co-scheduling the co-scheduled cell combination simultaneously) is less than the determined field size of DCI format 0_X / 1_X for multi-cell scheduling, then the LSB or MSB of this field is applied.

[0052] Accordingly, when DCI format 0_X / 1_X is configured, the size of the type 1C field of DCI format 0_X / 1_X can be determined by using the maximum field size in the cell with the smallest serving cell index in each co-scheduled cell combination or by using the maximum field size in all cells within this cell set. This may desirably provide a fixed size for the DCI format after RRC configuration. Additionally or alternatively, doing so may desirably avoid the monitoring problem that the user equipment 102 is configured to monitor a single size of a DCI format in the active BWP.

[0053] Embodiment 2

[0054] In some embodiments, if the field size of the type 1A field of one of the co-scheduled cells is less than the determined field size in DCI format 0_X / 1_X for multi-cell scheduling, then corresponding measures can be taken for the indication in this type 1A field.

[0055] In some embodiments, if the field size of a field in the DCI format used by one of the co-scheduled cells is less than the determined field size of the corresponding field in DCI format 0_X / 1_X for multi-cell scheduling, then a least significant bit (LSB) operation, evaluation, or re-parsing can be performed on this field. If one of the co-scheduled cells has no relevant configuration for this field, or if this field indicates an inapplicable value for this cell, the user equipment 102 can ignore this field of this cell.

[0056] In some embodiments, the type 1A field can be an OLPC field containing an open-loop power control (OLPC) parameter set indication. In a specific embodiment of these embodiments, the OLPC parameter set indication in DCI format 0_X may be consistent with the definition of the physical layer (PHY) priority indicator, for example, by having the same PHY priority and / or the same open-loop (OL) transmission power control (TPC) parameter set.

[0057] In one embodiment, it is assumed that cell 1 and cell 2 are co-scheduled by DCI format 0_X. Additionally, it is assumed that the SRS resource indicator SRI field is a type 2 field, cell 1 does not include the SRI field in DCI format 0_1 and is configured with a 2-bit OLPC, while cell 2 includes the SRI field in DCI format 0_1 and is configured with a 1-bit OLPC. In some embodiments, when the field size in one of the co-scheduled cells is smaller than the field size determined in DCI format 0_X / 1_X of that field, LSB can be applied. For example, when the OLPC indication is a 2-bit value '10', cell 1 may apply the second value in P0-PUSCH-Set with the lowest p0-PUSCH-SetID value, while cell 2 may apply the first P0-PUSCH-AlphaSet in p0-AlphaSets, which may result in different priority operations for PUSCH on multiple cells.

[0058] The following describes the OLPC field in DCI format 0_1.

[0059] The size indicated by the open-loop power control OLPC parameter set can be 0, 1, or 2 bits. If the higher layer parameter p0-PUSCH-SetList is not configured, the size indicated by the OLPC parameter set can be 0 bits. If the higher layer parameter p0-PUSCH-SetList is configured, the size indicated by the OLPC parameter set can be 1 or 2 bits.

[0060] Additionally, when there is an SRS resource indicator in DCI format 0_1, the size indicated by the OLPC parameter set may be 1 bit. For some embodiments, for a low priority case, the 1-bit value can be '0', while for a high priority case, the value can be '1'. Additionally or alternatively, a 1-bit value of '0' may indicate P0 in p0-AlphaSets{p0-PUSCH-AlphaSetId value = SRI field value}; while a 1-bit value of '1' may indicate P0 in P0-PUSCH-Set{p0-PUSCH-SetId value = SRI field value}.

[0061] Additionally or alternatively, if there is no SRS resource indicator in DCI format 0_1, whether the size indicated by the OLPC parameter set is 1 bit or 2 bits can be determined by the higher layer parameter olpc-ParameterSetDCI-0-1. Similar to the above, the bit values '0' and / or '00' may be used for low priority cases, while the bit values '1', '01', or '10' may be used for high priority cases. Additionally or alternatively, the bit values '0' and / or '00' may represent the first P0-PUSCH-AlphaSet in p0-AlphaSets; the bit value '1' or '01' may represent the first value in the P0-PUSCH-Set with the lowest p0-PUSCH-SetID value; and the bit value '10' may represent the second value in the P0-PUSCH-Set with the lowest p0-PUSCH-SetID value.

[0062] Additionally or alternatively, for some embodiments, including those related to low priority cases, the user equipment 102 may be provided with more than one value of p0-PUSCH-AlphaSetId through SRI-PUSCH-PowerControl. For such embodiments, if the DCI format scheduling the PUSCH transmission contains an SRI field, the user equipment 102 can obtain a mapping relationship between the set of values of the SRI field in the DCI format and the set of indexes provided by p0-PUSCH-AlphaSetId, based on the sri-PUSCH-PowerControlId in SRI-PUSCH-PowerControl, where the set of indexes maps to the set of P0-PUSCH-AlphaSet values. Additionally, the user equipment 102 can determine P O_UE_PUSCH,b,f,c (j) value from the p0-PUSCH-AlphaSetId values mapped to the SRI field value. Moreover, in some embodiments for high priority cases, if the DCI format also contains an OLPC field and the value of the OLPC parameter set indication field is "1", the user equipment 102 can determine P O_UE_PUSCH,b,f,c (j) value according to the first value in the P0-PUSCH-Set with the p0-PUSCH-SetId value mapped to the SRI field value.

[0063] In addition, in some embodiments, if a PUSCH transmission (except for PUSCH retransmissions corresponding to Random Access Response (RAR) uplink (UL) grants) is scheduled by a DCI format that does not include an SRI field, or if SRI-PUSCH-PowerControl is not provided to the UE (such as in the case of high priority), j = 2. Additionally or alternatively, for embodiments in which P0-PUSCH-Set is provided to user equipment 102 and the DCI format includes an OLPC field, user equipment 102 may determine the value of P O_UE_PUSCH,b,f,c (j) as follows: For low priority cases, when the OLPC parameter set indication value in the OLPC field is "0" or "00", determine the value from the first P0-PUSCH-AlphaSet in p0-AlphaSets; for high priority cases, when the OLPC parameter set indication value in the OLPC field is "1" or "01", determine the value from the first value in P0-PUSCH-Set with the lowest p0-PUSCH-SetID value; for high priority cases, when the OLPC parameter set indication value in the OLPC field is "10", determine the value from the second value in P0-PUSCH-Set with the lowest p0-PUSCH-SetID value; otherwise, user equipment 102 may determine P O_UE_PUSCH,b,f,c (j).

[0064] Other parameters of the OLPC field may include:

[0065] p0-PUSCH-SetList-r16 SEQUENCE(SIZE(1..maxNrofSRI-PUSCH-Mappings)) OF P0-PUSCH-Set-r16 OPTIONAL, -- Need R

[0066] olpc-ParameterSet SEQUENCE {

[0067] olpc-ParameterSetDCI-0-1-r16 INTEGER(1..2) OPTIONAL, -- Need R

[0068] olpc-ParameterSetDCI-0-2-r16 INTEGER(1..2) OPTIONAL -- Need R

[0069] }

[0070] SRI-PUSCH-PowerControl ::= SEQUENCE {

[0071] sri-PUSCH-PowerControlId SRI-PUSCH-PowerControlId,

[0072] sri-PUSCH-PathlossReferenceRS-Id PUSCH-PathlossReferenceRS-Id,

[0073] sri-P0-PUSCH-AlphaSetId P0-PUSCH-AlphaSetId,

[0074] sri-PUSCH-ClosedLoopIndex ENUMERATED {i0, i1}

[0075] }

[0076] SRI-PUSCH-PowerControlId ::= INTEGER

[0077] (0..maxNrofSRI-PUSCH-Mappings - 1)

[0078] P0-PUSCH-AlphaSet ::= SEQUENCE {

[0079] p0-PUSCH-AlphaSetId P0-PUSCH-AlphaSetId,

[0080] p0 INTEGER (-16..15) OPTIONAL, -- Need S

[0081] alpha Alpha OPTIONAL -- Need S

[0082] …

[0083] }

[0084] P0-PUSCH-AlphaSetId ::= INTEGER

[0085] (0..maxNrofP0-PUSCH-AlphaSets - 1)

[0086] P0-PUSCH-Set-r16 ::= SEQUENCE {

[0087] p0-PUSCH-SetId-r16 P0-PUSCH-SetId-r16,

[0088] p0-List-r16 SEQUENCE(SIZE(1..maxNrofP0-PUSCH-Set-r16))OF P0-PUSCH-r16OPTIONAL,--Need R ...

[0090] }

[0091] P0-PUSCH-SetId-r16::=INTEGER(0..maxNrofSRI-PUSCH-Mappings-1)

[0092] P0-PUSCH-r16::=INTEGER(-16..15)

[0093] maxNrofSRI-PUSCH-Mappings=16;

[0094] maxNrofP0-PUSCH-AlphaSets=30;

[0095] maxNrofP0-PUSCH-Set-r16=2.

[0096] In addition, in some embodiments, in order to make different PUSCHs on co-scheduled cells scheduled by DCI format 0_X have the same PHY priority and / or the same OL TPC parameter set, the OLPC field can be determined or implemented according to one or more of the following schemes.

[0097] In the first scheme (Scheme 1), the field type of the OLPC field is the same as that of the SRI field. For example, if the SRI field is configured as type 1A, then the OLPC field is correspondingly also type 1A. As another example, if the SRI field is configured as type 2, then the OLPC field is correspondingly also type 2. By restricting the field type of the OLPC field to match that of the SRI field, the same OL TPC parameter set can be indicated, and / or the same PUSCH PHY priority can be obtained for different PUSCHs on co-scheduled scheduled cells.

[0098] In a second scenario (Scenario 2), for a cell indicated by an OLPC parameter set with 1 bit, the OLPC parameter set indication initially having a value of '10' with 2 bits can be re - parsed and / or represented as a value of '1' with 1 bit. In some embodiments, an LSB function can be applied to re - parse or represent the 2 - bit value as a 1 - bit value. In other embodiments, the LSB function may not be applied, and the 1 - bit value can be re - parsed or represented as a 2 - bit value.

[0099] More specifically, in some embodiments of Scenario 2, the OLPC field can be a type 1A field. For a configuration where the field size of the OLPC field for one of the co - scheduled cells is less than the determined field size of the OLPC field in DCI format 0_X for multi - cell scheduling, the LSB of the OLPC field can be applied to re - parse or represent the 2 - bit OLPC parameter set indication '01' as a 1 - bit value of '1' for a cell with an OLPC field size of 1 bit. Additionally or alternatively, in some embodiments of Scenario 2, when the OLPC parameter set indication value is '01', cell 1 can apply the first value in P0 - PUSCH - Set with the lowest p0 - PUSCH - SetID value, and cell 2 can also apply the first value in P0 - PUSCH - Set with the lowest p0 - PUSCH - SetID value. This may in turn result in different PUSCHs on multiple cells having the same priority operation, which can be regarded as a high - priority operation.

[0100] As an example of Scenario 2, assume that cell 1 and cell 2 are co - scheduled via DCI format 0_X. Further assume that the SRI field is a type 2 field. Additionally, assume that for cell 1, DCI format 0_1 does not contain the SRI field and is configured with an OLPC field of 2 - bit size. Moreover, assume that for cell 2, DCI format 0_1 contains the SRI field and is also configured with an OLPC field of 1 - bit size. If the field size of one of the co - scheduled cells is less than the determined field size in DCI format 0_X / 1_X, then for a cell with an OLPC field size of 1 bit, the 2 - bit OLPC parameter set indication value '10' can be re - parsed or represented as a 1 - bit value of '1' without applying the LSB function. Additionally or alternatively, in some embodiments of Scenario 2, when the OLPC parameter set indication value is '10', cell 1 can apply the second value in P0 - PUSCH - Set with the lowest p0 - PUSCH - SetID value, and cell 2 can apply the first value in P0 - PUSCH - Set with the lowest p0 - PUSCH - SetID value. This may in turn result in different PUSCHs on multiple cells having the same priority operation, which can be regarded as a high - priority operation.

[0101] In some embodiments of Scenario 2, when the OLPC parameter set indication value is '00', Cell 1 can apply the first P0-PUSCH-AlphaSet in p0-AlphaSets, and Cell 2 will also apply the first P0-PUSCH-AlphaSet in p0-AlphaSets. This may in turn cause different PUSCHs on multiple cells to have the same priority operation, which can be regarded as a low-priority operation.

[0102] In the third scenario (Scenario 3), the size of the OLPC field can be configured for each cell set. Additionally or alternatively, the second value with the lowest p0-PUSCH-SetID value in P0-PUSCH-Set can be configured for all cells within the cell set. Under this restriction, the same set of OL TPC parameters can be indicated, and / or the same PUSCH PHY priority can be implemented and / or maintained.

[0103] Thus, when DCI format 0_X / 1_X is configured for multi-cell scheduling, for the Type 1A field, when the field size used for one of the co-scheduled cells is smaller than the field size determined in DCI format 0_X / 1_X, an LSB operation can be performed to re-parse or represent the 2-bit OLPC parameter indication value '10' as the 1-bit value '1' of a cell with a 1-bit OLPC field size. This may ideally cause different PUSCHs on multiple cells to have the same priority operation.

[0104] Embodiment 3

[0105] Additionally or alternatively, for DCI format 1_X / 0_X used for scheduling more than one cell (i.e., for multi-cell scheduling), the redundancy version RV field configured per transport block (TB) can be a Type 2 field. For DCI format 0_X / 1_X, the size of the RV field can be configured per cell per BWP.

[0106] For embodiments where the size of the RV field is one bit, one or more RV tables can be used to determine one or more RV values. For such embodiments, the RV table can associate each of the one-bit RV field values with an associated RV value. That is, in each table, the one-bit RV field value '0' can be associated with and / or indicate the first value, and the one-bit RV field value '1' can be associated with and / or indicate the second value. Two example tables are provided below.

[0107] Table 2: First example of a 1-bit redundancy version table

[0108]

[0109] Table 3: Second example of the redundancy version table for 1 bit

[0110] Value of the redundancy version field <![CDATA[rv of the application id value]]> 0 0 1 3

[0111] As shown in Table 2, the RV field value '0' is associated with and / or indicates the RV value 0, and the RV field value '1' is associated with and / or indicates the RV value 2. As shown in Table 3, the RV field value '0' is associated with and / or indicates the RV value 0, and the RV field value '1' is associated with and / or indicates the RV value 3. In some embodiments, the user equipment 102 and / or the network equipment 104 may be configured to use at least one of the tables to determine the RV value based on the RV field value in the RV field of the DCI format 0_X / 1_X, and / or determine how to indicate the RV value with the RV field value in the RV field of the DCI format 0_X / 1_X.

[0112] Next, the RVs in the DCI formats 0_1, 1_1, 0_2, and 1_2 are described.

[0113] For the DCI formats 0_1 and 1_1, the number of bits of the RV field value (the size of the RV field) can be determined as follows. If the number of scheduled PDSCHs indicated by the time domain resource allocation field is 1, the RV field value (or the size of the RV field) can be 2 bits, such as defined in Table 4. Otherwise, the RV field value (or the size of the RV field) can be 2, 3, 4, 5, 6, 7, or 8 bits determined by the maximum number of schedulable PDSCHs in all entries of the higher layer parameter pdsch-TimeDomainResourceAllocationListForMultiPDSCH, where each bit corresponds to a scheduled PDSCH, and the RV value can be determined according to a predetermined table (such as Table 2 above).

[0114] Table 4: Redundancy version

[0115]

[0116]

[0117] For the DCI formats 0_2 and 1_2, the RV field value can be 0, 1, or 2 bits, as determined by the higher layer parameter pumberOfBitsForRV-DCI-1-2. In some embodiments, in the case where the RV field value (or the size of the RV field) is 0 bits, the RV value (rv id) is 0. Additionally or alternatively, when the RV field value (or the size of the RV field) is 1 bit, the RV value can be determined according to Table 3 above. Additionally or alternatively, when the RV field value (or the size of the RV field) is 2 bits, the RV value can be determined according to a table (such as Table 4) that associates the 2-bit RV field value with the RV value.

[0118] In addition, in some embodiments, an RV table that associates RV field values with RV values 0 and 3 (also referred to as RV0 / 3 in the present disclosure) can be used for Ultra Reliable and Low Latency Communication (URLLC), which can be regarded as being used for high-priority PDSCH and / or PUSCH transmissions. Additionally, in some embodiments, an RV table that associates RV field values with RV values 0 and 2 (also referred to as RV0 / 2 here) can be used for enhanced mobile broadband eMBB or new unlicensed (licensed) radio NR-U, which can be regarded as being used for low-priority PDSCH and / or PUSCH transmissions.

[0119] In addition, in some embodiments, since the size of the RV field for DCI format 0_X / 1_X can be configured per BWP per cell, if the RV field size is 1 bit, the RV table used to determine and / or indicate the RV value can be determined according to one or more of the following schemes.

[0120] In the first scheme (Scheme 1), if the RV field size is 1 bit (or the RV field value is a 1-bit value), the corresponding RV table used is also configured per BWP per cell or per cell. That is, for DCI format 0_X / 1_X, the size of the RV field can be configured per BWP per cell, and the corresponding RV table can also be configured per BWP per cell or per cell. When implementing Scheme 1, different 1-bit RV tables can be configured for different cells within the cell set.

[0121] In the second scheme (Scheme 2), if the RV field size is 1 bit (or the RV field value is a 1-bit value), the corresponding RV table used is also configured per cell set. That is, for DCI format 0_X / 1_X, the size of the RV field can be configured per BWP per cell, and the corresponding RV table can also be configured, but per cell set. When implementing Scheme 2, the same 1-bit RV table can be configured for different cells within the cell set. Moreover, in some embodiments, the 1-bit RV table may only be used for cells configured with a 1-bit RV field size.

[0122] In a third scheme (Scheme 3), if the size of the RV field is one bit (or the RV field value is a value of one bit), the corresponding RV table is predefined. That is, for DCI format 0_X / 1_X, the size of the RV field can be configured per BWP per cell, and the corresponding 1-bit RV table is predefined, either RV0 / 2 (Table 2) or RV0 / 3 (Table 3). When implementing Scheme 3, the same 1-bit RV table can be configured for different cells within the cell set. Moreover, in some embodiments, the 1-bit RV table may be used only for cells configured with an RV field size of one bit.

[0123] Thus, when DCI format 0_X / 1_X is configured and for type 2 fields with reduced field size, the 1-bit RV table for indicating or determining the RV value can be determined using the default RV table, or can include one of two candidate tables per BWP per cell or per cell or per cell set. This may in turn enable the user equipment 102 and the network device 104 to have the same understanding regarding the RV value and its indication manner in DCI format 0_X / 1_X, which may in turn provide greater flexibility in scheduling, determining, and / or performing PDSCH / PUSCH retransmissions.

[0124] Embodiment 4

[0125] For a type 1B field, the size of the type 1B field in DCI format 0_X / 1_X is equal to the upper limit value (log2(N)), where N is the number of rows in the RRC configuration table, and each row contains multiple indices for all cells within the cell set. The type 1B field indicates a row in the configuration table. The type 1B index of a cell points to the corresponding index in the RRC configuration table, which is applicable to the values of DCI format 0_1 / 1_1 or MAC CE activation.

[0126] Therefore, the type 1B table should be configured. The detailed configuration includes at least one of the following schemes.

[0127] Scheme 1: The table is explicitly configured in the cell set-level configuration. Optionally, the table should also be BWP-specific. To reduce RRC signaling overhead, it needs to be configured by adding and releasing a list, and each element in the list corresponds to a BWP combination. Additionally, downlink scheduling and uplink scheduling should be configured separately. Since the BWP indicator in DCI is a type 1A field, there are at most 4 active BWP combinations. The maximum number of elements in the list should also be 4. The first element is used for the configuration of the first active BWP combination, the second element in the list is used for the configuration of the second active BWP combination, and so on.

[0128] The downlink scheduling configuration of DCI format 1_X mainly includes the configuration of type 1B fields in DCI format 1_X. For example, an index can be configured to identify the downlink scheduling set upon release. For another embodiment, for the time-domain resources of PDSCH, a table with a maximum of 16 rows can be configured. Each row includes the specific time-domain resources of PDSCH for each scheduled cell in the set. Among them, the specific time-domain resources of the scheduled cell are indicated by an index, and this index points to the time-domain resources of PDSCH according to the traditional configuration of DCI format 1_1 in the corresponding BWP. Since multi-cell scheduling and multi-PDSCH scheduling cannot be configured for the PUCCH group simultaneously, the value range of this index can be 0 - 15. For another embodiment, a table with a maximum of 16 rows can be configured for the rate matching mode indicator. For each row, the value range of the index of the scheduled cell should be 0 - 3. For another embodiment, a table with a maximum of 8 rows can be configured for the ZP CSI-RS trigger indication. For each row, the value range of the index of the scheduled cell should be 0 - 3. For another embodiment, a table with a maximum of 16 rows can be configured for the TCI state indication. For each row, the value range of the index of the scheduled cell should be 0 - 8. The index points to the TCI state activated by the MAC CE of the scheduled cell in the corresponding BWP. For another embodiment, a table with a maximum of 16 rows can be configured for the SRS request indication. For each row, the value range of the index of the scheduled cell should be 0 - 3. For another embodiment, a table with a maximum of 8 rows can be configured for the SRS offset indicator. For each row, the value range of the index of the scheduled cell should be 0 - 3.

[0129] The uplink scheduling configuration of DCI format 0_X mainly includes the configuration of type 1B fields in DCI format 0_X. For example, an index can be configured to identify the uplink scheduling set upon release. For another embodiment, a table with a maximum of 64 rows can be configured for the time-domain resource indication of PUSCH. For each row, since up to 6-bit TDRA tables can be repeatedly configured for PUSCH, the value range of the index of the scheduled cell should be 0 - 63. For another embodiment, a table with a maximum of 16 rows can be configured for the SRS request indication. For each row, the value range of the index of the scheduled cell should be 0 - 3. For another embodiment, a table with a maximum of 8 rows can be configured for the SRS offset indicator. For each row, the value range of the index of the scheduled cell should be 0 - 3.

[0130] The following are the embodiments of the RRC configuration of Scenario 1 that can be listed.

[0131]

[0132]

[0133]

[0134]

[0135] Solution 2: The table is explicitly configured in the configuration at each cell level. Optionally, the table should also be BWP-specific. In the usual way, downlink scheduling and uplink scheduling should be configured separately. Since the BWP indicator in DCI is a type 1A field, there are at most 4 active BWP combinations. When the number of BWPs in each cell within the cell set is the same, for a type 1B field, the columns of the table will be configured in each BWP of each cell.

[0136] For example, the PDSCH TimeDomainResourceAllocation in the following one BWP will be added to a column of the type 1B indication table for multi-cell scheduling. Note that the actual number of rows of each table is independently configured for different BWPs and is not greater than maxNrofDL-Allocation-r18. For example, 8 rows, 8 rows, 16 rows, 16 rows for each table.

[0137]

[0138]

[0139] While the number of BWPs in each cell within the cell set may be different. In this case, the rows of a column of a cell with a smaller number of BWPs can be merged with multiple BWPs of other cells with a larger number of BWPs. For example, cell #1 is configured with two BWPs, and cells #2, 3, 4 are configured with four BWPs. When BWP#1 in cell #1 is merged with BWP#1 and BWP#3 in cells #2 / 3 / 4, BWP#2 in cell #1 is merged with BWP#2 and BWP#4 in cells #2 / 3 / 4, and the behavior of TDRA in cells #2 / 3 / 4 in BWP#1 / 2 / 3 / 4 is 8 rows, 8 rows, 16 rows, 16 rows, the TDRA of type 1B for the cell set of each BWP also has 8 rows, 8 rows, 16 rows, 16 rows. Then, for cell #1 with two BWPs, the configuration of the columns in the table is determined by one of the following methods.

[0140] Method 1: Configure two different columns for different associated BWPs. That is, for one BWP of cell #1, two columns of two tables will be configured. Based on the above embodiments, two columns with 8 rows and 16 rows are configured. Optionally, the BWP Id can be configured in at least one of the two columns of the two tables.

[0141]

[0142]

[0143] Method 2: Configure a column with the maximum number of rows being the different associated BWPs. That is, for a BWP of cell #1, configure a column with the maximum number of rows being the number of rows in the two tables. According to the above embodiments, configure a column with the number of rows being the maximum value {8, 16} = 16 rows. And when the number of rows of the associated BWP is small, only the rows where the LSB is located will be used. That is, when associated with BWP#1, only rows #0 - 7 will be used.

[0144]

[0145]

[0146] The above description and the accompanying drawings provide specific exemplary embodiments and implementations. However, the subject matter described can be embodied in various different forms, and thus, the subject matter covered or claimed is intended to be construed as not limited to any of the exemplary embodiments set forth herein. The subject matter claimed or covered is expected to have a reasonably broad scope. Among other things, for example, the subject matter can be implemented as a method, device, component, system, or non - volatile computer - readable medium for storing computer code. Thus, the embodiments can take, for example, the form of hardware, software, firmware, storage media, or any combination thereof. For example, the method embodiments described above can be implemented by a component, device, or system including a memory and a processor by executing computer code stored in the memory.

[0147] Throughout the specification and the claims, some terms may have nuanced meanings that are implied or implicit in the context in addition to their explicitly stated meanings. Similarly, the phrase "in one embodiment / implementation" as used in this disclosure does not necessarily refer to the same embodiment, and the phrase "in another embodiment / implementation" as used in this disclosure does not necessarily refer to a different embodiment. For example, the subject matter claimed is intended to include, in whole or in part, combinations of the exemplary embodiments.

[0148] In general, terms can be understood, at least in part, from their use in context. For example, terms such as "and", "or", or "and / or" as used in this disclosure may have multiple meanings, and these meanings depend, at least in part, on the context in which such terms are used. Typically, if "or" is used to relate a list, such as A, B, or C, it is intended to mean A, B, and C (used here in an inclusive sense), as well as A, B, or C (used here in an exclusive sense). Additionally, the term "one or more" as used in this disclosure depends, at least in part, on context and can be used to describe any feature, structure, or characteristic in a singular sense, or can be used to describe a combination of features, structures, or characteristics in a plural sense. Similarly, terms such as "a", "an", or "the" can be understood to convey either a singular use or a plural use, at least in part, depending on the context. Further, the term "based on" can be understood to not necessarily be intended to convey a set of exclusive factors and can instead allow for additional factors that are not necessarily explicitly described, again at least in part, based on the context.

[0149] Throughout this disclosure, references to features, advantages, or similar expressions do not mean that all features and advantages that may be achieved by the present disclosure should or are included in any single implementation. Instead, references to these features and advantages are to be understood as meaning that a particular feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present disclosure. Thus, discussions of features and advantages throughout the disclosure and similar expressions may, but do not necessarily, refer to the same embodiment.

[0150] Furthermore, the features, advantages, and characteristics described in this disclosure may be combined in any suitable manner in one or more embodiments. Those of ordinary skill in the relevant art will recognize, based on the description of this disclosure, that the present disclosure can also be implemented without one or more specific features or advantages of a particular embodiment. In other cases, additional features and advantages may be found in certain embodiments that may not be present in all embodiments of the present disclosure.

[0151] The subject matter of this disclosure may also relate to or include, among other things, the following aspects:

[0152] A first aspect includes a method for wireless communication, the method comprising: a network device determining a downlink control information DCI format for multi-cell scheduling transmission in a cell set, the determining including determining at least one size of at least one DCI field of the DCI format; and the network device transmitting a DCI having the DCI format for scheduling transmission for at least one cell in the cell set.

[0153] The second aspect includes a method for wireless communication, the method including: a user equipment receiving a radio resource control (RRC) configuration for determining a downlink control information (DCI) format for multi-cell scheduling transmission in a cell set, the determination including determining at least one size of at least one DCI field of the DCI format; and the user equipment receiving a DCI having the DCI format for scheduling transmission for at least one cell in the cell set.

[0154] The third aspect includes any one of the first aspect or the second aspect, and further includes: wherein, the DCI field of the DCI format is a single field indicating information for only one cell in co-scheduled cells, and the size of the DCI field is determined by one cell of the cell set.

[0155] The fourth aspect includes the third aspect, and further includes: wherein, one cell of the cell set is determined by a first cell having the largest DCI field size in the active bandwidth part (BWP) of a second cell having the smallest cell index in each subset corresponding to respective combinations of co-scheduled cells in the cell set.

[0156] The fifth aspect includes the third aspect, and further includes: wherein, one cell of the cell set is determined by a first cell having the largest DCI field size in the active bandwidth part (BWP) of all cells within the cell set.

[0157] The sixth aspect includes the third aspect, and further includes: wherein, when a table defining combinations of co-scheduled cells of the cell set is configured, one cell of the cell set is determined by a first cell having the largest first DCI field size in the first active bandwidth part (BWP) of a second cell having the smallest cell index in each subset of the cell set; and when the table is not configured, one cell of the cell set is determined by a third cell having the second largest DCI field size in the second active BWP of all cells within the cell set.

[0158] The seventh aspect includes any one of the first aspect to the sixth aspect, and further includes: wherein, the at least one DCI field includes an open-loop power control (OLPC) field, the field including a parameter set indication, the method further including: determining an OLPC parameter by determining a field type of the OLPC field of the DCI format to match a field type of a sounding reference signal resource indicator (SRI).

[0159] The eighth aspect includes any one of the first to sixth aspects, and further includes: wherein, at least one DCI field of the DCI format includes an open-loop power control (OLPC) field, the OLPC field includes a parameter set indication, at least one size includes the size of the OLPC field, and wherein the size of the OLPC field is determined as the maximum field size of the active bandwidth part (BWP) in all cells within the cell set. The method further includes: when the size of the OLPC field of a cell in the cell set is less than the determined size of the OLPC field in the DCI format, re-parsing the parameter set indication of the OLPC field of the cells in the cell set from a 2-bit value "10" to a 1-bit value "1".

[0160] The ninth aspect includes any one of the first to sixth aspects, and further includes: wherein, at least one DCI field includes an open-loop power control (OLPC) field, the open-loop power control field includes a parameter set indication, at least one size includes the size of the OLPC field, and wherein the size of the OPLC field is configured for each cell set.

[0161] The tenth aspect includes any one of the first to ninth aspects, and further includes: wherein, at least one DCI field includes a redundancy version (RV) field, at least one size includes the size of the RV field, wherein the size of the RV field is configurable, and wherein when a 1-bit RV field is configured, two RV values are determined by a default RV table or configured in one of two candidate RV tables for each bandwidth part (BWP), each cell, or each cell set.

[0162] The eleventh aspect includes a wireless communication device, the wireless communication device includes a processor and a memory, wherein the processor is configured to read code from the memory to implement any one of the first to tenth aspects.

[0163] The twelfth aspect includes a computer program product, the computer program product includes a computer-readable program medium, the computer-readable program medium includes code stored thereon, the code when executed by a processor causes the processor to implement any one of the first to tenth aspects.

[0164] In addition to the features mentioned in each of the aspects listed above, some embodiments may singly or in combination show optional features mentioned in the above aspects and / or as disclosed in the above description and shown in the drawings.

Claims

1. A method for wireless communication, the method comprises: A network device determines a downlink control information (DCI) format for multi-cell scheduling transmission in a cell set, including determining at least one size of at least one DCI field of the DCI format; The network device transmits a DCI with the DCI format to schedule the transmission for at least one cell in the cell set.

2. A method for wireless communication, the method comprises: A user equipment receives a radio resource control (RRC) configuration for determining a DCI format of multi-cell scheduling transmission in a cell set, including determining at least one size of at least one DCI field of the DCI format; The user equipment receives a DCI with the DCI format to schedule the transmission for at least one cell in the cell set.

3. The method according to claim 1 or 2, wherein, The DCI field of the DCI format is a single field for indicating information for one cell in co-scheduled cells, and the size of the DCI field is determined by one cell of the cell set.

4. The method according to claim 3, wherein, One cell of the cell set is determined by a first cell having the largest DCI field size in the activated bandwidth part (BWP) of a second cell having the smallest cell index in each subset of the cell set, where each subset corresponds to a respective combination of co-scheduled cells in the cell set.

5. The method according to claim 3, wherein, One cell of the cell set is determined by a first cell having the largest DCI field size in the activated BWP of all cells within the cell set.

6. The method according to claim 3, wherein, When a table defining the combination of co-scheduled cells of the cell set is configured, one cell of the cell set is determined by a first cell having the largest first DCI field size in the first activated BWP of a second cell having the smallest cell index in each subset of the cell set; And when the table is not configured, one cell of the cell set is determined by a third cell having the second largest DCI field size in the second activated BWP of all cells within the cell set.

7. The method according to claim 1 or 2, wherein, The at least one DCI field includes an open-loop power control (OLPC) field, the field includes a parameter set indication, and the method further includes: determining OLPC parameters by determining the field type of the OLPC field of the DCI format to match the field type of a sounding reference signal resource indicator (SRI).

8. The method according to claim 1 or 2, wherein, At least one DCI field of the DCI format includes an OLPC field, the OLPC field includes a parameter set indication, wherein the at least one size includes the size of the OLPC field, and the size of the OLPC field is determined as the largest field size of the activated BWP of all cells within the cell set, and the method further includes: When the size of the OLPC field of a cell in the cell set is smaller than the determined size of the OLPC field in the DCI format, the parameter set indication of the OLPC field of the cell in the cell set is re-parsed from the 2-bit value "10" to the 1-bit value "1".

9. The method according to claim 1 or 2, wherein, the at least one DCI field includes an open-loop power control OLPC field, the OLPC field contains a parameter set indication, the at least one size includes the size of the OLPC field, wherein the size of the OPLC field is configured for each cell set.

10. The method according to claim 1 or 2, wherein, the at least one DCI field includes a redundancy version RV field, wherein the at least one size includes the size of the RV field, wherein the size of the RV field is configurable, and when a 1-bit RV field is configured, two RV values are determined by a default RV table, or are configured in one of two candidate RV tables for each bandwidth part BWP, each cell, or each cell set.

11. A wireless communication device, comprising a processor and a memory, wherein, the processor is configured to read code from the memory to perform the method according to any one of claims 1 to 10.

12. A computer program product, comprising a computer-readable program medium, the computer-readable program medium includes code stored thereon, the code when executed by a processor causes the processor to perform the method according to any one of claims 1 to 10.

Images