102 may be referred to as subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, UE, user terminals, a device, or by other terminology used in the art. The remote units 102 may communicate directly with one or more of the network units 104 via UL communication signals and/or the remote units 102 may communicate directly with other remote units 102 via sidelink communication.

The network units 104 may be distributed over a geographic region. In certain embodiments, a network unit 104 may also be referred to as an access point, an access terminal, a base, a base station, a Node-B, an eNB, a gNB, a Home Node-B, a RAN, a relay node, a device, a network device, an IAB node, a donor IAB node, or by any other terminology used in the art. The network units 104 are generally part of a radio access network that includes one or more controllers communicably coupled to one or more corresponding network units 104. The radio access network is generally communicably coupled to one or more core networks, which may be coupled to other networks, like the Internet and public switched telephone networks, among other networks. These and other elements of radio access and core networks are not illustrated but are well known generally by those having ordinary skill in the art.

In one implementation, the wireless communication system 100 is compliant with the 5G or NG (Next Generation) standard of the 3GPP protocol, wherein the network unit 104 transmits using NG RAN technology. More generally, however, the wireless communication system 100 may implement some other open or proprietary communication protocol, for example, WiMAX, among other protocols. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.

The network units 104 may serve a number of remote units 102 within a serving area, for example, a cell or a cell sector via a wireless communication link. The network units 104 transmit DL communication signals to serve the remote units 102 in the time, frequency, and/or spatial domain.

In various embodiments, a network unit 104 may determine configuration information comprising a plurality of instances of a physical downlink shared channel configuration parameter. In certain embodiments, the network unit 104 may transmit the configuration information to a user equipment (e.g., remote unit 102), wherein: the physical downlink shared channel configuration parameter is used for a physical downlink shared channel scheduled by downlink control information; the downlink control information is transmitted from a set of resources having a corresponding index of a plurality of indexes; and each index corresponds to an instance of the plurality of instances of the physical downlink shared channel configuration parameter. Accordingly, a network unit 104 may be used for transmitting information for PDSCH configurations.

In some embodiments, a remote unit 102 may receive configuration information from a network device (e.g., network unit 104), wherein: the configuration information comprises a plurality of instances of a physical downlink shared channel configuration parameter; the physical downlink shared channel configuration parameter is used for a physical downlink shared channel scheduled by downlink control information; the downlink control information is transmitted from a set of resources having a corresponding index of a plurality of indexes; and each index corresponds to an instance of the plurality of instances of the physical downlink shared channel configuration parameter. Accordingly, a remote unit 102 may be used for receiving information for PDSCH configurations.

FIG. 2 depicts one embodiment of an apparatus 200 that may be used for receiving information for PDSCH configurations. The apparatus 200 includes one embodiment of the remote unit 102. Furthermore, the remote unit 102 may include a processor 202, a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212. In some embodiments, the input device 206 and the display 208 are combined into a single device, such as a touchscreen. In certain embodiments, the remote unit 102 may not include any input device 206 and/or display 208. In various embodiments, the remote unit 102 may include one or more of the processor 202, the memory 204, the transmitter 210, and the receiver 212, and may not include the input device 206 and/or the display 208.

The processor 202, in one embodiment, may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations. For example, the processor 202 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, the processor 202 executes instructions stored in the memory 204 to perform the methods and routines described herein. The processor 202 is communicatively coupled to the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212.

The memory 204, in one embodiment, is a computer readable storage medium. In some embodiments, the memory 204 includes volatile computer storage media. For example, the memory 204 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”). In some embodiments, the memory 204 includes non-volatile computer storage media. For example, the memory 204 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 204 includes both volatile and non-volatile computer storage media. In some embodiments, the memory 204 also stores program code and related data, such as an operating system or other controller algorithms operating on the remote unit 102.

The input device 206, in one embodiment, may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. In some embodiments, the input device 206 may be integrated with the display 208, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, the input device 206 includes a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/or by handwriting on the touchscreen. In some embodiments, the input device 206 includes two or more different devices, such as a keyboard and a touch panel.

The display 208, in one embodiment, may include any known electronically controllable display or display device. The display 208 may be designed to output visual, audible, and/or haptic signals. In some embodiments, the display 208 includes an electronic display capable of outputting visual data to a user. For example, the display 208 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or similar display device capable of outputting images, text, or the like to a user. As another, non-limiting, example, the display 208 may include a wearable display such as a smart watch, smart glasses, a heads-up display, or the like. Further, the display 208 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.

In certain embodiments, the display 208 includes one or more speakers for producing sound. For example, the display 208 may produce an audible alert or notification (e.g., a beep or chime). In some embodiments, the display 208 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all or portions of the display 208 may be integrated with the input device 206. For example, the input device 206 and display 208 may form a touchscreen or similar touch-sensitive display. In other embodiments, the display 208 may be located near the input device 206.

The transmitter 210 is used to provide UL communication signals to the network unit 104 and the receiver 212 is used to receive DL communication signals from the network unit 104. In one embodiment, the receiver 212 receives configuration information from a network device (e.g., network unit 104), wherein: the configuration information comprises a plurality of instances of a physical downlink shared channel configuration parameter; the physical downlink shared channel configuration parameter is used for a physical downlink shared channel scheduled by downlink control information; the downlink control information is transmitted from a set of resources having a corresponding index of a plurality of indexes; and each index corresponds to an instance of the plurality of instances of the physical downlink shared channel configuration parameter.

Although only one transmitter 210 and one receiver 212 are illustrated, the remote unit 102 may have any suitable number of transmitters 210 and receivers 212. The transmitter 210 and the receiver 212 may be any suitable type of transmitters and receivers. In one embodiment, the transmitter 210 and the receiver 212 may be part of a transceiver.

FIG. 3 depicts one embodiment of an apparatus 300 that may be used for transmitting information for PDSCH configurations. The apparatus 300 includes one embodiment of the network unit 104. Furthermore, the network unit 104 may include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. As may be appreciated, the processor 302, the memory 304, the input device 306, the display 308, the transmitter 310, and the receiver 312 may be substantially similar to the processor 202, the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212 of the remote unit 102, respectively.

In some embodiments, the processor 302 determines configuration information comprising a plurality of instances of a physical downlink shared channel configuration parameter. In various embodiments, the transmitter 310 transmits the configuration information to a user equipment (e.g., remote unit 102), wherein: the physical downlink shared channel configuration parameter is used for a physical downlink shared channel scheduled by downlink control information; the downlink control information is transmitted from a set of resources having a corresponding index of a plurality of indexes; and each index corresponds to an instance of the plurality of instances of the physical downlink shared channel configuration parameter. Although only one transmitter 310 and one receiver 312 are illustrated, the network unit 104 may have any suitable number of transmitters 310 and receivers 312. The transmitter 310 and the receiver 312 may be any suitable type of transmitters and receivers. In one embodiment, the transmitter 310 and the receiver 312 may be part of a transceiver.

In various configurations, both S-DCI and M-DCI based M-TRP DL transmission may be used with either ideal backhaul or non-ideal backhaul. In some embodiments, for M-DCI scheduled multi-PDSCH, each TRP transmits its own PDSCH scheduled by a PDCCH. In such embodiments, some details of the PDSCH may be configured semi-statically in advance in RRC, while other details may be signaled dynamically in DCI. If a UE receives a DCI format 1_1 scheduling a PDSCH, the UE may need to determine which RRC parameter to use to decode the PDSCH. Various embodiments described herein correspond to an association between an RRC configured PDSCH-Config and DCI (e.g., which RRC parameter a UE should use for receiving a PDSCH from one of more TRPs).

In some configurations, only single TRP transmission is used, so a UE will receive PDSCH and PDCCH from the same TRP. In such configurations, there is only 1 DCI Format 1_1 sent from the TRP (e.g., gNB), only 1 RRC configured PDSCH-Config, and each field in the PDSCH-Config contains only a single value. Because there is only one TRP, there is no ambiguity about which parameter in the PDSCH-Config the fields in DCI format 1_1 refer to. For example, there is only one “dataScramblingIdentityPDSCH” parameter configured in the PDSCH-Config, and the UE uses this value to descramble all PDSCHs received. Similarly, there is only a single entry for the “dmrs-DownlinkForPDSCH-MappingTypeA” parameter in the PDSCH-Config, and UE the uses the “Antenna ports” field in DCI format 1_1 to refer to one of the configured DMRS configurations in RRC to determine the antenna ports and CDM groups in the received PDSCH.

Table 1 shows one embodiment of a PDSCH-Config IE and Table 2 shows one embodiment of field descriptions corresponding to the PDSCH-Config IE.

TABLE 1

PDSCH-Config Information Element

-- ASN1START

-- TAG-PDSCH-CONFIG-START

PDSCH-Config ::=
SEQUENCE {

dataScramblingIdentityPDSCH
INTEGER (0..1023)

OPTIONAL,
-- Need S

dmrs-DownlinkForPDSCH-MappingTypeA
SetupRelease { DMRS-DownlinkConfig }

OPTIONAL,
-- Need M

dmrs-DownlinkForPDSCH-MappingTypeB
SetupRelease { DMRS-DownlinkConfig }

OPTIONAL,
-- Need M

tci-StatesToAddModList
SEQUENCE (SIZE(1..maxNrofTCI-States)) OF TCI-State

OPTIONAL,
-- Need N

tci-StatesToReleaseList
SEQUENCE (SIZE(1..maxNrofTCI-States)) OF TCI-

StateId
OPTIONAL, -- Need N

vrb-ToPRB-Interleaver
ENUMERATED {n2, n4}

OPTIONAL,
-- Need S

resourceAllocation
ENUMERATED { resourceAllocationType0,

resourceAllocationType1, dynamicswitch},

pdsch-TimeDomainAllocationList
SetupRelease { PDSCH-

TimeDomainResourceAllocationList }
OPTIONAL, -- Need M

pdsch-AggregationFactor
ENUMERATED { n2, n4, n8 }

OPTIONAL,
-- Need S

rateMatchPatternToAddModList
SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF

RateMatchPattern
OPTIONAL, -- Need N

rateMatchPatternToReleaseList
SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF

RateMatchPatternId
OPTIONAL, -- Need N

rateMatchPatternGroup1
RateMatchPatternGroup

OPTIONAL,
-- Need R

rateMatchPatternGroup2
RateMatchPatternGroup

OPTIONAL,
-- Need R

rbg-Size
ENUMERATED {config1, config2},

mcs-Table
ENUMERATED {qam256, qam64LowSE}

OPTIONAL,
-- Need S

maxNrofCodeWordsScheduledByDCI
ENUMERATED {n1, n2}

OPTIONAL,
-- Need R

prb-BundlingType
CHOICE {

staticBundling
SEQUENCE {

bundleSize
ENUMERATED { n4, wideband }

OPTIONAL
-- Need S

},

dynamicBundling
SEQUENCE {

bundleSizeSet1
ENUMERATED { n4, wideband, n2-wideband, n4-

wideband }
OPTIONAL, -- Need S

bundleSizeSet2
ENUMERATED { n4, wideband }

OPTIONAL
-- Need S

}

},

zp-CSI-RS-ResourceToAddModList
SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-

Resources)) OF ZP-CSI-RS-Resource

OPTIONAL,
-- Need N

zp-CSI-RS-ResourceToReleaseList
SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-

Resources)) OF ZP-CSI-RS-ResourceId

OPTIONAL,
-- Need N

aperiodic-ZP-CSI-RS-ResourceSetsToAddModList
SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-

ResourceSets)) OF ZP-CSI-RS-ResourceSet

OPTIONAL,
-- Need N

aperiodic-ZP-CSI-RS-ResourceSetsToReleaseList
SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-

ResourceSets)) OF ZP-CSI-RS-ResourceSetId

OPTIONAL,
-- Need N

sp-ZP-CSI-RS-ResourceSetsToAddModList
SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets))

OF ZP-CSI-RS-ResourceSet

OPTIONAL,
-- Need N

sp-ZP-CSI-RS-ResourceSetsToReleaseList
SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets))

OF ZP-CSI-RS-ResourceSetId

OPTIONAL,
-- Need N

p-ZP-CSI-RS-ResourceSet
SetupRelease { ZP-CSI-RS-ResourceSet }

OPTIONAL,
-- Need M

...

}

RateMatchPatternGroup ::=
SEQUENCE (SIZE (1..maxNrofRateMatchPatternsPerGroup))

OF CHOICE {

cellLevel
RateMatchPatternId,

bwpLevel
RateMatchPatternId

}

-- TAG-PDSCH-CONFIG-STOP

-- ASN1STOP

TABLE 2

PDSCH-Config Field Descriptions

aperiodic-ZP-CSI-RS-ResourceSetsToAddModList
AddMod and/or Release lists for configuring

aperiodically triggered zero-power CSI-RS

resource sets. Each set contains a ZP-CSI-RS-

ResourceSetId and the IDs of one or more ZP-

CSI-RS-Resources (the actual resources are

defined in the zp-CSI-RS-

ResourceToAddModList). The network

configures the UE with at most 3 aperiodic

ZP-CSI-RS-ResourceSets and it uses only the

ZP-CSI-RS-ResourceSetId 1 to 3. The network

triggers a set by indicating its ZP-CSI-RS-

ResourceSetId in the DCI payload. The DCI

codepoint ‘01’ triggers the resource set with

ZP-CSI-RS-ResourceSetId 1, the DCI

codepoint ‘10’ triggers the resource set with

ZP-CSI-RS-ResourceSetId 2, and the DCI

codepoint ‘11’ triggers the resource set with

ZP-CSI-RS-ResourceSetId 3 (see TS 38.214,

clause 5.1.4.2)

dataScramblingIdentityPDSCH
Identifier used to initialize data scrambling

(c_init) for PDSCH. If the field is absent, the

UE applies the physical cell ID. (see TS

38.211, clause 7.3.1.1).

dmrs-DownlinkForPDSCH-MappingTypeA
DMRS configuration for PDSCH

transmissions using PDSCH mapping type A

(chosen dynamically via PDSCH-

TimeDomainResourceAllocation). Only the

fields dmrs-Type, dmrs-AdditionalPosition

and maxLength may be set differently for

mapping type A and B.

dmrs-DownlinkForPDSCH-MappingTypeB
DMRS configuration for PDSCH

transmissions using PDSCH mapping type B

(chosen dynamically via PDSCH-

TimeDomainResourceAllocation). Only the

fields dmrs-Type, dmrs-AdditionalPosition

and maxLength may be set differently for

mapping type A and B.

maxNrofCodeWordsScheduledByDCI
Maximum number of code words that a single

DCI may schedule. This changes the number

of MCS/RV/NDI bits in the DCI message

from 1 to 2.

mcs-Table
Indicates which MCS table the UE shall use

for PDSCH. (see TS 38.214, clause 5.1.3.1).

If the field is absent the UE applies the value

64QAM.

pdsch-AggregationFactor
Number of repetitions for data (see TS

38.214, clause 5.1.2.1). When the field is

absent the UE applies the value 1.

pdsch-TimeDomainAllocationList
List of time-domain configurations for timing

of DL assignment to DL data (see table

5.1.2.1.1-1 in TS 38.214).

prb-BundlingType
Indicates the PRB bundle type and bundle

size(s) (see TS 38.214, clause 5.1.2.3). If

dynamic is chosen, the actual bundleSizeSet1

or bundleSizeSet2 to use is indicated via DCI.

Constraints on bundleSize(Set) setting

depending on vrb-ToPRB-Interleaver and rbg-

Size settings are described in TS 38.214 [19],

clause 5.1.2.3. If a bundleSize(Set) value is

absent, the UE applies the value n2.

p-ZP-CSI-RS-ResourceSet
A set of periodically occurring ZP-CSI-RS-

Resources (the actual resources are defined in

the zp-CSI-RS-ResourceToAddModList). The

network uses the ZP-CSI-RS-

ResourceSetId = 0 for this set.

rateMatchPatternGroup1
The IDs of a first group of RateMatchPatterns

defined in PDSCH-Config −>

rateMatchPatternToAddModList (BWP

level) or in ServingCellConfig −>

rateMatchPatternToAddModList (cell level).

These patterns can be activated dynamically

by DCI (see TS 38.214, clause 5.1.4.1).

rateMatchPatternGroup2
The IDs of a second group of

RateMatchPatterns defined in PDSCH-

Config −> rateMatchPatternToAddModList

(BWP level) or in ServingCellConfig −>

rateMatchPatternToAddModList (cell level).

These patterns can be activated dynamically

by DCI (see TS 38.214, clause 5.1.4.1).

rateMatchPatternToAddModList
Resources patterns which the UE should rate

match PDSCH around. The UE rate matches

around the union of all resources indicated in

the nested bitmaps (see TS 38.214, clause

5.1.4.1). FFS: RAN1 indicates that there

should be a set of patterns per cell and one per

BWP => Having both seems unnecessary.

rbg-Size
Selection between config 1 and config 2 for

RBG size for PDSCH. The UE ignores this

field if resourceAllocation is set to

resourceAllocationType1 (see TS 38.214,

clause 5.1.2.2.1).

resourceAllocation
Configuration of resource allocation type 0

and resource allocation type 1 for non-

fallback DCI (see TS 38.214, clause 5.1.2.2).

sp-ZP-CSI-RS-ResourceSetsToAddModList
AddMod and/or Release lists for configuring

semi-persistent zero-power CSI-RS resource

sets. Each set contains a ZP-CSI-RS-

ResourceSetId and the IDs of one or more ZP-

CSI-RS-Resources (the actual resources are

defined in the zp-CSI-RS-

ResourceToAddModList) (see TS 38.214,

clause 5.1.4.2).

tci-StatesToAddModList
A list of TCI states indicating a transmission

configuration which includes QCL-

relationships between the DL RSs in one RS

set and the PDSCH DMRS ports (see TS

38.214, clause 5.1.5).

vrb-ToPRB-Interleaver
Interleaving unit configurable between 2 and

4 PRBs (see TS 38.211, clause 7.3.1.6). When

the field is absent, the UE performs non-

interleaved VRB-to-PRB mapping.

zp-CSI-RS-ResourceToAddModList
A list of ZP CSI-RS resources used for

PDSCH rate-matching. Each resource in this

list may be referred to from only one type of

resource set, i.e., aperiodic, semi-persistent or

periodic (see TS 38.214).

In certain embodiments that use M-DCI M-TRP transmission, each TRP transmits its own PDSCH scheduled by its own PDCCH. As may be appreciated, different PDSCHs transmitted from different TRPs may use different data scrambling IDs (e.g., dataScramblingIdentityPDSCH), different DMRS configurations (e.g., dmrs-DownlinkForPDSCH-MappingTypeA, dmrs-DownlinkForPDSCH-MappingTypeB), different TCI states (e.g., tci-StatesToAddModList, tci-StatesToReleaseList), and/or other different PDSCH transmission parameters. In some embodiments, different RRC parameters for different TRPs may be configured in the same PDSCH-Config IE with multiple fields, and, in other embodiments, different RRC parameters for different TRPs may be configured in multiple PDSCH-Config IEs. For example, if there are 2 TRPs, two different data scrambling IDs, two different dmrs-DownlinkForPDSCH-MappingTypeA, two different dmrs-DownlinkForPDSCH-MappingTypeB, and/or two different TCI states configurations may be provided in the same PDSCH-Config IE in RRC. As another example, two sets of transmission parameters in different PDSCH-Config IEs may be configured by RRC.

In various embodiments, to distinguish DCIs transmitted from different TRPs, an index (e.g., higher layer index) may be defined for one or more different set of resources that may be used by TRPs (e.g., CORESETs). As may be appreciated, each TRP may be configured to use a different set of resources or multiple sets of resources, therefore, the index may indicate a set of resources or multiple sets of resources which further indicate a specific TRP. In certain embodiments, a PDCCH containing DCI is transmitted in a set of resources and, therefore, is associated with an index. In such embodiments, the index is different from a CORESET ID and may be used to associate a set of resources or multiple sets of resources with a specific TRP. In some embodiments, multiple sets of resources (e.g., CORESETs) transmitted from the same TRP may be considered to be in a group (e.g., CORESET group) having the same index for each set of resources in the group.

In a first embodiment, multiple different PDSCH RRC parameters may be configured in the same PDSCH-Config IE, and a UE selects which parameter to use based on an index corresponding to a set of resources (e.g., CORESET) in which the UE receives scheduling DCI. In certain embodiments, if there are an N number of the same type of parameters, such as data scrambling IDs or DMRS configurations, configured in the same PDSCH-Config IE, a list of N indexes may also be included in the PDSCH-Config IE. In such embodiments, there may be a one-to-one relationship between each instance of an RRC parameter and each index value. Furthermore, if there is only one instance of an RRC parameter included in the PDSCH-Config IE, the single instance of the RRC parameter may apply to all index values. In various embodiments, if a UE receives scheduling DCI from a set of resources with an nth configured index (e.g., nth index with a first index in a list being 1 and counting upward by is in the list), the UE applies a corresponding nth configured RRC parameter, such as data scrambling ID, dmrs-DownlinkForPDSCH-MappingTypeA, dmrs-DownlinkForPDSCH-MappingTypeB, and/or TCI state, to the PDSCH. In some embodiments, if no list of indexes is configured in the PDSCH-Config IE, a UE may use an nth index among all configured sets of resources for an nth instance of a configured parameter.

In a second embodiment, a separate PDSCH-Config IE per TRP may be configured for a UE in which each PDSCH-config IE only contains RRC parameters related to PDSCH transmitted from one TRP (e.g., having a corresponding index), and the index may be included in the PDSCH-Config IE. In such embodiments, the UE applies the TRP specifically configured RRC PDSCH parameters, such as data scrambling ID, dmrs-DownlinkForPDSCH-MappingTypeA, dmrs-DownlinkForPDSCH-MappingTypeB, and/or TCI state, to a received PDSCH if the scheduling DCI is received in a set of resources with the corresponding index. In some embodiments, if an index is not included in a PDSCH-Config IE, a UE may assume that an nth configured PDSCH-Config IE is associated with an nth index among all the configured sets of resources.

FIG. 4 is a schematic flow chart diagram illustrating one embodiment of a method 400 for transmitting information for PDSCH configurations. In some embodiments, the method 400 is performed by an apparatus, such as the network unit 104. In certain embodiments, the method 400 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

The method 400 may include determining 402 configuration information comprising a plurality of instances of a physical downlink shared channel configuration parameter. In certain embodiments, the method 400 includes transmitting 404 the configuration information to a user equipment, wherein: the physical downlink shared channel configuration parameter is used for a physical downlink shared channel scheduled by downlink control information; the downlink control information is transmitted from a set of resources having a corresponding index of a plurality of indexes; and each index corresponds to an instance of the plurality of instances of the physical downlink shared channel configuration parameter.

In certain embodiments, each index of the plurality of indexes corresponds to at least one control resource set (e.g., one or more CORESETs). In some embodiments, the configuration information comprises a plurality of instances of selected physical downlink shared channel configuration parameters of a plurality of physical downlink shared channel configuration parameters. In various embodiments, the plurality of instances of the physical downlink shared channel configuration parameter is part of a single physical downlink shared channel configuration.

In one embodiment, one instance of at least one physical downlink shared channel configuration parameter corresponds to the plurality of indexes (e.g., one instance of a parameter is used for all indexes). In certain embodiments, the single physical downlink shared channel configuration comprises a list of the plurality of indexes, and instances of the plurality of instances of the physical downlink shared channel configuration parameter are mapped to the indexes in the list of the plurality of indexes. In some embodiments, in response to the configuration information not mapping instances of the plurality of instances of the physical downlink shared channel configuration parameter to the plurality of indexes, the instances of the plurality of instances of the physical downlink shared channel configuration parameter are mapped to the plurality of indexes in ascending order. For example, a first listed instance of the physical downlink shared channel configuration parameter in a list of instances of the physical downlink shared channel configuration parameter is mapped to a lowest index, a second listed instance of the physical downlink shared channel configuration parameter in the list of instances of the physical downlink shared channel configuration parameter is mapped to a second lowest index, and so forth.

In various embodiments, each instance of the plurality of instances of the physical downlink shared channel configuration parameter is in a separate physical downlink shared channel configuration. In one embodiment, the separate physical downlink shared channel configuration comprises an index of the plurality of indexes. In certain embodiments, in response to the separate physical downlink shared channel configuration not comprising an index of the plurality of indexes, the separate physical downlink shared channel configuration is mapped to the plurality of indexes in ascending order. For example, the first physical downlink shared channel configuration that is configured is mapped to a lowest index, the second physical downlink shared channel configuration that is configured is mapped to a second lowest index, and so forth.

In some embodiments, the configuration information comprises one or more physical downlink shared channel configuration parameters comprising dataScramblingIdentityPDSCH, dmrs-DownlinkForPDSCH-MappingTypeA, dmrs-DownlinkForPDSCH-MappingTypeB, tci-StatesToAddModList, tci-StatesToReleaseList, resourceAllocation, pdsch-TimeDomainAllocationList, pdsch-AggregationFactor, rbg-Size, mcs-Table, prb-BundleSize, or some combination thereof.

FIG. 5 is a schematic flow chart diagram illustrating one embodiment of a method 500 for receiving information for PDSCH configurations. In some embodiments, the method 500 is performed by an apparatus, such as the remote unit 102. In certain embodiments, the method 500 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

The method 500 may include receiving 502 configuration information from a network device, wherein: the configuration information comprises a plurality of instances of a physical downlink shared channel configuration parameter; the physical downlink shared channel configuration parameter is used for a physical downlink shared channel scheduled by downlink control information; the downlink control information is transmitted from a set of resources having a corresponding index of a plurality of indexes; and each index corresponds to an instance of the plurality of instances of the physical downlink shared channel configuration parameter.

In certain embodiments, each index of the plurality of indexes corresponds to at least one control resource set. In some embodiments, the configuration information comprises a plurality of instances of selected physical downlink shared channel configuration parameters of a plurality of physical downlink shared channel configuration parameters. In various embodiments, the plurality of instances of the physical downlink shared channel configuration parameter is part of a single physical downlink shared channel configuration.

In one embodiment, one instance of at least one physical downlink shared channel configuration parameter corresponds to the plurality of indexes. In certain embodiments, the single physical downlink shared channel configuration comprises a list of the plurality of indexes, and instances of the plurality of instances of the physical downlink shared channel configuration parameter are mapped to the indexes in the list of the plurality of indexes. In some embodiments, the method 500 further comprises, in response to the configuration information not mapping instances of the plurality of instances of the physical downlink shared channel configuration parameter to the plurality of indexes, mapping the instances of the plurality of instances of the physical downlink shared channel configuration parameter to the plurality of indexes in ascending order.

In various embodiments, each instance of the plurality of instances of the physical downlink shared channel configuration parameter is in a separate physical downlink shared channel configuration. In one embodiment, the separate physical downlink shared channel configuration comprises an index of the plurality of indexes. In certain embodiments, the method 500 further comprises, in response to the separate physical downlink shared channel configuration not comprising an index of the plurality of indexes, mapping the separate physical downlink shared channel configuration to the plurality of indexes in ascending order.

In some embodiments, the configuration information comprises one or more physical downlink shared channel configuration parameters comprising dataScramblingIdentityPDSCH, dmrs-DownlinkForPDSCH-MappingTypeA, dmrs-DownlinkForPDSCH-MappingTypeB, tci-StatesToAddModList, tci-StatesToReleaseList, resourceAllocation, pdsch-TimeDomainAllocationList, pdsch-AggregationFactor, rbg-Size, mcs-Table, prb-BundleSize, or some combination thereof.

In one embodiment, a method comprises: determining configuration information comprising a plurality of instances of a physical downlink shared channel configuration parameter; and transmitting the configuration information to a user equipment, wherein: the physical downlink shared channel configuration parameter is used for a physical downlink shared channel scheduled by downlink control information; the downlink control information is transmitted from a set of resources having a corresponding index of a plurality of indexes; and each index corresponds to an instance of the plurality of instances of the physical downlink shared channel configuration parameter.