WO2024072413A1

WO2024072413A1 - Method for supporting changing transmission parameters of multi-physical downlink shared channel/physical uplink shared channel for extended reality applications

Info

Publication number: WO2024072413A1
Application number: PCT/US2022/045394
Authority: WO
Inventors: Zexian Li; Margarita GAPEYENKO
Original assignee: Nokia Technologies Oy; Nokia Of America Corporation
Priority date: 2022-09-30
Filing date: 2022-09-30
Publication date: 2024-04-04

Abstract

Systems, methods, apparatuses, and computer program products for indicating changes of transmitting parameters for multi-PxSCH transmission. One method may include receiving, from a network entity, a configuration for at least one of multi-PxSCH transmission or PxSCH indicating at least one transmitting parameter to be adjusted, and receiving DCI scheduling at least one of the multi-PxSCH transmissions comprising at least one activation indication.

Description

TITLE:

METHOD FOR SUPPORTING CHANGING TRANSMISSION PARAMETERS OF MULTI-PHYSICAL DOWNLINK SHARED CHANNEL/PHYSICAL UPLINK SHARED CHANNEL FOR EXTENDED REALITY APPLICATIONS

TECHNICAL FIELD:

[0001] Some example embodiments may generally relate to mobile or wireless telecommunication systems, such as 3^rd Generation Partnership Project (3GPP) Long Term Evolution (LTE), 5^th generation (5G) radio access technology (RAT), new radio (NR) access technology, 6^th generation (6G), and/or other communications systems. For example, certain example embodiments may relate to systems and/or methods for indicating changes of transmitting parameters for multi-physical downlink shared channel (PDSCH)/physical uplink shared channel (PUSCH) (PxSCH) transmission.

BACKGROUND:

[0002] Examples of mobile or wireless telecommunication systems may include radio frequency (RF) 5G RAT, the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), LTE Evolved UTRAN (E-UTRAN), LTE-Advanced (LTE-A), LTE-A Pro, NR access technology, MulteFire Alliance and/or 6G. 5G wireless systems refer to the next generation (NG) of radio systems and network architecture. A 5G system is typically built on a 5G NR, but a 5G (or NG) network may also be built on E- UTRA radio. It is expected that NR can support service categories such as enhanced mobile broadband (eMBB), ultra-reliable low-latency- communication (URLLC), and massive machine-type communication (mMTC). NR is expected to deliver extreme broadband, ultra-robust, low- latency connectivity, and massive networking to support the Internet of Things (loT). The next generation radio access network (NG-RAN) represents the radio access network (RAN) for 5G, which may provide radio access for NR, LTE, and LTE-A. It is noted that the nodes in 5G providing radio access functionality to a user equipment (e.g., similar to the Node B in UTRAN or the Evolved Node B (eNB) in LTE) may be referred to as next-generation Node B (gNB) when built on NR radio, and may be referred to as next-generation eNB (NG-eNB) when built on E-UTRA radio.

SUMMARY:

[0003] In accordance with some example embodiments, a method may include receiving, from a network entity, a configuration for at least one of multiple physical downlink shared channel or physical uplink shared channel (PxSCH) transmission indicating at least one transmitting parameter to be adjusted. The method may further include receiving downlink control information scheduling at least one of the multiple PxSCH transmissions comprising at least one activation indication.

[0004] In accordance with certain example embodiments, an apparatus may include means for receiving, from a network entity, a configuration for at least one of multiple physical downlink shared channel or physical uplink shared channel (PxSCH) transmission indicating at least one transmitting parameter to be adjusted. The apparatus may further include means for receiving downlink control information scheduling at least one of the multiple PxSCH transmissions comprising at least one activation indication.

[0005] In accordance with various example embodiments, a non-transitory computer readable medium may include program instructions that, when executed by an apparatus, cause the apparatus to perform at least a method. The method may include receiving, from a network entity, a configuration for at least one of multiple physical downlink shared channel or physical uplink shared channel (PxSCH) transmission indicating at least one transmitting parameter to be adjusted. The method may further include receiving downlink control information scheduling at least one of the multiple PxSCH transmissions comprising at least one activation indication.

[0006] In accordance with some example embodiments, a computer program product may perform a method. The method may include receiving, from a network entity, a configuration for at least one of multiple physical downlink shared channel or physical uplink shared channel (PxSCH) transmission indicating at least one transmitting parameter to be adjusted. The method may further include receiving downlink control information scheduling at least one of the multiple PxSCH transmissions comprising at least one activation indication.

[0007] In accordance with certain example embodiments, an apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to receive, from a network entity, a configuration for at least one of multiple physical downlink shared channel or physical uplink shared channel (PxSCH) transmission indicating at least one transmitting parameter to be adjusted. The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to receive downlink control information scheduling at least one of the multiple PxSCH transmissions comprising at least one activation indication.

[0008] In accordance with various example embodiments, an apparatus may include receiving circuitry configured to receive, from a network entity, a configuration for at least one of multiple physical downlink shared channel or physical uplink shared channel (PxSCH) transmission indicating at least one transmitting parameter to be adjusted. The apparatus may further include receiving circuitry configured to receiving downlink control information scheduling at least one of the multiple PxSCH transmissions comprising at least one activation indication.

[0009] In accordance with some example embodiments, a method may include transmitting, to a user equipment, a configuration for at least one of multiple physical downlink shared channel or physical uplink shared channel (PxSCH) transmission indicating at least one transmitting parameter to be adjusted. The method may further include transmitting downlink control information scheduling at least one of the multiple PxSCH transmissions comprising at least one activation indication.

[0010] In accordance with certain example embodiments, an apparatus may include means for transmitting, to a user equipment, a configuration for at least one of multiple physical downlink shared channel or physical uplink shared channel (PxSCH) transmission indicating at least one transmitting parameter to be adjusted. The apparatus may further include means for transmitting downlink control information scheduling at least one of the multiple PxSCH transmissions comprising at least one activation indication.

[0011] In accordance with various example embodiments, a non-transitory computer readable medium may include program instructions that, when executed by an apparatus, cause the apparatus to perform at least a method. The method may include transmitting, to a user equipment, a configuration for at least one of multiple physical downlink shared channel or physical uplink shared channel (PxSCH) transmission indicating at least one transmitting parameter to be adjusted. The method may further include transmitting downlink control information scheduling at least one of the multiple PxSCH transmissions comprising at least one activation indication.

[0012] In accordance with some example embodiments, a computer program product may perform a method. The method may include transmitting, to a user equipment, a configuration for at least one of multiple physical downlink shared channel or physical uplink shared channel (PxSCH) transmission indicating at least one transmitting parameter to be adjusted. The method may further include transmitting downlink control information scheduling at least one of the multiple PxSCH transmissions comprising at least one activation indication.

[0013] In accordance with certain example embodiments, an apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to transmit, to a user equipment, a configuration for at least one of multiple physical downlink shared channel or physical uplink shared channel (PxSCH) transmission indicating at least one transmitting parameter to be adjusted. The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to transmit downlink control information scheduling at least one of the multiple PxSCH transmissions comprising at least one activation indication.

[0014] In accordance with various example embodiments, an apparatus may include transmitting circuitry configured to transmit, to a user equipment, a configuration for at least one of multiple physical downlink shared channel or physical uplink shared channel (PxSCH) transmission indicating at least one transmitting parameter to be adjusted. The apparatus may further include transmitting circuitry configured to transmit downlink control information scheduling at least one of the multiple PxSCH transmissions comprising at least one activation indication.

BRIEF DESCRIPTION OF THE DRAWINGS:

[0015] For a proper understanding of example embodiments, reference should be made to the accompanying drawings, wherein:

[0016] FIG. 1 illustrates an example of extended reality packets transmission with multi-PxSCH.

[0017] FIG. 2 illustrates an example of a signaling diagram according to certain example embodiments.

[0018] FIG. 3 illustrates an example of a flow diagram of a method according to some example embodiments.

[0019] FIG. 4 illustrates an example of a flow diagram of another method according to various example embodiments.

[0020] FIG. 5 illustrates an example of various network devices according to certain example embodiments. [0021] FIG. 6 illustrates an example of a 5G network and system architecture according to some example embodiments.

DETAILED DESCRIPTION:

[0022] 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 indicating changes of transmitting parameters for multi -PxS CH transmission is not intended to limit the scope of certain example embodiments, but is instead representative of selected example embodiments.

[0023] 3 GPP RAN Rel-18 is continuing to develop enhancements for extended reality (XR), particularly for XR-awareness in RAN, XR-specific power sharing, and XR-specific capacity improvements. With respect to XR- specific capacity improvements, 3GPP RAN Rel-18 seeks to provide more efficient resource allocation and scheduling for XR service characteristics (e.g., periodicity, multiple flows, jitter, latency, reliability) through a series of semi-persistent scheduling (SPS), configured grant (CG), and dynamic scheduling/grant enhancements. The dynamic scheduling/grant enhancements under consideration include determining how to support candidate capacity enhancement techniques for XR traffic based dynamic scheduling/grant transmissions, and in particular, allowing different configurations per PDSCH/PUSCH. In this regard, 3GPP RAN Rel-18 seeks to support single downlink control information (DCI) scheduling multi- PDSCHs, which are currently supported for frequency range (FR)2-2 (z.e., 52.6 - 71 GHz where larger subcarrier spacing may be used) to other subcarrier spacing (SCS) in FR1/FR2.

[0024] Dynamic grant (DG)-based scheduling may serve the XR traffic with varying and large-sized application packets/bursts, as well as possible jitter for downlink (DL) video and uplink (UL) pose information traffic (z.e., a position and orientation in space relative to an XR space). Further developments are expected on scheduling multi -PDSCHs/PUSCHs (e.g., multi -PxS CH) with a single DCI based on what has been specified in 3 GPP Rel-17, and based upon specific aspects resulting from XR traffic.

[0025] The multi -PxSCH framework of 3GPP Rel-17 may allow adjustment of the time allocation of the transport blocks (TBs) scheduled by the same multi-PxSCH DCI. This is possible because the DCI may indicate a row of a radio resource control (RRC)-configured time domain resource allocation (TDRA) table, where a different start and length indicator value (SLIV) can be given to each TB. In contrast, current multi-PxSCH does not allow changes of modulation and coding schemes (MCS) and physical resource block (PRB) allocation across the TBs scheduled together.

[0026] Such static/semi-static allocation of MCS and PRBs may be a limiting factor for XR services. For example, FIG. 1 depicts 6 TBs that need to be carried for the same video frame. In case with an even larger video frame size, more dynamic channel conditions, and reduced UE capabilities, the impacts due to static/semi-static allocation may worsen. Even with the scenario shown in FIG. 1, real transmission time for the first TB in the video frame may be much longer than the last TB (i.e., T1>T2).

[0027] In order to simultaneously fulfill the requirements of packet delay budget (PDB) and reliability, robust MCS schemes may be used for all TBs carrying the same video frame over multiple PDSCHs. Overall system efficiency may be reduced since the possible retransmission for the earlier scheduled TBs may not be utilized. Alternatively, if ineffective MCS schemes are applied to all TBs, the reliability of the last TB may be significantly reduced, thereby reducing the quality of the entire video frame, and harming the end user experience. Although the applied MCS schemes may be included in the DCI; however, this may increase overhead since, for each MCS scheme, 5 bits would be required. Thus, with variable 5G system conditions and XR traffic characteristics, it may be desirable to improve system performance by considering both spectral efficiency (e.g., control signalling overhead) and user experience with multi-PxSCH transmission.

[0028] Certain example embodiments described herein may have various benefits and/or advantages to overcome the disadvantages described above. For example, certain example embodiments may enable a base station to indicate changes of certain transmitting parameters (e.g., MCS for multi-PxSCH transmission) without introducing heavy signalling overhead. Thus, certain example embodiments discussed below are directed to improvements in computer-related technology.

[0029] FIG. 2 illustrates an example of a signaling diagram depicting for enabling a base station to indicate changes of certain transmitting parameters for multi-PxSCH transmission. NE 220 and UE 210 may be similar to NE 510 and UE 520, respectively, as illustrated in FIG. 5, according to certain example embodiments.

[0030] At 201, NE 220 may configure a rule for multi-PxSCH transmission that specifies, for example, which and how transmitting parameters may be changed from one PxSCH transmission to another transmission.

[0031] At 202, once the rule is received by UE 210, NE 220 may transmit DCI scheduling multi-PDSCHs to UE 210, where multi-PDSCH transmission is provided as one example. As an example, an activation indication may be included in the scheduling DCI.

[0032] In some example embodiments, NE 220 may configure UE 210 with which transmission parameters may be changed from a first PxSCH transmission to a second PxSCH transmission associated with one DCI scheduling multi-PxSCH transmission. As an example, the transmission parameters may include Tx power, MCS, a number of repetitions, frequency hopping, multiple input multiple output (MIMO) schemes, etc.

[0033] Additionally, NE 220 may configure UE 210 with step values indicative of changed transmission parameters. For example, Tx power may be increased by 2 dB from one transmission to another; this may be one level more robust MCS (e.g., based on an MCS table, such as Table 1 below) selection from one transmission to another. Various bit maps may be used to indicate the rules for changing the transmitting parameters (e.g., 000: no changes; 001 : only the last TB may use the lower MCS; 010: decrease MCS for every TB). This may be conveyed with DCI. The exact number of bits may depend on the number of rules configured. In some examples, one bit in the bit-map may correspond to one PDSCH occasion which may be used to indicate whether the MCS applied to the current PDSCH occasion may be different from the previous PDSCH occasion.

[0034] In various example embodiments, delta transmission parameters may also be included in the scheduling DCI. In an example of changing MCS scheme from one transmission to another, with RRC configuration, UE 210 may know that the MCS schemes from one transmission of PxSCHs to another transmission of PxSCHs are different. DCI may be used to indicate the change steps, for example, moving towards more robust MCS scheme. Table 1 below shows an example rule, where from one PDSCH transmission to another one, one level more robust MCS is applied. As MCS Index IMCS decreases, the MCS changing rule may become one level more robust, and MCS may be associated with a subsequent PDSCH.

Table 1: Example for MCS changing rules from one PDSCH transmission to another PDSCH transmission

[0035] In various example embodiments, in addition to the changing steps, RRC may configure one bit-map for such transmitting parameter change. In an example with four PDSCHs scheduled for one video frame, one bit-map may be [0011], wherein the first two transmissions may use the same transmitting parameters following the scheduling DCI, and the last two transmissions may use different transmitting parameters. Thus, DCI may be used to indicate whether configured changes should be applied. In this example, “0” may indicate no change of transmitting parameters comparing to the previous transmission (z.e., all PxSCH will use the same transmitting parameters), while “1” may indicate applying the configured transmitting parameter change compared to the previous transmission. It is noted that only 1 -bit overhead would be included in scheduling DCI.

[0036] Certain example embodiments may include changing multiple transmitting parameters (e.g., both MCS level and Tx power), wherein multiple bits may be utilized in the DCI if individual transmitting parameters need to be changed (z.e., one bit corresponding with one transmitting parameter). Some example embodiments may include applying different rules for transmitting parameters; in this case, DCI may include extra bits to notify UE 210 which MCS that UE 210 should apply to the remaining TBs. The different rules may be pre-defined via RRC or indicated via other protocol signalling (e.g, MAC CE).

[0037] Certain example embodiments may include explicitly indicating the transmitting parameters to be used in the multi-PxSCH in the DCI. As one example, the MCS parameter used for the 1^st PDSCH may be indicated in the scheduling DCI, and additional bits with the same DCI may indicate the change in MCS from one PxSCH to another PxSCH transmission. In an example where 4 PDSCHs are scheduled, the MCS parameter used for the 1^st PDSCH may be explicitly indicated in DCI, and an additional 3 bits may indicate the change in MCS for the remaining 3 PDSCHs. For example, “011,” “0” may indicate that the 2^nd PDSCH is using the same MCS as the 1^st PDSCH. The second bit “1” may indicate that the MCS used for the 3^rd PDSCH is different from the MCS used for the 2^nd PDSCH, and the third bit “1” may indicate that the MCS used for the 4^th PDSCH is different from the MCS used for the 3^rd PDSCH.

[0038] Various example embodiments may use semi-static RRC configuration-based activation. Specifically, after RRC configuration is completed, UE 210 may automatically apply the RRC configuration to the scheduled multiple PxSCHs, without requiring dynamic indications in DCI. This may provide the advantage of no additional bits being required in the scheduling DCI.

[0039] Certain example embodiments may include medium access control (MAC) control element (CE)-based activation. In particular, once the RRC configuration is completed, MAC CE may carry activation indications in the 1^st PDSCH transmission. The technique may only apply to PDSCH. [0040] At 203, NE 220 may transmit to UE 210 a first PDSCH transmission with the format according to the scheduling DCI. In some example embodiments, the transmitting parameters (e.g., MCS, HARQ process ID, RV) may be applied to the first PDSCH transmission.

[0041] At 204, NE 220 may transmit to UE 210 a second PDSCH transmission with different transmitting parameters according to RRC configuration. In various example embodiment, UE 210 may learn that the RRC configured rule is activated after decoding the DCI scheduling multi-PDSCH carrying activation indication at 202. UE 210 may decode the received 2^nd PDSCH with the updated parameters based on the rule configured by RRC. In some example embodiments, UE 210 may decode the PDSCH at a first instance according to the configuration for multi-PxSCH after receiving the at least one activation indication, and at a second instance according to the at least one of the transmitting parameters that has been adjusted.

[0042] At 205, NE 220 may transmit to UE 210 an A*¹¹ PDSCH transmission with different transmitting parameters according to RRC configuration; this procedure may be similar to that performed by UE 210 at 204

[0043] FIG. 3 illustrates an example of a flow diagram of a method for enabling a base station to indicate changes of certain transmitting parameters for multi-PxSCH transmission that may be performed by a UE, such as UE 520 illustrated in FIG. 5, according to various example embodiments.

[0044] At 301, the method may include receiving a rule, at a UE, from a NE such as NE 510 illustrated in FIG. 5, for configuration of multi-PxSCH transmission that specifies, for example, which and how transmitting parameters may be changed from one PxSCH transmission to another transmission.

[0045] At 302, once the rule is received, the method may include receiving DCI scheduling multi-PDSCHs from the NE, where multi-PDSCH transmission is provided as one example. As an example, an activation indication may be included in the scheduling DCI. [0046] In some example embodiments, the UE may be configured with which transmission parameters may be changed from a first PxSCH transmission to a second PxSCH transmission associated with one DCI scheduling multi- PxSCH transmission. As an example, the transmission parameters may include Tx power, MCS, a number of repetitions, frequency hopping, multiple input multiple output (MIMO) schemes, etc.

[0047] Additionally, the UE may be configured with step values indicative of changed transmission parameters. For example, Tx power may be increased by 2 dB from one transmission to another; this may be one level more robust MCS (e.g., based on an MCS table, such as Table 1 above) selection from one transmission to another. Various bit maps may be used to indicate the rules for changing the transmitting parameters (e.g., 000: no changes; 001 : only the last TB may use the lower MCS; 010: decrease MCS for every TB). This may be conveyed with DCI. The exact number of bits may depend on the number of rules configured. In some examples, one bit in the bit-map may correspond to one PDSCH occasion which may be used to indicate whether the MCS applied to the current PDSCH occasion may be different from the previous PDSCH occasion.

[0048] In various example embodiments, delta transmission parameters may also be included in the scheduling DCI. In an example of changing MCS scheme from one transmission to another, with RRC configuration, UE 210 may know that the MCS schemes from one transmission of PxSCHs to another transmission of PxSCHs are different. DCI may be used to indicate the change steps, for example, moving towards more robust MCS scheme. Table 1 below shows an example rule, where from one PDSCH transmission to another one, one level more robust MCS is applied. As MCS Index IMCS decreases, the MCS changing rule may become one level more robust, and MCS may be associated with a subsequent PDSCH.

[0049] In various example embodiments, in addition to the changing steps, RRC may configure one bit-map for such transmitting parameter change. In an example with four PDSCH scheduled for one video frame, one bit-map may be [0011], wherein the first two transmissions may use the same transmitting parameters following the scheduling DCI, and the last two transmissions may use different transmitting parameters. Thus, DCI may be used to indicate whether configured changes should be applied. In this example, “0” may indicate no change of transmitting parameters comparing to the previous transmission (z.e., all PxSCH will use the same transmitting parameters), while “1” may indicate applying the configured transmitting parameter change compared to the previous transmission. It is noted that only 1 -bit overhead would be included in scheduling DCI.

[0050] Certain example embodiments may include changing multiple transmitting parameters (e.g., both MCS level and Tx power), wherein multiple bits may be utilized in the DCI if individual transmitting parameters need to be changed (i.e., one bit corresponding with one transmitting parameter). Some example embodiments may include applying different rules for transmitting parameters; in this case, DCI may include extra bits to notify the UE which MCS that the UE should apply to the remaining TBs. The different rules may be pre-defined via RRC or indicated via other protocol signalling e.g., MAC CE).

[0051] Certain example embodiments may include explicitly indicating the transmitting parameters to be used in the multi-PxSCH in the DCI. As one example, the MCS parameter used for the 1^st PDSCH may be indicated in the scheduling DCI, and additional bits with the same DCI may indicate the change in MCS from one PxSCH to another PxSCH transmission. In an example where 4 PDSCHs are scheduled, the MCS parameter used for the 1^st PDSCH may be explicitly indicated in DCI, and an additional 3 bits may indicate the change in MCS for the remaining 3 PDSCHs. For example, “011,” “0” may indicate that the 2^nd PDSCH is using the same MCS as the 1^st PDSCH. The second bit “1” may indicate that the MCS used for the 3^rd PDSCH is different from the MCS used for the 2^nd PDSCH, and the third bit “1” may indicate that the MCS used for the 4^th PDSCH is different from the MCS used for the 3^rd PDSCH.

[0052] Various example embodiments may use semi-static RRC configuration-based activation. Specifically, after RRC configuration is completed, the UE may automatically apply the RRC configuration to the scheduled multiple PxSCH, without requiring dynamic indications in DCI. This may provide the advantage of no additional bits being required in the scheduling DCI.

[0053] Certain example embodiments may include medium access control (MAC) control element (CE)-based activation. In particular, once the RRC configuration is completed, MAC CE may carry activation indications in the 1^st PDSCH transmission. The technique may only apply to PDSCH.

[0054] At 303, the method may further include receiving a first PDSCH transmission with the format according to the scheduling DCI.

[0055] At 304, the method may further include receiving a second PDSCH transmission with different transmitting parameters according to RRC configuration. In various example embodiment, the UE may learn that the RRC configured rule is activated after decoding the DCI scheduling multi- PDSCH carrying activation indication at 302. The method may include decoding the received second PDSCH with the updated parameters based on the rule configured by RRC. In some example embodiments, the method may include decoding the PDSCH at a first instance according to the configuration for multi-PxSCH after receiving the at least one activation indication, and at a second instance according to the at least one of the transmitting parameters that has been adjusted.

[0056] At 305, the method may further include receiving an V^th PDSCH transmission with different transmitting parameters according to RRC configuration; this procedure may be similar to that performed at 304.

[0057] FIG. 4 illustrates an example of a flow diagram of a method for enabling a NE to indicate changes of certain transmitting parameters for multi- PxSCH transmission that may be performed by a NE, such as NE 510 illustrated in FIG. 5, according to various example embodiments.

[0058] At 401, the method may include transmitting a rule, to a UE, such as UE 520 illustrated in FIG. 5, for configuration of multi-PxSCH transmission that specifies, for example, which and how transmitting parameters may be changed from one PxSCH transmission to another transmission.

[0059] At 402, once the rule is transmitted, the method may include transmitting DCI scheduling multi-PDSCHs to the UE, where multi-PDSCH transmission is provided as one example. As an example, an activation indication may be included in the scheduling DCI.

[0060] In some example embodiments, the NE may configure the UE with which transmission parameters may be changed from a first PxSCH transmission to a second PxSCH transmission associated with one DCI scheduling multi-PxSCH transmission. As an example, the transmission parameters may include Tx power, MCS, a number of repetitions, frequency hopping, multiple input multiple output (MIMO) schemes, etc..

[0061] Additionally, the NE may configure the UE with step values indicative of changed transmission parameters. For example, Tx power may be increased by 2 dB from one transmission to another; this may be one level more robust MCS (e.g., based on an MCS table, such as Table 1 above) selection from one transmission to another. Various bit maps may be used to indicate the rules for changing the transmitting parameters (e.g., 000: no changes; 001 : only the last TB may use the lower MCS; 010: decrease MCS for every TB). This may be conveyed with DCI. The exact number of bits may depend on the number of rules configured. In some examples, one bit in the bit-map may correspond to one PDSCH occasion which may be used; whether the MCS applies to the current bit may be different from the previous bit.

[0062] In various example embodiments, delta transmission parameters may also be included in the scheduling DCI. In an example of changing MCS power from one transmission to another, with RRC configuration, the UE may know that the MCS schemes from one transmission of PxSCHs to another transmission of PxSCHs are different. DCI may be used to indicate the change steps, for example, moving towards more robust MCS scheme. Table 1 above shows an example rule, where from one PDSCH transmission to another one, one level more robust MCS is applied. As MCS Index IMCS decreases, the MCS changing rule may become one level more robust, and MCS may be associated with a subsequent PDSCH.

[0063] In various example embodiments, in addition to the changing steps, RRC may configure one bit-map for such transmitting parameter change. In an example with four PDSCH scheduled for one video frame, one bit-map may be [0011], wherein the first two transmissions may use the same transmitting parameters following the scheduling DCI, and the last two transmissions may use different transmitting parameters. Thus, DCI may be used to indicate whether configured changes should be applied. In this example, “0” may indicate no change of transmitting parameters comparing to the previous transmission (z.e., all PxSCH will use the same transmitting parameters), while “1” may indicate applying the configured transmitting parameter change compared to the previous transmission. It is noted that only 1 -bit overhead would be included in scheduling DCI.

[0064] Certain example embodiments may include changing multiple transmitting parameters (e.g., both MCS level and Tx power), wherein multiple bits may be utilized in the DCI if individual transmitting parameters need to be changed (z.e., one bit corresponding with one transmitting parameter). Some example embodiments may include applying different rules for transmitting parameters; in this case, DCI may include extra bits to notify the UE which MCS that the UE should apply to the remaining TBs. The different rules may be pre-defined via RRC or indicated via other protocol signalling (e.g., MAC CE).

[0065] Certain example embodiments may include explicitly indicating the transmitting parameters to be used in the multi-PxSCH in the DCI. As one example, the MCS parameter used for the 1^st PDSCH may be indicated in the scheduling DCI, and additional bits with the same DCI may indicate the change in MCS from one PxSCH to another PxSCH transmission. In an example where 4 PDSCHs are scheduled, the MCS parameter used for the 1^st PDSCH may be explicitly indicated in DCI, and an additional 3 bits may indicate the change in MCS for the remaining 3 PDSCHs. For example, “011,” “0” may indicate that the 2^nd PDSCH is using the same MCS as the 1^st PDSCH. The second bit “1” may indicate that the MCS used for the 3^rd PDSCH is different from the MCS used for the 2^nd PDSCH, and the third bit “1” may indicate that the MCS used for the 4^th PDSCH is different from the MCS used for the 3^rd PDSCH.

[0066] Various example embodiments may use semi-static RRC configuration-based activation. Specifically, after RRC configuration is completed, the UE may automatically apply the RRC configuration to the scheduled multiple PxSCH, without requiring dynamic indications in DCI. This may provide the advantage of no additional bits being required in the scheduling DCI.

[0067] Certain example embodiments may include medium access control (MAC) control element (CE)-based activation. In particular, once the RRC configuration is completed, MAC CE may carry activation indications in the 1^st PDSCH transmission. The technique may only apply to PDSCH.

[0068] At 403, the method may further include transmitting a first PDSCH transmission with the format according to the scheduling DCI.

[0069] At 404, the method may further include transmitting a second PDSCH transmission with different transmitting parameters according to RRC configuration.

[0070] At 405, the method may further include transmitting an V^th PDSCH transmission with different transmitting parameters according to RRC configuration. [0071] FIG. 5 illustrates an example of a system according to certain example embodiments. In one example embodiment, a system may include multiple devices, such as, for example, NE 510 and/or UE 520.

[0072] NE 510 may be one or more of a base station (e.g., 3G UMTS NodeB, 4G LTE Evolved NodeB, or 5G NR Next Generation NodeB), a serving gateway, a server, and/or any other access node or combination thereof.

[0073] NE 510 may further comprise at least one gNB-centralized unit (CU), which may be associated with at least one gNB-distributed unit (DU). The at least one gNB-CU and the at least one gNB-DU may be in communication via at least one Fl interface, at least one X_n-C interface, and/or at least one NG interface via a 5^th generation core (5GC).

[0074] UE 520 may include one or more of a mobile device, such as a mobile phone, smart phone, personal digital assistant (PDA), tablet, or portable media player, digital camera, pocket video camera, video game console, navigation unit, such as a global positioning system (GPS) device, desktop or laptop computer, single-location device, such as a sensor or smart meter, or any combination thereof. Furthermore, NE 510 and/or UE 520 may be one or more of a citizens broadband radio service device (CBSD).

[0075] NE 510 and/or UE 520 may include at least one processor, respectively indicated as 511 and 521. Processors 511 and 521 may be embodied by any computational or data processing device, such as a central processing unit (CPU), application specific integrated circuit (ASIC), or comparable device. The processors may be implemented as a single controller, or a plurality of controllers or processors.

[0076] At least one memory may be provided in one or more of the devices, as indicated at 512 and 522. The memory may be fixed or removable. The memory may include computer program instructions or computer code contained therein. Memories 512 and 522 may independently be any suitable storage device, such as a non-transitory computer-readable medium. The term “non-transitory,” as used herein, may correspond to a limitation of the medium itself (z.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., random access memory (RAM) vs. read-only memory (ROM)). A hard disk drive (HDD), random access memory (RAM), flash memory, or other suitable memory may be used. The memories may be combined on a single integrated circuit as the processor, or may be separate from the one or more processors. Furthermore, the computer program instructions stored in the memory, and which may be processed by the processors, may be any suitable form of computer program code, for example, a compiled or interpreted computer program written in any suitable programming language.

[0077] Processors 511 and 521, memories 512 and 522, and any subset thereof, may be configured to provide means corresponding to the various blocks of FIGs. 2-4. Although not shown, the devices may also include positioning hardware, such as GPS or micro electrical mechanical system (MEMS) hardware, which may be used to determine a location of the device. Other sensors are also permitted, and may be configured to determine location, elevation, velocity, orientation, and so forth, such as barometers, compasses, and the like.

[0078] As shown in FIG. 5, transceivers 513 and 523 may be provided, and one or more devices may also include at least one antenna, respectively illustrated as 514 and 524. The device may have many antennas, such as an array of antennas configured for MIMO communications, or multiple antennas for multiple RATs. Other configurations of these devices, for example, may be provided. Transceivers 513 and 523 may be a transmitter, a receiver, both a transmitter and a receiver, or a unit or device that may be configured both for transmission and reception.

[0079] The memory and the computer program instructions may be configured, with the processor for the particular device, to cause a hardware apparatus, such as UE, to perform any of the processes described above (z.e., FIGs. 2-4). Therefore, in certain example embodiments, a non-transitory computer-readable medium may be encoded with computer instructions that, when executed in hardware, perform a process such as one of the processes described herein. Alternatively, certain example embodiments may be performed entirely in hardware.

[0080] In certain example embodiments, an apparatus may include circuitry configured to perform any of the processes or functions illustrated in FIGs. 2- 4. As used in this application, the term “circuitry” may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry), (b) combinations of hardware circuits and software, such as (as applicable): (i) a combination of analog and/or digital hardware circuit(s) with software/firmware and (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions), and (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation. This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[0081] FIG. 6 illustrates an example of a 5G network and system architecture according to certain example embodiments. Shown are multiple network functions that may be implemented as software operating as part of a network device or dedicated hardware, as a network device itself or dedicated hardware, or as a virtual function operating as a network device or dedicated hardware. The NE and UE illustrated in FIG. 6 may be similar to NE 510 and UE 520, respectively. The user plane function (UPF) may provide services such as intra- RAT and inter-RAT mobility, routing and forwarding of data packets, inspection of packets, user plane quality of service (QoS) processing, buffering of downlink packets, and/or triggering of downlink data notifications. The application function (AF) may primarily interface with the core network to facilitate application usage of traffic routing and interact with the policy framework.

[0082] According to certain example embodiments, processors 511 and 521, and memories 512 and 522, may be included in or may form a part of processing circuitry or control circuitry. In addition, in some example embodiments, transceivers 513 and 523 may be included in or may form a part of transceiving circuitry.

[0083] In some example embodiments, an apparatus (e.g., NE 510 and/or UE 520) may include means for performing a method, a process, or any of the variants discussed herein. Examples of the means may include one or more processors, memory, controllers, transmitters, receivers, and/or computer program code for causing the performance of the operations.

[0084] In various example embodiments, apparatus 520 may be controlled by memory 522 and processor 521 to receive, from a network entity, a configuration for at least one of multiple physical downlink shared channel or physical uplink shared channel (PxSCH) transmission indicating at least one transmitting parameter to be adjusted; and receive downlink control information scheduling at least one of the multiple PxSCH transmissions comprising at least one activation indication.

[0085] Certain example embodiments may be directed to an apparatus that includes means for performing any of the methods described herein including, for example, means for receiving, from a network entity, a configuration for at least one of multiple physical downlink shared channel or physical uplink shared channel (PxSCH) transmission indicating at least one transmitting parameter to be adjusted; and means for receiving downlink control information scheduling at least one of the multiple PxSCH transmissions comprising at least one activation indication.

[0086] In various example embodiments, apparatus 510 may be controlled by memory 512 and processor 511 to transmit, to a user equipment, a configuration for at least one of multiple physical downlink shared channel or physical uplink shared channel (PxSCH) transmission indicating at least one transmitting parameter to be adjusted; and transmit downlink control information scheduling at least one of the multiple PxSCH transmissions comprising at least one activation indication.

[0087] Certain example embodiments may be directed to an apparatus that includes means for performing any of the methods described herein including, for example, means for transmitting, to a user equipment, a configuration for at least one of multiple physical downlink shared channel or physical uplink shared channel (PxSCH) transmission indicating at least one transmitting parameter to be adjusted; and means for transmitting downlink control information scheduling at least one of the multiple PxSCH transmissions comprising at least one activation indication.

[0088] 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 “various embodiments,” “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 example embodiment may be included in at least one example embodiment. Thus, appearances of the phrases “in various embodiments,” “in certain embodiments,” “in some embodiments,” or other similar language throughout this specification does not necessarily all refer to the same group of example embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments.

[0089] As used herein, “at least one of the following: <a list of two or more elements>” and “at least one of <a list of two or more elements>” and similar wording, where the list of two or more elements are joined by “and” or “or,” mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

[0090] Additionally, if desired, the different functions or procedures discussed above 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 description above should be considered as illustrative of the principles and teachings of certain example embodiments, and not in limitation thereof.

[0091] One having ordinary skill in the art will readily understand that the example embodiments 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 the example embodiments.

[0092] Partial Glossary

[0093] 3 GPP 3^rd Generation Partnership Project

[0094] 5G 5^th Generation

[0095] 5GC 5^th Generation Core

[0096] 6G 6^th Generation

[0097] ACK Acknowledgement

[0098] AF Application Function

[0099] ASIC Application Specific Integrated Circuit

[0100] BSR Buffer Status Report [0101] CBG Code Block Group

[0102] CBSD Citizens Broadband Radio Service Device

[0103] CE Control Elements

[0104] CG Configured Grant

[0105] CPU Central Processing Unit

[0106] CU Centralized Unit

[0107] DCI Downlink Control Information

[0108] DG Dynamic Grant

[0109] DL Downlink

[0110] DU Distributed Unit

[0111] eMBB Enhanced Mobile Broadband

[0112] eNB Evolved Node B

[0113] FR Frequency Range

[0114] gNB Next Generation Node B

[0115] GPS Global Positioning System

[0116] HARQ Hybrid Automatic Repeat Request

[0117] HDD Hard Disk Drive

[0118] loT Internet of Things

[0119] El Layer 1

[0120] LTE Long-Term Evolution

[0121] LTE -A Long-Term Evolution Advanced

[0122] MAC Medium Access Control

[0123] MCS Modulation and Coding Scheme

[0124] MEMS Micro Electrical Mechanical System

[0125] MIMO Multiple Input Multiple Output

[0126] mMTC Massive Machine Type Communication

[0127] NE Network Entity

[0128] NG Next Generation

[0129]NG-eNB Next Generation Evolved Node B

[0130JNG-RAN Next Generation Radio Access Network [0131] NR New Radio

[0132] PDA Personal Digital Assistance [0133J PDSCH Physical Downlink Shared Channel

[0134] PDB Packet Delay Budget

[0135] PRB Physical Resource Block

[0136J PUSCH Physical Uplink Shared Channel

[0137] PxSCH Physical Downlink Shared Channel/Physical Uplink Shared Channel

[0138] QoS Quality of Service

[0139] RAM Random Access Memory

[0140] RAN Radio Access Network

[0141] RAT Radio Access Technology

[0142] RF Radio Frequency

[0143] ROM Read-Only Memory

[0144] RRC Radio Resource Control

[0145] SCS Subcarrier Spacing

[0146] SLIV Start and Length Indicator Value

[0147] SPS Semi-Persistent Scheduling

[0148] TB Transport Block

[0149] TDRA Time Domain Resource Allocation

[0150] Tx Transmission

[0151] UE User Equipment

[0152] UL Uplink

[0153] UMTS Universal Mobile Telecommunications System

[0154] UPF User Plane Function

[0155J URLLC Ultra-Reliable and Low-Latency Communication

[0156J UTRAN Universal Mobile Telecommunications System

Terrestrial Radio Access Network

[0157] XR Extended Reality

Claims

WE CLAIM:

1. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive, from a network entity, a configuration for at least one of multiple physical downlink shared channel or physical uplink shared channel (PxSCH) transmission indicating at least one transmitting parameter to be adjusted; and receive downlink control information scheduling at least one of the multiple PxSCH transmissions comprising at least one activation indication.

2. The apparatus of claim 1, wherein the at least one memory and the instructions, when executed by the at least one processor, further cause the apparatus at least to: receive at least one physical downlink shared channel transmission according to at least one of the transmitting parameters that has been adjusted.

3. The apparatus of any of claims 1 or 2, wherein the at least one memory and the instructions, when executed by the at least one processor, further cause the apparatus at least to: decode the physical downlink shared channel at a first instance according to the configuration for multiple PxSCH after receiving the at least one activation indication and at a second instance according to the at least one of the transmitting parameters that has been adjusted.

4. The apparatus of any of claims 1-3, wherein a bit map comprises the configuration for multiple PxSCH transmission.

5. The apparatus of claim 4, wherein the configuration for multiple PxSCH transmission comprises at least one rule.

6. The apparatus of claim 5, wherein the at least one rule indicates a last transport block is to be used in a robust modulation and coding scheme.

7. The apparatus of claim 5, wherein the at least one rule indicates that a robust a modulation and coding scheme is to be used for every transport block.

8. The apparatus of any of claims 1-7, wherein the at least one memory and the instructions, when executed by the at least one processor, further cause the apparatus at least to: update the at least one transmitting parameter according to a radio resource control configuration.

9. The apparatus of any of claims 1-8, wherein the at least one multiple PxSCH transmission is scheduled with one downlink control information.

10. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: transmit, to a user equipment, a configuration for at least one of multiple physical downlink shared channel or physical uplink shared channel (PxSCH) transmission indicating at least one transmitting parameter to be adjusted; and transmit downlink control information scheduling at least one of the multiple PxSCH transmissions comprising at least one activation indication.

11. The apparatus of claim 10, wherein the at least one memory and the instructions, when executed by the at least one processor, further cause the apparatus at least to: transmit at least one physical downlink shared channel transmission according to at least one of the transmitting parameters that has been adjusted.

12. The apparatus of any of claims 10 or 11, wherein a bit map comprises the configuration for multiple PxSCH transmission.

13. The apparatus of claim 12, wherein the configuration for multiple PxSCH transmission comprises at least one rule.

14. The apparatus of claim 13, wherein the at least one rule indicates a last transport block is to be used in a robust modulation and coding scheme.

15. The apparatus of claim 14, wherein the at least one rule indicates that a robust a modulation and coding scheme is to be used for every transport block.

16. The apparatus of any of claims 10-15, wherein the at least one multiple PxSCH transmission is scheduled with one downlink control information.

17. An apparatus comprising : means for receiving, from a network entity, a configuration for at least one of multiple physical downlink shared channel or physical uplink shared channel (PxSCH) transmission indicating at least one transmitting parameter to be adjusted; and means for receiving downlink control information scheduling at least one of the multiple PxSCH transmissions comprising at least one activation indication.

18. The apparatus of claim 17, further comprising: means for receiving at least one physical downlink shared channel transmission according to at least one of the transmitting parameters that has been adjusted.

19. The apparatus of any of claims 17 or 18, further comprising: means for decoding the physical downlink shared channel at a first instance according to the configuration for multiple PxSCH after receiving the at least one activation indication and at a second instance according to the at least one of the transmitting parameters that has been adjusted.

20. The apparatus of any of claims 17-19, wherein a bit map comprises the configuration for multiple PxSCH transmission.

21. The apparatus of claim 20, wherein the configuration for multiple PxSCH transmission comprises at least one rule.

22. The apparatus of claim 21, wherein the at least one rule indicates a last transport block is to be used in a robust modulation and coding scheme.

23. The apparatus of claim 21, wherein the at least one rule indicates that a robust a modulation and coding scheme is to be used for every transport block.

24. The apparatus of any of claims 17-23, further comprising: means for updating the at least one transmitting parameter according to a radio resource control configuration.

25. The apparatus of any of claims 17-24, wherein the at least one multiple PxSCH transmission is scheduled with one downlink control information.

26. An apparatus comprising: means for transmitting, to a user equipment, a configuration for at least one of multiple physical downlink shared channel or physical uplink shared channel (PxSCH) transmission indicating at least one transmitting parameter to be adjusted; and means for transmitting downlink control information scheduling at least one of the multiple PxSCH transmissions comprising at least one activation indication.

27. The apparatus of claim 26, further comprising: means for transmitting at least one physical downlink shared channel transmission according to at least one of the transmitting parameters that has been adjusted.

28. The apparatus of any of claims 26 or 27, wherein a bit map comprises the configuration for multiple PxSCH transmission.

29. The apparatus of claim 28, wherein the configuration for multiple PxSCH transmission comprises at least one rule.

30. The apparatus of claim 29, wherein the at least one rule indicates a last transport block is to be used in a robust modulation and coding scheme.

31. The apparatus of claim 30, wherein the at least one rule indicates that a robust a modulation and coding scheme is to be used for every transport block.

32. The apparatus of any of claims 26-31, wherein the at least one multiple PxSCH transmission is scheduled with one downlink control information.

33. A method comprising : receiving, from a network entity, a configuration for at least one of multiple physical downlink shared channel or physical uplink shared channel (PxSCH) transmission indicating at least one transmitting parameter to be adjusted; and receiving downlink control information scheduling at least one of the multiple PxSCH transmissions comprising at least one activation indication.

34. The method of claim 33, further comprising: receiving at least one physical downlink shared channel transmission according to at least one of the transmitting parameters that has been adjusted.

35. The method of any of claims 33 or 34, further comprising: decoding the physical downlink shared channel at a first instance according to the configuration for multiple PxSCH after receiving the at least one activation indication and at a second instance according to the at least one of the transmitting parameters that has been adjusted.

36. The method of any of claims 33-35, wherein a bit map comprises the configuration for multiple PxSCH transmission.

37. The method of claim 36, wherein the configuration for multiple PxSCH transmission comprises at least one rule.

38. The method of claim 37, wherein the at least one rule indicates a last transport block is to be used in a robust modulation and coding scheme.

39. The method of claim 37, wherein the at least one rule indicates that a robust a modulation and coding scheme is to be used for every transport block.

40. The method of any of claims 33-39, further comprising: updating the at least one transmitting parameter according to a radio resource control configuration.

41. The method of any of claims 33-40, wherein the at least one multiple PxSCH transmission is scheduled with one downlink control information.

42. A method comprising: transmitting, to a user equipment, a configuration for at least one of multiple physical downlink shared channel or physical uplink shared channel (PxSCH) transmission indicating at least one transmitting parameter to be adjusted; and transmitting downlink control information scheduling at least one of the multiple PxSCH transmissions comprising at least one activation indication.

43. The method of claim 42, further comprising: transmitting at least one physical downlink shared channel transmission according to at least one of the transmitting parameters that has been adjusted.

44. The method of any of claims 42 or 43, wherein a bit map comprises the configuration for multiple PxSCH transmission.

45. The method of claim 44, wherein the configuration for multiple PxSCH transmission comprises at least one rule.

46. The method of claim 45, wherein the at least one rule indicates a last transport block is to be used in a robust modulation and coding scheme.

47. The method of claim 46, wherein the at least one rule indicates that a robust a modulation and coding scheme is to be used for every transport block.

48. The method of any of claims 42-47, wherein the at least one multiple PxSCH transmission is scheduled with one downlink control information.

49. A non-transitory computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least a method according to any of claims 33-48.

50. An apparatus comprising circuitry configured to perform a method according to any of claims 33-48.

51. A computer program comprising instructions, which, when executed by an apparatus, cause the apparatus to perform the method of any of claims 33-48.