JP7432009B2 - Methods and nodes for efficient MAC CE design for directing mapping between pathloss references and multiple SRIs - Google Patents

Description

RELATED APPLICATIONS This application is filed April 23, 2020, entitled "Efficient MAC CE design for indicating mapping between pathloss reference and multiple SRI," the contents of which are incorporated herein by reference. Filed in the United States Patent and Trademark Office on claims the benefit of priority to U.S. Provisional Patent Application No. 63/014,470.

TECHNICAL FIELD This specification relates generally to wireless communication systems, and specifically to a method for indicating mapping between a path loss reference and multiple SRIs.

Introduction

New Radio (NR)

New Generation Mobile Radio Communication Systems (5G) or New Radio (NR) supports a diverse set of use cases and a diverse set of deployment scenarios.

Uplink data transmissions may be dynamically scheduled using a physical downlink control channel (PDCCH). Similar to the downlink, the user equipment (UE) first decodes the uplink grant in the PDCCH and then interprets the decoded control information in the uplink grant, such as modulation order, coding rate, uplink resource allocation, etc. based on the physical uplink shared channel (PUSCH). The UE also needs to determine the uplink power for PUSCH transmission.

PUSCH power control

The PUSCH-PowerControl information element (IE) provides the PUSCH power control parameters, as shown below, where the PUSCH power control parameters include a path loss reference signal (RS) identification information/identifier (ID) for path loss estimation. ) and a list of SRS Resource Indication (SRI)-PUSCH-PowerControl elements, one of which is selected by the Sounding Reference Signal (SRS) Resource Indication (SRI) field in the downlink control information (DCI). SRI is an SRS resource indication field in DCI that provides a per-scheduling mapping of SRI to PUSCH path loss reference ID.

PUSCH-PowerControl
IE PUSCH-PowerControl is used to configure UE-specific power control parameters for PUSCH.
PUSCH-PowerControl information element

Media Access Control (MAC) Control Element (CE)

A MAC protocol data unit (PDU) is a string of bits that is byte-aligned (ie, a multiple of 8 bits) in length. A MAC service data unit (SDU) is a bit string that is byte-aligned (ie, a multiple of 8 bits) in length. The MAC CE is a bit string that is byte-aligned (ie, a multiple of 8 bits) in length.

The MAC subheader is a bit string that is byte-aligned (ie, a multiple of 8 bits) in length. Each MAC subheader is placed immediately before the corresponding MAC SDU, MAC CE, or padding.

A MAC PDU consists of one or more MAC sub-PDUs. Each MAC sub-PDU consists of one of the following:

- MAC subheader only (including padding),

- MAC subheader and MAC SDU,

- MAC subheader and MAC CE,

- MAC subheader and padding.

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

The MAC subheader, except for the fixed size MAC CE, the padding, and the MAC SDU containing the uplink (UL) common control channel (CCCH), consists of header fields R/F/LCID/(eLCID)/L. The MAC subheader for a fixed size MAC CE, padding and MAC SDU containing UL CCCH consists of two header fields R/LCID. The extended logical channel ID (eLCID) field is present when the LCID field is set to a particular value and absent otherwise.

Some examples of MAC subheaders are given in FIGS. 1-3.

FIG. 1 shows an R/F/LCID/(eLCID)/L MAC subheader with an 8-bit L field.

FIG. 2 shows an R/F/LCID/(eLCID)/L MAC subheader with a 16-bit L field.

FIG. 3 shows the R/LCID/(eLCID) MAC subheader.

A MAC CE with variable size has a subheader containing an L field. A MAC CE with a fixed size has a subheader that does not include an L field since the size of the MAC CE is determined by the LCID.

Mapping between SRI and PUSCH path loss reference ID

The network node uses the MAC CE to map (or associate) the SRI ID to the PUSCH path loss reference RS (reference signal) ID. The 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 38.321 16.0.0 currently incorporates MAC CE in Section 6.1.3.28 as follows:

6.1.3.28 PUSCH Path Loss Reference RS Activation/Deactivation (Deactivation) MAC CE

“The PUSCH Path Loss Reference RS Activation/Deactivation MAC CE is identified by the MAC subheader with the LCID specified in Table 6.2.1-1. It has a fixed size of 24 bits.

- Serving Cell ID: This field indicates the identity of the serving cell containing the activated/deactivated SRS resource set. The length of the field is 5 bits.

- BWP ID: This field indicates the UL BWP as the code point of the DCI Bandwidth Portion Indicator field specified in TS 38.212, [9], which contains the activated/deactivated SRS resource set. do. The length of the field is 2 bits.

- SRI ID: This field indicates the SRI PUSCH power control ID identified by sri-PUSCH-PowerControlId specified in TS38.331 [5]. The length of the field is 4 bits.

- PUSCH Pathloss Reference RS ID: This field indicates the PUSCH Pathloss Reference RS ID identified by the PUSCH-PathlossReferenceRS-Id specified in TS 38.331 [5], which should be activated/deactivated. do. The length of the field is 6 bits.

- R: Reserved bit set to 0.

For example, FIG. 4 shows a PUSCH Path Loss Reference RS Activation/Deactivation MAC CE that includes the fields just described above.

There is a problem with the current MAC CE. For example, the problem is that DCI chooses a one-to-one mapping between SRI and PUSCH Pathloss Reference RS ID, but the configuration given by Radio Resource Control (RRC) and MAC is one Pathloss Reference RS ID. It is possible to have multiple SRIs mapped to an ID. Furthermore, the UE can only follow four pathloss reference RS IDs at the same time.

To solve this problem, previous solutions suggested having a MAC CE, where multiple SRIs are included in the MAC CE. Therefore, the MAC CE is redesigned as shown in FIG.

FIG. 5 shows one MAC CE that can include multiple SRI IDs associated with the same pathloss RS.

The MAC CE includes a C1 field that is used to indicate the presence of additional SRI IDs. The MAC CE also includes a SUL field that is used to indicate that the MAC CE applies to supplementary uplink (SUL) carrier configuration.

The other fields are the same as described above with respect to FIG.

In this case, the network (NW)/network node includes multiple SRI IDs with the same mapping for the Path Loss Reference Signal (PL RS), ie PUSCH Path Loss Reference RS ID.

However, this particular MAC CE proposal wastes octets. There are at least three problems with this solution.

unnecessary field

The C1 field is not useful because the number of SRI ID fields can be inferred from the length field in the MAC CE header (not shown in the figure). If the C1 field is included during the overhead calculation, the MAC CE overhead will be larger.

overhead

Three R bits are included for each new SRI ID added. For example, when one SRI ID is included, 20% of the MAC CE consists of R bits, and when eight SRI IDs are included, more than 30% are R bits. This constitutes pure overhead since the R bit is not used. Therefore, the overhead increases with the number of SRI IDs added.

size

One octet is added for each new SRI ID, but the SRI ID field is only 4 bits. The size of the MAC CE is 2 octets + the number of SRI IDs.

Furthermore, it also needs to be possible to delete the mapping between the SRI ID and the pathloss reference RS ID. Neither the previous solution nor the current MAC CE can do that. The previous solution and current MAC CE can only add mappings.

Therefore, a more efficient design is needed, in which it is also possible to eliminate the mapping between SRI ID and pathloss reference RS ID.

Generally stated, embodiments of the present disclosure enable a lean design of MAC CE and mapping of path loss reference IDs to several SRIs based on the following.

- The length field (in the subheader) is used to determine the length of the MAC CE.

- The F field is used to determine the content of the last octet.

To enable deletion of the mapping between path loss reference RS ID and SRI, the following may be used.

- The E field is used to control whether the MAC CE is adding or removing SRI mapping from a particular Pathloss Reference RS ID.

According to one aspect, some embodiments include a method performed by a wireless device. For example, the method includes receiving a MAC CE from a network node, the MAC CE including a plurality of octets and a plurality of fields, a first field of the plurality of fields being a MAC CE of the received MAC CE. receiving a MAC CE used to indicate the number of sets of power control parameters in the last octet, the sets of power control parameters being associated with reference signals used for path loss estimation; , sending a transmission to a network node based on a set of power control parameters associated with the reference signal.

According to another aspect, some embodiments are configured or operable to perform one or more functions (e.g., actions, operations, steps, etc.) described herein. Including wireless devices.

In some embodiments, the wireless device includes one or more communication interfaces configured to communicate with one or more other wireless nodes and/or one or more network nodes; and operably connected processing circuitry, the processing circuitry being configured to perform one or more functions described herein. In some embodiments, the processing circuitry comprises at least one processor and instructions that, when executed by the processor, configure the at least one processor to perform one or more functions described herein. and at least one memory for storing.

In some embodiments, a wireless device may include one or more functional modules configured to perform one or more functions described herein.

According to one aspect, some embodiments include a method performed by a network node. For example, the method is to send a MAC CE to a wireless device, the MAC CE including a plurality of octets, each of the plurality of octets including a plurality of fields, and a first field of the plurality of fields , used to indicate the number of sets of power control parameters in the last octet of the MAC CE, where the set of power control parameters is associated with the reference signal used for path loss estimation. and receiving a transmission based on at least the set of power control parameters associated with the reference signal.

According to another aspect, some embodiments are configured or operable to perform one or more functions (e.g., actions, operations, steps, etc.) described herein. Contains network nodes.

In some embodiments, a network node includes one or more communication interfaces configured to communicate with one or more other wireless nodes and/or one or more network nodes; and operably connected processing circuitry, the processing circuitry being configured to perform one or more functions described herein. In some embodiments, the processing circuitry comprises at least one processor and instructions that, when executed by the processor, configure the at least one processor to perform one or more functions described herein. and at least one memory for storing.

In some embodiments, a network node may include one or more functional modules configured to perform one or more of the functions described herein.

According to yet another aspect, some embodiments perform one or more functions described herein when performed by processing circuitry (e.g., at least one processor) of a network node or wireless device. a non-transitory computer-readable medium storing a computer program product comprising instructions for configuring processing circuitry to perform.

Advantages/technical benefits of embodiments of the present disclosure are as follows.

- The proposed design does not contain unnecessary fields. The size of the MAC CE is determined by the length field in the header instead of using an additional field in the MAC CE.

- 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 when the number of SRI IDs is added, the portion of R bits will decrease.

- One octet is added for every other SRI ID. This means that the size of the MAC CE is 2 + CEIL (number of SRI IDs divided by 2), where CEIL() is the ceiling function, where the input is rounded to the nearest integer It will be done.

- Further functionality is enabled by the E field, which may be added to state whether the MAC CE is adding or removing an SRI mapping from a particular Pathloss Reference RS ID.

The Summary of the Invention is not an extensive overview of all contemplated embodiments and does not identify key or critical aspects or features of any or all embodiments or It does not define the scope of the form. To that extent, other aspects and features will become apparent to those skilled in the art upon consideration of the following description of specific embodiments in conjunction with the accompanying drawings.

Exemplary embodiments are explained in more detail with reference to the following figures.

FIG. 3 shows an R/F/LCID/(eLCID)/L MAC subheader with an 8-bit L field. FIG. 3 shows an R/F/LCID/(eLCID)/L MAC subheader with a 16-bit L field. FIG. 3 is a diagram showing an R/LCID/(eLCID) MAC subheader. FIG. 6 is a diagram illustrating PUSCH path loss reference RS activation/deactivation MAC CE; FIG. 3 shows a previous solution MAC CE for accommodating multiple SRIs; FIG. 3 illustrates a MAC CE with F-field, according to an embodiment of the present disclosure. FIG. 3 illustrates a MAC CE with an A/D field, according to one embodiment. FIG. 3 illustrates a MAC CE with a C field, according to an embodiment of the present disclosure. 2 is a flowchart of a method in a wireless device, according to one embodiment. 3 is a flowchart of a method at a network node, according to one embodiment. FIG. 1 is a diagram illustrating an example of a wireless communication system in which embodiments of the present disclosure may be implemented. 1 is a block diagram illustrating a wireless device, according to some embodiments of the present disclosure. FIG. 1 is a block diagram illustrating a wireless device, according to some embodiments of the present disclosure. FIG. 1 is a block diagram illustrating a network node, according to some embodiments of the present disclosure. FIG. 1 is a block diagram illustrating a network node, according to some embodiments of the present disclosure. FIG. FIG. 2 is a diagram illustrating a virtualized environment of network nodes, according to some embodiments of the present disclosure.

The embodiments described below represent information to enable any person 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 specifically addressed herein. It is to be understood that these concepts and applications are within the scope of the description.

In the description that follows, numerous specific details are set forth. However, it is understood that embodiments may be practiced without these specific details. In other instances, well-known circuits, structures and techniques have not been shown in detail in order not to obscure the understanding of the description. Those skilled in the art, using the included description, will be able to implement appropriate functionality without undue experimentation.

References herein to "one embodiment," "an embodiment," "exemplary embodiment," and the like are references to the described embodiment having specific features, structure, or characteristics, but not every embodiment necessarily includes a particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described with respect to an embodiment, such feature, structure, or characteristic may be implemented with respect to other embodiments, whether or not explicitly described. is submitted to be within the knowledge of a person skilled in the art.

As used herein, the singular forms "a," "an," and "the" shall include the plural forms unless the context clearly dictates otherwise. Additionally, as used herein, the terms "comprises," "comprising," "includes," and/or "including" refer to Specifies the presence of a feature, integer, step, action, element, and/or component, but one or more other features, integers, steps, actions, elements, components, and/or groups thereof It will be understood that this does not exclude the presence or addition of.

A general example of a PUSCH path loss reference RS activation/deactivation MACE CE 100 that allows solving the above-mentioned problem is shown in FIG. 6. For example, the PUSCH Pathloss Reference RS activation/deactivation MAC CE activates or deactivates/deactivates a certain PUSCH Pathloss Reference RS identified by the PUSCH-PathlossReferenceRS-Id specified in 3GPP TS38.331. Allows activation. This means that a radio resource control (RRC) configured RS for the UE to be considered as a path loss reference RS is activated (e.g. becomes active) as directed to the UE by the MAC CE. or may be deactivated (eg, become/remain inactive). If a Path Loss Reference RS is active, the UE considers the Path Loss Reference RS to be available. If a Path Loss Reference RS is inactive (eg, deactivated), the UE assumes that the Path Loss Reference RS is not available (despite the "placeholder" RRC configuration).

Note that the terms "pathloss reference RS ID" or "pathloss reference ID" or "pathloss reference" or "pathloss RS ID" may be used interchangeably.

MAC CE 100 has the following fields.

- Serving Cell ID 102: This field indicates the identity of the serving cell containing the activated/deactivated SRS resource set. The length of the field is 5 bits.

- BWP ID 104: This field indicates the UL BWP as the code point of the DCI Bandwidth Portion Indicator field specified in 3GPP TS38.212, which contains the activated/deactivated SRS resource set. The length of the field is 2 bits.

- SRI ID 106: This field indicates the SRI PUSCH power control ID identified by sri-PUSCH-PowerControlId specified in 3GPP TS38.331. The length of the field is 4 bits.

- Pathloss RS ID 108: This field indicates the PUSCH Pathloss Reference RS ID identified by the PUSCH-PathlossReferenceRS-Id specified in 3GPP TS38.331, which should be activated/deactivated. The length of the field is 6 bits.

- E110: A mapping (or association) between a Pathloss RS ID and SRI ID(s) is added (or updated if the SRI ID was previously mapped to another Pathloss RS ID) ) or be deleted (in which case the SRI ID(s) are not mapped to the Pathloss RS ID). If a field is set to a certain value, a mapping is added/updated. If the field is set to another value, the mapping is removed. The length of the field is 1 bit.

- F112: Indicates the presence of one SRI ID in the last octet. When set to a value, there is one SRI ID field and four R bits in the last octet. If set to another value, there are two SRI ID fields in the last octet and no R bit. The length of the field is 1 bit.

- Reserved bit set to R114:0.

As can be seen from the SRI ID field 106, the SRI ID is used to indicate a set of power control elements/parameters. This set of power control parameters may be directed to be mapped to a reference signal used for path loss estimation.

In a first example, the PUSCH Path Loss Reference RS Activation/Deactivation MAC CE may include one or two SRI fields starting from octet 3 to octet n (see, eg, FIG. 6). Octet 2 may include field F112, which determines whether the last octet includes one or two SRI fields. Note that in this first example there may be no E field.

On the UE side, when the UE receives a MAC CE, such as MAC CE 100, the UE determines from the length field how many octets the MAC CE body contains. Additionally, the UE determines from the F field how many SRI fields the last octet contains. Combining the information from the length field and the information from the F field, the UE can determine how many SRI fields are mapped (or associated) to one pathloss reference RS. Based on this information, the UE can, for example, determine the transmit power for sending uplink grants/transmissions to network nodes.

In the second example, the MAC CE includes an E field in addition to the F field. The E field determines how the UE should update the mapping of SRI to Path Loss Reference RS. More specifically, the E field is updated when a mapping between the Pathloss RS ID and the SRI ID(s) is added (or updated if the SRI ID was previously mapped to another Pathloss RS ID). (in which case the SRI ID(s) are not mapped to a pathloss RS ID). For example, if a field is set to a certain value, a mapping is added/updated. If the field is set to another value, it means that the mapping given in the MAC CE should be deleted by the UE.

Alternatively, the E field indicates whether the UE should forget any or all previous mappings related to the SRI and Pathloss Reference RS given in this MAC CE; It may be possible to control whether the CE should be considered to provide additional mapping for the indicated SRI. In this case, for example, if the E field is set to a value of 0, the UE forgets the mapping, and if the E field is set to 1, the UE adds a mapping between the SRI ID and the pathloss reference RS ID. It is considered as a mapping of Therefore, the E field indicates to the UE as to the mapping that should be either forgotten or added depending on the value of the E field.

When the UE receives the MAC CE in this second example, the UE may determine the number of SRI fields to be mapped to one path loss reference RS based on the length field and the F field. Furthermore, from the E field, the UE can decide whether the SRI field is updated/added or deleted with respect to the previous configuration the UE had for the mapping. Based on this information (i.e., the length field and the F and E fields), the UE can, for example, determine the transmit power for sending the uplink grant/transmission to the network node.

Another example of a PUSCH path loss reference RS activation/deactivation MAC CE 200 is shown in FIG.

In this example, field E110 (of FIG. 6) is replaced by A/D field 210.

More specifically, the MAC CE 200 of FIG. 7 includes the following fields.

- Serving Cell ID 202: This field indicates the identity of the serving cell containing the activated/deactivated SRS resource set. The length of the field is 5 bits.

- BWP ID 204: This field indicates the UL BWP as the code point of the DCI Bandwidth Portion Indicator field specified in 3GPP TS38.212, which contains the activated/deactivated SRS resource set. The length of the field is 2 bits.

- SRI ID 206: This field indicates the SRI PUSCH power control ID identified by sri-PUSCH-PowerControlId specified in 3GPP TS38.331. The length of the field is 4 bits.

- Pathloss RS ID 208: This field indicates the PUSCH Pathloss Reference RS ID identified by the PUSCH-PathlossReferenceRS-Id specified in 3GPP TS 38.331, which should be activated/deactivated. The length of the field is 6 bits.

- A/D 210: This field indicates whether the indicated PUSCH Path Loss Reference RS should be activated or deactivated. The field is set to one value to indicate activation and another value to indicate deactivation. The length of the field is 1 bit.

- F212: Indicates the presence of one SRI ID in the last octet. When set to a value, there is one SRI ID field and four R bits in the last octet. If set to another value, there are two SRI ID fields in the last octet and no R bit. The length of the field is 1 bit.

- Reserved bit set to R214:0.

In this example, the MAC CE includes an A/D field 210. This field indicates whether the indicated PUSCH path loss reference RS should be activated or deactivated. For example, the field may be set to 1 to indicate activation; otherwise, the field may indicate deactivation.

When the UE receives the MAC CE 200, the UE may decide whether the indicated PUSCH Path Loss Reference RS is activated or deactivated. If the A/D 210 field indicates activation, the UE activates the PUSCH Path Loss Reference RS. Based on this information, the UE may, for example, determine which activated PUSCH path loss reference RSs may be used to determine the transmit power for sending uplink transmissions to the network node. Can be done. If the A/D 210 field indicates deactivation, the UE does not use the deactivated PUSCH Path Loss Reference RS to determine transmit power.

Another example of a PUSCH path loss reference RS activation/deactivation MAC CE 300 is shown in FIG.

In this example, field C 312 may replace two of three fields: E field 110, A/D field 210, and F field 112 or 212.

More specifically, the MAC CE 300 of FIG. 8 includes the following fields.

- Serving Cell ID 302: This field indicates the identity of the serving cell containing the activated/deactivated SRS resource set. The length of the field is 5 bits.

- BWP ID 304: This field indicates the UL BWP as the code point of the DCI Bandwidth Portion Indicator field specified in 3GPP TS38.212, which contains the activated/deactivated SRS resource set. The length of the field is 2 bits.

- SRI ID 306: This field indicates the SRI PUSCH power control ID identified by sri-PUSCH-PowerControlId specified in 3GPP TS38.331. The length of the field is 4 bits.

- Pathloss RS ID 308: This field indicates the PUSCH Pathloss Reference RS ID identified by the PUSCH-PathlossReferenceRS-Id specified in 3GPP TS 38.331, which should be activated/deactivated. The length of the field is 6 bits.

- C3012: This field indicates options regarding how the UE should interpret the MAC CE300. For example, one code point indicates that the MAC CE deactivates the PUSCH path loss reference RS. The second code point indicates that the MAC CE activates the PUSCH path loss reference RS but does not change the SRI mapping with the reference signal given by RRC. The third code point indicates that the MAC CE activates the PUSCH Path Loss Reference RS and adds the SRI ID mapping to the PUSCH Path Loss Reference RS given by the RRC configured mapping. The fourth code point is when the MAC CE activates a PUSCH Path Loss Reference RS and sets the SRI ID mapping to PUSCH Path Loss Reference RS given by the RRC configured mapping to another SRI ID mapping to PUSCH Path Loss Reference RS. Instruct to replace. In another example, one code point may indicate that the MAC CE deactivates the PUSCH path loss reference RS. The second code point may indicate that the MAC CE activates the PUSCH Path Loss Reference RS and has one SRI ID in the last octet. The third code point may indicate that the MAC CE activates the PUSCH Path Loss Reference RS and has two SRI IDs in the last octet. The fourth code point may indicate that the MAC CE activates the PUSCH path loss reference RS but does not change the SRI mapping, and therefore the MAC CE does not have an octet with the SRI ID.

- F (optional, not shown): Indicates the presence of one SRI ID in the last octet. When set to a value, there is one SRI ID field and four R bits in the last octet. If set to another value, there are two SRI ID fields in the last octet and no R bit. The length of the field is 1 bit.

- R314: Reserved bit set to 0.

As a note, there is no F field shown in FIG. In this case, the number of SRIs may be fixed and pre-embedded in the C-field 312, for example.

In this example, MAC CE 300 includes a C field 312 instead of an E field, A/D field, or F field. C field 312 may have a length of 2 (bits). This field indicates options on how the UE should interpret the MAC CE.

For example, one code point indicates that the MAC CE deactivates the PUSCH path loss reference RS. The second code point indicates that the MAC CE activates the PUSCH Path Loss Reference RS but does not change the SRI mapping given by RRC. The third code point indicates that the MAC CE activates the PUSCH Path Loss Reference RS and adds the SRI ID mapping to the PUSCH Path Loss Reference RS to the RRC configured mappings. The fourth code point indicates that the MAC CE activates the PUSCH Path Loss Reference RS and replaces the SRI ID mapping to the PUSCH Path Loss Reference RS with the RRC configured mapping.

When the UE receives the MAC CE 300, the UE may determine the instructions included in the C field 312 and apply the instructions. The UE may activate the PUSCH Path Loss Reference RS, update the PUSCH Path Loss Reference RS, or add more SRI ID mappings. Based on this information, the UE can further determine, for example, the transmit power for sending uplink grants/transmissions to network nodes. If the indication from the C field 312 is to deactivate the PUSCH Path Loss Reference RS, the UE deactivates the PUSCH Path Loss Reference RS.

When a MAC CE is mentioned to direct or activate, etc., this means that it is the UE or the UE's MAC entity that performs the direction, activation, etc. using the information provided in the MAC CE. be understood to mean that

Referring now to FIG. 9, a flowchart of a method 400 in a wireless device for power control is illustrated. Method 400 includes the following.

Step 410: receiving a MAC CE from a network node, the MAC CE including multiple octets and multiple fields, a first field of the multiple fields being the last field of the received MAC CE. receiving a MAC CE used to indicate the number of a set of power control parameters in an octet, the set of power control parameters being associated with a reference signal used for path loss estimation;

Step 420: Sending a transmission to the network node based at least on a set of power control parameters associated with the reference signal.

For example, a reference signal may be indicated by a field for path loss RS ID, and a power control parameter may be indicated by a field for SRI ID. For example, one SRI ID (or one field for an SRI ID) can indicate one set of power control parameters, where the set can include one or more power control parameters. can. A mapping between the SRI ID and the pathloss RS ID may be established in the MAC CE such that the power control parameters indicated by the SRI ID are related to the reference signals indicated by the pathloss RS ID.

For example, the wireless device may further determine the total number of sets of power control parameters associated with the reference signal based on the length and the first field of the MAC CE. For example, the first field may be the F field and the length of the MAC CE may be given by the L field in the MAC CE or determined by the Logical Channel ID (LCID). An example may be shown in FIG. 6, where octets starting from the third octet to the last octet include the SRI ID. These octets contain two SRI IDs per octet except the last octet, which may contain one SRI ID or two SRI IDs. Therefore, knowing the size of the MAC CE and the number of SRI IDs in the last octet, the UE can determine the total number of SRI IDs.

In some examples, the MAC CE may further include a second field to indicate a reference signal. For example, the second field may be a field containing/indicating a path loss RS ID.

In some examples, the reference signal may be a sounding reference signal (SRS).

In some examples, the first field may indicate the 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 whether there is one or two SRI IDs in the last octet of the MAC CE.

In some examples, the received MAC CE may further include a third field.

In some examples, the third field indicates to the wireless device whether the mapping (or association) between the set of power control parameters and the reference signal is updated, added, or removed. It is possible. In this case, the third field may be an E field. For example, the E field allows to indicate the update, addition or deletion of mapping/association between SRI ID and Pathloss RS ID depending on the value of the E field.

In some examples, the third field (eg, the E field) can instruct the wireless device to delete all previous mappings between the set of power control parameters and the reference signal.

In some examples, the third field allows the wireless device to deactivate or activate path loss estimation for uplink transmissions based on the reference signal (identified to be used for path loss estimation). can be instructed to do so. In this case, the third field may be an A/D field. Path loss estimation is performed for the PUSCH channel, for example. Also, when the A/D field (or MAC CE) indicates activation, it determines which activated PUSCH path loss reference e.g. This means that the UE can decide whether the RS (or reference signal) can be used.

In some examples, the third field may instruct the UE how to interpret the received MAC CE. In this case, the third field may be the C field.

For example, the third field (e.g., the C field) includes a first code point that instructs the wireless device to deactivate path loss estimation (e.g., PUSCH path loss estimation) for uplink transmissions, and the wireless device a second code point that instructs the wireless device to activate PUSCH path loss estimation, but does not change the mapping between the set of power control parameters and the reference signal; a third code point instructing the wireless device to: activate PUSCH path loss estimation; and add a set of power control parameters to be mapped to the reference signal; and a fourth code point instructing to replace the set of power control parameters with another set of power control parameters to be mapped to the reference signal.

FIG. 10 shows a flowchart of a method 500 at a network node, such as a gNB, for power control. Method 500 includes the following.

Step 510: Sending a media access control (MAC) control element (CE) to the wireless device, wherein the MAC CE includes a plurality of octets, each of the plurality of octets includes a plurality of fields, and one of the plurality of fields. The first field of these is used to indicate the number of sets of power control parameters in the last octet of the MAC CE, and the set of power control parameters is related to the reference signal used for path loss estimation. sending a media access control (MAC) control element (CE),

Step 520: Receiving a transmission based on at least a set of power control parameters associated with a reference signal.

For example, a reference signal may be indicated by a field for path loss RS ID 108 and a power control parameter may be indicated by a field for SRI ID 106. For example, one SRI ID (or one field for an SRI ID) can indicate one set of power control parameters, where the set can include one or more power control parameters. can. A mapping between the SRI ID and the pathloss RS ID may be established in the MAC CE such that the power control parameters indicated by the SRI ID are related to the reference signals indicated by the pathloss RS ID.

In some examples, the total number of sets of power control parameters associated with reference signals may be determined based on the length and first field of the MAC CE.

In some examples, the length of the MAC CE may be given by the L field in the MAC CE or determined by the logical channel ID (LCID).

In some examples, the MAC CE may further include a second field to indicate a reference signal. For example, the second field may be a field containing/indicating a path loss RS ID.

In some examples, the reference signal may be a sounding reference signal (SRS).

In some examples, the first field may indicate the 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 whether there is one or two SRI IDs in the last octet of the MAC CE.

In some examples, the MAC CE may further include a third field.

In some examples, the third field can instruct the wireless device whether the mapping between the set of power control parameters and the reference signal is updated, added, or removed. . In this case, the third field may be an E field. For example, the E field allows to indicate the update, addition or deletion of mapping/association between SRI ID and Pathloss RS ID depending on the value of the E field.

In some examples, the third field (eg, the E field) can instruct the wireless device to delete all previous mappings between the set of power control parameters and the reference signal.

In some examples, the third field instructs the wireless device to deactivate or activate path loss estimation for the uplink transmission based on the reference signal (to be used for path loss estimation). can do. In this case, the third field may be an A/D field. Path loss estimation is performed for the PUSCH channel, for example.

In some examples, the third field may instruct the UE how to interpret the received MAC CE. In this case, the third field may be the C field.

For example, the third field (e.g., the C field) includes a first code point that instructs the wireless device to deactivate path loss estimation for uplink transmissions based on the reference signal; a second code point instructing the wireless device to activate path loss estimation for an uplink transmission based on the reference signal, but not changing a mapping between the set of power control parameters and the reference signal; a third code point instructing the radio to activate path loss estimation for the uplink transmission based on the reference signal and to add a set of power control parameters to be mapped to the reference signal; A device is configured to activate 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 reference signal. and a fourth code point indicating the .

Note that the association between the set of power control parameters and the reference signal may be given by a mapping between SRI ID and PUSCH path loss ID.

FIG. 11 shows an example of a wireless network 600 that may be used for wireless communications. The wireless network 600 includes a UE 610 and a plurality of wireless network nodes 620 (e.g., a Node B (NB) radio network controller (RNC), an evolved NB (eNB), next generation NB (gNB), etc.). Network 600 may use any suitable radio access network (RAN) deployment scenario, including a Universal Mobile Telecommunication System (UMTS) terrestrial radio access network (UTRAN) and an enhanced UMTS terrestrial radio access network (EUTRAN). UE 610 may be able to communicate directly with wireless network node 620 over the air interface. In some embodiments, UEs may also be able to communicate with each other via device-to-device (D2D) communication. In some embodiments, network nodes 620 may also be able to communicate with each other via an interface (eg, X2 in LTE, or other suitable interface), for example.

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

UE includes a wireless device, a wireless communication device, a target device, a D2D (device to device) UE, a machine type UE or a UE capable of machine-to-machine communication (M2M), a sensor equipped with a UE, an iPad, a tablet, a mobile terminal, Note that it can be a smartphone, laptop embedded equipment (LEE), laptop mounted equipment (LME), universal serial bus (USB) dongle, customer premises equipment (CPE), etc.

In some embodiments, a "network node" includes (base station, radio base station, base transceiver station, base station controller, network controller, gNB, NR BS, evolved Node B (eNB), Node B, multi-cell/ Wireless (which can include Multicast Coordinating Entities (MCEs), relay nodes, access points, wireless access points, remote radio units (RRUs), remote radio heads (RRHs), multi-standard BSs (also known as MSR BSs), etc. Radio network nodes such as access nodes, core network nodes (e.g. MME, SON nodes, cooperation nodes, positioning nodes, MDT nodes, etc.) and even external nodes (e.g. third party nodes, nodes external to the current network) ), etc., may be any type of network node. A network node may also include test equipment.

In some embodiments, network node 620 may interface with a wireless network controller (not shown). A radio network controller may control network node 620 and may provide some radio resource management functions, mobility management functions, and/or other suitable functions. In some embodiments, radio network controller functionality may be included in network node 620. A radio network controller may interface with core network node 640. In some embodiments, the radio network controller may interface with core network node 640 via interconnection network 630.

Interconnection network 630 may refer to an interconnection system capable of transmitting audio, video, signals, data, messages, or any combination of the foregoing. Interconnection network 630 may include a local network such as a public switched telephone network (PSTN), a public or private data network, a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), the Internet, a wired or wireless network, etc. , regional, or global communications or computer networks, corporate intranets, or combinations thereof.

In some embodiments, core network node 640 may manage communication session establishment and various other functions for wireless device 310. Examples of core network nodes 640 may include MSC, MME, SGW, PGW, O&M, OSS, SON, positioning node (eg, E-SMLC), MDT node, etc. Wireless device 110 may exchange some signals with core network node 640 using non-access stratum layers. With non-access stratum signaling, signals between wireless device 610 and core network node 640 may be passed transparently through the radio access network. In some embodiments, network node 620 may interface with one or more other network nodes on an inter-node interface. For example, network nodes 620 may interface with each other on X2 interfaces.

Although FIG. 11 depicts a particular configuration of network 600, this disclosure contemplates that the various embodiments described herein may be applied to various networks having any suitable configuration. . For example, network 600 may support any suitable number of wireless devices 610 and network nodes 620 and communications between wireless devices or between a wireless device and another communications device (such as a landline telephone). may include any additional elements suitable for. Embodiments may be implemented in any suitable type of communication system supporting any suitable communication standard and using any suitable components, in which a wireless device receives signals (e.g., data) and/or Applicable to any radio access technology (RAT) or multi-RAT system that transmits. Although some embodiments are described for NR and/or LTE, embodiments include UTRA, E-UTRA, Narrowband Internet of Things (NB-IoT), WiFi, Bluetooth, Next Generation RAT (NR, NX) , 4G, 5G, LTE FDD/TDD, etc., may be applicable to any RAT. Further, the communication system 600 may itself be connected to a host computer (see, eg, FIG. 20). Network 600 (with wireless device 610 and network node 620) may be capable of operating in the LAA or unlicensed spectrum.

FIG. 12 is a schematic block diagram of a wireless device 610, according to some embodiments of the present disclosure. As shown, the wireless device 610 includes one or more processors 710 (e.g., central processing unit (CPU), application specific integrated circuit (ASIC), field programmable gate array (FPGA), etc.) and memory 720. and a circuit 700 comprising: Wireless device 610 also includes one or more transceivers 730, each including one or more transmitters 740 and one or more receivers 750 coupled to one or more antennas 760. Further, processing circuit 700 may be connected to input interface 780 and output interface 785. Input interface 780 and output interface 785 are sometimes referred to as communication interfaces. Wireless device 610 may further include a power source 790.

In some embodiments, the functionality of wireless device 610 described above is implemented entirely or partially in software, e.g., stored in memory 720 and executed by processor(s) 710. can be done. For example, processor 710 is configured to perform all functions performed by wireless device 610. For example, processor 710 may be configured to perform any of the steps of method 400 FIG.

In some embodiments, a computer includes instructions that, when executed by the at least one processor 710, cause the at least one processor 710 to perform the functions of the wireless device 610 in accordance with any of the embodiments described herein. program will be provided. In some embodiments, a carrier is provided containing the computer program product described above. The carrier is one of an electronic signal, an optical signal, a wireless signal, or a computer readable storage medium (eg, a non-transitory computer readable medium such as memory).

FIG. 13 is a schematic block diagram of a wireless device 610, according to some other embodiments of the present disclosure. Wireless device 610 includes one or more modules 795, each of which is implemented in software. Module(s) 795 provides the functionality of wireless device 610 as described herein. For example, module 795 includes a receiving module operable to perform step 410 of FIG. 9 and a transmitting module operable to perform step 420 of FIG.

FIG. 14 is a schematic block diagram of a network node 620, according to some embodiments of the present disclosure. As shown, network node 620 includes processing circuitry 800 that includes one or more processors 810 (eg, CPU, ASIC, FPGA, etc.) and memory 820. The network node also includes a network interface 830. Network node 320 also includes one or more transceivers 840, each including one or more transmitters 850 and one or more receivers 860 coupled to one or more antennas 870. In some embodiments, the functionality of network node 620 described above is implemented entirely or partially in software, e.g., stored in memory 820 and executed by processor(s) 810. can be done. For example, processor 810 may be configured to perform any steps of method 500 of FIG. 10.

FIG. 15 is a schematic block diagram of a network node 620, according to some other embodiments of the present disclosure. Network node 620 includes one or more modules 880, each of which is implemented in software. Module(s) 880 provides the functionality of network node 620 as described herein. Module(s) 880 may include a transmitting module operable to implement step 510 of FIG. 10 and a receiving module operable to implement step 520 of FIG. 10.

FIG. 16 is a schematic block diagram illustrating a virtualized embodiment of a wireless device 610 or network node 620, according to some embodiments of the present disclosure. As used herein, "virtualized" node 1600 means that at least a portion of the functionality of network node 620 or wireless device 610 is A network node 620 or wireless device 610 that is implemented as a virtual component (via virtual machine(s) running on a physical processing node). For example, in FIG. 16, an instance or virtual appliance 1620 is provided that implements the methods or portions of the methods of some embodiments. One or more instances run in cloud computing environment 1600. The cloud computing environment provides processing circuitry 1630 and memory 1690-1 for one or more instances or virtual applications 1620. Memory 1690-1 includes instructions 1695 executable by processing circuitry 1660 to cause instance 1620 to perform a method or portion of a method described herein with respect to some embodiments. It is possible to operate.

Cloud computing environment 1600 comprises one or more general purpose network devices including hardware 1630, which may be a commercial off-the-shelf (COTS) processor, a dedicated application specific integrated circuit (ASIC), or a digital or analog Also known as a network interface card (1 one or more network interface controllers (NICs) 1670. The general purpose network device also includes a non-transitory machine-readable storage medium 1690-2 that stores software and/or instructions 1695 executable by the processor 1660. In operation, the processor/processing circuit(s) 1660 may be connected to a hypervisor 1650, sometimes referred to as a virtual machine monitor (VMM), and one or more virtual machines 1640 run by the hypervisor 1650. Execute software/instructions 1695 to instantiate.

A virtual machine 1640 is a software implementation of a physical machine that runs programs as if they were running on a physical, non-virtualized machine; Although running on a virtual machine (as opposed to running on a host electronic device) is not known as running on a virtual machine (as opposed to running on a host electronic device), some systems do Provides para-virtualization that makes it possible to become aware of the existence of virtualization. Each of the virtual machines 1640 may be associated with other virtual machines 1640 of the virtual machine(s) 1640 in time, whether by hardware dedicated to that virtual machine 1640 and/or by that virtual machine 1640. Although the time slice of the shared hardware 1630, the portion of the hardware 1630 that runs the virtual machine 1640 forms a separate virtual network element(s) (VNE).

Hypervisor 1650 may present virtual machine 1640 with a virtual operating platform that looks like networking hardware, and virtual machine 1640 has control communication and configuration module(s) and configuration module(s). This virtualization of hardware, which may be used to implement functions such as forwarding tables, is sometimes referred to as network functions virtualization (NFV). Therefore, NFV is used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage that can be located in data centers and customer premises equipment (CPE). obtain. Different embodiments of instances or virtual applications 1620 may be implemented on one or more of virtual machine(s) 1640, and the implementation may be performed differently.

In some embodiments, a carrier comprising the computer program product described above is provided. The carrier is one of an electronic signal, an optical signal, a wireless signal, or a computer readable storage medium (eg, a non-transitory computer readable medium such as memory).

Some embodiments are implemented as a non-transitory software product stored on a machine-readable medium (also referred to as a computer-readable medium, processor-readable medium, or computer-usable medium having computer-readable program code embodied in the medium). can be expressed. Machine-readable media can be magnetic, including diskettes, compact disk read-only memory (CD-ROM), digital versatile disk read-only memory (DVD-ROM) memory devices (volatile or non-volatile), or similar storage mechanisms. It can be any suitable tangible medium, including optical or electrical storage media. The machine-readable medium carries various sets of instructions, code sequences, configuration information, or other data that, when executed, cause a processor to perform steps in a method according to one or more of the described embodiments. It may contain. Those skilled in the art will appreciate that other instructions and operations necessary to implement the described embodiments may also be stored on machine-readable media. Software running from a machine-readable medium may interface with the circuitry to perform the tasks described.

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

Claims (32)

A method performed by a wireless device, the method 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, a first field of the plurality of fields being , is used to indicate the number of fields for indicating at least one set of power control parameters in the last octet of the received MAC CE, and the at least one set of power control parameters is used to indicate the path loss estimation. relating to a reference signal used for
- sending a transmission to a network node based at least on a set of power control parameters associated with said 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 the length of the MAC CE and the first field. Method described. 3. The method of claim 2, wherein the length of the MAC CE is given by an L field or determined by a Logical Channel ID (LCID). The method according to 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 claims 1 to 4, wherein the first field indicates a number of one field or two fields to indicate at least one set of power control parameters in the last octet of the MAC CE. The method described in any one of the above. 6. A method according to any preceding claim, wherein the received MAC CE further comprises a third field. 7. The third field indicates to the wireless device whether a mapping between a set of power control parameters and the reference signal is updated, added, or deleted. the method of. 8. The method of claim 6 or 7, wherein the third field instructs the wireless device to delete all previous mappings between a set of power control parameters and the reference signal. 7. The method of claim 6, wherein the third field instructs the wireless device to deactivate or activate path loss estimation for uplink transmissions based on the reference signal. 7. The method of claim 6, wherein the third field instructs the wireless device how to interpret the received MAC CE. Any of claims 6 to 10, wherein the third field includes a first code point instructing the wireless device to deactivate path loss estimation for uplink transmissions based on the reference signal. The method described in paragraph 1. The third field instructs the wireless device to activate path loss estimation for uplink transmissions based on the reference signal, but includes a mapping between a set of power control parameters and the reference signal. 12. A method according to any one of claims 6 to 11, comprising a second code point that is unchanged. the third field causing the wireless device to activate path loss estimation for uplink transmissions based on the reference signal; and adding a set of power control parameters to be mapped to the reference signal. 13. A method according to any one of claims 6 to 12, comprising a third code point instructing to perform. the third field is configured to cause the wireless device to activate path loss estimation for uplink transmissions based on the reference signal; and to configure a set of power control parameters to be mapped to the reference signal. 14. A method according to any one of claims 6 to 13, including a fourth code point for instructing to replace with another set of . 15. A wireless device comprising a communication interface and a processing circuit connected to the communication interface and configured to implement the method according to any one of claims 1 to 14. A method implemented by a network node for power control, the method comprising:
- sending a media access control (MAC) control element (CE) to a wireless device, wherein the MAC CE includes a plurality of octets, each of the plurality of octets includes a plurality of fields, and the plurality of fields a first field of the MAC CE is used to indicate the number of fields for indicating at least one set of power control parameters in the last octet of the MAC CE; the set is related to reference signals used for path loss estimation;
- receiving a transmission based on at least a set of power control parameters associated with the reference signal. 17. The method of claim 16, wherein the total number of fields for indicating at least one set of power control parameters associated with the reference signal is given by the length of the MAC CE and the first field. 18. The method of claim 17, wherein the length of the MAC CE is given by an L field or determined by a Logical Channel ID (LCID). 19. The method according to any one of claims 16 to 18, wherein the MAC CE further comprises a second field for indicating the reference signal. 20. The method of claims 16 to 19, wherein the first field indicates a number of one field or two fields to indicate at least one set of power control parameters in the last octet of the MAC CE. The method described in any one of the above. 21. A method according to any one of claims 16 to 20, wherein the MAC CE further comprises a third field. 22. The third field indicates to the wireless device whether a mapping between a set of power control parameters and the reference signal is updated, added, or deleted. the method of. 23. The method of claim 22, wherein the third field instructs the wireless device to delete all previous mappings between a set of power control parameters and the reference signal. 23. The method of claim 22, wherein the third field instructs the wireless device to deactivate or activate path loss estimation for uplink transmissions based on the reference signal. 23. The method of claim 22, wherein the third field instructs the wireless device how to interpret the received MAC CE. 26. Any of claims 21-25, wherein the third field includes a first code point instructing the wireless device to deactivate path loss estimation for uplink transmissions based on the reference signal. The method described in paragraph 1. the third field instructs the wireless device to activate the path loss estimation for uplink transmissions based on the reference signal, wherein the third field comprises a mapping between a set of power control parameters and the reference signal; 27. A method according to any one of claims 21 to 26, comprising a second code point that does not change. The third field causes the wireless device to activate the path loss estimation for uplink transmissions based on the reference signal and adds a set of power control parameters to be mapped to the reference signal. 28. A method according to any one of claims 21 to 27, comprising a third code point instructing to perform the following. the third field instructs the wireless device to activate the path loss estimation for uplink transmissions based on the reference signal; and a set of power control parameters to be mapped to the reference signal. 29. A method according to any one of claims 21 to 28, comprising a fourth code point instructing to replace with another set of parameters. A network node comprising a communication interface and a processing circuit connected to the communication interface and configured to implement the method according to any one of claims 16 to 29. 16. A computer program product comprising computer readable program code which, when executed by a processor of a wireless device according to claim 15, causes said processor to perform a method according to any one of claims 1 to 14. 31. A computer program product comprising computer readable program code which, when executed by a processor of a network node according to claim 30, causes said processor to perform the method according to any one of claims 16 to 29.

Images