WO2024113605A1 - Détermination de format de dci pour une planification multicellulaire pour des communications sans fil - Google Patents

Détermination de format de dci pour une planification multicellulaire pour des communications sans fil Download PDF

Info

Publication number
WO2024113605A1
WO2024113605A1 PCT/CN2023/087108 CN2023087108W WO2024113605A1 WO 2024113605 A1 WO2024113605 A1 WO 2024113605A1 CN 2023087108 W CN2023087108 W CN 2023087108W WO 2024113605 A1 WO2024113605 A1 WO 2024113605A1
Authority
WO
WIPO (PCT)
Prior art keywords
field
cells
cell
dci
size
Prior art date
Application number
PCT/CN2023/087108
Other languages
English (en)
Inventor
Jing Shi
Shuaihua KOU
Xianghui HAN
Original Assignee
Zte Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Zte Corporation filed Critical Zte Corporation
Priority to PCT/CN2023/087108 priority Critical patent/WO2024113605A1/fr
Publication of WO2024113605A1 publication Critical patent/WO2024113605A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/232—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows

Definitions

  • This document is directed generally to scheduling information determination for wireless communications.
  • 4G and 5G systems are developing support on features of enhanced mobile broadband (eMBB) , ultra-reliable low-latency communication (URLLC) , and massive machine-type communication (mMTC) .
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable low-latency communication
  • mMTC massive machine-type communication
  • carrier aggregation (CA) can be used in 4G, 5G, and further communication systems.
  • the scheduling mechanism only allows scheduling a physical uplink shared channel (PUSCH) transmission or a physical downlink shared channel (PDSCH) transmission in a single cell per a scheduling downlink control information (DCI) .
  • PUSCH physical uplink shared channel
  • PDSCH physical downlink shared channel
  • DCI scheduling downlink control information
  • the need to simultaneously schedule PUSCH/PDSCH transmissions in multiple cells is expected to increase.
  • Extending from single-cell scheduling to multi-cell PUSCH/PDSCH scheduling with a single scheduling DCI may desirably reduce control overhead.
  • formatting or other configuration issues when using a single scheduling DCI for multiple cells may arise. Ways to overcome such issues may be desirable.
  • a method for wireless communication includes: determining, by a network device, a downlink control information (DCI) format for multi-cell scheduling transmissions in a set of cells, the determining comprising determining at least one size of at least one DCI field of the DCI format; and transmitting, by the network device, a DCI having the DCI format to schedule the transmissions for at least one of the cells of the set of cells.
  • DCI downlink control information
  • a method for wireless communication that includes: receiving, by a user device, a radio resource control (RRC) configuration for determining a downlink control information (DCI) format for multi-cell scheduling transmissions in a set of cells, the determining comprising determining at least one size of at least one DCI field of the DCI format; and receiving, by the user device, a DCI having the DCI format to schedule the transmissions for at least one of the cells of the set of cells.
  • RRC radio resource control
  • a device such as a network device.
  • 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 methods above.
  • a computer program product may include a non-transitory computer-readable program medium with computer code stored thereupon, the computer code, when executed by one or more processors, causing the one or more processors to implement any of the methods above.
  • FIG. 1 shows a block diagram of an example of a wireless communication system.
  • FIG. 2 shows a diagram of an example of multi-cell scheduling.
  • FIG. 3 shows a flow chart of a method for wireless communication.
  • FIG. 4 shows a flow chart of a method for wireless communication.
  • the present description describes various embodiments of systems, apparatuses, devices, and methods for wireless communications related to scheduling information determination for wireless communications.
  • Fig. 1 shows a diagram of an example wireless communication system 100 including a plurality of communication nodes (or just nodes) that are configured to wirelessly communicate with each other.
  • the communication nodes include at least one user device 102 and at least one network device 104.
  • the example wireless communication system 100 in Fig. 1 is shown as including two user devices 102, including a first user device 102 (1) and a second user device 102 (2) , and one device 104.
  • various other examples of the wireless communication system 100 that include any of various combinations of one or more user devices 102 and/or one or more network devices 104 may be possible.
  • a user device as described herein such as the user device 102, may include a single electronic device or apparatus, or multiple (e.g., a network of) electronic devices or apparatuses, capable of communicating wirelessly over a network.
  • a user device may comprise or otherwise be referred to as a user terminal, a user terminal device, or a user equipment (UE) .
  • UE user equipment
  • a user device may be or include, but not limited to, a mobile device (such as a mobile phone, a smart phone, a smart watch, a tablet, a laptop computer, vehicle or other vessel (human, motor, or engine-powered, such as an automobile, a plane, a train, a ship, or a bicycle as non-limiting examples) or a fixed or stationary device, (such as a desktop computer or other computing device that is not ordinarily moved for long periods of time, such as appliances, other relatively heavy devices including Internet of things (IoT) , or computing devices used in commercial or industrial environments, as non-limiting examples) .
  • a mobile device such as a mobile phone, a smart phone, a smart watch, a tablet, a laptop computer, vehicle or other vessel (human, motor, or engine-powered, such as an automobile, a plane, a train, a ship, or a bicycle as non-limiting examples) or a fixed or stationary device, (such as a desktop computer or other computing device that is not ordinarily moved
  • a user device 102 may include transceiver circuitry 106 coupled to an antenna 108 to effect wireless communication with the network device 104.
  • the transceiver circuitry 106 may also be coupled to a processor 110, which may also be coupled to a memory 112 or other storage device.
  • the memory 112 may store therein instructions or code that, when read and executed by the processor 110, cause the processor 110 to implement various ones of the methods described herein.
  • a network device as described herein such as the network device 104, may include a single electronic device or apparatus, or multiple (e.g., a network of) electronic devices or apparatuses, and may comprise one or more wireless access nodes, base stations, or other wireless network access points capable of communicating wirelessly over a network with one or more user devices and/or with one or more other network devices 104.
  • the network device 104 may comprise 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 or next-generation (e.g., 6G) base stations, in various embodiments.
  • a network device 104 may include transceiver circuitry 114 coupled to an antenna 116, which may include an antenna tower 118 in various approaches, to effect wireless communication with the user device 102 or another network device 104.
  • the transceiver circuitry 114 may also be coupled to one or more processors 120, which may also be coupled to a memory 122 or other storage device.
  • the memory 122 may store therein instructions or code that, when read and executed by the processor 120, cause the processor 120 to implement one or more of the methods described herein.
  • two communication nodes in the wireless 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 or over a mobile network and/or a wireless access network according to one or more standards and/or specifications.
  • the standards and/or specifications may define the rules or procedures under which the communication nodes can wirelessly communicate, which, in various embodiments, may include those for communicating in millimeter (mm) -Wave bands, and/or with multi-antenna schemes and beamforming functions.
  • the standards and/or specifications are those that define a radio access technology and/or a cellular technology, such as Fourth Generation (4G) Long Term Evolution (LTE) , Fifth Generation (5G) New Radio (NR) , or New Radio Unlicensed (NR-U) , as non-limiting examples.
  • 4G Fourth Generation
  • LTE Long Term Evolution
  • 5G Fifth Generation
  • NR New Radio
  • NR-U New Radio Unlicensed
  • the communication nodes are configured to wirelessly communicate signals between each other.
  • a communication in the wireless system 100 between two communication nodes can be or include a transmission or a reception, and is generally both simultaneously, depending on the perspective of a particular node in the communication.
  • the first node may be referred to as a source or transmitting node or device
  • the second node may be referred to as a destination or receiving node or device
  • the communication may be considered a transmission for the first node and a reception for the second node.
  • a single communication node may be both a transmitting/source node and a receiving/destination node simultaneously or switch between being a source/transmitting node and a destination/receiving node.
  • particular signals can be characterized or defined as either an uplink (UL) signal, a downlink (DL) signal, or a sidelink (SL) signal.
  • An uplink signal is a signal transmitted from a user device 102 to a network device 104.
  • a downlink signal is a signal transmitted from a network device 104 to a user device 102.
  • a sidelink signal is a signal transmitted from a one user device 102 to another user device 102, or a signal transmitted from one network device 104 to a another network device 104.
  • a first/source user device 102 directly transmits a sidelink signal to a second/destination user device 102 without any forwarding of the sidelink signal to a network device 104.
  • signals communicated between communication nodes in the system 100 may be characterized or defined as a data signal or a control signal.
  • a data signal is a signal that includes or carries data, such multimedia data (e.g., voice and/or image data)
  • a control signal is a signal that carries control information that configures the communication nodes in certain ways in order to communicate with each other, or otherwise controls how the communication nodes communicate data signals with each other.
  • certain signals may be defined or characterized by combinations of data/control and uplink/downlink/sidelink, including uplink control signals, uplink data signals, downlink control signals, downlink data signals, sidelink control signals, and sidelink data signals.
  • a physical channel corresponds to a set of time-frequency resources used for transmission of a signal.
  • Different types of physical channels may be used to transmit different types of signals.
  • physical data channels (or just data channels) , also herein called traffic channels, are used to transmit data signals
  • physical control channels (or just control channels) are used to transmit control signals.
  • Example types of traffic channels include, but are not limited to, a physical downlink shared channel (PDSCH) used to communicate downlink data signals, a physical uplink shared channel (PUSCH) used to communicate uplink data signals, and a physical sidelink shared channel (PSSCH) used to communicate sidelink data signals.
  • PDSCH physical downlink shared channel
  • PUSCH physical uplink shared channel
  • PSSCH physical sidelink shared channel
  • example types of physical control channels include, but are not limited to, a physical downlink control channel (PDCCH) used to communicate downlink control signals, a physical uplink control channel (PUCCH) used to communicate uplink control signals, and a physical sidelink control channel (PSCCH) used to communicate sidelink control signals.
  • a particular type of physical channel is also used to refer to a signal that is transmitted on that particular type of physical channel, and/or a transmission on that particular type of transmission.
  • a PDSCH refers to the physical downlink shared channel itself, a downlink data signal transmitted on the PDSCH, or a downlink data transmission.
  • a communication node transmitting or receiving a PDSCH means that the communication node is transmitting or receiving a signal on a PDSCH.
  • a control signal that a communication node transmits may include control information comprising the information necessary to enable transmission of one or more data signals between communication nodes, and/or to schedule one or more data channels (or one or more transmissions on data channels) .
  • control information may include the information necessary for proper reception, decoding, and demodulation of a data signals received on physical data channels during a data transmission, and/or for uplink scheduling grants that inform the user device about the resources and transport format to use for uplink data transmissions.
  • the control information includes downlink control information (DCI) that is transmitted in the downlink direction from a network device 104 to a user device 102.
  • DCI downlink control information
  • control information includes uplink control information (UCI) that is transmitted in the uplink direction from a user device 102 to a network device 104, or sidelink control information (SCI) that is transmitted in the sidelink direction from one user device 102 (1) to another user device 102(2) .
  • UCI uplink control information
  • SCI sidelink control information
  • the scheduling processes used by the communication nodes in the wireless communication system may only schedule a PUSCH or PDSCH transmission in a single cell per one scheduling DCI.
  • a PUSCH or PDSCH transmission may be simultaneously scheduled in multiple cells (called multi-cell scheduling) using a single scheduling DCI, .
  • multi-cell scheduling Using only a single scheduling DCI for multi-cell scheduling a PUSCH or PDSCH transmission may desirably reduce control overhead.
  • multi-cell scheduling for a set of cells may be performed with a single scheduling DCI having a DCI format 0_X or a DCI format 1_X, where X is an integer.
  • a DCI format that is a DCI format 0_X or a DCI format 1_X is referred to as DCI 0_X/1_X.
  • a DCI size of a DCI format 0_X/1_X is counted on one cell among the set of cells
  • blind decoding (BD) /control channel element (CCE) of DCI format 0_X/1_X is counted on one cell among the set of cells
  • CCE control channel element
  • a search space of DCI format 0_X/1_X is configured on one cell of the set of cells and associated with the search space of the scheduling cell with the same search space identifier (ID) .
  • each field in the DCI format 0_X/1_X may have an associated field type.
  • each field type may be one of following types: Type-1A, Type-1B, Type-1C, or Type 2.
  • a field having a Type-1A field type is a single field that indicates common information to all co-scheduled cells.
  • a field having a Type-1B field type is a single field indicating separate information to each cell of the co-scheduled cells via joint indication,
  • a field having a Type-1C field is a single field that indicates information to only one of the co-scheduled cells.
  • a field having a Type-2 field type is a field that is separate or unique field for each cell of the co-scheduled cells.
  • the size of a Type-1A field in the DCI format 0_X/1_X is determined as a maximum field size of an active bandwidth part (BWP) among all cells within the set of cells.
  • BWP active bandwidth part
  • the field size of a DCI format for one cell of a set of co-scheduled cells may be smaller than a determined field size for a Type 1A field in the DCI format 0_X/1_X used for the multi-cell scheduling, which creates an inconsistency between DCI formats for one cell of a set of cells and for multi-cell scheduling for co-scheduled cells of the set of cells.
  • the present description describes ways to address this inconsistency.
  • the present description also describes ways to determine the size of a Type-1C field in the DCI format 0_X/1_X.
  • Fig. 2 shows a diagram of an example of multi-cell scheduling.
  • a scheduled cell can be only configured with one scheduling cell and a single multi-cell scheduling DCI (MC-DCI) having DCI format 0_X/1_X, which may be carried by a PDCCH, can be used to schedule multiple PxSCH on multiple cells, with each PxSCH on one cell, and where PxSCH can be PDSCH or PUSCH.
  • MC-DCI and/or SC-DCI single cell scheduling DCI, that is legacy DCI format, e.g. DCI format 0_1/1_1 can be supported on the scheduling cell for a scheduled cell, and the MC-DCI has a DCI format 0_X/1_X.
  • the DCI size and/or BD/CCE of a PDCCH carrying the multi-cell scheduling DCI may be counted on one cell among the set of cells.
  • Blind decode may correspond to the Maximum number of monitored PDCCH candidates per slot/span for a DL BWP with subcarrier spacing (SCS) configuration ⁇ ⁇ 0, 1, 2, 3 ⁇ for a single serving cell.
  • control channel element may correspond to the Maximum number of non-overlapped CCEs per slot/span for a DL BWP with SCS configuration ⁇ ⁇ 0, 1, 2, 3 ⁇ for a single serving cell.
  • the size of a Type-1B field in the DCI format 0_X/1_X may be equal to ceiling (log2 (N) ) , where N is the number of rows in a radio resource control (RRC) -configured table, with each row including multiple indexes for all cells within the set of cells.
  • the Type-1B field may indicate one row of the configured table.
  • a Type-1B index for a cell may point to a corresponding index in a RRC configured table applicable for DCI format 0_1/1_1 or medium access control (MAC) control element (CE) activated values.
  • the size of a per cell Type-2 field in the DCI format 0_X/1_X may be determined based on the active BWP for each cell.
  • Fig. 3 shows a flow chart of an example method 300 of wireless communication that involves DCI formats for multi-cell scheduling transmissions.
  • a network device 104 may determine a DCI format for multi-cell scheduling transmissions 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.
  • the network device 104 may transmit a DCI having the DCI format to schedule the transmissions for at least one of the cells of the set of cells.
  • Fig. 4 shows a flow chart of another example method 400 of wireless communication that involves DCI formats for multi-cell scheduling transmissions.
  • a user device 102 may receive a radio resource control (RRC) configuration for determining a DCI format for multi-cell scheduling transmissions 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.
  • the user device 102 may receive a DCI having the DCI format to schedule the transmissions for at least one of the cells of the set of cells.
  • RRC radio resource control
  • a DCI field of the DCI format is a single field indicating an information to only one of co-scheduled cells, and a size of the DCI field is determined by one cell of the set of cells.
  • the one cell of the set of cells is determined by a first cell with a maximum size of the DCI field in an active bandwidth part (BWP) of a second cell with a smallest cell index in each subset of the set of cells, where each subset is for a respective combination of co-scheduled cells of the set of cells.
  • BWP active bandwidth part
  • the one cell of the set of cells is determined by a first cell with a maximum size of the DCI field in an active bandwidth part (BWP) among all cells within the set of cells.
  • the one cell of the set of cells is determined by a first cell with a first maximum size of the DCI field in a first active bandwidth part (BWP) of a second cell with a smallest cell index in each subset of the set of cells when a table defining combinations of co- scheduled cells for the set of cells is configured, and the one cell of the set of cells is determined by a third cell with a second maximum size of the DCI field in a second active BWP among all cells within the set of cells when the table is not configured.
  • any two of the first, second, and third cells may be the same as or different than each other.
  • At least one DCI field includes an Open-loop power control (OLPC) field that comprises a parameter set indication.
  • OLPC Open-loop power control
  • the OLPC parameter set indication may be determined by determining a field type of the OLPC field for the DCI format to match a field type of a sounding reference signal resource indicator (SRI) .
  • SRI sounding reference signal resource indicator
  • At least one DCI field includes an Open-loop power control (OLPC) field comprising a parameter set indication, and a size of the OLPC field is determined as a maximum field size of an active bandwidth part (BWP) among all cells within the set of cells.
  • the parameter set indication of the OLPC field may be reinterpreted from a 2-bit with “10” value to a 1-bit with “1” value for a cell of the set of cells when an OLPC field size for the cell of the set of cells is smaller than the determined size of the OLPC field in the DCI format.
  • the user device 102 may not use the single 1-bit with ‘0’ value (e.g., the least significant bit (LSB) ) , and instead may represent, translate, or otherwise use only the single 1-bit with ‘1’ value for the parameter set indication in the OLPC field for the cell that uses only one bit for OLPC field size.
  • ‘0’ value e.g., the least significant bit (LSB)
  • LSB least significant bit
  • a DCI field includes an Open-loop power control (OLPC) field comprising a parameter set indication, and a of the OLPC field is configured per set of cells.
  • OLPC Open-loop power control
  • a DCI field includes a redundancy version (RV) field
  • RV redundancy version
  • a size of the RV field is configurable, where when one 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 per bandwidth part (BWP) , per cell, or per set of cells.
  • BWP bandwidth part
  • type 1A, 1B, 2 For DCI format 0_X/1_X, size determination of type 1A, 1B, 2 had be agreed. Besides the remaining issue of type-1A, the type-1C field size determination should be resolved.
  • a Type-1C field is a single field indicating an information to only one cell of co-scheduled cells.
  • the size of a Type-1C field is determined by the indicated cell of co-scheduled cells. For such embodiments, the DCI format 0_X/1_X will have a variable size. In some situations, it may be desirable to avoid having variable size.
  • Some embodiments for determining a Type-1C field size may leverage a channel state information (CSI) request, for example.
  • CSI channel state information
  • a size of CSI request field for cell numbers 1, 2, 3, 4 are 2 bits, 3 bits, 6 bits, 4 bits respectively.
  • co-scheduled cells include cell numbers 1, 2, and 3.
  • the Type-1C field size is 2 bits.
  • co-scheduled cells include cell numbers 2, 3, and 4.
  • the size of the CSI request is derived from the configuration on cell number 2
  • the Type-1C field size 3 bits For example, suppose co-scheduled cells include cell numbers 2, 3, and 4.
  • leveraging the size of the CSI field request may lead to different sizes of the Type-1C field field for DCI format 0_X, which may create problems since the user device 102 may be configured to monitor a DCI format with a same size in an active bandwidth part (BWP) .
  • BWP active bandwidth part
  • the Type-1C field may include at least a CSI request and/or an uplink shared channel (UL-SCH) indicator.
  • a CSI request may include 0, 1, 2, 3, 4, 5, or 6 bits, and may be determined by a higher layer parameter reportTriggerSize.
  • a CSI request in DCI format 0_X may belongs to a Type-1C field. This Type-1C field is applied to a cell with a smallest serving cell index among the co-scheduled cells.
  • an UL-SCH indicator may be have a “0” bit value or a “1” bit value as follows.
  • the UL-SCH indicator may have a 0 bit value when the number of scheduled PUSCH indicated by a time domain resource assignment field is larger than 1.
  • the UL-SCH indicator may otherwise have a “1” bit value.
  • a value of "1” indicates that the UL-SCH may be transmitted on the PUSCH and a value of "0" indicates that the UL-SCH may not be transmitted on the PUSCH.
  • a user device 102 may not be expected to receive a DCI format 0_1 with a UL-SCH indicator of "0" and a CSI request of all zero (s) .
  • a user device 102 may not be expected to receive a DCI format 0_1 with UL-SCH indicator of "0" , a CSI request of all zero (s) , and a SRS request of all zero (s) .
  • a UL-SCH indicator in DCI format 0_X may belong to the Type-1C field.
  • the Type-1C field may be applied to the cell with the smallest serving cell index among the co-scheduled cells.
  • the size of the Type 1C field in the DCI format 0_X/1_X is may determined by one of the following schemes.
  • a Type-1C field in the DCI format 0_X/1_X for a set of cells is determined as a maximum field size of an active bandwidth parts (BWP) among cells with a smallest serving cell index within each combination of co-scheduled cells for the set of cells.
  • BWP active bandwidth parts
  • Table 1 Combinations of co-scheduled cells for a set of cells (cell numbers 0, 1, 2, 3)
  • a size of a CSI request for cell numbers 0, 1, 2, 3 is 2, 3, 4, 5 bits, respectively.
  • the smallest serving cell index within each combination of co-scheduled cells for the set of cells are cell#0 for three combinations of co-scheduled cells and cell#1 for one combination of co-scheduled cells
  • the size of a Type-1C field in the DCI format 0_X/1_X for a set of cells is determined as the maximum field size of an active BWP among all cell within the set of cells.
  • Table 1 may be used or configured to derive the combinations of co-scheduled cells for the set of cells (cell numbers 0, 1, 2, 3) .
  • Scheme 3 if table defining combinations of co-scheduled cells for the set of cells is configured or available for use, Scheme 1 is used to determine the size of a Type-1C field. Otherwise, Scheme 2 is used to determine the size of the type-1C field.
  • LSB or MSB of the field is applied.
  • the size of a Type-1C field of a DCI format 0_X/1_X may be determined by using the maximum size among cells with a smallest serving cell index within each combination of co-scheduled cells, or the maximum size among all cells within the set of cells. This may desirably provide one fixed size of a DCI format after RRC configuration. In addition or alternatively, this may desirably prevent monitoring issues for user devices 102 configured to monitor a single size of one DCI format in an active BWP.
  • action in event that the field size of a Type-1A field for one of co-scheduled cells is smaller than the determined field size in the DCI format 0_X/1_X used for multi-cell scheduling, action may be taken with respect to the indication in the Type-1A field.
  • a least significant bit LSB operation, assessment, or reinterpretation may be applied to the field is applied.
  • the user device 102 may ignore this field for the cell.
  • a Type-1A field may be an Open-loop power control (OLPC) field that includes an OLPC parameter set indication.
  • OLPC Open-loop power control
  • the OLPC parameter set indication in DCI format 0_X may be aligned with a physical layer (PHY) priority indicator definition, such as by having the same PHY priority and/or the same open loop (OL) transmit power control (TPC) parameter sets.
  • PHY physical layer
  • TPC transmit power control
  • LSB may be applied where the field size for one of co-scheduled cells is smaller than the determined field size in the DCI format 0_X/1_X, LSB (s) of the field.
  • Cell 1 may apply the second value in P0-PUSCH-Set with the lowest p0-PUSCH-SetID value, while Cell 2 may apply a first P0-PUSCH-AlphaSet in p0-AlphaSets, which may result in different PUSCH on multiple cells with different priority operations.
  • a size of the Open-loop power control (OLPC) parameter set indication may be a 0, 1, 2-bit.
  • the size of OLPC parameter set indication may be 0 bit if the higher layer parameter p0-PUSCH- SetList is not configured.
  • the size of OLPC parameter set indication may be 1 bit or 2 bits if the higher layer parameter p0-PUSCH-SetList is configured.
  • the size of OLPC parameter set indication may be a 1-bit where a SRS resource indicator is present in the DCI format 0_1.
  • the value of 1-bit may be a ‘0’ for low priority situations, and may be a ‘1’ for high priority situations.
  • whether the size of OLPC parameter set indication is a 1-bit or a 2-bit, may be determined by a higher layer parameter olpc-ParameterSetDCI-0-1 if a SRS resource indicator is not present in the DCI format 0_1. Similar to above, a bit value of ‘0’ and/or ‘00’ may be for low priority situations, and a bit value of ‘1’ , ‘01’ , or ‘10’ may be for high priority situations.
  • a bit value of ‘0’ and/or ‘00’ may mean a first P0-PUSCH-AlphaSet in p0-AlphaSets; a bit value of ‘1’ or ‘01’ may mean a first value in P0-PUSCH-Set with the lowest p0-PUSCH-SetID value; and a bit value of ‘10’ may mean a second value in P0-PUSCH-Set with the lowest p0-PUSCH-SetID value.
  • the user device 102 may be provided by SRI-PUSCH-PowerControl with more than one value of p0-PUSCH-AlphaSetId.
  • SRI-PUSCH-PowerControl with more than one value of p0-PUSCH-AlphaSetId.
  • the user device 102 may obtain a mapping from sri-PUSCH-PowerControlId in SRI-PUSCH-PowerControl between a set of values for the SRI field in the DCI format and a set of indexes provided by p0-PUSCH-AlphaSetId that map to a set of P0-PUSCH-AlphaSet values.
  • the user device 102 may determine the value of P O_UE_PUSCH, b, f, c (j) from the p0-PUSCH-AlphaSetId value that is mapped to the SRI field value. Also, in some embodiments for high priority situations, if the DCI format also includes an OLPC field and a value of the OLPC parameter set indication field is '1' , the user device 102 may determine a value of P O_UE_PUSCH, b, f, c (j) from a first value in P0-PUSCH-Set with a p0-PUSCH-SetId value mapped to the SRI field value.
  • j 2.
  • the user device 102 may determine a value of P O_UE_PUSCH, b, f, c (j) from: for low priority situations, a first P0-PUSCH-AlphaSet in p0-AlphaSets where a value of OLPC parameter set indication in the OLPC field is '0' or '00' ; for high priority situations, a first value in P0-PUSCH-Set with the lowest p0-PUSCH-SetID value where a value of the OLPC parameter set indication in the OLPC field is '1' or '01' ; for high priority situations, a second value in P0-PUSCH-Set with the lowest p0-PUSCH-SetID value where a value of the OLPC parameter set indication in the OLPC field is '10' ; or else, the user device 102 may determine P O_UE_PUSCH, b,
  • Additional parameters for the OLPC field may include:
  • p0-PUSCH-SetList-r16 SEQUENCE (SIZE (1.. maxNrofSRI-PUSCH-Mappings) ) OF P0-PUSCH-Set-r16 OPTIONAL, --Need R
  • P0-PUSCH-AlphaSet : : SEQUENCE ⁇
  • P0-PUSCH-AlphaSetId : : INTEGER (0.. maxNrofP0-PUSCH-AlphaSets-1)
  • P0-PUSCH-SetId-r16 : : INTEGER (0.. maxNrofSRI-PUSCH-Mappings-1)
  • P0-PUSCH-r16 : : INTEGER (-16.. 15)
  • the OLPC field may be determined or implemented according to one or more of the following schemes.
  • the field type of OLPC is the same as the field type of the SRI field. For example, if the SRI field is configured as Type-1A, then the OLPC field is correspondingly Type-1A. As another example, if the SRI field is configured as Type-2, then OLPC field is correspondingly Type-2.
  • the same OL TPC parameter sets may be indicated, and/or the same PUSCH PHY priority may be obtained for different PUSCH on co-scheduled scheduled cells.
  • the OLPC parameter set indication initially having a 2-bit ‘10’ value may be reinterpreted and/or represented as being a 1-bit ‘1’ value for a cell with a 1-bit OLPC parameter set indication.
  • a LSB function may be applied to reinterpret or represent a 2-bit value as a 1-bit value.
  • the 1-bit value may be reinterpreted or represented as a the 2-bit value without applying a LSB function.
  • an OLPC field may be a type-1A field.
  • LSB (s) of the OLPC field may be applied in order to reinterpret or represent a two-bit OLPC parameter set indication of ‘01’ as a 1-bit value of ‘1’ for the cell with a one bit OLPC field size.
  • Cell 1 may apply the first value in P0-PUSCH-Set with the lowest p0-PUSCH-SetID value, and Cell 2 may also apply the first value in P0-PUSCH-Set with the lowest p0-PUSCH-SetID value. This, in turn, may result in different PUSCH on multiple cells with the same priority operation, which can be regarded as a high priority operation.
  • DCI format 0_X For Cell 1 and Cell 2 are co-scheduled by DCI format 0_X Further, suppose a SRI field is a type-2 field. Further, suppose for Cell 1, the DCI format 0_1 does not include a SRI field and is configured with an OLPC field having a size of two bits. Additionally, suppose for Cell 2, the DCI format 0_1 includes a SRI field, and further is configured with an OLPC field having a one bit field size.
  • a 2-bit OLPC parameter set indication value of ‘10’ may be reinterpreted or represented as a one-bit value of ‘1’ for the cell having a OLPC field size of one bit without a LSB function being applied.
  • Cell 1 may apply the second value in P0-PUSCH-Set with the lowest p0-PUSCH-SetID value
  • Cell 2 may apply the first value in P0-PUSCH-Set with the lowest p0-PUSCH-SetID value. This, in turn, may result in different PUSCH on multiple cells with the same priority operation, which can be regarded as a high priority operation.
  • Cell 1 may apply a first P0-PUSCH-AlphaSet in p0-AlphaSets, and Cell #2 will also apply a first P0-PUSCH-AlphaSet in p0-AlphaSets. This, in turn, may result in different PUSCH on multiple cells with the same priority operation, which can be regarded as a low priority operation.
  • the size of the OLPC field may be configured per set of cells.
  • the second value in P0-PUSCH-Set with the lowest p0-PUSCH-SetID value may be configured for all cells within the set of cells.
  • the same OL TPC parameter sets may be indicated, and/or the same PUSCH PHY priority may be achieved and/or maintained.
  • a LSB operation may be performed to reinterpret or represent a 2-bit OLPC parameter indication value of ‘10’ as a 1-bit value of ‘1’ for the cell with a 1-bit OLPC field size. This may desirably allow different PUSCH on multiple cells to have the same priority operation.
  • Redundancy version (RV) fields configured per transport block (TB) may be Type-2 fields.
  • the size of a RV field may be configured per BWP per cell for DCI format 0_X/1_X.
  • one or more RV tables may be used to determine one or more RV values.
  • a RV table may associate 1-bit RV field values each with an associated RV value. That is, in each table, a 1-bit RV field value of ‘0’ may be associated with and/or indicate a first value, and a 1-bit RV field value of ‘1’ may be associated with and/or indicate a second value.
  • Two example tables are provided below.
  • a RV field value of ‘0’ is associated with and/or indicates a RV value of 0, and a RV field value of ‘1’ is associated with and/or indicates a RV value of 2.
  • a RV field value of ‘0’ is associated with and/or indicates a RV value of 0, and a RV field value of ‘1’ is associated with and/or indicates a RV value of 3.
  • a user device 102 and/or a network device 104 may be configured to use at least one of the tables to determine a RV value based on a RV field value in a RV field of a DCI format 0_X/1_X, and/or determine how to indicate a RV value with a RV field value in a RV field of a DCI format 0_X/1_X.
  • RV in DCI formats 0_1, 1_1, 0_2, and 1_2 is now described.
  • the number of bits for RV field value (the size of the RV field) may be determined according to the following.
  • the RV field value (or the size of the RV field) may be 2 bits, such as defined in Table 4, if the number of scheduled PDSCH indicated by the time domain resource assignment field is 1. Otherwise, the RV field value (or the size of the RV field) may be 2, 3, 4, 5, 6, 7 or 8 bits, determined by the maximum number of schedulable PDSCHs among all entries in the higher layer parameter pdsch-TimeDomainResourceAllocationListForMultiPDSCH, where each bit corresponds to one scheduled PDSCH, and the RV value may be determined according to a predetermined table, such as Table 2 above.
  • the RV field value may be 0, 1 or 2 bits, as determined by higher layer parameter numberOfBitsForRV-DCI-1-2.
  • the RV value (rv id ) to be applied is 0.
  • the RV values may be determined according to Table 3, above.
  • the RV values may be determined according to a table that associates two-bit RV field values with RV values, such as Table 4.
  • a RV table that associates RV field values with RV values of 0 and 3 may be used for ultra-reliable low latency communications (URLLC) , which may be regarded as for high priority PDSCH and/or PUSCH transmissions.
  • a RV table that associates RV field values with RV values of 0 and 2 may be used for enhanced mobile broadband (eMBB) or New Radio-Unlicensed (NR-U) , which may be regarded as for low priority PDSCH and/or /PUSCH transmissions.
  • eMBB enhanced mobile broadband
  • NR-U New Radio-Unlicensed
  • the size of the RV field may be configured per BWP per cell for DCI format 0_X/1_X, in event that the RV field size is one bit, which RV table to use to determine and/or indicate a RV value, may be determined according to one or more of the following schemes.
  • a first scheme in event that the RV field size is one bit (or the RV field value is a one-bit value) , the corresponding RV table that is used is also configured per BWP per cell or per cell. That is, the size of the RV field may be configured per BWP per cell for DCI format 0_X/1_X, and the corresponding RV table is also configured per BWP per cell or per cell.
  • Scheme 1 different 1 bit RV tables can be configured for different cells within the set of cells.
  • the corresponding RV table that is used is also configured per set of cells. That is, the size of the RV field may be configured per BWP per cell for DCI format 0_X/1_X, and the corresponding RV table may also be configured, but per set of cells.
  • the same one-bit RV table may be configured for different cells within the set of cells.
  • the 1-bit RV table may be used only for the cell with a 1-bit RV field size configured.
  • the corresponding RV table is predefined. That is, the size of RV field may be configured per BWP per cell for DCI format 0_X/1_X, and the corresponding 1-bit RV table is predefined, either RV0/2 (Table 2) or RV0/3 (Table 3) .
  • the same 1-bit RV table may be used for different cells within the set of cells. Also, in some embodiments, the 1-bit RV table may be used only for the cell with a 1-bit RV field size configured.
  • the DCI format 0_X/1_X when configured and for a Type 2 field with a reduced field size, which 1-bit RV table to use to indicate or determine RV values may be determined using a default RV table or may include one of two candidate tables per BWP per cell or per cell or per set of cells.
  • This may allow the user device 102 and the network device 104 to have same understanding with respect to RV values and how they are indicated in the DCI format 0_X/1_X, which in turn, may allow for more flexibility when scheduling, determining, and/or performing PDSCH/PUSCH retransmissions.
  • Type-1B field the size of a Type-1B field in the DCI format 0_X/1_X is equal to ceiling (log2 (N) ) , where N is the number of rows in RRC-configured table with each row containing multiple indexes for all cells within the set of cells.
  • the Type-1B field indicates one row of the configured table.
  • the Type-1B index for a cell points to a corresponding index in a RRC configured table applicable for DCI format 0_1/1_1 or MAC CE activated values.
  • the detailed configuration comprise at least one of following schemes.
  • Scheme 1 The table is explicitly configured in the configuration of set of cells level.
  • the table should also be BWP-specific. It should be configured by means of add and release list to reduce the RRC signalling overhead, where each element in the list corresponds to a BWP combination.
  • the downlink scheduling and uplink scheduling should be configured separately. Since BWP indicator in DCI is 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 for the first active BWP combination, the second element in the list is used for the configuration for the second active BWP combination, and so on.
  • Downlink scheduling configurations for DCI format 1_X mainly includes the configurations for Type-1B fields in DCI format 1_X.
  • An index may be configured to identify a downlink scheduling set when released.
  • For the time domain resource for PDSCH a table with at most 16 rows can be configured. Each row includes the specific time domain resource for PDSCH for each scheduled cell in the set. Wherein, the specific time domain resource for a scheduled cell is indicated by an index, where the index points to the time domain resource for PDSCH according to the legacy configuration for DCI format 1_1 in the corresponding BWP. Since multi-cell scheduling and multi-PDSCH scheduling may not be configured simultaneously for a PUCCH group, the value range for the index may be 0 ⁇ 15.
  • a table with at most 16 rows can be configured for rate matching pattern indicator. For each row, the value range for the index for a scheduled cell should be 0 ⁇ 3. For another example, a table with at most 8 rows can be configured for ZP CSI-RS trigger indication. For each row, the value range for the index for a scheduled cell should be 0 ⁇ 3. For another example, a table with at most 16 rows can be configured for TCI state indication. For each row, the value range for the index for a scheduled cell should be 0 ⁇ 8. The index points to the TCI state activated by the MAC CE for the scheduled cell in the corresponding BWP. For another example, a table with at most 16 rows can be configured for SRS request indication. For each row, the value range for the index for a scheduled cell should be 0 ⁇ 3. For another example, a table with at most 8 rows can be configured for SRS offset indicator. For each row, the value range for the index for a scheduled cell should be 0 ⁇ 3.
  • Uplink scheduling configurations for DCI format 0_X mainly includes the configurations for Type-1B fields in DCI format 0_X.
  • an index may be configured to identify an uplink scheduling set when released.
  • a table with at most 64 rows can be configured for time domain resource indication for PUSCH.
  • the value range for the index for a scheduled cell should be 0 ⁇ 63 due to up to 6-bit TDRA table can be configured with PUSCH repetition.
  • a table with at most 16 rows can be configured for SRS request indication.
  • the value range for the index for a scheduled cell should be 0 ⁇ 3.
  • a table with at most 8 rows can be configured for SRS offset indicator.
  • the value range for the index for a scheduled cell should be 0 ⁇ 3.
  • Scheme 2 The table is explicitly configured in the configuration of each cell level.
  • the table should also be BWP-specific.
  • the downlink scheduling and uplink scheduling should be configured separately. Since BWP indicator in DCI is Type-1A field, there are at most 4 active BWP combinations. In case the number of BWPs in each cell within the set of cells are same, for a type-1B field, the column of the table will be configured in each BWP of each cell.
  • PDSCH TimeDomainResourceAllocation in one BWP will be added one column of the table for type-1B indication for multi-cell scheduling. Note the actual rows of each table for different BWP are independently configured and no larger thanmaxNrofDL-Allocations-r18, for example, 8, 8, 16, 16 rows for each table.
  • the number of BWPs in each cell within the set of cells may be different.
  • the rows of one column for one cell with less number of BWPs may be combined with multiple BWPs of other cells with more number of BWPs.
  • cell#1 are configured with two BWPs
  • cell#2, 3, 4 are configured with four BWPs
  • BWP#1 in cell#1 is combined with BWP#1 and BWP#3 in Cell#2/3/4
  • BWP#2 in cell#1 is combined with BWP#2 and BWP#4 in Cell#2/3/4
  • rows of TDRA in cell#2/3/4 in BWP#1/2/3/4 are 8, 8, 16, 16, the type-1B TDRA for the set of cell of each BWP are also with 8, 8, 16, 16 rows.
  • the configuration of the column in the table is determined by one of following methods.
  • 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 above example, two column with 8, 16 rows are configured.
  • BWP Id can be configured in at least one of two columns of two tables.
  • terms, such as “a, ” “an, ” or “the, ” may be understood to convey a singular usage or to convey a plural usage, depending at least in part upon context.
  • the term “based on” may be understood as not necessarily intended to convey an exclusive set of factors and may, instead, allow for existence of additional factors not necessarily expressly described, again, depending at least in part on context.
  • the subject matter of the disclosure may also relate to or include, among others, the following aspects:
  • a first aspect includes a method for wireless communication that includes: determining, by a network device, a downlink control information (DCI) format for multi-cell scheduling transmissions in a set of cells, the determining comprising determining at least one size of at least one DCI field of the DCI format; and transmitting, by the network device, a DCI having the DCI format to schedule the transmissions for at least one of the cells of the set of cells.
  • DCI downlink control information
  • a second aspect includes a method for wireless communication that includes: receiving, by a user device, a radio resource control (RRC) configuration for determining a downlink control information (DCI) format for multi-cell scheduling transmissions in a set of cells, the determining comprising determining at least one size of at least one DCI field of the DCI format; and receiving, by the user device, a DCI having the DCI format to schedule the transmissions for at least one of the cells of the set of cells.
  • RRC radio resource control
  • a third aspect includes any of the first or second aspects, and further includes wherein a DCI field of the DCI format is a single field indicating an information to only one of co-scheduled cells, and a size of the DCI field is determined by one cell of the set of cells.
  • a fourth aspect includes the third aspect, and further includes wherein the one cell of the set of cells is determined by a first cell with a maximum size of the DCI field in an active bandwidth part (BWP) of a second cell with a smallest cell index in each subset of the set of cells, wherein each subset is for a respective combination of co-scheduled cells of the set of cells
  • BWP active bandwidth part
  • a fifth aspect includes the third aspect, and further includes wherein the one cell of the set of cells is determined by a first cell with a maximum size of the DCI field in an active bandwidth part (BWP) among all cells within the set of cells.
  • BWP active bandwidth part
  • a sixth aspect includes the third aspect, and further includes wherein the one cell of the set of cells is determined by a first cell with a first maximum size of the DCI field in a first active bandwidth part (BWP) of a second cell with a smallest cell index in each subset of the set of cells when a table defining combinations of co-scheduled cells for the set of cells is configured, and the one cell of the set of cells is determined by a third cell with a second maximum size of the DCI field in a second active BWP among all cells within the set of cells when the table is not configured.
  • BWP active bandwidth part
  • a seventh aspect includes any of the first through sixth aspects, and further includes wherein the at least one DCI field comprises an Open-loop power control (OLPC) field that comprises a parameter set indication, the method further comprising: determining the OLPC parameter by determining a field type of the OLPC field for the DCI format to match a field type of a sounding reference signal resource indicator (SRI) .
  • OLPC Open-loop power control
  • An eighth aspect includes any of the first through sixth aspects, and further includes wherein the at least one DCI field of the DCI format comprises an Open-loop power control (OLPC) field comprising a parameter set indication, wherein the at least one size comprises a size of the OLPC field, and wherein the size of the OLPC field is determined as a maximum field size of an active bandwidth part (BWP) among all cells within the set of cells, the method further comprising: reinterpreting the parameter set indication of the OLPC field from a 2-bit “10” value to a 1-bit “1” value for a cell of the set of cells when an OLPC field size for the cell of the set of cells is smaller than the determined size of the OLPC field in the DCI format.
  • OLPC Open-loop power control
  • a ninth aspect includes any of the first through sixth aspects, and further includes wherein the at least one DCI field comprises an Open-loop power control (OLPC) field comprising a parameter set indication, the at least one size comprising a size of the OLPC field, and wherein the size of the OLPC field is configured per set of cells.
  • OLPC Open-loop power control
  • a tenth aspect includes any of the first through ninth aspects, and further includes wherein the at least one DCI field comprises a redundancy version (RV) field, wherein the at least one size comprises a size of the RV field, wherein the size of the RV field is configurable, and wherein when one 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 per bandwidth part (BWP) , per cell, or per set of cells.
  • RV redundancy version
  • An eleventh aspect includes a wireless communications apparatus that includes a processor and a memory, wherein the processor is configured to read code from the memory to implement any of the first through tenth aspects.
  • a twelfth aspect includes a computer program product comprising a computer-readable program medium comprising code stored thereupon, the code, when executed by a processor, causing the processor to implement any of the first through tenth aspects.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Ce document concerne de manière générale la communication sans fil impliquant un dispositif réseau qui détermine un format d'informations de commande de liaison descendante (DCI) pour des transmissions de planification multicellulaires dans un ensemble de cellules, la détermination comprenant l'identification d'au moins une taille d'au moins un champ DCI du format de DCI. Le dispositif réseau transmet des DCI ayant le format de DCI pour planifier les transmissions pour au moins l'une des cellules de l'ensemble de cellules. De plus, un dispositif utilisateur reçoit une configuration de gestion des ressources radio (RRC) pour déterminer le format de DCI pour les transmissions de planification multicellulaires dans l'ensemble de cellules, et reçoit les DCI ayant le format de DCI pour planifier les transmissions pour au moins l'une des cellules de l'ensemble de cellules.
PCT/CN2023/087108 2023-04-07 2023-04-07 Détermination de format de dci pour une planification multicellulaire pour des communications sans fil WO2024113605A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/087108 WO2024113605A1 (fr) 2023-04-07 2023-04-07 Détermination de format de dci pour une planification multicellulaire pour des communications sans fil

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/087108 WO2024113605A1 (fr) 2023-04-07 2023-04-07 Détermination de format de dci pour une planification multicellulaire pour des communications sans fil

Publications (1)

Publication Number Publication Date
WO2024113605A1 true WO2024113605A1 (fr) 2024-06-06

Family

ID=91322885

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/087108 WO2024113605A1 (fr) 2023-04-07 2023-04-07 Détermination de format de dci pour une planification multicellulaire pour des communications sans fil

Country Status (1)

Country Link
WO (1) WO2024113605A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190349978A1 (en) * 2018-05-10 2019-11-14 Mediatek Inc. Physical Resource Block Scaling For Data Channel With HARQ Process
CN114175562A (zh) * 2019-08-02 2022-03-11 夏普株式会社 用户装备、基站装置和方法
US20220216972A1 (en) * 2019-04-25 2022-07-07 Ntt Docomo, Inc. User terminal and radio communication method

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190349978A1 (en) * 2018-05-10 2019-11-14 Mediatek Inc. Physical Resource Block Scaling For Data Channel With HARQ Process
US20220216972A1 (en) * 2019-04-25 2022-07-07 Ntt Docomo, Inc. User terminal and radio communication method
CN114175562A (zh) * 2019-08-02 2022-03-11 夏普株式会社 用户装备、基站装置和方法

Similar Documents

Publication Publication Date Title
US11575483B2 (en) Devices and methods for HARQ-ACK feedback scheme on PUSCH in wireless communication systems
US11582004B2 (en) Method and apparatus for reporting channel state information in wireless communication systems
US11895526B2 (en) Method and apparatus for measuring and reporting channel state in wireless communication system
US11317461B2 (en) Method and apparatus for generating MAC PDU
CN114080773B (zh) 具有不同服务类型的harq-ack码本的sr传输的优先级区分
US20240306179A1 (en) Method and apparatus for configuring priority of uci
US20190141727A1 (en) Method for transmitting hybrid automatic repeat request feedback information, user equipment, base station and system
US10701638B2 (en) Method and apparatus for reducing energy consumption of terminal in wireless communication system
US11979833B2 (en) Method and device for reporting channel state information in wireless communication system
US20230029850A1 (en) Method and apparatus for repeatedly transmitting uplink data for network cooperative communication
US20220159568A1 (en) Method and apparatus for transmitting and receiving terminal support information in wireless communication system
US11139912B2 (en) Method and apparatus for repetition-based data transmission for network cooperative communication
US11051324B2 (en) Multi-bit scheduling request
US20230045905A1 (en) Method and apparatus for power headroom reporting for uplink data repetitive transmission in network cooperative communications
US11990995B2 (en) Method and apparatus for repetition-based data transmission for network cooperative communication
US11910315B2 (en) Method and apparatus for reducing power consumption of terminal in wireless communication system
US20230217478A1 (en) Method and apparatus for data scheduling in wireless communication system
WO2021134226A1 (fr) Procédé et appareil de transmission de données
US20220361206A1 (en) Signaling solution on reliability enhancement for uplink transmission
WO2024113605A1 (fr) Détermination de format de dci pour une planification multicellulaire pour des communications sans fil
WO2024000441A1 (fr) Planification et transmission multicellulaires pour les communications sans fil
WO2023193225A1 (fr) Transmission de signal de programmation pour communications sans fil
WO2024168629A1 (fr) Procédé et appareil de détermination de taille de bloc de transport, dispositif et support de stockage
WO2024059984A1 (fr) Procédé et appareil de détermination de taille de bloc de transport, dispositif et support de stockage
WO2024020947A1 (fr) Multiplexage d'informations de commande pour des communications sans fil

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23895773

Country of ref document: EP

Kind code of ref document: A1