EP4104326A1

EP4104326A1 - Modulation and coding scheme table to resource set associations for multi-transmit receive point operation

Info

Publication number: EP4104326A1
Application number: EP20839025.2A
Authority: EP
Inventors: Keeth Saliya JAYASINGHE LADDU
Original assignee: Nokia Technologies Oy
Current assignee: Nokia Technologies Oy
Priority date: 2020-02-11
Filing date: 2020-12-22
Publication date: 2022-12-21
Also published as: WO2021160331A1

Abstract

Systems, methods, apparatuses, and computer program products for providing multi-downlink control information (DCI) multi-transmit receive point (TRP) operation are described.

Description

MODULATION AND CODING SCHEME TABLE TO RESOURCE SET ASSOCIATIONS FOR MULTI-TRANSMIT RECEIVE POINT OPERATION

FIELD:

[0001] Some example embodiments may generally relate to mobile or wireless telecommunication systems, such as Long Term Evolution (LTE) or fifth generation (5G) radio access technology or new radio (NR) access technology, or other communications systems. For example, certain embodiments may be directed to systems and/or methods relating to multi-downlink control information (DCI) multi-transmit receive point (TRP) operation.

BACKGROUND:

[0002] Examples of mobile or wireless telecommunication systems may include the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), LTE-Advanced (LTE-A), MulteFire, LTE- A Pro, fifth generation (5G) radio access technology or new radio (NR) access technology, IEEE 802.11 based technologies, and/or Wi-Fi technologies. 5G wireless systems refer to the next generation (NG) of radio systems and network architecture. A 5G system is mostly built on a 5G new radio (NR), but a 5G (or NG) network can also build on the E-UTRA radio. It is estimated that NR provides bitrates on the order of 10-20 Gbit/s or higher, and can support at least service categories such as enhanced mobile broadband (eMBB) and ultra-reliable low-latency- communication (URLLC) as well as massive machine type communication (mMTC). NR is expected to deliver extreme broadband and ultra-robust, low latency connectivity and massive networking to support the Internet of Things (IoT). With IoT and machine-to-machine (M2M) communication becoming more widespread, there will be a growing need for networks that meet the needs of lower power, low data rate, and long battery life. The next generation radio access network (NG-RAN) represents the RAN for 5G, which can provide both NR and LTE (and LTE- Advanced) radio accesses. It is noted that, in 5G, the nodes that can provide radio access functionality to a user equipment (i.e., similar to the Node B, NB, in UTRAN or the evolved NB, eNB, in LTE) may be named next-generation NB (gNB) when built on NR radio and may be named next-generation eNB (NG-eNB) when built on E-UTRA radio.

BRIEF DESCRIPTION OF THE DRAWINGS:

[0003] For proper understanding of example embodiments, reference should be made to the accompanying drawings, wherein: [0004] Fig. 1 illustrates an example system depicting separate PDCCH sent via different TRPs to schedule PD SCH transmissions, according to an embodiment;

[0005] Fig. 2 illustrates an example system depicting the use of CORESET groups to relate the MCS tables, according to an embodiment; [0006] Fig. 3a illustrates an example of a PDSCH configuration information element (IE), according to an embodiment;

[0007] Fig. 3b illustrates an example table depicting the PDSCH configuration field descriptions, according to an embodiment;

[0008] Fig. 4a illustrates an example flow diagram of a method, according to an embodiment; [0009] Fig. 4b illustrates an example flow diagram of a method, according to an embodiment;

[0010] Fig. 5a illustrates an example block diagram of an apparatus, according to an embodiment; and

[0011] Fig. 5b illustrates an example block diagram of an apparatus, according to an embodiment.

DETAILED DESCRIPTION:

[0012] It will be readily understood that the components of certain example embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for multi downlink control information (DCI) multi-transmit receive point (TRP) operation, is not intended to limit the scope of certain embodiments but is representative of selected example embodiments. [0013] The features, structures, or characteristics of example embodiments described throughout this specification may be combined in any suitable manner in one or more example embodiments. For example, the usage of the phrases “certain embodiments,” “some embodiments,” or other similar language, throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment. Thus, appearances of the phrases “in certain embodiments,” “in some embodiments,” “in other embodiments,” or other similar language, throughout this specification do not necessarily all refer to the same group of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments.

[0014] Additionally, if desired, the different functions or procedures discussed below may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the described functions or procedures may be optional or may be combined. As such, the following description should be considered as illustrative of the principles and teachings of certain example embodiments, and not in limitation thereof.

[0015] In 3^rd generation partnership project (3GPP) NR multiple-input multiple-output (MIMO) enhancements for 3GPP Release- 16, multi -TRP was considered an important component due to the benefits of eMBB operations, as well as the capability of improving reliability for the URLLC services. In Release-16, objectives included enhancements on multi-TRP/panel transmission including improved reliability and robustness with both ideal and non-ideal backhaul, specifying downlink control signalling enhancement(s) for efficient support of non-coherent joint transmission, specifying (if needed) enhancements on uplink control signalling and/or reference signal(s) for non-coherent joint transmission, and multi-TRP techniques for URLLC requirements. [0016] In 3GPP Release-17, some of the objectives included enhancements on the support for multi-TRP deployment, targeting both frequency range 1 (FR1) and frequency range 2 (FR2). These enhancements may comprise: specifying features to improve reliability and robustness for channels other than physical downlink shared channel (PDSCH) (e.g., physical downlink control channel (PDCCH), physical uplink shared channel (PUSCH), and physical uplink control channel (PUCCH)) using multi-TRP and/or multi -panel with Release- 16 reliability features as the baseline, specifying quasi-co-location (QCL)/transmission configuration indication (TCI)-related enhancements to enable inter-cell multi-TRP operations assuming multi-DCI based multi-PDSCH reception, specifying (if needed) beam-management-related enhancements for simultaneous multi- TRP transmission with multi-panel reception, and enhancements to support HST-SFN deployment scenario, such as specifying solution(s) on QCL assumption for demodulation reference signal (DMRS) (e.g., multiple QCL assumptions for the same DMRS port(s), targeting DL-only transmission) and possibly specifying QCL/QCL-like relation (including applicable type(s) and the associated requirement) between DL and UL signal by reusing the unified TCI framework.

[0017] As will be discussed in more detail in the following, certain embodiments may relate to further enhancements on multiple PDCCH based multi-TRP transmission.

[0018] To support multiple-PDCCH based multi-TRP/panel transmission with intra-cell (same cell ID) and inter-cell (different Cell IDs), the following RRC configuration may be used to link multiple PDCCH/PDSCH pairs with multiple TRPs: one control resource set (CORESET) in a PDCCH configuration ( PDCCH-config ) corresponds to one TRP.

[0019] If a UE is configured by higher layer parameter PDCCH-config that contains two different values of a CORESET pool index ( CORESETPoolIndex ) in ControlResourceSet for the active bandwidth part (BWP) of a serving cell, the UE may expect to receive multiple PDCCHs scheduling fully, partially, and/or non-overlapped PDSCHs in time and frequency domain subject to UE capability. This may allow a UE to be not configured with either joint hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback or separate HARQ ACK feedback. For the CORESET without CORESETPoolIndex, the UE may assume that the CORESET is assigned with CORESETPoolIndex as 0.

[0020] The flexibility of this configuration is wide-ranging and this framework can be applied in general to other scenarios like enhancements for URLLC. Basically, the multi -DCI based multi - TRP framework allows out of order operations, which could be useful when supporting URLLC services via different TRPs or via the same TRP (with different CORESET groups). Certain embodiments described above and in the following may also be applied to multi-link association scheme(s) that may be used in future IEEE 802.11 and/or Wi-Fi networks. Multi-link association may mean that a station may have multiple links towards an access point (AP) within a single association. In other scenarios, the station may have simultaneously multiple associations, each towards different APs. At least this latter scenario, multi -AP association, may have common aspects with 3GPP multi-TRP technology. Therefore, as said, the example embodiments described herein may be applicable to IEEE 802.11 and/or Wi-Fi. In those embodiments, an AP may correspond to a TRP.

[0021] For multi-DCI based multi-TRP, when PDCCHs schedule two PDSCHs/PUSCHs across TRPs, i.e., PDCCHs are associated with different values of CORESETPoolIndex, following operations are allowed: PDCCH to PDSCH, PDCCH to PUSCH, and PDSCH to HARQ-ACK. In PDCCH to PDSCH operation, for any two HARQ process IDs in a given scheduled cell, if the UE is scheduled to start receiving a first PDSCH starting in symbol j by a PDCCH associated with a value of CORESETPoolIndex ending in symbol i, the UE can be scheduled to receive a PDSCH starting earlier than the end of the first PDSCH with a PDCCH associated with a different value of CORESETPoolIndex that ends later than symbol i. In PDCCH to PUSCH operation, for any two HARQ process IDs in a given scheduled cell, if the UE is scheduled to start a first PUSCH transmission starting in symbol j by a PDCCH associated with a value of CORESETPoolIndex ending in symbol i, the UE can be scheduled to transmit a PUSCH starting earlier than the end of the first PUSCH by a PDCCH associated with a different value of CORESETPoolIndex that ends later than symbol i. It is noted that, from the UE perspective, this does not imply overlapped PUSCHs at the time. In PDSCH to HARQ-Ack operation, in a given scheduled cell, the UE can receive a first PDSCH in slot i, with the corresponding HARQ-ACK assigned to be transmitted in slot j, and a second PDSCH associated with a CORESETPoolIndex different from the first PDSCH starting later than the first PDSCH with its corresponding HARQ-ACK assigned to be transmitted in a slot before slot j . The above operations are optional for a UE that supports multi-DCI based multi-TRP. For the CORESET without CORESETPoolIndex, the UE may assume that the

CORESET is assigned with CORESETPoolIndex as 0. [0022] As introduced above, certain embodiments may relate to multi-DCI multi-TRP schemes in which a UE may receive from multiple transmission reception points (TRPs), and where TRPs may schedule their downlink transmission towards the UE independently of each other. In Release- 16, this has been enabled such that, if a UE has received RRC configuration parameter PDCCH- Config with two different values of CoresetPoolIndex, with the values associated to different TRPs, the UE may receive multiple PDCCHs (from these different TRPs) scheduling fully, partially and/or non-overlapped PDSCHs in time and frequency domain. Thus, in Release- 16, CoresetPoolIndex may be used to indicate where to find PDSCHs in time-frequency space. However, it does not carry information relating to modulation and coding schemes (MCS), such as indications of which MCS table should be used.

[0023] Release- 16 multi-DCI based multi-TRP scheme is widely applicable for all the channel conditions of TRP-to-UE, and for ideal and non-ideal backhaul between TRP. As mentioned above, the framework provided in multi-DCI based multi-TRP transmission can be used for eMBB, as well as for URLLC and mixed service support. A benefit compared to a single DCI based multi- TRP transmission is the freedom provided in the scheduling and possibility to provide good performance even when the TRP-UE channels have significant variations. Fig. 1 illustrates an example system diagram in which separate PDCCH may be sent via different TRPs to schedule the PDSCH transmissions. If needed, multiple DCI based URLLC schemes (like TDM, FDM PDSCH schemes in Release- 16) can be supported using the same transmission block (TB) and indicating the same HARQ process ID towards the UE. However, it would be desirable to have certain flexibilities in the modulation and coding scheme (MCS) configurations to enable smooth operation for multi-DCI based multi-TRP schemes that are highlighted in the following.

[0024] When there is less than 5 dB difference in the reference signal received power (RSRP) measured at the UE side, TRPs can use the same MCS table as the scheduled MCSs by independent DCIs from each TRP may be much closer to each other. However, when one TRP supports high priority traffic compared to the other TRP, the required block error rate (BLER) operating point could be much lower, e.g., 10-5. Those cases may require using significantly different MCS compared to the TRP that supports low priority traffic. The MCS table to be used for the TRP (or the service type) is configured by the PDSCH configuration, where a change of the service may trigger to have RRC reconfiguration or use of different radio network temporary identifier (RNTI) at the TRP and the UE side (not all UEs may support such a feature).

[0025] Even in the scenario where a single service is supported to the UE via multiple TRPs (e.g., considering multi DCI multi-TRP transmission for eMBB), a significant difference in the RSRP values can be a reasonable assumption at the UE side. If the channel quality observed at the UE or variation of the channel(s) are significantly different, the link adaptation techniques may not work correctly when a single MCS table is used for both TRPs.

[0026] For example, if a first TRP (TRP1) carries high priority traffic and another TRP (TRP2) carries low priority traffic, or even if single service is carried via both TRPs but channel qualities observed at the UE differ, the use of a single MCS table is not optimal or may not work. As the existing configurations do not allow for configuring multiple MCS tables for multiple TRPs, certain embodiments herein introduce a new method for addressing at least this issue.

[0027] According to some example embodiments, when the multi-DCI based multi-TRP operation or framework is applied to a UE, the UE can be additionally configured to use multiple MCS tables, where the same or different MCS tables may be used among multiple TRPs. Currently, NR has three MCS tables, 64QAM (default table), 256QAM, and QAM64LowSE (for URLLC), and each TRP may be configured with at least with one of these. It is noted, however, that example embodiments are not necessarily limited to these MCS tables, as certain embodiments can be extended and applied to any type of MCS table.

[0028] In an embodiment, configuring multiple MCS tables may be performed using RRC signalling, where the configuration can be carried within the PDSCH configuration of the BWP configuration, and one or more MCS table(s) are indicated. According to one embodiment, if one MCS table is indicated, then Release- 16 behaviour as discussed above may be followed, where multiple TRPs use the indicated MCS table. In certain embodiments, when more than one MCS table is configured per UE, the UE may derive the MCS table to be used for receiving data from a TRP based on the CORESET(s) used by the TRP. Additionally, in an embodiment, when more than one MCS table is configured per UE, the UE may derive transport block size, low density parity check (LDPC) base graph, limited buffer rate matching (LBRM) parameters, and other related settings based on the CORESET associated with the detected PDCCH. A similar technique of configuring multiple MCS tables can be also applicable for PUSCH.

[0029] Fig. 2 illustrates an example system depicting the use of CORESET groups to relate the MCS tables, according to an embodiment. More specifically, Fig. 2 illustrates one example of using different CORESETs for two PDCCH transmissions. As illustrated in the example of Fig. 2, the UE may assume that eMBB transmission is scheduled in CORESET #1 or #2 with MCS table that supports 256 QAM MCS table and that eMBB transmission (or URLLC) is scheduled by CORESET #3 or #4 with MCS table that supports maximum 64 QAM entries.

[0030] In certain embodiments, a RRC update may be provided to reflect the changes for indicating different MCS tables for multi-DCI based multi-TRP scheme. For instance, Fig. 3a illustrates an example of a PDSCH configuration (PDSCH-Config) information element (IE) that may be used to configure the UE specific PDSCH parameters, according to one embodiment. As illustrated in the example of Fig. 3a, the PDSCH configuration IE comprises a mcs-Table2 entry, in addition to the mcs-Table entry. It is noted that RRC IE for CoresetPoolIndex (where values can be 0 or 1) per CORESET is supported in Release- 16. Fig. 3b illustrates an example table depicting the PDSCH-Config field descriptions, according to an example embodiment. When both mcs-Table and mcs-Table2 are configured, the UE may use the mcs-Table for the CORESETs configured with CoresetPoolIndex = 0 and may use the mcs-Table2 for the CORESETs configured with CoresetPoolIndex = 1.

[0031] According to some embodiments, for the PDSCH scheduled by a PDCCH with DCI format 1 0 or format 1 1 with CRC scrambled by C-RNTI, MCS-C-RNTI, TC-RNTI, CS-RNTI, SI-RNTI, RA-RNTI, or P-RNTI, or for the PDSCH scheduled without corresponding PDCCH transmissions using the higher-layer-provided PDSCH configuration SPS-Config, when a UE is configured by higher layer parameter PDCCH-Config that contains two different values of CoresetPoolIndex in ControlResourceSet, the UE may be configured with mcs-Table and mcs- Table2. When mcs-Table2 is configured, then mcs-Table may be used to the PDSCH scheduled by a PDCCH in ControlResourceSet having CoresetPoolIndex = 0 and mcs-Table2 may be used to the PDSCH scheduled by a PDCCH in ControlResourceSet having CoresetPoolIndex = 1.

[0032] In an embodiment, if the higher layer parameter mcs-Table or mcs-Table2 given by PDSCH-Config is set to 'qam256', and the PDSCH is scheduled by a PDCCH with DCI format 1 1 with CRC scrambled by C-RNTI, a UE may use IMCS (MCS index) and MCS Table that supports maximum 256 QAM entries to determine the modulation order (Q_m) and target code rate (R) used in the physical downlink shared channel (PDSCH). However, in an embodiment, when a UE is not configured with MCS-C-RNTI, the higher layer parameter mcs-Table or mcs-Table2 given by PDSCH-Config is set to 'qam64LowSE' and the PDSCH is scheduled by a PDCCH in a UE- specific search space with CRC scrambled by C-RNTI, the UE may use IMCS (MCS index) and MCS Table that supports maximum 64 QAM entries and lower spectral efficient entries (64LowSE QAM) to determine the modulation order (Q_m) and target code rate (R) used in the physical downlink shared channel (PDSCH). Otherwise, in certain embodiments, a UE may use IMCS (MCS index) and MCS Table that supports maximum 64 QAM entries to determine the modulation order (Q_m) and target code rate (R) used in the physical downlink shared channel (PDSCH). In some embodiments, a UE is not expected to decode a PDSCH scheduled with P-RNTI, RA-RNTI, SI- RNTI and Qm > 2.

[0033] Fig. 4a illustrates an example flow diagram of a method of MCS table to CORESETs association for multi-TRP operation, according to one example embodiment. In an example embodiment, the flow diagram of Fig. 4a may be performed by a network entity or network node associated with a communication system, such as LTE or 5G NR. For instance, in some example embodiments, the network node performing the method of Fig. 4a may comprise a base station, eNB, gNB, NG-RAN node, and/or TRP. In one example embodiment, the method of Fig. 4a may be performed by a TRP, such as that illustrated in Figs. 1 or 2.

[0034] As illustrated in the example of Fig. 4a, the method may comprise, at 300, transmitting, to one or more UE(s), a signal (e.g., RRC signal or message) indicating or configuring the UE(s) for the use of at least two different MCS tables including a first MCS table (e.g., MCS table 1) and a second MCS table (e.g., MCS table 2). In an embodiment, the transmitting 300 may comprise configuring the at least two MCS tables using RRC signalling, where the configuration can be carried within the PDSCH configuration of the BWP configuration. In some embodiments, the MCS tables may comprise 64QAM, 256QAM, and/or QAM64LowSE. In an embodiment, the transmitting 300 may further comprise indicating, for example in a PDCCH configuration (e.g., PDCCH-config parameter), at least two resource sets. According to one embodiment, the at least two resource sets may have or be associated to a resource set parameter. For example, in an embodiment, one of the at least two resource sets may have a first value for the resource set parameter and another of the at least two resource sets may have a second value for the resource set parameter, and the second value may be different from the first value. In some embodiments, the resource sets may comprise CORESETs and/or the resource set parameter may comprise a CORESET pool index. According to one embodiment, the first value for the resource set parameter may correspond to a CORESET pool index of 0 (i.e., CoresetPoolIndex= 0) and the second value for the resource set parameter may correspond to a CORESET pool index of 1 (i.e., CoresetPoolIndex= 1). In certain embodiments, each of the resource sets (e.g., CORESETs) may correspond to one or more TRP(s).

[0035] According to certain embodiments, the method may also comprise coordinating between TRPs when deciding the resource sets (e.g., CORESETs) per TRP. In one example embodiment, a TRP would not use resource sets that are assigned to another TRP. Also, in an embodiment, the method may comprise scheduling transmission with the correct (matching to the resource sets assigned) MCS table.

[0036] In some embodiments, the method of Fig. 4a may also comprise, at 310, transmitting, to the UE(s), a second signal associated with the first value for the resource set parameter and/or a third signal associated with the second value for the resource set parameter. For example, in one embodiment, the transmitting 310 may comprise transmitting a signal on at least one PDSCH associated with the CORESET pool index of 0 and/or transmitting a signal on at least one PDSCH associated with the CORESET pool index of 1. According to certain embodiments, the transmitting 310 of the second signal associated with the first value of the resource set parameter is configured to cause the UE(s) to use the first MCS table to decode the at least one PDSCH, and the transmitting 310 of the third signal associated with the second value of the resource set parameter is configured to cause the UE(s) to use the second MCS table to decode the at least one PDSCH. [0037] Fig. 4b illustrates an example flow diagram of a method of MCS table to CORESETs association for multi-TRP operation, according to one example embodiment. In an example embodiment, the flow diagram of Fig. 4b may be performed by a network entity or network node associated with a communication system, such as LTE or 5G NR. For instance, in some example embodiments, the network entity performing the method of Fig. 4b may be a UE, mobile station, IoT device, or the like. In one example embodiment, the method of Fig. 4b may be performed by the UE illustrated in Figs. 1 or 2, for instance. [0038] As illustrated in the example of Fig. 4b, the method may comprise, at 350, receiving, from a network node, a signal (e.g., RRC signal or message) indicating or configuring the use of at least two different MCS tables including a first MCS table (e.g., MCS table 1) and a second MCS table (e.g., MCS table 2). In an embodiment, the receiving 350 may comprise receiving the configuration of the at least two MCS tables using RRC signalling, where the configuration can be carried within the PDSCH (or PUSCH) configuration of the BWP configuration. In some embodiments, the MCS tables may comprise 64QAM, 256QAM, and/or QAM64FowSE. In an embodiment, the receiving 350 may further comprise receiving an indication, for example in a PDCCH configuration (e.g., PDCCH-config parameter), of at least two resource sets. According to one embodiment, the at least two resource sets may have or be associated to a resource set parameter. For example, in an embodiment, one of the at least two resource sets may have a first value for the resource set parameter and another of the at least two resource sets may have a second value for the resource set parameter, and the second value may be different from the first value. In some embodiments, the resource sets may comprise CORESETs and/or the resource set parameter may comprise a CORESET pool index. According to one embodiment, the first value for the resource set parameter may correspond to a CORESET pool index of 0 (i.e., CoresetPoolIndex= 0) and the second value for the resource set parameter may correspond to a CORESET pool index of 1 (i.e., CoresetPoolIndex= 1). In certain embodiments, each of the resource sets (e.g., CORESETs) may correspond to one or more TRP(s).

[0039] In an embodiment, the method of Fig. 4b may further comprise, at 360, receiving a second signal associated with the first value for the resource set parameter and/or receiving a third signal associated with the second value for the resource set parameter. According to certain embodiments, the receiving 360 may comprise receiving the second signal and/or third signal on at least one PDSCH. For instance, in an embodiment, the receiving 360 may comprise receiving the second signal on at least one PDSCH (or PUSCH) associated with the CORESET pool index of 0 and/or receiving the third signal on at least one PDSCH (or PUSCH) associated with the CORESET pool index of 1.

[0040] Further, in one embodiment, when receiving the second signal associated with the first value for the resource set parameter, the method may comprise, at 370, using the first MCS table to decode the second signal or the at least one PDSCH. Additionally or alternatively, in an embodiment, when receiving the third signal associated with the second value for the resource set parameter, the method may comprise, at 370, using the second MCS table to decode the third signal or the at least one PDSCH. For example, in an embodiment, the using 370 may comprise using the first MCS table to decode the PDSCH (or PUSCH) when the at least one PDSCH (or PUSCH) is associated with the CORESET pool index of 0, and/or using the second MCS table to decode the PDSCH (or PUSCH) when the at least one PDSCH (or PUSCH) is associated with the CORESET pool index of 1. In other words, according to certain embodiments, when more than one MCS table is configured for a UE, the UE may derive the MCS table to be used for receiving data from a TRP based on the CORESET(s) used by the TRP. In an embodiment, the using 370 may further comprise deriving transport block size, low density parity check (LDPC) base graph, limited buffer rate matching (LBRM) parameters, and other related settings based on the CORESET associated with the detected PDCCH (or PUSCH).

[0041] According to an embodiment, when the first MCS table or the second MCS table given by PDSCH configuration (e.g., PDSCH-config parameter) is set to 256 QAM, and the PDSCH is scheduled by a PDCCH with DCI format 1 1 with CRC scrambled by C-RNTI, the using 370 may comprise using an MCS index and MCS Table that supports 256 QAM to determine the modulation order (Q_m) and target code rate (R) used in the PDSCH. In an embodiment, when not configured with MCS-C-RNTI, and the first MCS table or the second MCS table given by PDSCH configuration (e.g., PDSCH-config parameter) is set to 64LowSE QAM and the PDSCH is scheduled by a PDCCH in a UE-specific search space with CRC scrambled by C-RNTI, the using 370 may comprise using a MCS index and MCS Table that supports 64 QAM to determine the modulation order (Q_m) and target code rate (R) used in the PDSCH. In another embodiment, as a default, the using 370 may comprise using an MCS index and MCS Table that supports 64 QAM to determine the modulation order (Q_m) and target code rate (R) used in the PDSCH.

[0042] It should be noted that, while example embodiments are discussed herein with reference to PDSCH, other embodiments are also applicable to PUSCH. Thus, the example methods for configuring multiple MCS tables discussed herein can be also applicable for PUSCH, according to certain embodiments.

[0043] Fig. 5a illustrates an example of an apparatus 10 according to an embodiment. In an embodiment, apparatus 10 may be a node, host, or server in a communications network or serving such a network. For example, apparatus 10 may be a satellite, base station, a Node B, an evolved Node B (eNB), 5G Node B or access point, next generation Node B (NG-NB or gNB), TRP, and/or WLAN access point, associated with a radio access network, such as a LTE network, 5G or NR. In example embodiments, apparatus 10 may be an eNB in LTE or gNB in 5G.

[0044] It should be understood that, in some example embodiments, apparatus 10 may be comprised of an edge cloud server as a distributed computing system where the server and the radio node may be stand-alone apparatuses communicating with each other via a radio path or via a wired connection, or they may be located in a same entity communicating via a wired connection. For instance, in certain example embodiments where apparatus 10 represents a gNB, it may be configured in a central unit (CU) and distributed unit (DU) architecture that divides the gNB functionality. In such an architecture, the CU may be a logical node that comprises gNB functions such as transfer of user data, mobility control, radio access network sharing, positioning, and/or session management, etc. The CU may control the operation of DU(s) over a front-haul interface. The DU may be a logical node that comprises a subset of the gNB functions, depending on the functional split option. It should be noted that one of ordinary skill in the art would understand that apparatus 10 may comprise components or features not shown in Fig. 5a.

[0045] As illustrated in the example of Fig. 5a, apparatus 10 may comprise a processor 12 for processing information and executing instructions or operations. Processor 12 may be any type of general or specific purpose processor. In fact, processor 12 may comprise one or more of general- purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples. While a single processor 12 is shown in Fig. 5a, multiple processors may be utilized according to other embodiments. For example, it should be understood that, in certain embodiments, apparatus 10 may comprise two or more processors that may form a multiprocessor system (e.g., in this case processor 12 may represent a multiprocessor) that may support multiprocessing. In certain embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster). [0046] Processor 12 may perform functions associated with the operation of apparatus 10, which may comprise, for example, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 10, including processes related to management of communication resources.

[0047] Apparatus 10 may further comprise or be coupled to a memory 14 (internal or external), which may be coupled to processor 12, for storing information and instructions that may be executed by processor 12. Memory 14 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and/or removable memory. For example, memory 14 can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, hard disk drive (HDD), or any other type of non-transitory machine or computer readable media. The instructions stored in memory 14 may comprise program instructions or computer program code that, when executed by processor 12, enable the apparatus 10 to perform tasks as described herein.

[0048] In an embodiment, apparatus 10 may further comprise or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium. For example, the external computer readable storage medium may store a computer program or software for execution by processor 12 and/or apparatus 10.

[0049] In some embodiments, apparatus 10 may also comprise or be coupled to one or more antennas 15 for transmitting and receiving signals and/or data to and from apparatus 10. Apparatus 10 may further comprise or be coupled to a transceiver 18 configured to transmit and receive information. The transceiver 18 may comprise, for example, a plurality of radio interfaces that may be coupled to the antenna(s) 15. The radio interfaces may correspond to a plurality of radio access technologies including one or more of GSM, NB-IoT, LTE, 5G, WLAN, Bluetooth, BT-LE, NFC, radio frequency identifier (RFID), ultrawideband (UWB), MulteFire, and the like. The radio interface may comprise components, such as filters, converters (for example, digital-to-analog converters and the like), mappers, a Fast Fourier Transform (FFT) module, and the like, to generate symbols for a transmission via one or more downlinks and to receive symbols, for example, via an uplink.

[0050] As such, transceiver 18 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 15 and demodulate information received via the antenna(s) 15 for further processing by other elements of apparatus 10. In other embodiments, transceiver 18 may be capable of transmitting and receiving signals or data directly. Additionally or alternatively, in some embodiments, apparatus 10 may comprise an input and/or output device (I/O device).

[0051] In an embodiment, memory 14 may store software modules that provide functionality when executed by processor 12. The modules may comprise, for example, an operating system that provides operating system functionality for apparatus 10. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 10. The components of apparatus 10 may be implemented in hardware, or as any suitable combination of hardware and software.

[0052] According to some embodiments, processor 12 and memory 14 may be comprised in or may form a part of processing circuitry or control circuitry. In addition, in some embodiments, transceiver 18 may be comprised in or may form a part of transceiver circuitry.

[0053] As used herein, the term “circuitry” may refer to hardware-only circuitry implementations (e.g., analog and/or digital circuitry), combinations of hardware circuits and software, combinations of analog and/or digital hardware circuits with software/firmware, any portions of hardware processor(s) with software (including digital signal processors) that work together to case an apparatus (e.g., apparatus 10) to perform various functions, and/or hardware circuit(s) and/or processor(s), or portions thereof, that use software for operation but where the software may not be present when it is not needed for operation. As a further example, as used herein, the term “circuitry” may also cover an implementation of merely a hardware circuit or processor (or multiple processors), or portion of a hardware circuit or processor, and its accompanying software and/or firmware. The term circuitry may also cover, for example, a baseband integrated circuit in a server, cellular network node or device, or other computing or network device.

[0054] As introduced above, in certain embodiments, apparatus 10 may be a network node or RAN node, such as a base station, access point, Node B, eNB, gNB, TRP, WLAN access point, or the like. According to certain embodiments, apparatus 10 may be controlled by memory 14 and processor 12 to perform the functions associated with any of the example embodiments described herein, such as the flow or signaling diagrams illustrated in Fig. 4a or Fig. 4b. In some embodiments, apparatus 10 may be configured to perform a process MCS table to CORESETs association for multi -TRP operation. In an embodiment, apparatus 10 may represent a network node, such as a gNB or TRP, for example.

[0055] In an embodiment, apparatus 10 may be controlled by memory 14 and processor 12 to transmit, to one or more UE(s), a signal (e.g., RRC signal or message) indicating or configuring the UE(s) for the use of at least two different MCS tables including a first MCS table (e.g., MCS table 1) and a second MCS table (e.g., MCS table 2). In an embodiment, apparatus 10 may be controlled by memory 14 and processor 12 to configure the use of the at least two MCS tables using RRC signalling, where the configuration can be carried within the PDSCH configuration of the BWP configuration. In some embodiments, the MCS tables may comprise 64QAM, 256QAM, and/or QAM64LowSE. In an embodiment, apparatus 10 may be controlled by memory 14 and processor 12 to indicate, for example in a PDCCH configuration (e.g., PDCCH-config parameter), at least two resource sets. According to one embodiment, the at least two resource sets may have or be associated to a resource set parameter. For example, in an embodiment, one of the at least two resource sets may have a first value for the resource set parameter and another of the at least two resource sets may have a second value for the resource set parameter, and the second value may be different from the first value. In some embodiments, the resource sets may comprise CORESETs and/or the resource set parameter may comprise a CORESET pool index. According to one embodiment, the first value for the resource set parameter may correspond to a CORESET pool index of 0 (i.e., CoresetPoolIndex= 0) and the second value for the resource set parameter may correspond to a CORESET pool index of 1 (i.e., CoresetPoolIndex= 1). In certain embodiments, each of the resource sets may correspond to one or more TRP(s).

[0056] According to certain embodiments, apparatus 10 may be controlled by memory 14 and processor 12 to coordinate between TRPs when deciding the resource sets (e.g., CORESETs) per TRP. In one example embodiment, a TRP would not use resource sets that are assigned to another TRP. Also, in an embodiment, the method may comprise scheduling transmission with the correct (matching to the resource set assigned) MCS table.

[0057] In some embodiments, apparatus 10 may be controlled by memory 14 and processor 12 to transmit, to the UE(s), a second signal associated with the first value for the resource set parameter and/or a third signal associated with the second value for the resource set parameter. For example, in one embodiment, when transmitting the second signal associated with the first value for the resource set parameter, apparatus 10 may be controlled by memory 14 and processor 12 to transmit a signal on at least one PDSCH associated with the CORESET pool index of 0. Further, in an embodiment, when transmitting the third signal associated with the second value for the resource set parameter, apparatus 10 may be controlled by memory 14 and processor 12 to transmit a signal on at least one PDSCH associated with the CORESET pool index of 1. According to certain embodiments, the transmission of the second signal associated with the first value of the resource set parameter is configured to cause the UE(s) to use the first MCS table to decode the second signal or the at least one PDSCH, and the transmission of the third signal associated with the second value of the resource set parameter is configured to cause the UE(s) to use the second MCS table to decode the third signal or the at least one PDSCH.

[0058] Fig. 5b illustrates an example of an apparatus 20 according to another embodiment. In an embodiment, apparatus 20 may be a node or element in a communications network or associated with such a network, such as a UE, mobile equipment (ME), mobile station, mobile device, stationary device, IoT device, or other device. As described herein, UE may alternatively be referred to as, for example, a mobile station, mobile equipment, mobile unit, mobile device, user device, subscriber station, wireless terminal, tablet, smart phone, IoT device, sensor or NB-IoT device, or the like. As one example, apparatus 20 may be implemented in, for instance, a wireless handheld device, a wireless plug-in accessory, or the like.

[0059] In some example embodiments, apparatus 20 may comprise one or more processors, one or more computer-readable storage medium (for example, memory, storage, or the like), one or more radio access components (for example, a modem, a transceiver, or the like), and/or a user interface. In some embodiments, apparatus 20 may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MulteFire, and/or any other radio access technologies. It should be noted that one of ordinary skill in the art would understand that apparatus 20 may comprise components or features not shown in Fig. 5b.

[0060] As illustrated in the example of Fig. 5b, apparatus 20 may comprise or be coupled to a processor 22 for processing information and executing instructions or operations. Processor 22 may be any type of general or specific purpose processor. In fact, processor 22 may comprise one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples. While a single processor 22 is shown in Fig. 5b, multiple processors may be utilized according to other embodiments. For example, it should be understood that, in certain embodiments, apparatus 20 may comprise two or more processors that may form a multiprocessor system (e.g., in this case processor 22 may represent a multiprocessor) that may support multiprocessing. In certain embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0061] Processor 22 may perform functions associated with the operation of apparatus 20 including, as some examples, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 20, including processes related to management of communication resources.

[0062] Apparatus 20 may further comprise or be coupled to a memory 24 (internal or external), which may be coupled to processor 22, for storing information and instructions that may be executed by processor 22. Memory 24 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and/or removable memory. For example, memory 24 can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, hard disk drive (HDD), or any other type of non-transitory machine or computer readable media. The instructions stored in memory 24 may comprise program instructions or computer program code that, when executed by processor 22, enable the apparatus 20 to perform tasks as described herein.

[0063] In an embodiment, apparatus 20 may further comprise or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium. For example, the external computer readable storage medium may store a computer program or software for execution by processor 22 and/or apparatus 20.

[0064] In some embodiments, apparatus 20 may also comprise or be coupled to one or more antennas 25 for receiving a downlink signal and for transmitting via an uplink from apparatus 20. Apparatus 20 may further comprise a transceiver 28 configured to transmit and receive information. The transceiver 28 may also comprise a radio interface (e.g., a modem) coupled to the antenna 25. The radio interface may correspond to a plurality of radio access technologies including one or more of GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, and the like. The radio interface may comprise other components, such as filters, converters (for example, digital-to-analog converters and the like), symbol demappers, signal shaping components, an Inverse Fast Fourier Transform (IFFT) module, and the like, to process symbols, such as OFDMA symbols, carried by a downlink or an uplink.

[0065] For instance, transceiver 28 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 25 and demodulate information received via the antenna(s) 25 for further processing by other elements of apparatus 20. In other embodiments, transceiver 28 may be capable of transmitting and receiving signals or data directly. Additionally or alternatively, in some embodiments, apparatus 20 may comprise an input and/or output device (I/O device). In certain embodiments, apparatus 20 may further comprise a user interface, such as a graphical user interface or touchscreen.

[0066] In an embodiment, memory 24 stores software modules that provide functionality when executed by processor 22. The modules may comprise, for example, an operating system that provides operating system functionality for apparatus 20. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 20. The components of apparatus 20 may be implemented in hardware, or as any suitable combination of hardware and software. According to an example embodiment, apparatus 20 may optionally be configured to communicate with apparatus 10 via a wireless or wired communications link 70 according to any radio access technology, such as NR. [0067] According to some embodiments, processor 22 and memory 24 may be comprised in or may form a part of processing circuitry or control circuitry. In addition, in some embodiments, transceiver 28 may be comprised in or may form a part of transceiving circuitry.

[0068] As discussed above, according to some embodiments, apparatus 20 may be a UE, mobile device, mobile station, ME, IoT device and/or NB-IoT device, for example. According to certain embodiments, apparatus 20 may be controlled by memory 24 and processor 22 to perform the functions associated with example embodiments described herein. For example, in some embodiments, apparatus 20 may be configured to perform one or more of the processes depicted in any of the flow charts or signaling diagrams described herein, such as those illustrated in Figs. 4a or 4b. In certain embodiments, apparatus 20 may comprise or represent a UE.

[0069] In certain embodiments, apparatus 20 may be controlled by memory 24 and processor 22 to receive, from a network node, a signal (e.g., RRC signal or message) indicating or configuring the use of at least two different MCS tables including a first MCS table (e.g., MCS table 1) and a second MCS table (e.g., MCS table 2). In an embodiment, apparatus 20 may be controlled by memory 24 and processor 22 to receive the configuration of the at least two MCS tables using RRC signalling, where the configuration can be carried within the PDSCH (or PUSCH) configuration of the BWP configuration. In some embodiments, the MCS tables may comprise 64QAM, 256QAM, and/or QAM64LowSE. In an embodiment, apparatus 20 may be controlled by memory 24 and processor 22 to receive an indication, for example in a PDCCH configuration (e.g., PDCCH-config parameter), of at least two resource sets. According to one embodiment, the at least two resource sets may have or be associated to a resource set parameter. For example, in an embodiment, one of the at least two resource sets may have a first value for the resource set parameter and another of the at least two resource sets may have a second value for the resource set parameter, and the second value may be different from the first value. In some embodiments, the resource sets may comprise CORESETs and/or the resource set parameter may comprise a CORESET pool index. According to one embodiment, the first value for the resource set parameter may correspond to a CORESET pool index of 0 (i.e., CoresetPoolIndex= 0) and the second value for the resource set parameter may correspond to a CORESET pool index of 1 (i.e., CoresetPoolIndex= 1). In certain embodiments, each of the resource sets (e.g., CORESETs) may correspond to one or more TRP(s). [0070] In an embodiment, apparatus 20 may be controlled by memory 24 and processor 22 to receive a second signal associated with the first value for the resource set parameter and/or receiving a third signal associated with the second value for the resource set parameter. According to some embodiments, the second signal and/or third signal may be received on at least one PDSCH. For instance, in an embodiment, apparatus 20 may be controlled by memory 24 and processor 22 to receive the second signal on at least one PDSCH (or PUSCH) associated with the CORESET pool index of 0 and/or to receive the third signal on at least one PDSCH (or PUSCH) associated with the CORESET pool index of 1. According to an embodiment, apparatus 20 may be controlled by memory 24 and processor 22 to use the first MCS table to decode the second signal or the PDSCH (or PUSCH) when the second signal is associated with the first value for the resource set parameter, and to use the second MCS table to decode the third signal or the PDSCH (or PUSCH) when the third signal is associated with the second value for the resource set parameter. For example, in an embodiment, apparatus 20 may be controlled by memory 24 and processor 22 to use the first MCS table to decode the PDSCH (or PUSCH) when the at least one PDSCH (or PUSCH) is associated with the CORESET pool index of 0, and/or to use the second MCS table to decode the PDSCH (or PUSCH) when the at least one PDSCH (or PUSCH) is associated with the CORESET pool index of 1. In other words, according to certain embodiments, when more than one MCS table is configured for apparatus 20, then apparatus 20 may be configured to derive the MCS table to be used for receiving data from a TRP based on the CORESET(s) used by the TRP. In an embodiment, apparatus 20 may be controlled by memory 24 and processor 22 to derive transport block size, low density parity check (LDPC) base graph, limited buffer rate matching (LBRM) parameters, and other related settings based on the CORESET associated with the detected PDCCH (or PUSCH).

[0071] According to an embodiment, when the first MCS table or the second MCS table given by PDSCH configuration (e.g., PDSCH-config parameter) is set to 256 QAM, and the PDSCH is scheduled by a PDCCH with DCI format 1 1 with CRC scrambled by C-RNTI, apparatus 20 may be controlled by memory 24 and processor 22 to use an MCS index and MCS Table that supports 256 QAM to determine the modulation order (Q_m) and target code rate (R) used in the PDSCH. In an embodiment, when apparatus 20 is not configured with MCS-C-RNTI, and the first MCS table or the second MCS table given by PDSCH configuration (e.g., PDSCH-config parameter) is set to 64LowSE QAM and the PDSCH is scheduled by a PDCCH in a UE-specific search space with CRC scrambled by C-RNTI, apparatus 20 may be controlled by memory 24 and processor 22 to use a MCS index and MCS Table that supports 64 QAM to determine the modulation order (Q_m) and target code rate (R) used in the PDSCH. In another embodiment, as a default, apparatus 20 may be controlled by memory 24 and processor 22 to use an MCS index and MCS Table that supports 64 QAM to determine the modulation order (Q_m) and target code rate (R) used in the PDSCH. [0072] Therefore, certain example embodiments provide several technological improvements, enhancements, and/or advantages over existing technological processes and constitute an improvement at least to the technological field of wireless network control and management. For example, certain embodiments may be directed to a multi-DCI multi-TRP approach that allows a

UE to receive from multiple TRPs, where the TRPs may schedule their downlink transmission towards the UE independently of each other. For example, one embodiment allows for the use of multiple MCS tables to support multi-TRP operation by applying an MCS table to CORESET association. Accordingly, the use of certain example embodiments results in improved functioning of communications networks and their nodes, such as base stations, eNBs, gNBs, TRPs, and/or UEs or mobile stations.

[0073] In some example embodiments, the functionality of any of the methods, processes, signaling diagrams, algorithms or flow charts described herein may be implemented by software and/or computer program code or portions of code stored in memory or other computer readable or tangible media, and executed by a processor.

[0074] In some example embodiments, an apparatus may be comprised or be associated with at least one software application, module, unit or entity configured as arithmetic operation(s), or as a program or portions of it (including an added or updated software routine), executed by at least one operation processor. Programs, also called program products or computer programs, including software routines, applets and macros, may be stored in any apparatus-readable data storage medium and may comprise program instructions to perform particular tasks.

[0075] A computer program product may comprise one or more computer-executable components which, when the program is run, are configured to carry out some example embodiments. The one or more computer-executable components may be at least one software code or portions of code. Modifications and configurations for implementing the functionality of an example embodiment may be performed as routine(s), which may be implemented as added or updated software routine(s). In one example, software routine(s) may be downloaded into the apparatus.

[0076] As an example, software or computer program code or portions of code may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program. Such carriers may comprise a record medium, computer memory, read-only memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and/or software distribution package, for example. Depending on the processing power needed, the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers. The computer readable medium or computer readable storage medium may be a non-transitory medium.

[0077] In other example embodiments, the functionality may be performed by hardware or circuitry comprised in an apparatus, for example through the use of an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array

(FPGA), or any other combination of hardware and software. In yet another example embodiment, the functionality may be implemented as a signal, such as a non-tangible means, that can be carried by an electromagnetic signal downloaded from the Internet or other network.

[0078] According to an example embodiment, an apparatus, such as a node, device, or a corresponding component, may be configured as circuitry, a computer or a microprocessor, such as single-chip computer element, or as a chipset, which may comprise at least a memory for providing storage capacity used for arithmetic operation(s) and/or an operation processor for executing the arithmetic operation(s).

[0079] One having ordinary skill in the art will readily understand that the example embodiments as discussed above may be practiced with procedures in a different order, and/or with hardware elements in configurations which are different than those which are disclosed. Therefore, although some embodiments have been described based upon these example embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of example embodiments.

[0080] A first embodiment is directed to a method, which may comprise receiving, at a user equipment, a signal configuring a use of at least two different modulation and coding scheme (MCS) tables comprising a first MCS table and a second MCS table, and receiving an indication of at least two resource sets (e.g., CORESETs). One of the at least two resource sets has a first value for the resource set parameter and another of the at least two resource sets has a second value for the resource set parameter. The second value may be different from the first value, and each of the at least two resource sets may correspond to at least one transmit receive point (TRP). When receiving at least one second signal associated with the first value for the resource set parameter, the method may comprise using the first MCS table to decode the at least one second signal. When receiving at least one third signal associated with the second value for the resource set parameter, the method may comprise using the second MCS table to decode the at least one third signal.

[0081] In a variant, the receiving of the signal configuring the use of at least two different MCS tables comprises receiving the configuration of the at least two MCS tables using RRC signalling, where the configuration can be carried within the PDSCH configuration.

[0082] According to a variant, the receiving of the indication comprises receiving the at least two resource sets in a PDCCH configuration parameter.

[0083] In a variant, the receiving of the second signal and/or the third signal comprises receiving the second signal and/or third signal on at least one PDSCH.

[0084] In one variant, the resource sets may comprise CORESETs. In another variant, the resource set parameter may comprise a CORESET pool index. [0085] In some variants, the first value for the resource set parameter may be a CORESET pool index of 0 and the second value for the resource set parameter may be a CORESET pool index of 1. [0086] In a variant, the at least two MCS tables comprise at least one of 64QAM, 256QAM, or QAM64LowSE.

[0087] According to a variant, the method may further comprise deriving transport block size, low density parity check (LDPC) base graph, limited buffer rate matching (LBRM) parameters, and other related settings based on the CORESET associated with the detected physical downlink control channel (PDCCH).

[0088] In a variant, when the first MCS table or the second MCS table given by PDSCH configuration is set to 256 QAM, and the PDSCH is scheduled by a PDCCH with DCI format 1 1 with CRC scrambled by C-RNTI, the using comprises using an MCS index and MCS Table that supports 256 QAM to determine the modulation order (Q_m) and target code rate (R) used in the PDSCH.

[0089] According to a variant, when the user equipment is not configured with MCS-C-RNTI, and the first MCS table or the second MCS table given by PDSCH configuration is set to 64LowSE QAM and the PDSCH is scheduled by a PDCCH in a user equipment-specific search space with CRC scrambled by C-RNTI, the using comprises using a MCS index and MCS Table that supports 64 QAM to determine the modulation order (Q_m) and target code rate (R) used in the PDSCH. [0090] In a variant, the using comprises using an MCS index and MCS Table that supports 64 QAM to determine the modulation order (Q_m) and target code rate (R) used in the PDSCH.

[0091] A second embodiment is directed to a method, which may comprise transmitting, from a network node, a signal configuring at least one user equipment for use of at least two different modulation and coding scheme (MCS) tables comprising a first MCS table and a second MCS table. The signal may comprise an indication of at least two resource sets, where each resource set is associated to a resource set parameter. One of the at least two resource sets has a first value for the resource set parameter and another of the at least two resource sets has a second value for the resource set parameter, the second value being different from the first value. Each of the at least two resource sets may correspond to at least one TRP. The method may also comprise transmitting, to the at least one user equipment, at least one of a second signal associated with the first value for the resource set parameter or a third signal associated with the second value for the resource set parameter. The transmitting of the at least one second signal associated with the first value for the resource set parameter is configured to cause the at least one user equipment to use the first modulation and coding scheme table to decode the at least one second signal, and the transmitting of the at least one third signal associated with the second value for the resource set parameter is configured to cause the at least one user equipment to use the second modulating and coding scheme table to decode the at least one third signal.

[0092] In a variant, the transmitting of the signal configuring the use of at least two different MCS tables comprises transmitting the configuration of the at least two MCS tables using RRC signalling, where the configuration can be carried within the PDSCH configuration.

[0093] In a variant, the at least two MCS tables comprise at least one of 64QAM, 256QAM, or QAM64LowSE.

[0094] A third embodiment is directed to an apparatus including at least one processor and at least one memory comprising computer program code. The at least one memory and computer program code may be configured, with the at least one processor, to cause the apparatus at least to perform the method according to the first embodiment, the second embodiment, and/or any other embodiments discussed herein, or any of the variants described above.

[0095] A fourth embodiment is directed to an apparatus that may comprise circuitry configured to perform the method according to the first embodiment, the second embodiment, and/or any other embodiments discussed herein, or any of the variants described above.

[0096] A fifth embodiment is directed to an apparatus that may comprise means for performing the method according to the first embodiment, the second embodiment, and/or any other embodiments discussed herein, or any of the variants described above.

[0097] A sixth embodiment is directed to a non-transitory computer readable medium comprising program instructions stored thereon for performing at least the method according to the first embodiment, the second embodiment, and/or any other embodiments discussed herein, or any of the variants described above.

Claims

We Claim:

1. A method, comprising: receiving, at a user equipment, a first signal configuring a use of at least two different modulation and coding scheme tables comprising a first modulation and coding scheme table and a second modulation and coding scheme table; receiving an indication of at least two resource sets, wherein each resource set is associated to a resource set parameter, wherein one of the at least two resource sets has a first value for the resource set parameter and another of the at least two resource sets has a second value for the resource set parameter, the second value being different from the first value, wherein each of the at least two resource sets corresponds to at least one transmit receive point; when receiving a second signal associated with the first value for the resource set parameter, using the first modulation and coding scheme table to decode the second signal; and when receiving a third signal associated with the second value for the resource set parameter, using the second modulation and coding scheme table to decode the third signal.

2. The method according to claim 1, wherein the receiving of the first signal configuring the use of at least two different modulation and coding scheme tables comprises receiving the configuration of the at least two modulation and coding scheme tables using radio resource control signalling, where the configuration can be carried within a physical downlink shared channel configuration.

3. The method according to claims 1 or 2, wherein the receiving of the indication comprises receiving the at least two resource sets in a physical downlink control channel configuration parameter.

4. The method according to any of claims 1-3, wherein the receiving of the second signal comprises receiving the second signal on a physical downlink shared channel, and wherein the receiving of the third signal comprises receiving the third signal on a physical downlink shared channel.

5. The method according to any of claims 1-4, wherein the at least two resource sets comprise control resource sets (CORESETs).

6. The method according to any of claims 1-5, wherein the resource set parameter comprises a control resource set (CORESET) pool index.

7. The method according to any of claims 1-6, wherein the first value for the resource set parameter comprises a control resource set (CORESET) pool index of 0, and wherein the second value for the resource set parameter comprises a control resource set (CORESET) pool index of 1.

8. The method according to any of claims 1-7, wherein the at least two modulation and coding scheme tables comprise at least one of 64QAM, 256QAM, or QAM64LowSE.

9. The method according to any of claims 1-8, further comprising deriving transport block size, low density parity check (LDPC) base graph, limited buffer rate matching (LBRM) parameters, and other related settings based on the resource set associated with the detected physical downlink control channel (PDCCH).

10. The method according to any of claims 1-9, wherein, when the first modulation and coding scheme table or the second modulation and coding scheme table given by physical downlink shared channel configuration is set to 256 QAM, and the physical downlink shared channel is scheduled by a physical downlink control channel with downlink control information format 1 1 with cyclic redundancy check scrambled by cell radio network temporary identifier (C-RNTI), the using comprises using a modulation and coding scheme index and modulation and coding scheme table that supports 256 QAM to determine the modulation order (Q_m) and target code rate (R) used in the physical downlink shared channel.

11. The method according to any of claims 1-10, wherein, when the user equipment is not configured with modulation and coding scheme cell radio network temporary identifier (MCS-C- RNTI), and the first modulation and coding scheme table or the second modulation and coding scheme table given by physical downlink shared channel configuration is set to 64LowSE QAM and the physical downlink shared channel is scheduled by a physical downlink control channel in a user equipment-specific search space with cyclic redundancy check scrambled by cell radio network temporary identifier (C-RNTI), the using comprises using a modulation and coding scheme index and modulation and coding scheme table that supports 64 QAM to determine the modulation order (Q_m) and target code rate (R) used in the physical downlink shared channel.

12. The method according to any of claims 1-11, wherein, the using comprises using modulation and coding scheme index and modulation and coding scheme table that supports 64 QAM to determine the modulation order (Q_m) and target code rate (R) used in the physical downlink shared channel.

13. The method according to any of claims 1-12, wherein the first signal comprises the indication of the at least two resource sets.

14. A method, comprising: transmitting, from a network node, a first signal configuring at least one user equipment for a use of at least two different modulation and coding scheme tables comprising a first modulation and coding scheme table and a second modulation and coding scheme table, wherein the signal further comprises an indication of at least two resource sets, wherein each resource set is associated to a resource set parameter, wherein one of the at least two resource sets has a first value for the resource set parameter and another of the at least two resource sets has a second value for the resource set parameter, the second value being different from the first value, and wherein each of the at least two resource sets corresponds to at least one transmit receive point; transmitting, to the at least one user equipment, at least one of a second signal associated with the first value for the resource set parameter or a third signal associated with the second value for the resource set parameter; wherein the transmitting of the at least one second signal associated with the first value for the resource set parameter is configured to cause the at least one user equipment to use the first modulation and coding scheme table to decode the at least one second signal, and the transmitting of the at least one third signal associated with the second value for the resource set parameter is configured to cause the at least one user equipment to use the second modulating and coding scheme table to decode the at least one third signal.

15. The method according to claim 14, wherein the transmitting of the signal configuring the use of at least two different modulation and coding scheme tables comprises transmitting the configuration of the at least two modulation and coding scheme tables using radio resource control signalling, where the configuration can be carried within a physical downlink shared channel configuration.

16. The method according to claims 14 or 15, wherein the at least two modulation and coding scheme tables comprise at least one of 64QAM, 256QAM, or QAM64LowSE.

17. The method according to any of claims 14-16, wherein the transmitting of the indication comprises transmitting the at least two resource sets in a physical downlink control channel configuration parameter.

18. The method according to any of claims 14-17, wherein the transmitting of the second signal comprises transmitting the second signal on a physical downlink shared channel, and wherein the transmitting of the third signal comprises transmitting the third signal on a physical downlink shared channel.

19. The method according to any of claims 14-18, wherein the at least two resource sets comprise control resource sets (CORESETs).

20. The method according to any of claims 14-19, wherein the resource set parameter comprises a control resource set (CORESET) pool index.

21. The method according to any of claims 14-20, wherein the first value for the resource set parameter comprises a control resource set (CORESET) pool index of 0, and wherein the second value for the resource set parameter comprises a control resource set (CORESET) pool index of 1.

22. An apparatus, comprising: at least one processor; and at least one memory comprising computer program code, the at least one memory and computer program code are configured, with the at least one processor, to cause the apparatus at least to: receive a first signal configuring a use of at least two different modulation and coding scheme tables comprising a first modulation and coding scheme table and a second modulation and coding scheme table; receive an indication of at least two resource sets, wherein each resource set is associated to a resource set parameter, wherein one of the at least two resource sets has a first value for the resource set parameter and another of the at least two resource sets has a second value for the resource set parameter, the second value being different from the first value, wherein each of the at least two resource sets corresponds to at least one transmit receive point; when receiving a second signal associated with the first value for the resource set parameter, use the first modulation and coding scheme table to decode the second signal; and when receiving a third signal associated with the second value for the resource set parameter, use the second modulation and coding scheme table to decode the third signal.

23. The apparatus according to claim 22, wherein, when receiving the first signal configuring the use of at least two different modulation and coding scheme tables, the at least one memory and computer program code are configured, with the at least one processor, to cause the apparatus at least to receive the configuration of the at least two modulation and coding scheme tables using radio resource control signalling, where the configuration can be carried within a physical downlink shared channel configuration.

24. The apparatus according to claims 22 or 23, wherein, when receiving the indication, the at least one memory and computer program code are configured, with the at least one processor, to cause the apparatus at least to receive the at least two resource sets in a physical downlink control channel configuration parameter.

25. The apparatus according to any of claims 22-24, wherein, when receiving the second signal, the at least one memory and computer program code are configured, with the at least one processor, to cause the apparatus at least to receive the second signal on a physical downlink shared channel, and, when receiving the third signal, the at least one memory and computer program code are configured, with the at least one processor, to cause the apparatus at least to receive the third signal on a physical downlink shared channel.

26. The apparatus according to any of claims 22-25, wherein the at least two resource sets comprise control resource sets (CORESETs).

27. The apparatus according to any of claims 22-26, wherein the resource set parameter comprises a control resource set (CORESET) pool index.

28. The apparatus according to any of claims 22-27, wherein the first value for the resource set parameter comprises a control resource set (CORESET) pool index of 0, and wherein the second value for the resource set parameter comprises a control resource set (CORESET) pool index of 1.

29. The apparatus according to any of claims 22-28, wherein the at least two modulation and coding scheme tables comprise at least one of 64QAM, 256QAM, or QAM64LowSE.

30. The apparatus according to any of claims 22-29, wherein the at least one memory and computer program code are configured, with the at least one processor, to cause the apparatus at least to derive transport block size, low density parity check (LDPC) base graph, limited buffer rate matching (LBRM) parameters, and other related settings based on the resource set associated with the detected physical downlink control channel (PDCCH).

31. The apparatus according to any of claims 22-30, wherein, when the first modulation and coding scheme table or the second modulation and coding scheme table given by physical downlink shared channel configuration is set to 256 QAM, and the physical downlink shared channel is scheduled by a physical downlink control channel with downlink control information format 1 1 with cyclic redundancy check scrambled by cell radio network temporary identifier (C-RNTI), the at least one memory and computer program code are configured, with the at least one processor, to cause the apparatus at least to use a modulation and coding scheme index and modulation and coding scheme table that supports 256 QAM to determine the modulation order (Q_m) and target code rate (R) used in the physical downlink shared channel.

32. The apparatus according to any of claims 22-31, wherein, when the apparatus is not configured with modulation and coding scheme cell radio network temporary identifier (MCS-C-RNTI), and the first modulation and coding scheme table or the second modulation and coding scheme table given by physical downlink shared channel configuration is set to 64LowSE QAM and the physical downlink shared channel is scheduled by a physical downlink control channel in a user equipment- specific search space with cyclic redundancy check scrambled by cell radio network temporary identifier (C-RNTI), the at least one memory and computer program code are configured, with the at least one processor, to cause the apparatus at least to use a modulation and coding scheme index and modulation and coding scheme table that supports 64 QAM to determine the modulation order (Q_m) and target code rate (R) used in the physical downlink shared channel.

33. The apparatus according to any of claims 22-32, wherein, the using comprises using modulation and coding scheme index and modulation and coding scheme table that supports 64 QAM to determine the modulation order (Q_m) and target code rate (R) used in the physical downlink shared channel.

34. The apparatus according to any of claims 22-33, wherein the first signal comprises the indication of the at least two resource sets.

35. An apparatus, comprising: at least one processor; and at least one memory comprising computer program code, the at least one memory and computer program code are configured, with the at least one processor, to cause the apparatus at least to: transmit a first signal configuring at least one user equipment for a use of at least two different modulation and coding scheme tables comprising a first modulation and coding scheme table and a second modulation and coding scheme table, wherein the signal further comprises an indication of at least two resource sets, wherein each resource set is associated to a resource set parameter, wherein one of the at least two resource sets has a first value for the resource set parameter and another of the at least two resource sets has a second value for the resource set parameter, the second value being different from the first value, and wherein each of the at least two resource sets corresponds to at least one transmit receive point; transmit, to the at least one user equipment, at least one of a second signal associated with the first value for the resource set parameter or a third signal associated with the second value for the resource set parameter; wherein the transmitting of the at least one second signal associated with the first value for the resource set parameter is configured to cause the at least one user equipment to use the first modulation and coding scheme table to decode the at least one signal, and the transmitting of the at least one second signal associated with the second value for the resource set parameter is configured to cause the at least one user equipment to use the second modulating and coding scheme table to decode the at least one signal.

36. The apparatus according to claim 35, wherein, when transmitting the signal configuring the use of at least two different modulation and coding scheme tables, the at least one memory and computer program code are configured, with the at least one processor, to cause the apparatus at least to transmit the configuration of the at least two modulation and coding scheme tables using radio resource control signalling, where the configuration can be carried within a physical downlink shared channel configuration.

37. The apparatus according to claims 35 or 36, wherein the at least two modulation and coding scheme tables comprise at least one of 64QAM, 256QAM, or QAM64LowSE.

38. The apparatus according to any of claims 35-37, wherein, when transmitting the indication, the at least one memory and computer program code are configured, with the at least one processor, to cause the apparatus at least to transmit the at least two resource sets in a physical downlink control channel configuration parameter.

39. The apparatus according to any of claims 35-38, wherein, when transmitting the second signal, the at least one memory and computer program code are configured, with the at least one processor, to cause the apparatus at least to transmit the second signal on a physical downlink shared channel, and, when transmitting the third signal, the at least one memory and computer program code are configured, with the at least one processor, to cause the apparatus at least to transmit the third signal on a physical downlink shared channel.

40. The apparatus according to any of claims 35-39, wherein the at least two resource sets comprise control resource sets (CORESETs).

41. The apparatus according to any of claims 35-40, wherein the resource set parameter comprises a control resource set (CORESET) pool index.

42. The apparatus according to any of claims 35-41, wherein the first value for the resource set parameter comprises a control resource set (CORESET) pool index of 0, and wherein the second value for the resource set parameter comprises a control resource set (CORESET) pool index of 1.

43. An apparatus, comprising: means for performing the method according to any of claims 1-21.

44. An apparatus, comprising: circuitry configured to perform the method according to any of claims 1-21.

45. A computer readable medium comprising program instructions stored thereon for performing at least the method according to any of claims 1-21.