OA20966A - Methods and Nodes for Efficient MAC CE design for indicating mapping between pathloss reference and multiple SRI. - Google Patents

Abstract

There is provided a method in a wireless device. The method comprises: receiving a Media Access Control (MAC) Control Element (CE) from a network node, the MAC CE comprising a plurality of octets and a plurality of fields, wherein a first field of the plurality of fields is used to indicate a number of sets of power control parameters in a last octet of the received MAC CE, the sets of power control parameters being associated with a reference signal used for path loss estimation; and sending a transmission to a network node, based at least on a set of power control parameters associated with the reference signal.

Description

METHODS AND NODES FOR EFFICIENT MAC CE DESIGN FOR INDICATING MAPPING BETWEEN PATHLOSS REFERENCE AND MULTIPLE SRI

RELATED APPLICATIONS

[0001] This application claims the benefits of priority of U.S. Provisional Patent Application No. 63/014,470, entitled “Efficient MAC CE design for indicating mapping between pathloss reference and multiple SRI and filed at the United States Patent and Trademark Office on April 23, 2020, the content of which is incorporated herein by reference.

TECHNICAL FIELD

[0002] The present description generally relates to wireless communication Systems, and particularly, to methods for indicating mapping between pathloss reference and multiple SRI.

INTRODUCTION

[0003] New Radio (NR)

[0004] The new génération mobile wireless communication system (5G) or new radio (NR) supports a diverse set of use cases and a diverse set of deployment scénarios.

[0005] Uplink data transmission can be dynamically scheduled using Physical Downlink Control Channel (PDCCH). Similarto downlink, a User Equipment (UE) first décodés uplink grants in PDCCH and then transmits data over Physical Uplink Shared Channel (PUSCH) based on the decoded control information in the uplink grant, such as modulation order, coding rate, uplink resource allocation, etc. Also, a UE needs to détermine an uplink power for a PUSCH transmission.

[0006] PUSCH power control

[0007] The PUSCH-PowerControl Information Element (iE), as shown below, provides PUSCH power control parameters including Pathloss Reference Signal (RS) identities/identifiers (IDs) for path loss estimation and a list of Sounding Reference Signai (SRS) resource indication (SRl)-PUSCH-PowerControl éléments among which one is selected by the SRS resource indication (SRI) field in the Downlink Control Information (DCI). SRI is the SRS resource indication field in the DC! which provides the per scheduling mapping of SRI to PUSCH pathloss reference ID.

PUSCH-PowerControl

The ΙΕ PUSCI I-PowerControl is used to configure UE spécifie power control parameter for PUSCH.

PUSCH-PowerControl information element

-- ASN1START

- - TAG-PUSCH-POWERCONTROL-START

PUS CH-PowerControl :: = tpc-Accumulation

OPTIONAL, Need S

SEQUENCE { enumerated { disabled } msg3-Alpha Alpha

OPTIONAL, -- Need Ξ pO-NominalWithoutGrant INTEGER (-202..24)

OPTIONAL·, -- Need M pO-AlphaSets SEQUENCE (SIZE (1..maxNrofP0PUSCH-AlphaSets)) OF PO-PUSCH-AlphaSet OPTIONAL, -· Need M pathlossReferenceRSToAddModList SEQUENCE (SIZE (1..maxNrofPUSCHPathlossRef erenceRSs) ) OF PUSCH-PathlossReferenceRS

OPTIONAL, -- Need N pathlossReferenceRSToReleaseList SEQUENCE (SIZE (1..maxNrofPUSCHPathlossRef erenceRSs ) ) OF PUSCH-PathlossReferenceRS-Id

OPTIONAL, -- Need N twoPUSCH-PC-AdjustmentStates ENUMERATED {twoStates}

OPTIONAL, -- Need S deltaMCS ENUMERATED {enabled} OPTIONAL, -

- Need S

Sri-PUSCH-MappingToAddModList SEQUENCE (SIZE (1..maxNrofSRIPUSCH-Mappings)) OF SRI-PUSCH-PowerControl

OPTIONAL, -- Need N

Sri-PUSCH-MappingToReleaseList SEQUENCE (SIZE (l..maxNrofSRIPUSCH-Mappings)) OF SRI-PUSCH-PowerControlId [-]

OPTIONAL - Need N } PO-PUSCH-AlphaSet :: = pO-PUSCH-AlphaSetld pO OPTIONAL, -- Need S alpha OPTIONAL -- Need S } PO-PUSCH-AlphaSetld ::= AlphaSets-1) PUSCH-PathlossReferenceRS :;= pusch-PathlossReferenceRS-Id referenceSignal ssb-Index csi-RS-lndex } PUSCH-PathlossReferenceRS-Id ::= PathlossReferenceRSs-1) SRI-PUSCH-PowerControl ::= sri-PUSCH-PowerControiId sri-PUSCH-PathlossReferenceRS-Id sri-PO -PUSCH-AlphaSetld

SEQUENCE {

PO-PUSCH-AlphaSetld, INTEGER (-16. .15)

Alpha

INTEGER (0..maxNrofPO-PUSCHSEQUENCE {

PUSCH-PathlossReferenceRS-Id

CHOICE {

SSB-Index,

NZP-CSI-RS-Resourceld

INTEGER (0..maxNrofPUSCHSEQUENCE {

SRI-PUSCH-PowerControlId, PUSCH-PathlossReferenceRS-Id PO-PUSCH-AlphaSetld,

-220966 sri-PUSCH-ClosedLoopIndex ENUMERATED { io, il } } £·

SRI-PUSCH-PowerControiId ::= INTEGER (0..maxNrofSRI-PUSCHMappings-1)

-- TAG-PUSCH-POWERCONTROL-STOP

-- ASN1STOP ________________________________PUSCH-PowerControl field descriptions deltaMCS

Indicates whether to apply delta MCS. When the field is absent, the UE applies Ks = 0 in delta_TFC formula for PUSCH (see TS 38.213 [13], clause 7.1). _______________________________________ msg3-Alpha

Dedicated alpha value for msg3 PUSCH (see TS 38.213 [13], clause 7.1). When the field is absent the UE applies the value 1._______________________________________________________________________ pO-AlphaSets configuration {pO-pusch, alpha} sets for PUSCH (except msg3), i.e., {{pO,alpha,indexl}, {p0,alpha,îndex2},...} (see TS 38.213 [13], clause 7.1). When no set is configured, the UE uses the PO-nominal for msg3 PUSCH, PO-UE is setto 0 and alpha is set according to msg3-Alpha configured for msg3 PUSCH._______________________________________________________ pO-NominaIWithoutGrant

PO value for UL grant-free/SPS based PUSCH. Value in dBm. Only even values (step size 2) allowed (see TS 38.213 [13], clause 7.1).___________________________________________________________ pathlossReferenceRSToAddModList

A set of Reference Signais (e.g. a CSI-RS config or a SS block) to be used for PUSCH path loss estimation. Up to maxNrofPUSCH-PathlossReferenceRSs may be configured (see TS 38.213 [13], clause 7.1).________________________________________________ sri-PUSCH-MappingToAddModList

A list of SRI-PUSCH-PowerControl éléments among which one is selected by the SRI field in DCI (see TS 38.213 [13], clause 7.1 )._______________________________________________________________________ tpc-Accumuiation

If enabled, UE applies TPC commands via accumulation. If not enabled, UE applies the TPC command without accumulation. If the field is absent, TPC accumulation is enabled (see TS 38.213 [13], clause 7,1).____ twoPUSCH-PC-AdjustmentStates

Number of PUSCH power control adjustment States maintained by the UE (i.e., fc(i)), If the field is present (n2) the UE maintains two power control states (i.e., fc(i,O) and fc(i, 1 )). If the field is absent, it maintains one power control State (i.e., fc(i,O)) (see TS 38.213 [13], clause 7.1).

SRI-PUSCH-PowerControl field descriptions sri-PO-PUSCH-AlphaSetld

The ID of a PO-PUSCH-AlphaSet as configured in pO-AlphaSets in PUSCH-PowerControl.

sri-PUSCH-ClosedLoopindex

The index of the closed power control loop associated with this SRI-PUSCH-PowerControl.

sri-PUSCH-PathlossReferenceRS-ld

The ID of PUSCH-PathiossReferenceRS as configured in the pathlossReferenceRSToAddModList in

PUSCH-PowerControl._________________________________________________________________ sri-PUSCH-PowerControlld

The ID of this SRI-PUSCH-PowerControl configuration. It is used as the codepoint (payload) in the SRI DCI field.

[0008] Medium Access Control (MAC) Control Eléments (CE)

[0009] A MAC protocol data unit (PDU) is a bit string that is byte aligned (i.e. multiple of 8 bits) in length. A MAC service data unit (SDU) is a bit string that is byte aligned (i.e. multiple

-320966 of 8 bits) in iength. A MAC CE is a bit string that is byte aligned (i.e. multiple of 8 bits) in length.

[0010] A MAC subheader is a bit string that is byte aligned (i.e. multiple of 8 bits) in length. Each MAC subheader is placed immediately in front of the correspondîng MAC SDU, MAC CE, or padding.

[0011] A MAC PDU consists of one or more MAC subPDUs. Each MAC subPDU consists of one of the following: A MAC subheader only (including padding); A MAC subheader and a MAC SDU; A MAC subheader and a MAC CE; A MAC subheader and padding.

[0012] Each MAC subheader corresponds to either a MAC SDU, a MAC CE, or padding.

[0013] A MAC subheader except for a fixed sized MAC CE, padding, and a MAC SDU containing uplink (UL) common Control Channel (CCCH), consists of the header fields R/F/LCID/(eLCID)/L. A MAC subheader Îor a fixed sized MAC CE, padding, and a MAC SDU containing UL CCCH, consists of the two header fields R/LCID. The extended Logical Channel ID (eLCID) field is présent when the LCID field is set to spécifie values and is otherwise absent.

[0014] Some examples of MAC subheaders are given in Figures 1-3.

[0015] Figure 1 illustrâtes a R/F/LClD/(eLCID)/L MAC subheader with 8-bit L field.

[0016] Figure 2 illustrâtes a R/F/LClD/(eLCID)/L MAC subheader with 16-bit L field.

[0017] Figure 3 illustrâtes a R/LCID/(eLCID) MAC subheader.

[0018] MAC CEs with variable size has a subheader which includes an L field. MAC CEs with a constant size has a subheader which does not include an L field, as the size of the MAC CE is determined by the LCID,

[0019] Mapping between SRI and PUSCH pathloss reference ID

[0020] A network node uses a MAC CE to map (or associate) SRI IDs to PUSCH pathloss reference RS (reference signal) ID. Third Génération Partnership Project (3GPP) TechnicaI Spécification (TS) 38.321 16.0.0currently captures the MAC CE as follows, in section 6.1.3.28:

[0021 ] 6.1.3.28 PUSCH Pathloss Reference RS Activation/Deactivation MAC CE

[0022] “The PUSCH Pathloss Reference RS Activation/Deactivation MAC CE is identified by a MAC subheader with LCID as specified in Table 6.2.1-1. It has a fixed size of 24 bits: [0023] - Serving Cell ID: This field indicates the identity of the Serving Cell, which contains activated/deactivated SRS Resource Set. The length of the field is 5 bits;

[0024] - BWP ID: This field indicates a UL BWP as the codepoint of the DCI bandwidth part indicator as specified in TS 38.212, [9], which contains activated/deactivated SRS Resource Set. The length of the field is 2 bits;

-420966

[0025] - SRI ID: This field indicates the SRI PUSCH power control ID îdentified by srb PUSCH-PowerControlid as specified in TS 38.331 [5], The length of the field is 4 bits;

[0026] - PUSCH Pathloss Reference RS ID: This field indicates the PUSCH Pathloss Reference RS ID îdentified by PUSCH-PathlossReferenceRS-ld as specified in TS 38.331 5 [5], which is to be activated/deactivated. The length of the field is 6 bits;

[0027] - R: Reserved bit, set to 0.

[0028] For example, Figure 4 illustrâtes a PUSCH Pathloss Reference RS Activation/Deactivation MAC CE, which comprises the fields just described above.

SUMMARY

[0029] There are problems with the current MAC CE. For example, the problem is that a

DCI selects a one-to-one mapping between a SRI and PUSCH pathloss reference RS ID, but the configuration given by Radio Resource Control (RRC) and MAC can hâve multiple SRis mapped to one pathloss reference RS ID. Further, the UE can only follow4 pathloss reference RS IDs at the same time.

[0030] For solving this problem, a prior solution suggested to hâve a MAC CE where multiple SRIs are included in the MAC CE. As such, the MAC CE is re-designed as shown in Figure 7.

[0031] Figure 5 illustrâtes one MAC CE that can include multiple SRI IDs which are associated with the same pathloss RS.

[0032] The MAC CE comprises a C1 field, which îs used to indicate the presence of the additional SRI ID. The MAC CE comprises also a SUL field, which is used to indicate that the MAC CE applies to a supplementary uplink (SUL) carrier configuration.

[0033] The other fields are the same as described above, with regards to Figure 4.

[0034] In this case, the network (NW)/network node includes multiple SRI IDs which hâve the same mapping for the pathloss reference signai (PL RS), i.e. PUSCH pathloss reference RS ID.

[0035] However, this spécifie MAC CE proposai wastes octets. There are at least three problems with this solution.

[0036] Unnecessary fields

[0037] The C1 fieid is not useful as the number of SRI ID fields can be deduced from the length field in the MAC CE header (not shown in the figure). If the C1 field is included in the overhead calculations, the MAC CE overhead becomes larger.

[0038] Overhead

[0039] For each new SRI ID added, 3 R-bits are included. For example, with 1 SRI ID 35 included, 20% of the MAC CE consists of R-bits; with 8 SRI IDs included, more than 30%

- 5 20966 are R bits. As R-bits are not used, this constitutes pure overhead. Therefore, the overhead increases with the number of SRI IDs added.

[0040] Size

[0041] One octet is added for each new SRI ID, while the SRI ID field is only 4 bits. The size of the MAC CE is 2 octets plus the number of SRI IDs.

[0042] Furthermore, there is also a need to be able to remove a mapping between SRI ID and Pathloss reference RS ID. Neither the prior solution nor the current MAC CE can do that. They can only add mappings.

[0043] Therefore, a more efficient design is needed, which is also able to remove mappings between SRI IDs and pathloss reference RS ID.

[0044] Generally stated, embodiments of this disclosure allow a lean design of the MAC CE and to map Pathloss reference ID with several SRIs based on the following:

[0045] - Length field (in the subheader) is used to détermine the length of the MAC CE;

[0046] - F field is used to détermine the content of the last octet.

[0047] To enable removal of mappings between Pathloss reference RS ID and SRIs, the following can be used:

[0048] - E field is used to control if the MAC CE is adding or removing SRI mappings from the spécifie pathloss reference RS ID.

[0049] According to an aspect, some embodiments include methods performed by a wireless device. For example, a method comprises: receiving a MAC CE from a network node, the MAC CE comprising a plurality of octets and a plurality of fîelds, wherein a first field of the plurality of fields is used to indicate a number of sets of power control parameters in a last octet of the received MAC CE, the sets of power central parameters being associated with a reference signal used for path loss estimation; and sending a transmission to a network node, based at least on a set of power central parameters associated with the reference signal.

[0050] According to another aspect, some embodiments include a wireless device configured, or opérable, to perform one or more functionalities (e.g. actions, operations, steps, etc.) as described herein.

[0051] In some embodiments, the wireless device may comprise one or more communication interfaces configured to communicate with one or more other radio nodes and/or with one or more network nodes, and processing circuitry operatively connected to the communication interface, the processing circuitry being configured to perform one or more functionalities as described herein. In some embodiments, the processing circuitry may comprise at least one processor and at least one memory storing instructions which,

-620966 upon being executed by the processor, configure the at least one processor to perform one or more functionalities as described herein.

[0052] In some embodiments, the wireless device may comprise one or more functional modules configured to perform one or more functionalities as described herein.

[0053] According to an aspect, some embodiments include methods performed by a network node. For example, a method comprises: sending to a wireless device a MAC CE, the MAC CE comprising a plurality of octets, each of which comprising a plurality of fields, wherein a first field of the plurality of fields is used to indicate a number of sets of power control parameters in a last octet of the MAC CE, the sets of power control parameters being associated with a reference signal used for path îoss estimation; and receiving a transmission based on at least a set of power contrai parameters associated with the reference signal.

[0054] According to another aspect, some embodiments include a network node configured/ opérable, to perform one or more functionalities (e.g. actions, operations, etc.) as described herein.

[0055] In some embodiments, the network node may comprise one or more communication interfaces configured to communicate with one or more other radio nodes and/or with one or more network nodes, and processing circuitry operatively connected to the communication interface, the processing circuitry being configured to perform one or more functionalities as described herein. In some embodiments, the processing circuitry may comprise at least one processor and at least one memory storing instructions which, upon being executed by the processor, configure the at least one processor to perform one or more functionalities as described herein.

[0056] In some embodiments, the network node may comprise one or more functional modules configured to perform one or more functionalities as described herein.

[0057] According to another aspect, some embodiments include a non-transitory computer-readable medium storing a computer program product comprising instructions which, when executed by a processing circuitry (e.g., a processor) of the network node or the wireless device, configure the processing circuitry to perform one or more functionalities as described herein.

[0058] The advantages/technical benefits of the embodiments of the present dîsclosure are:

[0059] - The proposed design contains no unnecessary fields. The size ofthe MAC CE is determined by the length field in the header instead of using an additional field in the MAC CE.

- 7 20966

[0060] - The number of R-bits included will be 0 for an even number of SRI IDs and 4 for an odd number of R-bits. This means that the fraction of R-bits will decrease as the number of SRI IDs is added.

[0061] - One octet is added for every other SRI ID. This means that the size of the MAC CE is 2 plus CEIL(number of SRI IDs divided by 2) where CEIL() is the ceiling function, where the input is rounded up to the closest rnteger.

[0062] - Further functionality is enabled by an E field, which can be added to State If the MAC CE is adding or removing SRI mappings from the spécifie pathloss reference RS ID. [0063] This summary is not an extensive overview of ail contemplated embodiments and is not intended to identify key or critical aspects or features of any or ail embodiments or to delineate the scope of any or all embodiments. In that sense, other aspects and features will become apparent to those ordinarily skilled in the art upon review of the following description of spécifie embodiments in conjunction with the accompanying figures.

BRIEF DESCRIPTION OF THE DRAWINGS

[0064] Exempiary embodiments will be described in more detail with reference to the following figures, in which:

[0065] Figure 1 illustrâtes a R/F/LC1D/(eLCID)/L MAC subheader with 8-bit L field.

[0066] Figure 2 illustrâtes a R/F/LCID/(eLCID)/L MAC subheader with 16-bit L field.

[0067] Figure 3 illustrâtes R/LCID/(eLCID) MAC subheader.

[0068] Figure 4 illustrâtes a PUSCH Pathloss Reference RS Activation/Deactivation MAC CE.

[0069] Figure 5 illustrâtes a prior solution MAC CE for accommodating multiple SRIs. [0070] Figure 6 illustrâtes a MAC CE with a F field, according to an embodiment.

[0071] Figure 7 illustrâtes a MAC CE with an A/D field, according to an embodiment.

[0072] Figure 8 illustrâtes a MAC CE with a C field, according to an embodiment

[0073] Figure 9 is a flow chart of a method in a wireless device, according to an embodiment.

[0074] Figure 10 is a flow chart of a method in a network node, according to an embodiment.

[0075] Figure 11 illustrâtes one example of a wireless communications System in which embodiments of the présent disclosure may be implemented.

[0076] Figure 12 is a block diagram that shows a wireless device according to an embodiment.

[0077] Figure 13 is a block diagram that shows a network node according to an embodiment.

-8 20966

DETAILED DESCRIPTION

[0078] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments. Upon reading the following description in light of the accompanying figures, those skilled in the art will understand the concepts of the description and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the description.

[0079] In the following description, numerous spécifie details are set forth. However, it is understood that embodiments may be practiced without these spécifie details. In other instances, well-known circuits, structures, and techniques hâve not been shown in detail in order not to obscure the understanding of the description. Those of ordinary skill in the art, with the included description, will be able to implement appropriate functionality without undue expérimentation.

[0080] References in the spécification to “one embodiment, an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particuiar feature, structure, or characteristic, but every embodiment may not necessarily include the particuiar feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particuiar feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

[0081] As used herein, the singular forms a, an and the are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises, “comprising,” “includes, and/or “including” when used herein, specify the presence of stated features, integers, steps, operations, éléments, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, éléments, components, and/or groups thereof.

[0082] A general example of a P U SC H Pathloss Reference RS Activation/Deactivation MACE CE 100, which allows to résolve the problème mentioned above, is illustrated in Figure 6. For example, a PUSCH Pathloss Reference RS Activation/Deactivation MAC CE allows to activate or inactivate/deactivate a certain PUSCH Pathloss Reference RS, identified by PUSCH-PathlossReferenceRS-ld as specified in 3GPP TS 38.331. This means that a certain RS that has been Radio Resource Control (RRC) configured for the UE to be considered as the pathloss reference RS can be activated (e.g. becomes active) or be deactivated (e.g. becomes/stays inactive), as indicated by the MAC CE to the UE. if the pathloss reference RS is active, the UE considers it as available. If it is inactive (e.g.

-920966 deactivated), the UE assumes it is not available (even though a “placeholder” is RRC configured).

[0083] It should be noted that the terms “pathloss reference RS ID” or pathloss reference ID” or “pathloss reference or Pathloss RS ID” can be used interchangeably.

[0084] The MAC CE 100 has the following fields:

[0085] - Serving Cell ID 102: This field indicates the identity of the Serving Cell, which contains activated/deactivated SRS Resource Set. The length of the field is 5 bits;

[0086] - BWP ID 104: This field indicates a UL BWP as the codepoint of the DCI bandwidth part indicator field as specîfied in 3GPP TS 38.212, which contains activated/deactivated SRS Resource Set. The iength of the field is 2 bits;

[0087] - SRI ID 106: This field indicates the SRI PUSCH power control ID identified by sriPUSCH-PowerCûntrolld as specîfied in 3GPP TS 38.331. The length of the field is 4 bits;

[0088] - Pathloss RS ID 108: This field indicates the PUSCH Pathloss Reference RS ID identified by PU SC H-Pathloss Reference RS-Id as specîfied in 3GPP TS 38.331, which is to be activated/deactivated. The length of the field is 6 bits;

[0089] - E 110: indicates whether a mapping (or association) between the Pathloss RS ID and SRI ID(s) is added (or updated if the SRI ID was previously mapped to another Pathloss RS ID) or removed (in which case the SRI ID(s) are not mapped to any Pathloss RS ID). If the field is set to one value, the mappings are added/updated. If the field is set to another value, the mappings are removed. The iength of the field is 1 bit;

[0090] - F 112: indicates the presence of one SRI ID in the last octet. If set to one value, there is 1 SRI ID field and 4 R-bits in the last octet. If set to another value, there are 2 SRI ID fields and no R-bits in the last octet. The length of the field is 1 bit;

[0091] - R 114: Reserved bit, set to 0.

[0092] As can be seen from the SRI ID field 106, a SRI ID is used to indicate a set of power control elements/parameters. This set of power control parameters can be indicated to be mapped to a reference signal used for pathloss estimation.

[0093] In a first example, a PUSCH Pathloss Reference RS Activation/Deactivation MAC CE can include one or two SRI fields starting from octet 3 until octet n (see Figure 6 for example). Octet 2 can include the field F 112, which détermines whether the last octet includes one or two SRI fields. 1n this first example, it should be noted that there may be no E field.

[0094] In the UE side, when the UE receives a MAC CE, such as MAC CE 100, the UE détermines from the length field how many octets the MAC CE body contains. Further, the UE détermines from the F field how many SRI fields the last octet contains. Combining the information from the length field and F field, the UE is able to determine how many SRI

- 10 20966 fields are mapped (or associated) to one pathloss reference RS. Based on this information, the UE can détermine a transmit power for sending an uplink grant/transmission to the network node, for example.

[0095] In a second example, the MAC CE includes the E field, in addition to the F field. 5 The E field détermines how the UE should update the mapping of SRI to pathloss reference RS. More specifically, the E field can indicate whether a mapping between the Pathloss RS ID and SRI ID(s) are added (or updated if the SRI ID was previously mapped to another Pathloss RS ID) or removed (in which case the SRI ID(s) are not mapped to any Pathloss RS ID). For example, if the field is set to one value, the mappings are added/updated. If 10 the field is set to another value, it means that the mappings given in the MAC CE should be removed by the UE.

[0096] Alternatively, the E field can control whether the UE should forget any or ail earlier mappings associated with the SRI and pathloss reference RS given in this MAC CE, or if the UE should consider the MAC CE as providing additional mappings for the indicated 15 SRI. In this case, for example, if the E field is set to the value of zéro (0), the UE forgets the mappings, if the E field is set to 1, the UE considers a mapping between SRI ID and the pathloss reference RS ID as an additional mapping. As such, the E field indicate to the UE about the mappings to be either forgotten or added, depending on the value of the E field.

[0097] When the UE receives the MAC CE in this second example, the UE can détermine the number of SRI fields mapped to one pathloss reference RS, based on the length field and F field. Furthermore, from the E field, the UE can détermine if the SRI fields are updated/added or removed with respect to the previous configuration the UE had for the mappings. Based on this information (i.e. the length and the F and E fields), the UE can 25 détermine a transmit power for sending an uplink grant/transmission to the network node, for example.

[0098] Another example of a PUSCH Pathloss Reference RS Activation/Deactivation MAC CE 200 is illustrated in Figure 1.

[0099] In this example, the field E 110 (of Figure 6) is replaced by an A/D field 210.

[0100] More specifically, the MAC CE 200 of Figure 7 comprises the following fields:

[0101] - Serving Cell ID 202: This field indicates the identity of the Serving Cell, which contains activated/deactivated SRS Resource Set. The length of the field is 5 bits;

[0102] - BWP ID 204: This field indicates a UL BWP as the codepoint of the DCI bandwidth part indicator field as specified in 3GPP TS 38.212, which contains activated/deactivated 35 SRS Resource Set. The length of the field is 2 bits;

-11 20966

[0103] - SRI ID 206: This field indicates the SRI PUSCH power control ID identified by sriPUSCH-PowerControlld as specified in 3GPP TS 38.331, The length ofthe field is 4 bits;

[0104] - Pathloss RS ID 208: This field indicates the PUSCH Pathloss Référencé RS ID identified by PUSCH-PathlossReferenceRS-ld as specified in 3GPP TS 38.331, which is to be activated/deactivated. The length of the field is 6 bits;

[0105] - A/D 210: This field indicates whether to activate or deactivate the indicated PUSCH Pathloss Référencé RS. The field is set to one value to indicate activation, and to another value to indicate deactivation. The length of the field is 1 bit;

[0106] - F 212: indicates the presence of one SRI ID in the last octet, if set to one value, there is 1 SRI ID field and 4 R-bits in the last octet. If set to another value, there are 2 SRI ID fields and no R-bits in the last octet. The length ofthe field is 1 bit;

[0107] - R 214: Reserved bit, setto 0.

[0108] in this exampie, the MAC CE includes the A/D field 210. This field indicates whether to activate or deactivate the indicated PUSCH Pathloss Référencé RS. For example, the field is set to 1 to indicate activation, otherwise it indicates deactivation.

[0109] When the UE receives the MAC CE 200, the UE can détermine if the indicated PUSCH Pathloss Référencé RS is activated or inactivated. If the A/D 210 field indicates activation, then the UE activâtes the PUSCH Pathloss Référencé RS. Based on this information, the UE can détermine which are the activated PUSCH pathloss Référencé RSs that may be used for determining the transmit power for sending an uplink transmission to the network node, for example. If the A/D 210 field indicates inactivation, then the UE does not use the inactivated PUSCH pathloss référencé RS for determining the transmit power,

[0110] Another example of a PUSCH Pathloss Référencé RS Activation/Deactivation MAC CE 300 is illustrated in Figure 8.

[0111] In this example, the field C 312 can replace 2 ofthe 3 fields, E field 110, A/D field 210andFfîeld 112or212.

[0112] More specifically, the MAC CE 300 of Figure 8 comprises the following fields: [0113] - Serving Cell ID 302: This field indicates the identity of the Serving Cell, which contains activated/deactivated SRS Resource Set. The length of the field is 5 bits;

[0114] - BWP ID 304: This field indicates a UL BWP as the codepoint ofthe DCI bandwidth part indicator field as specified in 3GPP TS 38.212, which contains activated/deactivated SRS Resource Set. The length of the field is 2 bits;

[0115] - SRI ID 306: This field indicates the SRI PUSCH power control ID identified by sriPUSCH-PowerControlld as specified in 3GPP TS 38.331. The length of the field is 4 bits;

-1220966

[0116] - Pathloss RS ID 308: This field indicates the PUSCH Pathloss Reference RS ID identified by PUSCH-PathlossReferenceRS-ld as specified in 3GPP TS 38.331, which is to be activated/deactivated. The length of the field is 6 bits;

[0117] - C 3012: This field indicates options on how a UE should interpret the MAC CE 300. For example, one codepoint indicates that the MAC CE deactivates the PUSCH Pathloss Reference RS. A second codepoint indicates that the MAC CE activâtes the PUSCH Pathloss Reference RS but does not change the SRI mappings with the reference signal, given by RRC. A third codepoint indicates that the MAC CE activâtes the PUSCH Pathloss Reference RS and adds SRI iD mappings to the PUSCH Pathioss Reference RS, as given by the RRC configurée! mappings. A fourth codepoint indicates that the MAC CE activâtes the PUSCH Pathloss Reference RS and replaces the SRI ID mappings to the PUSCH Pathloss Reference RS as given by the RRC configured mappings, with another SRI ID mapping to the PUSCH Pathloss Reference RS. For another example, one codepoint can indicate that the MAC CE deactivates the PUSCH Pathloss Reference RS. A second codepoint can indicate that the MAC CE activâtes the PUSCH Pathloss Reference RS and has one SRI ID in the last octet. A third codepoint can indicate that the MAC.CE activâtes the PUSCH Pathloss Reference RS and has two SRI ID in the last octet, A fourth codepoint can indicate that the MAC CE activâtes the PUSCH Pathloss Reference RS but does not change the SRI mappings, thus the MAC CE does not hâve any octets with SRI IDs.

[0118] - F (optional, not shown): indicates the presence of one SRI ID in the last octet. If set to one value, there is 1 SRI ID field and 4 R-bits in the last octet. If set to another value, there are 2 SR! ID fields and no R-bits in the last octet. The length of the field is 1 bit;

[0119] - R 314: Reserved bit, set to 0.

[0120] As a note, there is no F field illustrated in Figure 8. in this case, the number of SRis can be fixed and pre-embedded in the C field 312, for exampîe.

[0121] In this example, the MAC CE 300 includes a C field 312, instead ofthe E, A/D or F fields. The C field 312 can hâve a length of 2 (bits). This field indicates options on how the UE should interpret the MAC CE.

[0122] For example, one codepoint indicates that the MAC CE deactivates the PUSCH Pathloss Reference RS. A second codepoint indicates that the MAC CE activâtes the PUSCH Pathloss Reference RS but does not change the SRI mapping given by RRC. A third codepoint indicates that the MAC CE activâtes the PUSCH Pathloss Reference RS and adds SRI ID mappings to the PUSCH Pathloss Reference RS to the RRC configured mapping. A fourth codepoint indicates that the MAC CE activâtes the PUSCH Pathloss

-13 20966

Reference RS and replaces the SRI ID mappings to the PUSCH Pathloss Reference RS to the RRC configured mapping.

[0123] When the UE receives the MAC CE 300, the UE can détermine the indication contained in the C field 312 and apply the indication. The UE can activate the PUSCH Pathloss Reference RS and update it or add more SRI ID mappings. Based on this information, the UE can further détermine a transmit power for sending an uplink g rant/tra ns mission to the network node, for example. If the indication from the C field 312 is to deactivate the PUSCH Pathloss Reference RS, then the UE deactivates the PUSCH Pathloss Reference RS.

[0124] It should be understood that when it is stated that a MAC CE indicates or activâtes etc., it means that it is the UE or the MAC entity of the UE which performs the indication, activation etc., using the information provided in the MAC CE.

[0125] Now turning to Figure 9, a flow chart of a method 400 in a wireless device for power control will be described. Method 400 comprises:

[0126] Step 410: receiving a MAC CE from a network node, the MAC CE comprising a plurality of octets and a plurality of fields, wherein a first field ofthe plurality of fields is used to indicate a number of sets of power control parameters in a iast octet of the received MAC CE, the sets of power control parameters being associated with a reference signal used for path loss estimation;

[0127] Step 420: sending a transmission to a network node, based at least on a set of power control parameters associated with the reference signal.

[0128] For example, the reference signal can be indicated by the field for Pathloss RS ID and the power control parameters can be indicated by the fields for SRI IDs. For instance, one SRI !D (or one field for SRI ID) can indicate one set of power control parameters, where a set can comprise one or more power control parameters. A mapping between the SRI IDs and the Pathloss RS ID can be established in the MAC CE so that the power control parameters indicated by the SRI IDs are associated with the reference signal indicated by Pathloss RS ID.

[0129] For example, the wireless device may further détermine a total number of sets of power control parameters associated with the reference signal, based on a length of the MAC CE and the first field. For example, the first field can be the F field and the length of the MAC CE can be given by the L field in the MAC CE or is determined by Logical Channel ID (LCID). An example can be shown in Figure 6, where the octets, starting from the third octet to the Iast octet, contain SRI IDs. These octets contain 2 SRI IDs per octet, except for the Iast octet, which can contain one SRI ID or two SRI IDs. Therefore, knowing the size

-1420966 of the MAC CE and the number of SRI IDs in the last octet, the UE can determine a total number of SRI IDs.

[0130] In some examples, the MAC CE may further comprise a second field for indicating the RS. For example, the second field may be the field comprising/indrcating the Pathloss RS ID.

[0131] In some examples, the reference signal can be a Sounding Reference Signal (SRS).

[0132] In some examples, the first field may indicate a number of one set or two sets of power control parameters in the last octet of the MAC CE. For example, the F field indicates if there are one or two SRI IDs, in the last octet of the MAC CE.

[0133] In some examples, the received MAC CE may further comprise a third field.

[0134] In some examples, the third field may indicate to the wireless device if a mapping (or an association) between a set of power control parameters and the reference signal is updated or added or removed. In this case, the third field can be the E field. For example, the E field allows to indicate an update, adding or removal of any mappings/associations between the SRI IDs and the Pathloss RS ID, depending on the value of the E field.

[0135] In some examples, the third field (e.g. E field) can indicate to the wireless device to remove ail prevîous mappings between a set of power control parameters and the reference signal.

[0136] In some examples, the third field can indicate to the wireless device to inactivate or activate path loss estimation for uplink transmissions based on the reference signal (identified to be used for path loss estimation). In this case, the third field can be the A/D field. The path loss estimation is done for the PUSCH channel, for example. Also, when the A/D field (or the MAC CE) indicates activation, it means that the UE can determine which activated PUSCH pathloss Reference RSs (or reference signais) may be used for determining the transmit power for sending an uplink transmission to the network node, for example.

[0137] In some examples, the third field can indicate to the UE how to interpretthe received MAC CE. In this case, the third field can be the C field.

[0138] For example, the third field (e.g. C field) may comprise: a first codepoint that indicates to the wireless device to deactivate the path loss estimation for uplink transmissions (e.g. PUSCH Path loss estimation); a second codepoint that indicates to the wireless device to activate the PUSCH Path loss estimation, but does not change a mapping between the sets of power control parameters and the reference signal; a third codepoint that indicates to the wireless device to activate the PUSCH Path loss estimation and to add a set of power control parameters to be mapped to the reference signal; and a

-15 20966 fourth codepoint that indicates to the wireless device to activate the PUSCH Path loss estimation and to replace a set of power control parameters with another set of power control parameters to be mapped to the reference signal.

[0139] Figure 10 illustrâtes a flow chart of a method 500 in a network node, such as gNB, for power control. Method 500 comprises:

[0140] Step 510: sending to a wireless device a Media Access Control (MAC) Control Element (CE), the MAC CE comprising a plurality of octets, each of which comprising a plurality of fields, wherein a first field of the plurality of fields is used to indicate a number of sets of power control parameters in a last octet of the MAC CE, the set of power control parameters being associated with a reference signal used for path loss estimation; and [0141] Step 520: receiving a transmission, based on at least a set of power control parameters associated with the reference signal.

[0142] For example, the reference signal can be indicated by the field for Pathloss RS ID 108 and the power control parameters can be indicated by the fields for SRI IDs 106. For instance, one SRI ID (or one fieid for SRI ID) can indicate one set of power control parameters, where a set can comprise one or more power control parameters. A mapping between the SRI IDs and the Pathloss RS ID can be established in the MAC CE so that the power control parameters indicated by the SRI IDs are associated with the reference signal indicated by Pathloss RS ID.

[0143] In some examples, a total number of sets of power control parameters associated with the reference signal can be determined based on a length of the MAC CE and the first field.

[0144] In some examples, the length of the MAC CE can be given by a L field in the MAC CE or is determined by Logical Channel ID (LCID).

[0145] In some examples, the MAC CE further can comprise a second field for indicating the RS. For example, the second field may be the field comprising/indicating the Pathloss RS ID.

[0146] In some examples, the reference signal can be a Sounding Reference Signal (SRS).

[0147] In some examples, the first field can indicate a number of one set or two sets of power control parameters in the last octet of the MAC CE. For example, the F field indicates if there are one or two SRI IDs, in the last octet of the MAC CE.

[0148] In some examples, the MAC CE may further comprise a third field.

[0149] In some examples, the third field can indicate to the wireless device if a mapping between a set of power control parameters and the reference signal is updated or added or removed. In this case, the third field can be the E field. For example, the E field allows

- 1620966 to indicate an update, adding or removal of any mappings/associations between the SRI IDs and the Pathloss RS ID, depending on the value of the E field.

[0150] In some examples, the thîrd field (e.g. E field) can indicate to the wireless device to remove ail previous mappings between a set of power control parameters and the reference signai.

[0151] In some examples, the third field can indicate to the wireless device to inactivate or activate a path loss estimation for uplink transmissions based on the reference signal (to be used for path loss estimation). In this case, the third field can be the A/D field. The path loss estimation is done for the PUSCH channel, for example.

[0152] In some examples, the third field can indicate tofhe UE how to inferpret the received MAC CE. In this case, the third field can be the C field.

[0153] For example, the third fieid (e.g. C field) can comprise: a first codepoint that indicates to the wireless device to deactivate a path loss estimation for uplink transmissions based on the reference signal; a second codepoint that indicates to the wireless device to activate the path loss estimation for uplink transmissions based on the reference signal but does not change a mapping between the sets of power control parameters and the reference signal; a third codepoint that indicates to the wireless device to activate the path loss estimation for uplink transmissions based on the reference signal and to add a set of power control parameters to be mapped tothe reference signal; and a fourth codepoint that indicates to the wireless device to activate the path loss estimation for uplink transmissions based on the reference signal and to replace a set of power control parameters with another set of power control parameters to be mapped to the RS.

[0154] As a note, the associations between the sets of power control parameters and the reference signal can be given by mappings between SRI IDs and PUSCH pathloss ID.

[0155] Figure 11 illustrâtes an example of a wireless network 600 that may be used for wireless communications. Wireless network 600 includes UEs 610 and a plurality of radio network nodes 620 (e.g., Node Bs (NBs) Radio Network Controllers (RNCs), evolved NBs (eNBs), next génération NB (gNBs), etc.) directly or indirectly connected to a core network 630 which may comprise various core network nodes. The network 600 may use any suitable radio access network (RAN) deployment scénarios, including Universal Mobile Télécommunication System (UMTS) Terrestrial Radio Access Network (UTRAN), and Evolved UMTS Terrestrial Radio Access Network (EUTRAN). UEs 610 may be capable of communîcating directly with radio network nodes 620 over a wireless interface. In certain embodiments, UEs may also be capable of communîcating with each other via device-todevice (D2D) communication. In certain embodiments, network nodes 620 may also be

- 1720966 capable of communicating with each other, e.g. via an interface (e.g. X2 in LTE or other suitable interface).

[0156] As an example, LIE 610 may communicate with radio network node 620 over a wireless interface. That is, UE 610 may transmit wireless signais to and/or receive wireless 5 signais from radio network node 620. The wireless signais may contain voice traffic, data traffic, control signais, and/or any other suitable information. In some embodiments, an area of wireless signal coverage associated with a radio network node 620 may be referred to as a cell.

[0157] It should be noted that a UE may be a wireless device, a radio communication 10 device, target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine communication (M2M), a sensor equipped with UE, iPAD, Tablet, mobile terminais, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), Universal Serial Bus (USB) dongles, Customer Promises Equipment (CPE) etc.

[0158] In some embodiments, the “network node” can be any kind of network node which may comprise of a radio network node such as a radio access node (which can include a base station (BS), radio BS, base transceiver station, BS controller, network controller, gNB, NR BS, evolved Node B (eNB), Node B, Multi-cell/multicast Coordination Entity (MCE), relay node, access point, radio access point, Remote Radio Unit (RRU), Remote 20 Radio Head (RRH), a multi-standard BS (also known as MSR BS), etc.), a core network node (e.g., MME, SON node, a coordinating node, positioning node, MDT node, etc.), or even an external node (e.g., 3rd party node, a node external to the current network), etc. The network node may also comprise a test equipment.

[0159] In certain embodiments, network nodes 620 may interface with a radio network 25 controller (not shown). The radio network controller may control network nodes 620 and may provide certain radio resource management functions, mobility management functions, and/orother suitable functions. In certain embodiments, the functions ofthe radio network controller may be included in the network node 620. The radio network controller may interface with the core network node 640. In certain embodiments, the radio network 30 controller may interface with the core network node 640 via the interconnecting network 630.

[0160] The interconnecting network 630 may refer to any interconnecting system capable oftransmitting audio, video, signais, data, messages, or any combination ofthe preceding. The interconnectîng network 630 may include ail or a portion of a public switched téléphoné 35 network (PSTN), a public or private data network, a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a local, régional, or global

- 18 20966 communication or computer network such as the Internet, a wireline or wireless network, an enterprise intranet, or any other suitable communication link, including combinations thereof.

[0161] In some embodiments, the core network node 640 may manage the establishment of communication sessions and various other functionalities for wireless devices 310. Examples of core network node 640 may include MSC, MME, SGW, PGW, O&M, OSS, SON, positioning node (e.g. E-SMLC), MDT node, etc. Wireless devices 110 may exchange certain signais with the core network node 640 using the non-access stratum layer. In non-access stratum signaling, signais between wireless devices 610 and the core network node 640 may be transparently passed through the radio access network. In certain embodiments, network nodes 620 may interface with one or more other network nodes over an internode interface. For example, network nodes 620 may interface each other over an X2 interface.

[0162] Alfhough Figure 11 illustrâtes a particular arrangement of network 600, the présent disclosure contemplâtes that the various embodiments described herein may be applied to a variety of networks having any suitable configuration. For example, network 600 may include any suitable number of wireless devices 610 and network nodes 620, as well as any additional éléments suitable to support communication between wireless devices or between a wireless device and another communication device (such as a landline téléphoné). The embodiments may be implemented in any appropriate type of télécommunication System supporting any suitable communication standards and using any suitable components and are applicable to any radio access technology (RAT) or multiRAT Systems in which the wireless device receives and/or transmits signais (e.g., data). While certain embodiments are described for NR and/or LTE, the embodiments may be applicable to any RAT, such as UTRA, E-UTRA, narrow band internet of things (NB-loT), WiFi, Bluetooth, next génération RAT (NR, NX), 4G, 5G, LTE FDD/TDD, etc. Furthermore, the communication System 600 may itself be connected to a host computer (see Figure 20 for example). The network 600 (with the wireless devices 610 and network nodes 620) may be able to operate in LAA or unlicensed spectrum.

[0163] Figure 12 is a schematic block diagram of the wireless device 610 according to some embodiments. As iilustrated, the wireless device 610 includes circuitry 700 comprising one or more processors 710 (e.g., Central Processing Units (CPUs), Application Spécifie Integrated Circuits (ASICs), Field Programmable Gâte Arrays (FPGAs), and/or the like) and memory 720. The wireless device 610 also includes one or more transcelvers 730 each including one or more transmitters 740 and one or more receivers 750 coupled to one or more antennas 760. Furthermore, the processing circuitry

- 1920966

700 may be connected to an input interface 780 and an output interface 785. The input interface 780 and the output interface 785 may be referred to as communication interfaces. The wireless device 610 may further comprise power source 790.

[0164] In some embodiments, the functionalityofthe wireless device 610 described above may be fully or partially implemented in software that is, e.g., stored in the memory 720 and executed by the processor(s) 710. For example, the processor 710 is configured to perform ail the functionalities performed by the wireless device 610. For example, the processor 710 can be configured to perform any steps of the method 400 Figure 9.

[0165] In some embodiments, a computer program including instructions which, when executed by the at least one processor 710, causes the at least one processor 710 to carry out the functionality of the wireless device 610 according to any of the embodiments described herein is provided. In some embodiments, a carrier containing the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).

[0166] Figure 13 is a schematic block diagram of a network node 620 according to some embodiments of the present disclosure. As illustrated, the network node 620 includes a processing circuitry 800 comprising one or more processors 810 (e.g., CPUs, ASICs, FPGAs, and/or the like) and memory 820. The network node also comprises a network interface 830. The network node 320 also includes one or more transceivers 840 that each include one or more transmitters 850 and one or more receivers 860 coupled to one or more antennas 870. In some embodiments, the functionality of the network node 620 described above may be fully or partially implemented in software that is, e.g., stored in the memory 820 and executed by the processor(s) 810. For example, the processor 810 can be configured to perform any steps of the method 500 of Figure 10.

[0167] In some embodiments, a carrier comprising the computer program product is provided.

[0168] Some embodiments may be represented as a non-transitory software product stored in a machine-readable medium (also referred to as a computer-readable medium, a processor-readable medium, or a computer usable medium having a computer readable program code embodied therein). The machine-readable medium may be any suitable tangible medium including a magnetic, optical, or electrical storage medium including a diskette, compact disk read only memory (CD-ROM), digital versatile dise read only memory (DVD-ROM) memory device (volatile or non-volatile), or similar storage mechanism. The machine-readable medium may contain various sets of instructions, code sequences, configuration information, or other data, which, when executed, cause a

-2020966 processor to perform steps in a method according to one or more of the described embodiments. Software running from the machine-readable medium may interface with circuitry to perform the described tasks.

[0169] The above-described embodiments are intended to be examples only. Alterations, 5 modifications and variations may be effected to the particular embodiments by those of skill in the art without departing from the scope of the description, which is defined solely by the appended claims.

Claims (16)

1. A method performed by a wireless device comprising:

receiving a Media Access Control (MAC) Control Element (CE) from a network node, the MAC CE comprising a plurality of octets and a plurality of fields, wherein a first field of the plurality of fields is used to indicate a number of fields for indicating at least one set of power control parameters in a last octet of the received MAC CE, the at least one set of power control parameters being associated with a reference signal used for path loss estimation; and sending a transmission to a network node, based at least on a set of power control parameters associated with the reference signal.

2. The method of claim 1, further comprising determining a total number of fields for indicating at least one set of power control parameters associated with the reference signal, based on a length of the MAC CE and the first field.

3. The method of claim 2, wherein the length of the MAC CE is given by a L field or is determined by Logical Channel ID (LCID).

4. The method of any one of claims 1 to 3, wherein the MAC CE further comprises a second field for indicating the reference signal.

5. The method of any one of claims 1 to 4, wherein the first field indicates a number of one field or two fields, for indicating at least one set of power control parameters in the last octet of the MAC CE.

6. The method of any one of claims 1 to 5, wherein the received MAC CE further comprises a third field.

1. The method of claim 6, wherein the third field indicates to the wireless device if a mapping between a set of power control parameters and the reference signal is updated or added or removed.

8. The method of claim 6, wherein the third field indicates to the wireless device to inactivate or activate path loss estimation for uplink transmissions based on the reference signal.

9. The method of claim 6, wherein the third field indicates to the wireless device how to interpret the received MAC CE.

10. A wireless device comprising a communication interface and processing circuitry connected thereto and configured to perform the method of any one of claims 1 to 9.

-2220966

11. A method performed by a network node for power control, the method comprising:

sending to a wireless device a Media Access Control (MAC) Control Element (CE), the MAC CE comprising a plurality of octets, each of which comprising a plurality of fieids, wherein a first field of the plurality of fieids is used to indicate a number of fieids for indicating at least one set of power control parameters in a last octet of the MAC CE, the at least one set of power control parameters being associated with a reference signal used for path loss estimation; and receiving a transmission based on at least a set of power control parameters associated with the reference signal.

12. The method of claim 11, wherein a totai number of fieids for indicating at least one set of power control parameters associated with the reference signal is given by a length of the MAC CE and the first field.

13. The method of claim 12, wherein the length of the MAC CE is given by a L field or is determined by Logical Channel ID (LCID).

14. The method of any one of claims 11 to 13, wherein the MAC CE further comprises a second field for indicating the reference signal.

15. The method of any one of claims 11 to 14, wherein the first field indicates a number of one field or two fieids, for indicating at least one set of power control parameters in the last octet of the MAC CE.

16. A network node comprising a communication interface and processing circuitry connected thereto and configured to perform the method of any one of claims 11 to 15.

17. A computer program product comprising computer readable program code, when executed by a processor of a wireless device of claim 10, causes the processor to carry out the method of any one of ciaims 1 to 9, or when executed by a processor of a network node of claim 16, cause the processor to carry out the method of any of claims 11 to 15.