Determination of power control parameters in uplink channel repetition

Abstract

A wireless device may receive downlink control information (DCI) scheduling transmission of a transport block. In response to a sounding reference signal resource indicator (SRI) field being absent from the DCI, the wireless device may transmit a first repetition of the transport block with a first transmit power determined based on a first power control parameter set, and the wireless device may transmit a second repetition of the transport block with a second transmit power determined based on a second power control parameter set.

Description

Technical Field

[0001] Cross - reference to Related Applications This application claims the benefit of U.S. Provisional Patent Application No. 63 / 127,003, filed on December 17, 2020, which is hereby incorporated by reference in its entirety.

Summary of the Invention

Means for Solving the Problems

[0002] In this disclosure, various embodiments are presented as examples of how the disclosed technology can be implemented and / or how the disclosed technology can be practiced in environments and scenarios. It will be apparent to those skilled in the relevant technical fields that various changes in form and detail can be made without departing from the scope. Indeed, after reading the specification, methods of implementing alternative embodiments will be apparent to those skilled in the relevant technical fields. The present embodiments should not be limited by any of the exemplary embodiments. The embodiments of the present disclosure are described based on the accompanying drawings. Limitations, features, and / or elements from the disclosed exemplary embodiments can be combined to create further embodiments within the scope of the present disclosure. Figures emphasizing functions and advantages are shown for illustrative purposes only. The disclosed architecture is sufficiently flexible and configurable to be utilized in ways other than those shown. For example, any action listed in any flowchart can be rearranged or optionally used only in some embodiments. The present invention provides, for example, the following: (Item 1) It is a method, The wireless device receives one or more configuration parameters indicating a list of power control parameter sets, Receiving downlink control information (DCI) to schedule the transmission of transport blocks, Based on the absence of the Sounding Reference Signal Resource Indicator (SRI) field in the DCI, The first power control parameter set that occurs first in the above list, Selecting the second power control parameter set that occurs second in the aforementioned list, One or more first iterations of the transport block using a first transmission power determined based on the first power control parameter set, A method comprising transmitting one or more second repetitions of the transport block using a second transmission power determined based on the second set of power control parameters. (Item 2) It is a method, The wireless device receives downlink control information (DCI) that schedules the transmission of transport blocks, In response to the absence of a Sounding Reference Signal Resource Indicator (SRI) field in the DCI, One or more first iterations of the transport block using a first transmission power determined based on a first power control parameter set among multiple power control parameter sets, A method comprising transmitting one or more second repetitions of the transport block using a second transmission power determined based on a second power control parameter set among the plurality of power control parameter sets. (Item 3) It is a method, The wireless device receives downlink control information (DCI) that schedules the transmission of transport blocks, In response to the absence of a Sounding Reference Signal Resource Indicator (SRI) field in the DCI, A first iteration of the transport block using a first transmission power determined based on a first power control parameter set, A method comprising transmitting a second iteration of the transport block using a second transmission power determined based on a second power control parameter set. (Item 4) The method according to any one of items 1 to 3, wherein the SRI field is a first SRI field and a second SRI field that are not present in the DCI. (Item 5) The method according to any one of items 2 to 4, further comprising receiving one or more configuration parameters indicating a list of the plurality of power control parameter sets by the wireless device. (Item 6) The method according to any one of items 2 to 5, wherein the first power control parameter set occurs first on the list of the plurality of power control parameter sets, and the second power control parameter set occurs second on the list of the plurality of power control parameter sets. (Item 7) The method according to any one of items 1 to 6, wherein each power control parameter set in the list of power control parameter sets indicates the respective target received power value and the respective path loss compensation coefficient value. (Item 8) The method according to item 3, wherein the first iteration is one or more first iterations, and the second iteration is one or more second iterations. (Item 9) The first power control parameter set includes one or more first transmission power parameters, The method according to any one of items 1 to 8, wherein the second power control parameter set comprises one or more second transmission power parameters. (Item 10) The one or more first transmission power parameters are The first target received power value, The first path loss compensation coefficient value is shown below. The one or more second transmission power parameters are The first target received power value, The method according to any one of items 1 to 9, which indicates the first path loss compensation coefficient value. (Item 11) The first transmission power is The first target received power value and, The method according to any one of items 1 to 10, determined based on the first path loss compensation coefficient value. (Item 12) The second transmission power is The second target received power value and, The method according to any one of items 1 to 11, determined based on the second path loss compensation coefficient value. (Item 13) The one or more of the above configuration parameters are The first Sounding Reference Signal (SRS) resource set, The method described in any one of items 1 to 12, which indicates a second SRS resource set. (Item 14) The number of SRS resources in the first SRS resource set is equal to 1, and The method described in any one of items 1 to 13, wherein the number of SRS resources in the second SRS resource set is equal to 1. (Item 15) Based on the fact that the number of SRS resources in the first SRS resource set is equal to 1, the first SRI field does not exist in the DCI, The method according to any one of items 1 to 14, wherein the second SRI field does not exist in the DCI, based on the number of SRS resources in the second SRS resource set being equal to 1. (Item 16) The one or more of the above configuration parameters are The SRS usage parameters for the first SRS resource set described above, The method described in any one of items 1 to 15, which shows the SRS usage parameters for the second SRS resource set described above. (Item 17) The SRS usage parameters for the first SRS resource are set in the codebook, and the SRS usage parameters for the second SRS resource are set in the codebook, or The method according to any one of items 1 to 16, wherein the SRS usage parameter for the first SRS resource is set to a non-codebook, and the SRS usage parameter for the second SRS resource is set to a non-codebook. (Item 18) The method according to any one of items 1 to 17, wherein the DCI includes a time-domain resource alignment (TDRA) field indicating the number of repetitions of the transport block. (Item 19) The aforementioned transmission is The one or more first repetitions of the transport block occur in one or more first transmission opportunities. The method according to any one of items 1 to 18, wherein the one or more second repetitions of the transport block are in one or more second transmission opportunities. (Item 20) The above selection means that one or more of the configuration parameters are The aforementioned first SRS resource set, The method described in any one of items 1 to 19, based on the aforementioned second SRS resource set. (Item 21) The method according to any one of items 1 to 20, wherein the one or more configuration parameters include a path loss reference signal update parameter that enables an activation command and updates a path loss reference signal mapped to the list of power control parameter sets. (Item 22) The selection described herein is based on the fact that one or more of the configuration parameters include the path loss reference signal update parameters, as described in any one of items 1 to 21. (Item 23) The method according to any one of items 1 to 22, wherein the list of power control parameter sets is a list of target power path loss compensation sets. (Item 24) The method according to any one of items 1 to 23, wherein the DCI includes an open-loop power control (OLPC) parameter set index field having a first value. (Item 25) The above first value is, 0, or A method described in any one of items 1 through 24, equal to 00. (Item 26) A wireless device, One or more processors, A wireless device comprising: a memory that stores instructions causing the wireless device to perform the method described in any one of items 1 to 25 when executed by the one or more processors. (Item 27) A non-temporary computer-readable medium that, when executed by one or more processors, includes instructions that cause one or more processors to perform the method described in any one of items 1 to 25. (Item 28) It is a method, The base station transmits one or more configuration parameters indicating a list of power control parameter sets to the wireless device, This involves transmitting downlink control information (DCI) to schedule the transmission of transport blocks, Based on the absence of the Sounding Reference Signal Resource Indicator (SRI) field in the DCI, The first power control parameter set that occurs first in the above list, Selecting the second power control parameter set that occurs second in the aforementioned list, From the aforementioned wireless device, Based on the first power control parameter set, one or more first repetitions of the transport block transmitted using the first transmission power, A method comprising receiving one or more second repetitions of the transport block transmitted using a second transmission power based on the second power control parameter set. (Item 29) It is a method, The base station transmits downlink control information (DCI) to wireless devices to schedule the transmission of transport blocks, Based on the absence of a Sounding Reference Signal Resource Indicator (SRI) field in the DCI, the wireless device... Based on a first power control parameter set among multiple power control parameter sets, one or more first iterations of the transport block transmitted using a first transmission power, A method comprising receiving one or more second repetitions of the transport block transmitted using a second transmission power based on a second power control parameter set among the plurality of power control parameter sets. (Item 30) It is a method, The base station transmits downlink control information (DCI) to wireless devices to schedule the transmission of transport blocks, In response to the absence of a Sounding Reference Signal Resource Indicator (SRI) field in the DCI, the wireless device... Based on a first power control parameter set, a first iteration of the transport block is transmitted using a first transmission power, A method comprising receiving a second repetition of the transport block transmitted using a second transmission power based on a second power control parameter set. (Item 31) The method according to any one of items 28 to 30, wherein the SRI field is a first SRI field and a second SRI field that are not present in the DCI. (Item 32) The method according to any one of items 29 to 31, further comprising transmitting one or more configuration parameters indicating a list of the plurality of power control parameter sets by the base station. (Item 33) The method according to any one of items 29 to 32, wherein the first power control parameter set occurs first on the list of the plurality of power control parameter sets, and the second power control parameter set occurs second on the list of the plurality of power control parameter sets. (Item 34) The method according to any one of items 28 to 33, wherein each power control parameter set in the list of power control parameter sets indicates the respective target received power value and the respective path loss compensation coefficient value. (Item 35) The method according to item 30, wherein the first repetition is one or more first repetitions, and the second repetition is one or more second repetitions. (Item 36) The first power control parameter set includes one or more first transmission power parameters, The method according to any one of items 28 to 35, wherein the second power control parameter set comprises one or more second transmission power parameters. (Item 37) The one or more first transmission power parameters are The first target received power value, The first path loss compensation coefficient value is shown below. The one or more second transmission power parameters are The first target received power value, The method described in any one of items 28 to 36, which indicates the first path loss compensation coefficient value. (Item 38) The first transmission power is The first target received power value and, The method according to any one of items 28 to 37, further based on the first path loss compensation coefficient value. (Item 39) The second transmission power is The second target received power value and, The method according to any one of items 28 to 38, further based on the second path loss compensation coefficient value described above. (Item 40) The one or more of the above configuration parameters are The first Sounding Reference Signal (SRS) resource set, The method described in any one of items 28-39, which indicates a second SRS resource set. (Item 41) The number of SRS resources in the first SRS resource set is equal to 1, and The method described in any one of items 28-40, wherein the number of SRS resources in the second SRS resource set is equal to 1. (Item 42) Based on the fact that the number of SRS resources in the first SRS resource set is equal to 1, the first SRI field does not exist in the DCI, The method according to any one of items 28 to 41, wherein the second SRI field does not exist in the DCI, based on the number of SRS resources in the second SRS resource set being equal to 1. (Item 43) The one or more of the above configuration parameters are The SRS usage parameters for the first SRS resource set described above, The method described in any one of items 28 to 42, which shows the SRS usage parameters for the second SRS resource set described above. (Item 44) The SRS usage parameters for the first SRS resource are set in the codebook, and the SRS usage parameters for the second SRS resource are set in the codebook, or The method according to any one of items 28 to 43, wherein the SRS usage parameter for the first SRS resource is set to a non-codebook, and the SRS usage parameter for the second SRS resource is set to a non-codebook. (Item 45) The method according to any one of items 28 to 44, wherein the DCI includes a time-domain resource alignment (TDRA) field indicating the number of repetitions of the transport block. (Item 46) Receiving the above means The one or more first repetitions of the transport block occur in one or more first transmission opportunities. The method according to any one of items 28 to 45, wherein the one or more second repetitions of the transport block are in one or more second transmission opportunities. (Item 47) The above selection means that one or more of the configuration parameters are The aforementioned first SRS resource set, The method described in any one of items 28-46, based on the aforementioned second SRS resource set. (Item 48) The method according to any one of items 28 to 47, wherein the one or more configuration parameters include a path loss reference signal update parameter that enables an activation command and updates a path loss reference signal mapped to the list of power control parameter sets. (Item 49) The selection described herein is based on the fact that one or more of the configuration parameters include the path loss reference signal update parameters, as described in any one of items 28 to 48. (Item 50) The method according to any one of items 28 to 49, wherein the list of power control parameter sets is a list of target power path loss compensation sets. (Item 51) The method according to any one of items 28 to 50, wherein the DCI includes an open-loop power control (OLPC) parameter set index field having a first value. (Item 52) The above first value is, 0, or A method described in any one of items 28-51, equal to 00. (Item 53) It is a base station, One or more processors, A base station comprising: a memory that stores instructions, when executed by one or more processors, causing the base station to perform the method described in any one of items 28 to 52; (Item 54) A non-temporary computer-readable medium that, when executed by one or more processors, includes instructions causing one or more processors to perform the method described in any one of items 28 to 52. (Item 55) It is a system, A base station comprising one or more first processors and a memory storing instructions, wherein when the instructions are executed by the one or more first processors, the base station is instructed to transmit downlink control information (DCI) that schedules the transmission of a transport block. A wireless device comprising, wherein the wireless device comprises one or more second processors and a memory storing instructions, and when the instructions are executed by the one or more second processors, the wireless device, The DCI is received, and In response to the absence of a Sounding Reference Signal Resource Indicator (SRI) field in the DCI, A first iteration of the transport block using a first transmission power determined based on a first power control parameter set, A system for transmitting a second iteration of the transport block using a second transmission power determined based on a second power control parameter set. (Item 56) It is a method, The wireless device receives downlink control information (DCI) that schedules the transmission of transport blocks, Based on the absence of the Sounding Reference Signal Resource Indicator (SRI) field in the DCI, The first closed-loop index is equal to 0, Select a second closed-loop index equal to 1, One or more first iterations of the transport block using a first transmission power determined based on the first closed-loop index, A method comprising transmitting one or more second repetitions of the transport block using a second transmission power determined based on the second closed-loop index. (Item 57) It is a method, The wireless device receives downlink control information (DCI) that schedules the transmission of transport blocks, Based on the absence of the Sounding Reference Signal Resource Indicator (SRI) field in the DCI, One or more first iterations of the transport block using a first transmission power determined based on a first closed-loop index, A method comprising transmitting one or more second repetitions of the transport block using a second transmission power determined based on a second closed-loop index. (Item 58) The method according to item 56 or 57, wherein the SRI field includes a first SRI field and a second SRI field that are not present in the DCI. (Item 59) The method according to item 57 or 58, further comprising selecting a first closed-loop index equal to 0 and a second closed-loop index equal to 1 based on the absence of the SRI field, wherein the transmission is in response to the selection. (Item 60) The method according to any one of items 56 to 59, further comprising receiving one or more configuration parameters indicating a list of power control parameter sets by the wireless device. (Item 61) The method according to any one of items 56 to 60, wherein the first power control parameter set occurs first on the list of the plurality of power control parameter sets, and the second power control parameter set occurs second on the list of the plurality of power control parameter sets. (Item 62) The method according to any one of items 56 to 61, wherein each power control parameter set in the list of power control parameter sets indicates the respective target received power value and the respective path loss compensation coefficient value. (Item 63) The first power control parameter set includes one or more first transmission power parameters, The method according to any one of items 56 to 62, wherein the second power control parameter set comprises one or more second transmission power parameters. (Item 64) The one or more first transmission power parameters are The first target received power value, The first path loss compensation coefficient value is shown below. The one or more second transmission power parameters are The first target received power value, The method according to any one of items 56 to 63, which indicates the first path loss compensation coefficient value. (Item 65) The first transmission power is The first target received power value, The method according to any one of items 56 to 64, determined based on a first path loss compensation coefficient value. (Item 66) The second transmission power is The second target received power value, The method according to any one of items 56 to 65, determined based on a second path loss compensation coefficient value. (Item 67) The one or more of the above configuration parameters are The first Sounding Reference Signal (SRS) resource set, The method described in any one of items 56-66, which indicates a second SRS resource set. (Item 68) The number of SRS resources in the first SRS resource set is equal to 1, and The method according to any one of items 56 to 67, wherein the number of SRS resources in the second SRS resource set is equal to 1. (Item 69) Based on the fact that the number of SRS resources in the first SRS resource set is equal to 1, the first SRI field does not exist in the DCI, The method according to any one of items 56 to 68, wherein the second SRI field does not exist in the DCI, based on the number of SRS resources in the second SRS resource set being equal to 1. (Item 70) The SRS usage parameters for the first SRS resource set described above, The method according to any one of items 56 to 69, further comprising receiving one or more configuration parameters indicating SRS usage parameters for the second SRS resource set. (Item 71) The SRS usage parameters for the first SRS resource are set in the codebook, and the SRS usage parameters for the second SRS resource are set in the codebook, or The method according to any one of items 56 to 70, wherein the SRS usage parameter for the first SRS resource is set to a non-codebook, and the SRS usage parameter for the second SRS resource is set to a non-codebook. (Item 72) The method according to any one of items 56 to 71, wherein the DCI includes a time-domain resource alignment (TDRA) field indicating the number of repetitions of the transport block. (Item 73) The aforementioned transmission is The one or more first repetitions of the transport block occur in one or more first transmission opportunities. The method according to any one of items 56 to 72, wherein the one or more second repetitions of the transport block are in one or more second transmission opportunities. (Item 74) The method according to any one of items 56 to 73, wherein the DCI includes an open-loop power control (OLPC) parameter set index field having a first value. (Item 75) The above first value is, 0, or A method described in any one of items 56-74, equal to 00. (Item 76) A wireless device, One or more processors, A wireless device comprising: a memory that stores instructions causing the wireless device to perform the method described in any one of items 56 to 75 when executed by one or more processors. (Item 77) A non-temporary computer-readable medium comprising instructions that, when executed by one or more processors, cause one or more processors to perform the method described in any one of items 56 to 75. (Item 78) It is a method, The base station transmits downlink control information (DCI) to wireless devices to schedule the transmission of transport blocks, Based on the absence of the Sounding Reference Signal Resource Indicator (SRI) field in the DCI, The first closed-loop index is equal to 0, Select a second closed-loop index equal to 1, From the aforementioned wireless device, One or more first iterations of the transport block using a first transmission power based on the first closed-loop index, A method comprising receiving one or more second repetitions of the transport block using a second transmission power based on the second closed-loop index. (Item 79) It is a method, The base station transmits downlink control information (DCI) to wireless devices to schedule the transmission of transport blocks, Based on the absence of a Sounding Reference Signal Resource Indicator (SRI) field in the DCI, the wireless device... One or more first iterations of the transport block using a first transmission power based on a first closed-loop index, A method comprising receiving one or more second repetitions of the transport block using a second transmission power based on a second closed-loop index. (Item 80) The method according to item 78 or 79, wherein the SRI field includes a first SRI field and a second SRI field that are not present in the DCI. (Item 81) The method according to item 79 or 80, further comprising selecting a first closed-loop index equal to 0 and a second closed-loop index equal to 1 based on the absence of the SRI field, wherein the transmission is in response to the decision. (Item 82) The method according to any one of items 78 to 81, further comprising receiving one or more configuration parameters indicating a list of power control parameter sets by the wireless device. (Item 83) The method according to any one of items 78 to 82, wherein the first power control parameter set occurs first on the list of the plurality of power control parameter sets, and the second power control parameter set occurs second on the list of the plurality of power control parameter sets. (Item 84) The method according to any one of items 78 to 83, wherein each power control parameter set in the list of power control parameter sets indicates the respective target received power value and the respective path loss compensation coefficient value. (Item 85) The first power control parameter set includes one or more first transmission power parameters, The method according to any one of items 78 to 84, wherein the second power control parameter set comprises one or more second transmission power parameters. (Item 86) The one or more first transmission power parameters are The first target received power value, The first path loss compensation coefficient value is shown below. The one or more second transmission power parameters are The first target received power value, The method according to any one of items 78 to 85, which indicates the first path loss compensation coefficient value. (Item 87) The first transmission power is The first target received power value, The method according to any one of items 78 to 86, further based on a first path loss compensation coefficient value. (Item 88) The second transmission power is The second target received power value, The method according to any one of items 78 to 87, further based on a second path loss compensation coefficient value. (Item 89) The one or more of the above configuration parameters are The first Sounding Reference Signal (SRS) resource set, The method described in any one of items 78-88, which indicates a second SRS resource set. (Item 90) The number of SRS resources in the first SRS resource set is equal to 1, and The method described in any one of items 78-89, wherein the number of SRS resources in the second SRS resource set is equal to 1. (Item 91) Based on the fact that the number of SRS resources in the first SRS resource set is equal to 1, the first SRI field does not exist in the DCI, The method according to any one of items 78 to 90, wherein the second SRI field does not exist in the DCI, based on the number of SRS resources in the second SRS resource set being equal to 1. (Item 92) The SRS usage parameters for the first SRS resource set described above, The method according to any one of items 78 to 91, further comprising transmitting one or more configuration parameters indicating SRS usage parameters for the second SRS resource set. (Item 93) The SRS usage parameters for the first SRS resource are set in the codebook, and the SRS usage parameters for the second SRS resource are set in the codebook, or The method according to any one of items 78 to 92, wherein the SRS usage parameter for the first SRS resource is set to a non-codebook, and the SRS usage parameter for the second SRS resource is set to a non-codebook. (Item 94) The method according to any one of items 78 to 93, wherein the DCI includes a time-domain resource alignment (TDRA) field indicating the number of repetitions of the transport block. (Item 95) Receiving the above means The one or more first repetitions of the transport block occur in one or more first transmission opportunities. The method according to any one of items 78 to 94, wherein the one or more second repetitions of the transport block are in one or more second transmission opportunities. (Item 96) The method according to any one of items 78 to 95, wherein the DCI includes an open-loop power control (OLPC) parameter set index field having a first value. (Item 97) The above first value is, 0, or A method described in any one of items 78-96, equal to 00. (Item 98) It is a base station, One or more processors, A base station comprising: a memory that stores instructions, when executed by one or more processors, causing the base station to perform the method described in any one of items 78 to 97. (Item 99) A non-temporary computer-readable medium that, when executed by one or more processors, includes instructions causing one or more processors to perform the method described in any one of items 78 to 97. (Item 100) It is a system, A base station comprising one or more first processors and memory storing instructions, wherein when an instruction is executed by the one or more first processors, the base station receives A base station transmits downlink control information (DCI) to schedule the transmission of transport blocks, A wireless device comprising one or more second processors and a memory storing instructions, wherein when an instruction is executed by the one or more second processors, the wireless device provides The DCI is received, and Based on the absence of the Sounding Reference Signal Resource Indicator (SRI) field in the DCI, One or more first iterations of the transport block using a first transmission power determined based on a first closed-loop index, A system for transmitting one or more second repetitions of the transport block using a second transmission power determined based on a second closed-loop index. (Item 101) It is a method, By wireless devices, At least two Sounding Reference Signal (SRS) resource sets, Receiving one or more configuration parameters that indicate multiple power control parameter sets, Receiving downlink control information (DCI) that schedules the transmission of a transport block, wherein the DCI includes an open-loop power control (OLPC) parameter set index field. Based on the fact that one or more of the configuration parameters indicate the at least two SRS resource sets, and based on the value of the OLPC parameter set index field, A first power control parameter set among the plurality of power control parameter sets, Selecting a second power control parameter set from the aforementioned plurality of power control parameter sets, One or more first iterations of the transport block using a first transmission power determined based on the first power control parameter set, A method comprising transmitting one or more second repetitions of the transport block using a second transmission power determined based on the second set of power control parameters. (Item 102) It is a method, By wireless devices, Schedule the transmission of the transport block, Receiving downlink control information (DCI), including the open-loop power control (OLPC) field, Based on the value of the OLPC field, A first iteration of the transport block using a first transmission power determined based on a first power control parameter set, A method comprising transmitting a second iteration of the transport block using a second transmission power determined based on a second power control parameter set. (Item 103) By wireless devices, At least two Sounding Reference Signal (SRS) resource sets, The method according to item 102, further comprising receiving one or more configuration parameters that indicate a set of multiple power control parameters. (Item 104) The method according to item 102 or 103, wherein the OLPC field is an OLPC parameter set index field. (Item 105) Based on the value of the OLPC field, The first power control parameter set among the plurality of power control parameter sets, The method according to any one of items 102 to 104, further comprising selecting the second power control parameter set from the plurality of power control parameter sets. (Item 106) The method according to any one of items 102 to 105, wherein the selection is further based on one or more configuration parameters that represent the at least two SRS resource sets. (Item 107) The method according to any one of items 102 to 106, wherein the first repetition is one or more first repetitions, and the second repetition is one or more second repetitions. (Item 108) The one or more configuration parameters are applied to each of the at least two SRS resource sets. Codebook or The method described in any one of items 101-107, which indicates the usage parameters set for each non-codebook. (Item 109) The aforementioned DCI, The first SRS Resource Indicator (SRI) field, The method described in any one of items 101 to 108, further including a second SRI field. (Item 110) The first SRI field is mapped to the first power control parameter set index of the first power control parameter set, The method according to any one of items 101 to 109, wherein the second SRI field is mapped to the second power control parameter set index of the second power control parameter set. (Item 111) The method described in any one of items 101 to 110, wherein the value of the OLPC parameter set index field is equal to 1. (Item 112) The method according to any one of items 101 to 111, wherein the SRI field is not present in the DCI. (Item 113) The method according to any one of items 101 to 112, wherein the selection is further based on the absence of the SRI field in the DCI. (Item 114) The method according to any one of items 101 to 113, wherein the value of the OLPC parameter set index field is equal to "1" or "01". (Item 115) Determining the first transmission power is based on the first / start / initial value that occurs first in the first power control parameter set, and The method according to any one of items 101 to 114, wherein the second transmission power is determined based on the first / start / initial value that occurs first in the second power control parameter set. (Item 116) The method according to any one of items 101 to 115, wherein the value of the OLPC parameter set index field is equal to "10" or "11". (Item 117) Determining the first transmission power is based on the second / second start / initial value that occurs second in the first power control parameter set, The method according to any one of items 101 to 116, wherein the second transmission power is determined based on the second initial value of the second / second start that occurs second in the second power control parameter set. (Item 118) A wireless device, One or more processors, A base station comprising: a memory that stores instructions that cause the base station to perform the method described in any one of items 101 to 117 when executed by one or more processors. (Item 119) A non-temporary computer-readable medium that, when executed by one or more processors, includes instructions causing one or more processors to perform the method described in any one of items 101 to 117. (Item 120) It is a method, The base station communicates to the wireless device, At least two Sounding Reference Signal (SRS) resource sets, Transmitting one or more configuration parameters that represent multiple power control parameter sets, Transmitting downlink control information (DCI) that schedules the transmission of a transport block, wherein the DCI includes an open-loop power control (OLPC) parameter set index field. Based on the fact that one or more of the configuration parameters indicate the at least two SRS resource sets, and based on the value of the OLPC parameter set index field, A first power control parameter set among the plurality of power control parameter sets, Selecting a second power control parameter set from the aforementioned plurality of power control parameter sets, From the aforementioned wireless device, One or more first iterations of the transport block using a first transmission power based on the first power control parameter set, A method comprising receiving one or more second repetitions of the transport block using a second transmission power based on the second power control parameter set. (Item 121) It is a method, From the base station to the wireless device, Schedule the transmission of the transport block, Transmitting downlink control information (DCI), including the open-loop power control (OLPC) field, Based on the value of the OLPC field, the wireless device, A first iteration of the transport block using a first transmission power based on a first power control parameter set, A method comprising receiving a second iteration of the transport block using a second transmission power based on a second power control parameter set. (Item 122) By wireless devices, At least two Sounding Reference Signal (SRS) resource sets, The method according to item 121, further comprising receiving one or more configuration parameters that indicate a set of multiple power control parameters. (Item 123) The method according to item 121 or 122, wherein the OLPC field is an OLPC parameter set index field. (Item 124) Based on the value of the OLPC field, The first power control parameter set among the plurality of power control parameter sets, The method according to any one of items 121 to 123, further comprising selecting the second power control parameter set from the plurality of power control parameter sets. (Item 125) The method according to any one of items 121 to 124, wherein the selection is further based on one or more configuration parameters that represent the at least two SRS resource sets. (Item 126) The method according to any one of items 121 to 125, wherein the first repetition is one or more first repetitions, and the second repetition is one or more second repetitions. (Item 127) The one or more configuration parameters are applied to each of the at least two SRS resource sets. Codebook or The method described in any one of items 120-126, which indicates the usage parameters set for each non-codebook. (Item 128) The aforementioned DCI, The first SRS Resource Indicator (SRI) field, The method described in any one of items 120 to 127, further including a second SRI field. (Item 129) The first SRI field is mapped to the first power control parameter set index of the first power control parameter set, The method according to any one of items 120 to 128, wherein the second SRI field is mapped to the second power control parameter set index of the second power control parameter set. (Item 130) The method described in any one of items 120 to 129, wherein the value of the OLPC parameter set index field is equal to 1. (Item 131) The method according to any one of items 120 to 130, wherein the SRI field is not present in the DCI. (Item 132) The method according to any one of items 120 to 131, wherein the selection is further based on the absence of the SRI field in the DCI. (Item 133) The method according to any one of items 120 to 132, wherein the value of the OLPC parameter set index field is equal to "1" or "01". (Item 134) Determining the first transmission power is based on the first / start / initial value that occurs first in the first power control parameter set. The method according to any one of items 120 to 133, wherein the second transmission power is determined based on the first / start / initial value that occurs first in the second power control parameter set. (Item 135) The method according to any one of items 120 to 134, wherein the value of the OLPC parameter set index field is equal to "10" or "11". (Item 136) Determining the first transmission power is based on the second / second start / initial value that occurs second in the first power control parameter set, The method according to any one of items 120 to 135, wherein the second transmission power is determined based on the second initial value of the second / second start that occurs second in the second power control parameter set. (Item 137) It is a base station, One or more processors, A base station comprising: a memory that stores instructions, when executed by one or more processors, causing the base station to perform the method described in any one of items 120 to 136. (Item 138) A non-temporary computer-readable medium that, when executed by one or more processors, includes instructions causing one or more processors to perform the method described in any one of items 120 to 136. (Item 139) It is a system, A base station comprising one or more first processors and memory storing instructions, wherein when an instruction is executed by the one or more first processors, the base station receives Schedule the transmission of the transport block, A base station that transmits downlink control information (DCI), including an open-loop power control (OLPC) field, A wireless device comprising, wherein the wireless device comprises one or more second processors and a memory storing instructions, and when the instructions are executed by the one or more second processors, the wireless device, The DCI is received, and Based on the value of the OLPC field, A first iteration of the transport block using a first transmission power determined based on a first power control parameter set, A system for transmitting a second iteration of the transport block using a second transmission power determined based on a second power control parameter set.

Brief Description of the Drawings

[0003] Some examples of various embodiments of the present disclosure are described herein with reference to the drawings.

[0004] [Figure 1A] An exemplary mobile communication network in which embodiments of the present disclosure can be implemented is shown. [Figure 1B] This document illustrates an exemplary mobile communications network in which embodiments of the present disclosure may be implemented. [Figure 2A] The new radio (NR) user plane and control plane protocol stacks are shown, respectively. [Figure 2B] The new radio (NR) user plane and control plane protocol stacks are shown, respectively. [Figure 3] Figure 2A shows one example of services provided between the protocol layers of the NR user plane protocol stack. [Figure 4A] Figure 2A shows an exemplary downlink data flow through the NR user plane protocol stack. [Figure 4B] This shows an exemplary format for the MAC subheader in a MAC PDU. [Figure 5A] This shows the mapping between the logical channels, transport channels, and physical channels for downlink and uplink, respectively. [Figure 5B] This shows the mapping between the logical channels, transport channels, and physical channels for downlink and uplink, respectively. [Figure 6] This is an illustrative diagram showing the RRC state transition of a UE. [Figure 7] This shows an example configuration of an NR frame with grouped OFDM symbols. [Figure 8] This shows an exemplary configuration of slots in the time and frequency domains of the NR carrier. [Figure 9] This example demonstrates one instance of bandwidth adaptation using three configured BWPs for an NR carrier. [Figure 10A] This shows three carrier aggregation configurations, each with two component carriers. [Figure 10B] This shows one example of how aggregation cells can be composed of one or more PUCCH groups. [Figure 11A] An embodiment of the SS / PBCH block structure and position is shown. [Figure 11B]An example of CSI-RS mapped to the time and frequency domains is shown. [Figure 12A] Three examples of downlink and uplink beam management procedures are shown below. [Figure 12B] Three examples of downlink and uplink beam management procedures are shown below. [Figure 13A] The following describes a 4-step conflict-based random access procedure, a 2-step non-conflict random access procedure, and another 2-step random access procedure. [Figure 13B] The following describes a 4-step conflict-based random access procedure, a 2-step non-conflict random access procedure, and another 2-step random access procedure. [Figure 13C] The following describes a 4-step conflict-based random access procedure, a 2-step non-conflict random access procedure, and another 2-step random access procedure. [Figure 14A] This shows one example of a CORESET configuration for the bandwidth portion. [Figure 14B] This document presents one example of CCE-REG mapping for DCI transmission during CORESET and PDCCH processing. [Figure 15] This shows one embodiment of a wireless device that communicates with a base station. [Figure 16A] An exemplary structure for uplink and downlink transmission is shown. [Figure 16B] An exemplary structure for uplink and downlink transmission is shown. [Figure 16C] An exemplary structure for uplink and downlink transmission is shown. [Figure 16D] An exemplary structure for uplink and downlink transmission is shown. [Figure 17] An example of an repeated uplink channel according to one embodiment of the exemplary embodiments of this disclosure is shown. [Figure 18] An example of an repeated uplink channel according to one embodiment of the exemplary embodiments of this disclosure is shown. [Figure 19]An example of an repeated uplink channel according to one embodiment of the exemplary embodiments of this disclosure is shown. [Figure 20] An uplink repetition scheme according to one exemplary embodiment of the present disclosure is shown. [Figure 21] A flowchart of power control in an uplink channel iteration according to one exemplary embodiment of the present disclosure is shown. [Figure 22] A flowchart of power control in an uplink channel iteration according to one exemplary embodiment of the present disclosure is shown. [Figure 23] A flowchart of power control in an uplink channel iteration according to one exemplary embodiment of the present disclosure is shown. [Figure 24] A flowchart of power control in an uplink channel iteration according to one exemplary embodiment of the present disclosure is shown. [Modes for carrying out the invention]

[0005] The embodiments may be configured to operate as needed. The disclosed mechanisms may be executed, for example, in a wireless device, base station, wireless environment, network, or a combination thereof, when certain criteria are met. Exceptional criteria may be based, at least in part, on wireless device or network node configuration, traffic load, initial system setup, packet size, traffic characteristics, or a combination thereof. Various exemplary embodiments may be applied when one or more criteria are met. Therefore, it may be possible to implement exemplary embodiments that selectively implement the disclosed protocols.

[0006] A base station may communicate with a mixture of radio devices. Radio devices and / or base stations may support multiple technologies and / or multiple releases of the same technology. Radio devices may have certain capabilities depending on the category and / or capabilities of the radio device. Where this disclosure refers to a base station communicating with multiple radio devices, this disclosure may refer to a subset of all radio devices in a coverage area. This disclosure may refer, for example, to multiple radio devices of a given LTE or 5G release that have a given capability and are located in a given sector of a base station. Multiple radio devices in this disclosure may refer to a subset of all radio devices in a coverage area that are selected and / or operate according to the disclosed method, etc. Multiple base stations or multiple radio devices may exist in a coverage area that cannot comply with the disclosed method. For example, those radio devices or base stations may operate based on an older release of LTE or 5G technology.

[0007] In this specification, “a” and “an,” and similar phrases, are interpreted as “at least one” and “one or more.” Similarly, any term ending in the suffix “(s)” should be interpreted as “at least one” and “one or more.” In this specification, the term “may” should be interpreted as “for example, it may be.” In other words, the term “may” indicates that the phrase following the term “may” is one embodiment of several preferred possibilities, which may or may not be used by one or more of the various embodiments. Where used herein, the terms “comprises” and “consists of” enumerate one or more components of the element being described. The term “comprises” is interchangeable with “includes” and does not exclude unlisted components included in the element being described. In contrast, “consists of” provides a complete enumeration of one or more components of the element being described. Where used herein, the term “based on” should be interpreted as “at least partially based” rather than, for example, “based only on.” As used herein, the term "and / or" represents any possible combination of the enumerated elements. For example, "A, B, and / or C" could mean A, B, C, A and B, A and C, B and C, or A, B, and C.

[0008] If A and B are a set and all elements of A are also elements of B, then A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B = {cell 1, cell 2} are {cell 1}, {cell 2}, and {cell 1, cell 2}. The phrase "based on" (or equivalently "at least based on") indicates that the phrase following the term "based on" is one example of a number of preferred possibilities in which one or more different embodiments may or may not be used. The phrase "in response to" (or equivalently "at least in response to") indicates that the phrase following the phrase "in response to" is one example of a number of preferred possibilities in which one or more different embodiments may or may not be used. The phrase "according to" (or equivalently "at least in response to") indicates that the phrase following the phrase "according to" is one example of a number of preferred possibilities in which one or more different embodiments may or may not be used. The phrase “use / utilize” (or equivalently “at least use / utilize”) indicates that the phrase following “use / utilize” is one example of a number of preferred possibilities in which one or more of the various embodiments may or may not be used.

[0009] The term "configured" can relate to the capacity of a device, regardless of whether the device is operational or non-operating. "Configured" can refer to specific settings of a device that affect its operational characteristics, regardless of whether the device is operational or non-operating. In other words, hardware, software, firmware, registers, memory values, etc., can be "configured" within a device, regardless of whether the device is operational or non-operating, in order for the device to provide certain characteristics. Terms such as "control messages generated in a device" can mean that control messages, regardless of whether the device is operational or non-operating, have parameters that can be used to configure certain characteristics in the device or to implement certain actions in the device.

[0010] In this disclosure, a parameter (or equivalently referred to as a field, or information element: IE) may contain one or more information objects, and an information object may contain one or more other objects. For example, if parameter (IE)N contains parameter (IE)M, parameter (IE)M contains parameter (IE)K, and parameter (IE)K contains parameter (information element)J, then for example, N contains K and N contains J. In exemplary embodiments, if one or more messages contain multiple parameters, it means that one of the multiple parameters is contained in at least one of the one or more messages, but not in each of the one or more messages.

[0011] Many of the features presented are described as optional by the use of “may” or parentheses. For the sake of brevity and readability, this disclosure does not expressly describe all possible changes that may result from selecting from a set of optional features. This disclosure should be construed as expressly disclosing all such changes. For example, a system described as having three optional features can be embodied in seven ways: by just one of the three possible features, by any two of the three features, or by three of the three features.

[0012] Many of the elements described in the disclosed embodiments can be implemented as modules, where a module is defined as an element that performs a defined function and has a defined interface to other elements. Modules described in this disclosure may be implemented in hardware, software combined with hardware, firmware, wetware (e.g., hardware with biological elements), or a combination thereof, and they may be behaviorally equivalent. For example, a module may be implemented in a hardware machine (such as C, C++, Fortran, Java®, Basic, Matlab®) or in software routines written in a computer language configured to run in Simulink, Stateflow, GNU Octave, or LabVIEWMathScript. It may also be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital, and / or quantum hardware. Examples of programmable hardware include computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and complex-programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors are programmed using languages ​​such as assembly, C, and C++. FPGAs, ASICs, and CPLDs are often programmed using hardware description languages ​​(HDLs) such as VHSIC (VHDL) or Verilog, which configure connections between internal hardware modules with limited functionality in the programmable device. These techniques are often used in combination to achieve the desired results for the functional modules.

[0013] Figure 1A shows one embodiment of a mobile communications network 100 in which embodiments of the present disclosure may be implemented. The mobile communications network 100 may be, for example, a public land mobile network (PLMN) operated by a network operator. As shown in Figure 1A, the mobile communications network 100 includes a core network (CN) 102, a radio access network (RAN) 104, and radio devices 106.

[0014] CN102 may provide the wireless device 106 with an interface to one or more data networks (DNs), such as a public DN (e.g., the Internet), a private DN, and / or an intra-operator DN. As part of its interface function, CN102 may set up an end-to-end connection between the wireless device 106 and one or more DNs, authenticate the wireless device 106, and provide charging capabilities.

[0015] RAN104 can connect CN102 to radio device 106 via wireless communication over the air interface. As part of the wireless communication, RAN104 can provide scheduling, radio resource management, and retransmission protocols. The communication direction from RAN104 to radio device 106 over the air interface is known as the downlink, and the communication direction from radio device 106 to RAN104 over the air interface is known as the uplink. Downlink transmission can be isolated from uplink transmission using frequency division duplication (FDD), time division duplication (TDD), and / or some combination of the two duplication techniques.

[0016] The term "wireless device" may be used throughout this disclosure to mean and include any mobile or fixed (non-portable) device that requires or is capable of wireless communication. For example, a wireless device could be a telephone, smartphone, tablet, computer, laptop, sensor, meter, wearable device, Internet of Things (IoT) device, vehicle roadside unit (RSU), relay node, automobile, and / or any combination thereof. The term "wireless device" also includes other terms, including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handset, wireless transceiver unit (WTRU), and / or wireless communication device.

[0017] RAN104 may include one or more base stations (not shown). The term base station may be used throughout this disclosure to include and encompass Node B (associated with UMTS and / or 3G standards), evolved Node B (associated with eNB, E-UTRA and / or 4G standards), remote radio head (RRH), baseband processing unit coupled to one or more RRHs, repeater node or relay node used to extend the coverage area of ​​a donor node, next-generation evolved Node B (ng-eNB), generation Node B (associated with gNB, NR and / or 5G standards), access point (AP, associated with e.g., WiFi or other suitable wireless communication standards), and / or any combination thereof. A base station may include at least one gNB central unit (gNB-CU) and at least one gNB distributed unit (gNB-DU).

[0018] A base station included in RAN104 may include one or more sets of antennas for communicating with the radio device 106 over an air interface. For example, one or more base stations may include three sets of antennas, each for controlling three cells (or sectors). The size of a cell may be determined by the range over which a receiver (e.g., a base station receiver) can successfully receive transmissions from a transmitter (e.g., a radio device transmitter) operating in the cell. Together, the base station cells may provide radio coverage to the radio device 106 over a wide geographical area to support radio device mobility.

[0019] In addition to the three sector sites, other implementations of base stations are possible. For example, one or more base stations in RAN104 may be implemented as sector sites with more or fewer than three sectors. One or more base stations in RAN104 may be implemented as access points, as baseband processing units coupled to multiple remote radio heads (RRHs), and / or as repeater or relay nodes used to extend the coverage area of ​​a donor node. Baseband processing units coupled to RRHs may be part of a centralized or cloud RAN architecture, and the baseband processing units may be centralized or virtualized within a pool of baseband processing units. Repeater nodes may amplify and rebroadcast radio signals received from donor nodes. Relay nodes may perform the same / similar functions as repeater nodes, but may decode radio signals received from donor nodes to remove noise before amplifying and rebroadcasting the radio signals.

[0020] RAN104 can be deployed as a homogeneous network of macrocell base stations having similar antenna patterns and similar high-level transmission power. RAN104 can also be deployed as a heterogeneous network. In a heterogeneous network, small cell base stations can be used to provide smaller coverage areas, for example, overlapping with the relatively large coverage areas provided by macrocell base stations. Smaller coverage areas can be provided in areas with high data traffic (or so-called hotspots) or in areas with weak macrocell coverage. Examples of small cell base stations, in order of decreasing coverage area, include microcell base stations, picocell base stations, and femtocell base stations or home base stations.

[0021] The Third Generation Partnership Project (3GPP®) was formed in 1998 to provide global standardization for mobile communication network specifications, similar to mobile communication network 100 in Figure 1A. To date, 3GPP® has produced specifications for three generations of mobile networks: third-generation (3G) networks known as Universal Mobile Communications Systems (UMTS), fourth-generation (4G) networks known as Long-Term Evolution (LTE), and fifth-generation (5G) networks known as 5G Systems (5GS). Embodiments of this disclosure are described in reference to the RAN of a 3GPP® 5G network, referred to as Next Generation RAN (NG-RAN). Embodiments may be applicable to RANs of other mobile communication networks, such as RAN 104 in Figure 1A, the RANs of earlier 3G and 4G networks, and future networks that have not yet been specified (e.g., 3GPP® 6G networks). NG-RAN can be supplied to implement 5G radio access technology, also known as New Radio (NR), and to implement other radio access technologies, including 4G radio access technology or non-3GPP® radio access technology.

[0022] Figure 1B shows a mobile communications network 150 of another embodiment in which embodiments of the present disclosure may be implemented. The mobile communications network 150 may be, for example, a PLMN operated by a network operator. As shown in Figure 1B, the mobile communications network 150 includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UE156A and UE156B (collectively referred to as UE156). These components may be implemented and operated in the same or similar manner as the corresponding components described with respect to Figure 1A.

[0023] 5G-CN152 provides UE156 with an interface to one or more DNs, such as public DNs (e.g., the Internet), private DNs, and / or intra-operator DNs. As part of its interface functionality, 5G-CN152 may set up end-to-end connectivity between UE156 and one or more DNs, authenticate UE156, and provide charging capabilities. Compared to the CNs of 3GPP® 4G networks, the basis of 5G-CN152 may be a service-based architecture. This means that the architecture of the nodes constituting 5G-CN152 may be defined as network functions that provide services through interfaces to other network functions. The network functions of 5G-CN152 may be implemented in several ways, such as network elements on dedicated or shared hardware, software instances running on dedicated or shared hardware, or virtualized functions instantiated on a platform (e.g., a cloud-based platform).

[0024] As shown in Figure 1B, the 5G-CN152 includes Access and Mobility Management Function (AMF) 158A and User Plane Function (UPF) 158B, as shown in Figure 1B as a single component AMF / UPF158 for brevity. The UPF158B may function as a gateway between the NG-RAN154 and one or more DNs. The UPF158B may perform functions such as packet routing and forwarding, packet inspection and enforcement of user plane policy rules, traffic utilization reporting, uplink classification supporting routing of traffic flows to one or more DNs, quality of service (QoS) processing for the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic validation), downlink packet buffering, and downlink data notification triggers. The UPF158B may support multi-homed PDU sessions by functioning as an anchor point for intra / inter-radio access technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point interconnected to one or more DNs, and / or a branch point. UE156 can be configured to receive services via a PDU session, which is a logical connection between the UE and the DN.

[0025] The AMF158A may perform functions such as termination of non-access layer (NAS) signaling, NAS signaling security, access layer (AS) security control, inter-CN node signaling for mobility between 3GPP® access networks, idle-mode UE reachability (e.g., control and execution of paging retransmission), registered area management, intra-system and inter-system mobility support, access authentication, access permission including roaming privilege checks, mobility management control (subscriptions and policies), network slicing support, and / or selection of session management functions (SMF). NAS may refer to functions operating between CN and UE, and AS may refer to functions operating between UE and RAN.

[0026] For clarity, 5G-CN152 may include one or more additional network functions not shown in Figure 1B. For example, 5G-CN152 may include one or more of the following: Session Management Function (SMF), NR Repository Function (NRF), Policy Control Function (PCF), Network Exposure Function (NEF), Unified Data Management (UDM), Application Function (AF), and / or Authentication Server Function (AUSF).

[0027] NG-RAN154 may connect 5G-CN152 to UE156 via radio communication over an air interface. NG-RAN154 may include one or more gNBs (collectively gNB160) illustrated as gNB160A and gNB160B and / or one or more ng-eNBs (collectively ng-eNB162) illustrated as ng-eNB162A and ng-eNB162B. gNB160 and ng-eNB162 may more commonly be referred to as base stations. gNB160 and ng-eNB162 may include one or more sets of antennas for communicating with UE156 over an air interface. For example, one or more gNB160s and / or one or more ng-eNB162s may include three sets of antennas for controlling three cells (or sectors), each. In addition, the gNB160 and ng-eNB162 cells can provide wireless coverage to the UE156 over a wide geographical area to support UE mobility.

[0028] As shown in Figure 1B, gNB160 and / or ng-eNB162 may be connected to 5G-CN152 via the NG interface and to other base stations via the Xn interface. The NG and Xn interfaces may be established on an underlying transport network, such as an Internet Protocol (IP) transport network, using direct physical and / or indirect connections. gNB160 and / or ng-eNB162 may be connected to UE156 via the Uu interface. For example, as shown in Figure 1B, gNB160A may be connected to UE156A via the Uu interface. The NG, Xn, and Uu interfaces are associated with a protocol stack. The protocol stack associated with an interface may be used by the network elements in Figure 1B to exchange data and signaling messages and may include two planes: a user plane and a control plane. The user plane may process data of interest to the user. The control plane may process signaling messages of interest to the network elements.

[0029] The gNB160 and / or ng-eNB162 may be connected to one or more AMF / UPF functions of the 5G-CN152, such as the AMF / UPF158, by one or more NG interfaces. For example, the gNB160A may be connected to the UPF158B of the AMF / UPF158 by an NG-User Plane (NG-U) interface. The NG-U interface may provide the supply of user plane PDUs between the gNB160A and the UPF158B (e.g., unguaranteed delivery). The gNB160A may be connected to the AMF158A using an NG Control Plane (NG-C) interface. The NG-C interface may provide, for example, NG interface management, UE context management, UE mobility management, NAS message forwarding, paging, PDU session management and configuration forwarding and / or warning message transmission.

[0030] The gNB160 can provide NR user plane and control plane protocol termination to UE156 on a Uu interface. For example, the gNB160A can provide NR user plane and control plane protocol termination to UE156A on a Uu interface associated with a first protocol stack. The ng-eNB162 can provide Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol termination to UE156 on a Uu interface, where E-UTRA refers to 3GPP® 4G radio access technology. For example, the ng-eNB162B can provide E-UTRA user plane and control plane protocol termination to UE156B on a Uu interface associated with a second protocol stack.

[0031] The 5G-CN152 was described as being configured to handle NR and 4G radio access. Those skilled in the art will understand that it may be possible for NR to connect to the 4G core network in a mode known as “non-standalone operation.” In non-standalone operation, the 4G core network is used to provide (or at least support) control plane functions (e.g., initial access, mobility, and paging). Although only one AMF / UPF158 is shown in Figure 1B, one gNB or ng-eNB may be connected to multiple AMF / UPF nodes to provide redundancy and / or load shares across multiple AMF / UPF nodes.

[0032] As can be considered, in Figure 1B, interfaces between network elements (e.g., Uu, Xn, and NG interfaces) may be associated with a protocol stack used by the network elements to exchange data and signaling messages. The protocol stack may include two planes: a user plane and a control plane. The user plane may process data of interest to the user, and the control plane may process signaling messages of interest to the network elements.

[0033] Figures 2A and 2B show examples of NR user plane and NR control plane protocol stacks for the Uu interface between UE210 and gNB220, respectively. The protocol stacks shown in Figures 2A and 2B may be the same as or similar to those used for the Uu interface between UE156A and gNB160A shown in Figure 1B.

[0034] Figure 2A shows the NR user plane protocol stack, which includes five layers, implemented in the UE210 and gNB220. At the bottom of the protocol stack, the physical layers (PHYs) 211 and 221 can provide transport services to the upper layers of the protocol stack and may correspond to layer 1 of the Open Systems Interconnection (OSI) model. The following four protocols above PHYs 211 and 221 include the Media Access Control Layer (MAC) 212 and 222, the Radio Link Control Layer (RLC) 213 and 223, the Packet Data Convergence Protocol Layer (PDCP) 214 and 224, and the Service Data Application Protocol Layer (SDAP) 215 and 225. Together, these four protocols may constitute layer 2 or the data link layer of the OSI model.

[0035] Figure 3 shows one embodiment of the services provided between the protocol layers of the NR user plane protocol stack. Starting from the top of Figures 2A and 3, SDAP215 and 225 may perform QoS flow processing. UE210 may receive services via a PDU session, which may be a logical connection between UE210 and DN. A PDU session may have one or more QoS flows. CN's UPF (e.g., UPF158B) may map IP packets to one or more QoS flows in the PDU session based on QoS requirements (e.g., with respect to delay, data rate, and / or error rate). SDAP215 and 225 may perform mapping / unmapping between one or more QoS flows and one or more data radio bearers. Mapping / unmapping between QoS flows and data radio bearers may be determined by SDAP225 at gNB220. SDAP215 at UE210 may be notified about the mapping between QoS flows and data radio bearers via reflected mapping or control signaling received from gNB220. Regarding reflection mapping, the SDAP225 on the gNB220 can mark downlink packets with a QoS flow indicator (QFI), which can be observed by the SDAP215 on the UE210 to determine mapping / unmapping between the QoS flow and the data radio bearer.

[0036] PDCP214 and 224 can perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, encryption / decryption to prevent unauthorized decoding of data transmitted over the air interface, and integrity protection (to ensure that control messages originate from the intended source). PDCP214 and 224 can perform, for example, retransmission of undelivered packets, intra-sequence delivery and reordering of packets, and removal of duplicate packets for handover within gNB. PDCP214 and 224 can perform packet duplication to improve the likelihood of received packets and to remove any duplicate packets at the receiver. Packet duplication may be useful for services requiring high reliability.

[0037] Although not shown in Figure 3, PDCP214 and 224 can perform mapping / unmapping between split radio bearers and RLC channels in a dual-connection scenario. Dual-connection is a technique that allows a UE to connect to two cells, or more generally, two cell groups: a master cell group (MCG) and a secondary cell group (SCG). A split bearer is when a single radio bearer, such as one of the radio bearers provided by PDCP214 and 224 as a service to SDAP215 and 225, is handled by a cell group in a dual-connection. PDCP214 and 224 can map / unmap split radio bearers between RLC channels belonging to the cell group.

[0038] RLC213 and 223 can perform segmentation, retransmission via Automatic Repeat Request (ARQ), and removal of replicated data units received from MAC212 and 222, respectively. RLC213 and 223 can support three transmission modes: transparent mode (TM), unacknowledged response mode (UM), and acknowledgment mode (AM). Based on the transmission mode in which the RLC is operating, the RLC may perform one or more of the indicated functions. This RLC configuration can be per logical channel, independent of numerology and / or transmission time interval (TTI) duration. As shown in Figure 3, RLC213 and 223 can provide RLC channels as a service to PDCP214 and 224, respectively.

[0039] MAC212 and 222 may perform logical channel multiplexing / demultiplexing and / or mapping between logical channels and transport channels. Multiplexing / demultiplexing may include multiplexing / demultiplexing of data units belonging to one or more logical channels to / from transport blocks (TBs) delivered to / from PHY211 and 221. MAC222 may be configured to perform scheduling, scheduling information reporting, and priority processing between UEs by dynamic scheduling. Scheduling may be performed by gNB220 (on MAC222) for downlink and uplink. MAC212 and 222 may be configured to perform error correction, priority processing between logical channels of UE210 by logical channel prioritization, and / or padding through Hybrid Automatic Repeating Requests (HARQ) (e.g., one HARQ entity per carrier in the case of Carrier Aggregation (CA)). MAC212 and 222 may support one or more numerology and / or transmission timings. In one embodiment, mapping restrictions in logical channel prioritization can control which numerology and / or transmission timing a logical channel may use. As shown in Figure 3, MACs 212 and 222 may provide logical channels to RLCs 213 and 223 as a service.

[0040] PHY211 and 221 can perform transport channel mapping to physical channels and digital and analog signal processing functions for transmitting and receiving information over the air interface. These digital and analog signal processing functions may include, for example, coding / decoding and modulation / demodulation. PHY211 and 221 can perform multi-antenna mapping. As shown in Figure 3, PHY211 and 221 may provide one or more transport channels to MAC212 and 222 as a service.

[0041] Figure 4A shows an example of downlink data flow through the NR user plane protocol stack. Figure 4A shows the downlink data flow of three IP packets (n, n+1, and m) through the NR user plane protocol stack, generating two TBs on the gNB220. Uplink data flow through the NR user plane protocol stack may be similar to the downlink data flow shown in Figure 4A.

[0042] The downlink data flow in Figure 4A begins when SDAP225 receives three IP packets from one or more QoS flows and maps the three packets to wireless bearers. In Figure 4A, SDAP225 maps IP packets n and n+1 to the first wireless bearer 402 and IP packet m to the second wireless bearer 404. An SDAP header (labeled "H" in Figure 4A) is added to the IP packets. Data units from / to the upper protocol layer are called service data units (SDUs) in the lower protocol layer, and data units to / from the lower protocol layer are called protocol data units (PDUs) in the upper protocol layer. As shown in Figure 4A, the data unit from SDAP225 is the SDU of the lower protocol layer PDCP224 and the PDU of SDAP225.

[0043] The remaining protocol layers in Figure 4A may perform relevant functions (e.g., with respect to Figure 3), add corresponding headers, and forward their respective outputs to the next lower layer. For example, PDCP224 may perform IP header compression and encryption and forward its output to RLC223. RLC223 may optionally perform segmentation (e.g., as shown for IP packet m in Figure 4A) and forward its output to MAC222. MAC222 may multiplex several RLC PDUs and attach MAC subheaders to the RLC PDUs to form transport blocks. In NR, as shown in Figure 4A, MAC subheaders may be distributed throughout the MAC PDU. In LTE, MAC subheaders may be located entirely at the beginning of the MAC PDU. The NR MAC PDU structure can reduce processing time and associated delays because the MAC PDU subheaders may be computed before the complete MAC PDU is assembled.

[0044] Figure 4B shows an exemplary format of a MAC subheader in a MAC PDU. The MAC subheader includes an SDU length field to indicate the length (in bytes, etc.) of the MAC SDU that the MAC subheader corresponds to, a logical channel identifier (LCID) field to identify the logical channel initiated by the MAC SDU to assist in the multiplexing process, a flag (F) to indicate the size of the SDU length field, and a reserved bit (R) field for future use.

[0045] Figure 4B further illustrates MAC control elements (CEs) inserted into a MAC PDU by MACs such as MAC223 or MAC222. For example, Figure 4B shows two MAC CEs inserted into a MAC PDU. MAC CEs may be inserted at the beginning of the MAC PDU for downlink transmission (as shown in Figure 4B) and at the end of the MAC PDU for uplink transmission. MAC CEs may be used for in-band control signaling. Examples of MAC CEs include scheduling-related MAC CEs such as buffer status reports and power headroom reports, on / off MAC CEs for PDCP duplicate detection on / off, channel status information (CSI) reports, sounding reference signal (SRS) transmission, and pre-configured components, discontinuous receive (DRX)-related MAC CEs, timing progression MAC CEs, and random access-related MAC CEs. MAC CEs may be preceded by a MAC subheader in a format similar to that described for MAC SDUs and may be identified by a reserved value in the LCID field, which indicates the type of control information contained in the MAC CE.

[0046] Before describing the NR control plane protocol stack, we will first explain the logical channels, transport channels, and physical channels, as well as the mapping between channel types. One or more channels can be used to perform functions related to the NR control plane protocol stack, which will be discussed later.

[0047] Figures 5A and 5B show the mapping between logical channels, transport channels, and physical channels for downlink and uplink, respectively. Information is passed through channels between the RLC, MAC, and PHY of the NR protocol stack. Logical channels can be used between the RLC and MAC and can be classified as control channels that carry control and configuration information in the NR control plane, or as traffic channels that carry data in the NR user plane. Logical channels can be classified as dedicated logical channels for a particular UE, or as common logical channels that can be used by two or more UEs. Logical channels can also be defined by the type of information they carry. The set of logical channels defined by NR is, for example, - A paging control channel (PCCH) for carrying paging messages used to page UEs whose location is not known to the network at the cell level, - A broadcast control channel (BCCH) for carrying system information messages in the form of master information blocks (MIBs) and several system information blocks (SIBs), wherein the system information messages are used by the UE to obtain information about how the cell is configured and how it operates within the cell. - A common control channel (CCCH) for carrying control messages along with random access, -To configure the UE, a dedicated control channel (DCCH) is provided for transporting control messages to and from a specific UE. - Includes a dedicated traffic channel (DTCH) for transporting user data to and from specific UEs.

[0048] A transport channel is used between the MAC layer and the PHY layer and can be defined by how the information they carry is transmitted over the air interface. A set of transport channels defined by NR is, for example, - A paging channel (PCH) for carrying paging messages transmitted from the PCCH, - A broadcast channel (BCH) for transporting MIBs from BCCH, - A downlink shared channel (DL-SCH) for carrying downlink data and signaling messages, including SIBs from BCCH, - Uplink shared channel (UL-SCH) for transporting uplink data and signaling messages, - Includes Random Access Channels (RACH) that allow UEs to connect to the network without prior scheduling.

[0049] A PHY can pass information between its processing levels using physical channels. A physical channel may have an associated set of time-frequency resources for carrying information across one or more transport channels. The PHY may generate control information to support its low-level operation and provide control information to the lower levels of the PHY via physical control channels known as L1 / L2 control channels. The set of physical channels and physical control channels defined by NR is, for example, - A physical broadcast channel (PBCH) for transporting MIBs from the BCH, - A physical downlink shared channel (PDSCH) for carrying downlink data and signaling messages from DL-SCH, and paging messages from PCH, - A physical downlink control channel (PDCCH) for carrying downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling authorizations, and uplink power control commands. -UL-SCH and, in some examples, a physical uplink shared channel (PUSCH) for transporting uplink data and signaling messages from uplink control information (UCI), as described below. - A physical uplink control channel (PUCCH) for carrying UCI, which may include HARQ acknowledgment responses, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and scheduling requests (SR), - Includes a physical random access channel (PRACH) for random access.

[0050] Similar to the physical control channel, the physical layer generates physical signals to support the low-level operation of the physical layer. As shown in Figures 5A and 5B, the physical layer signals defined by the NR include the primary synchronization signal (PSS), secondary synchronization signal (SSS), channel state information reference signal (CSI-RS), demodulation reference signal (DMRS), sounding reference signal (SRS), and phase tracking reference signal (PT-RS). These physical layer signals are described in more detail below.

[0051] Figure 2B shows one embodiment of an NR control plane protocol stack. As shown in Figure 2B, the NR control plane protocol stack may use four first protocol layers, the same / similar to those in the example of the NR user plane protocol stack. These four protocol layers include PHY 211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224. Instead of having SDAP 215 and 225 at the top of the stack, as in the NR user plane protocol stack, the NR control plane stack has Radio Resource Control (RRC) 216 and 226, and NAS protocols 217 and 237 at the top of the NR control plane protocol stack.

[0052] NAS protocols 217 and 237 can provide control plane functions between the UE210 and the AMF230 (e.g., AMF158A), or more generally, between the UE210 and the CN. NAS protocols 217 and 237 can provide control plane functions between the UE210 and the AMF230 via signaling messages referred to as NAS messages. There is no direct path for NAS messages to be transported between the UE210 and the AMF230. NAS messages can be transported using the AS of the Uu and NG interfaces. NAS protocols 217 and 237 can provide control plane functions such as authentication, security, connection setup, mobility management, and session management.

[0053] RRC216 and 226 may provide control plane functionality between UE210 and gNB220, or more generally, between UE210 and RAN. RRC216 and 226 may provide control plane functionality between UE210 and gNB220 via signaling messages referred to as RRC messages. RRC messages may be transmitted between UE210 and RAN using a signaling radio bearer and the same / similar PDCP, RLC, MAC, and PHY protocol layers. MAC may multiplex control plane and user plane data within the same transport block (TB). RRC216 and 226 may provide control plane functions such as broadcasting system information related to the AS and NAS, paging initiated by the CN or RAN, establishing, maintaining, and releasing RRC connections between the UE210 and the RAN, security functions including key management, establishing, configuring, maintaining, and releasing signaling radio bearers and data radio bearers, mobility functions, QoS management functions, UE measurement reporting and reporting control, radio link failure (RLF) detection and recovery, and / or NAS message forwarding. As part of establishing the RRC connection, RRC216 and 226 may establish an RRC context, which may involve setting parameters for communication between the UE210 and the RAN.

[0054] Figure 6 is an exemplary diagram illustrating the RRC state transitions of a UE. The UE may be the same as or similar to the wireless device 106 shown in Figure 1A, the UE 210 shown in Figures 2A and 2B, or any other wireless device described herein. As shown in Figure 6, the UE may be in at least one of three RRC states: RRC connected 602 (e.g., RRC-CONNECTED), RRC idle 604 (e.g., RRC-IDLE), and RRC inactive 606 (e.g., RRC-INACTIVE).

[0055] In RRC connection 602, the UE has an established RRC context and may have at least one RRC connection with a base station. The base station may be one or more base stations included in RAN104 shown in Figure 1A, one of gNB160 or ng-eNB162 shown in Figure 1B, gNB220 shown in Figures 2A and 2B, or any other base station similar to any other base station described herein. The base station to which the UE is connected may have the UE's RRC context. The RRC context, referred to as the UE context, may include parameters for communication between the UE and the base station. These parameters may include, for example, one or more AS contexts, one or more radio link configuration parameters, bearer configuration information (e.g., related to data radio bearers, signaling radio bearers, logical channels, QoS flows, and / or PDU sessions), security information, and / or PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information. In RRC connection 602, the UE's mobility may be managed by the RAN (e.g., RAN104 or NG-RAN154). The UE may measure signal levels (e.g., reference signal levels) from the serving cell and adjacent cells and report these measurements to the base station currently serving the UE. Based on the reported measurements, the UE's serving base station may request a handover to one of the adjacent base stations' cells. The RRC state may transition from RRC connection 602 to RRC idle 604 via connection release procedure 608, or to RRC inactive 606 via connection deactivation procedure 610.

[0056] In RRC idle 604, the RRC context may not be established for the UE. In RRC idle 604, the UE may not have an RRC connection with the base station. While in RRC idle 604, the UE may be in a sleep state for most of the time (e.g., to conserve battery power). The UE may wake up periodically (e.g., once per discontinuous receive cycle) to monitor paging messages from the RAN. The mobility of the UE may be managed by the UE through a procedure known as cell reselection. The RRC state may transition from RRC idle 604 to RRC connected 602 via a connection establishment procedure 612, which may involve a random access procedure, as will be discussed in more detail below.

[0057] In RRC inactive 606, the previously established RRC context is maintained at the UE and base station. This reduces signaling overhead compared to the transition from RRC idle 604 to RRC connected 602, enabling a faster transition to RRC connected 602. In RRC inactive 606, the UE is in a sleep state, and the UE's mobility can be managed by the UE through cell reselection. The RRC state can transition from RRC inactive 606 to RRC connected 602 via connection restart procedure 614, or to RRC idle 604 via connection release procedure 616, which is the same as or similar to connection release procedure 608.

[0058] The RRC state can be associated with a mobility management mechanism. In RRC idle 604 and RRC inactive 606, mobility is managed by the UE through cell reselection. The purpose of mobility management in RRC idle 604 and RRC inactive 606 is to enable the network to notify the UE of events via paging messages without broadcasting paging messages across the entire mobile communications network. The mobility management mechanism used in RRC idle 604 and RRC inactive 606 may allow the network to track the UE at the cell group level so that paging messages can be broadcast on the cells of the cell group in which the UE currently resides, instead of across the entire mobile communications network. The mobility management mechanism in RRC idle 604 and RRC inactive 606 tracks the UE at the cell group level. They may do so using grouping at different granularities. For example, there may be three levels of granularity for cell grouping: individual cells, cells within a RAN area identified by a RAN Area Identifier (RAI), and cells within a group of RAN areas called a tracking area, identified by a Tracking Area Identifier (TAI).

[0059] A tracking area can be used to track a UE at the CN level. The CN (e.g., CN102 or 5G-CN152) may provide the UE with a list of TAIs associated with the UE registration area. If the UE moves to a cell associated with a TAI that is not included in the list of TAIs associated with the UE registration area through cell reselection, the UE may perform a registration update in the CN so that the CN can update the UE's location and provide the UE with a new UE registration area.

[0060] RAN areas can be used to track UEs at the RAN level. For UEs in an RRC inactive 606 state, a RAN notification area may be assigned to the UE. A RAN notification area may contain one or more cell identities, a list of RAIs, or a list of TAIs. In one embodiment, a base station may belong to one or more RAN notification areas. In one embodiment, a cell may belong to one or more RAN notification areas. If a UE moves to a cell that is not included in the RAN notification area assigned to the UE through cell reselection, the UE may perform a notification area update in the RAN to update the UE's RAN notification area.

[0061] A base station that stores the RRC context for a UE, or the last serving base station of the UE, may be referred to as an anchor base station. The anchor base station may maintain the RRC context for the UE at least for the duration that the UE remains in the anchor base station's RAN notification area and / or for the duration that the UE remains in an RRC inactive 606.

[0062] A gNB, such as the gNB160 in Figure 1B, can be divided into two parts: a central unit (gNB-CU) and one or more distributed units (gNB-DU). The gNB-CU can be coupled to one or more gNB-DUs using the F1 interface. The gNB-CU may include RRC, PDCP, and SDAP. The gNB-DU may include RLC, MAC, and PHY.

[0063] In NR, physical signals and physical channels (considered in relation to Figures 5A and 5B) can be mapped onto orthogonal frequency division multiplexing (OFDM) symbols. OFDM is a multicarrier communication scheme that transmits data over F orthogonal subcarriers (or tones). Before transmission, the data can be mapped to a series of complex symbols (e.g., M orthogonal amplitude modulation (M-QAM) or M phase shift keying (M-PSK) symbols) which are divided into F parallel symbol streams, referred to as source symbols. The F parallel symbol streams can be used as input to an inverse fast Fourier transform (IFFT) block that converts them to the time domain as if they were in the frequency domain. The IFFT block can take one from each of the F parallel symbol streams at a time into an F source symbol, and use each source symbol to modulate the amplitude and phase of one of the F sinusoidal basis functions corresponding to the F orthogonal subcarriers. The output of the IFFT block may be an F time domain sample representing the sum of the F orthogonal subcarriers. An F time domain sample can form a single OFDM symbol. After some processing (e.g., adding cyclic prefixes) and upconversion, the OFDM symbols provided by the IFFT block can be transmitted over the air interface at the carrier frequency. The parallel symbol streams can be mixed using an FFT block before being processed by the IFFT block. This process generates OFDM symbols precoded with discrete Fourier transform (DFT), which can be used by the UE in the uplink to reduce the peak-to-average power ratio (PAPR). The reverse process can be performed on the OFDM symbols at the receiver using an FFT block to reconstruct the data mapped to the source symbols.

[0064] Figure 7 shows an exemplary configuration of an NR frame in which OFDM symbols are grouped. An NR frame can be identified by a System Frame Number (SFN). An SFN may repeat over a period of 1024 frames. As shown, one NR frame may have a duration of 10 milliseconds (ms) and may contain 10 subframes, each with a duration of 1 millisecond. A subframe may be divided into slots, for example, each containing 14 OFDM symbols.

[0065] The duration of a slot may depend on the numerology used for the OFDM symbol of the slot. NR supports flexible numerology to accommodate different cell deployments (e.g., cells with carrier frequencies less than 1 GHz up to cells with carrier frequencies in the range of mm waves). Numerology can be defined with respect to subcarrier spacing and cyclic prefix duration. For numerology in NR, subcarrier spacing can be scaled up by a power of 2 from a baseline subcarrier spacing of 15 kHz, and cyclic prefix duration can be scaled down by a power of 2 from a baseline cyclic prefix duration of 4.7 μs. For example, NR defines numerology with the following subcarrier spacing / cyclic prefix duration combinations: 15 kHz / 4.7 μs, 30 kHz / 2.3 μs, 60 kHz / 1.2 μs, 120 kHz / 0.59 μs, and 240 kHz / 0.29 μs.

[0066] A slot can have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). Numerologies with higher subcarrier spacing have shorter slot durations and, accordingly, more slots per subframe. Figure 7 shows this numerology-dependent slot duration and slot transmission structure per subframe (for ease of illustration, numerologies with a 240 kHz subcarrier spacing are not shown in Figure 7). Subframes within the NR can be used as a numerology-independent time reference, while slots can be used as units on which uplink and downlink transmissions are scheduled. To support low latency, scheduling in the NR is separated from slot duration and can start with any OFDM symbol and continue for as many symbols as needed for transmission. These partial slot transmissions can be referred to as mini-slot transmissions or sub-slot transmissions.

[0067] Figure 8 shows an exemplary configuration of slots in the time and frequency domains of an NR carrier. A slot contains resource elements (REs) and resource blocks (RBs). An RE is the smallest physical resource in an NR. An RE spans one OFDM symbol in the time domain by one subcarrier in the frequency domain, as shown in Figure 8. An RB spans 12 consecutive REs in the frequency domain, as shown in Figure 8. An NR carrier may be limited to a width of 275 RBs or 275 × 12 = 3300 subcarriers. When used, such limitations may restrict the NR carrier to 50, 100, 200, and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz, respectively, with the 400 MHz bandwidth being set based on a carrier bandwidth limit of 400 MHz per unit.

[0068] Figure 8 shows a single numerology used across the entire bandwidth of the NR carrier. In other exemplary configurations, multiple numerologies may be supported on the same carrier.

[0069] NR can support a wide range of carrier bandwidths (e.g., up to 400 MHz for a 120 kHz subcarrier spacing). Not all UEs can receive the full carrier bandwidth (e.g., due to hardware limitations). Also, receiving the full carrier bandwidth may be prohibited from a power consumption standpoint for the UE. In one embodiment, to reduce power consumption and / or for other purposes, the UE may adapt the size of its receive bandwidth based on the amount of traffic scheduled to be received by the UE. This is called bandwidth adaptation.

[0070] NR supports UEs that cannot receive the entire carrier bandwidth and defines a Bandwidth Portion (BWP) that supports bandwidth adaptation. In one embodiment, a BWP may be defined by a subset of consecutive RBs on the carrier. A UE may consist of one or more downlink BWPs and one or more uplink BWPs per serving cell (e.g., up to four downlink BWPs and up to four uplink BWPs per serving cell) (e.g., via the RRC layer). At a given time, one or more of the BWPs configured for a serving cell may be active. These one or more BWPs may be referred to as the active BWPs of the serving cell. When a serving cell consists of a secondary uplink carrier, the serving cell may have one or more first active BWPs on the uplink carrier and one or more second active BWPs on the secondary uplink carrier.

[0071] For unpaired spectra, if the downlink BWP index of one downlink BWP is the same as the uplink BWP index of the other uplink BWP, then a downlink BWP from the configured set of downlink BWPs can be linked with an uplink BWP from the configured set of uplink BWPs. For unpaired spectra, the UE can expect that the center frequency of the downlink BWP is the same as the center frequency of the uplink BWP.

[0072] For a set of downlink BWPs configured on a primary cell (PCell), a base station may configure a UE for at least one search space with one or more control resource sets (CORESETs). A search space is a set of locations in the time and frequency domains from which a UE can find control information. A search space can be a UE-specific search space or a common search space (potentially usable by multiple UEs). For example, in an active downlink BWP, a base station may configure a UE in a common search space on a PCell or on a primary / secondary cell (PSCell).

[0073] For uplink BWPs within a configured set of uplink BWPs, the BS may configure the UE with one or more resource sets for one or more PUCCH transmissions. The UE may receive downlink receptions (e.g., PDCCH or PDSCH) within the downlink BWP according to the configured numerology (e.g., subcarrier spacing and cyclic prefix duration) for the downlink BWP. The UE may transmit uplink transmissions (e.g., PUCCH or PUSCH) within the uplink BWP according to the configured numerology (e.g., subcarrier spacing and cyclic prefix length of the uplink BWP).

[0074] One or more BWP indicator fields may be provided to the Downlink Control Information (DCI). The values ​​of the BWP indicator fields may indicate which of the configured set of BWPs is the active downlink BWP for one or more downlink receptions. The values ​​of one or more BWP indicator fields may indicate the active uplink BWP for one or more uplink transmissions.

[0075] A base station may semi-statically configure a UE with the default downlink BWP in the set of configured downlink BWPs associated with the PCell. If the base station does not provide a default downlink BWP for the UE, the default downlink BWP may be the initial active downlink BWP. The UE may determine which BWP is the initial active downlink BWP based on the CORESET configuration obtained using the PBCH.

[0076] A base station can configure the UE with the PCell's BWP inactive timer value. The UE may start or restart the BWP inactive timer at any appropriate time. For example, the UE may start or restart the BWP inactive timer when (a) the UE detects a DCI indicating an active downlink BWP other than the default downlink BWP for a paired spectral operation, or (b) the UE detects a DCI indicating an active downlink BWP or active uplink BWP other than the default downlink BWP or uplink BWP for an unpaired spectral operation. If the UE does not detect a DCI for a certain period (e.g., 1 millisecond or 0.5 milliseconds), the UE may run the BWP inactive timer toward expiration (e.g., increasing from 0 to the BWP inactive timer value, or decreasing from the BWP inactive timer value to 0). When the BWP inactive timer expires, the UE may switch from the active downlink BWP to the default downlink BWP.

[0077] In one embodiment, a base station may semi-statically configure a UE having one or more BWPs. The UE may switch the active BWP from the first BWP to the second BWP in response to receiving a DCI indicating a second BWP as the active BWP, and / or in response to the expiration of a BWP inactivity timer (for example, if the second BWP is the default BWP).

[0078] Downlink and uplink BWP switching (where BWP switching refers to switching from a currently active BWP to a currently inactive BWP) can be performed independently in a paired spectrum. In non-paired spectra, downlink and uplink BWP switching can be performed simultaneously. Switching between configured BWPs can occur based on RRC signaling, DCI, expiration of BWP inactivity timers, and / or the initiation of random access.

[0079] Figure 9 shows an example of bandwidth adaptation using three configured BWPs for an NR carrier. The UE, composed of the three BWPs, can switch from one BWP to another at a switching point. In the example shown in Figure 9, the BWPs include BWP902 with a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz, BWP904 with a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz, and BWP906 with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. BWP902 may be the initial active BWP, and BWP904 may be the default BWP. The UE can switch between BWPs at a switching point. In the example in Figure 9, the UE may switch from BWP902 to BWP904 at switching point 908. The switch at switching point 908 may occur for any preferred reason, for example, in response to the expiration of a BWP inactive timer (indicating a switch to the default BWP) and / or in response to receiving a DCI indicating BWP904 as the active BWP. The UE may switch from active BWP904 to BWP906 at switching point 910 in response to receiving a DCI indicating BWP906 as the active BWP. The UE may switch from active BWP906 to BWP904 at switching point 912 in response to the expiration of the BWP inactive timer and / or in response to receiving a DCI indicating BWP904 as the active BWP. The UE may switch from active BWP904 to BWP902 at switching point 914 in response to receiving a DCI indicating BWP902 as the active BWP.

[0080] If a UE is configured for a secondary cell with a set of configured downlink BWPs and a default downlink BWP in the timer value, the UE procedure for switching BWPs on the secondary cell may be the same / similar to that on the primary cell. For example, the UE may use the timer value and default downlink BWP for the secondary cell in the same / similar manner that the UE uses these values ​​for the primary cell.

[0081] To provide higher data rates, carrier aggregation (CA) can be used to aggregate two or more carriers and transmit them simultaneously to the same UE. The aggregated carriers in CA may be called component carriers (CCs). When CA is used, there are multiple serving cells for the UE and one for the CC. A CC can have three configurations within the frequency domain.

[0082] Figure 10A shows three CA configurations with two CCs. In the in-band, continuous configuration 1002, the two CCs are aggregated in the same frequency band (frequency band A) and are located directly adjacent to each other within the frequency band. In the in-band, discontinuous configuration 1004, the two CCs are aggregated in the same frequency band (frequency band A) and separated into frequency bands by a gap. In the interband configuration 1006, the two CCs are located in frequency bands (frequency band A and frequency band B).

[0083] In one embodiment, up to 32 CCs may be aggregated. The aggregated CCs may have the same or different bandwidths, subcarrier spacings, and / or duplication schemes (TDD or FDD). A serving cell of a UE using a CA may have downlink CCs. In the case of FDD, one or more uplink CCs may be optionally configured for the serving cell. Aggregating more downlink carriers than uplink carriers may be useful, for example, when a UE has more data traffic on the downlink than on the uplink.

[0084] When a CA is used, one of the aggregation cells of a UE may be referred to as a primary cell (PCell). A PCell may be the serving cell to which the UE first connects during RRC connection establishment, re-establishment, and / or handover. A PCell may provide the UE with NAS mobility information and security inputs. A UE may have different PCells. On the downlink, the carrier corresponding to a PCell may be referred to as the downlink primary CC (DL PCC). On the uplink, the carrier corresponding to a PCell may be referred to as the uplink primary CC (UL PCC). Other aggregation cells to the UE may be referred to as secondary cells (SCells). In one embodiment, an SCell may be configured after the PCell has been configured for the UE. For example, an SCell may be configured via an RRC connection reconfiguration procedure. On the downlink, the carrier corresponding to an SCell may be referred to as the downlink secondary CC (DL SCC). On the uplink, the carrier corresponding to an SCell may be referred to as the uplink secondary CC (UL SCC).

[0085] SCells configured for a UE may be activated and deactivated, for example, based on traffic and channel conditions. Deactivating a SCell may mean that PDCCH and PDSCH reception on the SCell is stopped, and PUSCH, SRS, and CQI transmission on the SCell is stopped. Configured SCells may be activated and deactivated using MAC CEs with respect to Figure 4B. For example, a MAC CE may use a bitmap (e.g., one bit per SCell) to indicate to the UE which SCells (e.g., from a subset of configured SCells) are to be activated or deactivated. Configured SCells may be deactivated in response to the expiration of SCell deactivation timers (e.g., one SCell deactivation timer per SCell).

[0086] Downlink control information, such as cell scheduling assignment and scheduling authorization, can be transmitted on the cell corresponding to the assignment and authorization, known as self-scheduling. DCI for a cell can be transmitted on another cell, known as cross-carrier scheduling. Uplink control information for aggregated cells (e.g., HARQ acknowledgments and channel state feedback such as CQI, PMI, and / or RI) can be transmitted on the PCell's PUCCH. A large number of aggregated downlink CCs can overload the PCell's PUCCH. A cell can be divided into multiple PUCCH groups.

[0087] Figure 10B shows one example of how aggregation cells can be configured into one or more PUCCH groups. PUCCH group 1010 and PUCCH group 1050 may each contain one or more downlink CCs. In the example in Figure 10B, PUCCH group 1010 contains three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. PUCCH group 1050, in this example, contains three downlink CCs: PCell 1051, SCell 1052, and SCell 1053. One or more uplink CCs may be configured as PCell 1021, SCell 1022, and SCell 1023. One or more other uplink CCs may be configured as primary S cells (PSCells) 1061, SCell 1062, and SCell 1063. Uplink control information (UCI) related to the downlink CC of PUCCH group 1010, indicated as UCI1031, UCI1032, and UCI1033, can be transmitted on the uplink of PCell 1021. Uplink control information (UCI) related to the downlink CC of PUCCH group 1050, indicated as UCI1071, UCI1072, and UCI1073, can be transmitted on the uplink of PSCell 1061. In one embodiment, if the aggregation cell depicted in Figure 10B is not divided into PUCCH group 1010 and PUCCH group 1050, the single uplink PCell and PCell for transmitting the UCI related to the downlink CC may become overloaded. Overload can be prevented by dividing the transmission of UCI between PCell 1021 and PSCell 1061.

[0088] A cell containing a downlink carrier and optionally an uplink carrier may be assigned a physical cell ID and a cell index. The physical cell ID or cell index may, depending on the context in which the physical cell ID is used, identify the downlink carrier and / or uplink carrier of the cell. The physical cell ID may be determined using synchronization signals transmitted on the downlink component carrier. The cell index may be determined using RRC messages. In this disclosure, the physical cell ID may be referred to as the carrier ID, and the cell index may be referred to as the carrier index. For example, when this disclosure refers to a first physical cell ID for a first downlink carrier, this disclosure may mean that the first physical cell ID is for a cell containing the first downlink carrier. The same concept may apply, for example, to carrier activation. When this disclosure indicates that a first carrier is activated, this specification may mean that the cell containing the first carrier is activated.

[0089] In CA, the multi-carrier nature of the PHY may be exposed to MAC. In one embodiment, HARQ entities may operate on a serving cell. Transport blocks may be generated per allocation / authorization per serving cell. Transport blocks and their potential HARQ retransmissions may be mapped to serving cells.

[0090] On the downlink, the base station may transmit one or more reference signals (RS) (e.g., PSS, SSS, CSI-RS, DMRS, and / or PT-RS, as shown in Figure 5A) to the UE (e.g., unicast, multicast, and / or broadcast). On the uplink, the UE may transmit one or more RS to the base station (e.g., DMRS, PT-RS, and / or SRS, as shown in Figure 5B). PSS and SSS may be transmitted by the base station, used by the UE, and synchronize the UE to the base station. PSS and SSS may be provided within a synchronization signal (SS) / physical broadcast channel (PBCH) block, which includes PSS, SSS, and PBCH. The base station may periodically transmit bursts of SS / PBCH blocks.

[0091] Figure 11A shows one embodiment of the structure and location of an SS / PBCH block. A burst of SS / PBCH blocks may consist of one or more SS / PBCH blocks (e.g., four SS / PBCH blocks as shown in Figure 11A). Bursts may be transmitted periodically (e.g., every two frames or every 20 milliseconds). Bursts may be limited to half frames (e.g., a first half frame with a duration of 5 milliseconds). Figure 11A is an embodiment, and it will be understood that these parameters (number of SS / PBCH blocks per burst, burst period, location of bursts within a frame) may be configured based on, for example, the carrier frequency of the cell through which the SS / PBCH block is transmitted, the cell's numerology or subcarrier spacing, the network configuration (e.g., using RRC signaling), or any other preferred factor. In one embodiment, the UE may assume a subcarrier spacing for the SS / PBCH block based on the monitored carrier frequency, unless the wireless network is configured to assume a different subcarrier spacing.

[0092] An SS / PBCH block may span one or more OFDM symbols in the time domain (e.g., four OFDM symbols as shown in the example in Figure 11A) and one or more subcarriers in the frequency domain (e.g., 240 consecutive subcarriers). PSS, SSS, and PBCH may have a common center frequency. A PSS may be transmitted first, e.g., over one OFDM symbol and 127 subcarriers. An SSS may be transmitted after a PSS (e.g., over the next two symbols), e.g., over one OFDM symbol and 127 subcarriers. A PBCH may be transmitted after a PSS (e.g., over the next three OFDM symbols), e.g., over 240 subcarriers.

[0093] The location of SS / PBCH blocks in the time and frequency domains may be unknown to the UE (e.g., when the UE is searching for a cell). To find and select a cell, the UE may monitor the carrier of the PSS. For example, the UE may monitor the frequency position within the carrier. If the PSS is not found after a certain duration (e.g., 20 milliseconds), the UE may search for the PSS at a different frequency position within the carrier, as indicated by the synchronization raster. If the PSS is found at a location in the time and frequency domains, the UE may determine the locations of the SSS and PBCH, respectively, based on the known structure of the SS / PBCH block. The SS / PBCH block may be a cell-defined SS block (CD-SSB). In one embodiment, a primary cell may be associated with a CD-SSB. The CD-SSB may be located on a synchronization raster. In one embodiment, cell selection / search and / or re-selection may be based on the CD-SSB.

[0094] SS / PBCH blocks can be used by the UE to determine one or more parameters of a cell. For example, the UE may determine the physical cell identifier (PCI) of a cell based on the PSS and SSS sequences, respectively. The UE may also determine the location of a cell's frame boundary based on the location of the SS / PBCH block. For example, the SS / PBCH block may indicate that it was transmitted according to a transmission pattern, and the SS / PBCH block in the transmission pattern is at a known distance from the frame boundary.

[0095] The PBCH may use QPSK modulation and forward error correction (FEC). FEC may use polar coding. One or more symbols spanning the PBCH may carry one or more DMRS for demodulation of the PBCH. The PBCH may include the cell's current system frame number (SFN) and / or an index of the SS / PBCH block timing index. These parameters may facilitate time synchronization of the UE to the base station. The PBCH may include a Master Information Block (MIB) used to provide one or more parameters to the UE. The MIB is used by the UE to identify the remaining minimum system information (RMSI) associated with the cell. The RMSI may include a System Information Block Type 1 (SIB1). The SIB1 may include information necessary for the UE to access the cell. The UE may use one or more parameters of the MIB to monitor the PDCCH, which may be used to schedule the PDSCH. The PDSCH may include the SIB1. The SIB1 can be decoded using the parameters provided in the MIB. The PBCH may indicate the absence of the SIB1. Based on the PBCH indicating the absence of SIB1, a frequency may be pointed to the UE. The UE may then search for the SS / PBCH block at the frequency pointed to by the UE.

[0096] The UE may assume that one or more SS / PBCH blocks transmitted with the same SS / PBCH block index are quasi-copositional (QCL) (e.g., having the same / similar Doppler spread, Doppler shift, mean gain, mean delay, and / or spatial Rx parameters). The UE cannot assume that QCL for SS / PBCH block transmissions have different SS / PBCH block indices.

[0097] SS / PBCH blocks (e.g., blocks within a half-frame) can be transmitted in a spatial direction (e.g., using different beams across the cell's coverage area). In one embodiment, a first SS / PBCH block may be transmitted in a first spatial direction using a first beam, and a second SS / PBCH block may be transmitted in a second spatial direction using a second beam.

[0098] In one embodiment, within the carrier frequency span, a base station may transmit multiple SS / PBCH blocks. In one embodiment, the first PCI of a first SS / PBCH block of multiple SS / PBCH blocks may be different from the second PCI of a second SS / PBCH block of multiple SS / PBCH blocks. PCIs of SS / PBCH blocks transmitted at different frequency locations may be different or the same.

[0099] CSI-RS can be transmitted by a base station and used by an UE to obtain channel status information (CSI). A base station may configure an UE with one or more CSI-RS for channel estimation or any other appropriate purpose. A base station may configure an UE with one or more identical / similar CSI-RS. An UE may measure one or more CSI-RS. Based on the measurement of one or more downlink CSI-RS, an UE may estimate the downlink channel status and / or generate a CSI report. An UE may provide the CSI report to the base station. The base station may perform link fitting using feedback provided by the UE (e.g., estimated downlink channel status).

[0100] A base station can semi-statically configure a UE with one or more sets of CSI-RS resources. CSI-RS resources may be associated with location and periodicity within the time and frequency domains. A base station may selectively activate and / or deactivate CSI-RS resources. A base station may indicate to the UE that CSI-RS resources within a set of CSI-RS resources are being activated and / or deactivated.

[0101] A base station can be configured to report CSI measurements. A base station can be configured to provide CSI reports periodically, aperiodicly, or semi-persistently. For periodic CSI reporting, the UE can consist of multiple CSI reports with varying timing and / or periodicity. For aperiodic CSI reporting, the base station can request the CSI report. For example, a base station can instruct the UE to measure configured CSI-RS resources and provide a CSI report on the measurements. For semi-persistent CSI reporting, the base station can configure the UE to periodically transmit periodic reports and selectively activate or deactivate them. A base station can use RRC signaling to configure the UE with CSI-RS resource sets and CSI reports.

[0102] A CSI-RS configuration may include one or more parameters indicating, for example, up to 32 antenna ports. The UE may be configured to use the same OFDM symbols for the downlink CSI-RS and the control resource set (CORESET) if the downlink CSI-RS and CORESET are spatially QCLed and the resource elements associated with the downlink CSI-RS are outside the physical resource block (PRB) configured for the CORESET. The UE may also be configured to use the same OFDM symbols for the downlink CSI-RS and the SS / PBCH block if the downlink CSI-RS and the SS / PBCH block are spatially QCLed and the resource elements associated with the downlink CSI-RS are outside the PRB configured for the SS / PBCH block.

[0103] Downlink DMRS may be transmitted by a base station and used by an UE for channel estimation. For example, downlink DMRS may be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCHs). An NR network may support one or more variable and / or configurable DMRS patterns for data demodulation. At least one downlink DMRS configuration may support a front-loaded DMRS pattern. A front-loaded DMRS may be mapped to one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). A base station may semi-statically configure an UE using the number of front-loaded DMRS symbols (e.g., maximum number) of the PDSCH. A DMRS configuration may support one or more DMRS ports. For example, in the case of single-user MIMO, a DMRS configuration may support up to eight orthogonal downlink DMRS ports per UE. In the case of multi-user MIMO, a DMRS configuration may support up to four orthogonal downlink DMRS ports per UE. A wireless network can support a common DMRS structure for downlink and uplink (e.g., at least for CP-OFDM). DMRS locations, DMRS patterns, and / or scrambling sequences may be the same or different. Base stations may transmit downlink DMRS and corresponding PDSCHs using the same precoding matrix. A UE may use one or more downlink DMRSs for coherent demodulation / channel estimation of PDSCHs.

[0104] In one embodiment, a transmitter (e.g., a base station) may use a precoder matrix for a portion of the transmission bandwidth. For example, the transmitter may use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. The first and second precoder matrices may differ based on the fact that the first bandwidth is different from the second bandwidth. The UE may assume that the same precoder matrix is ​​used across a set of PRBs. A set of PRBs may be represented as a precoder resource block group (PRG).

[0105] A PDSCH may contain one or more layers. The UE may assume that at least one symbol with a DMRS exists on one or more layers of the PDSCH. The upper layers may constitute up to three DMRSs for the PDSCH.

[0106] Downlink PT-RS may be transmitted by the base station and used by the UE for phase noise compensation. The presence of downlink PT-RS depends on the RRC configuration. The presence and / or pattern of downlink PT-RS may be configured on a UE-specific basis using a combination of RRC signaling and / or association with one or more parameters used for other purposes (e.g., Modulation and Coding Scheme (MCS)), which may be indicated by DCI. When configured, the dynamic presence of downlink PT-RS may be associated with one or more DCI parameters, including at least the MCS. An NR network may support multiple PT-RS densities defined in the time and / or frequency domains. The frequency domain density, if present, may be associated with at least one configuration of the scheduled bandwidth. The UE may assume the same precoding for DMRS ports and PT-RS ports. The number of PT-RS ports may be less than the number of DMRS ports in the scheduled resources. Downlink PT-RS may be limited to the UE's scheduled time / frequency period. Downlink PT-RS may be transmitted on symbols to facilitate phase tracking at the receiver.

[0107] The UE may transmit uplink DMRS to the base station for channel estimation. For example, the base station may use uplink DMRS for coherent demodulation of one or more uplink physical channels. For example, the UE may transmit uplink DMRS on PUSCH and / or PUCCH. Uplink DMRS may span a frequency range similar to the frequency range associated with the corresponding physical channel. The base station may configure the UE with one or more uplink DMRS configurations. At least one DMRS configuration may support a front-loaded DMRS pattern. A front-loaded DMRS may be mapped to one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRS may be configured to transmit on one or more symbols of PUSCH and / or PUCCH. The base station may semi-statically configure the UE with a number (e.g., maximum number) of front-loaded DMRS symbols for PUSCH and / or PUCCH that the UE may use to schedule single-symbol DMRS and / or dual-symbol DMRS. The NR network may support a common DMRS structure for downlink and uplink (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)), where the DMRS location, DMRS pattern, and / or DMRS scrambling sequence may be the same or different.

[0108] A PUSCH may include one or more layers, and a UE may transmit at least one symbol having DMRS present on one or more layers of the PUSCH. In one embodiment, the upper layers may constitute up to three DMRS relative to the PUSCH.

[0109] Uplink PT-RS (which may be used by base stations for phase tracking and / or phase noise compensation) may or may not be present depending on the UE's RRC configuration. The presence and / or pattern of uplink PT-RS may be configured on a UE-specific basis by a combination of one or more parameters used for other purposes (e.g., modulation and coding scheme (MCS)) that may be indicated by RRC signaling and / or DCI. When configured, the dynamic presence of uplink PT-RS may be associated with one or more DCI parameters, including at least the MCS. A radio network may support multiple uplink PT-RS densities defined in the time / frequency domain. The frequency domain density may be associated with at least one configuration of the scheduled bandwidth, if it exists. A UE may assume the same precoding for DMRS ports and PT-RS ports. The number of PT-RS ports may be less than the number of DMRS ports in the scheduled resources. For example, uplink PT-RS may be limited to the UE's scheduled time / frequency period.

[0110] SRS can be transmitted by the UE to the base station for channel state estimation to support uplink channel-dependent scheduling and / or link fitting. The SRS transmitted by the UE may enable the base station to estimate the uplink channel state at one or more frequencies. The base station's scheduler can use the estimated uplink channel state to allocate one or more resource blocks for uplink push transmissions from the UE. The base station may semi-statically configure the UE with one or more SRS resource sets. In the case of an SRS resource set, the base station may configure the UE with one or more SRS resources. SRS resource set applicability may be configured by higher-layer (e.g., RRC) parameters. For example, when higher-layer parameters indicate beam management, SRS resources within one or more SRS resource sets (e.g., having identical / similar time-domain behavior, periodicity, aperiodicity, and / or similar characteristics) may be transmitted instantaneously (e.g., simultaneously). The UE may transmit one or more SRS resources within an SRS resource set. NR networks may support aperiodic, periodic, and / or semi-persistent SRS transmissions. A UE may transmit SRS resources based on one or more trigger types, which may include higher-layer signaling (e.g., RRC) and / or one or more DCI formats. In one embodiment, at least one DCI format may be used by the UE to select at least one of one or more configured sets of SRS resources. SRS trigger type 0 may refer to an SRS triggered based on higher-layer signaling. SRS trigger type 1 may refer to an SRS triggered based on one or more DCI formats. In one embodiment, when a PUSCH and an SRS are transmitted in the same slot, the UE may be configured to transmit an SRS after the transmission of a PUSCH and the corresponding uplink DMRS.

[0111] A base station may quasi-statistically configure a UE using one or more SRS configuration parameters that indicate at least one of the following: SRS resource configuration identifier, number of SRS ports, time-domain behavior of the SRS resource configuration (e.g., representation of periodic, semi-persistent, or aperiodic SRS), slots, minislots, and / or subframe-level periodicity, offsets for periodic and / or aperiodic SRS resources, number of OFDM symbols in the SRS resource, start OFDM symbol of the SRS resource, SRS bandwidth, frequency-hopping bandwidth, period shift, and / or SRS sequence ID.

[0112] Antenna ports are defined such that the channel on which a symbol on an antenna port is carried can be inferred from the channel on which another symbol on the same antenna port is carried. When a first symbol and a second symbol are transmitted on the same antenna port, the receiver can infer the channel for carrying the second symbol on the antenna port (e.g., fade gain, multipath delay, and / or similar) from the channel for carrying the first symbol on the antenna port. The first and second antenna ports may be said to be quasi-copositional (QCL) if one or more large-scale characteristics of the channel on which the first symbol on the first antenna port is carried can be inferred from the channel on which the second symbol on the second antenna port is carried. One or more large-scale characteristics may include at least one of delay spread, Doppler spread, Doppler shift, mean gain, mean delay, and / or spatial receive (Rx) parameters.

[0113] Channels using beamforming require beam management. Beam management may include beam measurement, beam selection, and beam indexing. A beam may be associated with one or more reference signals. For example, a beam may be identified by one or more beamformed reference signals. The UE may perform downlink beam measurement based on a downlink reference signal (e.g., Channel Status Information Reference Signal (CSI-RS)) and generate a beam measurement report. The UE may perform downlink beam measurement procedures after the RRC connection is set up at the base station.

[0114] Figure 11B shows an example of a Channel State Information Reference Signal (CSI-RS) mapped to time and frequency domains. The square shown in Figure 11B may span resource blocks (RBs) within the cell bandwidth. A base station can transmit one or more RRC messages containing CSI-RS resource configuration parameters that indicate one or more CSI-RSs. One or more of the following parameters can be set by higher-layer signaling (e.g., RRC and / or MAC signaling) for the CSI-RS resource configuration. CSI-RS resource configuration identity, number of CSI-RS ports, CSI-RS configuration (e.g., position of symbols and resource elements (REs) within subframes), CSI-RS subframe configuration (e.g., subframe position, offset, and periodicity of radio frames), CSI-RS power parameters, CSI-RS sequence parameters, code division multiplexing (CDM) type parameters, frequency density, transmission comb, pseudo-collocation (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

[0115] The three beams shown in Figure 11B can be configured for a UE with a UE-specific configuration. Three beams (beam #1, beam #2, and beam #3) are shown in Figure 11B, and more or fewer beams can be configured. Beam #1 can be assigned as CSI-RS1101, which can be transmitted on one or more subcarriers in the RB of a first symbol. Beam #2 can be assigned as CSI-RS1102, which can be transmitted on one or more subcarriers in the RB of a second symbol. Beam #3 can be assigned as CSI-RS1103, which can be transmitted on one or more subcarriers in the RB of a third symbol. By using frequency division multiplexing (FDM), a base station can transmit another CSI-RS associated with a beam of another UE using other subcarriers in the same RB (e.g., those not used to transmit CSI-RS1101). By using time-domain multiplexing (TDM), the beam used for a UE can be configured so that the UE's beam uses symbols from the beams of other UEs.

[0116] The CSI-RS (e.g., CSI-RS1101, 1102, 1103) shown in Figure 11B may be transmitted by a base station and used by a UE for one or more measurements. For example, a UE may measure the reference signal received power (RSRP) of a configured CSI-RS resource. The base station may configure a UE with a reporting configuration, and the UE may report the RSRP measurement to the network (e.g., via one or more base stations) based on the reporting configuration. In one embodiment, the base station may determine one or more transmission configuration index (TCI) states, including several reference signals, based on the reported measurement results. In one embodiment, the base station may indicate one or more TCI states to the UE (e.g., via RRC signaling, MAC CE, and / or DCI). The UE may receive a downlink transmission having a received (Rx) beam determined based on one or more TCI states. In one embodiment, the UE may or may not have beam correspondence capability. If the UE has beam correspondence capability, the UE may determine the spatial domain filter of the transmission (Tx) beam based on the spatial domain filter of the corresponding Rx beam. If the UE does not have beam correspondence capability, the UE may perform an uplink beam selection procedure to determine the spatial domain filter of the Tx beam. The UE may perform an uplink beam selection procedure based on one or more sounding reference signal (SRS) resources configured to the UE by the base station. The base station may select and indicate an uplink beam for the UE based on measurements of one or more SRS resources transmitted by the UE.

[0117] In beam management procedures, the UE may evaluate (e.g., measure) the channel quality of a beam pair link, including one or more beam pair links, a transmitted beam transmitted by a base station, and a received beam received by the UE. Based on the evaluation, the UE may transmit a beam measurement report indicating one or more beam pair quality parameters, including, for example, one or more beam identities (e.g., beam index, reference signal index, or similar), RSRP, precoding matrix indicator (PMI), channel quality indicator (CQI), and / or rank indicator (RI).

[0118] Figure 12A shows examples of three downlink beam management procedures, namely P1, P2, and P3. Procedure P1 may enable UE measurements on the transmission (Tx) beams of a transmission receiving point (TRP) (or multiple TRPs) to support the selection of one or more base station Tx beams and / or UE Rx beams (shown as ellipses in the top and bottom rows of P1, respectively). Beamforming at a TRP may include a Tx beam sweep of the beam set (shown as ellipses rotating counterclockwise, indicated by dashed arrows, in the top rows of P1 and P2). Beamforming at a UE may include an Rx beam sweep for the beam set (shown as ellipses rotating clockwise, indicated by dashed arrows, in the bottom rows of P1 and P3). Procedure P2 may be used to enable UE measurements on the Tx beams of a TRP (shown as ellipses rotating counterclockwise, indicated by dashed arrows, in the top row of P2). The UE and / or base station may perform step P2 using a smaller set of beams than those used in step P1, or using a narrower beam than those used in step P1. This may be referred to as beam refinement. The UE may perform step P3 for Rx beam determination by using the same Tx beam at the base station and sweeping the Rx beam at the UE.

[0119] Figure 12B shows examples of three uplink beam management procedures, namely U1, U2, and U3. Procedure U1 may be used to allow a base station to perform measurements on a UE's Tx beam to support the selection of one or more UE Tx beams and / or base station Rx beams (shown as ellipses in the top and bottom rows of U1, respectively). Beamforming at the UE may include, for example, a Tx beam sweep from a set of beams (shown as ellipses rotating clockwise, indicated by dashed arrows in the bottom rows of U1 and U3). Beamforming at the base station may include, for example, an Rx beam sweep from a set of beams (shown as ellipses rotating counterclockwise, indicated by dashed arrows in the top rows of U1 and U2). Procedure U2 may be used to allow a base station to adjust its Rx beam when the UE is using a fixed Tx beam. The UE and / or base station may perform procedure U2 using a smaller set of beams than used in procedure P1, or using a narrower beam than the beam used in procedure P1. This may be referred to as beam refinement. The UE may perform procedure U3 to adjust its Tx beam when the base station is using a fixed Rx beam.

[0120] Based on the detection of a beam failure, the UE may initiate a beam failure recovery (BFR) procedure. Based on the initiation of the BFR procedure, the UE may transmit a BFR request (e.g., preamble, UCI, SR, MAC CE, and / or similar). The UE may detect a beam failure based on the determination that the quality of the beam pair link of the associated control channel is unsatisfactory (e.g., having an error rate higher than the error rate threshold, a received signal power lower than the received signal power threshold, a timer expiring, and / or similar).

[0121] A UE may measure the quality of a beampair link using one or more reference signals (RS) including one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more demodulated reference signals (DMRS). The quality of a beampair link may be based on one or more of the following: block error rate (BLER), RSRP value, signal-to-interference plus noise ratio (SINR) value, reference signal reception quality (RSRQ) value, and / or CSI values ​​measured at the RS resources. A base station may indicate that an RS resource is quasi-coordinated (QCLed) with one or more DMRS of a channel (e.g., control channel, shared data channel, and / or similar). An RS resource and one or more DMRS of a channel may be QCLed if the channel characteristics from the transmission to the UE via the RS resources (e.g., Doppler shift, Doppler spread, mean delay, delay spread, spatial Rx parameter, fade, and / or similar) are similar to or identical to the channel characteristics from the transmission to the UE via the channel.

[0122] The network (e.g., the network's gNB and / or ng-eNB) and / or UE may initiate a random access procedure. A UE in the RRC-IDLE state and / or the RRC-INACTIVE state may initiate a random access procedure to request network connection setup. A UE may initiate a random access procedure from the RRC-CONNECTED state. A UE may initiate a random access procedure to request uplink resources (e.g., for uplink transmission of SR when no PUCCH resources are available) and / or obtain uplink timing (e.g., if the uplink synchronization state is not synchronized). A UE may initiate a random access procedure to request one or more System Information Blocks (SIBs) (e.g., SIB2, SIB3, and / or other system information such as similar ones). A UE may initiate a random access procedure for beam failure recovery requests. The network may initiate a random access procedure to establish time alignment for handover and / or SCell addition.

[0123] Figure 13A illustrates a four-step competition-based random access procedure. Before the procedure begins, the base station may transmit a configuration message 1310 to the UE. The procedure shown in Figure 13A involves the transmission of four messages: Msg1 1311, Msg2 1312, Msg3 1313, and Msg4 1314. Msg1 1311 may contain and / or be referred to as a preamble (or random access preamble). Msg2 1312 may be referred to as a random access response (RAR) and / or as a random access response (RAR).

[0124] Configuration message 1310 may be transmitted, for example, using one or more RRC messages. One or more RRC messages may indicate one or more random access channel (RACH) parameters to the UE. One or more RACH parameters may include at least one of the following: one or more general parameters for random access procedures (e.g., RACH-configGeneral), cell-specific parameters (e.g., RACH-ConfigCommon), and / or dedicated parameters (e.g., RACH-configDedicated). The base station may broadcast or multicast one or more RRC messages to one or more UEs. One or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to the UE in the RRC_CONNECTED state and / or RRC_INACTIVE state). Based on one or more RACH parameters, the UE may determine the time-frequency resources and / or uplink transmission power for the transmission of Msg1 1311 and / or Msg3 1313. Based on one or more RACH parameters, the UE may determine the receive timing and downlink channel for receiving Msg2 1312 and Msg4 1314.

[0125] One or more RACH parameters provided in configuration message 1310 may indicate one or more physical RACH (PRACH) opportunities available for transmission of Msg1 1311. One or more PRACH opportunities may be predefined. One or more RACH parameters may indicate one or more available sets of one or more PRACH opportunities (e.g., prach-ConfigIndex). One or more RACH parameters may indicate an association between (a) one or more PRACH opportunities and (b) one or more reference signals. One or more RACH parameters may indicate an association between (a) one or more preambles and (b) one or more reference signals. One or more reference signals may be SS / PBCH blocks and / or CSI-RS. For example, one or more RACH parameters may indicate the number of SS / PBCH blocks mapped to PRACH opportunities and / or the number of preambles mapped to SS / PBCH blocks.

[0126] One or more RACH parameters provided in configuration message 1310 can be used to determine the uplink transmission power of Msg1 1311 and / or Msg3 1313. For example, one or more RACH parameters may indicate reference power for preamble transmission (e.g., received target power and / or initial power for preamble transmission). There may be one or more power offsets indicated by one or more RACH parameters. For example, one or more RACH parameters may indicate a power ramping step, a power offset between SSB and CSI-RS, a power offset between transmissions of Msg1 1311 and Msg3 1313, and / or a power offset value between preamble groups. One or more RACH parameters may indicate one or more thresholds for the UE to determine at least one reference signal (e.g., SSB and / or CSI-RS) and / or uplink carriers (e.g., normal uplink (NUL) carrier and / or complementary uplink (SUL) carrier).

[0127] Msg1 1311 may include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions). RRC messages may be used to constitute one or more preamble groups (e.g., group A and / or group B). A preamble group may include one or more preambles. The UE may determine a preamble group based on path loss measurements and / or the size of Msg3 1313. The UE may measure the RSRP of one or more reference signals (e.g., SSB and / or CSI-RS) and determine at least one reference signal that has an RSRP exceeding an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). The UE may, for example, select at least one preamble to be associated with one or more reference signals and / or a selected preamble group if the association between one or more preambles and at least one reference signal is constituted by an RRC message.

[0128] The UE may determine the preamble based on one or more RACH parameters provided in configuration message 1310. For example, the UE may determine the preamble based on path loss measurements, RSRP measurements, and / or the size of Msg3 1313. As another example, one or more RACH parameters may indicate the preamble format, the maximum number of preamble transmissions, and / or one or more thresholds for determining one or more preamble groups (e.g., group A and group B). The base station may use one or more RACH parameters to configure the UE with associations between one or more preambles and one or more reference signals (e.g., SSB and / or CSI-RS). If associations are configured, the UE may determine, based on the associations, to include the preamble in Msg1 1311. Msg1 1311 may be transmitted to the base station via one or more PRACH opportunities. The UE may use one or more reference signals (e.g., SSB and / or CSI-RS) for preamble selection and PRACH opportunity determination. One or more RACH parameters (e.g., ra-ssb-OccasionMskIndex and / or ra-OccasionList) may indicate an association between a PRACH opportunity and one or more reference signals.

[0129] The UE may perform a preamble retransmission if no response is received after the preamble transmission. The UE may increase the uplink transmission power for the preamble retransmission. The UE may select an initial preamble transmission power based on path loss measurements and / or target received preamble power configured by the network. The UE may determine to retransmit the preamble and ramp up the uplink transmission power. The UE may receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMPING_STEP) indicating the ramping step of the preamble retransmission. The ramping step may be the amount of incremental increase in uplink transmission power for the retransmission. The UE may ramp up the uplink transmission power if it determines that the reference signal (e.g., SSB and / or CSI-RS) is the same as the previous preamble transmission. The UE may count the number of preamble transmissions and / or retransmissions (e.g., PREAMBLE_TRANSMISSION_COUNTER). For example, the UE may determine that the random access procedure failed to complete if the number of preamble transmissions exceeds a threshold defined by one or more RACH parameters (e.g., preambleTransMax).

[0130] Msg2 1312 received by the UE may contain RARs. In some scenarios, Msg2 1312 may contain multiple RARs corresponding to multiple UEs. Msg2 1312 may be received after or in response to the transmission of Msg1 1311. Msg2 1312 may be scheduled on the DL-SCH and displayed on the PDCCH using a Random Access RNTI (RA-RNTI). Msg2 1312 may indicate that Msg1 1311 has been received by the base station. Msg2 1312 may contain time alignment commands that the UE can use to adjust the transmission timing of the UE, scheduling permission for the transmission of Msg3 1313, and / or a temporary cell RNTI (TC-RNTI). After transmitting the preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor the PDCCH of Msg2 1312. A UE may determine when to start a time window based on the PRACH opportunity that the UE uses to transmit the preamble. For example, a UE may start a time window after one or more symbols of the last symbol of the preamble (e.g., on the first PDCCH opportunity from the end of preamble transmission). One or more symbols may be determined based on numerology. PDCCH may be in a common lookup space composed of RRC messages (e.g., a Type1-PDCCH common lookup space). A UE may identify a RAR based on a Radio Network Temporary Identifier (RNTI). An RNTI may be used in response to one or more events that initiate a random access procedure. A UE may use a Random Access RNTI (RA-RNTI). An RA-RNTI may be associated with a PRACH opportunity in which the UE transmits the preamble. For example, a UE may determine an RA-RNTI based on the OFDM symbol index, slot index, frequency domain index, and / or the UL carrier indicator of the PRACH opportunity. One embodiment of an RA-RNTI may be as follows: RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id s_id can be the index of the first OFDM symbol of the PRACH opportunity (e.g., 0 ≤ s_id < 14), t_id can be the index of the first slot of the PRACH opportunity in the system frame (e.g., 0 ≤ t_id < 80), f_id can be the index of the PRACH opportunity in the frequency domain (e.g., 0 ≤ f_id < 8), and ul_carrier_id can be the UL carrier used for preamble transmission (e.g., 0 for a NUL carrier, 1 for a SUL carrier). A UE may transmit Msg3 1313 in response to the successful reception of Msg2 1312 (for example, using the resources identified in Msg2 1312). Msg3 1313 may be used for conflict resolution in a conflict-based random access procedure, for example, as shown in Figure 13A. In some scenarios, multiple UEs may transmit the same preamble to a base station, and the base station may provide a RAR corresponding to the UEs. If multiple UEs interpret the RAR as corresponding to themselves, a mismatch may occur. Conflict resolution (e.g., the use of Msg3 1313 and Msg4 1314) can be used to increase the likelihood that a UE will not mistakenly use the identity of another UE. To implement conflict resolution, a UE may include a device identifier in Msg3 1313 (e.g., C-RNTI, if assigned, TC-RNTI included in Msg2 1312, and / or any other appropriate identifier).

[0131] Msg4 1314 may be received after or in response to the transmission of Msg3 1313. If a C-RNTI was included in Msg3 1313, the base station uses the C-RNTI to address the UE on the PDCCH. If the UE's unique C-RNTI is found on the PDCCH, the random access procedure is determined to have completed successfully. If a TC-RNTI is included in Msg3 1313 (e.g., if the UE is in the RRC_IDLE state or otherwise not connected to the base station), Msg4 1314 is received using the DL-SCH associated with the TC-RNTI. If the MAC PDU is successfully decoded and the MAC PDU matches the CCCH SDU transmitted (e.g., transmitted) in Msg3 1313, or otherwise contains the corresponding UE conflict resolution identity MAC CE, the UE may determine that conflict resolution was successful, and / or the UE may determine that the random access procedure has completed successfully.

[0132] A UE may consist of a complementary uplink (SUL) carrier and a non-ultra-uplink (NUL) carrier. Initial access (e.g., random access procedures) may be supported on the uplink carrier. For example, a base station may configure a UE with two separate RACH configurations, namely one for SUL carriers and one for NUL carriers. In the case of random access within a cell configured with SUL carriers, the network may indicate which carrier (NUL or SUL) to use. A UE may determine a SUL carrier, for example, if the measured quality of one or more reference signals is below the broadcast threshold. Uplink transmission of a random access procedure (e.g., Msg1 1311 and / or Msg3 1313) may remain on the selected carrier. In one or more instances, a UE may switch uplink carriers during a random access procedure (e.g., between Msg1 1311 and Msg3 1313). For example, the UE may determine and / or switch the uplink carriers for Msg1 1311 and / or Msg3 1313 based on a channel clear assessment (e.g., listen before talk).

[0133] Figure 13B illustrates a two-step contention-free random access procedure. Similar to the four-step contention-based random access procedure shown in Figure 13A, the base station may transmit a configuration message 1320 to the UE before the procedure begins. Configuration message 1320 may be similar in some respects to configuration message 1310. Figure 13B includes the transmission of two messages, namely Msg1 1321 and Msg2 1322. Msg1 1321 and Msg2 1322 may be similar in some respects to Msg1 1311 and Msg2 1312 shown in Figure 13A, respectively. As can be seen from Figures 13A and 13B, a contention-free random access procedure may not include messages similar to Msg3 1313 and / or Msg4 1314.

[0134] The uncontested random access procedure shown in Figure 13B may be initiated for beam failure recovery, other SI requests, SCell additions, and / or handovers. For example, the base station may indicate or assign the preamble to be used for Msg1 1321 to the UE. The UE may receive an index of the preamble (e.g., ra-PreambleIndex) from the base station via the PDCCH and / or RRC.

[0135] After transmitting the preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor the RAR's PDCCH. In the case of a beam failure recovery request, the base station may configure the UE with a separate time window and / or separate PDCCH within the search space indicated by the RRC message (e.g., recoverySearchSpaceId). The UE may monitor PDCCH transmissions destined for Cell RNTI (C-RNTI) in the search space. In the uncontested random access procedure shown in Figure 13B, the UE may determine that the random access procedure has completed successfully after transmitting Msg1 1321 and receiving the corresponding Msg2 1322, or in response to it. The UE may determine that the random access procedure has completed successfully, for example, if the PDCCH transmission is addressed to C-RNTI. The UE may determine that the random access procedure has completed successfully, for example, if the UE receives a RAR containing a preamble identifier corresponding to the preamble transmitted by the UE, and / or if the RAR contains a MAC sub-PDU containing the preamble identifier. The UE may determine the response as an indicator of acknowledgment of the response to the SI request.

[0136] Figure 13C illustrates another two-step random access procedure. Similar to the random access procedures shown in Figures 13A and 13B, the base station may transmit a configuration message 1330 to the UE before the procedure begins. The configuration message 1330 may be similar in some respects to configuration messages 1310 and / or 1320. Figure 13C includes the transmission of two messages, namely Msg A 1331 and Msg B 1332.

[0137] Msg A 1331 may be transmitted by the UE via uplink transmission. Msg A 1331 may include one or more transmissions of the preamble 1341 and / or one or more transmissions of the transport block 1342. The transport block 1342 may include content similar to and / or equivalent to the content of Msg 3 1313 shown in Figure 13A. The transport block 1342 may include UCI (e.g., SR, HARQ ACK / NACK, and / or similar). The UE may receive Msg B 1332 after transmitting Msg A 1331 or in response to it. Msg B 1332 may include content similar to and / or equivalent to the content of Msg 2 1312 (e.g., RAR) shown in Figures 13A and 13B, and / or Msg 4 1314 shown in Figure 13A.

[0138] The UE may initiate the two-step random access procedure shown in Figure 13C for licensed and / or unlicensed spectra. The UE may determine whether to initiate the two-step random access procedure based on one or more factors. One or more factors may be the radio access technology in use (e.g., LTE, NR, and / or similar), whether the UE has a valid TA, cell size, the UE's RRC status, the spectrum type (e.g., licensed vs. unlicensed), and / or any other preferred factors.

[0139] The UE may determine the radio resources and / or uplink transmission power for the transport block 1342 contained in the preamble 1341 and / or Msg A 1331 based on the two-step RACH parameters contained in configuration message 1330. The RACH parameters may indicate the modulation and coding scheme (MCS), time-frequency resources, and / or power control for the preamble 1341 and / or transport block 1342. The time-frequency resources for transmission of the preamble 1341 (e.g., PRACH) and the time-frequency resources for transmission of the transport block 1342 (e.g., PUSCH) may be multiplexed using FDM, TDM, and / or CDM. The RACH parameters may enable the UE to determine the receive timing and downlink channel for monitoring and / or receiving Msg B 1332.

[0140] Transport block 1342 may include data (e.g., latency-sensitive data), a UE identifier, security information, and / or device information (e.g., International Mobile Subscriber Identity (IMSI)). The base station may transmit Msg B 1332 in response to Msg A 1331. Msg B 1332 may include at least one of the following: a preamble identifier, a timing advance command, a power control command, an uplink authorization (e.g., radio resource allocation and / or MCS), a UE identifier for conflict resolution, and / or an RNTI (e.g., C-RNTI or TC-RNTI). The UE may determine that it has successfully completed the two-step random access procedure if the preamble identifier in Msg B 1332 matches the preamble transmitted by the UE, and / or the UE identifier in Msg B 1332 matches the UE identifier in Msg A 1331 (e.g., transport block 1342).

[0141] UEs and base stations may exchange control signaling. Control signaling may be referred to as L1 / L2 control signaling and may originate from the PHY layer (e.g., layer 1) and / or the MAC layer (e.g., layer 2). Control signaling may include downlink control signaling transmitted from the base station to the UE and / or uplink control signaling transmitted from the UE to the base station.

[0142] Downlink control signaling may include downlink scheduling assignments, uplink scheduling authorizations indicating uplink radio resources and / or transport formats, slot format information, preemption indicators, power control commands, and / or other optional signaling. A UE may receive downlink control signaling in a payload transmitted by a base station over a physical downlink control channel (PDCCH). The payload transmitted over the PDCCH may be referred to as downlink control information (DCI). In some scenarios, the PDCCH may be a group-common PDCCH (GC-PDCCH) common to a group of UEs.

[0143] A base station may add one or more cyclic redundancy check (CRC) parity bits to the DCI to facilitate the detection of transmission errors. When the DCI is intended for a UE (or group of UEs), the base station may scramble the CRC parity bits with the UE identifier (or identifier of the group of UEs). Scrambling the CRC parity bits with an identifier may involve Modulo-2 addition (or exclusive OR operation) of the identifier value and the CRC parity bits. The identifier may include a 16-bit Radio Network Temporary Identifier (RNTI).

[0144] DCIs can be used for different purposes. The purpose may be indicated by the type of RNTI used to scramble the CRC parity bits. For example, a DCI with CRC parity bits scrambled with a paging RNTI (P-RNTI) may indicate paging information and / or system information change notifications. P-RNTI can be predefined as "FFFE" in hexadecimal. A DCI with CRC parity bits scrambled with a system information RNTI (SI-RNTI) may indicate broadcast transmission of system information. SI-RNTI can be predefined as "FFFF" in hexadecimal. A DCI with CRC parity bits scrambled with a random access RNTI (RA-RNTI) may indicate a random access response (RAR). A DCI with CRC parity bits scrambled with a cell RNTI (C-RNTI) may indicate unicast transmission of dynamic scheduling and / or triggers for random access in PDCCH sequences. A DCI with a scrambled CRC parity bit in a temporary cell RNTI (TC-RNTI) may exhibit conflict resolution (e.g., Msg3 similar to Msg3 1313 shown in Figure 13A). Other RNTI encodings configured in the UE by the base station include Configured Scheduling RNTI (CS-RNTI), Transmit Power Control-PUCCH RNTI (TPC-PUCCH-RNTI), Transmit Power Control-PUSCH RNTI (TPC-PUSCH-RNTI), Transmit Power Control-SRS RNTI (TPC-SRS-RNTI), Interruption RNTI (INT-RNTI), Slot Format Indication RNTI (SFI-RNTI), Semi-Persistent CSI RNTI (SP-CSI-RNTI), Modulation and Coding Scheme Cell RNTI (MCS-C-RNTI), and / or similar.

[0145] Depending on the purpose and / or content of the DCI, the base station may transmit the DCI in one or more DCI formats. For example, DCI format 0_0 can be used for scheduling pushes within a cell. DCI format 0_0 may be a fallback DCI format (e.g., with a compact DCI payload). DCI format 0_1 ​​may be used for scheduling pushes within a cell (e.g., with a larger DCI payload than DCI format 0_0). DCI format 1_0 may be used for scheduling PDSCHs within a cell. DCI format 1_0 may be a fallback DCI format (e.g., with a compact DCI payload). DCI format 1_1 may be used for scheduling PDSCHs within a cell (e.g., with a larger DCI payload than DCI format 1_0). DCI format 2_0 may be used to provide a slot format index to a group of UEs. DCI format 2_1 may be used to inform a group of UEs of physical resource blocks and / or OFDM symbols that the UEs assume are not intended for transmission to the UEs. DCI format 2_2 may be used for transmitting Transmission Power Control (TPC) commands for PUCCH or PUSCH. DCI format 2_3 may be used for transmitting a group of TPC commands for SRS transmission by one or more UEs. DCI formats for new features may be defined in future releases. DCI formats may have different DCI sizes or may share the same DCI size.

[0146] After scrambling the DCI with RNTI, the base station may process the DCI using channel coding (e.g., polar coding), rate matching, scrambling, and / or QPSK modulation. The base station may map the coded and modulated DCI onto resource elements used and / or configured for the PDCCH. Based on the DCI payload size and / or base station coverage, the base station may transmit the DCI over a PDCCH occupying several consecutive control channel elements (CCEs). The number of consecutive CCEs (referred to as the aggregation level) can be 1, 2, 4, 8, 16, and / or any other suitable number. A CCE may contain a number of resource element groups (REGs) (e.g., 6). A REG may contain resource blocks in OFDM symbols. Mapping the coded and modulated DCI onto resource elements may be based on mappings of CCEs and REGs (e.g., CCE-REG mappings).

[0147] Figure 14A shows one embodiment of a CORESET configuration for a bandwidth portion. A base station may transmit DCI via PDCCH on one or more control resource sets (CORESETs). A CORESET may contain time-frequency resources that the UE attempts to decode the DCI using one or more lookup spaces. A base station may configure a CORESET within a time-frequency domain. In the example in Figure 14A, the first CORESET 1401 and the second CORESET 1402 occur at the first symbol in the slot. The first CORESET 1401 overlaps with the second CORESET 1402 in the frequency domain. The third CORESET 1403 occurs at the third symbol in the slot. The fourth CORESET 1404 occurs at the seventh symbol in the slot. A CORESET may have a different number of resource blocks in the frequency domain.

[0148] Figure 14B shows one embodiment of CCE-REG mapping for DCI transmission on CORESET and PDCCH processing. CCE-REG mapping can be interleaved mapping (e.g., for the purpose of providing frequency diversity) or non-interleaved mapping (e.g., for the purpose of facilitating interference adjustment and / or frequency-selective transmission of control channels). A base station may perform different or the same CCE-REG mapping on different CORESETs. A CORESET may be associated with CCE-REG mapping by RRC configuration. A CORESET may consist of antenna port ready co-position (QCL) parameters. The antenna port QCL parameters may indicate QCL information for demodulated reference signals (DMRS) for PDCCH reception within the CORESET.

[0149] A base station may transmit an RRC message to the UE containing configuration parameters for one or more CORESETs and one or more search space sets. The configuration parameters may indicate the relationship between the search space set and the CORESET. A search space set may contain a set of PDCCH candidates formed by CCEs at a given aggregation level. The configuration parameters may indicate the number of PDCCH candidates monitored per aggregation level, the PDCCH monitoring period and PDCCH monitoring pattern, one or more DCI formats monitored by the UE, and / or whether the search space set is a common search space set or a UE-specific search space set. The set of CCEs in a common search space set may be predefined and known to the UE. The set of CCEs in a UE-specific search space set may be configured based on the UE's identity (e.g., C-RNTI).

[0150] As shown in Figure 14B, the UE may determine the time-frequency resources of the CORESET based on the RRC message. The UE may determine the CCE~REG mapping to the CORESET (e.g., interleaved or non-interleaved, and / or mapping parameters) based on the CORESET configuration parameters. The UE may determine the number of search space sets configured on the CORESET (e.g., up to 10) based on the RRC message. The UE may monitor a set of PDCCH candidates according to the configuration parameters of the search space set. The UE may monitor a set of PDCCH candidates in one or more CORESETs to detect one or more DCIs. Monitoring may include decoding one or more PDCCH candidates from the set of PDCCH candidates according to the monitored DCI format. Monitoring may include decoding the DCI content of one or more PDCCH candidates having possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., the number of CCEs in a common search space, the number of PDCCH candidates, and / or the number of PDCCH candidates in a UE-specific search space), and possible (or configured) DCI formats. Decoding may be referred to as blind decoding. The UE may determine a valid DCI for the UE in response to a CRC check (e.g., a scramble bit against the CRC parity bit of a DCI that matches an RNTI value). The UE may process the information contained in the DCI (e.g., scheduling assignments, uplink permission, power control, slot format indicators, downlink preemption, and / or similar).

[0151] The UE may transmit uplink control signaling (e.g., uplink control information (UCI)) to the base station. Uplink control signaling may include Hybrid Automatic Repeat Request (HARQ) acknowledgments for received DL-SCH transport blocks. After receiving a DL-SCH transport block, the UE may transmit HARQ acknowledgments. Uplink control signaling may include channel status information (CSI) indicating the channel quality of the physical downlink channel. The UE may transmit CSI to the base station. Based on the received CSI, the base station may determine transmission format parameters for downlink transmission (e.g., multi-antenna and beamforming schemes). Uplink control signaling may include scheduling requests (SRs). The UE may transmit SRs indicating that uplink data is available for transmission to the base station. The UE may transmit UCI (e.g., HARQ acknowledgments (HARQ-ACK), CSI reports, SRs, etc.) over the physical uplink control channel (PUCCH) or physical uplink shared channel (PUSCH). The UE may transmit uplink control signaling via PUCCH using one of several PUCCH formats.

[0152] Five PUCCH formats may exist, and a UE can determine the PUCCH format based on the size of the UCI (e.g., the number of uplink symbols and UCI bits in the UCI transmission). PUCCH format 0 may have the length of one or two OFDM symbols and may contain two or fewer bits. A UE may use PUCCH format 0 to transmit a UCI in a PUCCH resource if the transmission exceeds one or two symbols and the number of HARQ-ACK information bits with positive or negative SR (HARQ-ACK / SR bits) is one or two. PUCCH format 1 may occupy a number between 4 and 14 OFDM symbols and may contain two or fewer bits. A UE may use PUCCH format 1 if the transmission consists of four or more symbols and the number of HARQ-ACK / SR bits is one or two. PUCCH format 2 may occupy one or two OFDM symbols and may contain more than two bits. A UE may use PUCCH format 2 if the transmission exceeds one or two symbols and the number of UCI bits is two or more. PUCCH format 3 may occupy a number between 4 and 14 OFDM symbols and may include more than 2 bits. A UE may use PUCCH format 3 if the transmission has four or more symbols, the number of UCI bits is two or more, and the PUCCH resource does not contain orthogonal cover codes. PUCCH format 4 may occupy a number between 4 and 14 OFDM symbols and may include more than 2 bits. A UE may use PUCCH format 4 if the transmission has four or more symbols, the number of UCI bits is two or more, and the PUCCH resource contains orthogonal cover codes.

[0153] A base station may transmit configuration parameters for multiple PUCCH resource sets to a UE, for example, using RRC messages. Multiple PUCCH resource sets (e.g., up to four sets) may be configured on a cell's uplink BWP. A PUCCH resource set may consist of multiple PUCCH resources, each having a PUCCH resource identified by a PUCCH resource set index, a PUCCH resource identifier (e.g., pucch-Resourceid), and / or the number of UCI information bits (e.g., maximum number) that the UE may transmit using one of the multiple PUCCH resources in the PUCCH resource set. When multiple PUCCH resource sets are configured, the UE may select one of the multiple PUCCH resource sets based on the total bit length of the UCI information bits (e.g., HARQ-ACK, SR, and / or CSI). If the total bit length of the UCI information bits is 2 or less, the UE may select the first PUCCH resource set whose index is equal to "0". If the total bit length of the UCI information bits is greater than 2 and less than or equal to the first configuration value, the UE may select a second PUCCH resource set with a PUCCH resource set index equal to "1". If the total bit length of the UCI information bits is greater than the first configuration value and less than or equal to the second configuration value, the UE may select a third PUCCH resource set with a PUCCH resource set index equal to "2". If the total bit length of the UCI information bits is greater than the second configuration value and less than or equal to the third value (e.g., 1406), the UE may select a fourth PUCCH resource set with a PUCCH resource set index equal to "3".

[0154] After determining a PUCCH resource set from multiple PUCCH resource sets, the UE may determine a PUCCH resource from the PUCCH resource set for UCI (HARQ-ACK, CSI, and / or SR) transmission. The UE may determine a PUCCH resource based on the PUCCH resource indicator in the DCI (e.g., DCI format 1_0 or DCI format 1_1) received on the PDCCH. The 3-bit PUCCH resource indicator in the DCI may indicate one of the eight PUCCH resources in the PUCCH resource set. Based on the PUCCH resource indicator, the UE may transmit UCI (HARQ-ACK, CSI, and / or SR) using the PUCCH resource indicated by the PUCCH resource indicator in the DCI.

[0155] Figure 15 shows one embodiment of a wireless device 1502 communicating with a base station 1504 according to an embodiment of the present disclosure. The wireless device 1502 and base station 1504 may be part of a mobile communication network, such as the mobile communication network 100 shown in Figure 1A, the mobile communication network 150 shown in Figure 1B, or other communication networks. Only one wireless device 1502 and one base station 1504 are shown in Figure 15. However, it will be understood that a mobile communication network may include multiple UEs and / or multiple base stations having the same or similar configuration as shown in Figure 15.

[0156] Base station 1504 may connect radio device 1502 to a core network (not shown) via radio communication over an air interface (or radio interface) 1506. The communication direction from base station 1504 to radio device 1502 over air interface 1506 is known as the downlink, and the communication direction from radio device 1502 to base station 1504 over air interface is known as the uplink. Downlink transmissions may be isolated from uplink transmissions using FDD, TDD, and / or some combination of two redundancy techniques.

[0157] In the downlink, data transmitted from base station 1504 to radio device 1502 may be provided to processing system 1508 of base station 1504. The data may be provided to processing system 1508 by, for example, the core network. In the uplink, data transmitted from radio device 1502 to base station 1504 may be provided to processing system 1518 of radio device 1502. Processing systems 1508 and 1518 may process the data for transmission by implementing OSI functions of layers 3 and 2. Layer 2 may include, for example, the SDAP layer, PDCP layer, RLC layer, and MAC layer with respect to Figures 2A, 2B, 3, and 4A. Layer 3 may include the RRC layer with respect to Figure 2B.

[0158] Data that has been processed by processing system 1508 and is to be transmitted to radio device 1502 may be provided to transmission processing system 1510 of base station 1504. Similarly, data that has been processed by processing system 1518 and is to be transmitted to base station 1504 may be provided to transmission processing system 1520 of radio device 1502. Transmission processing systems 1510 and 1520 may implement the OSI functions of layer 1. Layer 1 may include a PHY layer with respect to Figures 2A, 2B, 3, and 4A. For transmission processing, the PHY layer may perform, for example, forward error correction coding of the transport channel, interleaving, rate matching, mapping of the transport channel to a physical channel, modulation of the physical channel, multiple input multiple output (MIMO) or multi-antenna processing, and / or similar.

[0159] At base station 1504, receiving processing system 1512 may receive uplink transmissions from radio device 1502. At radio device 1502, receiving processing system 1522 may receive downlink transmissions from base station 1504. Receiving processing systems 1512 and 1522 may implement OSI functions of layer 1. Layer 1 may include a PHY layer with respect to Figures 2A, 2B, 3, and 4A. In the case of receiving processing, the PHY layer may perform, for example, error detection, forward error correction decoding, deinterleaving, demapping of transport channels to physical channels, demodulation of physical channels, MIMO or multi-antenna processing, and / or similar.

[0160] As shown in Figure 15, the wireless device 1502 and the base station 1504 may include multiple antennas. Multiple antennas may be used to implement one or more MIMO or multi-antenna techniques such as spatial multiplexing (e.g., single-user MIMO or multi-user MIMO), transmission / reception diversity, and / or beamforming. In other examples, the wireless device 1502 and / or the base station 1504 may have a single antenna.

[0161] Processing systems 1508 and 1518 may be associated with memories 1514 and 1524, respectively. Memories 1514 and 1524 (e.g., one or more non-temporary computer-readable media) may store computer program instructions or code that can be executed by processing systems 1508 and / or 1518 to perform one or more functions considered in this application. Although not shown in Figure 15, transmission processing systems 1510, 1520, reception processing system 1512, and / or reception processing system 1522 may be coupled to memories (e.g., one or more non-temporary computer-readable media) that store computer program instructions or code that can be executed to perform one or more of their respective functions.

[0162] Processing system 1508 and / or processing system 1518 may include one or more controllers and / or one or more processors. One or more controllers and / or one or more processors may include, for example, general-purpose processors, digital signal processors (DSPs), microcontrollers, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) and / or other programmable logic devices, discrete gates and / or transistor logic, discrete hardware components, onboard units, or any combination thereof. Processing system 1508 and / or processing system 1518 may perform at least one of signal coding / processing, data processing, power control, input / output processing, and / or any other functions that may enable the wireless device 1502 and base station 1504 to operate in a wireless environment.

[0163] Processing system 1508 and / or processing system 1518 may be connected to one or more peripheral devices 1516 and / or one or more peripheral devices 1526, respectively. One or more peripheral devices 1516 and one or more peripheral devices 1526 may include software and / or hardware that provide features and / or functions, such as speakers, microphones, keypads, displays, touchpads, power supplies, satellite transceivers, Universal Serial-Wire Universal Bus (USB) ports, hands-free headsets, frequency modulation (FM) radio units, media players, internet browsers, electronic control units (e.g., for vehicles), and / or one or more sensors (e.g., accelerometers, gyroscopes, temperature sensors, radar sensors, lidar sensors, ultrasonic sensors, light sensors, cameras, and / or similar). Processing system 1508 and / or processing system 1518 may receive user input data from one or more peripheral devices 1516 and / or one or more peripheral devices 1526 and / or provide user output data. The processing system 1518 within the wireless device 1502 may be configured to receive power from a power source and / or distribute power to other components within the wireless device 1502. The power source may include one or more power sources, such as a battery, a solar cell, a fuel cell, or any combination thereof. The processing system 1508 and / or the processing system 1518 may be connected to GPS chipsets 1517 and 1527, respectively. The GPS chipsets 1517 and 1527 may be configured to provide geographic location information for the wireless device 1502 and the base station 1504, respectively.

[0164] Figure 16A shows an exemplary structure for uplink transmission. The baseband signal representing the physical uplink shared channel may perform one or more functions. These one or more functions may include at least one of the following: scrambling, modulation of scrambled bits to generate complex-valued symbols, mapping of complex-valued modulated symbols onto one or more transmission layers, conversion precoding to generate complex-valued symbols, precoding of complex-valued symbols, mapping of precoded complex-valued symbols to resource elements, generation of complex-valued time-domain single-carrier frequency division multiplexing access (SC-FDMA) or CP-OFDM signals to antenna ports, and / or similar. In one embodiment, an SC-FDMA signal for uplink transmission may be generated when conversion precoding is enabled. In one embodiment, a CP-OFDM signal for uplink transmission may be generated by Figure 16A when conversion precoding is disabled. These functions are shown as examples, and it is expected that other mechanisms may be implemented in various embodiments.

[0165] Figure 16B shows an exemplary structure for modulation and upconversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued SC-FDMA or CP-OFDM baseband signal and / or a complex-valued physical random access channel (PRACH) baseband signal to the antenna port. Filtering may be used before transmission.

[0166] Figure 16C shows an exemplary structure of downlink transmission. The baseband signal representing the physical downlink channel may perform one or more functions. These functions may include scrambling the encoded bits in the codeword to be transmitted over the physical channel, modulating the scrambled bits to generate a complex-valued modulation symbol, mapping the complex-valued modulation symbol to one or more transmission layers, precoding the complex-valued modulation symbol on the layer for transmission over the antenna port, mapping the complex-valued modulation symbol to resource elements at the antenna port, generating a complex-valued time-domain OFDM signal for each antenna port, and / or similar. These functions are shown as examples, and it is expected that other mechanisms may be implemented in various embodiments.

[0167] Figure 16D shows another exemplary structure for modulation and upconversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued OFDM baseband signal for the antenna port. Filtering may be used before transmission.

[0168] A wireless device may receive one or more messages (e.g., RRC messages) from a base station that include configuration parameters for multiple cells (e.g., primary cells, secondary cells). The wireless device may communicate with at least one base station (e.g., two or more base stations in a dual connection) via multiple cells. One or more messages (e.g., as part of configuration parameters) may include parameters for the physical, MAC, RLC, PCDP, SDAP, and RRC layers to configure the wireless device. For example, configuration parameters may include parameters for configuring physical and MAC layer channels, bearers, etc. For example, configuration parameters may include parameters indicating timer values ​​for the physical layer, MAC layer, RLC layer, PCDP layer, SDAP layer, RRC layer, and / or communication channels.

[0169] A timer, once started, begins execution and may continue execution until stopped or expired. A timer may be started when not running, or restarted when running. A timer may be associated with a value (for example, a timer may start or restart from a certain value, or start from 0 and expire when a value is reached). The duration of a timer may not be updated until the timer is stopped or expires (for example, by a BWP switch). A timer may be used to measure the time duration / window of a process. Where this specification refers to implementations and procedures related to one or more timers, it will be understood that there are multiple ways of implementing one or more timers. For example, it will be understood that one or more of the multiple ways of implementing a timer may be used to measure the duration / window of a procedure. For example, a random access response window timer may be used to measure the window time for receiving a random access response. In one embodiment, instead of the start and expiration of a random access response window timer, the time difference between two time stamps may be used. When a timer is restarted, the process for measuring the time window may be restarted. Other exemplary implementations may be provided to restart the time window measurement.

[0170] A wireless device may receive one or more messages from, for example, a base station, containing one or more configuration parameters. The wireless device may receive downlink control information (DCI) that schedules a transport block (e.g., PUSCH). The DCI may not include the SRI field. Based on, for example, the absence of the SRI field in the DCI, the wireless device may determine default open-loop power control parameters (e.g., target received power P_0-PUSCH, path loss compensation factor alpha, closed-loop process number 1). The default open-loop power control parameters may not include the (default) path loss reference signal.

[0171] A wireless device may determine the transmission power based on default open-loop power control parameters. The wireless device may transmit a transport block with / using the transmission power.

[0172] In one embodiment, a wireless device may function with a plurality of TRPs, including a first TRP and a second TRP (e.g., transmitting to / receiving from a plurality of TRPs). The wireless device may receive a DCI that schedules the repetition of a transport block (e.g., PUSCH) among the first and second TRPs. The wireless device may transmit a transport block to / for / to a first TRP in one or more first transmission opportunities, and may transmit a transport block to / for / to a second TRP in one or more second transmission opportunities. This may increase the reliability of the transmission of the transport block. For example, when the first TRP experiences interference (e.g., due to a tree, building, etc.), the second TRP may receive the transport block.

[0173] In one embodiment, the DCI for scheduling the repetition of a transport block may not include an SRI field. A DCI that does not include an SRI field may include, for example, a DCI that does not include a first SRI field and a DCI that does not include a second SRI field. A DCI that does not include an SRI field may include, for example, a DCI that includes a first SRI field and does not include a second SRI field. In the implementation of existing technology, a wireless device may determine default open-loop power control parameters based on the fact that the DCI does not include an SRI field. The wireless device may transmit the repetition of a transport block with / using transmission power determined based on the default open-loop power control parameters. Using the (same) transmission power for the repetition of a transport block, or determining the transmission power based on the (same) default open-loop power control parameters, may not be efficient. For example, the repetition of a transport block may be directed toward a first TRP and a second TRP, and the first TRP and the second TRP may not be located in the same position. The positions / directions of the first TRP and the second TRP may differ. The first and second TRPs may be subject to different channel conditions (e.g., channel fade, distance, interference, etc.). Using the (same) transmission power and / or determining the transmission power based on the (same) default open-loop power control parameters may result in inaccurate transmission power (e.g., lower or higher than the required transmission power) for repeated transport blocks. A wireless device may transmit a transport block toward at least one of the first and second TRPs with / using inaccurate transmission power, which may increase interference to other cells and / or wireless devices.

[0174] An exemplary embodiment enhances / improves the determination of open-loop power control parameters when a wireless device transmits repetitions of transport blocks to / for multiple TRPs. In the exemplary embodiment, when the DCI scheduling the repetitions of transport blocks does not include SRI fields (e.g., both a first SRI field and a second SRI field), the wireless device may determine two default open-loop power control parameters.

[0175] A wireless device may determine two transmission powers based on two default open-loop power control parameters. The wireless device may transmit a transport block in one or more first transmission opportunities (towards / towards a first TRP) with / using a first transmission power of the two transmission powers. The wireless device may determine a first transmission power based on a first default open-loop power control parameter of the two default open-loop power control parameters. The wireless device may transmit a transport block in one or more second transmission opportunities (towards / towards a second TRP) with / using a second transmission power of the two transmission powers. The wireless device may determine a second transmission power based on a second default open-loop power control parameter of the two default open-loop power control parameters.

[0176] In exemplary embodiments, the DCI for scheduling the repetition of a transport block may include a first SRI field but may not include a second SRI field. In this case, the wireless device may determine a second default open-loop power control parameter for the repetition of the transport block. The wireless device may transmit the transport block in one or more first transmission opportunities toward / to a first TRP with / using a first transmission power determined based on the open-loop power control parameter indicated by the first SRI field. The wireless device may transmit the transport block in one or more second transmission opportunities toward / to a second TRP with / using a second transmission power determined based on a second default open-loop power control parameter.

[0177] Using two (different) transmission powers based on two (different) default open-loop power control parameters, or determining the transmission power based on two (different) open-loop power control parameters, for repeated transport blocks directed to different TRPs can result in accurate transmission power determination. A wireless device can then transmit the transport block to each TRP with / using the accurate transmission power. This can result in reduced uplink interference to other cells and / or wireless devices. This, in turn, can lead to reliable reception of the transport block and a reduced error rate.

[0178] Figures 17, 18, and 19 show an example of power control in an uplink channel repeat according to one embodiment of the present disclosure.

[0179] Figure 20 shows one embodiment of an uplink repeating scheme according to one aspect of the embodiments of the present disclosure.

[0180] A wireless device may receive one or more messages (for example, at time T0 in Figures 17-19). In one embodiment, the wireless device may receive one or more messages from a base station. One or more messages may include one or more configuration parameters. In one embodiment, one or more configuration parameters may be RRC configuration parameters. In one embodiment, one or more configuration parameters may be RRC reconstruction parameters.

[0181] In one embodiment, one or more configuration parameters may be for a cell. In one embodiment, at least one of the one or more configuration parameters may be for a cell. In one embodiment, the cell may be a primary cell (PCell). In one embodiment, the cell may be a secondary cell (SCell). The cell may be a secondary cell composed of PUCCHs (e.g., a PUCCH SCell). In one embodiment, the cell may be an unlicensed cell, for example, operating in an unlicensed band. In one embodiment, the cell may be a licensed cell, for example, operating in a licensed band. In one embodiment, the cell may operate in a first frequency range (FR1). FR1 may include, for example, a frequency band below 6 GHz. In one embodiment, the cell may operate in a second frequency range (FR2). FR2 may include, for example, a frequency band from 24 GHz to 52.6 GHz.

[0182] In one embodiment, the wireless device may perform uplink transmission (e.g., PUSCH, PUCCH, SRS) through the cell at a first time and a first frequency. The wireless device may perform downlink reception (e.g., PDCCH, PDSCH) through the cell at a second time and a second frequency. In one embodiment, the cell may operate in time-division duplex (TDD) mode. In TDD mode, the first frequency and the second frequency may be the same. In TDD mode, the first time and the second time may be different. In one embodiment, the cell may operate in frequency-division duplex (FDD) mode. In FDD mode, the first frequency and the second frequency may be different. In FDD mode, the first time and the second time may be the same.

[0183] In one embodiment, the wireless device may be in RRC connection mode. In one embodiment, the wireless device may be in RRC idle mode. In one embodiment, the wireless device may be in RRC inactive mode.

[0184] In one embodiment, a cell may include multiple BWPs. The multiple BWPs may include one or more uplink BWPs, including the cell's uplink BWP. The multiple BWPs may include one or more downlink BWPs, including the cell's downlink BWP.

[0185] In one embodiment, a BWP with multiple BWPs may be in either an active or inactive state. In one embodiment, in the active state of one or more downlink BWPs, a wireless device may monitor downlink channels / signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / for / to the downlink BWP. In one embodiment, in the active state of one or more downlink BWPs, a wireless device may receive PDSCH on / for / to the downlink BWP. In one embodiment, in the inactive state of one or more downlink BWPs, a wireless device may not monitor downlink channels / signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / for / to the downlink BWP. In the inactive state of one or more downlink BWPs, a wireless device may stop monitoring (or receiving) downlink channels / signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / for / to the downlink BWP. In one embodiment, when one or more downlink BWPs are inactive, the wireless device may not receive PDSCH on / through / for the downlink BWPs. When one or more downlink BWPs are inactive, the wireless device may stop receiving PDSCH on / through / for the downlink BWPs.

[0186] In one embodiment, when one or more uplink BWPs are active, a wireless device can transmit uplink signals / channels (e.g., PUCCH, preamble, PUSCH, PRACH, SRS, etc.) over / through the uplink BWPs. In one embodiment, when one or more uplink BWPs are inactive, a wireless device cannot transmit uplink signals / channels (e.g., PUCCH, preamble, PUSCH, PRACH, SRS, etc.) over / through the uplink BWPs.

[0187] In one embodiment, a wireless device can activate one or more downlink BWPs of a cell. In one embodiment, activating a downlink BWP may include the wireless device setting (or switching to) the downlink BWP as the active downlink BWP of the cell. In one embodiment, activating a downlink BWP may include the wireless device setting the downlink BWP to an active state. In one embodiment, activating a downlink BWP may include switching the downlink BWP from an inactive state to an active state.

[0188] In one embodiment, a wireless device may activate one or more uplink BWPs of a cell. In one embodiment, activating an uplink BWP may include the wireless device setting (or switching to) the uplink BWP as the active uplink BWP of the cell. In one embodiment, activating an uplink BWP may include the wireless device setting the uplink BWP to an active state. In one embodiment, activating an uplink BWP may include switching the uplink BWP from an inactive state to an active state.

[0189] In one embodiment, one or more configuration parameters may be for the cell's (active) downlink BWP. In one embodiment, at least one of the one or more configuration parameters may be for the cell's downlink BWP.

[0190] In one embodiment, one or more configuration parameters may be for the cell's (active) uplink BWP. In one embodiment, at least one of the one or more configuration parameters may be for the cell's uplink BWP.

[0191] In one embodiment, the wireless device may, for example, transmit a UE capability message containing UE capability information to a base station.

[0192] In one embodiment, UE capability information may indicate / configure support for beam correspondence without an uplink beam sweep (e.g., beamCorrespondenceWithoutUL-BeamSweeping). In one embodiment, a wireless device may indicate support for beam correspondence without an uplink sweep by setting the value of beamCorrespondenceWithoutUL-BeamSweeping in the UE capability message to a first value (e.g., one). Based on the UE capability information indicating support for beam correspondence without an uplink beam sweep, the wireless device may determine / select a (suitable) beam (or spatial domain transmission filter) for uplink transmission based on downlink measurements, without relying on an uplink beam sweep. The wireless device may not determine / select a (suitable) beam (or spatial domain transmission filter) for uplink transmission based on an uplink beam sweep.

[0193] In one embodiment, UE capability information may indicate support for repeated transmission of uplink signals (e.g., PUCCH, PUSCH, transport block, SRS). Repeating may occur, for example, in TDM. Repeating may occur, for example, in FDM. Repeating may occur, for example, in SDM / SFN (e.g., spatial domain / division multiplexing). Repeating may occur, for example, in CDM (e.g., code domain / division multiplexing). A wireless device may repeat the transmission of uplink signals, for example, based on the UE capability information indicating support for repeated transmission of uplink signals.

[0194] In the embodiment, one or more configuration parameters may indicate a target power level set list (e.g., p0-PUSCH-SetList). A target power level set list may indicate / include one or more target power level sets (e.g., P0-PUSCH-Set). One or more configuration parameters may indicate one or more target power level sets (or target power level set lists) for a cell. One or more configuration parameters may indicate one or more target power level sets (or target power level set lists) for a cell's (active) uplink BWP. A wireless device may use one or more target power level sets for determining the transmission power of an uplink channel (e.g., PUSCH, PUCCH, SRS).

[0195] In one embodiment, one or more configuration parameters may indicate one or more target power level set indices / identifiers for one or more target power level sets (e.g., provided by a higher-level parameter p0-PUSCH-SetId). In one embodiment, each target power level set of one or more target power level sets may be identified / indicated by its respective target power level set index of one or more target power level set indices. In one embodiment, a first target power level set of one or more target power level sets may be identified by a first target power level set index of one or more target power level set indices. A second target power level set of one or more target power level sets may be identified by a second target power level set index of one or more target power level set indices.

[0196] In one embodiment, one or more configuration parameters may indicate a target power path loss compensation set list (e.g., p0-AlphaSets). A target power path loss compensation set list may indicate / include one or more target power path loss compensation sets (e.g., P0-PUSCH-AlphaSet). One or more configuration parameters may indicate one or more target power path loss compensation sets (or target power path loss compensation set lists) for a cell. One or more configuration parameters may indicate one or more target power path loss compensation sets (or target power path loss compensation set lists) for the (active) uplink BWP of a cell. A wireless device may use one or more target power path loss compensation sets for determining the transmission power of an uplink channel (e.g., PUSCH, PUCCH, SRS).

[0197] In an embodiment, one or more configuration parameters may indicate an index / identifier (for example, provided by the higher-level parameter P0-PUSCH-AlphaSetId) for one or more target power path loss compensation sets. In an embodiment, each target power path loss compensation set of one or more target power path loss compensation sets may be identified / indicated by its respective target power path loss compensation set index in one or more target power path loss compensation set indices. In an embodiment, a first target power path loss compensation set of one or more target power path loss compensation sets may be identified by a first target power path loss compensation set index in one or more target power path loss compensation set indices. A second target power path loss compensation set of one or more target power path loss compensation sets may be identified by a second target power path loss compensation set index in one or more target power path loss compensation set indices.

[0198] In one embodiment, one or more configuration parameters may represent one or more power control parameter sets (e.g., SRI-PUSCH-PowerControl).

[0199] In one embodiment, one or more configuration parameters may indicate one or more power control parameter set indices / identifiers for one or more power control parameter sets (e.g., provided by the higher-level parameter sri-PUSCH-PowerControlId). In one embodiment, each power control parameter set of one or more power control parameter sets may be identified / indicated by its respective power control parameter set index of one or more power control parameter set indices. In one embodiment, a first power control parameter set of one or more power control parameter sets may be identified by a first power control parameter set index of one or more power control parameter set indices. A second power control parameter set of one or more power control parameter sets may be identified by a second power control parameter set index of one or more power control parameter set indices.

[0200] One or more power control parameter sets may indicate (or be mapped to) one or more target power level sets. Each power control parameter set in one or more power control parameter sets may indicate (or be mapped to) each target power level set of one or more target power level sets. For example, the first power control parameter set of one or more power control parameter sets may indicate (or be mapped to) the first target power level set of one or more target power level sets. One or more configuration parameters may indicate the index (e.g., p0-PUSCH-SetId) of the first target power level set of the first target power level set for the first power control parameter set. The second power control parameter set of one or more power control parameter sets may indicate (or be mapped to) the second target power level set of one or more target power level sets. One or more configuration parameters may indicate the index (e.g., p0-PUSCH-SetId) of the second target power level set of the second target power level set for the second power control parameter set. A third power control parameter set of one or more power control parameter sets may indicate (or map to) a first target power level set. One or more configuration parameters may indicate a first target power level set index of the first target power level set to the third power control parameter set. One or more target power level set indices may include a first target power level set index and a second target power level set index. One or more configuration parameters may indicate, for example, a mapping between one or more power control parameter sets and one or more target power level sets. The mapping between one or more power control parameter sets and one or more target power level sets may, for example, be predefined / fixed / preconfigured. The mapping between one or more power control parameter sets and one or more target power level sets may, for example, be a one-to-one mapping.The mapping between one or more power control parameter sets and one or more target power level sets may be, for example, a one-to-many mapping. The mapping between one or more power control parameter sets and one or more target power level sets may be, for example, a many-to-one mapping.

[0201] One or more power control parameter sets may indicate (or be mapped to) one or more target power path loss compensation sets. Each power control parameter set in one or more power control parameter sets may indicate (or be mapped to) each target power path loss compensation set of one or more target power path loss compensation sets. For example, the first power control parameter set of one or more power control parameter sets may indicate (or be mapped to) the first target power path loss compensation set of one or more target power path loss compensation sets. One or more configuration parameters may indicate, for the first power control parameter set, the index (e.g., P0-PUSCH-AlphaSetId) of the first target power path loss compensation set of the first target power path loss compensation set. The second power control parameter set of one or more power control parameter sets may indicate (or be mapped to) the second target power path loss compensation set of one or more target power path loss compensation sets. One or more configuration parameters may indicate, for a second power control parameter set, the index of the second target power path loss compensation set (e.g., P0-PUSCH-AlphaSetId) of the second target power path loss compensation set. A third power control parameter set of one or more power control parameter sets may indicate (or be mapped to) the first target power path loss compensation set. One or more configuration parameters may indicate, for a third power control parameter set, the index of the first target power path loss compensation set of the first target power path loss compensation set. One or more target power path loss compensation set indices may include the first target power path loss compensation set index and the second target power path loss compensation set index. One or more configuration parameters may indicate, for example, a mapping between one or more power control parameter sets and one or more target power path loss compensation sets. The mapping between one or more power control parameter sets and one or more target power path loss compensation sets may, for example, be predefined / fixed / preconfigured.The mapping between one or more power control parameter sets and one or more target power path loss compensation sets may be, for example, a one-to-one mapping. The mapping between one or more power control parameter sets and one or more target power path loss compensation sets may be, for example, a one-to-many mapping. The mapping between one or more power control parameter sets and one or more target power path loss compensation sets may be, for example, a many-to-one mapping.

[0202] In one embodiment, one or more configuration parameters may not specify a target power level setlist (e.g., p0-PUSCH-SetList). One or more configuration parameters may not specify a target power level setlist for, for example, a cell. One or more configuration parameters may not specify a target power level setlist for, for example, a cell's (active) uplink BWP.

[0203] In one embodiment, one or more configuration parameters may not indicate one or more target power level sets (e.g., P0-PUSCH-Set). One or more configuration parameters may not indicate a target power level set for, for example, a cell. One or more configuration parameters may not indicate a list of target power level sets for, for example, a cell's (active) uplink BWP.

[0204] In one embodiment, one or more configuration parameters may not represent one or more power control parameter sets (e.g., SRI-PUSCH-PowerControl). One or more configuration parameters may not represent one or more power control parameter sets for, for example, a cell. One or more configuration parameters may not represent one or more power control parameter sets for, for example, a cell's (active) uplink BWP.

[0205] In one embodiment, the value of the open-loop parameter may be equal to 2 (e.g., j=2). An open-loop parameter value equal to 2 may indicate a scheduled PUSCH transmission (e.g., via a dynamic uplink grant). An open-loop parameter value equal to 0 may indicate an msg3 PUSCH transmission for a random access procedure. An open-loop parameter value equal to 1 may indicate a PUSCH transmission for a configured uplink grant (e.g., a grant-free PUSCH transmission).

[0206] In one embodiment, one or more configuration parameters may indicate multiple SRS resource sets, each containing at least two SRS resource sets. The at least two SRS resource sets may include a first SRS resource set (e.g., SRS resource set 1 in Figure 17) and a second SRS resource set (e.g., SRS resource set 2 in Figure 17).

[0207] In one embodiment, at least one of the two SRS resource sets (e.g., a first SRS resource set and / or a second SRS resource set) may be periodic. One or more configuration parameters may indicate the periodic resource type of the SRS resource set (e.g., the resource type of a higher-level parameter is set to be periodic).

[0208] In one embodiment, at least one of the two SRS resource sets (e.g., a first SRS resource set and / or a second SRS resource set) may be aperiodic. One or more configuration parameters may indicate the aperiodic resource type of the SRS resource set (e.g., the resource type of a higher-level parameter is set to aperiodic).

[0209] In one embodiment, at least one of two SRS resource sets (e.g., a first SRS resource set and / or a second SRS resource set) may be semi-persistent. One or more configuration parameters may indicate the semi-persistent resource type of the SRS resource set (e.g., the resource type of a higher-level parameter is set to semi-persistent).

[0210] In one embodiment, one or more configuration parameters may include certain SRS usage parameters for at least two SRS resource sets.

[0211] The SRS usage parameter can be (and set to) a codebook, for example (e.g., use=codebook). At least two SRS resource sets can be used for codebook-based uplink transmission (e.g., PUSCH transmission) based on the fact that the SRS usage parameter is a codebook. Each of the at least two SRS resource sets can be used for codebook-based uplink transmission.

[0212] The SRS usage parameter can be (and set to) non-codebook (e.g., use = non-codebook). At least two SRS resource sets can be used for non-codebook-based uplink transmissions (e.g., PUSCH transmissions) based on the SRS usage parameter which is non-codebook (and is set to). Each of the at least two SRS resource sets can be used for non-codebook-based uplink transmissions.

[0213] One or more configuration parameters may include a first SRS usage parameter for the SRS resource set. One or more configuration parameters may include a second SRS usage parameter for the SRS resource set.

[0214] In one embodiment, the first SRS usage parameter may be (or may be set to) a codebook. The second SRS usage parameter may be (or may be set to) a codebook.

[0215] In one embodiment, the first SRS usage parameter may be (or may be set to) a non-codebook. The second SRS usage parameter may also be (or may be set to) a non-codebook.

[0216] In one embodiment, a wireless device may receive / detect a DCI (for example, at time T1 in Figures 17-19). The DCI may be, for example, DCI format 0-0. The DCI may be, for example, DCI format 0-1. The DCI may be, for example, DCI format 0-2. The DCI format may be, for example, DCI format 0-x, where x = 0, 1, 2, 3, ...

[0217] In one embodiment, DCI may schedule the transmission of transport blocks (e.g., PUSCH transmission). DCI may schedule the transmission of transport blocks (e.g., TB in Figures 17-19) over / through an uplink channel (e.g., PUSCH, PUCCH). DCI may include a dynamic uplink grant for the transmission of transport blocks. A wireless device may transmit transport blocks (e.g., TB in Figures 17-19) via uplink resources indicated by, for example, DCI (or a dynamic uplink grant). An uplink channel may include uplink resources. An (active) uplink BWP may include uplink resources.

[0218] In one embodiment, one or more configuration parameters may indicate one or more configured uplink grants (e.g., by the upper-layer parameter ConfiguredGrantConfig). One or more configured uplink grants may include a configured uplink grant. In one embodiment, a configured uplink grant may be a type 2 configured uplink grant (or configured grant type 2). In a type 2 configured uplink grant, PDCCH may indicate / provide the uplink grant. DCI (or layer 1 signaling) may indicate configured uplink grant active. A wireless device may store an uplink grant as a configured uplink grant based on the fact that receiving DCI indicates configured uplink grant activation. In one embodiment, DCI may activate a configured uplink grant. In one embodiment, a wireless device may transmit a transport block (e.g., TB in Figures 17-19) for a configured uplink grant over / through an uplink channel (e.g., PUSCH, PUCCH). A wireless device may transmit a transport block (e.g., a PUSCH transmission) through one or more periodic uplink resources of a configured uplink grant. One or more periodic uplink resources may include uplink resources (e.g., a PUSCH resource, a PUCCH resource, an SRS resource). An uplink channel may include one or more uplink resources. An (active) uplink BWP may include uplink resources.

[0219] In one embodiment, a wireless device may not transmit a transport block for a random access procedure. A wireless device may not transmit a transport block for the transmission of msg3 for a random access procedure. The transmission of a transport block may not be for PUSCH retransmission corresponding to a Random Access Response (RAR) uplink grant. DCI may not be able to schedule retransmission of PUSCH transmissions that were (initially) scheduled by a RAR uplink grant.

[0220] DCI may include a Time Domain Resource Alignment (TDRA) field. The TDRA field may indicate a resource allocation table. The resource allocation table may be indicated, for example, by one or more configuration parameters. The resource allocation table may be, for example, pre-configured / fixed. The TDRA field may indicate the number of repetitions for a transport block (e.g., numberofrepetitions). The resource allocation table may include the number of repetitions (e.g., numberofrepetitions). The number of repetitions (e.g., numberofrepetitions) may be present in the resource allocation table. In Figures 17-19, the number of repetitions is equal to 4 (e.g., numberofrepetitions=4).

[0221] In one embodiment, the numberofrepetitions of a higher-level parameter may not exist in the resource allocation table indicated by the TDRA field in DCI. One or more configuration parameters may not include the number of repetitions of a higher-level parameter in the resource allocation table. In one embodiment, one or more configuration parameters may indicate the number of repetitions (e.g., push-AggregationFactor). In Figures 17-19, the number of repetitions is equal to 4 (e.g., push-AggregationFactor=4).

[0222] In one embodiment, the number of repetitions may be for the repetition of a transport block via an uplink resource (or uplink channel) (e.g., a PUCCH resource, an SRS resource, a PUSCH resource). In one embodiment, one or more configuration parameters may indicate multiple uplink signal / channel transmission / repetition opportunities (e.g., a PUSCH transmission opportunity, a PUCCH transmission opportunity) for the transmission / repetition of a transport block. In one embodiment, DCI may indicate multiple uplink signal / channel transmission / repetition opportunities (e.g., a PUSCH transmission opportunity, a PUCCH transmission opportunity) for the transmission / repetition of a transport block. In one embodiment, DCI may indicate the first / starting / earliest uplink signal / channel transmission / repetition opportunity. Based on the first / starting / earliest uplink signal / channel transmission / repetition opportunity, the wireless device may determine multiple uplink signal / channel transmission / repetition opportunities, including the first / starting / earliest uplink signal / channel transmission / repetition opportunity, for the transmission / repetition of a transport block. A wireless device may determine the first / starting / earliest uplink signal / channel transmission / repeat opportunity based on one or more fields in the DCI (e.g., TDRA, FDRA, etc.). The number of uplink signal / channel transmission opportunities may be equal to, for example, the number of repetitions.

[0223] In one embodiment, a wireless device may transmit a transport block over / on / in / over multiple uplink signals / channel transmissions / repetition opportunities (e.g., times T2a to T2d in Figures 17 to 19). The wireless device may repeat the transmission of a transport block over / on / in / over multiple uplink signals / channel transmissions / repetition opportunities. The wireless device may transmit a transport block "number of repetitions" times. For example, when the number of repetitions is 4, the wireless device may transmit the transport block 4 times. When the number of repetitions is 2, the wireless device may transmit the transport block 2 times.

[0224] A wireless device may, for example, repeat a transport block (transmission of) over / on / in / on multiple uplink signal / channel transmission / repeating opportunities, based on the TDRA field indicating the number of repetitions.

[0225] A wireless device may, for example, repeat a transport block (transmission of) over / on / in / on multiple uplink signal / channel transmission / repeating opportunities, based on one or more configuration parameters indicating the number of repetitions.

[0226] In one embodiment, one or more configuration parameters may indicate a repeating scheme (e.g., FDM-Scheme, TDM-Scheme, SFN-Scheme, SDM-Scheme, CDM-Scheme). In one embodiment, DCI may indicate a repeating scheme. DCI may include one or more fields indicating a repeating scheme (e.g., SRI field, TCI field, antenna port field, etc.). The repeating scheme may be for the repetition of transmission of transport blocks (e.g., PUSCH transmission) over uplink resources (e.g., PUCCH resource, SRS resource, PUSCH resource). The repeating scheme may be, for example, a time-domain repeating scheme (e.g., TDM in Figure 20). The repeating scheme may be, for example, a frequency-domain repeating scheme (e.g., FDM in Figure 20). The repeating scheme may be, for example, a code / space-domain repeating scheme (e.g., SDM / SFN in Figure 20). In Figures 17-19, the repeating scheme is a time-domain repeating scheme.

[0227] A wireless device may, for example, repeat transport blocks (of transmission) across / over / in multiple uplink signal / channel transmission / repeated opportunities, based on one or more configuration parameters indicating a repeating scheme.

[0228] A repeating transport block can be, for example, a repeating time domain (e.g., TDM, TDMSchemeA, TDMSchemeB, etc. in Figure 20). In a repeating time domain, multiple uplink signal / channel transmission opportunities may not overlap in time. Each uplink signal / channel transmission opportunity in a repeating uplink signal / channel transmission opportunity may have non-overlapping time domain resource allocations to other uplink signal / channel transmission opportunities in the repeating uplink signal / channel transmission opportunity. For example, the first uplink signal / channel transmission opportunity in a repeating uplink signal / channel transmission opportunity may not overlap in time with the second uplink signal / channel transmission opportunity in the repeating uplink signal / channel transmission opportunity. The first and second uplink signal / channel transmission opportunities may be different. In a repeating time domain, multiple uplink signal / channel transmission opportunities may or may not overlap in frequency. Multiple uplink signal / channel transmission / repeating opportunities are the first TX opportunity, second TX opportunity, third TX opportunity, and fourth TX opportunity in time-domain repetition (e.g., TDM) in Figure 20. In time-domain repetition, the repetition of a transport block can be, for example, a time unit (e.g., TDM-ed). A wireless device can repeat the transmission of a transport block over / on / in / over a time unit. A time unit can be, for example, continuous. A time unit can be, for example, non-continuous (e.g., it may have time / symbol / slot gaps). The number of time units can be equal to the number of repetitions. A time unit can be, for example, a time slot. A time unit can be, for example, a minislot. A time unit can be, for example, a time symbol (e.g., an OFDM symbol). A time unit can be, for example, a subframe. A time unit can be, for example, an actual / nominal repetition. Multiple uplink signal / channel transmission opportunities can / occur in time units.For example, the first uplink signal / channel transmission opportunity among multiple uplink signal / channel transmission opportunities may occur in a first time unit. The second uplink signal / channel transmission opportunity among multiple uplink signal / channel transmission opportunities may occur in a second time unit, etc. The first time unit may be different from the second time unit. The first time unit may not overlap temporally with the second time unit.

[0229] A repeating transport block may be, for example, a repeating frequency domain (e.g., FDM, FDMSchemeA, FDMSchemeB, etc. in Figure 20). In a repeating time domain, multiple uplink signal / channel transmission opportunities may or may not overlap in time. In a repeating frequency domain, multiple uplink signal / channel transmission opportunities may not overlap in frequency. Each uplink signal / channel transmission opportunity of multiple uplink signal / channel transmission opportunities may have non-overlapping frequency domain resource allocations with respect to other uplink signal / channel transmission opportunities of the multiple uplink signal / channel transmission opportunities. For example, the first uplink signal / channel transmission opportunity of multiple uplink signal / channel transmission opportunities may not overlap in frequency with respect to the second uplink signal / channel transmission opportunity of the multiple uplink signal / channel transmission opportunities. The first and second uplink signal / channel transmission opportunities may overlap in time. The first and second uplink signal / channel transmission opportunities may be different. Multiple uplink signal / channel transmission / repeating opportunities are the first TX opportunity, second TX opportunity, etc., in frequency domain repetition (e.g., FDM) in Figure 20. In frequency domain repetition, the repetition of a transport block can be / occur in, for example, frequency units (e.g., frequency, PRB, frequency band, subband, bandwidth portion, cell). A wireless device can repeat the transmission of a transport block over / on / in frequency units, for example. Frequency units can be, for example, continuous. Frequency units can be, for example, non-continuous (e.g., they can have frequency / PRB gaps). The number of frequency units can be equal to the number of repetitions. Frequency units can be, for example, frequency bands. Frequency units can be, for example, physical resource blocks (PRBs). Frequency units can be, for example, BWPs. Frequency units can be, for example, cells. Multiple uplink signal / channel transmission opportunities can be / occur in frequency units.For example, the first uplink signal / channel transmission opportunity among multiple uplink signal / channel transmission opportunities may be / occur as the first frequency unit in frequency units. The second uplink signal / channel transmission opportunity among multiple uplink signal / channel transmission opportunities may be / occur as the second frequency unit in frequency units, etc. The first frequency unit may be different from the second frequency unit. The first frequency unit may not overlap with the second frequency unit in frequency.

[0230] The repetition of a transport block can be, for example, a code / spatial domain repetition scheme (e.g., SDM / SFN, SDM scheme, CDM scheme, SDMScheme, CDMScheme, etc. in Figure 20). In a code / spatial domain repetition scheme, multiple uplink signal / channel transmission opportunities may overlap in time. In a code / spatial domain repetition scheme, multiple uplink signal / channel transmission opportunities may overlap in frequency. In a code / spatial domain repetition, multiple uplink signal / channel transmission opportunities may be uplink signal / channel transmission opportunities (e.g., or a single uplink signal / channel transmission opportunity). Each uplink signal / channel transmission opportunity in multiple uplink signal / channel transmission opportunities may be the same (or the same as an uplink signal / channel transmission opportunity or a single uplink signal / channel transmission opportunity). Each uplink signal / channel transmission opportunity in multiple uplink signal / channel transmission opportunities may have overlapping frequency domain resource allocations with respect to other uplink signal / channel transmission opportunities among the multiple uplink signal / channel transmission opportunities. Each uplink signal / channel transmission opportunity in a plurality of uplink signal / channel transmission opportunities may have time-domain resource allocations that overlap with other uplink signal / channel transmission opportunities in the plurality of uplink signal / channel transmission opportunities. For example, the first uplink signal / channel transmission opportunity in a plurality of uplink signal / channel transmission opportunities may overlap in time and frequency with the second uplink signal / channel transmission opportunity in the plurality of uplink signal / channel transmission opportunities. The first uplink signal / channel transmission opportunity (e.g., the first TX opportunity) and the second uplink signal / channel transmission opportunity (e.g., the second TX opportunity) may be the same. The plurality of uplink signal / channel transmission / repetition opportunities are the first TX opportunity and the second TX opportunity in the code / spatial domain repetition (e.g., SDM / SFN) in Figure 20. The first TX opportunity and the second TX opportunity may be the same in the code / spatial domain repetition (e.g., they may overlap in time and frequency).In a code / spatial domain iteration, multiple uplink signal / channel transmission opportunities may occur in the same frequency unit (e.g., frequency, PRB, frequency band, bandwidth portion, cell). For example, the first frequency unit of the first uplink signal / channel transmission opportunity and the second frequency unit of the second uplink signal / channel transmission opportunity may overlap in frequency. Multiple uplink signal / channel transmission opportunities may occur in the same time unit (e.g., symbol, actual / nominal iteration, minislot, slot, subframe, etc.). For example, the first time unit of the first uplink signal / channel transmission opportunity and the second time unit of the second uplink signal / channel transmission opportunity may overlap in time.

[0231] For example, in Figures 17 to 19, the multiple uplink signal / channel transmission opportunities include a first uplink signal / channel transmission opportunity (e.g., the first TX opportunity, the first time slot, the first actual / nominal repetition), a second uplink signal / channel transmission opportunity (e.g., the second TX opportunity, the second time slot, the second actual / nominal repetition), a third uplink signal / channel transmission opportunity (e.g., the third TX opportunity, the third time slot, the third actual / nominal repetition), and a fourth uplink signal / channel transmission opportunity (e.g., the fourth TX opportunity, the fourth time slot, the fourth actual / nominal repetition).

[0232] In one embodiment, a wireless device may determine / calculate / calculate multiple transmission powers. The wireless device may determine / calculate / calculate multiple transmission powers for the transmission of a transport block.

[0233] A wireless device may transmit a transport block using / with multiple transmission powers.

[0234] A wireless device may determine / calculate / calculate multiple transmission powers for, for example, the repetition of a transport block. The wireless device may repeat the transmission of a transport block with / using multiple transmission powers (for example, at times T2a to T2d in Figures 17 to 19). The wireless device may transmit the repetition of a transport block with / using multiple transmission powers.

[0235] In one embodiment, a wireless device may transmit a transport block over / on / in / at multiple uplink signal / channel transmission / repeating opportunities (e.g., times T2a to T2d in Figures 17 to 19) with multiple transmission powers. A wireless device may transmit a transport block over / on / at each of the multiple uplink signal / channel transmission opportunities with / using each of the multiple transmission powers. A wireless device may transmit a transport block at each of the multiple uplink signal / channel transmission opportunities with / using each of the multiple transmission powers.

[0236] A wireless device may transmit a transport block across / on / in one or more first uplink signal / channel transmission opportunities of multiple uplink signal / channel transmission opportunities, using / with a first transmission power of multiple transmission powers. A wireless device may transmit a transport block across / on / in one or more second uplink signal / channel transmission opportunities of multiple uplink signal / channel transmission opportunities, using / with a second transmission power of multiple transmission powers. In Figures 17 to 19, one or more first uplink signal / channel transmission opportunities are a first uplink signal / channel transmission opportunity (e.g., the first TX opportunity, the first time slot, the first actual / nominal repetition at time T2a) and a third uplink signal / channel transmission opportunity (e.g., the third TX opportunity, the third time slot, the third actual / nominal repetition at time T2c). One or more second uplink signal / channel transmission opportunities are the second uplink signal / channel transmission opportunity (e.g., the second TX opportunity, the second time slot, the second actual / nominal repetition at time T2b) and the fourth uplink signal / channel transmission opportunity (e.g., the fourth TX opportunity, the fourth time slot, the fourth actual / nominal repetition at time T2d).

[0237] In one embodiment, the number of repetitions may be 2. Multiple uplink signal / channel transmission opportunities may include a first uplink signal / channel transmission opportunity (the first TX opportunity) and a second uplink signal / channel transmission opportunity (e.g., the second TX opportunity). A wireless device may transmit the transport block in the first uplink signal / channel transmission opportunity with / using a first transmission power. A wireless device may apply the first transmission power to the first uplink signal / channel transmission opportunity. A wireless device may transmit the transport block in the second uplink signal / channel transmission opportunity with / using a second transmission power. A wireless device may apply the second transmission power to the second uplink signal / channel transmission opportunity.

[0238] In one embodiment, the number of repetitions may be greater than (or more than) 2. In one embodiment, one or more configuration parameters may indicate periodic mapping. Periodic mapping can enable / indicate the mapping of multiple transmission powers to multiple uplink signal / channel transmission opportunities, for example, periodically (e.g., periodically switching transmission powers). A wireless device may transmit a transport block with / using a first transmission power on a first uplink signal / channel transmission opportunity (e.g., the first TX opportunity) of multiple uplink signal / channel transmission opportunities. A wireless device may apply the first transmission power to a first uplink signal / channel transmission opportunity. A wireless device may transmit a transport block with / using a second transmission power on a second uplink signal / channel transmission opportunity (e.g., the second TX opportunity) of multiple uplink signal / channel transmission opportunities. A wireless device may apply the second transmission power to a second uplink signal / channel transmission opportunity. The same transmission power mapping pattern can remain for multiple uplink signal / channel transmission opportunities, for example, based on one or more configuration parameters exhibiting periodic mapping. A retained uplink signal / channel transmission opportunity may not include the first and second uplink signal / channel transmission opportunities. For example, if the number of repetitions is equal to 4, multiple uplink signal / channel transmission opportunities may include the first uplink signal / channel transmission opportunity, the second uplink signal / channel transmission opportunity, the third uplink signal / channel transmission opportunity (e.g., the third TX opportunity), and the fourth uplink signal / channel transmission opportunity (e.g., the fourth TX opportunity). A wireless device may transmit a transport block in the first and third uplink signal / channel transmission opportunities with / using the first transmission power. The wireless device may transmit a transport block in a second uplink signal / channel transmission opportunity and a fourth uplink signal / channel transmission opportunity with / using a second transmission power.For example, when the number of repetitions is equal to 8, multiple uplink signal / channel transmission opportunities may include a first uplink signal / channel transmission opportunity (e.g., the first TX opportunity), a second uplink signal / channel transmission opportunity (e.g., the second TX opportunity), a third uplink signal / channel transmission opportunity (e.g., the third TX opportunity), a fourth uplink signal / channel transmission opportunity (e.g., the fourth TX opportunity), a fifth uplink signal / channel transmission opportunity (e.g., the fifth TX opportunity), a sixth uplink signal / channel transmission opportunity (e.g., the sixth TX opportunity), a seventh uplink signal / channel transmission opportunity (e.g., the seventh TX opportunity), and an eighth uplink signal / channel transmission opportunity (e.g., the eighth TX opportunity). A wireless device may transmit the transport block in the first uplink signal / channel transmission opportunity, the third uplink signal / channel transmission opportunity, the fifth uplink signal / channel transmission opportunity, and the seventh uplink signal / channel transmission opportunity with / using a first transmission power. The wireless device may transmit transport blocks in the second uplink signal / channel transmission opportunity, the fourth uplink signal / channel transmission opportunity, the sixth uplink signal / channel transmission opportunity, and the eighth uplink signal / channel transmission opportunity with / using a second transmission power. Figures 17-19 show an example of periodic mapping (for example, the first transmission power is used for the first and third uplink signal / channel transmission opportunities, and the second transmission power is used for the second and fourth uplink signal / channel transmission opportunities).

[0239] In one embodiment, the number of repetitions may be greater than (or more than) 2. In one embodiment, one or more configuration parameters may indicate sequential mapping. Sequential mapping may enable the mapping of multiple transmission powers to multiple uplink signal / channel transmission opportunities sequentially (e.g., sequentially switching transmission powers). A wireless device may transmit a transport block in a first uplink signal / channel transmission opportunity (e.g., the first TX opportunity) and in a second uplink signal / channel transmission opportunity (e.g., the second TX opportunity) among the multiple uplink signal / channel transmission opportunities, with / using the first transmission power. The wireless device may apply the first transmission power to the first uplink signal / channel transmission opportunity and to the second uplink signal / channel transmission opportunity. A wireless device may transmit a transport block in a third uplink signal / channel transmission opportunity (e.g., the third TX opportunity) and in a fourth uplink signal / channel transmission opportunity (e.g., the fourth TX opportunity) among multiple uplink signal / channel transmission opportunities, with / using a second transmission power. The wireless device may apply the second transmission power to the third uplink signal / channel transmission opportunity and to the fourth uplink signal / channel transmission opportunity. The same transmission power mapping pattern may remain in uplink signal / channel transmission opportunities of multiple uplink signal / channel transmission opportunities, for example, based on one or more configuration parameters indicating sequential mapping. The remaining uplink signal / channel transmission opportunities may not include the first, second, third, and fourth uplink signal / channel transmission opportunities.For example, if the number of repetitions is equal to 4, multiple uplink signal / channel transmission opportunities may include a first uplink signal / channel transmission opportunity, a second uplink signal / channel transmission opportunity, a third uplink signal / channel transmission opportunity (e.g., a third TX opportunity), and a fourth uplink signal / channel transmission opportunity (e.g., a fourth TX opportunity). A wireless device may transmit a transport block in the first uplink signal / channel transmission opportunity and the second uplink signal / channel transmission opportunity with / using a first transmission power. A wireless device may transmit a transport block in the third uplink signal / channel transmission opportunity and the fourth uplink signal / channel transmission opportunity with / using a second transmission power. For example, when the number of repetitions is equal to 8, multiple uplink signal / channel transmission opportunities may include a first uplink signal / channel transmission opportunity (e.g., the first TX opportunity), a second uplink signal / channel transmission opportunity (e.g., the second TX opportunity), a third uplink signal / channel transmission opportunity (e.g., the third TX opportunity), a fourth uplink signal / channel transmission opportunity (e.g., the fourth TX opportunity), a fifth uplink signal / channel transmission opportunity (e.g., the fifth TX opportunity), a sixth uplink signal / channel transmission opportunity (e.g., the sixth TX opportunity), a seventh uplink signal / channel transmission opportunity (e.g., the seventh TX opportunity), and an eighth uplink signal / channel transmission opportunity (e.g., the eighth TX opportunity). A wireless device may transmit the transport block in the first uplink signal / channel transmission opportunity, the second uplink signal / channel transmission opportunity, the fifth uplink signal / channel transmission opportunity, and the sixth uplink signal / channel transmission opportunity with / using a first transmission power. The wireless device may transmit transport blocks in the third uplink signal / channel transmission opportunity, the fourth uplink signal / channel transmission opportunity, the seventh uplink signal / channel transmission opportunity, and the eighth uplink signal / channel transmission opportunity with / using a second transmission power.

[0240] In one embodiment, a wireless device may transmit a transport block over / on / in / on / a multiple uplink signal / channel transmission opportunities with / using multiple transmission powers, based on one or more configuration parameters that represent a repeating scheme.

[0241] In the embodiment, one or more configuration parameters may include enable parameters (e.g., PUSCH repeat, PUCCH repeat, enableTwoPLForPUSCH repeat, enableTwoPowerControlForPUSCH repeat, etc.). Enable parameters may be set to "enabled". One or more configuration parameters may indicate "enabled" for an enable parameter. The value of an enable parameter may indicate / can indicate "enabled". Enable parameters may be for cells. Enable parameters may allow determination / selection of multiple transmission powers for a repeat of a transport block (e.g., PUSCH transmission). Enable parameters may allow determination / selection of multiple power control parameters (e.g., path loss compensation coefficient, target power level, closed-loop process number, etc.) for a repeat of a transport block. Enable parameters may allow determination / selection of multiple transmission powers for transmission of a transport block (e.g., PUSCH transmission). Enable parameters may allow determination / selection of multiple transmission powers for transmitting a transport block to / to multiple TRPs. In one embodiment, a wireless device may transmit a transport block over / on / in multiple uplink signal / channel transmission opportunities, based on one or more configuration parameters, including an activation parameter, which is set to enable, using / with multiple transmission powers.

[0242] In one embodiment, a wireless device may transmit a transport block over / in / on

[0243] In one embodiment, a wireless device may transmit a transport block over / in / on

[0244] DCI may include antenna port fields.

[0245] In one embodiment, the antenna port field may represent a DM-RS port within a code division multiplexing (CDM) group relative to the transport block.

[0246] In one embodiment, a wireless device may transmit a transport block over / in / onon / in / on / on / in / on / on / in / on / on / in / on / on / on / in / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on / on

[0247] In one embodiment, the antenna port field may represent DM-RS ports within at least two CDM groups.

[0248] A wireless device may transmit a transport block in an uplink signal / channel transmission opportunity (or uplink resource) with / using multiple transmission powers. A wireless device may transmit a first portion of a transport block (or one or more first data layers / streams or one or more first DM-RS portions or one or more first symbols) in an uplink signal / channel transmission opportunity (or in a first symbol of an uplink signal / channel transmission opportunity) with / using a first transmission power of multiple transmission powers. A wireless device may transmit a second portion of a transport block (or one or more second data layers / streams or one or more second DM-RS portions or one or more second symbols) in an uplink signal / channel transmission opportunity (or in a second symbol of an uplink signal / channel transmission opportunity) with / using a second transmission power of multiple transmission powers. A transport block may comprise a first portion and a second portion. A transport block may comprise one or more first data layers / streams and one or more second data layers / streams. A transport block may include one or more first symbols and one or more second symbols. For example, one or more first symbols may include symbols 0, 1, and 2 of the transport block, and one or more second symbols may include symbols 3, 4, and 5 of the transport block. A transport block may include symbols 0, 1, ..., 4, and 5. Opportunities for uplink signal / channel transmission may include first symbols and second symbols.

[0249] A wireless device may, for example, transmit a first portion of a transport block with / using a first transmission power and a second portion of a transport block with / using a second transmission power, based on the fact that the antenna port field indicates a DM-RS port in at least two CDM groups.

[0250] A wireless device may, for example, transmit a first portion of a transport block with a first transmission power and a second portion of a transport block with a second transmission power based on one or more fields of DCI.

[0251] A wireless device may, for example, transmit a first part of a transport block with / using a first transmission power and a second part of a transport block with / using a second transmission power, based on the repetition scheme being a repetition of a code / spatial domain (SDM / SFN in Figure 20).

[0252] In one embodiment, the first SRS resource set may include a first set of SRS resources (e.g., SRS resource 1, SRS resource 2). The second SRS resource set may include a second set of SRS resources (e.g., SRS resource 3, SRS resource 4).

[0253] A DCI may include two SRI fields (or two UL TCI fields or a single UL TCI field indicating two UL TCI status / SRI fields), including a first SRI field and a second SRI field. A DCI may include two SRI fields based on a first SRS resource set containing a first set of multiple SRS resources and a second SRS resource set containing a second set of multiple SRS resources. A DCI may include two SRI fields based on a first SRS resource set containing more than one SRS resource and a second SRS resource set containing more than one SRS resource.

[0254] In one embodiment, the first SRI field may indicate (or be mapped to) a first power control parameter set among one or more power control parameter sets. The value of the first SRI field may indicate the first power control parameter set. The value of the first SRI field may be equal to the first power control parameter set index among one or more power control parameter set indices that identify the first power control parameter set. The value of the first SRI field may be mapped to (or indicate) (or indicate) the first power control parameter set index. One or more configuration parameters may indicate, for example, a mapping between the first SRI field and the first power control parameter set. The mapping between the first SRI field and the first power control parameter set may, for example, be preconfigured / predefined / preset / fixed.

[0255] In one embodiment, the first power control parameter set may represent (or be mapped to) a first target power level set of one or more target power level sets. The first target power level set may include one or more values ​​(e.g., p0-List). The one or more values ​​may be for one or more target power levels (or target received power, or target received level). Each of the one or more values ​​may be for each of the target power levels of the one or more target power levels. The wireless device controls the first target power (or first target received power, P0) based on the first / starting / earliest value among the one or more values ​​in the first target power level set. O_UE_PUSCH、b、f、c (j)) can be determined. For example, when one or more values ​​(e.g., p0-List) = [7], the first / starting / earliest value is 7. When one or more values ​​(e.g., p0-List) = [9, 10], the first / starting / earliest value is 9. When one or more values ​​(e.g., p0-List) = [-5, 8], the first / starting / earliest value is -5.

[0256] In one embodiment, the first / starting / earliest value in one or more values ​​may include the first element / member in a vector / set containing one or more values. For example, if one or more values ​​= [value1, value2], the first / starting / earliest value may be "value1". If one or more values ​​= [value9, value8], the first / starting / earliest value may be "value9".

[0257] In one embodiment, the first power control parameter set may represent (or be mapped to) a first target power path loss compensation set of one or more target power path loss compensation sets.

[0258] In one embodiment, the first target power path loss compensation set may include a value for a target power level (e.g., p0). The wireless device may determine the first target power (or first target received power) based on this value. The value may be, for example, between -16 and 15. In one embodiment, the first target power path loss compensation set may include one or more values ​​(e.g., p0-List). The one or more values ​​may correspond to one or more target power levels (or target received power, or target received level). Each of the one or more values ​​may correspond to each of the target power levels of the one or more target power levels. The wireless device may determine the first target power (or first target received power) based on the first / initial / earliest value among the one or more values ​​in the first target power path loss compensation set.

[0259] In one embodiment, DCI may include an open-loop power control (OLPC) parameter set index field. The value of the open-loop power control parameter set index field may be equal to 1. The first SRI field may indicate (or be mapped to) a first target power level set of one or more target power level sets. The value of the first SRI field may indicate a first target power level set. The value of the first SRI field may be equal to a first target power level set index among one or more target power level set indices that identify the first target power level set. The value of the first SRI field may be mapped to (or indicate) a first target power level set index. One or more configuration parameters may indicate, for example, a mapping between the first SRI field and a first target power level. The mapping between the first SRI field and the first target power level may be, for example, pre-configured / pre-defined / pre-set / fixed. The first target power level set may include one or more values ​​(e.g., p0-List). One or more values ​​may correspond to one or more target power levels (or target received power, or target received level). Each of the one or more values ​​may correspond to each of the target power levels of the one or more target power levels. A wireless device may determine a first target power (or first target received power) based on the first / initial / earliest value among one or more values ​​in a first set of target power levels.

[0260] In one embodiment, the first target power path loss compensation set may include a value for a path loss compensation coefficient (e.g., alpha). A wireless device may determine the first path loss compensation coefficient based on this value. The value may be, for example, between 0 and 1 (e.g., [0,1]). In one embodiment, the first target power path loss compensation set may include one or more values ​​(e.g., alpha-List). The one or more values ​​may be for one or more path loss compensation coefficients. Each of the one or more values ​​may be for each of the one or more path loss compensation coefficients. A wireless device may determine the first path loss compensation coefficient based on the first / initial / earliest value among the one or more values ​​in the first target power path loss compensation set.

[0261] In one embodiment, the first power control parameter set may represent / create a value for a closed-loop process index (e.g., sri-PUSCH-ClosedLoopIndex). The wireless device may determine the first closed-loop process index based on the value. In one embodiment, the first power control parameter set may include one or more values ​​(e.g., sri-PUSCH-ClosedLoopIndex-List). The one or more values ​​may correspond to one or more closed-loop process indices. Each value of the one or more values ​​may correspond to each of the one or more closed-loop process indices. The wireless device may determine the first closed-loop process index based on the first / initial / earliest value among the one or more values ​​in the first power control parameter set.

[0262] In one embodiment, the second SRI field may indicate (or be mapped to) a second power control parameter set among one or more power control parameter sets. The value of the second SRI field may indicate a second power control parameter set. The value of the second SRI field may be equal to a second power control parameter set index among one or more power control parameter set indices that identify the second power control parameter set. The value of the second SRI field may be mapped to (or represent) a second power control parameter set index. One or more configuration parameters may indicate, for example, a mapping between the second SRI field and the second power control parameter set. The mapping between the second SRI field and the second power control parameter set may, for example, be preconfigured / predefined / pre-set / fixed.

[0263] In one embodiment, a wireless device may determine / calculate / calculate a first transmission power among a plurality of transmission powers based on a first target power. The wireless device may determine / calculate / calculate a first transmission power based on a first target power in response, for example, that the DCI includes a first SRI field.

[0264] In one embodiment, a wireless device may determine / calculate / calculate a first transmission power among a plurality of transmission powers based on a first path loss compensation coefficient. The wireless device may determine / calculate / calculate a first transmission power based on a first path loss compensation coefficient in response, for example, that the DCI includes a first SRI field.

[0265] In one embodiment, a wireless device may determine / calculate / calculate a first transmission power among a plurality of transmission powers based on a first closed-loop process index. The wireless device may determine / calculate / calculate a first transmission power based on a first closed-loop process index, for example, in response to the DCI including a first SRI field.

[0266] In one embodiment, the second power control parameter set may represent (or be mapped to) a second target power level set of one or more target power level sets. The second target power level set may include one or more values ​​(e.g., p0-List). The one or more values ​​may correspond to one or more target power levels (or target received power, or target received level). Each of the one or more values ​​may correspond to each of the target power levels of the one or more target power levels. In an embodiment, the wireless device may determine the second target power (or second target received power) based on the first / initial / earliest value among the one or more values ​​in the second target power level set. For example, when one or more values ​​(e.g., p0-List) = [7], the first / initial / earliest value is 7. When one or more values ​​(e.g., p0-List) = [9, 10], the first / initial / earliest value is 9. When one or more values ​​(e.g., p0-List) = [-5, 8], the first / start / earliest value is -5. In one embodiment, the wireless device determines the second target power (or second target received power, P) based on the second / second start / second earliest value of one or more values ​​in the second target power set. O_UE_PUSCH、b、f、c (j)) can be determined. For example, if one or more values ​​(e.g., p0-List) = [9, 10], the second / second earliest value of the second / second start is 10. When one or more values ​​(e.g., p0-List) = [-5, 8], the second / second earliest value of the second / second start is 8. In embodiments, a wireless device may determine a second target power (or second target received power) based on the third / third earliest value of one or more values ​​of a second target power level set. For example, if one or more values ​​(e.g., p0-List) = [9, 10, 12], the third / third earliest value of the third / third start is 12. When one or more values ​​(e.g., p0-List) = [-5, 8, -3], the third / third earliest value of the third / third start is -3.

[0267] In one embodiment, the second / second earliest value of one or more values ​​may be a second element / member in a vector / set containing one or more values. For example, if one or more values ​​= [value 1, value 2], the second / second earliest value of the second starting value may be "value 2". If one or more values ​​= [value 10, value 9], the second / second earliest value of the second starting value may be "value 9".

[0268] In one embodiment, the third / third-start / third-earliest value in one or more values ​​may be the third element / member in a vector / set containing one or more values. For example, when one or more values ​​= [value1, value2, value3], the third / third-start / third-earliest value may be "value3". When one or more values ​​= [value12, value9, value11], the third / third-start / third-earliest value may be "value11".

[0269] In one embodiment, the fourth / fourth-start / fourth-earliest value in one or more values ​​may be the fourth element / member in a vector / set containing one or more values. For example, when one or more values ​​= [value1, value2, value3, value4], the fourth / fourth-start / fourth-earliest value may be "value4". When one or more values ​​= [value8, value9, value11, value3], the fourth / fourth-start / fourth-earliest value may be "value3".

[0270] In the embodiment, the second power control parameter set may represent (or be mapped to) a second target power path loss compensation set of one or more target power path loss compensation sets.

[0271] In one embodiment, the second target power path loss compensation set may include a value for a target power level (e.g., p0). The wireless device may determine the second target power (or second target received power) based on this value. The value may be, for example, between -16 and 15. In one embodiment, the second target power path loss compensation set may include one or more values ​​(e.g., p0-List). The one or more values ​​may correspond to one or more target power levels (or target received power, or target received level). Each of the one or more values ​​may correspond to each of the target power levels of the one or more target power levels. The wireless device may determine the second target power (or second target received power) based on the second / second earliest value of the one or more values ​​in the second target power path loss compensation set. For example, if one or more values ​​(e.g., p0-List) = [9, 10], then the second / second earliest value is 10. When one or more values ​​(for example, p0-List) = [-5, 8], the second / second start / second earliest value is 8.

[0272] In one embodiment, DCI may include an open-loop power control parameter set index field. The value of the open-loop power control parameter set index field may be 1. A second SRI field may indicate (or be mapped to) a second target power level set of one or more target power level sets. The value of the second SRI field may indicate a second target power level set. The value of the second SRI field may be equal to a second target power level set index among one or more target power level set indices that identify the second target power level set. The value of the second SRI field may be mapped to (or indicate) a second target power level set index. One or more configuration parameters may indicate, for example, a mapping between the second SRI field and a second target power level. The mapping between the second SRI field and the second target power level may be, for example, pre-configured / pre-defined / pre-set / fixed. The second target power level set may include one or more values ​​(e.g., p0-List). One or more values ​​may correspond to one or more target power levels (or target received power, or target received level). Each of the one or more values ​​may correspond to each of the target power levels of the one or more target power levels. The wireless device may determine a second target power (or second target received power) based on the first / start / earliest value among one or more values ​​in the second target power level set. The wireless device may determine a second target power (or second target received power) based on the second / second start / second earliest value among one or more values ​​in the second target power level set. The wireless device may determine a second target power (or second target received power) based on the third / third start / third earliest value among one or more values ​​in the second target power level set.

[0273] In one embodiment, the second target power path loss compensation set may include a value for a path loss compensation coefficient (e.g., alpha). The wireless device may determine the second path loss compensation coefficient based on this value. The value may be, for example, between 0 and 1 (e.g., [0,1]). In one embodiment, the second target power path loss compensation set may include one or more values ​​(e.g., alpha-List). The one or more values ​​may correspond to one or more path loss compensation coefficients. Each of the one or more values ​​may correspond to each of the one or more path loss compensation coefficients. The wireless device may determine the second path loss compensation coefficient based on the second / second start / second earliest value among the one or more values ​​of the second target power path loss compensation set.

[0274] In one embodiment, a second power control parameter set may display / create values ​​for closed-loop process indices (e.g., sri-PUSCH-ClosedLoopIndex). A wireless device may determine the second closed-loop process index based on these values. In one embodiment, the second power control parameter set may include one or more values ​​(e.g., sri-PUSCH-ClosedLoopIndex-List). The one or more values ​​may correspond to one or more closed-loop process indices. Each value in the one or more values ​​may correspond to one or more closed-loop process indices. A wireless device may determine the second closed-loop process index based on the second / second earliest value of one or more values ​​in the second power control parameter set.

[0275] In one embodiment, a wireless device may determine / calculate / calculate a second transmission power among a plurality of transmission powers based on a second target power. The wireless device may determine / calculate / calculate a second transmission power based on a second target power in response, for example, that the DCI includes a second SRI field.

[0276] In one embodiment, a wireless device may determine / calculate / calculate a second transmission power among multiple transmission powers based on a second path loss compensation coefficient. The wireless device may determine / calculate / calculate a second transmission power based on a second path loss compensation coefficient, for example, in response to the DCI including a second SRI field.

[0277] In one embodiment, a wireless device may determine / calculate / calculate a second transmission power among a plurality of transmission powers based on a second closed-loop process index. The wireless device may determine / calculate / calculate a second transmission power based on a second closed-loop process index, for example, in response to the DCI including a second SRI field.

[0278] In Figures 17 and 19, the first SRS resource set may include a single SRS resource (e.g., SRS resource 1). The second SRS resource set may include multiple SRS resources (e.g., SRS resource 3, SRS resource 4). The DCI may not include a first SRI field (or first TCI field) based on a first SRS resource set containing a single SRS resource. The DCI may include a second SRI field (or second TCI field) based on a second SRS resource set containing multiple SRS resources. The DCI may include a second SRI field based on a second SRS resource set containing more than one SRS resource.

[0279] In Figures 17 and 19, the first SRS resource set may include, for example, a single SRS resource (e.g., SRS resource 1 in Figure 17). The second SRS resource set may include, for example, a single SRS resource (e.g., SRS resource set 2 in Figure 17). A DCI may not include the first SRI field (or first TCI field) based on the first SRS resource set which includes a single SRS resource. A DCI may not include the second SRI field (or second TCI field) based on the second SRS resource set which includes a single SRS resource. A DCI may not include the first SRI field based on the first SRS resource set which does not include more than one SRS resource. A DCI may not include the second SRI field based on the second SRS resource set which does not include more than one SRS resource. A DCI may not include the first and second SRI fields (e.g., SRI fields not shown in Figure 17).

[0280] In Figures 18 and 19, one or more configuration parameters may not represent, for example, one or more power control parameter sets (e.g., SRI-PUSCH-PowerControl). For example, DCI may or may not include a first SRI field. For example, DCI may or may not include a second SRI field.

[0281] The wireless device may determine a first default target power.

[0282] In Figures 17 and 19, the wireless device may determine a first default target power based on the fact that the DCI does not include a first SRI field.

[0283] In Figures 18 and 19, the wireless device may determine a first default target power based on the fact that one or more configuration parameters do not indicate one or more sets of power control parameters.

[0284] One or more configuration parameters may indicate, for example, a target power level setting list (e.g., p0-PUSCH-SetList). One or more configuration parameters may indicate one or more target power level sets (e.g., P0-PUSCH-Set). The DCI may include, for example, an open-loop power control parameter set index field. The wireless device may determine a first default target power based on the fact that one or more configuration parameters indicate one or more target power level sets. The wireless device may determine a first default target power based on the fact that the DCI includes an open-loop power control parameter set index field.

[0285] In one embodiment, the value of the open-loop power control parameter set index field may be (equal to) "0". In one embodiment, the value of the open-loop power control parameter set index field may be (equal to) "00". A wireless device may determine a first default target power based on a first target power path loss compensation set among one or more target power path loss compensation sets. The first target power path loss compensation set may be the first / starting / earliest target power path loss compensation set among one or more target power path loss compensation sets. The first target power path loss compensation set may be the first / starting / earliest target power path loss compensation set in the target power path loss compensation set list. For example, when the target power path loss compensation set list = [P0-PUSCH-AlphaSet1, P0-PUSCH-AlphaSet2, P0-PUSCH-AlphaSet3], the first target power path loss compensation set is P0-PUSCH-AlphaSet1. When the target power path loss compensation set list = [P0-PUSCH-AlphaSet2, P0-PUSCH-AlphaSet1, P0-PUSCH-AlphaSet3], the first target power path loss compensation set is P0-PUSCH-AlphaSet2. One or more target power path loss compensation sets include P0-PUSCH-AlphaSet1, P0-PUSCH-AlphaSet2, and P0-PUSCH-AlphaSet3. In one embodiment, the first target power path loss compensation set may include a value for the target power level (e.g., p0). The wireless device may determine a first default target power based on this value. In one embodiment, the first target power path loss compensation set may include one or more values ​​(e.g., p0-List). The wireless device may determine a first default target power based on the first / starting / earliest value among one or more values ​​in the first target power path loss compensation set.

[0286] In one embodiment, the value of the open-loop power control parameter set index field may be (equal to) "1". In one embodiment, the value of the open-loop power control parameter set index field may be (equal to) "01". The wireless device may determine a first default target power based on a first target power level set of one or more target power level sets. The first target power level set may be identified / indicated by the lowest first target power level set index among one or more target power level set indices of one or more target power level sets. One or more target power level set indices may include the first target power level set index. The first target power level set may include one or more values ​​(e.g., p0-List). The wireless device may determine a first default target power based on the first / starting / earliest value among one or more values ​​in the first target power level set.

[0287] In one embodiment, the value of the open-loop power control parameter set index field may be (equal to) "10". The wireless device may determine a first default target power based on a first target power level set of one or more target power level sets. The first target power level set may be identified / indicated by the lowest first target power level set index among one or more target power level set indices of one or more target power level sets. One or more target power level set indices may include the first target power level set index. The first target power level set may include one or more values ​​(e.g., p0-List). The wireless device may determine a first default target power based on the second / second earliest value of one or more values ​​of the first target power level set.

[0288] One or more configuration parameters may not indicate, for example, a target power level setting list (e.g., p0-PUSCH-SetList). One or more configuration parameters may not indicate one or more target power level sets (e.g., P0-PUSCH-Set). DCI may not include, for example, an open-loop power control parameter set index field. A wireless device may determine a first default target power based on a first target power path loss compensation set among one or more target power path loss compensation sets. The first target power path loss compensation set may be the first / starting / earliest target power path loss compensation set among one or more target power path loss compensation sets. The first target power path loss compensation set may be the first / starting / earliest target power path loss compensation set in a target power path loss compensation set list. In one embodiment, the first target power path loss compensation set may include a value for a target power level (e.g., p0). A wireless device may determine a first default target power based on this value. In one embodiment, the first target power path loss compensation set may include one or more values ​​(e.g., p0-List). The wireless device may determine the first default target power based on the first / start / earliest value among the one or more values ​​in the first target power path loss compensation set. The wireless device may determine the first default target power based on the fact that one or more configuration parameters do not indicate one or more target power level sets. The wireless device may determine the first default target power based on the fact that DCI does not include the open-loop power control parameter set index field.

[0289] The wireless device may determine a first default path loss compensation coefficient.

[0290] In Figures 17 and 19, the wireless device may determine a first default path loss compensation coefficient based on the fact that the DCI does not include a first SRI field.

[0291] In Figures 18 and 19, the wireless device may determine a first default path loss compensation coefficient based on the fact that one or more configuration parameters do not indicate one or more sets of power control parameters.

[0292] A wireless device may determine a first default path loss compensation coefficient based on a first target power path loss compensation set from among one or more target power path loss compensation sets. The first target power path loss compensation set may be the first / starting / earliest target power path loss compensation set from among one or more target power path loss compensation sets. The first target power path loss compensation set may be the first / starting / earliest target power path loss compensation set in the target power path loss compensation set list. For example, when the target power path loss compensation set list = [P0-PUSCH-AlphaSet1, P0-PUSCH-AlphaSet2, P0-PUSCH-AlphaSet3], the first target power path loss compensation set is P0-PUSCH-AlphaSet1. When the target power path loss compensation set list = [P0-PUSCH-AlphaSet3, P0-PUSCH-AlphaSet2, P0-PUSCH-AlphaSet1], the first target power path loss compensation set is P0-PUSCH-AlphaSet3. One or more target power path loss compensation sets include P0-PUSCH-AlphaSet1, P0-PUSCH-AlphaSet2, and P0-PUSCH-AlphaSet3. In one embodiment, the first target power path loss compensation set may include a value for the path loss compensation coefficient (e.g., alpha). The wireless device may determine a first default path loss compensation coefficient based on this value. In one embodiment, the first target power path loss compensation set may include one or more values ​​(e.g., alpha-List). The wireless device may determine a first default path loss compensation coefficient based on the first / initial / earliest value among one or more values ​​in the first target power path loss compensation set.

[0293] The wireless device may determine a first default closed-loop process index.

[0294] In Figures 17 and 19, the wireless device may determine a first default closed-loop process index based on the fact that the DCI does not include a first SRI field. The value of the first default closed-loop process index may be equal to a first value, which could be equal to, for example, 0 (e.g., l=0).

[0295] In Figures 18 and 19, the wireless device may determine a first default closed-loop process index based on the fact that one or more configuration parameters do not indicate one or more sets of power control parameters.

[0296] In one embodiment, a wireless device may determine / calculate / calculate a first transmission power among a plurality of transmission powers based on a first default target power. The wireless device may determine / calculate / calculate a first transmission power based on a first default target power in response, for example, that the DCI does not include a first SRI field. The wireless device may determine / calculate / calculate a first transmission power based on a first default target power in response, for example, that one or more configuration parameters do not indicate one or more power control parameter sets.

[0297] In one embodiment, a wireless device may determine / calculate / calculate a first transmission power among a plurality of transmission powers based on a first default path loss compensation coefficient. The wireless device may determine / calculate / calculate a first transmission power based on a first default path loss compensation coefficient in response, for example, that the DCI does not include a first SRI field. The wireless device may determine / calculate / calculate a first transmission power based on a first default path loss compensation coefficient in response, for example, that one or more configuration parameters do not indicate one or more power control parameter sets.

[0298] In one embodiment, a wireless device may determine / calculate / calculate a first transmission power among a plurality of transmission powers based on a first default closed-loop process index. The wireless device may determine / calculate / calculate a first transmission power based on a first default closed-loop process index in response, for example, that the DCI does not include a first SRI field. The wireless device may determine / calculate / calculate a first transmission power based on a first default closed-loop process index in response, for example, that one or more configuration parameters do not indicate one or more power control parameter sets.

[0299] In Figures 17 and 19, the first SRS resource set may include, for example, multiple SRS resources (e.g., SRS resource 1 and SRS resource 2). The second SRS resource set may include a single SRS resource (e.g., SRS resource 3). The DCI may not include a second SRI field (or second TCI field) based on a second SRS resource set containing a single SRS resource. The DCI may include a first SRI field (or first TCI field) based on a first SRS resource set containing multiple SRS resources. The DCI may include a first SRI field based on a first SRS resource set containing more than one SRS resource.

[0300] In Figures 17 and 19, the first SRS resource set may include, for example, a single SRS resource (e.g., SRS resource 1 in Figure 17). The second SRS resource set may include a single SRS resource (e.g., SRS resource set 2 in Figure 17). A DCI may not include the first SRI field (or first TCI field) based on the first SRS resource set which includes a single SRS resource. A DCI may not include the second SRI field (or second TCI field) based on the second SRS resource set which includes a single SRS resource. A DCI may not include the first SRI field based on the first SRS resource set which does not include more than one SRS resource. A DCI may not include the second SRI field based on the second SRS resource set which does not include more than one SRS resource. A DCI may not include the first and second SRI fields (e.g., SRI fields not shown in Figure 17).

[0301] In Figures 18 and 19, one or more configuration parameters may not represent, for example, one or more power control parameter sets (e.g., SRI-PUSCH-PowerControl). For example, DCI may or may not include a first SRI field. For example, DCI may or may not include a second SRI field.

[0302] The wireless device may determine a second default target power.

[0303] In Figures 17 and 19, the wireless device may determine a second default target power based on the fact that the DCI does not include a second SRI field.

[0304] In Figures 18 and 19, the wireless device may determine a second default target power based on the fact that one or more configuration parameters do not indicate one or more sets of power control parameters.

[0305] One or more configuration parameters may indicate, for example, a target power level setting list (e.g., p0-PUSCH-SetList). One or more configuration parameters may indicate one or more target power level sets (e.g., P0-PUSCH-Set). The DCI may include, for example, an open-loop power control parameter set index field. The wireless device may determine a second default target power based on the fact that one or more configuration parameters indicate one or more target power level sets. The wireless device may determine a second default target power based on the fact that the DCI includes an open-loop power control parameter set index field.

[0306] In one embodiment, the value of the open-loop power control parameter set index field may be (equal to) "0". In one embodiment, the value of the open-loop power control parameter set index field may be (equal to) "00". A wireless device may determine a second default target power based on a first target power path loss compensation set among one or more target power path loss compensation sets. The first target power path loss compensation set may be the first / starting / earliest target power path loss compensation set among one or more target power path loss compensation sets. The first target power path loss compensation set may be the first / starting / earliest target power path loss compensation set in the target power path loss compensation set list. For example, when the target power path loss compensation set list = [P0-PUSCH-AlphaSet1, P0-PUSCH-AlphaSet2, P0-PUSCH-AlphaSet3], the first target power path loss compensation set is P0-PUSCH-AlphaSet1. One or more target power path loss compensation sets include P0-PUSCH-AlphaSet1, P0-PUSCH-AlphaSet2, and P0-PUSCH-AlphaSet3. In one embodiment, the first target power path loss compensation set may include a value for the target power level (e.g., p0). The wireless device may determine a second default target power based on this value. In one embodiment, the first target power path loss compensation set may include one or more values ​​(e.g., p0-List). The wireless device may determine a second default target power based on the second / second-start / second-earliest value among one or more values ​​in the first target power path loss compensation set. The wireless device may determine a second default target power based on a second target power path loss compensation set among one or more target power path loss compensation sets. The second target power path loss compensation set may be the second / second-start / second-earliest target power path loss compensation set among one or more target power path loss compensation sets.The second target power-path loss compensation set may be the second / second-start / second-earliest target power-path loss compensation set in the target power-path loss compensation set list. For example, when the target power-path loss compensation set list = [P0-PUSCH-AlphaSet1, P0-PUSCH-AlphaSet2, P0-PUSCH-AlphaSet3], the second target power-path loss compensation set is P0-PUSCH-AlphaSet2. When the target power-path loss compensation set list = [P0-PUSCH-AlphaSet2, P0-PUSCH-AlphaSet3, P0-PUSCH-AlphaSet1], the second target power-path loss compensation set is P0-PUSCH-AlphaSet3. One or more target power-path loss compensation sets include P0-PUSCH-AlphaSet1, P0-PUSCH-AlphaSet2, and P0-PUSCH-AlphaSet3. In one embodiment, the second target power path loss compensation set may include a value (e.g., p0). The wireless device may determine a second default target power based on the value in the second target power path loss compensation set.

[0307] In one embodiment, the value of the open-loop power control parameter set index field may be (equal to) "1". In one embodiment, the value of the open-loop power control parameter set index field may be (equal to) "01". The wireless device may determine a second default target power based, for example, on a first target power level set of one or more target power level sets. The first target power level set may be identified / indicated by the lowest first target power level set index among one or more target power level set indices of one or more target power level sets. One or more target power level set indices may include the first target power level set index. The first target power level set may include one or more values ​​(e.g., p0-List). The wireless device may determine a second default target power based on the third / third earliest value among one or more values ​​of the first target power level set. The wireless device may determine a second default target power based, for example, on a second target power level set of one or more target power level sets. A second target power level set may be identified / indicated, for example, by the second lowest second target power level set index among one or more target power level set indices of one or more target power level sets. A second target power level set may be identified / indicated, for example, by the highest second target power level set index among one or more target power level set indices of one or more target power level sets. One or more target power level set indices may include a second target power level set index. A second target power level set may include one or more values ​​(e.g., p0-List). A wireless device may determine a second default target power based on the first / starting / earliest value among one or more values ​​in the second target power level set.

[0308] For example, one or more target power level sets may include a first target power level set identified / indicated by a first target power level set index. One or more target power level sets may include a second target power level set identified / indicated by a second target power level set index. One or more target power level sets may comprise a third target power level set identified / indicated by a third target power level set index. One or more target power level set indices may include a first target power level set index, a second target power level set index, and a third target power level set index. For example, when first target power level setting index > second target power level setting index > third target power level setting index, the second target power level setting index is identified / indicated by the second lowest second target power level setting index among the first target power level setting index, the second target power level setting index, and the third target power level setting index. For example, when the third target power level setting index > the first target power level setting index > the second target power level setting index, the first target power level setting index is identified / indicated by the second lowest first target power level setting index among the first, second, and third target power level setting indexes.

[0309] In one embodiment, the value of the open-loop power control parameter set index field may be (equal to) "10". The wireless device may determine a second default target power based, for example, on a first target power level set of one or more target power level sets. The first target power level set may be identified / indicated by the lowest first target power level set index among one or more target power level set indices of one or more target power level sets. One or more target power level set indices may include the first target power level set index. The first target power level set may include one or more values ​​(e.g., p0-List). The wireless device may determine a second default target power based on the fourth / fourth earliest value among one or more values ​​of the first target power level set. The wireless device may determine a second default target power based, for example, on a second target power level set of one or more target power level sets. A second target power level set may be identified / indicated, for example, by the second lowest second target power level set index among one or more target power level set indices of one or more target power level sets. A second target power level set may be identified / indicated, for example, by the highest second target power level set index among one or more target power level set indices of one or more target power level sets. One or more target power level set indices may include a second target power level set index. A second target power level set may include one or more values ​​(e.g., p0-List). A wireless device may determine a second default target power based on the second / second earliest value of one or more values ​​of the second target power level set.

[0310] One or more configuration parameters may not indicate, for example, a target power level setting list (e.g., p0-PUSCH-SetList). One or more configuration parameters may not indicate one or more target power level sets (e.g., P0-PUSCH-Set). DCI may not include, for example, an open-loop power control parameter set index field. A wireless device may determine a second default target power based on a first target power path loss compensation set among one or more target power path loss compensation sets. The first target power path loss compensation set may be the first / starting / earliest target power path loss compensation set among one or more target power path loss compensation sets. The first target power path loss compensation set may be the first / starting / earliest target power path loss compensation set in a target power path loss compensation set list. In one embodiment, the first target power path loss compensation set may include one or more values ​​(e.g., p0-List). A wireless device may determine a second default target power based on the second / second earliest starting value among one or more values ​​in a first target power path loss compensation set. The wireless device may determine a second default target power based on a second target power path loss compensation set among one or more target power path loss compensation sets. The second target power path loss compensation set may be the second / second earliest starting value among one or more target power path loss compensation sets. The second target power path loss compensation set may be the second / second earliest starting value in the target power path loss compensation set list. In one embodiment, the second target power path loss compensation set may include a value (e.g., p0). The wireless device may determine a second default target power based on a value in the second target power path loss compensation set. The wireless device may determine a second default target power based on one or more configuration parameters not indicating one or more target power level sets.The wireless device may determine a second default target power based on the fact that DCI does not include an open-loop power control parameter set index field.

[0311] The wireless device may determine a second default path loss compensation coefficient.

[0312] In Figures 17 and 19, the wireless device may determine a second default path loss compensation coefficient based on the fact that DCI does not include a second SRI field.

[0313] In Figures 18 and 19, the wireless device may determine a second default path loss compensation coefficient based on the fact that one or more configuration parameters do not indicate one or more sets of power control parameters.

[0314] A wireless device may determine a second default path loss compensation coefficient based on a first target power loss compensation set from among one or more target power loss compensation sets. The first target power path loss compensation set may be the first / starting / earliest target power path loss compensation set from among one or more target power path loss compensation sets. The first target power path loss compensation set may be the first / starting / earliest target power path loss compensation set from a target power path loss compensation set list. In one embodiment, the first target power path loss compensation set may include one or more values ​​(e.g., alpha-List). A wireless device may determine a second default path loss compensation coefficient based on the second / second-starting / second-earliest value from one or more values ​​in the first target power path loss compensation set. A wireless device may determine a second default path loss compensation coefficient based on a second target power loss compensation set configured from among one or more target power loss compensation sets. The second target power path loss compensation set may be the second / second-start / second-earliest target power path loss compensation set among one or more target power path loss compensation sets. The second target power path loss compensation set may be the second / second-start / second-earliest target power path loss compensation set in the target power path loss compensation set list. In one embodiment, the second target power path loss compensation set may include a value (e.g., alpha). The wireless device may determine a second default path loss compensation coefficient based on the value of the second target power loss compensation set.

[0315] The wireless device may determine a second default closed-loop process index.

[0316] In Figures 17 and 19, the wireless device may determine a second default closed-loop process index based on the fact that the DCI does not include a second SRI field. The value of the second default closed-loop process index may be equal to the second value, which could be, for example, 1 (e.g., l=1).

[0317] In Figures 18 and 19, the wireless device may determine a second default closed-loop process index based on the fact that one or more configuration parameters do not indicate one or more sets of power control parameters.

[0318] In one embodiment, a wireless device may determine / calculate / calculate a second transmission power among a plurality of transmission powers based on a second default target power. The wireless device may determine / calculate / calculate a second transmission power based on a second default target power in response, for example, that the DCI does not include a second SRI field. The wireless device may determine / calculate / calculate a second transmission power based on a second default target power in response, for example, that one or more configuration parameters do not indicate one or more power control parameter sets.

[0319] In one embodiment, a wireless device may determine / calculate / calculate a second transmission power among multiple transmission powers based on a second default path loss compensation coefficient. The wireless device may determine / calculate / calculate a second transmission power based on a second default path loss compensation coefficient in response, for example, that the DCI does not include a second SRI field. The wireless device may determine / calculate / calculate a second transmission power based on a second default path loss compensation coefficient in response, for example, that one or more configuration parameters do not indicate one or more power control parameter sets.

[0320] In one embodiment, a wireless device may determine / calculate / calculate a second transmission power among multiple transmission powers based on a second default closed-loop process index. The wireless device may determine / calculate / calculate a second transmission power based on a second default closed-loop process index in response, for example, that the DCI does not include a second SRI field. The wireless device may determine / calculate / calculate a second transmission power based on a second default closed-loop process index in response, for example, that one or more configuration parameters do not indicate one or more power control parameter sets.

[0321] A wireless device may transmit a transport block (or a first portion of a transport block or one or more first data layers / streams of a transport block) with / using a first transmission power. A wireless device may transmit a transport block with / using a first transmission power during one or more first uplink signal / channel transmission opportunities (e.g., times T2a and T2c in Figures 17-19). A wireless device may transmit a transport block (or a second portion of a transport block or one or more second data layers / streams of a transport block) with / using a second transmission power. A wireless device may transmit a transport block with / using a second transmission power during one or more second uplink signal / channel transmission opportunities (e.g., times T2b and T2d in Figures 17-19).

[0322] Wireless devices can transmit transport blocks via the cell's active uplink BWP.

[0323] A wireless device may determine a first default target power (and / or a first default path loss compensation coefficient and / or a first default closed-loop process index) based, for example, on one or more configuration parameters indicating at least two SRS resource sets using SRS usage parameters set in a codebook.

[0324] A wireless device may determine a second default target power (and / or a second default path loss compensation coefficient and / or a second default closed-loop process index) based, for example, on one or more configuration parameters indicating at least two sets of SRS resources using SRS usage parameters set in a codebook.

[0325] In one embodiment, a wireless device is supplied to (e.g., transmits to and / or receives from) multiple TRPs. Based on being supplied by the multiple TRPs, the wireless device may determine a first default target power (and / or a first default path loss compensation coefficient and / or a first default closed-loop process index) and a second default target power (and / or a second default path loss compensation coefficient and / or a second default closed-loop process index). Based on being supplied by the multiple TRPs, the wireless device may determine a first default target power (and / or a first default path loss compensation coefficient and / or a first default closed-loop process index). Based on being supplied by the multiple TRPs, the wireless device may determine a second default target power (and / or a second default path loss compensation coefficient and / or a second default closed-loop process index).

[0326] A wireless device may determine a first default target power (and / or a first default path loss compensation factor and / or a first default closed-loop process index) and a second default target power (and / or a second default path loss compensation factor and / or a second default closed-loop process index) for multiple TRPs, for example, based on the DCI (one or more fields of the DCI) indicating a repeating transport block.

[0327] A wireless device may determine a first default target power (and / or a first default path loss compensation coefficient and / or a first default closed-loop process index) based on the DCI (one or more fields of the DCI) indicating, for example, a repetition of transport blocks toward / to multiple TRPs.

[0328] A wireless device may determine a second default target power (and / or a second default path loss compensation coefficient and / or a second default closed-loop process index) based on the DCI (one or more fields of the DCI) indicating, for example, a repetition of transport blocks toward / to multiple TRPs.

[0329] In one embodiment, a wireless device may determine a first default target power (and / or a first default path loss compensation factor and / or a first default closed-loop process index) and a second default target power (and / or a second default path loss compensation factor and / or a second default closed-loop process index) based on one or more configuration parameters including an enable parameter. The enable parameter may be set to "enabled". One or more configuration parameters may indicate "enabled" for the enable parameter.

[0330] In one embodiment, a wireless device may determine a first default target power (and / or a first default path loss compensation coefficient and / or a first default closed-loop process index) based on one or more configuration parameters including an enable parameter. The enable parameter may be set to "enabled". One or more configuration parameters may indicate "enabled" for the enable parameter.

[0331] In the embodiment, the wireless device may determine a second default target power (and / or a second default path loss compensation coefficient and / or a second default closed-loop process index) based on one or more configuration parameters including an enable parameter. The enable parameter may be set to "enabled". One or more configuration parameters may indicate "enabled" for the enable parameter.

[0332] In the embodiment, the wireless device may determine a first default target power (and / or a first default path loss compensation coefficient and / or a first default closed-loop process index) and a second default target power (and / or a second default path loss compensation coefficient and / or a second default closed-loop process index) based on one or more configuration parameters indicating a repetition scheme (e.g., FDM-Scheme, TDM-Scheme, SDM-Scheme, CDM-Scheme). The repetition scheme may be for the repetition of transport block transmissions (e.g., PUSCH repetition).

[0333] In one embodiment, a wireless device may determine a first default target power (and / or a first default path loss correction factor and / or a first default closed-loop process index) based on one or more configuration parameters that indicate a repetition scheme (e.g., FDM-Scheme, TDM-Scheme, SDM-Scheme, CDM-Scheme). The repetition scheme may be for the repetition of transmission in a transport block (e.g., PUSCH repetition).

[0334] In one embodiment, a wireless device may determine a second default target power (and / or a second default path loss correction factor and / or a second default closed-loop process index) based on one or more configuration parameters that indicate a repetition scheme (e.g., FDM-Scheme, TDM-Scheme, SDM-Scheme, CDM-Scheme). The repetition scheme may be for the repetition of transmission in a transport block (e.g., PUSCH repetition).

[0335] In the embodiment, the wireless device may determine a first default target power (and / or a first default path loss compensation factor and / or a first default closed-loop process index) and a second default target power (and / or a second default path loss compensation factor and / or a second default closed-loop process index) based on the UE's capability information indicating / including be...

Claims

1. It is a method, The wireless device receives downlink control information (DCI) that schedules a physical uplink shared channel (PUCH), In response to the DCI not including a Sounding Reference Signal Resource Indicator (SRI) field based on the number of SRS resources in the SRS resource set, A first iteration of the PUSCH using a first transmission power determined based on a first power control parameter set including a first target received power, The second iteration of the PUSCH uses a second transmission power determined based on a second power control parameter set including a second target received power, and To transmit and Methods that include...

2. Receiving a second DCI to schedule a second PUSCH, In response that the second DCI includes the first SRI field and the second SRI field, The first iteration of the second PUSCH using a third transmission power determined based on a third power control parameter set indicated by the first SRI field, The second iteration of the second PUSCH uses a fourth transmission power determined based on the fourth power control parameter set indicated by the second SRI field and To transmit and The method according to claim 1, further comprising:

3. The wireless device further includes receiving one or more configuration parameters indicating a list of power control parameter sets, including the first power control parameter set and the second power control parameter set. The first power control parameter set is the first to occur on the list of power control parameter sets, The method according to claim 1, wherein the second power control parameter set is the second to occur on the list of power control parameter sets.

4. The first power control parameter set further includes a first path loss compensation coefficient value, The method according to claim 1, wherein the second power control parameter set further includes a second path loss compensation coefficient value.

5. The method according to claim 1, wherein the DCI is determined not to include the SRI field based on the fact that the number of SRS resources in the SRS resource set is 1.

6. The method according to claim 5, further comprising receiving one or more configuration parameters indicating SRS usage parameters for the SRS resource set.

7. Transmitting the first repetition includes transmitting the first repetition at the first transmission opportunity, The method according to claim 1, wherein transmitting the second repetition includes transmitting the second repetition on a second transmission opportunity.

8. The method according to claim 1, further comprising selecting a first power control parameter set based on a first SRS resource set and selecting a second power control parameter set based on a second SRS resource set.

9. A wireless device, One or more processors, The memory that stores the instructions and Equipped with, When the instruction is executed by one or more processors, Receiving downlink control information (DCI) to schedule a physical uplink shared channel (PUSCH), In response to the DCI not including a Sounding Reference Signal Resource Indicator (SRI) field based on the number of SRS resources in the SRS resource set, A first iteration of the PUSCH using a first transmission power determined based on a first power control parameter set including a first target received power, The second iteration of the PUSCH uses a second transmission power determined based on a second power control parameter set including a second target received power, and To transmit and A wireless device that causes the aforementioned wireless device to perform the above action.

10. The aforementioned instruction is, Receiving a second DCI to schedule a second PUSCH, In response that the second DCI includes the first SRI field and the second SRI field, The first iteration of the second PUSCH using a third transmission power determined based on a third power control parameter set indicated by the first SRI field, The second iteration of the second PUSCH uses a fourth transmission power determined based on the fourth power control parameter set indicated by the second SRI field and To transmit and The wireless device according to claim 9, further having the wireless device perform the above.

11. The instruction further causes the wireless device to receive one or more configuration parameters indicating a list of power control parameter sets, including the first power control parameter set and the second power control parameter set. The first power control parameter set is the first to occur on the list of power control parameter sets, The wireless device according to claim 9, wherein the second power control parameter set occurs second on the list of the power control parameter set.

12. The first power control parameter set further includes a first path loss compensation coefficient value, The wireless device according to claim 9, wherein the second power control parameter set further includes a second path loss compensation coefficient value.

13. The wireless device according to claim 9, wherein the DCI is determined not to include the SRI field based on the number of SRS resources in the SRS resource set being 1.

14. The wireless device according to claim 13, wherein the instruction further causes the wireless device to receive one or more configuration parameters indicating SRS usage parameters for the SRS resource set.

15. The aforementioned instruction is, In the first transmission opportunity, the first repetition is transmitted, In the second transmission opportunity, the second repetition is transmitted. The wireless device according to claim 9, further having the wireless device perform the above.

16. The aforementioned instruction is, Selecting the first power control parameter set based on the first SRS resource set, Selecting the second power control parameter set based on the second SRS resource set and The wireless device according to claim 9, further having the wireless device perform the above.

17. It is a system, A base station comprising one or more first processors and a first memory storing first instructions, wherein the first instructions, when executed by the one or more first processors, cause the base station to transmit downlink control information (DCI) that schedules a physical uplink shared channel (PUSCH), A wireless device comprising one or more second processors and a second memory storing second instructions, wherein the second instructions are executed by the one or more second processors. Receiving the aforementioned DCI, In response to the DCI not including a Sounding Reference Signal (SRS) Resource Indicator (SRI) field based on the number of SRS resources in the SRS resource set, A first iteration of the PUSCH using a first transmission power determined based on a first power control parameter set including a first target received power, The second iteration of the PUSCH uses a second transmission power determined based on a second power control parameter set including a second target received power, and To transmit and The wireless device is made to perform the above, and A system equipped with these features.

Images