Resource determination in control channel repetition - Patents.com

Abstract

A wireless device may receive at least one repetition of downlink control information (DCI) that triggers an acknowledgement message via at least one control resource set (core set) of a core set configured for DCI repetition. The wireless device may transmit the acknowledgement message via a physical uplink control channel (PUCCH) resource based on an index of a starting control channel element (CCE) of the core set among the core sets associated with the search space set identified by the lowest search space set index and the number of CCEs in the core set.

Description

[Background technology]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of U.S. Provisional Patent Application No. 63 / 088,136, filed October 6, 2020, which is incorporated herein by reference in its entirety. Summary of the Invention [Means for solving the problem]

[0002] Detailed Description of the Invention In this disclosure, various embodiments are presented as examples of how the disclosed technology may be implemented and / or how the disclosed technology may be practiced in environments and scenarios. It will be apparent to those skilled in the relevant art that various changes in form and details can be made without departing from the scope. Indeed, after reading the specification, it will become apparent to those skilled in the relevant art how to implement alternative embodiments. The present embodiments should not be limited by any of the exemplary embodiments. Embodiments of the present disclosure are described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed exemplary embodiments may be combined to create further embodiments within the scope of the present disclosure. Figures highlighting features and advantages are shown by way of example only. The disclosed architecture is sufficiently flexible and configurable to be utilized in ways other than those shown. For example, the actions listed in any flowchart may be rearranged or used only optionally in some embodiments. The present invention provides, for example, the following. (Item 1) monitoring, by a wireless device, a plurality of control resource sets (core sets) for repetition of downlink control information (DCI); receiving at least one repetition of the DCI via at least one core set of the plurality of core sets, the repetition triggering transmission of a Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK); selecting a core set from the plurality of core sets that is associated with the search space set identified by the lowest search space set index; an index of a starting control channel element (CCE) of the core set of the plurality of core sets; and determining a physical uplink control channel (PUCCH) resource based on a number of one or more CCEs in the core set; and transmitting the HARQ-ACK over the PUCCH resource. (Item 2) receiving, by the wireless device and via at least one control resource set (core set) of a core set configured for repetition of downlink control information (DCI), at least one repetition of the DCI that triggers an acknowledgement message; an index of a starting control channel element (CCE) in a core set associated with a search space set identified by a lowest search space set index in said core set; and and transmitting the acknowledgement message over a physical uplink control channel (PUCCH) resource based on a number of one or more CCEs in the core set. (Item 3) 3. The method of claim 2, wherein the acknowledgement message is a Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK). (Item 4) 4. The method of any one of items 2 to 3, further comprising monitoring the core set for repetition of the DCI. (Item 5) 5. The method of any one of items 2 to 4, further comprising selecting the core set from among the core sets based on the core set being associated with the search space set identified in the lowest search space set index. (Item 6) the index of the starting CCE of the core set; and 6. The method according to any one of items 2 to 5, further comprising determining the PUCCH resource based on the number of the one or more CCEs in the core set. (Item 7) 7. The method according to any one of items 2 to 6, wherein the core set is a plurality of core sets. (Item 8) monitoring, by a wireless device, a plurality of control resource sets (core sets) for repetition of downlink control information (DCI); receiving a repetition of the DCI via a first core set of the plurality of core sets, the repetition triggering transmission of a Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK); a second core set associated with the search space set identified by the lowest search space set index among the plurality of core sets; an index of a starting control channel element (CCE) of the second core set; and determining physical uplink control channel (PUCCH) resources based on a number of one or more CCEs of the second core set; and transmitting the HARQ-ACK over the PUCCH resource. (Item 9) receiving, by the wireless device and via a first control resource set (core set) of a core set configured for repetition of downlink control information (DCI), the repetition triggering an acknowledgement message; an index of a starting control channel element (CCE) of a second core set of the core set; and transmitting the acknowledgement message over physical uplink control channel (PUCCH) resources based on the number of one or more CCEs in the second core set, the second core set being associated with a search space set identified by a lowest search space set index. (Item 10) Item 10. The method of item 9, wherein the acknowledgement message is a Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK). (Item 11) 11. The method of any one of items 9 to 10, further comprising monitoring the core set for repetition of the DCI. (Item 12) the index of the starting CCE of the second core set; and 12. The method according to any one of items 9 to 11, further comprising determining the PUCCH resource based on the number of the one or more CCEs of the second core set. (Item 13) 13. The method according to any one of items 9 to 12, wherein the core set is a plurality of core sets. (Item 14) 14. The method of any one of items 1 to 13, further comprising receiving one or more messages including one or more configuration parameters. (Item 15) The DCI schedules a physical downlink shared channel (PDSCH) transmission; and 15. The method according to any one of items 1 to 14, wherein the HARQ-ACK is for the PDSCH transmission. (Item 16) The DCI indicates a semi-persistent scheduling (SPS) PDSCH release for an SPS configuration; and Item 16. The method according to any one of items 1 to 15, wherein the HARQ-ACK is for acknowledging receipt of the DCI indicating the SPS PDSCH release. (Item 17) The DCI indicates a dormant state of a secondary cell (SCell), 17. The method according to any one of items 1 to 16, wherein the HARQ-ACK is for acknowledging receipt of the DCI indicating an SCell dormant state. (Item 18) The one or more configuration parameters, for the core set, a set of resource blocks, and 18. The method of any one of items 14 to 17, showing CCE to resource element group (REG) mapping. (Item 19) the set of resource blocks, and Item 19. The method of item 18, further comprising determining the one or more CCEs of the core set based on the CCE to REG mapping. (Item 20) 20. The method according to any one of items 1 to 19, wherein the DCI includes a PUCCH resource indicator field. (Item 21) 21. The method of claim 20, wherein the determining the PUCCH resource is further based on a value of the PUCCH resource indicator field. (Item 22) 22. The method of any one of items 1 to 21, wherein the DCI includes a timing indicator field. (Item 23) 23. The method of claim 22, wherein the transmitting is within a time slot indicated by a value of the timing indicator field. (Item 24) 24. The method according to any one of items 14 to 23, wherein the one or more configuration parameters indicate one or more PUCCH resource sets including a starting PUCCH resource set that occurs first among the one or more PUCCH resource sets. (Item 25) 25. The method of claim 24, wherein the first PUCCH resource set includes a plurality of PUCCH resources including the PUCCH resource. (Item 26) 26. The method of claim 25, wherein the number of the plurality of PUCCH resources is greater than a value. (Item 27) 27. The method of claim 26, wherein the value is equal to 8. (Item 28) 28. The method of claim 27, wherein the determining of the PUCCH resource is in response to the number of the plurality of PUCCH resources being greater than the value. (Item 29) 29. A method according to any one of items 24 to 28, wherein the one or more configuration parameters indicate, for the starting PUCCH resource set, a PUCCH resource set index that is the lowest among one or more PUCCH resource set indices of the one or more PUCCH resource sets. (Item 30) said monitoring includes monitoring a plurality of search space sets associated with said plurality of core sets; and 30. The method according to any one of items 1 to 29, wherein each search space set of the plurality of search space sets is associated with a respective core set of the plurality of core sets. (Item 31) the one or more configuration parameters indicate a plurality of search space set indexes for the plurality of search space sets that include the search space set; and Item 31. The method of item 30, wherein each search space set of the plurality of search space sets is identified by a respective search space set index of the plurality of search space set indexes. (Item 32) the search space set index of the search space set of the core set is lowest among the plurality of search space set indexes of the plurality of search space sets; and Item 32. The method of item 31, wherein the plurality of search space set indexes includes the search space set index. (Item 33) Item 33. The method of item 32, wherein the one or more configuration parameters indicate the core set for the search space set. (Item 34) 34. The method according to any one of items 32 to 33, wherein the one or more configuration parameters indicate an association between the search space set and the core set. (Item 35) 35. The method of any one of items 32 to 34, wherein the selection of the core set from among a plurality of core sets is based on the one or more configuration parameters indicating downlink control channel repetition. (Item 36) 36. The method according to any one of items 1 to 35, wherein the starting CCE is a CCE having a lowest index among the indices of the one or more CCEs in the core set. (Item 37) 37. The method according to any one of items 1 to 36, wherein the at least one core set comprises the core set. (Item 38) Item 38. The method of item 37, wherein receiving the at least one repetition of the DCI via the at least one core set includes receiving the DCI via one or more first received CCEs of the one or more CCEs of the core set. (Item 39) Item 39. The method of item 38, wherein the starting CCE is a CCE having a lowest index among the indices of the one or more first received CCEs. (Item 40) 40. The method according to any one of items 1 to 39, wherein the at least one core set does not include the core set. (Item 41) receiving the at least one repetition of the DCI via the at least one core set includes receiving the DCI via one or more second received CCEs of one or more second CCEs of a second core set; and Item 41. The method of item 40, wherein the at least one core set comprises the second core set. (Item 42) Item 42. The method according to item 41, wherein the starting CCE is a CCE having a lowest index among the indices of the one or more second received CCEs. (Item 43) 43. The method according to any one of items 41 to 42, wherein the starting CCE is associated with a CCE having a lowest index among indices of the one or more second received CCEs. (Item 44) Item 44. The method of item 43, wherein the one or more configuration parameters indicate an association between the one or more CCEs of the core set and the one or more second CCEs of the second core set. (Item 45) the repetition of the DCI is relative to a downlink control channel repetition; and the downlink control channel repetition comprises: Time Domain Control Channel Repeat, or 45. The method according to any one of items 1 to 44, wherein at least one of the frequency domain control channel repetitions. (Item 46) Item 46. The method of item 45, wherein the one or more configuration parameters indicate the plurality of core sets for the downlink control channel repetition. (Item 47) 47. The method according to any one of items 1 to 46, wherein determining the PUCCH resource is based on the one or more configuration parameters indicating downlink control channel repetition. (Item 48) receiving a second DCI via a second core set not associated with the downlink control channel repetition, the second DCI triggering transmission of a second HARQ-ACK; the index of the starting CCE of the second core set from which the second DCI is received; and determining a second PUCCH resource based on a number of one or more second CCEs in / of the second core set; 48. The method of any one of items 1 to 47, further comprising: transmitting the second HARQ-ACK via the second PUCCH resource. (Item 49) The HARQ-ACK Acknowledgment (ACK), or 49. The method of any one of items 1 to 48, comprising a negative ACK (NACK). (Item 50) the at least one core set is the first core set; and 50. The method according to any one of items 1 to 49, wherein the core set is the second core set. (Item 51) 1. A wireless device, comprising: one or more processors; A wireless device comprising: a memory storing instructions that, when executed by the one or more processors, cause the wireless device to implement the method described in any one of items 1 to 50. (Item 52) A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method of any one of items 1 to 50. (Item 53) transmitting, by a base station and to a wireless device, repetitions of downlink control information (DCI) over a plurality of control resource sets (core sets), the DCI triggering the wireless device to transmit a hybrid automatic repeat request-acknowledgement (HARQ-ACK); selecting a core set from the plurality of core sets that is associated with the search space set identified by the lowest search space set index; an index of a starting control channel element (CCE) of the core set of the plurality of core sets; and determining a physical uplink control channel (PUCCH) resource based on a number of one or more CCEs in the core set; receiving the HARQ-ACK from the wireless device and via the PUCCH resource. (Item 54) transmitting, by a base station and to a wireless device, repetitions of downlink control information (DCI) over a control resource set (core set), the DCI triggering the wireless device to transmit an acknowledgement message; from the wireless device, an index of a starting control channel element (CCE) in a core set associated with a search space set identified by a lowest search space set index in said core set; and receiving the acknowledgement message over a physical uplink control channel (PUCCH) resource based on a number of one or more CCEs in the core set. (Item 55) Item 55. The method of item 54, wherein the acknowledgement message is a Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK). (Item 56) 56. The method of any one of items 54 to 55, further comprising selecting the core set from among the core sets based on the core set being associated with the search space set identified in the lowest search space set index. (Item 57) the index of the starting CCE of the core set; and 56. The method according to any one of items 54 to 55, further comprising determining a PUCCH resource based on the number of the one or more CCEs in the core set. (Item 58) 58. The method according to any one of items 54 to 57, wherein the core set is a plurality of core sets. (Item 59) transmitting, by a base station and to a wireless device, repetitions of downlink control information (DCI) over a plurality of control resource sets (core sets), the DCI triggering the wireless device to transmit a hybrid automatic repeat request-acknowledgement (HARQ-ACK); a second core set associated with the search space set identified by the lowest search space set index among the plurality of core sets; an index of a starting control channel element (CCE) of the second core set; and determining physical uplink control channel (PUCCH) resources based on a number of one or more CCEs of the second core set; receiving the HARQ-ACK from the wireless device and via the PUCCH resource. (Item 60) transmitting, by a base station and to a wireless device, repetitions of downlink control information (DCI) over a control resource set (core set), the DCI triggering the wireless device to transmit an acknowledgement message; from the wireless device, an index of a starting control channel element (CCE) of a second core set of the core set; and receiving the acknowledgment message over a physical uplink control channel (PUCCH) resource based on the number of one or more CCEs in the second core set, the second core set being associated with a search space set identified by a lowest search space set index. (Item 61) Item 61. The method of item 60, wherein the acknowledgement message is a Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK). (Item 62) the index of the starting CCE of the second core set; and 62. The method according to any one of items 60 to 61, further comprising determining the PUCCH resource based on the number of the one or more CCEs of the second core set. (Item 63) 63. The method according to any one of items 60 to 62, wherein the core set is a plurality of core sets. (Item 64) 64. The method of any one of items 53 to 63, further comprising sending one or more messages including one or more configuration parameters. (Item 65) The DCI schedules a physical downlink shared channel (PDSCH) transmission; and Item 65. The method according to any one of items 53 to 64, wherein the HARQ-ACK is for the PDSCH transmission. (Item 66) The DCI indicates a semi-persistent scheduling (SPS) PDSCH release for an SPS configuration; and Item 66. The method according to any one of items 53 to 65, wherein the HARQ-ACK is for acknowledging receipt of the DCI indicating the SPS PDSCH release. (Item 67) The DCI indicates a dormant state of a secondary cell (SCell), 67. The method according to any one of items 53 to 66, wherein the HARQ-ACK is for acknowledging receipt of the DCI indicating an SCell dormant state. (Item 68) The one or more configuration parameters, for the core set, a set of resource blocks, and 68. The method of any one of items 64 to 67, showing CCE to resource element group (REG) mapping. (Item 69) the set of resource blocks, and Item 69. The method of item 68, further comprising determining the one or more CCEs of the core set based on the CCE to REG mapping. (Item 70) Item 69. The method of any one of items 53 to 69, wherein the DCI includes a PUCCH resource indicator field. (Item 71) Item 71. The method of item 70, wherein the determining the PUCCH resource is further based on a value of the PUCCH resource indicator field. (Item 72) 72. The method of any one of items 53 to 71, wherein the DCI includes a timing indicator field. (Item 73) Item 73. The method of item 72, wherein the receiving is within a time slot indicated by a value of the timing indicator field. (Item 74) 74. A method according to any one of items 64 to 73, wherein the one or more configuration parameters indicate one or more PUCCH resource sets including a starting PUCCH resource set that occurs first in the one or more PUCCH resource sets. (Item 75) Item 75. The method of item 74, wherein the starting PUCCH resource set includes a plurality of PUCCH resources including the PUCCH resource. (Item 76) Item 76. The method of item 75, wherein the number of the plurality of PUCCH resources is greater than a value. (Item 77) 77. The method of claim 76, wherein the value is equal to 8. (Item 78) Item 78. The method of item 77, wherein the determining of the PUCCH resource is in response to the number of the plurality of PUCCH resources being greater than the value. (Item 79) 79. A method according to any one of items 74 to 78, wherein the one or more configuration parameters indicate, for the starting PUCCH resource set, a PUCCH resource set index that is lowest among one or more PUCCH resource set indices of the one or more PUCCH resource sets. (Item 80) the transmitting includes transmitting through a plurality of search space sets associated with the plurality of core sets; and 80. The method of any one of items 44 to 79, wherein each search space set of the plurality of search space sets is associated with a respective core set of the plurality of core sets. (Item 81) the one or more configuration parameters indicate a plurality of search space set indexes for the plurality of search space sets that include the search space set; and Item 81. The method of item 80, wherein each search space set of the plurality of search space sets is identified by a respective search space set index of the plurality of search space set indexes. (Item 82) the search space set index of the search space set of the core set is lowest among the plurality of search space set indexes of the plurality of search space sets; and Item 82. The method of item 81, wherein the plurality of search space set indexes includes the search space set index. (Item 83) Item 83. The method of item 82, wherein the one or more configuration parameters indicate the core set for the search space set. (Item 84) 84. The method of any one of items 82 to 83, wherein the one or more configuration parameters indicate an association between the search space set and the core set. (Item 85) 85. The method of any one of items 82 to 84, wherein the selection of the core set from among the plurality of core sets is based on the one or more configuration parameters indicating downlink control channel repetition. (Item 86) 86. The method of any one of items 53 to 85, wherein the starting CCE is a CCE having the lowest index value of the one or more CCEs of the core set. (Item 87) 87. The method according to any one of items 53 to 86, wherein the at least one core set comprises the core set. (Item 88) Item 88. The method of item 87, wherein transmitting the repetition of the DCI via the core set includes transmitting the DCI via one or more first transmission CCEs of the one or more CCEs of the core set. (Item 89) Item 89. The method of item 88, wherein the starting CCE is a CCE having a lowest index among the indices of the one or more first transmission CCEs. (Item 90) 89. The method according to any one of items 53 to 89, wherein the at least one core set does not include the core set. (Item 91) Item 91. The method of item 90, wherein transmitting the repetition of the DCI over the core set includes transmitting the DCI over a second CCE of a second core set of the core set. (Item 92) Item 92. The method of item 91, wherein the starting CCE is a CCE having a lowest index among the indexes of the one or more second transmission CCEs. (Item 93) Item 93. The method according to any one of items 91 to 92, wherein the starting CCE is associated with a CCE having a lowest index among indices of the one or more second transmission CCEs. (Item 94) Item 94. The method of item 93, wherein the one or more configuration parameters indicate an association between the one or more CCEs of the core set and the one or more second CCEs of the second core set. (Item 95) the repetition of the DCI is relative to a downlink control channel repetition; and the downlink control channel repetition comprises: Time Domain Control Channel Repeat, or Item 95. The method according to any one of items 53 to 94, wherein at least one of the frequency domain control channel repetitions. (Item 96) Item 96. The method of item 95, wherein the one or more configuration parameters indicate the plurality of core sets for the downlink control channel repetition. (Item 97) Item 97. The method according to any one of items 64 to 96, wherein determining the PUCCH resource is based on the one or more configuration parameters indicating downlink control channel repetition. (Item 98) transmitting a second DCI to the wireless device and via a second core set not associated with a downlink control channel repetition, the second DCI triggering transmission of a second HARQ-ACK; the index of the starting CCE of the second core set, and determining a second PUCCH resource based on a number of one or more second CCEs in / of the second core set; Item 98. The method of any one of items 53 to 97, further comprising receiving the second HARQ-ACK from the wireless device and via the second PUCCH resource. (Item 99) The HARQ-ACK Acknowledgment (ACK), or 99. The method of any one of items 53 to 98, comprising a negative ACK (NACK). (Item 100) 99. The method according to any one of items 53 to 99, wherein the at least one core set is the first core set and the core set is the second core set. (Item 101) A base station, one or more processors; A base station comprising: a memory storing instructions that, when executed by the one or more processors, cause the base station to implement the method described in any one of items 53 to 100. (Item 102) A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method of any one of items 53 to 100. (Item 103) A base station, comprising: one or more first processors; and when executed by the one or more first processors, the base station: a base station including: a memory storing instructions for transmitting repetitions of downlink control information (DCI) over a control resource set (core set), the DCI triggering an acknowledgement message; a wireless device, the wireless device comprising: one or more second processors; and a program that, when executed by the one or more second processors, causes the wireless device to: receiving, via at least one of the core sets, at least one repetition of the DCI that triggers the acknowledgement message; and an index of a starting control channel element (CCE) in a core set associated with a search space set identified by a lowest search space set index in said core set; and and a wireless device including: a memory that stores instructions to cause the transmission of the acknowledgement message via a physical uplink control channel (PUCCH) resource based on the number of one or more CCEs in the core set. (Item 104) A base station, comprising: one or more first processors; and when executed by the one or more first processors, the base station: a base station including: a memory storing instructions for transmitting repetitions of downlink control information (DCI) over a control resource set (core set), the DCI triggering an acknowledgement message; a wireless device, the wireless device comprising: one or more second processors; and a program that, when executed by the one or more second processors, causes the wireless device to: receiving a repetition of downlink control information (DCI) via a first core set of the core sets configured for repetition of the DCI, the repetition triggering the acknowledgement message; and an index of a starting control channel element (CCE) of a second core set of the core set; and and a memory that stores instructions to cause the transmission of the acknowledgment message over a physical uplink control channel (PUCCH) resource based on the number of one or more CCEs in the second core set, the second core set being associated with a search space set identified by a lowest search space set index. (Item 105) monitoring, by a wireless device, a plurality of control resource sets (core sets) for repetition of downlink control information (DCI); receiving at least one repetition of the DCI scheduling a transport block via at least one core set of the plurality of core sets; determining a resource block (RB) based on the lowest RB among the RBs of the plurality of core sets; receiving the transport block starting from the RB. (Item 106) receiving, by a wireless device and via at least one control resource set (core set) of a core set configured for repetition of downlink control information (DCI), at least one repetition of the DCI scheduling a transport block; receiving the transport block starting from a resource block (RB) determined based on a lowest RB of the core set. (Item 107) Item 107. The method of item 106, further comprising monitoring the core set for the repetition of the DCI. (Item 108) 108. The method of any one of items 106 to 107, further comprising determining the RB based on the lowest RB among the RBs of the core set. (Item 109) 109. The method according to any one of items 106 to 108, wherein the core set is a plurality of core sets. (Item 110) monitoring, by a wireless device, a plurality of control resource sets (core sets) for repetition of downlink control information (DCI); receiving a repetition of the DCI scheduling a transport block over a first core set of the plurality of core sets; determining a resource block (RB) based on the lowest RB among the RBs of the plurality of core sets; receiving the transport block starting from the RB. (Item 111) receiving, by a wireless device and via a first control resource set (core set) of a core set configured for repetition of downlink control information (DCI), the repetition scheduling a transport block; receiving the transport block starting from a resource block (RB) determined based on a lowest RB of the core set. (Item 112) 112. The method of claim 111, further comprising monitoring the core set for the repetition of the DCI. (Item 113) 113. The method of any one of items 111 to 112, further comprising determining the RB based on the lowest RB among the RBSs of the core set. (Item 114) 114. The method according to any one of items 111 to 113, wherein the core set is a plurality of core sets. (Item 115) Item 115. The method according to any one of items 105 to 114, wherein a Physical Downlink Shared Channel (PDSCH) transmission comprises the transport block. (Item 116) said monitoring includes monitoring a plurality of search space sets associated with said plurality of core sets; and 116. The method according to any one of items 105 to 115, wherein each search space set of the plurality of search space sets is associated with a respective core set of the plurality of core sets. (Item 117) 117. The method according to any one of Items 105 to 116, wherein the plurality of search space sets is a plurality of common search space sets. (Item 118) 118. The method of any one of items 105 to 117, wherein the RB is equal to the lowest RB of the core set. (Item 119) Item 119. The method according to any one of items 105 to 118, wherein the DCI is DCI format 1_0. (Item 120) 119. The method of any one of items 105 to 119, further comprising receiving one or more messages including one or more configuration parameters. (Item 121) Item 121. The method of item 120, wherein the one or more configuration parameters indicate one or more RBs of the core set. (Item 122) Item 122. The method according to any one of Items 105 to 121, wherein the lowest RB of the core set is an RB having a lowest frequency among one or more frequencies of the one or more RBs of the core set. (Item 123) Item 123. The method according to any one of items 105 to 122, wherein the lowest RB of the core set is an RB having a lowest starting frequency among one or more starting frequencies of the one or more RBs of the core set. (Item 124) Item 124. The method of any one of items 105 to 123, wherein the DCI includes a resource indication field having a value. (Item 125) Item 125. The method of item 124, further comprising determining a starting virtual RB based on the value of the resource indication field. (Item 126) Item 126. The method according to any one of items 124 to 125, further comprising determining an RB length based on the value of the resource indication field. (Item 127) 127. The method according to any one of items 125 to 126, wherein the determining of the RB is further based on the starting virtual RB. (Item 128) The RB is the lowest RB of the core set; The method according to item 127, wherein the sum is equal to the sum of the starting virtual RB. (Item 129) Item 129. The method according to any one of items 126 to 128, wherein the size of the transport block is equal to the RB length. (Item 130) Item 130. The method of item 129, wherein the receiving of the transport block is in one or more RBs. (Item 131) Item 131. The method of item 130, wherein the number of the one or more RBs is equal to the RB length. (Item 132) 132. The method according to any one of items 130 to 131, wherein the RB is a starting RB among the one or more RBs on which the transport block is received. (Item 133) Item 133. The method of any one of items 105 to 132, wherein determining the RB based on the lowest RB of the core set is responsive to the plurality of search space sets being the plurality of common search space sets. (Item 134) 1. A wireless device, comprising: one or more processors; A wireless device comprising: a memory storing instructions that, when executed by the one or more processors, cause the wireless device to implement the method described in any one of items 105 to 133. (Item 135) A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method of any one of items 105 to 133. (Item 136) transmitting, by a base station and to a wireless device, repetitions of downlink control information (DCI) over a control resource set (core set), the DCI scheduling a transport block; determining a resource block (RB) based on the lowest RB among the RBs of the plurality of core sets; transmitting the transport block starting from the RB to the wireless device. (Item 137) transmitting, by a base station and to a wireless device, repetitions of downlink control information (DCI) over a control resource set (core set), the DCI scheduling a transport block; transmitting the transport block starting from a resource block (RB) determined based on a lowest RB of the core set. (Item 138) Item 138. The method of item 137, further comprising determining the RB based on the lowest RB among the RBs of the core set. (Item 139) 139. The method according to any one of items 137 to 138, wherein the core set is a plurality of core sets. (Item 140) Item 139. The method according to any one of items 136 to 138, wherein a Physical Downlink Shared Channel (PDSCH) transmission comprises the transport block. (Item 141) the transmitting includes transmitting through a plurality of search space sets associated with the plurality of core sets; and 141. The method of any one of items 136 to 140, wherein each search space set of the plurality of search space sets is associated with a respective core set of the plurality of core sets. (Item 142) Item 142. The method according to any one of Items 141 to 141, wherein the plurality of search space sets is a plurality of common search space sets. (Item 143) 143. The method of any one of items 136 to 142, wherein the RB is equal to the lowest RB of the core set. (Item 144) Item 144. The method according to any one of items 136 to 143, wherein the DCI is DCI format 1_0. (Item 145) 145. The method of any one of items 136 to 144, further comprising sending one or more messages including one or more configuration parameters. (Item 146) Item 146. The method of item 145, wherein the one or more configuration parameters indicate one or more RBs of the core set. (Item 147) Item 147. The method of item 146, wherein the lowest RB of the core set is the RB having the lowest frequency among one or more frequencies of the one or more RBs of the core set. (Item 148) Item 148. The method of any one of Items 146 to 147, wherein the lowest RB of the core set is the RB having the lowest starting frequency among one or more starting frequencies of the one or more RBs of the core set. (Item 149) Item 149. A method according to any one of items 136 to 148, wherein the DCI includes a resource indication field having a value. (Item 150) Item 149. The method of item 149, further comprising determining a starting virtual RB based on the value of the resource indication field. (Item 151) Item 151. The method of item 150, further comprising determining an RB length based on the value of the resource indication field. (Item 152) Item 152. The method according to any one of items 150 to 151, wherein the determining of the RB is further based on the starting virtual RB. (Item 153) The RB is the lowest RB of the core set; The method described in item 152, wherein the sum is equal to the sum of the starting virtual RB. (Item 154) Item 154. The method according to any one of items 151 to 153, wherein the size of the transport block is equal to the RB length. (Item 155) Item 155. The method of item 154, wherein the receiving of the transport block is in one or more RBs. (Item 156) Item 156. The method of item 155, wherein the number of the one or more RBs is equal to the RB length. (Item 157) 157. The method according to any one of items 155 to 156, wherein the RB is a starting RB of the one or more RBs on which the transport block is received. (Item 158) Item 158. The method of any one of items 142 to 157, wherein determining the RB based on the lowest RB of the core set is responsive to the plurality of search space sets being the plurality of common search space sets. (Item 159) A base station, one or more processors; A base station comprising: a memory storing instructions that, when executed by the one or more processors, cause the base station to implement the method of any one of items 136 to 158. (Item 160) A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method of any one of items 136 to 158. (Item 161) A base station, comprising: one or more first processors; and when executed by the one or more first processors, the base station: transmitting repetitions of downlink control information (DCI) over a control resource set (core set), the DCI scheduling transport blocks; and a memory storing instructions for transmitting the transport block from a resource block (RB) determined based on a lowest RB of the core set; and a wireless device, the wireless device comprising: one or more second processors; and a program that, when executed by the one or more second processors, causes the wireless device to: receiving at least one repetition of the DCI scheduling the transport block via at least one of the core sets configured for repetition of the DCI; and and a wireless device including: a memory that stores instructions to perform receiving the transport block starting from the RB determined based on the lowest RB of the core set. (Item 162) A base station, comprising: one or more first processors; and when executed by the one or more first processors, the base station: transmitting repetitions of downlink control information (DCI) over a control resource set (core set), the DCI scheduling transport blocks; and a memory storing instructions for transmitting the transport block from a resource block (RB) determined based on a lowest RB of the core set; and a wireless device, the wireless device comprising: one or more second processors; and a program that, when executed by the one or more second processors, causes the wireless device to: receiving a repetition of the DCI scheduling the transport block via a first core set of the core sets configured for repetition of the DCI; and and a wireless device including: a memory that stores instructions to perform receiving the transport block starting from the RB determined based on the lowest RB of the core set. [Brief explanation of the drawings]

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

[0004] [Figure 1] 1A and 1B illustrate an example of a mobile communication network in which embodiments of the present disclosure may be implemented.

[0005] [Figure 2] 2A and 2B show the New Radio (NR) user plane and control plane protocol stacks, respectively.

[0006] [Figure 3] FIG. 3 shows examples of services provided between protocol layers of the NR user plane protocol stack of FIG. 2A.

[0007] [Figure 4] Figure 4A shows an example downlink data flow through the NR user plane protocol stack of Figure 2A. Figure 4B shows an example format of a MAC subheader in a MAC PDU.

[0008] [Figure 5] 5A and 5B show the mapping between downlink and uplink logical, transport, and physical channels, respectively.

[0009] [Figure 6] FIG. 6 is an exemplary diagram illustrating RRC state transitions for a UE.

[0010] [Figure 7] FIG. 7 shows an example of the structure of an NR frame in which OFDM symbols are grouped.

[0011] [Figure 8] Figure 8 shows an example of a slot configuration in the time and frequency domain of an NR carrier.

[0012] [Figure 9] FIG. 9 shows an example of bandwidth adaptation using three configured BWPs for an NR carrier.

[0013] [Figure 10] Figure 10A shows three carrier aggregation configurations with two component carriers, and Figure 10B shows an example of how aggregation cells can be configured into one or more PUCCH groups.

[0014] [Figure 11] Figure 11A shows an example of an SS / PBCH block structure and location, and Figure 11B shows an example of a CSI-RS mapped to the time and frequency domain.

[0015] [Figure 12] 12A and 12B show examples of three downlink and uplink beam management procedures, respectively.

[0016] [Figure 13] 13A, 13B, and 13C show a four-step contention-based random access procedure, a two-step contention-free random access procedure, and an alternative two-step random access procedure, respectively.

[0017] [Figure 14] Figure 14A shows an example of a CORESET configuration for bandwidth portions, and Figure 14B shows an example of CCE to REG mapping for DCI transmission on CORESET and PDCCH processing.

[0018] [Figure 15] FIG. 15 illustrates an embodiment of a wireless device communicating with a base station.

[0019] [Figure 16] 16A, 16B, 16C, and 16D show example structures for uplink and downlink transmissions.

[0020] [Figure 17] FIG. 17 illustrates exemplary control and / or data configuration parameters according to an aspect of an embodiment of the present disclosure.

[0021] [Figure 18] FIG. 18 illustrates an example of core set configuration parameters according to an aspect of an embodiment of the present disclosure.

[0022] [Figure 19] FIG. 19 illustrates an example of PDCCH repetition according to one aspect of an embodiment of the present disclosure.

[0023] [Figure 20] FIG. 20 illustrates an example of control channel repetition across multiple TRPs according to one aspect of an embodiment of the present disclosure.

[0024] [Figure 21] FIG. 21 illustrates an example of control channel repetition according to one aspect of an embodiment of the present disclosure.

[0025] [Figure 22] FIG. 22 illustrates an example of a core set associated with multiple TCI states as an active TCI state, according to an aspect of an embodiment of the present disclosure.

[0026] [Figure 23] FIG. 23 illustrates an example of a MAC CE format for activating multiple TCI states for a core set, according to an aspect of an embodiment of the present disclosure.

[0027] [Figure 24] FIG. 24 is an example of uplink resource determination with control channel repetition according to one aspect of an embodiment of the present disclosure.

[0028] [Figure 25] FIG. 25 is an example flow diagram of uplink resource determination with control channel repetition according to one aspect of an embodiment of the present disclosure.

[0029] [Figure 26] FIG. 26 is an example of downlink resource determination with control channel repetition according to one aspect of an embodiment of the present disclosure.

[0030] [Figure 27] FIG. 27 is an example flow diagram of downlink resource determination with control channel repetition according to an aspect of an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0031] Embodiments may be configured to operate as needed. The disclosed mechanisms may be executed when certain criteria are met, for example, in a wireless device, a base station, a wireless environment, a network, a combination of the above, etc. Exemplary criteria may be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system settings, packet size, traffic characteristics, a combination of the above, etc. Once one or more criteria are met, various exemplary embodiments may be applied. Thus, it may be possible to implement exemplary embodiments that selectively implement the disclosed protocols.

[0032] A base station may communicate with a mix of wireless devices. Wireless devices and / or base stations may support multiple technologies and / or multiple releases of the same technology. Wireless devices may have certain capabilities depending on the category and / or capabilities of the wireless devices. When this disclosure refers to a base station communicating with multiple wireless devices, this disclosure may refer to a subset of all wireless devices in the coverage area. For example, this disclosure may refer to multiple wireless devices of a given LTE or 5G release that include a given capability and are located in a given sector of the base station. In this disclosure, multiple wireless devices may refer to selected wireless devices and / or a subset of all wireless devices in the coverage area that perform according to the disclosed methods, etc. There may be multiple base stations or multiple wireless devices in the coverage area that may not comply with the disclosed methods. For example, those wireless devices or base stations operate based on older releases of LTE or 5G technology.

[0033] As used herein, "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." As used herein, the term "may" is interpreted as "may, for example." In other words, the term "may" indicates that the phrase following the term "may" is one example of multiple suitable possibilities and may or may not be used by one or more of various embodiments. As used herein, the terms "comprises" and "consists of" list one or more components of a described element. The term "comprises" is interchangeable with "includes" and does not exclude unlisted components that are included in a described element. In contrast, "consists of" provides a complete list of one or more components of a described element. As used herein, the term "based on" should be interpreted as "based at least in part on," rather than, for example, "based only on." As used herein, the term "and / or" refers to any possible combination of the listed elements. For example, "A, B, and / or C" can refer to A, B, C, A and B, A and C, B and C, or A, B, and C.

[0034] If A and B are sets and every element of A is also an element of B, then A is said to be a subset of B. Only non-empty sets and subsets are considered herein. For example, possible subsets of B = {cell1, cell2} are {cell1}, {cell2}, and {cell1, cell2}. The phrase "based on" (or equivalently, "based at least on") indicates that the phrase following the term "based on" is one example of many suitable possibilities that may or may not be used in one or more of various embodiments. The phrase "responsive to" (or equivalently, "at least in response to") indicates that the phrase following the phrase "responsive to" is one example of many suitable possibilities that may or may not be used in one or more of various embodiments. The phrase "according to" (or equivalently, "at least in response to") indicates that the phrase following the phrase "according to" is one example of many suitable possibilities that may or may not be used in one or more of various embodiments. The phrase "adopted / used" (or equivalently "at least adopted / used") indicates that the phrase following the phrase "adopted / used" is one example of many suitable possibilities that may or may not be used in one or more of various embodiments.

[0035] The term configured may relate to the capacity of a device, regardless of whether the device is in an operational or non-operational state. Configuring may also refer to specific settings of a device that affect the operational characteristics of the device, regardless of whether the device is in an operational or non-operational state. In other words, hardware, software, firmware, registers, memory values, etc. may be "configured" within a device, regardless of whether the device is in an operational or non-operational state, to provide the device with specific characteristics. Terms such as "control message originating in a device" may mean that the control message has parameters that can be used to configure specific characteristics in the device or to implement specific actions in the device, regardless of whether the device is in an operational or non-operational state.

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

[0037] Furthermore, many features presented above are described as optional by the use of "may" or parentheses. For the sake of brevity and readability, this disclosure does not explicitly describe each and every variation that may be obtained by selecting from a set of optional features. This disclosure should be construed as explicitly disclosing all such variations. For example, a system described as having three optional features may be embodied in seven ways: with only one of the three possible features, with any two of the three features, or with three of the three features.

[0038] Many of the elements described in the disclosed embodiments may be implemented as modules. Here, a module is defined as an element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (e.g., hardware with biological components), or a combination thereof, which may be behaviorally equivalent. For example, a module may be implemented as a software routine written in a computer language configured to run on a hardware machine (e.g., C, C++, Fortran, Java, Basic, Matlab, etc.) or Simulink, Stateflow, GNU Octave, or LabVIEW MathScript. It may also be possible to implement modules using physical hardware incorporating 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 Verilog or VHSIC Hardware Description Language (VHDL), which configure the connections between the programmable device's less functional internal hardware modules. The above techniques are often used in combination to achieve a functional modular result.

[0039] 1A illustrates an example of a mobile communication network 100 in which an embodiment of the present disclosure may be implemented. The mobile communication network 100 may be, for example, a public land mobile network (PLMN) run by a network operator. As shown in FIG. 1A, the mobile communication network 100 includes a core network (CN) 102, a radio access network (RAN) 104, and wireless devices 106.

[0040] The CN 102 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 interfacing function, the CN 102 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 functionality.

[0041] The RAN 104 may connect the CN 102 to the wireless devices 106 via wireless communication over the air interface. As part of the wireless communication, the RAN 104 may provide scheduling, radio resource management, and retransmission protocols. The communication direction from the RAN 104 to the wireless devices 106 over the air interface is known as the downlink, and the communication direction from the wireless devices 106 to the RAN 104 over the air interface is known as the uplink. Downlink transmissions may be separated from uplink transmissions using frequency division duplexing (FDD), time division duplexing (TDD), and / or some combination of the two duplexing techniques.

[0042] The term wireless device may be used throughout this disclosure to refer to and encompass any mobile or fixed (non-portable) device for which wireless communication is required or available. For example, a wireless device may be a phone, a smartphone, a tablet, a computer, a laptop, a sensor, a meter, a wearable device, an Internet of Things (IoT) device, a vehicular roadside unit (RSU), a relay node, an automobile, and / or any combination thereof. The term wireless device encompasses other terms, including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handset, wireless transmit / receive unit (WTRU), and / or wireless communication device.

[0043] The RAN 104 may include one or more base stations (not shown). The term base station may be used throughout this disclosure to refer to and encompass a Node B (associated with UMTS and / or 3G standards), an evolved Node B (eNB, associated with E-UTRA and / or 4G standards), a remote radio head (RRH), a baseband processing unit coupled to one or more RRHs, a repeater or relay node used to extend the coverage area of ​​a donor node, a next generation evolved Node B (ng-eNB), a generation Node B (gNB, associated with NR and / or 5G standards), an access point (AP, e.g., associated with WiFi or other suitable wireless communication standard), 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).

[0044] The base stations included in the RAN 104 may include one or more sets of antennas for communicating over the air interface with the wireless devices 106. For example, one or more base stations may include three sets of antennas for controlling three cells (or sectors) respectively. 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 wireless device transmitter) operating in the cell. Together, the base station cells may provide wireless coverage to the wireless devices 106 over a wide geographic area to support wireless device mobility.

[0045] In addition to three-sector sites, other implementations of base stations are possible. For example, one or more base stations of the RAN 104 may be implemented as sector sites having more or less than three sectors. One or more base stations of the RAN 104 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. The baseband processing units coupled to the 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. A repeater node may amplify and rebroadcast radio signals received from a donor node. A relay node may perform the same / similar functions as a repeater node, but may decode radio signals received from a donor node and remove noise before amplifying and rebroadcasting the radio signals.

[0046] The RAN 104 may be deployed as a homogeneous network of macrocell base stations having similar antenna patterns and similar high levels of transmit power. The RAN 104 may be deployed as a heterogeneous network. In a heterogeneous network, small cell base stations may be used to provide small coverage areas, such as coverage areas that overlap with the relatively large coverage areas provided by macrocell base stations. The small coverage areas may be provided in areas of high data traffic (or so-called hot spots) or areas where macrocell coverage is weak. Examples of small cell base stations include, in order of decreasing coverage area, microcell base stations, picocell base stations, and femtocell or home base stations.

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

[0048] 1B illustrates another example mobile communication network 150 in which embodiments of the present disclosure may be implemented. The mobile communication network 150 may be, for example, a PLMN run by a network operator. As shown in FIG. 1B, the mobile communication network 150 includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UEs 156A and 156B (collectively, UEs 156). These components may be implemented and operate in the same or similar manner as the corresponding components described with respect to FIG. 1A.

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

[0050] As shown in FIG. 1B, the 5G-CN 152 includes an access and mobility management function (AMF) 158A and a user plane function (UPF) 158B, shown in FIG. 1B as a single component AMF / UPF 158, for simplicity. The UPF 158B may function as a gateway between the NG-RAN 154 and one or more DNs. The UPF 158B may perform functions such as packet routing and forwarding, packet inspection and user plane policy rule enforcement, traffic usage reporting, uplink classification to support 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 triggering. The UPF 158B may function 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 branching point to support multi-homed PDU sessions. The UE 156 may be configured to receive services via a PDU session, which is a logical connection between the UE and the DN.

[0051] The AMF 158A may perform functions such as termination of Non-Access Stratum (NAS) signaling, NAS signaling security, Access Stratum (AS) security control, inter-CN node signaling for mobility between 3GPP® access networks, idle mode UE reachability (e.g., control and execution of paging retransmissions), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including checking roaming rights, mobility management control (subscription and policy), support for network slicing, and / or session management function (SMF) selection. NAS may refer to a function operating between the CN and the UE, and AS may refer to a function operating between the UE and the RAN.

[0052] 5G-CN 152 may include one or more additional network functions not shown in FIG. 1B for clarity. For example, 5G-CN 152 may include one or more of a Session Management Function (SMF), an NR Repository Function (NRF), a Policy Control Function (PCF), a Network Exposure Function (NEF), a Unified Data Management (UDM), an Application Function (AF), and / or an Authentication Server Function (AUSF).

[0053] The NG-RAN 154 may connect the 5G-CN 152 to the UE 156 via wireless communication over the air interface. The NG-RAN 154 may include one or more gNBs (collectively gNBs 160), illustrated as gNB 160A and gNB 160B, and / or one or more ng-eNBs (collectively ng-eNBs 162), illustrated as ng-eNB 162A and ng-eNB 162B. The gNBs 160 and ng-eNBs 162 may more generally be referred to as base stations. The gNBs 160 and ng-eNBs 162 may include one or more sets of antennas for communicating with the UE 156 over the air interface. For example, one or more of the gNBs 160 and / or one or more of the ng-eNBs 162 may include three sets of antennas for controlling three cells (or sectors), respectively. Together, the gNB160 and ng-eNB162 cells may provide radio coverage to the UE156 over a wide geographic area to support UE mobility.

[0054] As shown in FIG. 1B, the gNB 160 and / or the ng-eNB 162 may be connected to the 5G-CN 152 via an NG interface and to other base stations via an Xn interface. The NG and Xn interfaces may be established using direct physical connections and / or indirect connections over an underlying transport network, such as an Internet Protocol (IP) transport network. The gNB 160 and / or the ng-eNB 162 may be connected to the UE 156 via a Uu interface. For example, as shown in FIG. 1B, the gNB 160A may be connected to the UE 156A via a Uu interface. The NG, Xn, and Uu interfaces are associated with protocol stacks. The protocol stacks associated with the interfaces may be used by the network elements of FIG. 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.

[0055] The gNB 160 and / or ng-eNB 162 may be connected to one or more AMF / UPF functions of the 5G-CN 152, such as the AMF / UPF 158, by one or more NG interfaces. For example, the gNB 160A may be connected to the UPF 158B of the AMF / UPF 158 by an NG-User Plane (NG-U) interface. The NG-U interface may provide for the provisioning of user plane PDUs between the gNB 160A and the UPF 158B (e.g., non-guaranteed delivery). The gNB 160A may connect to the AMF 158A 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, forwarding of NAS messages, paging, PDU session management, and configuration forwarding and / or alert message transmission.

[0056] The gNB 160 may provide NR user plane and control plane protocol terminations toward the UE 156 over the Uu interface. For example, the gNB 160A may provide NR user plane and control plane protocol terminations toward the UE 156A over the Uu interface associated with a first protocol stack. The ng-eNB 162 may provide Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations toward the UE 156 over the Uu interface, where E-UTRA refers to a 3GPP 4G radio access technology. For example, the ng-eNB 162B may provide E-UTRA user plane and control plane protocol terminations toward the UE 156B over the Uu interface associated with a second protocol stack.

[0057] The 5G-CN 152 has been described as being configured to handle NR and 4G radio access. Those skilled in the art will understand that it may be possible for the NR to connect to a 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 / UPF 158 is shown in FIG. 1B, one gNB or ng-eNB may be connected to multiple AMF / UPF nodes to provide redundancy and / or load sharing across multiple AMF / UPF nodes.

[0058] 1B, interfaces between network elements (e.g., Uu, Xn, and NG interfaces) may be associated with protocol stacks that the network elements use to exchange data and signaling messages. The protocol stacks may include two planes: a user plane and a control plane. The user plane may handle data of interest to users, and the control plane may handle signaling messages of interest to network elements.

[0059] 2A and 2B show example NR user plane and NR control plane protocol stacks, respectively, for the Uu interface between UE 210 and gNB 220. The protocol stacks shown in Figures 2A and 2B may be the same as or similar to those used for the Uu interface between UE 156A and gNB 160A shown in Figure 1B, for example.

[0060] 2A shows an NR user plane protocol stack including five layers implemented in the UE 210 and the gNB 220. At the bottom of the protocol stack, physical layers (PHYs) 211 and 221 may provide transport services to the higher layers of the protocol stack and may correspond to Layer 1 of the Open Systems Interconnection (OSI) model. The next four protocols above the PHYs 211 and 221 include media access control layers (MAC) 212 and 222, radio link control layers (RLC) 213 and 223, packet data convergence protocol layers (PDCP) 214 and 224, and service data application protocol layers (SDAP) 215 and 225. Together, these four protocols may constitute Layer 2, or the data link layer, of the OSI model.

[0061] FIG. 3 illustrates an example of services provided between protocol layers in the NR user plane protocol stack. Starting from the top of FIGS. 2A and 3, the SDAPs 215 and 225 may perform QoS flow processing. The UE 210 may receive services via a PDU session, which may be a logical connection between the UE 210 and the DN. A PDU session may have one or more QoS flows. A UPF (e.g., UPF 158B) in the CN may map IP packets to one or more QoS flows of the PDU session based on QoS requirements (e.g., in terms of delay, data rate, and / or error rate). The SDAPs 215 and 225 may perform mapping / de-mapping between one or more QoS flows and one or more data radio bearers. The mapping / de-mapping between QoS flows and data radio bearers may be determined by the SDAP 225 at the gNB 220. The SDAP 215 at the UE 210 may be informed of the mapping between QoS flows and data radio bearers via reflected mapping or control signaling received from the gNB 220. For reflective mapping, the SDAP 225 at the gNB 220 may mark the downlink packets with a QoS flow indicator (QFI) that may be observed by the SDAP 215 at the UE 210 to determine the mapping / demapping between QoS flows and data radio bearers.

[0062] PDCPs 214 and 224 may perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, encryption / decryption to prevent unauthorized decryption of data transmitted over the air interface, and integrity protection (to ensure that control messages originate from the intended source). PDCPs 214 and 224 may perform, for example, retransmission of untransmitted packets, in-sequence delivery and reordering of packets, and elimination of duplicate received packets for intra-gNB handover. PDCPs 214 and 224 may perform packet duplication to improve the likelihood of a packet being received and to eliminate any duplicate packets at the receiver. Packet duplication may be useful for services that require high reliability.

[0063] Although not shown in FIG. 3, the PDCPs 214 and 224 may perform mapping / demapping between split radio bearers and RLC channels in a dual connectivity scenario. Dual connectivity 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 the PDCPs 214 and 224 as a service to the SDAPs 215 and 225, is handled by a cell group in dual connectivity. The PDCPs 214 and 224 may map / demap the split radio bearer between the RLC channels belonging to the cell group.

[0064] The RLCs 213 and 223 may perform segmentation, retransmission via automatic repeat request (ARQ), and removal of duplicate data units received from the MACs 212 and 222, respectively. The RLCs 213 and 223 may support three transmission modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged 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 may be per logical channel, independent of numerology and / or transmission time interval (TTI) duration. As shown in FIG. 3, the RLCs 213 and 223 may provide RLC channels as services to the PDCPs 214 and 224, respectively.

[0065] The MACs 212 and 222 may perform multiplexing / demultiplexing of logical channels 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 the PHYs 211 and 221. The MAC 222 may be configured to perform scheduling, scheduling information reporting, and priority handling between UEs through dynamic scheduling. Scheduling may be performed at the gNB 220 (at the MAC 222) for the downlink and uplink. The MACs 212 and 222 may be configured to perform error correction, priority handling between the logical channels of the UE 210 through logical channel prioritization, and / or padding through hybrid automatic repeat request (HARQ) (e.g., one HARQ entity per carrier in the case of carrier aggregation (CA)). The MACs 212 and 222 may support one or more numerologies and / or transmission timings. In one embodiment, mapping restrictions on logical channel prioritization may control which numerology and / or transmission timing a logical channel may use. As shown in Figure 3, MACs 212 and 222 may offer logical channels as services to RLCs 213 and 223.

[0066] The PHYs 211 and 221 may perform transport channel to physical channel mapping and digital and analog signal processing functions to transmit and receive information over the air interface. These digital and analog signal processing functions may include, for example, encoding / decoding and modulation / demodulation. The PHYs 211 and 221 may perform multi-antenna mapping. As shown in Figure 3, the PHYs 211 and 221 may provide one or more transport channels as services to the MACs 212 and 222.

[0067] Figure 4A shows an example of a downlink data flow through the NR user plane protocol stack. Figure 4A shows a downlink data flow of three IP packets (n, n+1, and m) through the NR user plane protocol stack, generating two TBs at gNB 220. The uplink data flow through the NR user plane protocol stack can be similar to the downlink data flow shown in Figure 4A.

[0068] The downlink data flow in Figure 4A begins when the SDAP 225 receives three IP packets from one or more QoS flows and maps the three packets to radio bearers. In Figure 4A, the SDAP 225 maps IP packets n and n+1 to the first radio bearer 402 and maps IP packet m to the second radio bearer 404. An SDAP header (labeled "H" in Figure 4A) is added to the IP packets. Data units from / to higher protocol layers are referred to as service data units (SDUs) of the lower protocol layers, and data units to / from lower protocol layers are referred to as protocol data units (PDUs) of the higher protocol layers. As shown in Figure 4A, the data units from the SDAP 225 are SDUs of the lower protocol layer PDCP 224 and PDUs of the SDAP 225.

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

[0070] 4B shows an example format of a MAC subheader in a MAC PDU. The MAC subheader includes an SDU length field to indicate the length (e.g., in bytes) of the MAC SDU that the MAC subheader corresponds to, a logical channel identifier (LCID) field to identify the logical channel that the MAC SDU originated on to assist in the demultiplexing process, a flag (F) to indicate the size of the SDU length field, and a reserved bit (R) field for future use.

[0071] FIG. 4B further illustrates a MAC Control Element (CE) inserted into a MAC PDU by a MAC, such as MAC 223 or MAC 222. For example, FIG. 4B illustrates two MAC CEs inserted into a MAC PDU. A MAC CE may be inserted at the beginning of a MAC PDU for downlink transmission (as shown in FIG. 4B) and at the end of a 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; activation / deactivation MAC CEs, such as those for PDCP duplicate detection activation / deactivation, channel state information (CSI) reports, sounding reference signal (SRS) transmissions, and pre-configured components; discontinuous reception (DRX)-related MAC CEs; timing advancement MAC CEs; and random access-related MAC CEs. A MAC CE may be preceded by a MAC subheader in a format similar to that described for a MAC SDU and may be identified with a reserved value in the LCID field, which indicates the type of control information included in the MAC CE.

[0072] Before describing the NR control plane protocol stack, we first describe logical, transport, and physical channels and the mapping between channel types. One or more channels may be used to perform functions related to the NR control plane protocol stack, as described below.

[0073] Figures 5A and 5B show the mapping between logical channels, transport channels, and physical channels for the downlink and uplink, respectively. Information is transmitted through channels between the RLC, MAC, and PHY of the NR protocol stack. Logical channels may be used between the RLC and MAC and may be classified as control channels, which carry control and configuration information within the NR control plane, or as traffic channels, which carry data within the NR user plane. Logical channels may be classified as dedicated logical channels dedicated to a specific UE or as common logical channels that can be used by multiple UEs. Logical channels may also be defined by the type of information they carry. The set of logical channels defined by NR includes, for example, - a paging control channel (PCCH) for displaying paging messages used to page UEs whose location is unknown to the network at cell level; - a Broadcast Control Channel (BCCH) for carrying system information messages in the form of a Master Information Block (MIB) and several System Information Blocks (SIBs), which can be used by UEs to obtain information about how the cell is configured and how to operate within the cell; - a Common Control Channel (CCCH) for transmitting control messages together with random access; - a dedicated control channel (DCCH) for transmitting control messages to and from a specific UE for configuring the UE; - Dedicated Traffic Channel (DTCH) for transmitting user data to and from a specific UE.

[0074] Transport channels are used between the MAC and PHY layers and may be defined by how they transmit the information they transmit over the air interface. The set of transport channels defined by NR includes, for example: - a paging channel (PCH) for transmitting paging messages originating from the PCCH; - a Broadcast Channel (BCH) for carrying the MIB from the BCCH; - a Downlink Shared Channel (DL-SCH) for transmission of downlink data and signaling messages, including SIBs from the BCCH; - an uplink shared channel (UL-SCH) for transmitting uplink data and signaling messages; - A Random Access Channel (RACH) that allows a UE to connect to the network without prior scheduling.

[0075] The PHY can pass information between processing levels of the PHY using physical channels. A physical channel may have an associated set of time-frequency resources for carrying information for one or more transport channels. The PHY generates control information to support the lower-level operation of the PHY and may 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 includes, for example: - a Physical Broadcast Channel (PBCH) for carrying the MIB from the BCH; - a Physical Downlink Shared Channel (PDSCH) for carrying downlink data and signaling messages from the DL-SCH and paging messages from the PCH; - a Physical Downlink Control Channel (PDCCH) for carrying Downlink Control Information (DCI), which may include downlink scheduling commands, uplink scheduling grants, and uplink power control commands; - a Physical Uplink Shared Channel (PUSCH) for carrying uplink data and signaling messages from the UL-SCH and, in some cases, Uplink Control Information (UCI), as described below; - a physical uplink control channel (PUCCH) for carrying UCI, which may include a HARQ acknowledgement, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and a scheduling request (SR); - A Physical Random Access Channel (PRACH) for random access.

[0076] Similar to the physical control channel, the physical layer generates physical signals to support the low-level operations of the physical layer. As shown in Figures 5A and 5B, the physical layer signals defined by 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.

[0077] 2B shows an example of an NR control plane protocol stack. In FIG. 2B, the NR control plane protocol stack may use the same / similar first four protocol layers as the example 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 like 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.

[0078] The NAS protocols 217 and 237 may provide control plane functions between the UE 210 and the AMF 230 (e.g., AMF 158A), or more generally, between the UE 210 and the CN. The NAS protocols 217 and 237 may provide control plane functions between the UE 210 and the AMF 230 via signaling messages called NAS messages. There is no direct path between the UE 210 and the AMF 230 over which NAS messages can be transmitted. NAS messages may be transmitted using the ASs of the Uu and NG interfaces. The NAS protocols 217 and 237 may provide control plane functions such as authentication, security, connection setup, mobility management, and session management.

[0079] The RRCs 216 and 226 may provide a control plane function between the UE 210 and the gNB 220, or more generally, between the UE 210 and the RAN. The RRCs 216 and 226 may provide a control plane function between the UE 210 and the gNB 220 via signaling messages referred to as RRC messages. The RRC messages may be transmitted between the UE 210 and the RAN using signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers. The MAC may multiplex control plane and user plane data within the same transport block (TB). The RRCs 216 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, establishment, maintenance, and release of an RRC connection between the UE 210 and the RAN, security functions including key management, establishment, configuration, maintenance, and release of signaling 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 an RRC connection, the RRCs 216 and 226 may establish an RRC context, which may involve setting parameters for communication between the UE 210 and the RAN.

[0080] 6 is an example diagram illustrating RRC state transitions of a UE. The UE may be the same as or similar to the wireless device 106 shown in FIG. 1A, the UE 210 shown in FIG. 2A and FIG. 2B, or any other wireless device described in this disclosure. As shown in FIG. 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).

[0081] In the 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 similar to one of one or more base stations included in the RAN 104 shown in FIG. 1A, one of the gNB 160 or ng-eNB 162 shown in FIG. 1B, the gNB 220 shown in FIGS. 2A and 2B, or any other base station described in this disclosure. 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., associated with 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 the RRC connection 602, the UE's mobility may be managed by the RAN (e.g., the RAN 104 or the NG-RAN 154). The UE may measure signal levels (e.g., reference signal levels) from the serving cell and neighboring cells and report these measurements to the base station currently serving the UE. The UE's serving base station may request a handover to a cell of one of the neighboring base stations based on the reported measurements. The RRC state may transition from RRC Connected 602 to RRC Idle 604 via a Connection Release procedure 608 or to RRC Inactive 606 via a Connection Deactivation procedure 610.

[0082] In RRC idle 604, no RRC context may be established for the UE. In RRC idle 604, the UE may not have an RRC connection with a base station. During RRC idle 604, the UE may be in a sleep state most of the time (e.g., to conserve battery power). The UE may wake up periodically (e.g., once per discontinuous reception cycle) to monitor for paging messages from the RAN. UE mobility 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 discussed in more detail below.

[0083] In RRC Inactive 606, the previously established RRC context is maintained in the UE and the base station. This reduces signaling overhead and allows for a fast transition to RRC Connected 602 compared to transitioning from RRC Idle 604 to RRC Connected 602. In RRC Inactive 606, the UE is in a sleep state and UE mobility may be managed by the UE through cell reselection. The RRC state may transition from RRC Inactive 606 to RRC Connected 602 by a Connection Resume procedure 614 or to RRC Idle 604 via a Connection Release procedure 616 that is the same as or similar to the Connection Release procedure 608.

[0084] An RRC state may 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 allow the network to notify the UE of events via paging messages without broadcasting the paging messages throughout the entire mobile communication network. The mobility management mechanism used in RRC Idle 604 and RRC Inactive 606 may enable the network to track the UE on a cell group level so that paging messages may be broadcast on cells of the cell group in which the UE currently resides instead of the entire mobile communication network. The mobility management mechanisms in RRC Idle 604 and RRC Inactive 606 track UEs on a cell group level. They may do so using different levels of granularity of grouping. For example, there may be three levels of granularity of cell grouping: individual cells, cells within a RAN area identified by a RAN Area Identifier (RAI), and cells within a group of RAN areas referred to as a tracking area and identified by a Tracking Area Identifier (TAI).

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

[0086] The RAN area may be used to track the UE at the RAN level. For a UE in the RRC inactive 606 state, the UE may be assigned a RAN notification area. The RAN notification area may include 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 the UE moves, through cell reselection, to a cell that is not included in the RAN notification area assigned to the UE, the UE may perform a notification area update with the RAN to update the RAN notification area of ​​the UE.

[0087] A base station that stores the RRC context for the UE, or the last serving base station for 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 during the time the UE remains in the RAN notification area of ​​the anchor base station and / or during the time the UE remains in RRC inactive 606.

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

[0089] In NR, physical signals and physical channels (FIGS. 5A and 5B) may be mapped onto orthogonal frequency division multiplexing (OFDM) symbols. OFDM is a multicarrier communication scheme that transmits data on F orthogonal subcarriers (or tones). Before transmission, data may be mapped to a series of complex symbols (e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols), referred to as source symbols, which are divided into F parallel symbol streams. The F parallel symbol streams may be treated as if they were in the frequency domain and used as input to an inverse fast Fourier transform (IFFT) block, which converts them to the time domain. The IFFT block may take F source symbols, one from each of the F parallel symbol streams at a time, 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 F time-domain samples representing a sum of the F orthogonal subcarriers. The F time-domain samples may form a single OFDM symbol. After some processing (e.g., adding a cyclic prefix) and upconversion, the OFDM symbols provided by the IFFT block can be transmitted over the air interface at a carrier frequency. The F parallel symbol streams can be mixed using an FFT block before being processed by the IFFT block. This processing produces discrete Fourier transform (DFT) pre-coded OFDM symbols that can be used by UEs in the uplink to reduce the peak-to-average power ratio (PAPR). Inverse processing can be performed on the OFDM symbols at the receiver using an FFT block to recover the data mapped to the source symbols.

[0090] FIG. 7 shows an example of an NR frame structure in which OFDM symbols are grouped. NR frames may be identified by a system frame number (SFN). The SFN may repeat at a period of 1024 frames. As shown, one NR frame may be 10 milliseconds (ms) in duration and may include 10 subframes, each 1 ms in duration. The subframes may be divided into slots, each including, for example, 14 OFDM symbols per slot.

[0091] 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 mm-wave range). Numerology may be defined in terms of subcarrier spacing and cyclic prefix duration. For numerology in NR, subcarrier spacing may be scaled up by a power of two from the baseline subcarrier spacing of 15 kHz, and cyclic prefix duration may be scaled down by a power of two from the baseline cyclic prefix duration of 4.7 μs. For example, NR defines numerology using 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.

[0092] A slot may have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). Numerologies with higher subcarrier spacing have shorter slot durations and correspondingly more slots per subframe. Figure 7 illustrates this numerology-dependent slot duration and slot-per-subframe transmission structure (for ease of illustration, a numerology with 240 kHz subcarrier spacing is not shown in Figure 7). While a subframe in NR may be used as a numerology-independent time reference, a slot may be used as the unit by which uplink and downlink transmissions are scheduled. To support low latency, scheduling in NR is decoupled from slot duration and can begin with any OFDM symbol and continue for as many symbols as necessary for transmission. These partial slot transmissions may be referred to as minislot or subslot transmissions.

[0093] Figure 8 shows an example of a slot configuration in the time and frequency domains of an NR carrier. A slot includes resource elements (REs) and resource blocks (RBs). An RE is the smallest physical resource in 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 x 12 = 3300 subcarriers. If used, these restrictions may limit an NR carrier to 50, 100, 200, and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz, respectively, and the 400 MHz bandwidth may be set based on the 400 MHz per carrier bandwidth limit.

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

[0095] NR may support a wide range of carrier bandwidths (e.g., up to 400 MHz with 120 kHz subcarrier spacing). Not all UEs may be able to receive the entire carrier bandwidth (e.g., due to hardware limitations). Also, receiving the entire carrier bandwidth may be prohibitive from a UE power consumption perspective. In one embodiment, to reduce power consumption and / or for other purposes, the UE may adapt the size of its reception bandwidth based on the amount of traffic the UE intends to receive. This is referred to as bandwidth adaptation.

[0096] NR defines a bandwidth portion (BWP) to support UEs that cannot receive the entire carrier bandwidth and supports bandwidth adaptation. In one embodiment, a BWP may be defined by a subset of contiguous RBs on a carrier. A UE may be configured (e.g., via the RRC layer) with 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). 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 BWP of the serving cell. When a serving cell is configured with 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.

[0097] For unpaired spectrum, a downlink BWP from the set of configured downlink BWPs may be linked with an uplink BWP from the set of configured uplink BWPs if the downlink BWP index of the downlink BWP and the uplink BWP index of the uplink BWP are the same. For unpaired spectrum, the UE may expect the center frequency of the downlink BWP to be the same as the center frequency of the uplink BWP.

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

[0099] For an uplink BWP within a set of configured 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 for the uplink BWP).

[0100] One or more BWP indicator fields may be provided in the downlink control information (DCI). The value of the BWP indicator field may indicate which BWPs of a set of configured BWPs are active downlink BWPs for one or more downlink receptions. The value of the one or more BWP indicator fields may indicate active uplink BWPs for one or more uplink transmissions.

[0101] The base station may semi-statically configure the UE with a default downlink BWP within a 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.

[0102] The base station can configure the UE with a BWP inactivity timer value for the PCell. The UE may start or restart the BWP inactivity timer at any appropriate time. For example, the UE may start or restart the BWP inactivity timer (a) when the UE detects a DCI indicating an active downlink BWP other than the default downlink BWP for paired spectrum operation, or (b) when the UE detects a DCI indicating an active downlink BWP or an active uplink BWP other than the default downlink BWP or uplink BWP for unpaired spectrum operation. If the UE does not detect a DCI for a certain period of time (e.g., 1 ms or 0.5 ms), the UE may run the BWP inactivity timer towards expiration (e.g., increasing it from zero to the BWP inactivity timer value or decreasing it from the BWP inactivity timer value to zero). When the BWP inactivity timer expires, the UE may switch from the active downlink BWP to the default downlink BWP.

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

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

[0105] FIG. 9 illustrates an example of bandwidth adaptation using three configured BWPs for an NR carrier. A UE configured with three BWPs may switch from one BWP to another at a switch point. In the example shown in FIG. 9, the BWPs include BWP 902 with a 40 MHz bandwidth and 15 kHz subcarrier spacing, BWP 904 with a 10 MHz bandwidth and 15 kHz subcarrier spacing, and BWP 906 with a 20 MHz bandwidth and 60 kHz subcarrier spacing. BWP 902 may be the initial active BWP, and BWP 904 may be the default BWP. A UE may switch between BWPs at a switch point. In the example of FIG. 9, the UE may switch from BWP 902 to BWP 904 at switch point 908. The switch at switch point 908 may occur for any suitable reason, such as in response to expiration of a BWP inactivity timer (indicating switching to the default BWP) and / or in response to receiving a DCI indicating BWP 904 as the active BWP. The UE may switch from the active BWP 904 to BWP 906 at switch point 910 in response to receiving a DCI indicating BWP 906 as the active BWP. The UE may switch from the active BWP 906 to BWP 904 at switch point 912 in response to expiration of a BWP inactivity timer and / or in response to receiving a DCI indicating BWP 904 as the active BWP. The UE may switch from the active BWP 904 to BWP 902 at switch point 914 in response to receiving a DCI indicating BWP 902 as the active BWP.

[0106] If the UE is configured for a secondary cell with a default downlink BWP in the configured set of downlink BWPs and timer values, 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 timer values ​​and default downlink BWPs for the secondary cell in the same / similar manner that the UE uses these values ​​for the primary cell.

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

[0108] 10A shows three CA configurations with two CCs. In the intra-band contiguous configuration 1002, two CCs are aggregated in the same frequency band (frequency band A) and are located immediately adjacent to each other within the frequency band. In the intra-band non-contiguous configuration 1004, two CCs are aggregated in the same frequency band (frequency band A) and are separated by a gap. In the intra-band configuration 1006, two CCs are located in frequency bands (frequency band A and frequency band B).

[0109] In one embodiment, up to 32 CCs may be aggregated. The aggregated CCs may have the same or different bandwidths, subcarrier spacing, and / or duplexing schemes (TDD or FDD). A serving cell of a UE using CA may have a downlink CC. For FDD, one or more uplink CCs may optionally be configured for the serving cell. Being able to aggregate 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.

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

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

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

[0113] 10B shows an example of how aggregation cells may be configured into one or more PUCCH groups. PUCCH group 1010 and PUCCH group 1050 may each include one or more downlink CCs. In the example of FIG. 10B, PUCCH group 1010 includes three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. PUCCH group 1050 includes three downlink CCs: PCell 1051, SCell 1052, and SCell 1053 in this example. 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 SCells (PSCells) 1061, SCell 1062, and SCell 1063. Uplink control information (UCI) associated with downlink CCs of PUCCH group 1010, denoted as UCI 1031, UCI 1032, and UCI 1033, may be transmitted on the uplink of PCell 1021. Uplink control information (UCI) associated with downlink CCs of PUCCH group 1050, denoted as UCI 1071, UCI 1072, and UCI 1073, may be transmitted on the uplink of PSCell 1061. In one example, if the aggregation cell depicted in FIG. 10B were not divided into PUCCH group 1010 and PUCCH group 1050, a single uplink PCell and PCell for transmitting UCI associated with downlink CCs may be overloaded. By dividing the transmission of UCIs between PCell 1021 and PSCell 1061, the overload may be prevented.

[0114] A cell including 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 identify the downlink carrier and / or the uplink carrier of a cell, for example, depending on the context in which the physical cell ID is used. The physical cell ID may be determined using a synchronization signal transmitted on a downlink component carrier. The cell index may be determined using an RRC message. In this disclosure, the physical cell ID may be referred to as a carrier ID, and the cell index may be referred to as a 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 including 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 including the first carrier is activated.

[0115] In CA, the multi-carrier nature of the PHY may be exposed to the MAC. In one embodiment, a HARQ entity may operate on the serving cell. Transport blocks may be generated per assignment / grant per serving cell. Transport blocks and potential HARQ retransmissions of transport blocks may be mapped to the serving cell.

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

[0117] FIG. 11A illustrates an example of the structure and location of SS / PBCH blocks. A burst of SS / PBCH blocks may include one or more SS / PBCH blocks (e.g., four SS / PBCH blocks as shown in FIG. 11A). Bursts may be transmitted periodically (e.g., every two frames or every 20 milliseconds). Bursts may be limited to half-frames (e.g., the first half-frame having a 5 millisecond duration). It will be appreciated that FIG. 11A is an example, and these parameters (number of SS / PBCH blocks per burst, burst periodicity, and burst position within a frame) may be configurable based on, for example, the carrier frequency of the cell in which the SS / PBCH blocks are transmitted, the cell's numerology or subcarrier spacing, configuration by the network (e.g., using RRC signaling), or any other suitable factor. In one example, the UE may assume a subcarrier spacing for the SS / PBCH blocks based on the monitored carrier frequency, unless the wireless network configures the UE to assume a different subcarrier spacing.

[0118] 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 of FIG. 11A) and one or more subcarriers in the frequency domain (e.g., 240 consecutive subcarriers). The PSS, SSS, and PBCH may have a common center frequency. The PSS may be transmitted first and may span, for example, one OFDM symbol and 127 subcarriers. The SSS may be transmitted after the PSS (e.g., two symbols later) and may span one OFDM symbol and 127 subcarriers. The PBCH may be transmitted after the PSS (e.g., over the next three OFDM symbols) and may span 240 subcarriers.

[0119] The location of the SS / PBCH block in the time and frequency domain 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 for a PSS. For example, the UE may monitor a frequency location within the carrier. If the PSS is not found after a certain period of time (e.g., 20 milliseconds), the UE may search for a PSS at a different frequency location within the carrier as indicated by the synchronization raster. If the PSS is found at a location in the time and frequency domain, the UE may determine the location 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, the primary cell may be associated with the CD-SSB. The CD-SSB may be located on the synchronization raster. In one embodiment, cell selection / search and / or reselection may be based on the CD-SSB.

[0120] The SS / PBCH block may be used by the UE to determine one or more parameters of the cell. For example, the UE may determine a physical cell identifier (PCI) of the cell based on the PSS and SSS sequences, respectively. The UE may determine the location of a frame boundary of the cell 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, in which the SS / PBCH block is a known distance from the frame boundary.

[0121] The PBCH may use QPSK modulation and may use forward error correction (FEC). The FEC may use polar coding. One or more symbols spanned by the PBCH may carry one or more DMRSs for demodulation of the PBCH. The PBCH may include an indication of the cell's current system frame number (SFN) and / or 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 can be used by the UE to find the remaining minimum system information (RMSI) associated with the cell. The RMSI may include system information block type 1 (SIB1). SIB1 may include information necessary for the UE to access the cell. The UE may use one or more parameters in the MIB to monitor the PDCCH, which may be used to schedule the PDSCH. The PDSCH may include SIB1. SIB1 may be decoded using the parameters provided in the MIB. The PBCH may indicate the absence of SIB1. Based on the PBCH indicating that SIB1 is not present, the UE may point to a frequency, and the UE may search for an SS / PBCH block on the frequency to which the UE is pointed.

[0122] The UE may assume that one or more SS / PBCH blocks transmitted with the same SS / PBCH block index are quasi-co-located (QCL'd) (e.g., have the same / similar Doppler spread, Doppler shift, average gain, average delay, and / or spatial Rx parameters). The UE may not assume that the QCL's for SS / PBCH block transmissions have different SS / PBCH block indices.

[0123] SS / PBCH blocks (e.g., blocks within a half frame) may be transmitted in spatial directions (e.g., using different beams across the coverage area of ​​a cell). 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.

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

[0125] The CSI-RS may be transmitted by a base station and used by a UE to obtain channel state information (CSI). The base station may configure the UE with one or more CSI-RS for channel estimation or any other suitable purpose. The base station may configure the UE with one or more of the same / similar CSI-RS. The UE may measure one or more CSI-RS. The UE may estimate downlink channel conditions and / or generate a CSI report based on measurements of one or more downlink CSI-RS. The UE may provide the CSI report to the base station. The base station may perform link adaptation using feedback provided by the UE (e.g., estimated downlink channel conditions).

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

[0127] A base station may configure a UE to report CSI measurements. The base station may configure the UE to provide CSI reports periodically, aperiodically, or semi-persistently. For periodic CSI reporting, the UE may be configured with the timing and / or periodicity of CSI reports. For aperiodic CSI reporting, the base station may request CSI reports. For example, the base station may instruct the UE to measure configured CSI-RS resources and provide CSI reports related to the measurements. For semi-persistent CSI reporting, the base station may configure the UE to periodically send periodic reports and selectively activate or deactivate them. The base station may configure the UE with a CSI-RS resource set and CSI reports using RRC signaling.

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

[0129] Downlink DMRS may be transmitted by a base station and used by a UE for channel estimation. For example, downlink DMRS may be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCH). 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 frontloaded DMRS pattern. The frontloaded DMRS may be mapped to one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). The base station may semi-statically configure the UE with the number (e.g., maximum number) of frontloaded DMRS symbols for 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. The wireless network can support a common downlink and uplink DMRS structure (e.g., at least for CP-OFDM). The DMRS position, DMRS pattern, and / or scrambling sequence may be the same or different. The base station may transmit the downlink DMRS and corresponding PDSCH using the same precoding matrix. The UE may use one or more downlink DMRSs for coherent demodulation / channel estimation of the PDSCH.

[0130] In one example, a transmitter (e.g., a base station) may use a precoder matrix for a portion of a 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 precoder matrix and the second precoder matrix may differ based on the first bandwidth being different from the second bandwidth. The UE may assume that the same precoding matrix is ​​used across a set of PRBs. The set of PRBs may be denoted as a precoding resource block group (PRG).

[0131] The PDSCH may include one or more layers. The UE may assume that at least one symbol with a DMRS is present on one or more layers of the PDSCH. Higher layers may configure up to three DMRSs for the PDSCH.

[0132] The downlink PT-RS may be transmitted by the base station and used by the UE for phase noise compensation. Whether the downlink PT-RS is present depends on the RRC configuration. The presence and / or pattern of the downlink PT-RS may be configurable on a UE-specific basis using a combination of RRC signaling and / or an association with one or more parameters used for other purposes (e.g., modulation and coding scheme (MCS)) that may be indicated by DCI. If configured, the dynamic presence of the 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 domain. 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 the DMRS port and the PT-RS port. The number of PT-RS ports may be less than the number of DMRS ports within the scheduled resources. The downlink PT-RS may be restricted to the UE's scheduled time / frequency period. The downlink PT-RS may be transmitted over symbols to facilitate phase tracking at the receiver.

[0133] The UE may transmit an uplink DMRS to a base station for channel estimation. For example, the base station may use the uplink DMRS for coherent demodulation of one or more uplink physical channels. For example, the UE may transmit the uplink DMRS on a PUSCH and / or a PUCCH. The uplink DM-RS 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 frontloaded DMRS pattern. The frontloaded 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 the PUSCH and / or a PUCCH. The base station may semi-statically configure the UE with the number (e.g., maximum number) of frontloaded DMRS symbols for the PUSCH and / or a PUCCH that the UE may use to schedule single-symbol DMRS and / or dual-symbol DMRS. An NR network may support a common DMRS structure for the downlink and uplink (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)), where the DMRS position, DMRS pattern, and / or DMRS scrambling sequence may be the same but different.

[0134] The PUSCH may include one or more layers, and the UE may transmit at least one symbol having a DMRS present on one or more layers of the PUSCH. In one embodiment, higher layers may configure up to three DMRSs for the PUSCH.

[0135] The uplink PT-RS (which may be used by the base station 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 the 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)), which may be indicated by RRC signaling and / or DCI. If configured, the dynamic presence of the uplink PT-RS may be associated with one or more DCI parameters, including at least the MCS. The wireless network may support multiple uplink PT-RS densities defined in the time / frequency domain. 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 the DMRS port and the PT-RS port. The number of PT-RS ports may be less than the number of DMRS ports within the scheduled resources. For example, the uplink PT-RS may be restricted to the UE's scheduled time / frequency period.

[0136] The SRS may be transmitted by the UE to the base station for channel condition estimation to support uplink channel-dependent scheduling and / or link adaptation. The SRS transmitted by the UE may enable the base station to estimate uplink channel conditions at one or more frequencies. The base station scheduler can use the estimated uplink channel conditions to allocate one or more resource blocks for uplink PUSCH transmission from the UE. The base station may semi-statically configure the UE with one or more SRS resource sets. For 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, if higher layer parameters indicate beam management, SRS resources in one or more SRS resource sets (e.g., having the same / similar time-domain behavior, periodicity, aperiodicity, and / or similar) may be transmitted instantaneously (e.g., simultaneously). The UE may transmit one or more SRS resources in an SRS resource set. An NR network may support aperiodic, periodic, and / or semi-persistent SRS transmission. 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 for a UE to select at least one of one or more configured SRS resource sets. 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, if a PUSCH and an SRS are transmitted in the same slot, the UE may be configured to transmit the SRS after the transmission of the PUSCH and the corresponding uplink DMRS.

[0137] The base station may quasi-statistically configure the UE with one or more SRS configuration parameters indicating at least one of an SRS resource configuration identifier, number of SRS ports, time-domain behavior of the SRS resource configuration (e.g., indication of periodic, semi-persistent, or aperiodic SRS), slot, minislot, and / or subframe-level periodicity, offset for periodic and / or aperiodic SRS resources, number of OFDM symbols in the SRS resource, starting OFDM symbol of the SRS resource, SRS bandwidth, frequency hopping bandwidth, periodic shift, and / or SRS sequence ID.

[0138] Antenna ports are defined such that the channel through which a symbol on an antenna port is carried can be inferred from the channel through 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, a receiver may infer the channel (e.g., fade gain, multipath delay, and / or the like) for carrying a second symbol on the antenna port from the channel through which the first symbol on the antenna port is carried. A first antenna port and a second antenna port may be referred to as quasi-colocated (QCL) if one or more large-scale characteristics of the channel through which the first symbol on the first antenna port is conveyed can be inferred from the channel through which the second symbol on the second antenna port is transmitted. The one or more large-scale characteristics may include at least one of delay spread, Doppler spread, Doppler shift, average gain, average delay, and / or spatial receive (Rx) parameters.

[0139] In a channel using beamforming, beam management is required. Beam management may include beam measurement, beam selection, and beam indication. A beam may be associated with one or more reference signals. For example, a beam may be identified by one or more beamforming reference signals. A UE may perform downlink beam measurement based on a downlink reference signal (e.g., a channel state information reference signal (CSI-RS)) and generate a beam measurement report. The UE may perform a downlink beam measurement procedure after an RRC connection is established with the base station.

[0140] 11B shows an example of a channel state information reference signal (CSI-RS) mapped to the time and frequency domain. The squares shown in FIG. 11B may span resource blocks (RBs) within the bandwidth of a cell. The 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 configured 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., symbol and resource element (RE) location within a subframe), CSI-RS subframe configuration (e.g., subframe location, offset, and radio frame periodicity), CSI-RS power parameters, CSI-RS sequence parameters, code division multiplexing (CDM) type parameters, frequency density, transmit comb, quasi-colocation (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

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

[0142] The CSI-RS (e.g., CSI-RS 1101, 1102, 1103) shown in FIG. 11B may be transmitted by a base station and used by a UE for one or more measurements. For example, the UE may measure the reference signal received power (RSRP) of configured CSI-RS resources. The base station may configure the UE with a reporting configuration, and the UE may report RSRP measurements 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 indication (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 with a receive (Rx) beam determined based on the 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 transmit (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 the uplink beam selection procedure based on one or more sounding reference signal (SRS) resources configured for 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.

[0143] In a beam management procedure, a UE may evaluate (e.g., measure) the channel quality of one or more beam pair links, including a transmit beam transmitted by a base station and a receive 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 identifications (e.g., beam index, reference signal index, or the like), RSRP, precoding matrix indicator (PMI), channel quality indicator (CQI), and / or rank indicator (RI).

[0144] FIG. 12A shows three example downlink beam management procedures, P1, P2, and P3. Procedure P1 may enable UE measurements at the transmit (Tx) beams of a transmit receive point (TRP) (or multiple TRPs) to support 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 a set of beams (shown as an ellipse rotating counterclockwise as indicated by the dashed arrows in the top rows of P1 and P2). Beamforming at a UE may include an Rx beam sweep of a set of beams (shown as an ellipse rotating clockwise as indicated by the dashed arrows in the bottom rows of P1 and P3). Procedure P2 may be used to enable UE measurements at the Tx beams of a TRP (shown as an ellipse rotating counterclockwise as indicated by the dashed arrows in the top row of P2). The UE and / or base station may perform procedure P2 using a smaller set of beams than used in procedure P1 or using narrower beams than used in procedure P1. This may be referred to as beam refinement. The UE may perform procedure P3 for Rx beam determination by using the same Tx beam at the base station and sweeping the Rx beam at the UE.

[0145] FIG. 12B shows three example uplink beam management procedures, U1, U2, and U3. Procedure U1 may be used, for example, to enable the base station to perform measurements on the UE's Tx beams 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 as 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 as indicated by dashed arrows in the top rows of U1 and U2). Procedure U2 may be used to enable the base station to adjust its Rx beam when the UE uses 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 narrower beams than 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 uses a fixed Rx beam.

[0146] The UE may initiate a beam failure recovery (BFR) procedure based on detecting a beam failure. The UE may transmit a BFR request (e.g., a preamble, UCI, SR, MAC CE, and / or the like) based on initiating the BFR procedure. The UE may detect beam failure based on determining that the quality of the beam pair link of the associated control channel is unsatisfactory (e.g., has an error rate higher than an error rate threshold, a received signal power lower than a received signal power threshold, a timer expiration, and / or the like).

[0147] A UE may measure the quality of a beam pair link using one or more reference signals (RSs), including one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more demodulation reference signals (DMRSs). The quality of the beam pair link may be based on one or more of a block error rate (BLER), an RSRP value, a signal-to-interference-plus-noise ratio (SINR) value, a reference signal received quality (RSRQ) value, and / or a CSI value measured on the RS resources. The base station may indicate that an RS resource is quasi-co-located (QCLed) with one or more DM-RSs of a channel (e.g., a control channel, a shared data channel, and / or the like). The RS resource and one or more DMRSs of the channel may be QCLed when the channel characteristics (e.g., Doppler shift, Doppler spread, mean delay, delay spread, spatial Rx parameters, fading, and / or the like) from a transmission to the UE via the RS resource are similar or identical to the channel characteristics from a transmission to the UE via the channel.

[0148] The network (e.g., a gNB and / or ng-eNB of the network) and / or the UE may initiate a random access procedure. A UE in an RRC_IDLE state and / or a UE in an RRC_INACTIVE state may initiate a random access procedure to request connection setup to the network. A UE may initiate a random access procedure from an RRC_CONNECTED state. A UE may initiate a random access procedure to request uplink resources (e.g., for SR uplink transmission when there are no PUCCH resources available) and / or to acquire uplink timing (e.g., when 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). A UE may initiate a random access procedure for a beam failure recovery request. The network may initiate a random access procedure to establish time alignment for handover and / or for SCell addition.

[0149] Figure 13A shows a four-step contention-based random access procedure. Before the procedure begins, the base station may send a configuration message 1310 to the UE. Figure 13A includes the transmission of four messages: Msg1 1311, Msg2 1312, Msg3 1313, and Msg4 1314. Msg1 1311 may include and / or be referred to as a preamble (or random access preamble). Msg2 1312 may include and / or be referred to as a random access response (RAR).

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

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

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

[0153] Msg1 1311 may include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions). The RRC message may be used to configure 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 the preamble group based on a path loss measurement 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 having an RSRP above an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). The UE may select at least one preamble associated with one or more reference signals and / or the selected preamble group, for example, when an association between one or more preambles and at least one reference signal is configured by the RRC message.

[0154] The UE may determine a preamble based on one or more RACH parameters provided in the configuration message 1310. For example, the UE may determine a preamble based on a path loss measurement, an RSRP measurement, and / or the size of Msg3 1313. As another example, the one or more RACH parameters may indicate one or more thresholds for determining a preamble format, a maximum number of preamble transmissions, and / or one or more preamble groups (e.g., Group A and Group B). The base station may configure the UE with an association between one or more preambles and one or more reference signals (e.g., SSB and / or CSI-RS) using the one or more RACH parameters. If an association is configured, the UE may determine a preamble to include in Msg1 1311 based on the association. 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 (eg, ra-ssb-OccasionMskIndex and / or ra-OccasionList) may indicate an association between a PRACH occasion and one or more reference signals.

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

[0156] Msg2 1312 received by the UE may include an RAR. In some scenarios, Msg2 1312 may include 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 indicated 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 include a time alignment command that the UE may use to adjust its transmission timing, a scheduling grant 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) in which it monitors the PDCCH for Msg2 1312. The UE may determine when to start the time window based on the PRACH opportunity the UE uses to transmit the preamble. For example, the UE may start the time window one or more symbols after the last symbol of the preamble (e.g., on the first PDCCH opportunity from the end of the preamble transmission). The one or more symbols may be determined based on numerology. The PDCCH may be within a common search space configured by an RRC message (e.g., a Type 1-PDCCH common search space). The UE may identify the RAR based on a radio network temporary identifier (RNTI). The RNTI may be used in response to one or more events that initiate a random access procedure. The UE may use a random access RNTI (RA-RNTI). The RA-RNTI may be associated with the PRACH opportunity on which the UE transmits the preamble. For example, the UE may determine the RA-RNTI based on an OFDM symbol index, a slot index, a frequency domain index, and / or an UL carrier indicator of the PRACH opportunity. Examples of the RA-RNTI may be as follows: RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id where s_id may be the index of the first OFDM symbol of the PRACH opportunity (e.g., 0≦s_id<14), t_id may be the index of the first slot of the PRACH opportunity within the system frame (e.g., 0≦t_id<80), f_id may be the index of the PRACH opportunity in the frequency domain (e.g., 0≦f_id<8), and ul_carrier_id may be the UL carrier used for preamble transmission (e.g., 0 for NUL carrier and 1 for SUL carrier). The UE may transmit Msg3 1313 in response to successful reception of Msg2 1312 (e.g., using the resources identified in Msg2 1312). Msg3 1313 may be used for contention resolution, for example, in the contention-based random access procedure shown in FIG. 13A. In some scenarios, multiple UEs may transmit the same preamble to the base station, and the base station may provide the UE with a corresponding RAR. If multiple UEs interpret the RAR as corresponding to themselves, a discrepancy may occur. Contention resolution (e.g., use of Msg3 1313 and Msg4 1314) may be used to increase the likelihood that a UE does not mistakenly use the identity of another UE. To perform contention resolution, the UE may include a device identifier (e.g., C-RNTI, if assigned, TC-RNTI included in Msg2 1312, and / or any other suitable identifier) ​​in Msg3 1313.

[0157] 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 addresses the UE on the PDCCH using the C-RNTI. If the UE's unique C-RNTI is detected on the PDCCH, the random access procedure is determined to have completed successfully. If a TC-RNTI is included in Msg3 1313 (e.g., the UE is in an RRC_IDLE state or is 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 matches the CCCH SDU sent (e.g., transmitted) in Msg3 1313 or otherwise includes the corresponding UE contention resolution identity MAC CE, the UE may determine that contention resolution was successful and / or the UE may determine that the random access procedure was completed successfully.

[0158] A UE may be configured with a complementary uplink (SUL) carrier and a normal uplink (NUL) carrier. Initial access (e.g., random access procedure) may be supported on the uplink carrier. For example, a base station may configure a UE with two separate RACH configurations, one for the SUL carrier and one for the NUL carrier. For random access in a cell configured with an SUL carrier, the network may indicate which carrier (NUL or SUL) to use. The UE may determine the SUL carrier, for example, if the measured quality of one or more reference signals is lower than a broadcast threshold. Uplink transmissions of the random access procedure (e.g., Msg1 1311 and / or Msg3 1313) can remain on the selected carrier. The UE may switch uplink carriers during the random access procedure (e.g., between Msg1 1311 and Msg3 1313) in one or more instances. For example, the UE may determine and / or switch uplink carriers for Msg1 1311 and / or Msg3 1313 based on a channel clear assessment (eg, listen-before-talk).

[0159] Figure 13B shows 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. The configuration message 1320 may be similar in some respects to the configuration message 1310. Figure 13B includes the transmission of two messages, Msg1 1321 and Msg2 1322. Msg1 1321 and Msg2 1322 may be similar in some respects to Msg1 1311 and Msg2 1312, respectively, shown in Figure 13A. As can be seen from Figures 13A and 13B, the contention-free random access procedure may not include messages similar to Msg3 1313 and / or Msg4 1314.

[0160] 13B may be initiated for beam failure recovery, other SI requests, SCell addition, and / or handover. For example, the base station may indicate or assign to the UE the preamble to be used for Msg1 1321. The UE may receive an indication of the preamble (e.g., ra-PreambleIndex) from the base station via PDCCH and / or RRC.

[0161] After transmitting the preamble, the UE may start a time window (e.g., ra-ResponseWindow) in which it monitors the PDCCH for the RAR. 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 for PDCCH transmissions addressed to the Cell RNTI (C-RNTI) over the search space. In the contention-free random access procedure shown in FIG. 13B, the UE may determine that the random access procedure has completed successfully after or in response to transmitting Msg1 1321 and receiving the corresponding Msg2 1322. The UE may determine that the random access procedure has completed successfully, for example, if the PDCCH transmission is addressed to the C-RNTI. The UE may determine that the random access procedure is successfully completed, for example, if the UE receives an RAR including a preamble identifier corresponding to the preamble transmitted by the UE and / or if the RAR includes a MAC sub-PDU including the preamble identifier. The UE may determine the response as an indication of a response acknowledgment to the SI request.

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

[0163] Msg A 1331 may be transmitted in an uplink transmission by the UE. Msg A 1331 may include one or more transmissions of preamble 1341 and / or one or more transmissions of transport block 1342. Transport block 1342 may include content similar and / or equivalent to the content of Msg3 1313 shown in FIG. 13A. Transport block 1342 may include UCI (e.g., SR, HARQ ACK / NACK, and / or similar). The UE may receive Msg B 1332 after or in response to the transmission of Msg A 1331. Msg B 1332 may include content similar and / or equivalent to the content of Msg2 1312 (e.g., RAR) shown in FIGS. 13A and 13B and / or Msg4 1314 shown in FIG. 13A.

[0164] The UE may initiate the two-step random access procedure of Figure 13C for licensed and / or unlicensed spectrum. The UE may determine whether to initiate the two-step random access procedure based on one or more factors. The 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, the cell size, the RRC state of the UE, the type of spectrum (e.g., licensed vs. unlicensed), and / or any other suitable factor.

[0165] The UE may determine radio resources and / or uplink transmit power for the preamble 1341 and / or the transport block 1342 included in Msg A 1331 based on the two-step RACH parameters included in the configuration message 1330. The RACH parameters may indicate a modulation and coding scheme (MCS), time-frequency resources, and / or power control for the preamble 1341 and / or the 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.

[0166] The transport block 1342 may include data (e.g., delay-sensitive data), a UE identifier, security information, and / or device information (e.g., International Mobile Subscriber Identity (IMSI)). The base station may send Msg B 1332 in response to Msg A 1331. Msg B 1332 may include at least one of a preamble identifier, a timing advance command, a power control command, an uplink grant (e.g., radio resource allocation and / or MCS), a UE identifier for contention resolution, and / or an RNTI (e.g., C-RNTI or TC-RNTI). The UE may determine that the two-step random access procedure is successfully completed 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 (e.g., transport block 1342) in Msg A 1331.

[0167] The UE and the base station may exchange control signaling, which 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). The 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.

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

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

[0170] DCIs may 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 notification. The P-RNTI may be predefined as "FFFE" in hexadecimal. A DCI with CRC parity bits scrambled with a system information RNTI (SI-RNTI) may indicate a broadcast transmission of system information. The SI-RNTI may 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 a unicast transmission of dynamic scheduling and / or a random access of PDCCH order trigger. A DCI with CRC parity bits scrambled with the Temporary Cell RNTI (TC-RNTI) may indicate contention resolution (e.g., Msg3 similar to Msg3 1313 shown in FIG. 13A). Encodings of other RNTIs 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 the like.

[0171] Depending on the purpose and / or content of the DCI, a base station may transmit the DCI in one or more DCI formats. For example, DCI format 0_0 may be used for scheduling the PUSCH in a cell. DCI format 0_0 may be a fallback DCI format (e.g., has a compact DCI payload). DCI format 0_1 ​​may be used for scheduling the PUSCH in a cell (e.g., has a larger DCI payload than DCI format 0_0). DCI format 1_0 may be used for scheduling the PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g., has a compact DCI payload). DCI format 1_1 may be used for scheduling the PDSCH in a cell (e.g., has a larger DCI payload than DCI format 1_0). DCI format 2_0 may be used to provide a slot format indication to a group of UEs. DCI format 2_1 may be used to inform a group of UEs of the physical resource blocks and / or OFDM symbols that the UE assumes are not intended for transmission to the UE. DCI format 2_2 may be used to transmit transmit power control (TPC) commands for PUCCH or PUSCH. DCI format 2_3 may be used to transmit 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 share the same DCI size.

[0172] After scrambling the DCI with the 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 payload size of the DCI and / or the base station's coverage, the base station may transmit the DCI via the PDCCH occupying several consecutive control channel elements (CCEs). The number of consecutive CCEs (referred to as the aggregation level) may be 1, 2, 4, 8, 16, and / or any other suitable number. A CCE may include a number of resource element groups (REGs) (e.g., 6). A REG may include a resource block within an OFDM symbol. The mapping of the coded and modulated DCI onto resource elements may be based on a mapping of CCEs and REGs (e.g., CCE to REG mapping).

[0173] FIG. 14A illustrates an example of a CORESET configuration for a bandwidth portion. A base station may transmit DCI via a PDCCH on one or more control resource sets (CORESETs). A CORESET may include time-frequency resources on which a UE attempts to decode the DCI using one or more search spaces. A base station may configure CORESETs in the time-frequency domain. In the example of FIG. 14A, a first CORESET 1401 and a second CORESET 1402 occur at the first symbol in a 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 of the slot. The CORESETs may have different numbers of resource blocks in the frequency domain.

[0174] FIG. 14B shows an example of CCE-to-REG mapping for DCI transmission on a CORESET and PDCCH processing. The CCE-to-REG mapping may be interleaved (e.g., to provide frequency diversity) or non-interleaved (e.g., to facilitate interference coordination and / or frequency-selective transmission of control channels). A base station may perform different or identical CCE-to-REG mappings on different CORESETs. A CORESET may be associated with a CCE-to-REG mapping by RRC configuration. A CORESET may be configured with an antenna port quasi-co-location (QCL) parameter. The QCL parameter of an antenna port may indicate the QCL information of a demodulation reference signal (DMRS) for PDCCH reception within the CORESET.

[0175] The base station may send an RRC message to the UE including configuration parameters for one or more CORESETs and one or more search space sets. The configuration parameters may indicate an association between the search space set and the CORESET. The search space set may include a set of PDCCH candidates formed by CCEs at a given aggregation level. The configuration parameters may indicate the number of PDCCH candidates to be monitored per aggregation level, a PDCCH monitoring periodicity and PDCCH monitoring pattern, one or more DCI formats to be 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 the common search space set may be predefined and known to the UE. The set of CCEs in the UE-specific search space set may be configured based on the UE's identity (e.g., C-RNTI).

[0176] As shown in FIG. 14B , the UE may determine time-frequency resources of the CORESET based on the RRC message. The UE may determine CCE-to-REG mapping (e.g., interleaved or non-interleaved, and / or mapping parameters) for the CORESET based on configuration parameters of the CORESET. The UE may determine the number of search space sets (e.g., up to 10) configured on the CORESET based on the RRC message. The UE may monitor a set of PDCCH candidates according to the configuration parameters of the search space sets. The UE may monitor a set of PDCCH candidates in one or more CORESETs to detect one or more DCIs. The monitoring may include decoding one or more PDCCH candidates of the set of PDCCH candidates according to the monitored DCI format. The monitoring may include decoding DCI content of one or more PDCCH candidates having possible (or configured) PDCCH positions, possible (or configured) PDCCH formats (e.g., the number of CCEs in the common search space, the number of PDCCH candidates, and / or the number of PDCCH candidates in the UE-specific search space), and possible (or configured) DCI formats. The decoding may be referred to as blind-blind-combined-blind decoding. The UE may determine the valid DCI for the UE in response to a CRC check (e.g., scrambling bits against CRC parity bits of the DCI matching the RNTI value). The UE may process information included in the DCI (e.g., scheduling assignment, uplink grant, power control, slot format indication, downlink preemption, and / or the like).

[0177] The UE may transmit uplink control signaling (e.g., uplink control information (UCI)) to the base station. The uplink control signaling may include a hybrid automatic repeat request (HARQ) acknowledgment for a received DL-SCH transport block. The UE may transmit the HARQ acknowledgment after receiving the DL-SCH transport block. The uplink control signaling may include channel state information (CSI) indicating the channel quality of the physical downlink channel. The UE may transmit the CSI to the base station. The base station may determine transmit format parameters (e.g., including multiple antennas and beamforming schemes) for the downlink transmission based on the received CSI. The uplink control signaling may include a scheduling request (SR). The UE may transmit the SR indicating that uplink data is available for transmission to the base station. The UE may transmit the UCI (e.g., a HARQ acknowledgment (HARQ-ACK), a CSI report, an SR, etc.) via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). A UE may transmit uplink control signaling via the PUCCH using one of several PUCCH formats.

[0178] There may be five PUCCH formats, and the UE may determine the PUCCH format based on the size of the UCI (e.g., the number of uplink symbols for UCI transmission and the number of UCI bits). PUCCH format 0 may have a length of one or two OFDM symbols and may contain two or fewer bits. The UE may use PUCCH format 0 to transmit UCI on PUCCH resources if the transmission is more than 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 between four and fourteen OFDM symbols and may contain two or fewer bits. The UE may use PUCCH format 1 if the transmission is 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. The UE may use PUCCH format 2 if the transmission is more than one or two symbols and the number of UCI bits is two or more. PUCCH format 3 may occupy between 4 and 14 OFDM symbols and may include more than 2 bits. A UE may use PUCCH format 3 if the transmission is four or more symbols, the number of UCI bits is two or more, and the PUCCH resource does not include an orthogonal cover code. PUCCH format 4 may occupy between 4 and 14 OFDM symbols and may include more than 2 bits. A UE may use PUCCH format 4 if the transmission is four or more symbols, the number of UCI bits is two or more, and the PUCCH resource includes an orthogonal cover code.

[0179] The base station may transmit configuration parameters for multiple PUCCH resource sets to the UE, for example, using an RRC message. Multiple PUCCH resource sets (e.g., up to four sets) may be configured on the uplink BWP of the cell. A PUCCH resource set may be configured with a PUCCH resource set index, multiple PUCCH resources with the PUCCH resource identified by a PUCCH resource identifier (e.g., pucch-Resourceid), and / or the number (e.g., maximum number) of UCI information bits that the UE may transmit using one of the multiple PUCCH resources in the PUCCH resource set. When configured with multiple PUCCH resource sets, 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 two or less, the UE may select the first PUCCH resource set whose PUCCH resource set 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 a first configuration value, the UE may select a second PUCCH resource set having 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 a second configuration value, the UE may select a third PUCCH resource set having 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 a third value (e.g., 1406), the UE may select a fourth PUCCH resource set having a PUCCH resource set index equal to '3'.

[0180] After determining a PUCCH resource set from the 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 the PUCCH resource based on a PUCCH resource indicator in 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 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.

[0181] 15 illustrates an example of a wireless device 1502 communicating with a base station 1504 in accordance with an embodiment of the present disclosure. The wireless device 1502 and the base station 1504 may be part of a mobile communication network, such as the mobile communication network 100 shown in FIG. 1A, the mobile communication network 150 shown in FIG. 1B, or other communication network. Only one wireless device 1502 and one base station 1504 are shown in FIG. 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 that shown in FIG. 15.

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

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

[0184] After being processed by processing system 1508, data to be transmitted to wireless device 1502 may be provided to transmit processing system 1510 of base station 1504. Similarly, after being processed by processing system 1518, data to be transmitted to base station 1504 may be provided to transmit processing system 1520 of wireless device 1502. Transmit processing system 1510 and transmit processing system 1520 may implement the OSI functions of Layer 1. Layer 1 may include the PHY layer with respect to FIGS. 2A, 2B, 3, and 4A. For transmit processing, the PHY layer may perform, for example, forward error correction coding of transport channels, interleaving, rate matching, mapping of transport channels to physical channels, modulation of physical channels, multiple-input multiple-output (MIMO) or multi-antenna processing, and / or the like.

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

[0186] 15, the wireless device 1502 and the base station 1504 may include multiple antennas. The 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), transmit / receive diversity, and / or beamforming. In other examples, the wireless device 1502 and / or the base station 1504 may have a single antenna.

[0187] Processing system 1508 and processing system 1518 may be associated with memory 1514 and memory 1524, respectively. Memory 1514 and memory 1524 (e.g., one or more non-transitory computer-readable media) may store computer program instructions or code that may be executed by processing system 1508 and / or processing system 1518 to perform one or more functions discussed herein. Although not shown in FIG. 15 , transmit processing system 1510, transmit processing system 1520, receive processing system 1512, and / or receive processing system 1522 may be coupled to memory (e.g., one or more non-transitory computer-readable media) that stores computer program instructions or code that may be executed to perform one or more of their respective functions.

[0188] The processing system 1508 and / or the processing system 1518 may include one or more controllers and / or one or more processors. The one or more controllers and / or the one or more processors may include, for example, a general-purpose processor, a digital signal processor (DSP), a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) and / or other programmable logic devices, discrete gate and / or transistor logic, discrete hardware components, on-board units, or any combination thereof. The processing system 1508 and / or the processing system 1518 may perform at least one of signal coding / processing, data processing, power control, input / output processing, and / or any other functionality that may enable the wireless device 1502 and the base station 1504 to operate in a wireless environment.

[0189] Processing system 1508 and / or processing system 1518 may be connected to one or more peripheral devices 1516 and one or more peripheral devices 1526, respectively. The one or more peripheral devices 1516 and one or more peripheral devices 1526 may include software and / or hardware that provide features and / or functionality, such as a speaker, a microphone, a keypad, a display, a touchpad, a power supply, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulation (FM) radio unit, a media player, an internet browser, an electronic control unit (e.g., for a vehicle), and / or one or more sensors (e.g., an accelerometer, gyroscope, temperature sensor, radar sensor, lidar sensor, ultrasonic sensor, light sensor, camera, and / or the like). Processing system 1508 and / or processing system 1518 may receive user input data and / or provide user output data from the one or more peripheral devices 1516 and / or one or more peripheral devices 1526. The processing system 1518 in the wireless device 1502 can receive power from a power source and / or may be configured to distribute power to other components in 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 a GPS chipset 1517 and a GPS chipset 1527, respectively. The GPS chipset 1517 and the GPS chipset 1527 may be configured to provide geographic location information of the wireless device 1502 and the base station 1504, respectively.

[0190] FIG. 16A shows an example structure for uplink transmission. A baseband signal representing a physical uplink shared channel may perform one or more functions. The one or more functions may include at least one of scrambling, modulation of scramble bits to generate complex-valued symbols, mapping of complex-valued modulation symbols onto one or several transmission layers, transform precoding to generate complex-valued symbols, precoding of the complex-valued symbols, mapping of the precoded complex-valued symbols to resource elements, generation of complex-valued time-domain single-carrier frequency-division multiple access (SC-FDMA) or CP-OFDM signals to antenna ports, and / or the like. In one example, if transform precoding is enabled, an SC-FDMA signal for uplink transmission may be generated. In one example, if transform precoding is not enabled, a CP-OFDM signal for uplink transmission may be generated according to FIG. 16A. These functions are shown by way of example, and it is anticipated that other mechanisms may be implemented in various embodiments.

[0191] 16B shows an example 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 for an antenna port. Filtering may be used before transmission.

[0192] 16C shows an example structure of a downlink transmission. The baseband signal representing the physical downlink channel can perform one or more functions. The one or more functions may include scrambling coded bits in a codeword to be transmitted on the physical channel, modulating the scrambled bits to generate complex-valued modulation symbols, mapping the complex-valued modulation symbols onto one or more transmission layers, precoding the complex-valued modulation symbols on the layers for transmission on the antenna ports, mapping the complex-valued modulation symbols of the antenna ports to resource elements, generating a complex-valued time-domain OFDM signal per antenna port, and / or the like. These functions are shown as examples, and it is anticipated that other mechanisms may be implemented in various embodiments.

[0193] 16D shows another example structure for modulating and upconverting a baseband signal to a carrier frequency. The baseband signal may be a complex-valued OFDM baseband signal for an antenna port. Filtering may be used before transmission.

[0194] A wireless device may receive one or more messages (e.g., RRC messages) from a base station including configuration parameters for multiple cells (e.g., a primary cell, a secondary cell). The wireless device may communicate with at least one base station (e.g., two or more base stations for dual connectivity) via the multiple cells. The one or more messages (e.g., as part of the configuration parameters) may include physical, MAC, RLC, PCDP, SDAP, and RRC layer parameters for configuring the wireless device. For example, the configuration parameters may include parameters for configuring physical and MAC layer channels, bearers, etc. For example, the 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.

[0195] A timer may begin execution when started and continue to run until stopped or expires. A timer may be started if it is not running or restarted if it is running. A timer may be associated with a value (e.g., a timer may be started or restarted from a value, or may start from zero and expire when the value is reached). A timer's duration may not be updated until the timer is stopped or expires (e.g., due to BWP switching). A timer may be used to measure the period / window of a process. When this specification refers to implementations and procedures related to one or more timers, it will be understood that there are multiple ways to implement one or more timers. For example, it will be understood that one or more of multiple ways for implementing a timer may be used to measure the period / 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, the time difference between two timestamps may be used instead of the start and expiration of the random access response window timer. When the timer is restarted, the process for measuring the time window may be restarted. Other example implementations may be provided for restarting the measurement of the time window.

[0196] A wireless device may receive / detect a DCI via a core set. The DCI may trigger transmission of a HARQ-ACK information bit. For example, the DCI may schedule a transport block (e.g., a PDSCH), and the wireless device may transmit the HARQ-ACK information bit of the transport block. For example, the DCI may indicate an SPS release, and the wireless device may transmit the HARQ-ACK information bit to acknowledge receipt of the DCI indicating the SPS release. In existing technology, a wireless device may determine uplink resources (e.g., PUCCH resources) for transmission of the HARQ-ACK information bit based on the core set from which the wireless device receives the DCI. The wireless device may determine the uplink resources based, for example, on the number of control channel elements (CCEs) of the core set. The wireless device may determine the uplink resources from which the wireless device receives the DCI based, for example, on the first / earliest / starting CCE of the core set.

[0197] In one example, a wireless device may receive configuration parameters, for example, from a base station. The configuration parameters may indicate control channel repetition, and the base station transmits multiple DCI / PDCCHs (or repetitions of DCI) over multiple core sets. The repetitions may be transmitted in multiple transmission / repetition opportunities (e.g., time slots). The wireless device may monitor multiple core sets at multiple transmission opportunities for the multiple DCI / PDCCHs (or repetitions of DCI). Thus, control channel repetition may increase the reliability and robustness of the control channel.

[0198] In existing technology, the co-implementation of uplink resource determination and control channel repetition may cause ambiguity / misalignment regarding the uplink resource used to transmit the HARQ-ACK information bit. In one embodiment, a wireless device may receive DCI via a first core set of multiple core sets. The DCI may trigger transmission of the HARQ-ACK information bit. In an implementation of the existing technology, the wireless device may determine a first uplink resource based on the first core set for transmission of the HARQ-ACK information bit. The wireless device may transmit the HARQ-ACK information bit via the first uplink resource. In one embodiment, the base station may not have information about which core set the wireless device successfully received the DCI on.

[0199] In one embodiment, the base station may determine the second uplink resource based on a second core set of the plurality of core sets for receiving the HARQ-ACK information bit. The base station may determine the second uplink resource based on the second core set, for example, randomly / blindly (or based on a rule unknown to the wireless device). The base station may monitor the second uplink resource for receiving the HARQ-ACK information bit. The first uplink resource determined by the wireless device and the second uplink resource determined by the base station may not be identical. Misalignment / ambiguity on the uplink resource may result in the loss of reception of the HARQ-ACK information bit. This may lead to increased retransmissions, increased delays / delays in successful communication, and increased power consumption.

[0200] In one embodiment, the base station may monitor the first uplink resource and the second uplink resource for reception of the HARQ-ACK information bit, which may increase power consumption at the base station. In one embodiment, the wireless device may transmit the HARQ-ACK information bit over the first uplink resource and the second uplink resource, which may increase power consumption at the wireless device.

[0201] Exemplary embodiments enhance / improve uplink resource determination when DCI, which triggers transmission of HARQ-ACK information bits, is transmitted by a base station and via multiple core sets. In exemplary embodiments, the wireless device and base station may determine a selected core set from among multiple core sets based on a predefined rule (e.g., the lowest core set index, or the core set with the lowest / highest bandwidth, or the core set monitored at the last monitoring opportunity). The wireless device and base station may determine uplink resources for the HARQ-ACK information bits based on the selected core set. This may reduce the possibility of misalignment on uplink resources used to transmit HARQ-ACK information bit symbols. This may reduce delays / latencies in successful communication, reduce power consumption, and reduce retransmissions.

[0202] A wireless device may receive / detect DCI (e.g., DCI 1-0) that schedules a transport block (e.g., a PDSCH) via a core set. The wireless device may receive DCI via a common search space set (CSS) of the core set. In existing technology, a wireless device may receive a transport block based on the lowest resource block (RB) of the core set.

[0203] In one example, a wireless device may receive configuration parameters, for example, from a base station. The configuration parameters may indicate control channel repetition, and the base station transmits multiple DCI / PDCCHs (or repetitions of DCI) over multiple core sets. The repetitions may be transmitted in multiple transmission / repetition opportunities (e.g., time slots). The wireless device may monitor multiple core sets at multiple transmission opportunities for the multiple DCI / PDCCHs (or repetitions of DCI). Thus, control channel repetition may increase the reliability and robustness of the control channel.

[0204] In existing technology, the joint implementation of resource block determination and control channel repetition can cause ambiguity / misalignment regarding the starting resource block used to receive a transport block. In one example, a wireless device may receive DCI scheduling a transport block via a first core set of a plurality of core sets. The wireless device may not receive (or may miss receiving) DCI scheduling a transport block via a second core set of the plurality of core sets. In an implementation of existing technology, a wireless device may receive a transport block based on the lowest RB of the first core set. In one example, a base station may not have information about which core set the wireless device successfully received DCI on.

[0205] In one embodiment, the base station may transmit a transport block based on the lowest RBs of the second core set. The base station may, for example, randomly / blindly (or based on a rule unknown to the wireless device) determine the lowest RBs of the second core set. The lowest RBs of the first core set used by the wireless device to receive the transport block and the lowest RBs of the second core set used by the base station to transmit the transport block may not be the same. Misalignment / ambiguity of the lowest RBs may result in missed reception of the transport block, which may lead to increased retransmissions, increased delays / delays in successful communication, and increased power consumption.

[0206] In one embodiment, the base station may transmit a transport block based on the lowest RBs of the first core set and the lowest RBs of the second core set, which may increase power consumption at the base station, which may increase resource overhead.

[0207] Exemplary embodiments enhance / improve resource block determination when DCI scheduling a transport block is transmitted by a base station and via multiple core sets. In the exemplary embodiments, a wireless device and a base station may determine a selected core set from among multiple core sets based on a predefined rule (e.g., the lowest core set index, or the core set with the lowest / highest bandwidth, or the core set monitored at the last monitoring opportunity). The wireless device may receive a transport block based on the lowest RBs of the selected core set, and the base station may transmit a transport block based on the lowest RBs of the selected core set. This can reduce the possibility of misalignment of the lowest RBs used for transmitting and receiving a transport block. This can reduce delays / delays in successful communication, reduce resource overhead, reduce power consumption, and reduce retransmissions.

[0208] The PDCCH may carry scheduling assignments and other control information in the form of DCI messages. Information carried by the PDCCH may be referred to as DCI. A base station may transmit multiple PDCCHs in the control region to a wireless device. The wireless device may monitor multiple PDCCHs. A PDCCH may include a set of one or more control channel elements (CCEs). The monitoring may include performing blind decoding on multiple candidate PDCCHs. The blind decoding may include performing cyclic redundancy check (CRC) demasking on each of the multiple candidate PDCCHs using a radio network temporary identifier (RNTI). The blind decoding may be used to detect the PDCCH. If no CRC error is detected, the wireless device may determine that the PDCCH carries unique control information.

[0209] FIG. 17 illustrates example configuration parameters for control and / or data according to one aspect of an embodiment of the present disclosure. A wireless device may receive one or more radio resource control (RRC) messages including configuration parameters for a cell. The configuration parameters may include one or more parameters of a serving cell configuration (e.g., ServingCellConfig). The one or more parameters of the serving cell configuration may indicate one or more downlink bandwidth portions (e.g., a list of BWP-downlink). The one or more parameters of the serving cell configuration may indicate one or more uplink bandwidth portions (e.g., a list of BWP-uplink). The downlink bandwidth portion (e.g., BWP-downlink) and / or the uplink bandwidth portion (e.g., BWP-uplink) may include a bandwidth portion index (e.g., bwp-Id), a configuration parameter of a cell-common downlink bandwidth portion (e.g., BWP-downlink-common), and / or a UE-specific downlink bandwidth portion (e.g., BDelink-Id). For example, the bandwidth portion index (bwp-Id) may indicate the bandwidth portion configuration, and the bandwidth portion index is the bandwidth portion index. The bandwidth portion configuration may include location and bandwidth information (locationAndBandwidth). The locationAndBandwidth may indicate a starting resource block (RB) of the bandwidth portion and a bandwidth of the bandwidth portion based on a reference point (e.g., point A of the carrier / cell of the bandwidth portion). The bandwidth portion configuration may include a subcarrier spacing (e.g., subcarrierSpacing) and a cyclic prefix (e.g., cyclicPrefix). For example, the subcarrier spacing may be one of 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, 480 kHz, and 960 kHz. For example, the cyclic prefix may be one of a normal cyclic prefix and an extended cyclic prefix.

[0210] Configuration parameters for a cell-specific downlink bandwidth (e.g., BWP-DownlinkCommon) may include genericParameters, pdcch-ConfigCommon, and / or pdsch-ConfigCommon. For example, pdcch-ConfigCommon may include cell-specific parameters for receiving downlink control information (DCI) via a cell-specific downlink bandwidth portion (e.g., initial BWP). For example, pdsch-ConfigCommon may include cell-specific parameters for receiving a PDSCH of a transport block (TB) via a cell-specific downlink bandwidth portion. Configuration parameters for a UE-specific downlink bandwidth portion (e.g., BWP-DownlinkDedicated) may include pdcch-Config, pdsch-Config, sps-Config, and / or radioLinkMonitoringConfig (e.g., RLM-Config). The configuration parameters may include sps-ConfigList and / or beamFailureRecoverySCellConfig. For example, beamFailureRecoverySCellConfig may include reference signal parameters for beam failure recovery of a secondary cell. For example, pdcch-Config may include parameters for receiving DCI for a UE-specific downlink bandwidth portion. For example, pdsch-Config may include parameters for receiving a PDSCH of a TB for a UE-specific downlink bandwidth portion. For example, sps-Config may include parameters for receiving a semi-persistent scheduling PDSCH. The base station may configure an SPS for a BWP or a list of SPSs for a BWP. For example, radioLinkMonitoringConfig may include parameters for radio link monitoring.

[0211] The configuration parameters of pdcch-Config may include at least one of a core set, a search space set, downlink preemption (e.g., downlinkPreemption), transmit power control (TPC) for the PUSCH (e.g., tpc-PUSCH), TPC for the PUCCH, and / or TPC for the SRS. The configuration parameters may include a list of search space switching groups (e.g., searchesSpaceSwitchingGroup), a search space switching timer (e.g., searchSpaceSwitchingTimer), uplink cancellation, and / or a monitoring capability configuration (e.g., monitoringCapabilityConfig). The base station may configure the list of search space switching groups, where a wireless device may switch from a first search space group to a second search space group based on the search space switching timer or a rule, indication, or event. The base station may configure up to K (e.g., K = 3) core sets for the BWP of the cell. The downlink preemption may indicate whether to monitor the downlink preemption indication of the cell. The monitoring capability setting may indicate whether the wireless device's monitoring capability is configured for the cell, and if so, whether the capability is based on basic or advanced capabilities. The base station may configure a search space of up to M (e.g., M=10) for the BWP of the cell. The tpc-PUCH, tpc-PUSCH, or tpc-SRS may enable and / or configure reception of TPC commands for the PUCCH, PUSCH, or SRS, respectively. The uplink withdrawal may indicate monitoring the uplink withdrawal of the cell.

[0212] The configuration parameters of pdcch-ConfigCommon may include control resource set zero (e.g., controlResourceSetZero), a common control resource set (e.g., commonControlResourceSet), search space zero (e.g., searchSpaceZero), a list of common search spaces (e.g., commonSearchSpaceList), a search space for SIB1 (e.g., searchSpaceSIB1), a search space for other SIBs (e.g., searchSpaceOtherSystemInformation), a search space for paging (e.g., pagingSearchSpace), a search space for random access (e.g., ra-SearchSpace), and / or a first PDCCH monitoring opportunity. Control resource set zero may include parameters for a first core set having an index value zero. Core set zero may be configured for an initial bandwidth portion of the cell. The wireless device may use control resource set zero in the BWP of the cell, and the BWP is not the initial BWP of the cell based on one or more conditions. For example, the numerology of the BWP may be the same as the numerology of the initial BWP. For example, the BWP may include the initial BWP. For example, the BWP may include control resource set zero. The common control resource set may be an additional common core set that may be used for the common search space (CSS) or the UE-specific search space (USS). The base station may configure the bandwidth of the common control resource set to be smaller than or equal to the bandwidth of control resource set zero. The base station may configure the common control resource set so that the common control resource set is included in control resource set zero (e.g., CORESET#0). The list of common search spaces may include one or more CSSs. The list of common search spaces may not include a search space with index zero (e.g., SS#0). The first PDCCH monitoring occasion may indicate a monitoring occasion for a paging occasion.The base station may configure search spaces for monitoring DCI for paging (e.g., pagingSearchSpace), RAR monitoring (e.g., ra-SearchSpace), SIB1 (e.g., searchSpaceSIB1), and / or other SIBs other than SIB1 (e.g., searchSpaceOtherSystemInformation). A search space with index zero (e.g., searchSpaceZero, SS#0) may be configured for the initial BWP of the cell. Similar to core set#0, SS#0 may be used in the BWP of the cell based on one or more conditions.

[0213] FIG. 18 illustrates example configuration parameters of a core set according to one aspect of an embodiment of the present disclosure. The ControlResourceSet (CoreSet) may include a core set index (e.g., ControlResourceSetID), frequency domain resources (e.g., frequencyDomainResources), a core set duration (e.g., a number of OFDM symbols between [1, maxCoReSetDuration], where maxCoReSetDuration=3), and a control channel element (CCE) to resource element group (REG) mapping type (e.g., between interleaved and non-interleaved). When the CCE-REG mapping type is configured as interleaved, the base station may also configure the REG bundle size (e.g., reg-BundleSize) and interleaver size (e.g., interleaverSize). The core set may also include a precoder granularity (e.g., between the same as the REG bundle (e.g., sameAsREG-bundle) and across all contiguous RBs (e.g., allContiguousRBs)). For example, if the precoder granularity is configured as "same as REG bundle," the wireless device may assume that the same precoder is used across the REGs in the bundle. For example, if the precoder granularity is configured as "across all contiguous RBs," the wireless device may assume that the same precoder is used across the contiguous RBs in the core set. The core set may include a list of TCI states, and the core set is not core set #0. The core set may include a parameter for TCI presence in the DCI. When the core set is configured with TCI presence in the DCI, the wireless device may expect a DCI format that includes a TCI indication in the DCI based on the DCI format scheduled via the search space associated with the core set. For example, the DCI format may be DCI format 1_1 and / or DCI format 0_1.The core set may optionally include one or more of a DMR scrambling identity, a core set pool index, an extended core set index (e.g., ControlResourceSetId-v16xy), a DCI present in the DCI for DCI format 1_2, and an RB offset. For example, if the extended core set index is present in the core set configuration, the wireless device may ignore the core set index. The extended core set index may indicate a value between [0, ..., 15], while the core set index may indicate a value between [0, ..., 11].

[0214] The core set is associated with the search space, and the wireless device may determine search space candidates and / or monitoring opportunities for the search space based on the configuration of the search space and the core set. The search space is associated with the core set, and the wireless device may determine search space candidates and / or monitoring opportunities for the search space based on the configuration of the search space and the core set. The parameters of the search space may include an index of the core set when the search space is associated with a core set or when a core set is associated with the search space.

[0215] The search space may include a search space index (e.g., searchSpaceId), an associated core set index (e.g., controlResourceSetId), a monitoring periodicity and offset (e.g., periodicity in terms of slot number and offset in terms of slot number between [1, 2560] slots for the periodicity, offset between [0, ..., P-1] where P is the periodicity). The search space may include a duration, and the wireless device may monitor the search space in consecutive slots starting from the monitoring opportunity based on the duration. The base station may not configure the period of the search space for scheduling DCI format 2_0. The maximum duration value may be the periodicity - 1 (e.g., repeated in each slot within the interval / periodicity). The search space may include a bitmap of the size of the monitoring symbols in the slot (e.g., 12 for extended cyclic prefix (CP) and 14 for normal CP). The search space may include multiple candidate sets for each aggregation level (e.g., aggregation level L= (e.g., a first number of candidates for aggregation level L=1, a second number of candidates for aggregation level L=2, etc.) The search space may include a search space type (e.g., between CSS and USS). Each CSS or USS may include one or more DCI formats to be monitored in the search space. For example, for a CSS, one or more of DCI format 0_0 / 1_0, DCI format 2_0, DCI format 2_1, DCI format 2_2, and DCI format 2_3 may be configured. For a USS, the base station may configure a list of search space group indexes (if configured). For a USS, the base station may configure frequency monitoring opportunities / positions for wideband operation in unlicensed or licensed spectrum. In this specification, DCI format 0_0 / 1_0 may be used interchangeably with DCI format 0-0 / 1-0 or fallback DCI format. DCI format 0_1 / 1_1 may be used interchangeably with DCI format 0-1 / 1-1 or non-fallback DCI format.DCI formats 0_2 / 1_2 may be used interchangeably with DCI formats 0-2 / 1-2 or non-fallback DCI formats.

[0216] The configuration parameters of pdsch-Config may include parameters for receiving transport blocks. For example, the configuration parameters may include a data scrambling ID for the PDSCH, a DM-RS mapping type (e.g., between mapping type A and mapping type B), a list of transmission configuration indicator (TCI) states, parameters for a (virtual RB) VRB to (physical RB) PRB interleaver, a resource allocation type (e.g., resource allocation type 0, resource allocation type 1, or dynamic switching between the two), a list of time-domain allocations, an aggregation factor, a list of rate-matching patterns, a resource block group (RBG) size, an MCS table (e.g., between QAM256 and QAM64LowSE, between high MCS or low MCS), a maximum codeword (e.g., between 1 or 2), parameters related to PRB bundling, a maximum MIMO layer, a minimum scheduling offset related to power saving techniques, and / or one or more parameters related to DCI format 1_2 (e.g., compact DCI or small DCI format).

[0217] In one embodiment, a base station may configure a core set having multiple TCI states. The base station may indicate, via a MAC CE command or a DCI command, a TCI of multiple TCI states for the core set as an active TCI state. For example, a serving cell index (e.g., serving cell ID) may indicate an index of a serving cell to which a MAC CE command applies. A core set index (e.g., CORESET ID) may indicate a core set index to which a MAC CE command applies. A TCI state index (e.g., TCI-State-ID) may indicate a TCI state identified by a TCI-State-Id. For example, if the core set is CORESET#0, the TCI-State-ID may indicate one of the first 64 TCI states configured for the pdsch-Config of the BWP of the serving cell. The BWP of the serving cell may be the active BWP of the cell. If the core set is not CORESET#0 (eg, if the CORESET ID is not zero), the TCI state ID may indicate a TCI state among multiple TCI states configured for the core set in pdcch-Config.

[0218] In one embodiment, a physical downlink control channel (PDCCH) may include one or more control channel elements (CCEs). For example, a PDCCH may include one CCE, which may correspond to an aggregation level (AL) of 1. For example, a PDCCH may include two CCEs, which may correspond to an AL of 2 (AL=2). For example, a PDCCH may include four CCEs, which may correspond to an AL of 4 (AL=4). For example, a PDCCH may include eight CCEs, which may correspond to an AL of 8 (AL=8). For example, a PDCCH may include 16 CCEs, which may correspond to an AL of 16 (AL=16).

[0219] In an embodiment, the PDCCH may be carried over one or more control resource sets (core sets). A core set may include N_rb_coreset resource blocks (RBs) in the frequency domain and N_symbol_coreset symbols in the time domain. For example, N_rb_coreset may be a multiple of 6 RBs (e.g., 6, 12, 18, ...). For example, N_symbol_coreset may be 1, 2, or 3. A CCE may include M (e.g., M=6) resource element groups (REGs). For example, one REG may include one RB in one OFDM symbol. The REGs in the core set may be ordered / numbered in increasing order in a time-first manner, starting from 0 for the first OFDM symbol and the smallest number (e.g., lowest frequency) of RBs in the core set. The wireless device may increase the numbering of the first OFDM symbol by increasing the frequency position or RB index. The wireless device may move to the next symbol in response to all RBs of the first symbol being indexed. The wireless device may map one or more REG indices to one or more 6 RBs of the N_rb_coreset RBs within the N_symbol_coreset OFDM symbols of the core set.

[0220] In one embodiment, a wireless device may receive configuration parameters from a base station. The configuration parameters may indicate one or more core sets. One core set may be associated with one CCE-REG mapping. For example, a single core set may have a single CCE mapping to physical RBs / resources of a single core set. For example, the CCE-REG of a core set may be interleaved or non-interleaved. For example, a REG bundle may include L consecutive REGs (e.g., iL, iL+1, ..., iL+L-1). For example, L may be the REG bundle size (e.g., L=2 or 6 if N_symbol_coreset=1, and L=N_symbol_coreset or 6 if N_symbol_coreset is 2 or 3). The index (e.g., i) of the REG bundle may be in the range of [0, 1, ..., N_reg_coreset / L-1]. For example, N_reg_coreset may be defined as N_rb_coreset*N_symbol_coreset (e.g., the total number of REGs in a single core set). For example, the jth indexed CCE may include one or more REG bundles of {f(6j / L), f(6j / L+1), ..., f(6j / L+6 / L-1)}. For example, f(x) may be an interleaver function. In one embodiment, when the CCE-to-REG mapping may be non-interleaved, f(x) may be x (e.g., the jth CCE may be 6j / L, 6j / L+1, ..., and 6j / L+6 / L-1). When the CCE-to-REG mapping may be interleaved, L may be defined as one of {2, 6} when N_symbol_coreset is 1, or as one of {N_symbol_coreset, 6} when N_symbol_coreset is 2 or 3.If the CCE to REG mapping can be interleaved, the function f(x) may be defined as (rC+c+n_shift)mod(N_reg_coreset / L), where x=cR+r, r=0,1,...,R-1, c=0,1,...,C-1, C=N_reg_coreset / (L*R), and R is one of {2, 3, 6}.

[0221] For example, the configuration parameters may include frequencyDomainResources, which may define N_rb_coreset. The configuration parameters may include a period, which may define N_symbol_coreset. The configuration parameters may include cce-REG-MappingType, which may select between interleaved mapping or non-interleaved mapping. The configuration parameters may include reg-BundleSize, which may define a value of L for interleaved mapping. For non-interleaved mapping, L=6 may be pre-set. The configuration parameters may include shiftIndex, which may determine n_shift as one of {0, 1, ..., 274}. The wireless device may determine / assume the same precoding for REGs in a REG bundle when the precoder granularity (e.g., indicated / configured by the configuration parameter precoderGranularity) is configured as sameAsREG-bundle. The wireless device may determine / assume the same precoding for all REGs in a set of contiguous RBs of a core set when precoderGranularity is configured as allContiguousRBs.

[0222] A first core set (e.g., CORESET#0) may be defined / configured with L=6, R=2, n_shift=cell ID, and precoderGranularity=sameAsREG-bundle.

[0223] In one embodiment, a base station may transmit one or more messages including configuration parameters. The configuration parameters may be for multiple serving cells for a wireless device. The configuration parameters may include parameters enabling control channel repetition. For example, the control channel repetition may be transmitted via one or more serving cells. The control channel repetition may schedule one or more resources for a transport block. The transport block may be transmitted via one or more PDSCHs or one or more PUSCHs. For example, the control channel repetition may be transmitted via a single cell, which may operate with a single transmission / reception point (TRP) or multiple TRPs. The base station may transmit one or more control channels for the control channel repetition via one or more resources (e.g., multiple downlink control signal / channel transmission opportunities) in different frequency resources (e.g., repetition in the frequency domain or multiple carriers / cells). The one or more resources may overlap in the time domain. The base station may transmit one or more second control channels for the control channel repetition via one or more second resources (e.g., multiple downlink control signal / channel transmission opportunities) in different time resources (e.g., repetition in the time domain or multiple slots). One or more second resources may overlap in the frequency domain. For example, a base station may transmit repetitions of a control channel repetition over multiple core sets of a single cell. For example, a base station may transmit repetitions of a control channel repetition over multiple search spaces of a single cell.

[0224] In one embodiment, a control channel repetition may be transmitted via multiple PDCCHs. For example, a PDCCH may refer to a physical control channel transmitted in one search space candidate. A search space candidate may include one or more CCEs based on an aggregation level. Multiple PDCCHs may be transmitted via multiple core sets for multiple cells. For example, a base station may transmit PDCCHs for multiple PDCCHs via a core set of cells for multiple cells. Multiple PDCCHs may be transmitted via multiple core sets for cells. For example, a base station may transmit PDCCHs for multiple PDCCHs via a core set of core sets for multiple core sets. Multiple PDCCHs may be transmitted via multiple search spaces, and PDCCHs for multiple PDCCHs may be transmitted via search spaces of multiple search spaces. Multiple PDCCHs may be transmitted via multiple search space candidates, and each PDCCH of the multiple PDCCHs may be transmitted via a respective search space candidate of the multiple search space candidates. The multiple search space candidates may belong to a single search space or multiple search spaces. A search space may include a set of search space candidates for a monitoring opportunity. A search space monitoring opportunity may refer to a timing opportunity at which a wireless device may monitor search space candidates for receiving a DCI / a PDCCH.

[0225] In one embodiment, the PDCCHs of the multiple PDCCHs for a control channel repetition may convey / transmit DCI based on a DCI format. For example, a first DCI of a first PDCCH of the multiple PDCCHs may be the same as a second DCI of a second PDCCH of the multiple PDCCHs. For example, the content of the first DCI / PDCCH may be the same as the content of the second DCI / PDCCH. Based on the same content of the multiple PDCCHs, the wireless device may aggregate the multiple DCI / PDCCHs before decoding the DCI / PDCCHs. For example, the wireless device may need to determine a reference frequency domain resource (e.g., a reference downlink control signal / channel transmission / repetition opportunity) and / or a reference time domain resource (e.g., a reference downlink control signal / channel transmission / repetition opportunity) and / or a reference CCE index and / or a reference REG index when the control channel repetition is transmitted / performed via equal-content DCI / PDCCHs. For example, the wireless device may determine an aggregated DCI / PDCCH by aggregating the multiple DCI / PDCCHs. The wireless device can decode the aggregated DCI / PDCCH.

[0226] For example, reference frequency domain resources for the multiple DCI / PDCCHs may be determined based on the earliest PDCCH (or the latest PDCCH) of the multiple PDCCHs. For example, if a first PDCCH of the multiple PDCCHs is transmitted in slot n and a second PDCCH of the multiple PDCCHs is transmitted in slot n+1, the first PDCCH may determine the reference frequency domain resource. Similarly, reference time domain resources and / or reference CCE indexes and / or reference REGs may be determined based on the earliest PDCCH or the latest PDCCH. Reference frequency (and / or time) domain resources for the multiple DCI / PDCCHs may be determined based on CORESET indices of one or more CORESETs in which the multiple DCI / PDCCHs are transmitted. For example, the minimum (or maximum) core set index of one or more CORESETs may be used for the determination.

[0227] Reference frequency (and / or time) domain resources for the multiple DCI / PDCCHs may be determined based on search space indexes of one or more search spaces in which the multiple DCI / PDCCHs are transmitted. For example, the minimum (or maximum) index of the one or more search spaces may be used for the determination. Reference frequency domain resources for the multiple DCI / PDCCHs may be determined based on cell indexes of one or more cells in which the multiple DCI / PDCCHs are transmitted. For example, the minimum (or maximum) index of the one or more cells may be used for the determination. Similarly, reference time domain resources and / or reference CCE indexes and / or reference REGs may be determined based on a CORESET index, a search space index, and / or a cell index. A combination of the transmission time, CORESET index, search space, and / or cell index may be used. For example, a first reference frequency domain resource may be determined based on the transmission time of the DCI / PDCCH. When multiple DCI / PDCCHs are transmitted simultaneously, the wireless device may further identify a reference DCI / PDCCH from among the multiple DCI / PDCCHs using the CORESET index, search space index, and / or cell index. The wireless device may determine a reference DCI / PDCCH for determining a reference frequency domain resource, a reference time domain resource, a reference CCE index, and / or a reference REG index.

[0228] In one embodiment, the base station may configure / indicate a maximum repetition number K for control channel repetition by / via a configuration parameter. The base station may transmit a repetition number M that is less than K. In response to M being less than K, the wireless device may determine a reference DCI / PDCCH based on a candidate DCI / PDCCH in the Kth repetition, regardless of whether the Kth repetition was actually transmitted (or whether the Kth repetition was actually received). The wireless device may determine a reference DCI / PDCCH based on a first DCI / PDCCH that is the first repetition. The wireless device may determine a reference DCI / PDCCH based on the last DCI / PDCCH that was actually transmitted (e.g., the Mth repetition). For convenience, this type of control channel repetition (e.g., the same content is repeated across multiple DCI / PDCCHs) may be referred to herein as a first control channel repetition mode (e.g., mode 1, repetition mode 1, first repetition mode). In one embodiment, the base station may configure a list of time domain resource allocation entries. The time-domain resource allocation entry may include a number of repetitions of the control channel, a scheduling offset between the control channel and the PDSCH, and / or a number of PDSCH repetitions. For example, the number of repetitions of the control channel may represent a repetition number K. Based on the repetition number, the wireless device may determine a reference DCI / PDCCH timing based on the Kth DCI / PDCCH repetition. The repeated DCI / PDCCH may indicate an entry in a list of time-domain resource allocation entries.

[0229] In one embodiment, a first DCI / PDCCH of the plurality of DCI / PDCCHs may be different from a second DCI / PDCCH of the plurality of DCI / PDCCHs. For example, the wireless device may not aggregate the first DCI / PDCCH and the second DCI / PDCCH because the content of the first DCI / PDCCH may be different. The wireless device may attempt to decode the first DCI / PDCCH separately from the second DCI / PDCCH. For example, the wireless device may complete decoding of a control channel repetition when the wireless device receives at least one DCI / PDCCH of the plurality of DCI / PDCCHs. For example, when the wireless device receives at least one DCI / PDCCH of the plurality of DCI / PDCCHs, the wireless device may receive or transmit a TB scheduled by the plurality of DCI / PDCCHs. Herein, this type of control channel repetition (e.g., potentially different content is transmitted via multiple DCI / PDCCHs, and the DCI / PDCCHs of the multiple DCI / PDCCHs may schedule one or more resources of a transport block) may be referred to as a second control channel repetition mode (e.g., mode 2, repeat mode 2, second repetition mode). For example, a reference DCI / PDCCH of the multiple DCI / PDCCHs based on the second control channel repetition mode may be each DCI / PDCCH received by the wireless device.

[0230] FIG. 19 illustrates an example of PDCCH repetition according to one aspect of an embodiment of the present disclosure. The base station may transmit one or more RRC messages including configuration parameters. The configuration parameters may include parameters for control channel repetition. The parameters may include one or more scheduling carriers / cells for transmitting one or more PDCCHs / DCIs of the repeated control channel (or control channel repetition). The parameters may include one or more search spaces for the control channel repetition. FIG. 19 illustrates an example of enabling control channel repetition via a first search space (SS#1) of a first carrier / cell (DL carrier#0). The parameters may indicate one or more indices of one or more search spaces of the first carrier and / or a carrier / cell index of the first carrier. The base station may transmit a first PDCCH and schedule a TB via the first carrier via the first search space of the first carrier. The base station may transmit a second PDCCH, scheduling the TB via the first carrier via the first search space of the first carrier. The first PDCCH and the second PDCCH may be transmitted via multiple monitoring opportunities of the first search space. The wireless device may aggregate the first PDCCH and the second PDCCH based on the first control channel repetition mode, or may attempt to independently receive / decode each PDCCH based on the second control channel repetition mode. Based on the first PDCCH and / or the second PDCCH, the wireless device may receive a TB.

[0231] In one embodiment, the base station may transmit one or more RRC messages indicating enabled control channel repetitions for the first carrier / cell. Based on the indication of the control channel repetitions, the wireless device may determine one or more first search spaces of the first carrier / cell for the control channel repetitions based on the active BWP of the first carrier / cell. For example, the one or more first search spaces may be configured in a non-fallback DCI format, or may be configured in DCI format 1_1 and / or DCI format 1_2 and / or DCI format 0_1 ​​and / or DCI format 0_2. In one embodiment, the one or more RRC messages may indicate one or more search space indices of the one or more first search spaces for the control channel repetitions. The one or more RRC messages may indicate one or more DCI formats, and the wireless device may apply the control channel repetitions. The wireless device may determine one or more first search spaces of the first carrier / cell based on the one or more DCI formats of the control channel repetitions.

[0232] In one embodiment, a base station may transmit multiple DCI / PDCCHs via multiple TRPs, or via multiple core set pools, or via multiple core set groups, to schedule resources for a transport block of a cell. For example, the base station may configure a first TRP (or a first core set pool) for a first cell via one or more RRC messages. The one or more RRC messages may include configuration parameters. The configuration parameters may include a first core set pool for the first cell. The configuration parameters may include a second core set pool for the first cell. For example, the second core set pool may correspond to a second TRP for the first cell. The base station may transmit the first DCI / PDCCH via a first search space of a first core set in the first core set pool. The base station may transmit the second DCI / PDCCH via a second search space of a second core set in the second core set pool. The first DCI / PDCCH and the second DCI / PDCCH may schedule resources for a transport block. The primary / PDCCH and the secondary DCI / PDCCH may be repeated transmissions of control information (e.g., DCI). A transport block may be transmitted, for example, via a primary TRP and a secondary TRP. A transport block may be transmitted based on multiple TCI states. A transport block may be transmitted based on a TCI state, and a TCI state is associated with multiple TCI states. A transport block may be transmitted, for example, via a primary TRP or a secondary TRP.

[0233] The configuration parameter may indicate a control channel repetition enabled / configured for the first cell. For example, a parameter for a control channel repetition mode may be configured. The control channel repetition mode may be a first control channel repetition mode or a second control channel repetition mode. The configuration parameter may indicate a first core set associated with (or configured in) a first core set pool. The configuration parameter may indicate a second core set associated with (or configured in) a second core set pool. The wireless device may determine a pair of a first core set and a second core set on which the repeated DCI / PDCCH may be transmitted based on a rule. For example, the wireless device may determine the first core set of the first core set pool based on a search space associated with the first core set, and the wireless device may monitor DCI formats via the search space. For example, the DCI format may be DCI format 1_1, or DCI format 0_1, or DCI format 1_2, or DCI format 0_2 (or DCI format 3_0, or DCI format 3_1). If there are multiple first search spaces for a first core set pool configured with DCI formats, the wireless device may determine multiple first core sets for the first core set pool. Similarly, the wireless device may determine a second core set for a second core set pool based on a search space associated with a second core set, and the wireless device may monitor the DCI formats via the search space. If there are multiple second search spaces for a second core set pool configured with DCI formats, the wireless device may determine multiple second search spaces. In one embodiment, the wireless device may be configured with at most one search space for a DCI format in each core set pool.

[0234] In one embodiment, the wireless device may determine a second core set of a second core set pool based on a first core set index of a first core set of the first core set pool. For example, the second index of the second core set may be the first core set index + GAP. For example, GAP may be a determined / predetermined value (e.g., 0, 12). For example, the configuration parameters may include a parameter indicating the value of GAP. In one embodiment, the wireless device may determine a second core set based on a second search space associated with the second core set and the first search space. For example, the index of the second search space may be the first index of the first search space + SS-GAP. For example, SS-GAP may be a predetermined value (e.g., 20, 0). For example, the wireless device may determine a second core set and / or a second search space based on an association configured by the configuration parameters. For example, the configuration parameters may indicate an association between each of the core sets / search spaces associated with the first core set pool and each of the core sets / search spaces associated with the second core set pool. In one embodiment, the configuration parameters may include a first search space of a first core set and / or a first core set pool. The wireless device may monitor a first DCI / PDCCH via the first search space of the first core set pool. The configuration parameters may indicate / include a parameter indicating control channel repetition across multiple TRPs or multiple core set pools for the first core set or first search space. Based on the parameter, the wireless device may determine a second search space of a second core set or second core set pool. For example, the wireless device may determine the second core set based on one or more parameters of the first core set. For example, the same set of resource blocks configured for the first core set may be used for the second core set. For example, monitoring opportunities for the first search space may be used to determine monitoring opportunities for the second search space.

[0235] In one embodiment, the base station may indicate control channel repetition based on (or for) a core set. For example, the base station may transmit multiple DCI / PDCCHs via the core set. The base station may transmit multiple DCI / PDCCHs via multiple TRPs. The base station may transmit one of multiple RRC messages and / or MAC CEs indicating that multiple TCI states are activated for the core set. For example, the multiple TCI states may include a first TCI state corresponding to a first TRP of the multiple TRPs and a second TCI state corresponding to a second TRP of the multiple TRPs. The base station may transmit one or more second RRC messages including configuration parameters for the core set. For example, the configuration parameters may indicate control channel repetition based on the core set. The configuration parameters may indicate control channel repetition across the multiple TRPs. The configuration parameters may indicate a repetition pattern across the multiple TRPs. For example, a repetition pattern (e.g., a TRP switching pattern) may be [0,...,0,1,...,1], where 0 may represent the first TRP of the multiple TRPs and 1 may represent the second TRP of the multiple TRPs. A base station may indicate, for example, via a configuration parameter, a bitmap indicating the number of control channel repetitions. Each bit of the bitmap may represent which TRP may transmit the i-th repetition. The repetition pattern may be [0,1,0,1,...,0,1]. The repetition pattern may be [0,0,...,0,1,1,...,1,0,0,...,0,1,1,...,1]. Various repetition patterns may be considered. Based on the repetition pattern, a wireless device may receive control channel repetitions based on a TCI state of multiple TCI states. For example, when the repetition pattern indicates a first TRP, the wireless device may receive control channel repetitions based on the first TCI state. The wireless device may receive the control channel repetition based on the second TCI state when the repetition indicates a second TRP.

[0236] FIG. 20 illustrates an example of control channel repetition across multiple TRPs according to one aspect of an embodiment of the present disclosure. A base station may transmit one or more RRC messages including configuration parameters. The configuration parameters may indicate / include a first TRP (TRP#0) and a second TRP (TRP#1) associated with a cell. The configuration parameters may include / indicate control channel repetition across multiple TRPs (e.g., via the first TRP and the second TRP). The base station may transmit a first DCI / PDCCH (e.g., PDCCH#1) via the first TRP or the first core set pool. The first DCI / PDCCH may include / indicate resources for scheduling the TB over the multiple TRPs. The base station may transmit a second DCI / PDCCH (e.g., PDCCH#2) via the second TRP or the second core set pool. The second DCI / PDCCH may include / indicate resources for scheduling the TB over the multiple TRPs. The first DCI / PDCCH and the second DCI / PDCCH may indicate the same HARQ process index (e.g., HARQ-K) scheduling the TB. The base station may transmit the third DCI / PDCCH via the first TRP. The base station may transmit the fourth DCI / PDCCH (e.g., PDCCH #4) via the second TRP. The control information scheduling the TB may be repeated four times via multiple TRPs. The wireless device may monitor the first DCI / PDCCH and the third DCI / PDCCH based on a first TCI state associated with the first TRP or the first core set pool. The wireless device may monitor the second DCI / PDCCH and the fourth DCI / PDCCH associated with the second TRP or the second core set pool based on a second TCI state.

[0237] The base station may repeat the TB via four repetitions of the first TRP and four repetitions of the second TRP. The wireless device may simultaneously repeat the TB via the first TRP and the second TRP when the wireless device can support simultaneous reception via the first TRP and the second TRP. If the wireless device does not support simultaneous reception via the first TRP and the second TRP, the base station may transmit repeated transmissions of the TB via the first TRP and the second TRP based on time domain division multiplexing. For example, the base station may transmit the first repetition of the repeated transmission via the first TRP. The base station may transmit the second repetition of the repeated transmission via the second TRP. The switching pattern between the first TRP and the second TRP may be configured by the base station based on RRC / MAC-CE / DCI signaling. The first DCI and the second DCI may schedule repeated transmissions of the TB. The control channel repetition embodiment via multiple TRPs may enhance reliability and result in a better QoS experience.

[0238] In an example, a base station may transmit one or more RRC messages including configuration parameters. The configuration parameters may indicate enabled control channel repetitions for a cell. The base station may transmit multiple DCI / PDCCHs to schedule transport blocks over multiple core sets for the cell. For example, the configuration parameters may configure a first core set and a second core set for control channel repetitions. The configuration parameters may include / indicate a first search space associated with the first core set. The configuration parameters may include / indicate a second search space associated with the second core set. The configuration parameters may include / indicate a first TCI state associated with the first core set. The configuration parameters may include / indicate a second TCI state associated with the second core set. The first TCI state may be the same as or different from the second TCI state. The configuration parameters may include / indicate a set of first TCI states associated with the first core set. One or more MAC CEs may indicate a first TCI state of the set of first TCI states for the first core set. For example, the configuration parameters may include / indicate a second set of TCI states associated with the second core set. One or more second MAC CEs may indicate a second TCI state of the second set of TCI states for the second core set. The configuration parameters may indicate that the first core set and the second core set are associated for scheduling repeated DCI / PDCCH for the transport block.

[0239] In one embodiment, the configuration parameters may indicate / include search spaces associated with the first core set and the second core set. The configuration parameters may include multiple core set indices. The configuration parameters may include a core set index among the multiple core set indices, which indicates the first core set. The configuration parameters may include one or more indexes among the multiple core set indices of a repeated / additional core set (e.g., a core set used for control channel repetition in addition to the first core set and the second core set). For example, the index of the one or more indexes may indicate the second core set. When the first core set and the second core set are associated with control channel repetition, the first parameter of the first core set and the second parameter of the second core set may have restrictions on configuration. For example, the set of resource blocks (RBs) in the frequency domain of the first core set may be the same as the set (or a subset or superset) of resource blocks in the frequency domain of the second core set. The wireless device may determine the set of RBs belonging to the first core set and the second core set for the control channel repetition. For example, the first duration of the first core set may be the same as the second duration of the second core set. For example, the number of REGs of the first core set may be the same as the number of REGs. For example, the number of CCEs of the first core set may be the same as (or smaller than) the number of CCEs of the second core set. The wireless device may determine the number of REGs based on the determined set of RBs or based on the set of RBs of the first core set. For example, the first CCE-to-REG mapping type (e.g., between interleaved and non-interleaved) of the first core set may be the same as the second CCE-to-REG mapping type of the second core set. For example, the granularity of the precoder of the first core set may be configured to be the same as the granularity of the precoder of the second core set. For example, the first tci-PresenceInDCI of the first core set may be the same as the second tci-PresenceInDCI of the second core set.For example, the first rb-offset of a first core set can be the same as the second rb-offset of a second core set.

[0240] The first core set and the second core set may have different possible configurations for one or more parameters. For example, the one or more parameters may include one or more TCI states. For example, the one or more parameters may include a DM-RS scrambling identity (e.g., pdcch-DMRS-scrambleID). For example, the one or more parameters may include a core set pool index (e.g., coresetPoolIndex). For example, the one or more parameters may include a core set index.

[0241] When the wireless device may receive the first configuration parameter of the first core set and the second configuration parameter of the second core set, the wireless device may determine whether the first number of CCEs of the first core set is equal to or greater than the second number of CCEs of the second core set. Based on the determination, the wireless device may consider the first core set, and the second core set may be used for control channel repetition. Otherwise, the wireless device may determine the first core set, and the second core set may not be used for control channel repetition. Alternatively, the wireless device may determine the smallest number of CCEs (e.g., M) of one or more CCEs of one or more core sets (e.g., determine the core set of the one or more core sets having the smallest number of CCEs). For example, one or more core sets may be configured / indicated / used for control channel repetition. The wireless device may determine / assume / consider that the first M candidates of each core set of the one or more core sets are to be used for control channel repetition.

[0242] In one example, the wireless device may determine a number of REGs in a first core set of one or more core sets configured for control channel repetition. The wireless device may determine a second number of REGs in a second core set of the one or more core sets. The wireless device may determine whether the number of REGs is equal to the second number of REGs. In response to determining that the number of REGs is equal to the second number of REGs, the wireless device may consider the control channel repetition to be configured via the first core set and the second core set. Otherwise, the wireless device may consider the configuration as an error case and may not activate control channel repetition via the first core set and the second core set. In one example, the wireless device may determine a minimum number of REGs for one or more core sets (e.g., determine a core set with a minimum number of REGs). The wireless device may assume a minimum number of REGs to be used for control channel repetition.

[0243] The search space configuration parameters associated with the first core set and the second core set may include / indicate a switching pattern or mapping pattern of the first core set and the second core set. For example, the wireless device may determine a search space monitoring opportunity based on the search space configuration parameters. The wireless device may determine the search space monitoring opportunity based on the first core set. The wireless device may determine a second search space monitoring opportunity or an extended monitoring opportunity based on a rule. For example, the wireless device may determine a second search space monitoring opportunity as the slot following the first monitoring opportunity. The wireless device may determine the second search space monitoring opportunity based on the second search space. The configuration parameters may indicate a bitmap of multiple OFDM symbols within a slot (or multiple slots, etc.). The bitmap may indicate a 0 for the first core set or a 1 for the second core set for each corresponding OFDM symbol or slot. If a 0 is indicated for an OFDM symbol, the wireless device may monitor the search space monitoring opportunity based on the first core set. If a 1 is indicated for the second OFDM symbol, the wireless device may monitor a second search space monitoring opportunity based on the second core set.

[0244] In one example, a wireless device may receive one or more RRC messages including configuration parameters. The configuration parameters may indicate / include a core set of bandwidth portions of a cell. The configuration parameters may include search space parameters associated with the core set. The search space parameters may indicate a first monitoring periodicity in units of a first time period. For example, the first time period may be a slot or a number of slots. The search space parameters may indicate a second monitoring periodicity in units of a second time period. For example, the second time period may be an OFDM symbol or a number of OFDM symbols or slots. For example, the second time period may be smaller than the first time period. The wireless device may monitor one or more repeated DCI / PDCCHs via one or more monitoring occasions (e.g., multiple downlink control signal / channel transmission opportunities) determined based on the second monitoring periodicity within the first monitoring periodicity. For example, the configuration parameters may indicate one or more monitoring occasions within the first monitoring periodicity.

[0245] For example, a wireless device may receive / monitor a first DCI / PDCCH of one or more repeating DCI / PDCCHs via a first monitoring opportunity of one or more monitoring opportunities. The wireless device may receive / monitor a second DCI / PDCCH of one or more repeating DCI / PDCCHs via a second monitoring opportunity of one or more monitoring opportunities. The first DCI / PDCCH may be identical to the second DCI / PDCCH. The first DCI / PDCCH and the second DCI / PDCCH may indicate the same resource for the transport block. The wireless device may receive / monitor a DCI via one or more monitoring opportunities, and search space candidates for the DCI may include one or more candidates for the one or more monitoring opportunities. For example, the search space candidates may include a first candidate for the first monitoring opportunity and a second candidate for the second monitoring opportunity. For example, a first starting CCE index of the first candidate for the first monitoring opportunity may be the same as a second starting CCE index of the second candidate for the second monitoring opportunity.

[0246] A wireless device may receive / monitor the DCI / PDCCH via one or more monitoring occasions, and the DCI / PDCCH search space candidates may include one or more CCEs from the one or more monitoring occasions.

[0247] For example, a core set may be associated with multiple TCI states as active TCI states. For example, the multiple TCI states may be activated via one or more RRC messages or MAC CEs or DCIs. The wireless device may monitor a first monitoring opportunity based on a first TCI of the multiple TCI states. The wireless device may monitor a second monitoring opportunity based on a second TCI of the multiple TCI states.

[0248] FIG. 21 illustrates an example of control channel repetitions according to one aspect of an embodiment of the present disclosure. For example, a base station may transmit one or more RRC messages including configuration parameters. The configuration parameters may include / indicate a core set associated with an active TCI state. The base station may activate the active TCI state via one or more RRC messages, one or more MAC CEs, or one or more DCIs. The configuration parameters may include / indicate a bitmap indicating one or more monitoring opportunities for the control channel repetitions. FIG. 21 illustrates a bitmap size of 14 (e.g., the bitmap corresponds to a slot where each bit is mapped to each OFDM symbol). The bitmap indicates monitoring opportunities for the first and sixth OFDM symbols of a slot. The configuration parameters may indicate / include a first monitoring periodicity as two slots (e.g., monitor every two slots). In each monitoring periodicity, the wireless device may determine one or more monitoring opportunities based on the bitmap. For example, if a bitmap is not present, the wireless device may determine a monitoring opportunity starting with the first OFDM symbol of the slot. 21, the wireless device may determine a first monitoring opportunity and a second monitoring opportunity based on the bitmap for each monitoring period. The wireless device may monitor the first monitoring opportunity and the second monitoring opportunity to receive one or more DCI / PDCCHs that schedule transport blocks.

[0249] In one embodiment, the configuration parameter indicates one or more monitoring occasions within a monitoring period for the search space. For example, monitoringSlotPeriodicityAndOffset may determine the monitoring periodicity. If the parameter may include monitoringSymbolWithinSlot, the wireless device may determine the monitoring period based on the gap between each monitoring opportunity within a slot based on monitoringSymbolWithinSlot. The wireless device may expect equal intervals between monitoring opportunities within a slot. Alternatively, when the search space is used for control channel repetition, the parameter may not include monitoringSymbolsWithinSlot. In one embodiment, monitoringSymbolsWithinSlot may be used to indicate one or more monitoring occasions within a monitoring periodicity determined based on monitoringSlotPeriodicityAndOffset when control channel repetition is enabled. For example, a parameter indicating enablement of control channel repetition may be configured for the search space, for a core set associated with the search space, or for a DCI format monitored via the search space. For example, the duration of the search space may be used to determine one or more monitoring occasions within a monitoring period. For example, if the monitoring periodicity is greater than a slot, the wireless device may determine one or more monitoring occasions based on the monitoring periodicity and the period. For example, if the monitoring periodicity is P slots and the duration is D, the wireless device may determine a first monitoring occasion of the one or more monitoring occasions based on the monitoringSlotPeriodicityAndOffset. The wireless device may determine a second monitoring occasion of the one or more monitoring occasions as the slot following the first monitoring occasion. The wireless device may determine D number of monitoring occasions starting from the first monitoring occasion in consecutive slots. For example, if the search space is configured / associated with multiple core sets, the search space may include multiple control resource set IDs (e.g., controlResourceSetID and secondcontrolResourceSetID).

[0250] In one example, a base station may transmit a first DCI / PDCCH via a first monitoring opportunity of one or more monitoring opportunities. The base station may transmit a second DCI / PDCCH via a second monitoring opportunity of one or more monitoring opportunities. The first DCI / PDCCH and the second DCI / PDCCH may indicate the same resource for the transport block. The first content of the first DCI / PDCCH may be the same as or different from the second content of the second DCI / PDCCH. The wireless device may attempt to decode the first DCI / PDCCH independently from the second DCI / PDCCH. The wireless device may not assume that the base station may transmit the first DCI / PDCCH and the second DCI / PDCCH. The base station may transmit one or more DCI / PDCCHs over one or more monitoring opportunities. The base station may transmit a single DCI / PDCCH over one or more monitoring opportunities. The base station may transmit a DCI / PDCCH at each monitoring opportunity. The base station may transmit any number of repeated DCI / PDCCHs over one or more monitoring occasions.

[0251] The base station may indicate that a first control channel repetition mode is to be used for one or more monitoring occasions. Based on the first control channel repetition mode, the wireless device may determine the number of one or more monitoring occasions O in the monitoring periodicity. Based on the time-first method, the monitoring occasions of the one or more monitoring occasions are indexed from 0, ..., O-1. The wireless device may attempt to decode one or more search space candidates aggregating candidates from monitoring occasions 0 to i (e.g., i = 0, ..., O-1 or i = 0, 1, 3, 7, ...). For example, if O is 4, the wireless device may attempt to decode a first candidate aggregating candidates from a first monitoring occasion of the one or more monitoring occasions. The wireless device may attempt to decode a second candidate aggregating a candidate and another candidate from a second monitoring occasion of the one or more monitoring occasions. The wireless device may attempt to decode a fourth candidate aggregating each candidate of each monitoring occasion of the one or more monitoring occasions. The wireless device may aggregate candidates from one or more monitoring occasions in which the starting CCE index of some of the candidates is the same, or the wireless device may determine candidates based on a rule. For example, the wireless device may determine candidates for the same frequency resource at each monitoring occasion. For example, the wireless device may determine candidates for the same REG (or the same REG index) at each monitoring occasion.

[0252] In one embodiment, the wireless device may determine a respective list of candidates over each monitoring occasion of one or more monitoring occasions within the monitoring periodicity of the search space. The wireless device may determine the list of candidates over one or more monitoring occasions based on the respective list of candidates. The list of candidates may include one or more candidates for an aggregation level. For example, the wireless device may determine a first list of candidates for a first aggregation level 2*L based on two candidates over two monitoring occasions for aggregation level L or four candidates over four monitoring occasions for aggregation level L / 2.

[0253] In an example of determining one or more search space candidates for an aggregation level across one or more monitoring occasions, the base station may indicate four monitoring occasions, with monitoring periods indexed from the first to the fourth monitoring occasions. In this example, the candidate set for an aggregation level is assumed to be consistent across the four monitoring occasions. For example, a first candidate for aggregation level 2 may start at the third CCE, and a second candidate for aggregation level 2 may start at the fifth CCE. For example, a first candidate for aggregation level 4 may start at N_CCE (e.g., multiple CCEs) through the eighth CCE, and a second candidate for aggregation level 4 may start at N_CCE through the fourth CCE. The wireless device may determine a list of candidates having an aggregation level of 8 by combining / aggregating four candidates with aggregation level 2 (one candidate from each monitoring occasion) and / or by combining / aggregating two candidates with aggregation level 4 (one candidate from each monitoring occasion). In this example, the first box on the left and the second small box on the right indicate AL=8 candidates. The wireless device may determine more candidates by aggregating / combining a second candidate with AL=2 and / or may determine a second candidate with AL=4. Similarly, the wireless device may determine a candidate with aggregation level (AL)=16 by combining / aggregating four candidates with AL=4. The wireless device may determine two AL=16 candidates.

[0254] The wireless device may not aggregate candidates where the candidates may not include candidates from the first monitoring occasion (or the first monitoring occasion, the earliest monitoring occasion in the monitoring period). The wireless device may determine possible aggregation levels and / or candidates by aggregating candidates from the first monitoring occasion, the first + second monitoring occasion, the first + second + third + fourth monitoring occasion, the first + second + third + fourth + fifth + sixth + seventh + eighth, ..., etc.

[0255] In one embodiment, the wireless device may determine a list of aggregation level candidates based on a hash function applied to each slot. The same candidate may be mapped if the first monitoring opportunity and the second monitoring opportunity occur in the same slot. Otherwise, a different candidate may be determined. The base station may transmit DCI over the candidates over one or more monitoring opportunities.

[0256] In one embodiment, the base station may transmit one or more messages including configuration parameters. The configuration parameters may include / indicate a search space group for the control channel repetition. The search space group may include one or more search spaces. For example, the search group may include a first search space for a first carrier and a second search space for a second carrier. For example, the search space group may include a first search space for a first BWP of a cell and a second search space for a second BWP of the cell. For example, the search space group may include the first search space for the first BWP of the first cell and the second search space for the second BWP of the second cell. For example, for a BWP of a cell, the configuration parameters may indicate one or more search space groups. The search space groups of the one or more search space groups may be associated / configured with one or more DCI formats. In one embodiment, the wireless device may determine the search space group based on one or more search spaces configured / associated with the BWP of the cell, and each search space of the one or more search spaces may be configured to monitor a DCI format of one or more DCI formats. For example, the one or more DCI formats may include DCI format 1_1 and DCI format 0_1. For example, the one or more DCI formats may include DCI format 0_0 and DCI format 1_0. For example, the one or more DCI formats may include DCI format 1_2 and DCI format 0_2. For example, the one or more DCI formats may include DCI format 3_0 and DCI format 3_1. For example, the one or more DCI formats may include downlink / uplink DCI of non-fallback DCI. For example, the one or more DCI formats may include downlink / uplink DCI of fallback DCI. For example, the one or more DCI formats may include a DCI format of sidelink DCI.

[0257] The wireless device may determine search space candidates across one or more search spaces of a search space group based on multiple core sets in a manner similar to that addressed for control iterations. In one embodiment, the wireless device may determine one or more monitoring opportunities within a slot based on one or more search spaces. For example, in slot n, the wireless device may determine one or more first monitoring opportunities based on a first search space of one or more search spaces. The wireless device may determine one or more second monitoring opportunities based on a second search space of one or more search spaces in slot n. The wireless device may monitor one or more first monitoring opportunities and one or more second monitoring opportunities for slot n. The wireless device may not expect overlap in the time domain between a monitoring opportunity of a search space of one or more search spaces and a second monitoring opportunity of a second search space of one or more search spaces. The wireless device may monitor one or more repeated DCIs based on a DCI format via one or more monitoring opportunities within a slot.

[0258] In one embodiment, one or more repeated DCIs may be transmitted by a base station via one or more PDCCHs, where each PDCCH may transmit / transmit a respective DCI. Each DCI of the one or more repeated DCIs may have the same content or different content. A wireless device may aggregate one or more repeated DCIs when each DCI may have the same content. In one embodiment, one or more repeated DCIs may be transmitted via a PDCCH, where the PDCCH may be transmitted across one or more search space candidates of one or more search spaces. In one embodiment, a DCI may be repeatedly transmitted via one or more PDCCHs, where each PDCCH may repeatedly transmit / transmit a DCI.

[0259] In one example, a base station may associate multiple TCI states with a core set as active TCI states. FIG. 22 illustrates an example of a core set associated with multiple TCI states as active TCI states, according to one aspect of an embodiment of the present disclosure. In an example, a base station may indicate multiple monitoring opportunities within a slot or within a monitoring period for control channel repetition. A wireless device may monitor a first monitoring opportunity based on a first TCI state of the multiple TCI states. A wireless device may monitor a second monitoring opportunity based on a second TCI state of the multiple TCI states. A base station may indicate a pattern for switching between the multiple TCI states. For example, configuration parameters of a search space associated with a core set may include / indicate enabling control channel repetition. The configuration parameters may include / indicate enabling TCI switching or enabling control channel repetition over multiple TCI states. The configuration parameters may include / indicate a switching pattern. For example, the switching pattern may alternate between a first TCI state of the plurality of TCI states and a second TCI state of the plurality of TCI states at each monitoring opportunity of one or more monitoring opportunities within a monitoring periodicity or slot or within several slots (e.g., during a monitoring periodicity configured by the monitoringSlotPeriodicityAndOffset of the search space). For example, the switching pattern may be half and half between the first TCI state and the second TCI state. For example, the number of the one or more monitoring opportunities is K. The wireless device may monitor the first floor (K / 2) monitoring opportunities based on the first TCI state. The wireless device may monitor the remaining monitoring opportunities based on the second TCI state within the monitoring period. For example, the switching pattern may be a bitmap indicating the TCI state at each monitoring opportunity of the one or more monitoring opportunities.

[0260] FIG. 23 shows an example of a MAC CE format (e.g., a UE-specific PDCCH MAC CE TCI state indication, an UE-specific PDCCH MAC CE extended TCI state indication) that indicates / activates / updates / selects one or more TCI states (e.g., TCI state 1 and TCI state 2) for a core set of serving cells. The base station may indicate one or more TCI state indexes (e.g., TCI state ID1 and TCI state ID2) in the MAC CE format to activate one or more TCI states for a core set (indicated by a core set ID). The one or more TCI state indexes may indicate / identify one or more TCI states. Each TCI state index of the one or more TCI state indexes may indicate / identify a respective TCI state of the one or more TCI states. The MAC CE format may include one or more fields. A first field of the one or more fields may indicate / include a serving cell index (e.g., a serving cell ID provided by the higher layer parameter ServCellIndex or indicated by one or more configuration parameters) that indicates / identifies the serving cell. A second field of the one or more fields may indicate / include a core set index (e.g., Core Set ID) that identifies a core set of the serving cell. A third field of the one or more fields may indicate / include a first TCI state index (e.g., TCI State ID1) that identifies a first TCI state. The one or more TCI states may include the first TCI state. A fourth field (e.g., R) of the one or more fields may be a reserved field. A fifth field of the one or more fields may indicate / include a second TCI state index (e.g., TCI State ID2) that identifies a second TCI state. In one embodiment, one or more fields of the MAC CE format may include a second TCI state index based on the value of the fourth field (e.g., R).For example, if the value of the fourth field is equal to zero, the MAC CE format may not include a second TCI state index (e.g., the fifth field may be a reserved field). If the value of the fourth field is equal to one, the MAC CE format may include a second TCI state index. The one or more TCI states may include the second TCI state. The MAC CE format may be an activation command. The configuration parameter may indicate a first TCI state index for the first TCI state. The configuration parameter may indicate a second TCI state index for the second TCI state. The configuration parameter may indicate a core set index for the core set. The configuration parameter may indicate a serving cell index for the serving cell. The configuration parameter may indicate one or more TCI state indices for the one or more TCI states. The one or more TCI states may include a first TCI state and a second TCI state. The one or more TCI state indices may include a first TCI state index and a second TCI state index.

[0261] FIG. 24 is an example of uplink resource determination with control channel repetition according to one aspect of an embodiment of the present disclosure.

[0262] FIG. 26 is an example of downlink resource determination with control channel repetition according to one aspect of an embodiment of the present disclosure.

[0263] In one embodiment, the wireless device may receive one or more messages. In one embodiment, the wireless device may receive one or more messages from a base station. The one or more messages may include one or more configuration parameters. In one embodiment, the one or more configuration parameters may be RRC configuration parameters. In one embodiment, the one or more configuration parameters may be RRC reconfiguration parameters.

[0264] In one embodiment, the 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 configured with a PUCCH (e.g., a PUCCH SCell). In one embodiment, the cell may be an unlicensed cell, e.g., operating in an unlicensed band. In one embodiment, the cell may be a licensed cell, e.g., operating in a licensed band. In one embodiment, the cell may operate in a first frequency range (FR1). FR1 may include, e.g., a frequency band below 6 GHz. In one embodiment, the cell may operate in a second frequency range (FR2). FR2 may include, e.g., a frequency band between 24 GHz and 52.6 GHz.

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

[0266] In one embodiment, the wireless device may be in an RRC connected mode.

[0267] In one embodiment, the wireless device may be in an RRC idle mode.

[0268] In one embodiment, the wireless device may be in an RRC inactive mode.

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

[0270] In one embodiment, a BWP of a plurality of BWPs may be in one of an active state and an inactive state. In one embodiment, in the downlink BWP active state of one or more downlink BWPs, the wireless device may monitor downlink channels / signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / for / via the downlink BWPs. In one embodiment, in the downlink BWP active state of one or more downlink BWPs, the wireless device may receive PDSCH on / for / via / for the downlink BWPs. In one embodiment, in the downlink BWP inactive state of one or more downlink BWPs, the wireless device may not monitor downlink channels / signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / for / via the downlink BWPs. In the downlink BWP inactive state of one or more downlink BWPs, the wireless device may stop monitoring (or receiving) downlink channels / signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / for / via the downlink BWPs. In one embodiment, in a downlink BWP inactive state of one or more downlink BWPs, the wireless device may not receive a PDSCH on / through / for the downlink BWPs. In a downlink BWP inactive state of one or more downlink BWPs, the wireless device may stop receiving a PDSCH on / through / for the downlink BWPs.

[0271] In one embodiment, in an uplink BWP active state of one or more uplink BWPs, the wireless device can transmit uplink signals / channels (e.g., PUCCH, preamble, PUSCH, PRACH, SRS, etc.) on / via the uplink BWPs. In one embodiment, in an uplink BWP inactive state of one or more uplink BWPs, the wireless device may not transmit uplink signals / channels (e.g., PUCCH, preamble, PUSCH, PRACH, SRS, etc.) on / via the uplink BWPs.

[0272] In one embodiment, a wireless device may activate a downlink BWP of one or more downlink BWPs of a cell. In one embodiment, activating a downlink BWP may include the wireless device setting (or switching to) a 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.

[0273] In one embodiment, a wireless device may activate an uplink BWP of one or more uplink BWPs of a cell. In one embodiment, activating an uplink BWP may include the wireless device setting (or switching to) an 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.

[0274] In one embodiment, the one or more configuration parameters may be for an (active) downlink BWP of the cell. In one embodiment, at least one configuration parameter of the one or more configuration parameters may be for a downlink BWP of the cell.

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

[0276] In one embodiment, the one or more configuration parameters may indicate multiple core sets. The one or more configuration parameters may indicate multiple core sets for a cell's (active) downlink BWP. In one embodiment, a cell's (active) downlink BWP may include multiple core sets. The multiple core sets may include a first core set (e.g., core set 1 in Figures 24 and 26). The multiple core sets may include a second core set (e.g., core set 2 in Figures 24 and 26).

[0277] In one example, the one or more configuration parameters may indicate multiple core set indexes (e.g., provided by the upper layer parameter ControlResourceSetId) of the multiple core sets. In one example, each core set of the multiple core sets may be identified / indicated by a respective core set index of the multiple core set indexes. In one example, a first core set of the multiple core sets (e.g., core set 1 in Figures 24 and 26) may be identified by a first core set index of the multiple core set indexes. A second core set of the multiple core sets (e.g., core set 2 in Figures 24 and 26) may be identified by a second core set index of the multiple core set indexes.

[0278] In one embodiment, the core set index may be a core set identifier / indicator.

[0279] In one embodiment, the first core set and the second core set may be different, and the first core set index and the second core set index may be different.

[0280] In one embodiment, the one or more configuration parameters may indicate multiple search space sets for, for example, a cell's downlink BWP (e.g., by the higher layer parameter SearchSpace). In one embodiment, the one or more configuration parameters may indicate multiple search space sets for, for example, a cell (e.g., by the higher layer parameter SearchSpace).

[0281] In one embodiment, one or more configuration parameters may indicate search space set indexes / identifiers (e.g., provided by the higher layer parameter searchSpaceId) for the multiple search space sets. In one embodiment, each search space set of the multiple search space sets may be identified by a respective search space set index in the search space set index. In one embodiment, a first search space set of the multiple search space sets may be identified by a first search space set index in the search space set index. In one embodiment, a second search space set of the multiple search space sets may be identified by a second search space set index in the search space set index.

[0282] In an embodiment, the one or more configuration parameters may indicate a PDCCH monitoring periodicity (e.g., monitoringSlotPeriodicityAndOffset) for the multiple search space sets. The one or more configuration parameters may indicate a respective PDCCH monitoring periodicity (e.g., monitoringSlotPeriodicityAndOffset) of the PDCCH monitoring periodicity for each search space set of the multiple search space sets. The one or more configuration parameters may indicate a first PDCCH monitoring periodicity (e.g., 2 slots) of the PDCCH monitoring periodicity for a first search space set of the multiple search space sets. The one or more configuration parameters may indicate a second PDCCH monitoring periodicity (e.g., 10 slots) of the PDCCH monitoring periodicity for a second search space set of the multiple search space sets.

[0283] In one embodiment, a search space set of multiple search space sets may be associated (or linked) with a core set of multiple core sets. In one embodiment, one or more configuration parameters may indicate a core set (or a core set index of a core set) of a search space set (e.g., provided by the upper layer parameter controlResourceSetId of the upper layer parameter SearchSpace). In one embodiment, the association (or linking) may be one-to-one. A one-to-one association may include a search space set associated (or linked) with a core set not associated (or linked) with a second core set that is different from the core set. The multiple core sets may include the second core set.

[0284] In one example, based on a search space set being associated with (or linked to) a core set, the wireless device may monitor PDCCH candidates in PDCCH monitoring opportunities for / of the search space set associated with (or linked to) the core set for downlink control signals / channels (e.g., DCI, PDCCH, RS, GC-PDCCH, DMS, etc.). In one example, based on a search space set being associated with (or linked to) a core set, the wireless device may monitor PDCCH candidates in PDCCH monitoring opportunities for / for the search space set within the core set associated with (or linked to) the search space set for DCI. In one example, based on a search space set being associated with (or linked to) a core set, the wireless device may monitor PDCCHs of the search space set within the core set associated with (or linked to) the search space set for DCI.

[0285] The wireless device may monitor downlink control channels in a core set of multiple core sets for a DCI. Monitoring downlink control channels in a core set for a DCI may include monitoring one or more PDCCH candidates in one or more PDCCH monitoring opportunities for / of one or more search space sets associated with the core set for the DCI. The multiple search space sets may include one or more search space sets. One or more configuration parameters may indicate one or more search space sets of the core set. The wireless device may determine one or more PDCCH monitoring opportunities for the one or more search space sets based on one or more PDCCH monitoring periodicities (e.g., monitoringSlotPeriodicityAndOffset) of the one or more search space sets. The PDCCH monitoring periodicity may include one or more PDCCH monitoring periods.

[0286] In one embodiment, the one or more configuration parameters may indicate multiple core set indexes for multiple search space sets (e.g., provided by the higher-layer parameter controlResourceSetId in the higher-layer parameter SearchSpace). In one embodiment, each search space set of the multiple search space sets may be associated (or linked) to a respective core set of the multiple core sets, identified by a respective core set index of the multiple core set indexes. In one embodiment, the one or more configuration parameters may indicate a first core set index of a first core set of a first search space set. The one or more configuration parameters may indicate a first core set index of a first core set in a first core set index field of the first search space set (e.g., provided by the higher-layer parameter controlResourceSetId of the higher-layer parameter SearchSpace). The first search space set may be associated (or linked) to the first core set based on the one or more configuration parameters indicating the first core set index of the first core set for the first search space set. In one embodiment, the one or more configuration parameters may indicate a first core set index of a first core set for a second search space set. The one or more configuration parameters may indicate a first core set index of the first core set in a second core set index field of the second search space set (e.g., provided by the higher layer parameter controlResourceSetId of the higher layer parameter SearchSpace). The second search space set may be associated (or linked) to the first core set based on the one or more configuration parameters indicating the first core set index of the first core set for the second search space set. In one embodiment, the one or more configuration parameters may indicate a second core set index of the second core set for the first search space set.A first search space set may be associated (or linked) to a second core set based on one or more configuration parameters indicating a second core set index of the second core set for the first search space set. In one embodiment, the one or more configuration parameters may indicate a second core set index of the second core set for the second search space set. A second search space set may be associated (or linked) to a second core set based on one or more configuration parameters indicating a second core set index of the second core set for the second search space set.

[0287] In one embodiment, one or more first search space sets of the plurality of search space sets may be associated (or linked) with a first core set. One or more configuration parameters may indicate a first core set (or a first core set index for the first core set) for the one or more first search space sets. One or more configuration parameters may indicate a first core set (or a first core set index for the first core set) for each search space set of the one or more first search space sets. One or more configuration parameters may indicate one or more first search space sets for the first core set. One or more second search space sets of the plurality of search space sets may be associated (or linked) with a second core set. One or more configuration parameters may indicate a second core set (or a second core set index for the second core set) for each search space set of the one or more second search space sets. One or more configuration parameters may indicate one or more second search space sets for the second core set.

[0288] The wireless device may monitor for DCI one or more PDCCH candidates in one or more first PDCCH monitoring opportunities for / from one or more first search space sets associated with the first core set.

[0289] The wireless device may monitor one or more PDCCH candidates for DCI at one or more second PDCCH monitoring opportunities for / with one or more second search space sets associated with the second core set.

[0290] The one or more configuration parameters may indicate control channel repetition (e.g., repetition / aggregation of PDCCH). The one or more configuration parameters may include a control channel repetition enable parameter that enables (or activates or indicates) control channel repetition. The control channel repetition may include repetition of downlink control signals / channels (e.g., PDCCH, DCI).

[0291] In one embodiment, the one or more configuration parameters may indicate a repetition number for the control channel repetition.

[0292] In one example, the one or more configuration parameters may indicate a number of control channel repetitions for a plurality of core sets. The one or more configuration parameters may indicate a number of control channel repetitions for each core set of the plurality of core sets. In one example, the one or more configuration parameters may indicate a number of control channel repetitions for a plurality of search space sets of the plurality of core sets. The one or more configuration parameters may indicate a number of control channel repetitions for each search space set of each core set of the plurality of core sets. In an example, the one or more configuration parameters may indicate a number of control channel repetitions for at least one search space set of the plurality of search space sets.

[0293] In one embodiment, the one or more configuration parameters may indicate multiple core sets for control channel repetition. The one or more configuration parameters may link / map / associate multiple core sets for control channel repetition.

[0294] In one embodiment, the wireless device may receive a DCI indicating a repetition number for a control channel repetition. The DCI may include a field indicating the repetition number (e.g., a DCI subframe / slot repetition number field).

[0295] In one embodiment, the repetition number may be, for example, the repetition number of a downlink control signal / channel (e.g., PDCCH, DCI). The base station may transmit multiple DCI / PDCCHs (e.g., DCI1 and DCI2 in Figures 24 and 26) for the repetition of the downlink control signal / channel. The wireless device may monitor PDCCH candidates for the multiple DCI / PDCCHs (or for the repetition of the downlink control signal / channel). The number of the multiple DCI / PDCCHs may be equal to the repetition number (e.g., the number of repetitions is equal to 2 in Figures 24 and 26). The multiple DCI / PDCCHs may include a first downlink control signal / channel (e.g., DCI1 in Figures 24 and 26) and a second downlink control signal / channel (e.g., DCI2 in Figures 24 and 26).

[0296] In one example, a wireless device may be served (e.g., received or transmitted) by multiple TRPs (e.g., TRP1 and TRP2 in Figures 24 and 26). Each downlink control signal / channel of the multiple DCI / PDCCHs may be transmitted by a respective TRP of the multiple TRPs. For example, in Figures 24 and 26, a first TRP (e.g., TRP1) of the multiple TRPs may transmit DCI1, and a second TRP (e.g., TRP2) of the multiple TRPs may transmit DCI2.

[0297] In an embodiment, each downlink control signal / channel of the multiple DCI / PDCCHs may be the same (or may have the same content, e.g., the same DCI field, the same DCI size, the same payload, the same values ​​for the DCI field). Each downlink control signal / channel of the multiple DCI / PDCCHs may be the same as a downlink control signal / channel. Each downlink control signal / channel of the multiple DCI / PDCCHs may be a repetition of a downlink control signal / channel. A base station may repeat a downlink control signal / channel by transmitting multiple DCI / PDCCHs. For example, in Figures 24 and 26, DCI1 and DCI2 may be the same (or equal). The content of DCI1 and DCI2 may be the same. The payloads of DCI1 and DCI2 may be the same. The DCI fields (or values ​​of the DCI fields) of DCI1 and DCI2 may be the same.

[0298] In an embodiment, the first downlink control signal / channel and the second downlink control signal / channel may be the same (e.g., same content, same DCI fields, same DCI size, same payload, same values ​​for DCI fields, etc.). In one embodiment, the first downlink control signal / channel and the second downlink control signal / channel may be the same as the downlink control signal / channel. The first downlink control signal / channel may be a downlink control signal / channel. The second downlink control signal / channel may be a downlink control signal / channel. The first downlink control signal / channel and the second downlink control signal / channel may be a repeat of the downlink control signal / channel.

[0299] A base station may transmit multiple DCI / PDCCHs via / in multiple core sets (e.g., Core Set 1 and Core Set 2 in Figures 24 and 26) for repetition of downlink control signals / channels. The base station may transmit each downlink control signal / channel of the multiple DCI / PDCCHs via a respective core set of the multiple core sets. Transmitting multiple DCI / PDCCHs via / in multiple core sets for repetition of downlink control signals / channels may include transmitting downlink control signals / channels via / in multiple core sets. Transmitting multiple DCI / PDCCHs via / in multiple core sets for repetition of downlink control signals / channels may include repeating transmission of downlink control signals / channels via / in multiple core sets. The base station may transmit multiple DCI / PDCCHs via / in multiple search space sets associated with the multiple core sets for repetition of downlink control signals / channels. The base station may transmit each downlink control signal / channel of the multiple DCI / PDCCHs via / in a respective search space set of the multiple search space sets for repetition of downlink control signals / channels. For example, in Figures 24 and 26, a base station transmits a first downlink control signal / channel via a first core set. The base station may transmit the first downlink control signal / channel via one or more first search space sets associated with the first core set. The base station may transmit the first downlink control signal / channel via at least one first search space set of the one or more first search space sets. The base station transmits a second downlink control signal / channel via a second core set. The base station may transmit the second downlink control signal / channel via one or more second search space sets associated with the second core set. The base station may transmit the second downlink control signal / channel via at least one second search space set of the one or more second search space sets.

[0300] The wireless device may monitor multiple core sets for downlink control signal / channel repetitions for multiple DCI / PDCCHs. The wireless device may monitor a respective core set of the multiple core sets for each downlink control signal / channel of the multiple DCI / PDCCHs. Monitoring multiple core sets for downlink control signal / channel repetitions for multiple DCI / PDCCHs may include monitoring multiple core sets for downlink control signal / channels. Monitoring multiple core sets for downlink control signal / channel repetitions for multiple DCI / PDCCHs may include monitoring multiple core sets for downlink control signal / channel repetitions. The wireless device may monitor multiple search space sets associated with the multiple core sets for downlink control signal / channel repetitions for multiple DCI / PDCCHs. The wireless device may monitor each search space set of the multiple search space sets for downlink control signal / channel repetitions for each downlink control signal / channel of the multiple DCI / PDCCHs. For example, in Figures 24 and 26, the wireless device may monitor a first core set for a first downlink control signal / channel. The wireless device may monitor one or more first search space sets associated with a first core set for a first downlink control signal / channel. The wireless device may monitor at least one first search space set of the one or more first search space sets for a first downlink control signal / channel. The wireless device may monitor a second core set for a second downlink control signal / channel. The wireless device may monitor one or more second search space sets associated with a second core set for a second downlink control signal / channel. The wireless device may monitor at least one second search space set of the one or more second search space sets for a second downlink control signal / channel.

[0301] In one example, a wireless device may determine multiple downlink control signal / channel transmission / repetition opportunities (e.g., PDCCH transmission / repetition / monitoring opportunities) for control channel repetition. The wireless device may determine multiple downlink control signal / channel transmission / repetition opportunities for downlink control signal / channel repetition. A base station may transmit multiple DCI / PDCCHs across / across / on / in multiple downlink control signal / channel transmission / repetition opportunities (e.g., PDCCH transmission / repetition opportunity 1 and PDCCH transmission / repetition opportunity 2 in Figures 24 and 26) via multiple core sets. A base station may transmit downlink control signals / channels across / across / on / in multiple downlink control signal / channel transmission / repetition opportunities via multiple core sets. A base station may transmit downlink control signals / channels across / across / on / in each downlink control signal / channel transmission / repetition opportunity of the multiple downlink control signal / channel transmission / repetition opportunities via each core set of the multiple core sets. A base station may repeat a downlink control signal / channel transmission across / across / on / in multiple downlink control signal / channel transmission / repetition opportunities. For example, in FIG. 24 and FIG. 26, the multiple downlink control signal / channel transmission / repetition opportunities include a first downlink control signal / channel transmission / repetition opportunity (e.g., PDCCH transmission / repetition opportunity 1) and a second downlink control signal / channel transmission / repetition opportunity (e.g., PDCCH transmission / repetition opportunity 2). A base station may transmit a first downlink control signal / channel in the first downlink control signal / channel transmission / repetition opportunity via a first core set. A base station may transmit a second downlink control signal / channel in the second downlink control signal / channel transmission / repetition opportunity via a second core set.

[0302] A wireless device may monitor multiple core sets over / across / on / at multiple downlink control signal / channel transmission / repetition opportunities for multiple DCI / PDCCHs. A wireless device may monitor multiple core sets over / across / on / at multiple downlink control signal / channel transmission / repetition opportunities for a downlink control signal / channel. A wireless device may monitor each core set of multiple core sets over / across / on / at each downlink control signal / channel transmission / repetition opportunity of multiple downlink control signal / channel transmission / repetition opportunities for a downlink control signal / channel. A wireless device may monitor multiple core sets over / across / on / at multiple downlink control signal / channel transmission / repetition opportunities for a repetition of a downlink control signal / channel. For example, in Figures 24 and 26, a wireless device monitors a first core set in a first downlink control signal / channel transmission / repetition opportunity for a first downlink control signal / channel. A wireless device monitors a second core set in a second downlink control signal / channel transmission / repetition opportunity for a second downlink control signal / channel.

[0303] The wireless device may monitor the multiple core sets over / across / over / over multiple downlink control signal / channel transmission / repetition opportunities. The wireless device may monitor each core set of the multiple core sets over / across / over / over a respective downlink control signal / channel transmission / repetition opportunity of the multiple downlink control signal / channel transmission / repetition opportunities. For example, the wireless device may monitor a first core set for downlink control signals / channels over / across / over / over one or more first downlink control signal / channel transmission / repetition opportunities of the multiple downlink control signal / channel transmission / repetition opportunities. The wireless device may monitor a second core set for downlink control signals / channels over / across / over / over one or more second downlink control signal / channel transmission / repetition opportunities of the multiple downlink control signal / channel transmission / repetition opportunities. The one or more first downlink control signal / channel transmission / repetition opportunities may include a first downlink control signal / channel transmission / repetition opportunity. The one or more second downlink control signal / channel transmission / repetition opportunities may include a second downlink control signal / channel transmission / repetition opportunity.

[0304] A base station may transmit downlink control signals / channels over / across / on / in each of a plurality of downlink control signal / channel transmission / repetition opportunities via each core set of a plurality of core sets. For example, a base station may transmit a downlink control signal / channel over / across / on / in one or more first downlink control signal / channel transmission / repetition opportunities via a first core set. A base station may transmit a downlink control signal / channel over / across / on / in one or more second downlink control signal / channel transmission / repetition opportunities via a second core set.

[0305] In one embodiment, the repetition of a downlink control signal / channel (or transmission of multiple DCI / PDCCHs) may be / occur, for example, per time unit (e.g., TDM-ed). The time units may be, for example, consecutive. The time units may not be, for example, consecutive. The number of time units may be equal to the number of repetitions. The time unit may be, for example, a time slot. The time unit may be, for example, a minislot. The time unit may be, for example, a time symbol (e.g., OFDM symbol). The time unit may be, for example, a subframe. The time unit may be, for example, a monitoring opportunity in time (e.g., PDCCH monitoring opportunity). The number of multiple downlink control signal / channel transmission opportunities may be equal to the number of repetitions. The multiple downlink control signal / channel transmission opportunities may be / occur per time unit. For example, a first downlink control signal / channel transmission opportunity of the multiple downlink control signal / channel transmission opportunities may be / occur in a first time unit of the time units. A second downlink control signal / channel transmission opportunity of the multiple downlink control signal / channel transmission opportunities may be / occur in a second time unit of the time units.

[0306] In one embodiment, the repetition of a downlink control signal / channel (or transmission of multiple DCI / PDCCHs) may be / occur, for example, in frequency units (FDM-ed). The number of frequency units may be equal to the number of repetitions. The frequency unit may be, for example, a frequency band. The frequency unit may be, for example, a physical resource block (PRB). The frequency unit may be, for example, a resource element group (REG). The frequency unit may be, for example, a REG bundle. The frequency unit may be, for example, a control element (CE). The frequency unit may be, for example, a BWP. The frequency unit may be, for example, a cell. The number of multiple downlink control signal / channel transmission opportunities may be equal to the number of repetitions. The multiple downlink control signal / channel transmission opportunities may be / occur in frequency units. For example, a first downlink control signal / channel transmission opportunity of the multiple downlink control signal / channel transmission opportunities may be / occur in a first frequency unit of frequency units. A second downlink control signal / channel transmission opportunity of the multiple downlink control signal / channel transmission opportunities may be / occur in a second frequency unit of frequency units.

[0307] A base station may transmit multiple DCI / PDCCHs across / across time units. A base station may transmit multiple DCI / PDCCHs across / across frequency units. A base station may repeat downlink control signal / channel transmission across / across multiple uplink signal / channel transmission opportunities. A base station may transmit downlink control signal / channels with a repetition number. For example, in Figures 24 and 26, the multiple downlink control signal / channel transmission opportunities include a first downlink control signal / channel transmission opportunity (first TX opportunity) and a second downlink control signal / channel transmission opportunity (second TX opportunity). The first downlink control signal / channel transmission opportunity may be / occur in a first time unit of time units (e.g., a first time slot, a first symbol, a first subframe, a first PDCCH monitoring opportunity). The second downlink control signal / channel transmission opportunity may be / occur in a second time unit of time units (e.g., a second time slot, a second symbol, a second subframe, a second PDCCH monitoring opportunity). The first downlink control signal / channel transmission opportunity may be / occur in a first frequency unit of frequency units (e.g., first PRB, first cell, first frequency, first BWP, first subband, first REG bundle, first CE), and the second downlink control signal / channel transmission opportunity may be / occur in a second frequency unit of frequency units (e.g., second PRB, second cell, second frequency, second BWP, second subband, second REG bundle, second CE).

[0308] In one embodiment, the one or more configuration parameters may indicate a repetition scheme for control channel repetition (eg, according to higher layer parameters RepetitionSchemeConfig, FDM-Scheme, TDM-Scheme, SDM-Scheme, CDM-Scheme).

[0309] The repetition scheme may be, for example, a time domain repetition scheme, the repetition scheme may be, for example, a frequency domain repetition scheme, or the repetition scheme may be, for example, a space / code domain repetition scheme.

[0310] In one embodiment, a wireless device may monitor multiple core sets for multiple DCI / PDCCHs across / across multiple downlink control signal / channel transmission opportunities based on one or more configuration parameters indicating a repetition scheme.

[0311] In one embodiment, the repetition scheme may be a time-domain repetition scheme (e.g., a TDM scheme, inter-slot repetition, intra-slot repetition, TDMSchemeA, TDMSchemeB, etc.). In a time-domain repetition scheme, the multiple downlink control signal / channel transmission opportunities (e.g., a first TX opportunity and a second TX opportunity) may not overlap in time. In a time-domain repetition scheme, the multiple downlink control signal / channel transmission opportunities may or may not overlap in frequency. Each downlink control signal / channel transmission opportunity of the multiple downlink control signal / channel transmission opportunities may have a non-overlapping time-domain resource allocation with respect to other signal / channel transmission opportunities of the multiple downlink control signal / channel transmission opportunities. For example, a first downlink control signal / channel transmission opportunity of the multiple downlink control signal / channel transmission opportunities may not overlap in time with a second downlink control signal / channel transmission opportunity of the multiple downlink control signal / channel transmission opportunities. The first downlink control signal / channel transmission opportunity and the second downlink control signal / channel transmission opportunity may be different. For example, in a time-domain repetition scheme, a first downlink control signal / channel transmission opportunity (first TX opportunity) and a second downlink control signal / channel transmission opportunity (e.g., second TX opportunity) may not overlap in frequency. The multiple downlink control signal / channel transmission opportunities may occur in different time units. For example, the first time unit and the second time unit may not overlap in time. The first time unit and the second time unit may be different.

[0312] In one embodiment, the repetition scheme may be a frequency-domain repetition scheme (e.g., an FDM scheme, FDMSchemeA, FDMSchemeB, etc.). In a frequency-domain repetition scheme, the multiple downlink control signal / channel transmission opportunities may or may not overlap in time. In a frequency-domain repetition scheme, the multiple downlink control signal / channel transmission opportunities may not overlap in frequency. Each downlink control signal / channel transmission opportunity of the multiple downlink control signal / channel transmission opportunities may have a non-overlapping frequency-domain resource allocation with respect to other signal / channel transmission opportunities of the multiple downlink control signal / channel transmission opportunities. For example, a first downlink control signal / channel transmission opportunity of the multiple downlink control signal / channel transmission opportunities may not overlap in frequency with a second downlink control signal / channel transmission opportunity of the multiple downlink control signal / channel transmission opportunities. The first downlink control signal / channel transmission opportunity and the second downlink control signal / channel transmission opportunity may be different. For example, in a frequency-domain repetition scheme, the first downlink control signal / channel transmission opportunity (first TX opportunity) and the second downlink control signal / channel transmission opportunity (second TX opportunity) may not overlap in frequency. The first downlink control signal / channel transmission opportunity (first TX opportunity) and the second downlink control signal / channel transmission opportunity (second TX opportunity) may overlap in time. The multiple downlink control signal / channel transmission opportunities may occur in different frequency units (e.g., frequencies, PRBs, REGs, CEs, frequency bands, bandwidth portions, cells). For example, the first frequency unit of the first downlink control signal / channel transmission opportunity and the second frequency unit of the second downlink control signal / channel transmission opportunity may not overlap in frequency. The first frequency unit and the second frequency unit may be different.

[0313] In one embodiment, the repetition scheme may be a space / code domain repetition scheme (e.g., an SFN scheme, an SDM scheme, a CDM scheme, an SDMS scheme, a CDMS scheme, etc.). In a space / code domain repetition scheme, multiple downlink control signal / channel transmission opportunities may overlap in time. In a space / code domain repetition scheme, multiple downlink control signal / channel transmission opportunities may overlap in frequency. In a space / code domain repetition scheme, multiple downlink control signal / channel transmission opportunities may be a single downlink control signal / channel transmission opportunity. Each downlink control signal / channel transmission opportunity of the multiple downlink control signal / channel transmission opportunities may have overlapping frequency domain resource allocations with other downlink control signal / channel transmission opportunities of the multiple downlink control signal / channel transmission opportunities. Each downlink control signal / channel transmission opportunity of the multiple downlink control signal / channel transmission opportunities may have overlapping time domain resource allocations with other downlink control signal / channel transmission opportunities of the multiple downlink control signal / channel transmission opportunities. Each downlink control signal / channel transmission opportunity of the multiple downlink control signal / channel transmission opportunities may be identical. For example, a first downlink control signal / channel transmission opportunity of the multiple downlink control signal / channel transmission opportunities may overlap in time and frequency with a second downlink control signal / channel transmission opportunity of the multiple downlink control signal / channel transmission opportunities. The first downlink control signal / channel transmission opportunity and the second downlink control signal / channel transmission opportunity may be the same. For example, in a space / code domain repetition scheme, the first downlink control signal / channel transmission opportunity (first TX opportunity) and the second downlink control signal / channel transmission opportunity (second TX opportunity) may overlap in frequency. The first downlink con...

Claims

1. 1. A method comprising: A base station transmits, to a wireless device, a physical downlink control channel (PDCCH) comprising downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH), the PDCCH including PDCCH candidates from multiple search space sets associated with multiple control resource sets (core sets) configured for repetition; transmitting a transport block via the PDSCH to the wireless device, where resource block (RB) numbering of the PDSCH starts from a lowest RB of a core set having a lowest index among the plurality of core sets; A method comprising:

2. 2. The method of claim 1, further comprising: transmitting repetitions of the DCI over the multiple search space sets associated with the multiple core sets.

3. The method of claim 1 , wherein the plurality of search space sets is a plurality of common search space sets.

4. The method of claim 1 , wherein the DCI format of the DCI is DCI format 1_0.

5. 2. The method of claim 1, further comprising sending one or more messages comprising one or more configuration parameters indicating that the search space sets associated with the core sets are configured for iteration.

6. The method of claim 1 , wherein the lowest RB of the core set is the RB having a lowest starting frequency among one or more starting frequencies of one or more RBs of the core set.

7. The DCI comprises a resource indication field having a value indicating a virtual RB; The method of claim 1 , wherein a starting RB for receiving the transport block is determined based on a sum of the lowest RB and the virtual RB.

8. A base station, one or more processors; Memory to store instructions Equipped with The instructions, when executed by the one or more processors, transmitting, to a wireless device, a physical downlink control channel (PDCCH) comprising downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH), the PDCCH including PDCCH candidates from a plurality of search space sets associated with a plurality of control resource sets (core sets) configured for repetition; transmitting a transport block via the PDSCH to the wireless device, where resource block (RB) numbering of the PDSCH starts from a lowest RB of a core set having a lowest index among the plurality of core sets; A base station that causes the base station to perform the above.

9. The instruction: transmitting repetitions of the DCI over the plurality of search space sets associated with the plurality of core sets. The base station of claim 8 , further comprising:

10. The base station of claim 8 , wherein the plurality of search space sets are a plurality of common search space sets.

11. The base station according to claim 8 , wherein the DCI format of the DCI is DCI format 1_0.

12. The instruction: sending one or more messages comprising one or more configuration parameters indicating that the plurality of search space sets associated with the plurality of core sets are configured for iteration; The base station of claim 8 , further comprising:

13. The base station of claim 8 , wherein the lowest RB of the core set is an RB having a lowest starting frequency among one or more starting frequencies of one or more RBs of the core set.

14. The DCI comprises a resource indication field having a value indicating a virtual RB; The base station of claim 8 , wherein a starting RB for receiving the transport block is determined based on a sum of the lowest RB and the virtual RB.

15. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors of a wireless device, receiving a physical downlink control channel (PDCCH) comprising downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH), the PDCCH including PDCCH candidates from a plurality of search space sets associated with a plurality of control resource sets (core sets) configured for recursion; receiving a transport block via the PDSCH, where resource block (RB) numbering of the PDSCH starts from a lowest RB of a core set having a lowest index among the plurality of core sets; A non-transitory computer-readable medium for causing the wireless device to:

16. The instruction: monitoring through the plurality of search space sets associated with the plurality of core sets for the DCI iterations; 20. The non-transitory computer-readable medium of claim 15, further causing the wireless device to:

17. 16. The non-transitory computer-readable medium of claim 15, wherein the plurality of search space sets is a plurality of common search space sets.

18. 16. The non-transitory computer-readable medium of claim 15, wherein a DCI format of the DCI is DCI format 1_0.

19. 16. The non-transitory computer-readable medium of claim 15, wherein the lowest RB of the core set is an RB having a lowest starting frequency among one or more starting frequencies of one or more RBs of the core set.

20. The DCI comprises a resource indication field having a value indicating a virtual RB; 16. The non-transitory computer-readable medium of claim 15, wherein a starting RB for receiving the transport block is determined based on a sum of the lowest RB and the virtual RB.

Images