Common beam index based link selection

Abstract

The wireless device receives, from a base station, parameters indicative of a plurality of transmission configuration indicators (TCIs), including a first TCI for downlink reception and a second TCI for uplink transmission. A plurality of code points of a TCI field of a downlink control information (DCI) format are mapped to the plurality of TCIs. The wireless device receives a downlink control information (DCI) in a DCI format including a TCI field indicative of a code point of the plurality of code points. Based on the code point being mapped to a TCI of the second TCI, it is determined that the TCI is applicable for uplink transmission. Based on the TCI, an uplink signal is transmitted via an uplink control channel and an uplink shared channel.

Description

[Technical Field]

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

[0002] 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 detail 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) 1. A method comprising: From the base station by the wireless device, a first plurality of transmission configuration indicators (TCIs) for downlink reception; and receiving configuration parameters for a second plurality of TCIs for uplink transmission; receiving a parameter indicative of a plurality of TCIs, the plurality of TCIs comprising: a first TCI for downlink reception from the first plurality of TCIs; and a second TCI for uplink transmission from the second plurality of TCIs; mapping a plurality of code points of a TCI field of a downlink control information (DCI) format to the plurality of TCIs, wherein each code point of the plurality of code points is mapped to a respective TCI of the plurality of TCIs; receiving a DCI in the DCI format, the DCI format including the TCI field indicating a codepoint among the plurality of codepoints; determining that the TCI is applicable for uplink transmission based on the code point being mapped to a TCI among the second TCIs; and transmitting an uplink signal over an uplink control channel and an uplink shared channel based on the TCI. (Item 2) 1. A method comprising: receiving, by a wireless device, parameters indicative of a plurality of transmission configuration indicators (TCIs), the plurality of TCIs comprising: a first TCI for downlink reception; a second TCI for uplink transmission; and Mapping a plurality of code points of a TCI field of a downlink control information (DCI) format to the plurality of TCIs; receiving a DCI in the DCI format, the DCI format including the TCI field indicating a codepoint among the plurality of codepoints; determining that the TCI is applicable for uplink transmission based on the code point being mapped to a TCI among the second TCIs; and transmitting an uplink signal over an uplink control channel and an uplink shared channel based on the TCI. (Item 3) 3. The method of claim 2, wherein the plurality of code points are mapped correspondingly to the plurality of TCIs. (Item 4) 4. The method of claim 2 or 3, wherein each code point of the plurality of code points is mapped to a respective TCI of the plurality of TCIs. (Item 5) 5. The method according to any one of items 2 to 4, wherein the quantity of the plurality of code points is the same as the quantity of the TCI indicated by the parameter. (Item 6) 6. The method according to any one of items 2 to 5, wherein the DCI format comprises DCI format 1_2, DCI format 1_1, or DCI format 1_0. (Item 7) 7. The method according to any one of items 2 to 6, wherein, based on the DCI being in the DCI format, it is determined that the DCI includes the TCI field using a value indicating the code point. (Item 8) The parameters, for each TCI of the plurality of TCIs, cell index, Bandwidth Partial Index, a reference signal (RS) index indicating at least one of a channel state information reference signal (CSI-RS) index or a synchronization signal block (SSB) index; and 8. The method according to any one of items 2 to 7, showing a quasi-co-location type indicator. (Item 9) 9. The method of claim 8, wherein the transmitting the uplink signal includes transmitting an uplink data packet over a physical uplink shared channel (PUSCH) resource using the same spatial domain filter as that used to receive a reference signal indicated by the reference signal index associated with the TCI. (Item 10) 10. The method of claim 8 or 9, wherein the transmitting the uplink signal includes transmitting uplink control information over a PUCCH resource using the same spatial domain filter as that used to receive the reference signal indicated by the reference signal index associated with the TCI. (Item 11) 11. The method according to any one of items 8 to 10, wherein the transmitting the uplink signal includes transmitting a sounding reference signal using the same spatial domain filter as that used to receive the reference signal indicated by the reference signal index associated with the TCI. (Item 12) receiving a radio resource control (RRC) message, the RRC message comprising: a first plurality of TCIs for downlink reception; and 12. The method of any one of items 2 to 11, further comprising indicating and receiving a second plurality of TCIs for uplink transmission. (Item 13) the parameters are received in one or more Medium Access Control Elements (MAC CEs); and the first TCI from the first plurality of TCIs; and Item 13. The method of item 12, further comprising indicating activation of the second TCI from the second plurality of TCIs. (Item 14) receiving a second DCI in the DCI format including a second TCI field indicating a second codepoint of the plurality of codepoints; determining, based on the second code point being mapped to a second TCI of the first TCI, that the second TCI is applicable for downlink reception; 14. The method according to any one of items 2 to 13, further comprising receiving a downlink signal via a downlink control channel and a downlink shared channel based on the second TCI. (Item 15) Item 15. The method of item 14, wherein the second DCI schedules downlink resources for receiving the downlink signal, and the downlink signal is received based on the scheduled downlink resources. (Item 16) Item 16. The method of item 15, wherein the downlink resource is indicated by a downlink grant indicated by the second DCI. (Item 17) the downlink reception receiving a physical downlink shared channel (PDSCH); receiving a physical downlink control channel (PDCCH); Receipt of CSI-RS, or 17. The method according to any one of items 2 to 16, comprising at least one of receiving an SSB signal. (Item 18) the uplink transmission: transmitting a physical uplink shared channel (PUSCH); Physical Uplink Control Channel (PUCCH) transmission, or 18. The method according to any one of items 2 to 17, comprising at least one of: transmitting an SRS; (Item 19) 19. The method according to any one of items 2 to 18, wherein the parameters are received in one or more messages, including one or more Radio Resource Control (RRC) messages. (Item 20) 20. The method according to any one of items 2 to 19, wherein the parameters are received in one or more messages, including one or more Medium Access Control - Control Element (MAC-CE) messages. (Item 21) 21. The method according to any one of items 2 to 20, wherein the DCI is of a DCI format including downlink resource allocation via a Physical Downlink Shared Channel (PDSCH). (Item 22) 22. The method according to any one of items 2 to 21, wherein the DCI is of a DCI format including uplink resource allocation via a Physical Uplink Shared Channel (PUSCH). (Item 23) 23. The method according to any one of claims 2 to 22, wherein the transmitting the uplink signal includes transmitting an uplink data packet via a PUSCH resource using a spatial domain filter determined based on the TCI. (Item 24) 24. The method according to claim 23, wherein the PUSCH resource is indicated by a DCI. (Item 25) 25. The method according to any one of items 2 to 24, wherein the transmitting the uplink signal includes transmitting uplink control information via a PUCCH resource using a spatial domain filter determined based on the TCI. (Item 26) 26. The method of claim 25, wherein the PUCCH resource is indicated by the DCI. (Item 27) 27. The method according to any one of items 2 to 26, wherein the transmitting the uplink signal includes transmitting a sounding reference signal using a spatial domain filter determined based on the TCI. (Item 28) 28. The method according to any one of items 2 to 27, further comprising determining the TCI based on a TCI index. (Item 29) 29. The method according to any one of items 2 to 28, wherein the code point is associated with the TCI index that identifies the TCI. (Item 30) 30. The method of any one of items 2 to 29, wherein each TCI of the plurality of TCIs is associated with a link indicator. (Item 31) Item 31. The method of item 30, wherein the link indicator indicates one of a downlink and an uplink. (Item 32) Item 31. The method of item 30, wherein the link indicator indicates one of a downlink, an uplink, and a combination of a downlink and an uplink. (Item 33) Item 33. The method according to any one of items 2 to 32, wherein the DCI schedules uplink resources for transmitting the uplink signal. (Item 34) 34. The method of any one of items 2 to 33, wherein the parameters are received in a message including a TCI activation status field. (Item 35) Item 35. The method of item 34, wherein the TCI activation status field indicates the activation / deactivation status of one or more TCIs among the plurality of TCIs. (Item 36) 36. The method according to any one of items 30 to 35, wherein the plurality of code points comprises a first set of code points and a second set of code points. (Item 37) 37. The method of any one of items 30 to 36, further comprising mapping the set of first code points to the first TCI based on the link indicator of each of the first TCIs indicating a downlink. (Item 38) 38. The method of any one of items 30 to 37, further comprising: determining a first code point from the set of first code points as a mapping to the first TCI using the lowest TCI index of the first TCI. (Item 39) 38. The method of any one of items 30 to 37, further comprising: determining a first code point from the set of first code points as a mapping to the first TCI using the highest TCI index of the first TCI. (Item 40) Item 40. The method of item 38 or 39, wherein the first code point is a reference code point in the first set of code points from which other code points in the first set are determined. (Item 41) 41. The method of any one of items 30 to 40, further comprising mapping the set of second code points to the second TCI based on the link indicator of each of the second TCIs indicating an uplink. (Item 42) 42. The method according to any one of items 30 to 41, further comprising determining a second code point from the set of second code points as a mapping to the second TCI using the lowest TCI index of the second TCI. (Item 43) 42. The method according to any one of items 30 to 41, further comprising: determining a second code point from the set of second code points as a mapping to the second TCI using the highest TCI index of the second TCI. (Item 44) Item 44. The method of item 42 or 43, wherein the second code point is a reference code point in the second set of code points from which other code points in the second set are determined. (Item 45) said receiving said parameters receiving a first indication activating the first TCI for downlink reception; 45. The method of any one of items 2 to 44, comprising receiving a second indication that activates the second TCI for uplink transmission. (Item 46) Item 46. The method of item 45, wherein the first code point is determined to map to a respective TCI of the first TCIs in response to receiving the first indicator, and the second code point is determined to map to a respective TCI of the second TCIs in response to receiving the second indicator. (Item 47) 47. The method of any one of items 2 to 46, wherein the DCI schedules transmission of uplink data. (Item 48) 48. The method of claim 47, further comprising: determining, in response to receiving the DCI, that an uplink buffer is currently empty, wherein the uplink signal does not contain data from the uplink buffer. (Item 49) 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 perform the method described in any one of items 1 to 48. (Item 50) 49. 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 48. (Item 51) 1. A method comprising: by the base station to the wireless device; a first plurality of transmission configuration indicators (TCIs) for downlink reception; and transmitting configuration parameters of a second plurality of TCIs for uplink transmission; transmitting a parameter indicating a plurality of TCIs, the plurality of TCIs comprising: a first TCI for downlink reception from the first plurality of TCIs; and a second TCI for uplink transmission from the second plurality of TCIs; and mapping a plurality of code points of a TCI field of a downlink control information (DCI) format to the plurality of TCIs, wherein each code point of the plurality of code points is mapped to a respective TCI of the plurality of TCIs; transmitting a DCI of the DCI format including the TCI field indicating a code point among the plurality of code points; determining that the TCI is applicable for uplink transmission based on the code point being mapped to a TCI among the second TCIs; receiving an uplink signal via an uplink control channel and an uplink shared channel based on the TCI. (Item 52) 1. A method comprising: transmitting, by a base station to a wireless device, parameters indicative of a plurality of transmission configuration indicators (TCIs), the plurality of TCIs comprising: a first TCI for downlink reception; a second TCI for uplink transmission; and Mapping a plurality of code points of a TCI field of a downlink control information (DCI) format to the plurality of TCIs; transmitting a DCI of the DCI format including the TCI field indicating a code point among the plurality of code points; determining that the TCI is applicable for uplink transmission based on the code point being mapped to a TCI among the second TCIs; receiving an uplink signal via an uplink control channel and an uplink shared channel based on the TCI. (Item 53) Item 53. The method of item 52, wherein the plurality of code points are mapped correspondingly to the plurality of TCIs. (Item 54) Item 54. The method of item 52 or 53, wherein each code point of the plurality of code points is mapped to a respective TCI of the plurality of TCIs. (Item 55) 55. The method according to any one of items 52 to 54, wherein the quantity of the plurality of code points is the same as the quantity of the TCI indicated by the parameter. (Item 56) 56. The method according to any one of items 52 to 55, wherein the DCI format comprises DCI format 1_2, DCI format 1_1, or DCI format 1_0. (Item 57) 57. A method according to any one of items 52 to 56, wherein, based on the DCI being of the DCI format, it is determined that the DCI includes the TCI field using a value indicating the code point. (Item 58) The parameters, for each TCI of the plurality of TCIs, cell index, Bandwidth Partial Index, a reference signal (RS) index indicating at least one of a channel state information reference signal (CSI-RS) index or a synchronization signal block (SSB) index; and 58. The method of any one of items 52 to 57, showing a quasi-co-location type indicator. (Item 59) 59. The method of claim 58, wherein receiving the uplink signal includes receiving an uplink data packet over a physical uplink shared channel (PUSCH) resource using the same spatial domain filter as that transmitting a reference signal indicated by the reference signal index associated with the TCI. (Item 60) 50. The method of claim 58 or 59, wherein receiving the uplink signal includes receiving uplink control information over a PUCCH resource using the same spatial domain filter as that used to transmit the reference signal indicated by the reference signal index associated with the TCI. (Item 61) 61. The method of any one of items 58 to 60, wherein receiving the uplink signal includes receiving a sounding reference signal using the same spatial domain filter as that used to transmit the reference signal indicated by the reference signal index associated with the TCI. (Item 62) transmitting a radio resource control (RRC) message, a first plurality of TCIs for downlink reception; and Item 62. The method of any one of items 52 to 61, further comprising transmitting the RRC message indicating a second plurality of TCIs for uplink transmission. (Item 63) the parameters are transmitted in one or more Medium Access Control Elements (MAC CEs); and the first TCI from the first plurality of TCIs; and Item 63. The method of item 62, further comprising indicating activation of the second TCI from the second plurality of TCIs. (Item 64) transmitting a second DCI in the DCI format, the second DCI including a second TCI field indicating a second code point of the plurality of code points; determining, based on the second code point being mapped to a second TCI of the first TCI, that the second TCI is applicable for downlink reception; 64. The method according to any one of items 52 to 63, further comprising: transmitting a downlink signal via a downlink control channel and a downlink shared channel based on the second TCI. (Item 65) Item 65. The method of item 64, wherein the second DCI schedules downlink resources for transmitting the downlink signal, and the downlink signal is transmitted based on the scheduled downlink resources. (Item 66) Item 66. The method of item 65, wherein the downlink resource is indicated by a downlink grant indicated by the second DCI. (Item 67) the downlink reception receiving a physical downlink shared channel (PDSCH); receiving a physical downlink control channel (PDCCH); Receipt of CSI-RS, or 67. The method according to any one of items 52 to 66, comprising at least one of receiving SSB signals. (Item 68) the uplink transmission: transmitting a physical uplink shared channel (PUSCH); Physical Uplink Control Channel (PUCCH) transmission, or 68. The method according to any one of items 52 to 67, comprising at least one of: transmitting an SRS; (Item 69) Item 69. The method according to any one of items 52 to 68, wherein the parameters are transmitted in one or more messages, including one or more Radio Resource Control (RRC) messages. (Item 70) Item 69. The method according to any one of items 52 to 69, wherein the parameters are transmitted in one or more messages, including one or more Medium Access Control - Control Element (MAC-CE) messages. (Item 71) 71. The method according to any one of items 52 to 70, wherein the DCI is in the DCI format including downlink resource allocation via a Physical Downlink Shared Channel (PDSCH). (Item 72) 72. The method according to any one of items 52 to 71, wherein the DCI is in the DCI format including uplink resource allocation via a Physical Uplink Shared Channel (PUSCH). (Item 73) 73. The method of any one of items 52 to 72, wherein the receiving of the uplink signal includes receiving an uplink data packet via a PUSCH resource using a spatial domain filter determined based on the TCI. (Item 74) Item 74. The method according to item 73, wherein the PUSCH resource is indicated by a DCI. (Item 75) 75. The method of any one of items 52 to 74, wherein receiving the uplink signal includes receiving uplink control information via PUCCH resources using a spatial domain filter determined based on the TCI. (Item 76) Item 76. The method of item 75, wherein the PUCCH resource is indicated by the DCI. (Item 77) 77. The method of any one of items 52 to 76, wherein receiving the uplink signal includes receiving a sounding reference signal using a spatial domain filter determined based on the TCI. (Item 78) 78. The method according to any one of items 52 to 77, further comprising determining the TCI based on a TCI index. (Item 79) Item 79. The method of any one of items 52 to 78, wherein the code point is associated with the TCI index that identifies the TCI. (Item 80) Item 80. The method of any one of items 52 to 79, wherein each TCI of the plurality of TCIs is associated with a link indicator. (Item 81) Item 81. The method of item 80, wherein the link indicator indicates one of a downlink and an uplink. (Item 82) Item 81. The method of item 80, wherein the link indicator indicates one of a downlink, an uplink, and a combination of a downlink and an uplink. (Item 83) 83. The method of any one of items 52 to 82, wherein the DCI schedules uplink resources for receiving the uplink signal. (Item 84) 84. The method according to any one of items 52 to 83, wherein the parameters are transmitted in a message including a TCI activation status field. (Item 85) Item 85. The method of item 84, wherein the TCI activation status field indicates the activation / deactivation status of one or more TCIs among the plurality of TCIs. (Item 86) 86. The method of any one of items 80 to 85, wherein the plurality of code points comprises a first set of code points and a second set of code points. (Item 87) 87. The method of any one of items 80 to 86, further comprising mapping the set of first code points to the first TCI based on the link indicator of each of the first TCIs indicating a downlink. (Item 88) 88. The method of any one of items 80 to 87, further comprising: determining a first code point from the set of first code points as a mapping to the first TCI using the lowest TCI index of the first TCI. (Item 89) 88. The method of any one of items 80 to 87, further comprising: determining a first code point from the set of first code points as a mapping to the first TCI using the highest TCI index of the first TCI. (Item 90) Item 89. The method of item 88 or 89, wherein the first code point is a reference code point in the first set of code points from which other code points in the first set are determined. (Item 91) 91. The method of any one of items 80 to 90, further comprising mapping the set of second code points to the second TCI based on the link indicator of each of the second TCIs indicating an uplink. (Item 92) 92. The method of any one of items 80 to 91, further comprising: determining a second code point from the set of second code points as a mapping to the second TCI using the lowest TCI index of the second TCI. (Item 93) 92. The method of any one of items 80 to 91, further comprising: determining a second code point from the set of second code points as a mapping to the second TCI using the highest TCI index of the second TCI. (Item 94) Item 94. The method of any one of items 82 to 93, wherein the second code point is a reference code point in the second set of code points from which other code points in the second set are determined. (Item 95) transmitting the parameters receiving a first indication activating the first TCI for downlink reception; 95. The method of any one of items 52 to 94, further comprising receiving a second indication that activates the second TCI for uplink transmission. (Item 96) Item 96. The method of item 95, wherein the first code point is determined to map to a respective TCI of the first TCIs based on transmitting the first indicator, and the second code point is determined to map to a respective TCI of the second TCIs based on transmitting the second indicator. (Item 97) Item 97. A method according to any one of items 52 to 96, wherein the DCI schedules transmission of uplink data. (Item 98) 98. The method of claim 97, further comprising: determining, in response to receiving the DCI, that an uplink buffer is currently empty, and determining that the uplink signal does not contain data in the uplink buffer. (Item 99) 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 wireless device to perform the method described in any one of items 51 to 98. (Item 100) 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 51 to 98. (Item 101) 1. A system comprising: 1. A base station comprising: one or more first processors; and a first memory storing first instructions, wherein the first instructions, when executed by the one or more first processors, cause the base station to: transmitting a parameter indicative of a plurality of transmission configuration indicators (TCIs), the plurality of TCIs comprising: a first TCI for downlink reception; a second TCI for uplink transmission; Mapping a plurality of code points of a TCI field of a downlink control information (DCI) format to the plurality of TCIs; transmitting DCI in the DCI format, the DCI including the TCI field indicating a code point among the plurality of code points; determining that the TCI is applicable for uplink transmission based on the code point being mapped to a TCI among the second TCIs; a base station receiving an uplink signal via an uplink control channel and an uplink shared channel based on the TCI; 1. A wireless device comprising: one or more second processors; and a second memory storing second instructions, the second instructions, when executed by the one or more second processors, causing the wireless device to: receiving the parameters indicative of the plurality of TCIs; mapping the plurality of code points of the TCI field of the DCI format to the plurality of TCIs; receiving the DCI in the DCI format, the DCI including the TCI field indicating the codepoint among the plurality of codepoints; determining that the TCI is applicable for uplink transmission based on the code point being mapped to the TCI among the second TCIs; a wireless device configured to transmit the uplink signal via the uplink control channel and the uplink shared channel based on the TCI. (Item 102) 1. A system comprising: A base station comprising one or more first processors and a first memory storing first instructions, the first instructions, when executed by the one or more first processors, causing the base station to perform the method according to any one of items 51 to 98; A system comprising: a wireless device comprising one or more second processors; and a second memory storing second instructions, the second instructions, when executed by the one or more second processors, causing the wireless device to perform the method described in any one of items 1 to 48. [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 1A] 1 illustrates an example of a mobile communication network in which embodiments of the present disclosure may be implemented. [Figure 1B] 1 illustrates an example of a mobile communication network in which embodiments of the present disclosure may be implemented. [Figure 2] The new radio (NR) user plane and control plane protocol stacks are shown, respectively. [Figure 3] 2B illustrates one embodiment of services provided between protocol layers of the NR user plane protocol stack of FIG. 2A. [Figure 4A] 2B illustrates an exemplary downlink data flow through the NR user plane protocol stack of FIG. 2A. [Figure 4B] 1 illustrates an exemplary format of a MAC subheader in a MAC PDU. [Figure 5]The mapping between downlink and uplink logical, transport, and physical channels is shown, respectively. [Figure 6] FIG. 1 is an exemplary diagram illustrating RRC state transitions of a UE. [Figure 7] 1 illustrates an example structure of an NR frame in which OFDM symbols are grouped. [Figure 8] 1 illustrates an example configuration of slots in the time and frequency domain of an NR carrier. [Figure 9] 1 illustrates an example of bandwidth adaptation using three configured BWPs for an NR carrier. [Figure 10A] Three carrier aggregation configurations with two component carriers are shown. [Figure 10B] 1 illustrates an example of how aggregation cells can be organized into one or more PUCCH groups. [Figure 11A] 1 shows one embodiment of an SS / PBCH block structure and location. [Figure 11B] 1 illustrates an example of a CSI-RS mapped to the time and frequency domain. [Figure 12A] Three examples of downlink and uplink beam management procedures are shown, respectively. [Figure 12B] Three examples of downlink and uplink beam management procedures are shown, respectively. [Figure 13A] A four-step contention-based random access procedure, a two-step contention-free random access procedure, and an alternative two-step random access procedure are shown, respectively. [Figure 13B] A four-step contention-based random access procedure, a two-step contention-free random access procedure, and an alternative two-step random access procedure are shown, respectively. [Figure 13C] A four-step contention-based random access procedure, a two-step contention-free random access procedure, and an alternative two-step random access procedure are shown, respectively. [Figure 14A]1 shows an example of a CORESET configuration for bandwidth portions. [Figure 14B] 1 illustrates an embodiment of CCE-to-REG mapping for DCI transmission on CORESET and PDCCH processing. [Figure 15] 1 illustrates an embodiment of a wireless device communicating with a base station. [Figure 16] 1 shows an exemplary structure for uplink and downlink transmissions. [Figure 17A] 1 illustrates an example of a MAC subheader, according to some embodiments. [Figure 17B] 1 illustrates an example of a MAC subheader, according to some embodiments. [Figure 17C] 1 illustrates an example of a MAC subheader, according to some embodiments. [Figure 18A] 1 illustrates an example of a DL MAC PDU, according to some embodiments. [Figure 18B] 1 illustrates an example of a UL MAC PDU, according to some embodiments. [Figure 19] 1 illustrates an example of multiple LCIDs for downlink, according to some embodiments. [Figure 20] 1 illustrates an example of multiple LCIDs for an uplink, according to some embodiments. [Figure 21A] 10 illustrates an example of an SCell activation / deactivation MAC CE format, according to some embodiments. [Figure 21B] 10 illustrates an example of an SCell activation / deactivation MAC CE format, according to some embodiments. [Figure 22] 1 illustrates an example of a wireless communication system having multiple TRPs / panels, according to some embodiments. [Figure 23] 10 illustrates examples of individual TCI metrics, according to some embodiments. [Figure 24] 1 illustrates an example of a combined TCI index, according to some embodiments. [Figure 25] 1 illustrates an example of a common TCI index, according to some embodiments. [Figure 26] 1 illustrates an example of an N-octet TCI index MAC-CE according to some embodiments. [Figure 27] 1 illustrates an example of determining the codepoint of the TCI field of the DCI, according to some embodiments. [Figure 28A] 1 illustrates an example of determining the code point of the TCI field of the DCI, according to some embodiments. [Figure 28B] 1 illustrates an example of determining the code point of the TCI field of the DCI, according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0005] Detailed Description of the Invention 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.

[0006] 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 also refer to a subset of all wireless devices in the coverage area. This disclosure may refer, for example, to multiple wireless devices of a given LTE or 5G release that include a given capability and are in a given sector of the base station. Multiple wireless devices in this disclosure 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, the wireless devices or base stations may perform based on older releases of LTE or 5G technology.

[0007] 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 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.

[0008] 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 "in response to" (or equivalently, "at least in response to") indicates that the phrase following the phrase "in response 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 "adopted / used at least") 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 the various embodiments.

[0009] The term configured may relate to the capacity of a device, regardless of whether the device is in an operational or non-operational state. Configured may refer to a particular setting of a device that affects 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 particular characteristics. A term such as "a control message originating in a device" may mean that the control message has parameters that can be used to configure particular characteristics in the device or to implement particular actions in the device, regardless of whether the device is in an operational or non-operational state.

[0010] In this disclosure, a parameter (or equivalently referred to as a field, or information element: IE) may contain one or more information objects, which in turn may contain one or more other objects. For example, if parameter (IE) N contains parameter (IE) M, which contains parameter (IE) K, which in turn contains parameter (information element) J, then N contains K and N contains J. In an exemplary 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.

[0011] Many presented features are described as optional through 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.

[0012] 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 a module 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 a hardware description language (HDL) such as Verilog or Verilog Hardware Description Language (VHDL), which configures 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.

[0013] 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.

[0014] 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.

[0015] 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 over the air interface from the RAN 104 to the wireless devices 106 is known as the downlink, and the communication direction over the air interface from the wireless devices 106 to the RAN 104 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.

[0016] 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.

[0017] 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 node 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 standards), and / or any combination thereof. A base station may include at least one gNB central unit (gNB-CU) and at least one gNB distributed unit (gNB-DU).

[0018] 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.

[0019] 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 a sector site having more or less than three sectors. One or more base stations of the RAN 104 may be implemented as an access point, as a baseband processing unit coupled to multiple remote radio heads (RRHs), and / or as a repeater or relay node used to extend the coverage area of ​​a donor node. The baseband processing unit coupled to the RRHs may be part of a centralized or cloud RAN architecture, and the baseband processing unit may be centralized or virtualized within a pool of baseband processing units. A repeater node may amplify and rebroadcast wireless signals received from a donor node. A relay node may perform the same / similar functions as a repeater node, but may decode wireless signals received from a donor node and remove noise before amplifying and rebroadcasting the wireless signals.

[0020] 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.

[0021] The 3rd 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 a 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.

[0022] 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.

[0023] 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 5G-CN 152 may be based on 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).

[0024] 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, which are shown in FIG. 1B as a single component, AMF / UPF 158, for ease of explanation. 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.

[0025] 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.

[0026] 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).

[0027] 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 be more generally 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.

[0028] As shown in FIG. 1B, the gNB 160 and / or the ng-eNB 162 may be connected to the 5G-CN 152 by an NG interface and to other base stations by an Xn interface. The NG and Xn interfaces may be established using a direct physical connection and / or an indirect connection 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 by a Uu interface. For example, as shown in FIG. 1B, the gNB 160A may be connected to the UE 156A by 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 a user. The control plane may process signaling messages of interest to the network elements.

[0029] 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 be connected 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, transport of NAS messages, paging, PDU session management, and configuration transfer and / or alert message transmission.

[0030] 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.

[0031] 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.

[0032] 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 the user, and the control plane may handle signaling messages of interest to the network elements.

[0033] Figures 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.

[0034] 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.

[0035] 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. The CN's UPF (e.g., UPF 158B) 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 mapping / demapping between QoS flows and data radio bearers.

[0036] 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 decoding 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 retransmission of undelivered packets, in-sequence delivery and reordering of packets, and removal of duplicate received packets, for example, for intra-gNB handover. PDCPs 214 and 224 may perform packet duplication to improve the likelihood of a packet being received and to remove any duplicate packets at the receiver. Packet duplication may be useful for services that require high reliability.

[0037] 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.

[0038] 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.

[0039] 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.

[0040] The PHYs 211 and 221 may perform mapping of transport channels to physical channels 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 FIG. 3, the PHYs 211 and 221 may provide one or more transport channels as services to the MACs 212 and 222.

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

[0042] The downlink data flow in Figure 4A begins when 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.

[0043] 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 subheaders 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 subheaders may be calculated before the complete MAC PDU is assembled.

[0044] 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 to which the MAC subheader corresponds, a logical channel identifier (LCID) field to identify the logical channel on which the MAC SDU originated 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.

[0045] 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 the MAC PDU for downlink transmission (as shown in FIG. 4B) and at the end of the MAC PDU for uplink transmission. MAC CEs may be used for in-band control signaling. Examples of MAC CEs include scheduling-related MAC CEs, such as buffer status reports and power headroom reports; 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 the 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.

[0046] 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.

[0047] 5A and 5B show the mapping between logical channels, transport channels, and physical channels for the downlink and uplink, respectively. Information is passed 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 in the NR control plane, or as traffic channels, which carry data in the NR user plane. Logical channels may be classified as dedicated logical channels, which are dedicated to a specific UE, or as common logical channels, which can be used by more than one UE. 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 indicating paging messages used to page UEs whose location is unknown to the network at the cell level; a Broadcast Control Channel (BCCH) for conveying 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 carrying control messages along with random access; - a dedicated control channel (DCCH) for carrying control messages to and from a specific UE for configuring the UE; - Dedicated Traffic Channel (DTCH) for carrying user data to and from a specific UE.

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

[0049] The PHY may use physical channels to pass information between processing levels of the PHY. A physical channel may have an associated set of time-frequency resources for carrying information for one or more transport channels. The PHY may generate control information to support the lower level operation of the PHY and provide control information to the lower levels of the PHY via physical control channels known as L1 / L2 control channels. The set of physical channels and physical control channels defined by NR may include, 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.

[0050] 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), the Secondary Synchronization Signal (SSS), the Channel State Information Reference Signal (CSI-RS), the Demodulation Reference Signal (DMRS), the Sounding Reference Signal (SRS), and the Phase Tracking Reference Signal (PT-RS). These physical layer signals are described in more detail below.

[0051] 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.

[0052] The NAS protocols 217 and 237 may provide control plane functions between the UE 210 and the AMF 230 (e.g., the 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 transported. NAS messages can be transported 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.

[0053] 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 control of reporting, 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 communications between the UE 210 and the RAN.

[0054] 6 is an example diagram illustrating RRC state transitions for 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).

[0055] 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 the 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.

[0056] In RRC idle 604, an RRC context may not 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.

[0057] 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 faster 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.

[0058] 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 allow the network to track the UE on a cell group level so that paging messages can 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 the UE on a cell group level. They may do so using different 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 called a Tracking Area and identified by a Tracking Area Identifier (TAI).

[0059] 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 UE registration areas. 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 enable the CN to update the UE's location and provide the UE with a new UE registration area.

[0060] The RAN area may be used to track the UE at the RAN level. For a UE in 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.

[0061] A base station that stores the RRC context for a 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 while the UE remains in the RAN notification area of ​​the anchor base station and / or while the UE remains in RRC inactive 606.

[0062] A gNB, such as gNB 160 in FIG. 1B, may be divided into two parts: a central unit (gNB-CU) and one or more distributed units (gNB-DUs). The gNB-CU may 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.

[0063] 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, the 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, which 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 the FFT block to recover the data mapped to the source symbols.

[0064] Figure 7 shows an example configuration of an NR frame 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.

[0065] The duration of a slot may depend on the numerology used for the OFDM symbol of the slot. NR supports flexible numerology to accommodate different cell deployments (e.g., cells with carrier frequencies less than 1 GHz up to cells with carrier frequencies in the mm-wave range). Numerologies 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 numerologies with the following subcarrier spacing / cyclic prefix duration combinations: 15 kHz / 4.7 μs, 30 kHz / 2.3 μs, 60 kHz / 1.2 μs, 120 kHz / 0.59 μs, and 240 kHz / 0.29 μs.

[0066] A slot 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 the 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.

[0067] Figure 8 shows an example configuration of a slot in the time and frequency domain for 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.

[0068] 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.

[0069] 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.

[0070] 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 BWPs 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.

[0071] For unpaired spectrum, a downlink BWP from a set of configured downlink BWPs may be linked with an uplink BWP from a 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.

[0072] 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) for an active downlink BWP.

[0073] 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).

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

[0075] 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.

[0076] The base station may 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.

[0077] 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).

[0078] Downlink and uplink BWP switching (BWP switching refers to switching from a currently active BWP to a non-currently active BWP) can be performed 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.

[0079] 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 switching 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 switching point. In the example of FIG. 9, the UE may switch from BWP 902 to BWP 904 at switching point 908. Switching at switching 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 be switched from the active BWP 904 to BWP 906 at switching point 910 in response to receiving a DCI indicating BWP 906 as the active BWP. The UE may be switched from the active BWP 906 to BWP 904 at switching 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 be switched from the active BWP 904 to BWP 902 at switching point 914 in response to receiving a DCI indicating BWP 902 as the active BWP.

[0080] If the UE is configured for a secondary cell with a default downlink BWP in the set of configured downlink BWPs and timer values, the UE procedures for switching BWPs on the secondary cell may be the same / similar to those 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.

[0081] To provide greater 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 many serving cells for the UE and one cell for the CC. A CC can have three configurations in the frequency domain:

[0082] 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).

[0083] 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). The 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. The ability 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.

[0084] When CA is used, one of the aggregation cells for a UE 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 for a 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).

[0085] A configured SCell for a UE may be activated and deactivated based on, for example, traffic and channel conditions. Deactivating a SCell may mean that PDCCH and PDSCH reception on the SCell is stopped and PUSCH, SRS, and CQI transmission on the SCell is stopped. A configured SCell may be activated and deactivated using a MAC CE, with reference 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 the UE are activated or deactivated. A configured SCell may be deactivated in response to expiration of a SCell deactivation timer (e.g., one SCell deactivation timer per SCell).

[0086] Downlink control information, such as scheduling assignments and scheduling grants for a cell, 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. A cell may be divided into multiple PUCCH groups.

[0087] 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. 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 embodiment, if the aggregation cells 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 UCI between PCell 1021 and PSCell 1061, the overload may be prevented.

[0088] 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.

[0089] 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.

[0090] 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 a UE. In the uplink, a UE may transmit one or more RSs to a 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.

[0091] 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 duration of 5 milliseconds). It will be appreciated that FIG. 11A is an example implementation, and these parameters (number of SS / PBCH blocks per burst, burst periodicity, and burst position within a frame) may be configured based on, for example, the carrier frequency of the cell in which the SS / PBCH block is 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 block based on the monitored carrier frequency, unless the wireless network configures the UE to assume a different subcarrier spacing.

[0092] An SS / PBCH block may span one or more OFDM symbols in the time domain (e.g., four OFDM symbols as shown in the example 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.

[0093] 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 duration (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, a 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.

[0094] 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, where the SS / PBCH block in the transmission pattern is a known distance from the frame boundary.

[0095] 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 may 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 of 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.

[0096] 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.

[0097] 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 example, a first SS / PBCH block may be transmitted in a first spatial direction using a first beam, and a second SS / PBCH block may be transmitted in a second spatial direction using a second beam.

[0098] In one embodiment, within the 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.

[0099] 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 a UE with one or more CSI-RS for channel estimation or any other suitable purpose. The base station may configure a 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).

[0100] 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 which CSI-RS resources in a CSI-RS resource set are activated and / or deactivated.

[0101] 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 transmit and selectively activate or deactivate periodic reports. The base station may configure the UE with a CSI-RS resource set and CSI reports using RRC signaling.

[0102] 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) if 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 if 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.

[0103] The downlink DMRS may be transmitted by a base station and used by a UE for channel estimation. For example, the 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. The DMRS configuration may support one or more DMRS ports. For example, in the case of single-user MIMO, the DMRS configuration may support up to eight orthogonal downlink DMRS ports per UE. In the case of multi-user MIMO, the 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 can be the same or different. The base station can transmit the downlink DMRS and corresponding PDSCH using the same precoding matrix. The UE can use one or more downlink DMRSs for coherent demodulation / channel estimation of the PDSCH.

[0104] In one embodiment, 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 be different 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).

[0105] 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.

[0106] 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 configured 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. The 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 resource. The downlink PT-RS may be limited to the UE's scheduled time / frequency duration. The downlink PT-RS may be transmitted over symbols to facilitate phase tracking at the receiver.

[0107] A 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 DMRS may span a frequency range similar to the frequency range associated with the corresponding physical channel. The base station may configure the UE with one or more uplink DMRS configurations. At least one DMRS configuration may support a 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 the 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 the 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 or different.

[0108] 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.

[0109] The uplink PT-RS (which may be used by the base station for phase tracking and / or phase noise compensation) may be present or absent 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 limited to the UE's scheduled time / frequency duration.

[0110] The SRS may be transmitted by the UE to a 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 may 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 at a certain time (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 by 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 an SRS after the transmission of the PUSCH and the corresponding uplink DMRS.

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

[0112] 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) through which the second symbol on the antenna port is carried 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 carried can be inferred from the channel through which the second symbol on the second antenna port is carried. 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.

[0113] In a channel using beamforming, beam management is required. Beam management may include beam measurement, beam selection, and beam index. 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. A UE may perform a downlink beam measurement procedure after an RRC connection is set up with a base station.

[0114] 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. A base station may transmit one or more RRC messages containing CSI-RS resource configuration parameters indicating one or more CSI-RS. One or more of the following parameters may be set by higher layer signaling (e.g., RRC and / or MAC signaling) for the CSI-RS resource configuration: CSI-RS resource configuration identity, number of CSI-RS ports, CSI-RS configuration (e.g., 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-coordinate (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

[0115] The three beams shown in FIG. 11B may be configured for a UE with 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 in the RB of the first symbol. Beam #2 may be assigned with CSI-RS 1102, which may be transmitted on one or more subcarriers in the RB of the second symbol. Beam #3 may be assigned with CSI-RS 1103, which may be transmitted on one or more subcarriers in 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 in 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.

[0116] 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 indicator (TCI) states, including several reference signals, based on the reported measurements. 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 index an uplink beam for the UE based on measurements of one or more SRS resources transmitted by the UE.

[0117] 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).

[0118] 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 (indicated as ellipses in the top and bottom rows of P1, respectively). Beamforming at a TRP may include a Tx beam sweep for 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 for 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.

[0119] 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.

[0120] The UE may initiate a beam failure recovery (BFR) procedure based on the detection of a beam failure. The UE may transmit a BFR request (e.g., a preamble, UCI, SR, MAC CE, and / or the like) based on the initiation of 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).

[0121] 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 a 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 over the RS resource are similar or identical to the channel characteristics from a transmission to the UE over the channel.

[0122] 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 uplink transmission of SR when there are no available PUCCH resources) 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.

[0123] Figure 13A shows a four-step contention-based random access procedure. Before the procedure begins, the base station may transmit 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).

[0124] 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 the 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 transmitted 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.

[0125] The one or more RACH parameters provided in the configuration message 1310 may indicate one or more physical RACH (PRACH) opportunities available for transmission of 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.

[0126] 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).

[0127] 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 the one or more reference signals and / or the selected preamble group, for example, if an association between one or more preambles and at least one reference signal is configured by the RRC message.

[0128] The UE may determine the preamble based on one or more RACH parameters provided in the configuration message 1310. For example, the UE may determine the 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.

[0129] 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 (eg, preambleTransMax).

[0130] The UE receives Msg2 1312, which 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 indexed 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 transmission of Msg3 1313, and / or a temporary cell RNTI (TC-RNTI). After transmitting the preamble, the UE may begin 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 Type1-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 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 will 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.

[0131] Msg4 1314 may be received after or in response to 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 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.

[0132] 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 the uplink carrier for Msg1 1311 and / or Msg3 1313 based on a channel clear assessment (eg, listen-before-talk).

[0133] 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.

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

[0135] 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 the transmission of Msg1 1321 and the reception of 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 a 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 confirmation to the SI request.

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

[0137] Msg A 1331 may be transmitted by the UE in an uplink transmission. 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 the like). 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.

[0138] 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.

[0139] 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.

[0140] 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 transmit 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.

[0141] 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.

[0142] The downlink control signaling may include downlink scheduling assignments, uplink scheduling grants indicating uplink radio resources and / or transport formats, slot format information, preemption indicators, power control commands, and / or any other suitable signaling. A UE may receive the 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.

[0143] 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 the UE's identifier (or the identifier of the group of UEs). Scrambling the CRC parity bits with the 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).

[0144] 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.

[0145] 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 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.

[0146] After scrambling the DCI with the RNTI, the base station may process the DCI with channel coding (e.g., polarity 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 a PDCCH occupying several consecutive control channel elements (CCEs). The number of consecutive CCEs (referred to as an 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).

[0147] FIG. 14A illustrates an example of a CORESET configuration for bandwidth portions. 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 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 a 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.

[0148] Figure 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 frequency-selective transmission of interference coordination and / or 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 a quasi-coordinated location (QCL) parameter of an antenna port. The QCL parameter of an antenna port may indicate QCL information of a demodulation reference signal (DMRS) for PDCCH reception within the CORESET.

[0149] The base station may transmit an RRC message to the UE including configuration parameters of 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 monitored per aggregation level, the PDCCH monitoring periodicity and PDCCH monitoring pattern, one or more DCI formats monitored by the UE, and / or whether the search space set is a common search space set or a UE-specific search space set. The set of CCEs in 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).

[0150] 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 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 indicator, downlink preemption, and / or the like).

[0151] 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 transmission format parameters (e.g., including multiple antennas and beamforming schemes) for 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 over the PUCCH using one of several PUCCH formats.

[0152] 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 transmit UCI on PUCCH resources using PUCCH format 0 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. A 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 two 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 resources do not include an orthogonal cover code. PUCCH format 4 may occupy between 4 and 14 OFDM symbols and may include more than two 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 resources include an orthogonal cover code.

[0153] The base station may transmit configuration parameters of 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 less than or equal to two, 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 the 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 the 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'.

[0154] 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 of 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.

[0155] 15 illustrates an example of a wireless device 1502 communicating with a base station 1504 according to 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 another communication network. While only one wireless device 1502 and one base station 1504 are shown in FIG. 15, it will be understood that a mobile communication network may include more than one UE and / or more than one base station having the same or similar configuration as that shown in FIG. 15.

[0156] 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.

[0157] On the downlink, data transmitted from base station 1504 to wireless device 1502 may be provided to processing system 1508 of base station 1504. The data may be provided to processing system 1508 by, for example, a core network. On the uplink, data transmitted from wireless device 1502 to base station 1504 may be provided to processing system 1518 of wireless device 1502. Processing system 1508 and 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.

[0158] After being processed by processing system 1508, data to be transmitted to wireless device 1502 may be provided to transmission 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 transmission processing system 1520 of wireless device 1502. Transmission processing system 1510 and transmission 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 transmission 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.

[0159] 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.

[0160] 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.

[0161] 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.

[0162] 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 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.

[0163] 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. 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, an indexing device, 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 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 can be configured to distribute power to other components in the wireless device 1502. The power source can 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 can be connected to a GPS chipset 1517 and a GPS chipset 1527, respectively. The GPS chipset 1517 and the GPS chipset 1527 can be configured to provide geographic location information for the wireless device 1502 and the base station 1504, respectively.

[0164] FIG. 16A illustrates an exemplary 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 illustrated by way of example, and it is anticipated that other mechanisms may be implemented in various embodiments.

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

[0166] 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 several 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.

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

[0168] A wireless device may receive one or more messages (e.g., RRC messages) from a base station 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.

[0169] A timer may begin execution when started and continue to run until it is 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 a 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 a 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.

[0170] A base station may transmit one or more MAC PDUs to a wireless device. In one embodiment, the MAC PDU may be a bit string whose length is byte-aligned (e.g., a multiple of 8 bits). In one embodiment, the bit string may be represented by a table with the most significant bit being the leftmost bit of the first row of the table and the least significant bit being the rightmost bit of the last row of the table. More generally, the bit string is read from left to right, then in row reading order. In one embodiment, the bit order of the parameter field in the MAC PDU is represented with the most significant bit first in the leftmost bit and the least significant bit last in the rightmost bit.

[0171] In one embodiment, the MAC SDU may be a bit string whose length is byte-aligned (e.g., a multiple of 8 bits). In one embodiment, the MAC SDU may be included in the MAC PDU after the first bit. The MAC CE may be a bit string whose length is byte-aligned (e.g., a multiple of 8 bits). The MAC subheader may be a bit string whose length is byte-aligned (e.g., a multiple of 8 bits). In one embodiment, the MAC subheader may be located immediately before the corresponding MAC SDU, MAC CE, or padding. The MAC entity may ignore the value of the reserved bit in the DL MAC PDU.

[0172] In one embodiment, a MAC PDU may include one or more MAC sub-PDUs, where a MAC sub-PDU includes a MAC subheader only (including padding), a MAC subheader and a MAC SDU, a MAC subheader and a MAC CE, and / or a MAC subheader and padding. The MAC SDUs may be of variable size. The MAC subheader may correspond to a MAC SDU, a MAC CE, or padding.

[0173] In one embodiment, if the MAC subheader corresponds to a MAC SDU, a variable-sized MAC CE, or padding, the MAC subheader may include a 1-bit R field, a 1-bit F field, a multi-bit LCID field, and / or a multi-bit L field.

[0174] Figure 17A shows an example of a MAC subheader with an R field, an F field, an LCID field, and an L field. In the example MAC subheader of Figure 17A, the LCID field may be 6 bits long, and the L field may be 8 bits long. Figure 17B shows an example of a MAC subheader with an R field, an F field, an LCID field, and an L field. In the example MAC subheader of Figure 17B, the LCID field may be 6 bits long, and the L field may be 16 bits long. If the MAC subheader supports fixed-size MAC CE or padding, the MAC subheader may include a 2-bit R field and a multi-bit LCID field. Figure 17C shows an example of a MAC subheader including an R field and an LCID field. In the example MAC subheader of Figure 17C, the LCID field may be 6 bits long, and the R field may be 2 bits long.

[0175] FIG. 18A shows an example of a DL MAC PDU. Multiple MAC CEs, such as MAC CEs 1 and 2, may be arranged together. A MAC sub-PDU containing a MAC CE may be arranged before any MAC sub-PDU containing a MAC SDU or a MAC sub-PDU containing padding. FIG. 18B shows an example of a UL MAC PDU. Multiple MAC CEs, such as MAC CEs 1 and 2, may be arranged together. A MAC sub-PDU containing a MAC CE may be arranged after a MAC sub-PDU containing a MAC SDU, for example, after all MAC sub-PDUs containing MAC SDUs. Furthermore, a MAC sub-PDU may be arranged before a MAC sub-PDU containing padding.

[0176] In one embodiment, the MAC entity of the base station may transmit one or more MAC CEs to the MAC entity of the wireless device. Figure 19 shows an example of multiple LCIDs that may be associated with one or more MAC CEs. One or more MAC CEs may include Semi-Persistent (SP) Zero Power (ZP) CSI-RS Resource Set Activation / Deactivation MAC CE, PUCCH Spatial Relationship Activation / Deactivation MAC CE, SP SRS Activation / Deactivation MAC CE, SP CSI Report for PUCCH Activation / Deactivation MAC CE, Transmission Configuration Indicator (TCI) State Indication for UE-specific PDCCH MAC CE, TCI State Indication for UE-specific PDSCH MAC CE, Aperiodic CSI Trigger State Subselection MAC CE, SP CSI-RS / CSI-IM Resource Set Activation / Deactivation MAC CE, e.g., CSI Interference Measurement (CSI-IM), UE Contention Resolution Identity MAC CE, Timing Advance Command MAC CE, DRX Command MAC CE, Long DRX Command MAC CE, SCell Activation / Deactivation MAC CE (1 octet), SCell Activation / Deactivation MAC CE. The MAC CE may include at least one of a Long DRX command MAC CE (4 octets), a Long DRX command MAC CE (4 octets), and / or a Duplicate Activation / Deactivation MAC CE. In one embodiment, a MAC CE, such as a MAC CE sent by a base station MAC entity to a wireless device MAC entity, may have an LCID in a MAC subheader corresponding to the MAC CE. Different MAC CEs may have different LCIDs in the MAC subheader corresponding to the MAC CE. For example, an LCID given by 111011 in a MAC subheader may indicate that the MAC CE associated with the MAC subheader is a Long DRX command MAC CE.

[0177] In one embodiment, the MAC entity of the wireless device can transmit one or more MAC CEs to the MAC entity of the base station. Figure 20 illustrates one embodiment of the one or more MAC CEs. The one or more MAC CEs may include at least one of a short buffer status report (BSR) MAC CE, a long BSR MAC CE, a C-RNTI MAC CE, a configured grant confirmation MAC CE, a single-entry power headroom report (PHR) MAC CE, a multiple-entry PHR MAC CE, a short barring BSR, and / or a long barring BSR. In one embodiment, a MAC CE may have an LCID in a MAC subheader corresponding to the MAC CE. Different MAC CEs may have different LCIDs in the MAC subheaders corresponding to the MAC CE. For example, an LCID given by 111011 in a MAC subheader may indicate that the MAC CE associated with the MAC subheader is a short barring command MAC CE.

[0178] In carrier aggregation (CA), two or more component carriers (CCs) may be aggregated. Using CA techniques, a wireless device may simultaneously receive or transmit on one or more CCs, depending on the capabilities of the wireless device. In one embodiment, a wireless device may support CA for adjacent and / or non-adjacent CCs. CCs may be organized into cells. For example, CCs may be organized into one primary cell (PCell) and one or more secondary cells (SCells). When configured with CA, a wireless device may have one RRC connection with the network. During RRC connection establishment / re-establishment / handover, the cell providing NAS mobility information may be the serving cell. During RRC connection re-establishment / handover procedures, the cell providing security input may be the serving cell. In one embodiment, the serving cell may refer to the PCell. In one embodiment, a base station may send one or more messages to a wireless device, including configuration parameters for a plurality of one or more SCells, depending on the capabilities of the wireless device.

[0179] When configured with CA, the base station and / or wireless device may use an SCell activation / deactivation mechanism to improve battery or power consumption of the wireless device. When a wireless device is configured with one or more SCells, the base station may activate or deactivate at least one of the one or more SCells. An SCell may be deactivated unless the SCell state associated with the SCell is set to "activated" or "dormant" upon configuration.

[0180] The wireless device may activate / deactivate the SCell in response to receiving the SCell activation / deactivation MAC CE. In one embodiment, the base station may send one or more messages including an SCell timer (e.g., sCellDeactivationTimer) to the wireless device. In one embodiment, the wireless device may deactivate the SCell in response to expiration of the SCell timer.

[0181] When the wireless device receives an SCell activation / deactivation MAC CE activating the SCell, the wireless device may activate the SCell. In response to the SCell activation, the wireless device may perform operations including SRS transmission on the SCell, CQI / PMI / RI / CRI reporting for the SCell, e.g., CSI-RS resource indicator (CRI), PDCCH monitoring on the SCell, PDCCH monitoring for the SCell, and / or PUCCH transmission on the SCell. In response to the SCell activation, the wireless device may start or restart a first SCell timer (e.g., sCellDeactivationTimer) associated with the SCell. The wireless device may start or restart the first SCell timer in a slot when the SCell activation / deactivation MAC CE activating the SCell is received. In one embodiment, in response to the SCell activation, the wireless device may (re)initialize one or more suspended configured uplink grants of configured grant type 1 associated with the SCell according to a stored configuration. In one embodiment, in response to activation of the SCell, the wireless device may trigger a PHR.

[0182] When the wireless device receives an SCell activation / deactivation MAC CE that deactivates an activated SCell, the wireless device may deactivate the activated SCell. In one embodiment, when a first SCell timer (e.g., sCellDeactivationTimer) associated with the activated SCell expires, the wireless device may deactivate the activated SCell. In response to the deactivation of the activated SCell, the wireless device may stop the first SCell timer associated with the activated SCell. In one embodiment, in response to the deactivation of the activated SCell, the wireless device may clear one or more configured downlink assignments and / or one or more configured uplink grants of configured uplink grant type 2 associated with the activated SCell. In one embodiment, in response to the deactivation of the activated SCell, the wireless device may suspend one or more configured uplink grants of configured uplink grant type 1 associated with the activated SCell and / or flush HARQ buffers associated with the activated SCell.

[0183] When an SCell is deactivated, the wireless device may not perform operations including transmitting an SRS on the SCell, reporting CQI / PMI / RI / CRI of the SCell, transmitting on a UL-SCH on the SCell, transmitting on a RACH on the SCell, monitoring at least one first PDCCH on the SCell, monitoring at least one second PDCCH on the SCell, and / or transmitting a PUCCH on the SCell. When the at least one first PDCCH on the activated SCell indicates an uplink grant or a downlink assignment, the wireless device may restart a first SCell timer (e.g., sCellDeactivationTimer) associated with the activated SCell. In one embodiment, if at least one second PDCCH on a serving cell (e.g., a PCell or a SCell configured with a PUCCH, e.g., a PUCCH SCell) scheduling the activated SCell indicates an uplink grant or a downlink assignment for the activated SCell, the wireless device may restart a first SCell timer (e.g., sCellDeactivationTimer) associated with the activated SCell. In one embodiment, when an SCell is deactivated, if there is an ongoing random access procedure on the SCell, the wireless device may abort the ongoing random access procedure on the SCell.

[0184] Figure 21A shows an example of a one-octet SCell activation / deactivation MAC CE. A first MAC PDU subheader with a first LCID (e.g., "111010" as shown in Figure 19) can identify the one-octet SCell activation / deactivation MAC CE. The size of the one-octet SCell activation / deactivation MAC CE may be constant. The one-octet SCell activation / deactivation MAC CE may include a single octet. The single octet can include a first number of C fields (e.g., 7) and a second number of R fields (e.g., 1). Figure 21B shows an example of a four-octet SCell activation / deactivation MAC CE. A second MAC PDU subheader with a second LCID (e.g., "111001" as shown in Figure 19) can identify the four-octet SCell activation / deactivation MAC CE. The size of the 4-octet SCell activation / deactivation MAC CE may be constant. The 4-octet SCell activation / deactivation MAC CE may include 4 octets. The 4 octets may include a third number C field (e.g., 31) and a fourth number R field (e.g., 1).

[0185] In FIG. 21A and / or FIG. 21B, when an SCell having SCell index i is configured, C i The field may indicate the activation / deactivation status of the SCell with SCell index i. i When the field is set to 1, the SCell with SCell index i may be activated. i If the field is set to zero, the SCell with SCell index i may be deactivated. In one embodiment, if there is no SCell configured with SCell index i, the wireless device iThe R field may be ignored. In Figures 21A and 21B, the R field may indicate reserved bits. The R field may be set to zero.

[0186] A base station may configure a wireless device with an uplink (UL) bandwidth portion (BWP) and a downlink (DL) BWP to enable bandwidth adaptation (BA) on a PCell. If carrier aggregation is configured, the base station may further configure the wireless device with at least a DL BWP to enable BA on an SCell (e.g., there may be no UL BWP on the UL). For a PCell, the initial active BWP may be a first BWP used for initial access. For an SCell, the first active BWP may be a second BWP that the wireless device is configured to operate on when the SCell is activated. In paired spectrum (e.g., FDD), the base station and / or wireless device can switch between the DL BWP and the UL BWP individually. In unpaired spectrum (e.g., TDD), the base station and / or wireless device can switch between the DL BWP and the UL BWP simultaneously.

[0187] In one embodiment, the base station and / or wireless device can switch BWPs between configured BWPs via a DCI or a BWP inactivity timer. If a BWP inactivity timer is configured for a serving cell, the base station and / or wireless device can switch the active BWP to a default BWP in response to expiration of the BWP inactivity timer associated with the serving cell. The default BWP can be configured by the network. In one embodiment, for an FDD system, if configured with a BA, one UL BWP and one DL BWP for each uplink carrier can be simultaneously active in the active serving cell. In one embodiment, for a TDD system, one DL / UL BWP pair can be simultaneously active in the active serving cell. Operating with one UL BWP and one DL BWP (or one DL / UL pair) can improve battery consumption of the wireless device. BWPs other than the one active UL BWP and one active DL BWP on which the wireless device can operate can be deactivated. In a deactivated BWP, the wireless device may not monitor the PDCCH and / or may not transmit on the PUCCH, PRACH, and UL-SCH.

[0188] In one embodiment, a serving cell may be configured with up to a first number (e.g., four) of BWPs. In one embodiment, for an activated serving cell, there may be one active BWP at any time. In one embodiment, BWP switching for a serving cell may be used to activate inactive BWPs and deactivate active BWPs at a time. In one embodiment, BWP switching may be controlled by a PDCCH indicating a downlink assignment or an uplink grant. In one embodiment, BWP switching may be controlled by a BWP inactivity timer (e.g., bwp-InactivityTimer). In one embodiment, BWP switching may be controlled by a MAC entity in response to the initiation of a random access procedure. Upon addition of an SpCell or activation of an SCell, one BWP may be initially activated without receiving a PDCCH indicating a downlink assignment or an uplink grant. The active BWP of a serving cell may be indicated by RRC and / or PDCCH. In one embodiment, for unpaired spectrum, a DL BWP can be paired with a UL BWP, and BWP switching can be common to both UL and DL.

[0189] The base station may configure the wireless device with a list of one or more TCI state configurations via a higher layer parameter PDSCH-Config for the serving cell. The number of one or more TCI states may depend on the capabilities of the wireless device. The wireless device may use one or more TCI states to decode the PDSCH according to the PDCCH detected using the DCI. The DCI may be intended for the wireless device and the wireless device's serving cell.

[0190] In one embodiment, a TCI state of one or more TCI state configurations may include one or more parameters. The wireless device may use the one or more parameters to configure a quasi-coordinate relationship between one or two downlink reference signals of the PDSCH (e.g., a first DL RS and a second DL RS) and a DM-RS port. The quasi-coordinate relationship may be configured by an upper layer parameter qcl-Type1 for the first DL RS. The quasi-coordinate relationship may be configured by an upper layer parameter qcl-Type2 for the second DL RS (if configured).

[0191] In one embodiment, when a wireless device configures a quasi-coordinate relationship between two downlink reference signals (e.g., between a first DL RS and a second DL RS), the first QCL type of the first DL RS and the second QCL type of the second DL RS may not be the same. In one embodiment, the first DL RS and the second DL RS may be the same. In one embodiment, the first DL RS and the second DL RS may be different.

[0192] In one embodiment, the quasi-co-location type (e.g., first QCL type, second QCL type) of a DL RS (e.g., first DL RS, second DL RS) may be provided to the wireless device by an upper layer parameter qcl-Type of QCL-Info. The upper layer parameter QCL-Type may be at least one of QCL-TypeA: {Doppler shift, Doppler spread, average delay, delay spread}; QCL-TypeB: {Doppler shift, Doppler spread}; QCL-TypeC: {average delay, Doppler shift}; and QCL-TypeD: {Spatial Rx parameter}.

[0193] In one embodiment, the wireless device may receive an activation command. The activation command may be used to map one or more TCI states (e.g., up to eight) to one or more code points of a DCI field "Transmission Configuration Indicator (TCI)." In one embodiment, the wireless device may transmit a HARQ-ACK corresponding to a PDSCH for slot n. The PDSCH may include / carry an activation command. In response to transmitting the HARQ-ACK in slot n, the wireless device may map one or more TCI states and one or more code points of a DCI field "Transmission Configuration Indicator (TCI)."

number

[0194] In one embodiment, after the wireless device receives an initial higher layer configuration of one or more TCI states and before receiving an activation command, the wireless device may assume that one or more DM-RS ports of the PDSCH of the serving cell are quasi-co-located with the SSB / PBCH block. In one embodiment, the wireless device may determine the SSB / PBCH block in the initial access procedure for "QCL-Type A." In one embodiment, the wireless device may determine the SSB / PBCH block in the initial access procedure for "QCL-Type D" (if applicable).

[0195] In one embodiment, a wireless device may be configured by a base station with an upper layer parameter TCI-PresentInDCI. If the upper layer parameter TCI-PresentInDCI is set as “enabled” for a control resource set (CORESET) that schedules a PDSCH, the wireless device may assume that the TCI field is present in a DCI format (e.g., DCI format 1_1) for a PDCCH transmitted on the CORESET.

[0196] In one embodiment, the base station may not configure a CORESET with the higher layer parameter TCI-PresentInDCI. In one embodiment, the CORESET may schedule a PDSCH. In one embodiment, a time offset between the DCI received in the CORESET (e.g., DCI format 1_1, DCI format 1_0) and the reception of the (corresponding) PDSCH may be equal to or greater than a threshold (e.g., Threshold-Sched-Offset). In one embodiment, the threshold may be based on reported UE capabilities. In one embodiment, the wireless device may apply a second TCI state to the CORESET used for PDCCH transmission of the DCI. In one embodiment, the wireless device may apply a second QCL assumption to the CORESET used for PDCCH transmission of the DCI. In one embodiment, in response to the base station configuring a CORESET with the higher layer parameter TCI-PresentInDCI and when the time offset between the reception of the DCI and the PDSCH is equal to or greater than a threshold, the wireless device may perform default PDSCH RS selection. In one embodiment, in default PDSCH RS selection, the wireless device may assume that a first QCL assumption for a first TCI state or PDSCH is the same as a second QCL assumption applied for a second TCI state or CORESET to determine quasi-identical antenna port locations for the PDSCH.

[0197] In one embodiment, the base station may configure the CORESET with an upper layer parameter TCI-PresentInDCI. In one embodiment, the upper layer parameter TCI-PresentInDCI may be set as "enabled." In one embodiment, the CORESET may schedule the PDSCH using DCI (e.g., DCI format 1_0). In one embodiment, the DCI may not include a TCI field. In one embodiment, the time offset between reception of the DCI received in the CORESET and the (corresponding) PDSCH may be greater than or equal to a threshold (e.g., Threshold-Sched-Offset). In one embodiment, the threshold may be based on reported UE capabilities. In one embodiment, the wireless device may apply a second TCI state to the CORESET used for PDCCH transmission of the DCI. In one embodiment, the wireless device may apply a second QCL assumption to the CORESET used for PDCCH transmission of the DCI. In one embodiment, in response to the base station scheduling a PDSCH using a DCI that does not include a TCI field and the time offset between reception of the DCI and the PDSCH being equal to or greater than a threshold, the wireless device may perform default PDSCH RS selection. In one example embodiment, in the default PDSCH RS selection, the wireless device may assume that a first QCL assumption for a first TCI state or PDSCH is the same as a second QCL assumption applied for a second TCI state or CORESET to determine quasi-identical antenna port locations for the PDSCH.

[0198] In one embodiment, the base station may configure a CORESET with an upper layer parameter TCI-PresentInDCI. In one embodiment, the upper layer parameter TCI-PresentInDCI may be set as "enabled." The wireless device may receive a DCI in the CORESET of a scheduling component carrier. The DCI may include a TCI field. In response to the upper layer parameter TCI-PresentinDCI being set as "enabled," the TCI field in the DCI in the scheduling component carrier may point to one or more activated TCI states (e.g., after receiving an activation command) on the scheduled component carrier or DL ​​BWP.

[0199] In one embodiment, the base station may configure CORESET with an upper layer parameter TCI-PresentInDCI. In one embodiment, the upper layer parameter TCI-PresentInDCI may be set as “enabled.” The wireless device may receive DCI (e.g., DCI format 1_1) in CORESET. In one embodiment, the DCI may schedule a PDSCH for the wireless device. In one embodiment, a TCI field may be present in the DCI. In one embodiment, a time offset between the DCI and reception of the (corresponding scheduled) PDSCH may be greater than or equal to a threshold (e.g., Threshold-Sched-Offset). In one embodiment, the threshold may be based on reported UE capabilities. In one embodiment, in response to the TCI field being present in the DCI scheduling the PDSCH and in response to the upper layer parameter TCI-PresentinDCI being set as “enabled” for CORESET, the wireless device may use the TCI state according to the value of the TCI field in the detected PDCCH with the DCI to determine quasi-coincident positions of antenna ports for the PDSCH. In one embodiment, the use of the TCI state by the value of the TCI field may include that the wireless device may assume that one or more DM-RS ports of the PDSCH of the serving cell are quasi-co-located with one or more RSs in the TCI state with respect to one or more QCL type parameters given by the TCI state when the time offset between reception of the DCI and the PDSCH is greater than or equal to a threshold. In one embodiment, the value of the TCI field may indicate the TCI state.

[0200] In one embodiment, a base station may configure a wireless device with a single-slot PDSCH. In one embodiment, the single-slot PDSCH may be scheduled in the slot. In one embodiment, the base station may activate one or more TCI states in the slot. In response to configuring the single-slot PDSCH, the TCI state (e.g., indicated by a TCI field of a DCI scheduling the single-slot PDSCH) may be based on one or more activated TCI states in the slot having the scheduled single-slot PDSCH. In one embodiment, the TCI state may be one of one or more activated TCI states in the slot. In one embodiment, the TCI field of the DCI may indicate the TCI state of one or more activated TCI states in the slot.

[0201] In one embodiment, a wireless device may be configured with a CORESET. In one embodiment, the CORESET may be associated with a search space set for cross-carrier scheduling. In one embodiment, in response to the CORESET being associated with the search space set for cross-carrier scheduling, the wireless device may expect the upper layer parameter TCI-PresentInDCI to be set to “enabled” for the CORESET. In one embodiment, a base station may configure a serving cell with one or more TCI states. In one embodiment, the wireless device may detect a PDCCH using a DCI in the search space set and schedule a PDSCH. In one embodiment, a TCI field in the DCI may indicate at least one of the one or more TCI states. In one embodiment, at least one of the one or more TCI states (scheduled by the search space set) may include a QCL type (e.g., QCL-TypeD, etc.). In one embodiment, in response to at least one of the one or more TCI states scheduled by a search space set that includes a QCL type, the wireless device may expect a time offset between the reception of a PDCCH detected in the search space set and a (corresponding) PDSCH to be greater than or equal to a threshold (e.g., Threshold-Sched-Offset).

[0202] In one embodiment, the base station may configure CORESET with an upper layer parameter TCI-PresentInDCI. In one embodiment, the upper layer parameter TCI-PresentInDCI may be set as "enabled." In one embodiment, when the upper layer parameter TCI-PresentInDCI is set to "enabled" for CORESET, the offset between the DCI in CORESET and the reception of the PDSCH scheduled by the DCI may be less than a threshold (e.g., Threshold-Sched-Offset).

[0203] In one embodiment, the base station may not configure CORESET with the higher layer parameter TCI-PresentInDCI. In one embodiment, the wireless device may be in RRC connected mode. In one embodiment, the wireless device may be in RRC idle mode. In one embodiment, the wireless device may be in RRC inactive mode. In one embodiment, if the higher layer parameter TCI-PresentInDCI is not configured for CORESET, the offset between reception of DCI in the core set and the PDSCH scheduled by the DCI may be lower than a threshold (e.g., Threshold-Sched-Offset).

[0204] In one embodiment, a wireless device may monitor one or more CORESETs (or one or more search spaces) within an active BWP (e.g., an active downlink BWP) of a serving cell within one or more slots. In one embodiment, monitoring one or more CORESETs within an active BWP of a serving cell within one or more slots may include monitoring at least one CORESET within an active BWP of a serving cell within each slot of the one or more slots. In one embodiment, the most recent slot of the one or more slots may occur at a most recent time. In one embodiment, a wireless device may monitor one or more second CORESETs of one or more CORESETs in the most recent slot within an active BWP of a serving cell. In response to monitoring one or more second CORESETs of the most recent slot and the most recent slot occurring at a most recent time, the wireless device may determine the most recent slot. In one embodiment, each CORESET of the one or more second CORESETs may be identified by a CORESET-specific index (e.g., indicated by a higher layer CORESET-ID). In one embodiment, a CORESET-specific index of a CORESET of the one or more second CORESETs may be the lowest among the CORESET-specific indexes of the one or more second CORESETs. In one embodiment, the wireless device may monitor a search space associated with a CORESET in a most recent slot. In one embodiment, in response to monitoring the search space associated with the CORESET in the most recent slot having the lowest CORESET-specific index of the CORESET, the wireless device may select a CORESET of the one or more second CORESETs.

[0205] In one embodiment, when the offset between reception of DCI in a CORESET and the PDSCH scheduled by the DCI is lower than a threshold (e.g., Threshold-Sched-Offset), the wireless device may perform default PDSCH RS selection. In one embodiment, in default PDSCH RS selection, the wireless device may assume that one or more DM-RS ports of the PDSCH of the serving cell are quasi-co-located with one or more RSs in the TCI state with respect to one or more QCL type parameters. One or more RSs in the TCI state may be used for PDCCH quasi-co-location indicators of the (selected) CORESET of one or more second CORESETs.

[0206] In one embodiment, the wireless device may receive DCI via a PDCCH in the CORESET. In one embodiment, the DCI may schedule a PDSCH. In one embodiment, an offset between reception of the DCI and the PDSCH may be less than a threshold (e.g., Threshold-Sched-Offset). A first QCL type (e.g., "QCL-Type D") of one or more DM-RS ports of the PDSCH may be different from a second QCL type (e.g., "QCL-Type D") of one or more second DM-RS ports of the PDCCH. In one embodiment, the PDSCH and the PDCCH may overlap by at least one symbol. In one embodiment, in response to the PDSCH and the PDCCH overlapping by at least one symbol and the first QCL type being different from the second QCL type, the wireless device prioritizes reception of the PDCCH associated with the CORESET. In one embodiment, the prioritization may apply to an intra-band CA case (when the PDSCH and the CORESET are on different component carriers). In one embodiment, prioritizing reception of the PDCCH may include receiving the PDSCH with a second QCL type of one or more second DM-RS ports of the PDCCH. In one embodiment, prioritizing reception of the PDCCH may include overriding a first QCL type of one or more DM-RS ports of the PDSCH with a second QCL type of one or more second DM-RS ports of the PDCCH. In one embodiment, prioritizing reception of the PDCCH may include assuming a spatial QCL (e.g., a second QCL type) of the PDCCH for simultaneous reception of the PDCCH and the PDSCH on the PDSCH. In one embodiment, prioritizing reception of the PDCCH may include applying a spatial QCL (e.g., a second QCL type) of the PDCCH for simultaneous reception of the PDCCH and the PDSCH on the PDSCH. In one embodiment, prioritizing reception of the PDCCH may include receiving the PDCCH and not receiving the PDSCH.

[0207] In one example, none of the configured TCI states includes a QCL type (e.g., “QCL-TypeD”). In response to none of the configured TCI states including a QCL type, the wireless device may obtain other QCL assumptions from the indicated TCI state for that scheduled PDSCH, regardless of the time offset between reception of the DCI and the corresponding PDSCH.

[0208] In one embodiment, the wireless device may use the CSI-RS for at least one of time / frequency tracking, CSI calculation, L1-RSRP calculation, and mobility.

[0209] In one embodiment, the base station may configure the wireless device to monitor CORESET over one or more symbols. In one embodiment, the CSI-RS resources may be associated with an NZP-CSI-RS-ResourceSet. The higher layer parameter repetition of the NZP-CSI-RS-ResourceSet may be set to "on." In one embodiment, in response to the CSI-RS resources being associated with the NZP-CSI-RS-ResourceSet by setting the higher layer parameter repetition to "on," the wireless device may not expect to be configured with CSI-RS of the CSI-RS resources over one or more symbols.

[0210] In one embodiment, the higher layer parameter repetition of NZP-CSI-RS-ResourceSet may not be set to "on." In one embodiment, a base station may configure CSI-RS resources and one or more search space sets associated with CORESET within the same one or more symbols (e.g., OFDM symbols). In one embodiment, in response to the higher layer parameter repetition of NZP-CSI-RS-ResourceSet not being set to "on" and the CSI-RS resources and one or more search space sets associated with CORESET being configured in the same one or more symbols, a wireless device may assume that the CSI-RS of the CSI-RS resources and one or more DM-RS ports of the PDCCH are quasi-co-located with "QCL-TypeD." In one embodiment, a base station may transmit a PDCCH in one or more search space sets associated with CORESET.

[0211] In one embodiment, the higher layer parameter repetition of NZP-CSI-RS-ResourceSet may not be set to "on." In one embodiment, the base station may configure one or more search space sets associated with the CSI-RS resources of a first cell and the CORESET of a second cell within the same one or more symbols (e.g., OFDM symbols). In one embodiment, in response to the higher layer parameter repetition of NZP-CSI-RS-ResourceSet not being set to "on" and the one or more search space sets associated with the CSI-RS resources and the CORESET being configured in the same one or more symbols, the wireless device may assume that the CSI-RS of the CSI-RS resources and one or more DM-RS ports of the PDCCH are quasi-co-located with "QCL-TypeD." In one embodiment, the base station may transmit the PDCCH in one or more search space sets associated with the CORESET. In one embodiment, the first cell and the second cell may be on different in-band component carriers.

[0212] In one embodiment, a base station may configure a wireless device with CSI-RS in a first PRB set. In one embodiment, the base station may configure a wireless device with one or more search space sets associated with one or more symbols (e.g., OFDM symbols) and a CORESET of a second PRB set. In one embodiment, the wireless device may not expect the first PRB set and the second PRB set to overlap in one or more symbols.

[0213] In one embodiment, the base station may configure the wireless device with CSI-RS resources and SS / PBCH blocks in the same one or more (OFDM) symbols. In one embodiment, in response to the CSI-RS resources and SS / PBCH blocks being configured in the same one or more (OFDM) symbols, the wireless device may assume that the CSI-RS resources and SS / PBCH blocks are quasi-co-located with a QCL type (e.g., "QCL-Type D").

[0214] In one embodiment, the base station may configure the CSI-RS resources into a first PRB set for the wireless device. In one embodiment, the base station may configure the SS / PBCH blocks into a second PRB set for the wireless device. In one embodiment, the wireless device may not expect the first PRB set to overlap with the second PRB set.

[0215] In one embodiment, a base station may configure a CSI-RS resource with a first subcarrier spacing for a wireless device. In one embodiment, a base station may configure an SS / PBCH block with a second subcarrier spacing for a wireless device. In one embodiment, the wireless device may expect the first subcarrier spacing and the second subcarrier spacing to be the same.

[0216] In one example, a base station may configure a wireless device with an NZP-CSI-RS-ResourceSet. In one example, the NZP-CSI-RS-ResourceSet may be configured with the upper layer parameter repetition set to "on." In one example, in response to the NZP-CSI-RS-ResourceSet being configured with the upper layer parameter repetition set to "on," the wireless device may assume that the base station transmits one or more CSI-RS resources in the NZP-CSI-RS-ResourceSet with the same downlink spatial domain transmit (Tx) filter. In one example, the base station may transmit each CSI-RS resource of the one or more CSI-RS resources in a different symbol (e.g., OFDM symbol).

[0217] In one example, the NZP-CSI-RS-ResourceSet may be configured with the higher layer parameter repetition set to “off.” In one example, in response to the NZP-CSI-RS-ResourceSet being configured with the higher layer parameter repetition set to “off,” the wireless device may not assume that the base station will transmit one or more CSI-RS resources in the NZP-CSI-RS-ResourceSet using the same downlink spatial-domain transmit filter.

[0218] In one embodiment, a base station may configure a wireless device with an upper layer parameter group BasedBeamReporting. In one embodiment, the base station may set the upper layer parameter group BasedBeamReporting to “enabled.” In response to setting the upper layer parameter group BasedBeamReporting to “enabled,” the wireless device may report at least two different resource indicators (e.g., CRI, SSBRI) in a single report instance for one or more reporting configurations. In one embodiment, the wireless device may receive at least two RSs (e.g., CSI-RS, SSB) simultaneously indicated by at least two different resource indicators. In one embodiment, the wireless device may receive at least two RSs simultaneously using a single spatial domain receive (Rx) filter. In one embodiment, the wireless device may receive at least two RSs simultaneously using multiple simultaneous spatial domain Rx filters.

[0219] In one embodiment, a base station may require (add) one or more pieces of user equipment (UE) radio access capability information of a wireless device. In response to requiring one or more pieces of UE radio access capability information, the base station may initiate a procedure to request one or more pieces of UE radio access capability information from the wireless device (e.g., via an information element UECapabilityEnquiry). In one embodiment, the wireless device may use an information element (e.g., a UECapabilityInformation message) to transfer one or more pieces of UE radio access capability information requested by the base station. In one embodiment, the wireless device may provide thresholds (e.g., timeDurationForQCL, Threshold-Sched-Offset) in FeatureSetDownlink indicating a set of features that the wireless device supports.

[0220] In one embodiment, the threshold may include a minimum number of OFDM symbols required by a wireless device to perform PDCCH reception using a DCI and apply spatial QCL information (e.g., TCI status, etc.) received in (or indicated by) the DCI for processing of a PDSCH scheduled by the DCI.

[0221] In one embodiment, the wireless device may require a minimum number of OFDM symbols between PDCCH reception and PDSCH processing to apply the spatial QCL information indicated by the DCI to the PDSCH.

[0222] In one embodiment, a base station may configure a wireless device with one or more sounding reference signal (SRS) resource sets via an upper layer parameter SRS-ResourceSet. In one embodiment, for one or more SRS resource sets, the base station may configure the wireless device with one or more SRS resources via an upper layer parameter SRS-Resource. In one embodiment, the wireless device may indicate to the base station (e.g., via SRS_capability) a maximum number of one or more SRS resources. In one embodiment, the base station may configure the availability of an SRS resource set via an upper layer parameter usage in the upper layer parameter SRS-ResourceSet.

[0223] In one example, when the upper layer parameter "usage" is set to "BeamManagement," the wireless device may transmit (e.g., simultaneously) one SRS resource of the one or more SRS resources in each SRS resource set at a given time. In one example, the wireless device may determine that the one SRS resource of the one or more SRS resources in each SRS resource set may have the same time-domain behavior in the same BWP (e.g., uplink BWP). In one example, in response to determining, the wireless device may simultaneously transmit the one SRS resource of the one or more SRS resources in each SRS resource set in the same BWP.

[0224] In one embodiment, when the upper layer parameter "usage" is set to "BeamManagement," the wireless device may transmit only one SRS resource in each of one or more SRS resource sets at a given time (e.g., simultaneously). In one embodiment, the wireless device may determine that only one SRS resource in each of one or more SRS resource sets may have the same time-domain behavior in the same BWP (e.g., uplink BWP). In one embodiment, in response to determining, the wireless device may simultaneously transmit only one SRS resource in each of one or more SRS resource sets in the same BWP.

[0225] In one embodiment, when the upper layer parameter "usage" is set to "BeamManagement," the wireless device may simultaneously transmit one SRS resource in each of one or more SRS resource sets at a given time. In one embodiment, the wireless device may determine that one SRS resource in each of one or more SRS resource sets may have the same time-domain behavior in the same BWP (e.g., uplink BWP). In one embodiment, in response to determining, the wireless device may simultaneously transmit one SRS resource in each of one or more SRS resource sets in the same BWP.

[0226] In one embodiment, the one or more SRS resource sets may include a first SRS resource set and a second SRS resource set. In one embodiment, the first SRS resource set may include one or more first SRS resources. The one or more first SRS resources may include the first SRS resource and the second SRS resource. In one embodiment, the second SRS resource set may include one or more second SRS resources. The one or more second SRS resources may include a third SRS resource and a fourth SRS resource.

[0227] In one embodiment, the first time domain behavior of the first SRS resource and the third time domain behavior of the third SRS resource may be identical in the BWP. In one embodiment, when the upper layer parameter usage is set to “BeamManagement,” the wireless device may transmit the first SRS resource of the first SRS resource set and the third SRS resource of the second SRS resource set simultaneously at a predetermined time in the BWP in response to the first time domain behavior of the first SRS resource and the third time domain behavior of the third SRS resource being identical.

[0228] In one embodiment, the first time domain behavior of the first SRS resource and the fourth time domain behavior of the fourth SRS resource may be different in the BWP. In one embodiment, when the upper layer parameter "usage" is set to "BeamManagement," the wireless device may not simultaneously transmit the first SRS resource of the first SRS resource set and the fourth SRS resource of the second SRS resource set at a given time in the BWP in response to the first time domain behavior of the first SRS resource and the fourth time domain behavior of the fourth resource being different.

[0229] In one example, the second time domain behavior of the second SRS resource and the fourth time domain behavior of the fourth SRS resource may be the same in the BWP. In one example, when the upper layer parameter "usage" is set to "BeamManagement," the wireless device may simultaneously transmit the second SRS resource of the first SRS resource set and the fourth SRS resource of the second SRS resource set at a predetermined time in the BWP in response to the second time domain behavior of the second SRS resource and the fourth time domain behavior of the fourth SRS resource being the same.

[0230] In one embodiment, the second time domain behavior of the second SRS resource and the third time domain behavior of the third SRS resource may be different in the BWP. In one embodiment, when the higher layer parameter "usage" is set to "BeamManagement," the wireless device may not simultaneously transmit the second SRS resource of the first SRS resource set and the third SRS resource of the second SRS resource set at a given time in the BWP in response to the second time domain behavior of the second SRS resource and the third time domain behavior of the third SRS resource being different.

[0231] In one embodiment, the upper layer parameter SRS-resource may semi-statically configure at least one of an srs-resource index indicating the configuration of the SRS resource (e.g., provided by the upper layer parameter srs-ResourceId), a time-domain behavior of the configuration of the SRS resource (e.g., indicated by the upper layer parameter resourceType), an SRS sequence ID (e.g., provided by the upper layer parameter sequenceId), and a spatial relationship configuration between the reference RS and the target SRS. In one embodiment, the base station may configure the wireless device using the upper layer parameter spatialRelationInfo. In one embodiment, the upper layer parameter spatialRelationInfo may include an index (ID) of the reference RS. In one embodiment, the time-domain behavior of the SRS resource may be periodic transmission, semi-persistent transmission, or aperiodic SRS transmission. In one embodiment, the time-domain behavior of the SRS resource may include a transmission periodicity, a transmission offset of the SRS resource, etc.

[0232] In one example, the wireless device may determine that an upper layer parameter servingCellId indicating a serving cell may be present in the upper layer parameter spatialRelationInfo. In response to determining, the wireless device may determine that the reference RS may be a first RS (e.g., an SS / PBCH block, a CSI-RS) configured on the serving cell.

[0233] In one embodiment, the wireless device may determine that an upper layer parameter uplinkBWP indicating an uplink BWP and an upper layer parameter servingCellId indicating a serving cell may be present in the upper layer parameter spatialRelationInfo. In one embodiment, in response to determining, the wireless device may determine that the reference RS may be a first RS (e.g., SRS) configured on the uplink BWP of the serving cell.

[0234] In one embodiment, the base station may configure a target SRS on the serving cell. In one embodiment, the wireless device may determine that the upper layer parameter servingCellId may not be present in the upper layer parameter spatialRelationInfo. In response to the determination, the wireless device may determine that the reference RS may be a first RS (e.g., SS / PBCH block, CSI-RS) configured on the serving cell.

[0235] In one embodiment, the base station may configure a target SRS on the serving cell. In one embodiment, the wireless device may determine that the upper layer parameter servingCellId is absent and that the upper layer parameter uplinkBWP indicating an uplink BWP is present in the upper layer parameter spatialRelationInfo. In response to the determination, the wireless device may determine that the reference RS may be a first RS (e.g., an SRS) configured on the uplink BWP of the serving cell.

[0236] In one embodiment, the wireless device may transmit the PUSCH and the SRS in the same slot. In response to transmitting the PUSCH and the SRS in the same slot, the base station may configure the wireless device to transmit the SRS after transmitting the PUSCH (and corresponding DM-RS).

[0237] In one embodiment, the base station may configure the wireless device with one or more SRS resource configurations. In one embodiment, the higher layer parameter resourceType in the higher layer parameter SRS resource may be set to "periodic."

[0238] In one embodiment, the base station may configure the wireless device with the higher layer parameter spatialRelationInfo, which may include the ID of the reference RS (e.g., ssb-Index, csi-RS-Index, srs).

[0239] In one embodiment, the reference RS may be an SS / PBCH block. In one embodiment, the reference RS may be a CSI-RS (e.g., a periodic CSI-RS, a semi-persistent CSI-RS, or an aperiodic CSI-RS). In one embodiment, the wireless device may receive the reference RS using a spatial-domain receive (Rx) filter. In one embodiment, in response to the higher layer parameter spatialRelationInfo indicating that the reference RS (e.g., by the ID of the reference RS) is an SS / PBCH block or a CSI-RS, the wireless device may transmit the target SRS resource using the same spatial-domain transmit (Tx) filter as the spatial-domain receive (Rx) filter. In one embodiment, in response to the higher layer parameter spatialRelationInfo indicating the reference RS (e.g., by the ID of the reference RS), the wireless device may transmit the target SRS resource using the spatial-domain Rx filter.

[0240] In one example, the reference RS may be an SRS (e.g., a periodic SRS, a semi-persistent SRS, or an aperiodic SRS). In one example, the wireless device may transmit the reference RS using a spatial domain transmit (Tx) filter. In one example, in response to the higher layer parameter spatialRelationInfo indicating that the reference RS (e.g., by the ID of the reference RS) is an SRS, the wireless device may transmit the target SRS resource using a spatial domain transmit (Tx) filter.

[0241] In one embodiment, the base station may activate and deactivate one or more configured SRS resource sets (e.g., semi-persistent SRS resource sets) of the serving cell by transmitting an SP SRS Activation / Deactivation MAC CE. In one embodiment, the one or more configured SRS resource sets may be initially deactivated upon configuration. In one embodiment, the one or more configured SRS resource sets may be deactivated after handover.

[0242] In one embodiment, a base station may configure a wireless device with one or more SRS resource sets (e.g., semi-persistent SRS resource sets). In one embodiment, the upper layer parameter resourceType in the upper layer parameter SRS resource may be set to "semi-persistent". In one embodiment, the wireless device may receive an activation command (e.g., SP SRS Activation / Deactivation MAC CE) for an SRS resource set of the one or more SRS resource sets from the base station. In one embodiment, a PDSCH may carry the activation command. In one embodiment, the wireless device may transmit a HARQ-ACK for the PDSCH in slot n. In one embodiment, in response to transmitting a HARQ-ACK for the PDSCH in slot n, the wireless device

number

[0243] In one embodiment, a Resource Serving Cell ID field indicating the serving cell may be present in the activation command. In one embodiment, the reference RS may be an SS / PBCH block resource or an NZP CSI-RS resource. In response to the Resource Serving Cell ID field being present and the reference RS being an SS / PBCH block resource or an NZP CSI-RS resource, the reference RS (e.g., SS / PBCH block, NZP CSI-RS resource) may be configured on the serving cell.

[0244] In one embodiment, the base station may configure (activated) an SRS resource set on the serving cell. In one embodiment, the Resource Serving Cell ID field may not be present in the activation command. In response to the absence of the Resource Serving Cell ID field and the base station configuring an SRS resource set on the serving cell, reference RSs (e.g., SS / PBCH blocks, NZP CSI-RS resources) may be configured on the serving cell.

[0245] In one embodiment, a Resource Serving Cell ID field indicating a serving cell and a Resource BWP ID field indicating an uplink BWP may be present in the activation command. In response to the presence of the Resource Serving Cell ID field and the Resource BWP ID field, a reference RS (e.g., an SRS resource) may be configured on the uplink BWP of the serving cell.

[0246] In one embodiment, the base station may configure an SRS resource set on the uplink BWP of the serving cell. In one embodiment, the Resource Serving Cell ID field and the Resource BWP ID field may not be present in the activation command. In response to the Resource Serving Cell ID field and the Resource BWP ID field being absent and an SRS resource set being configured on the uplink BWP of the serving cell, a reference RS (e.g., an SRS resource) may be configured on the uplink BWP of the serving cell.

[0247] In one example, the base station may configure an SRS resource in the (activated) SRS resource set using the higher layer parameter spatialRelationInfo. In response to the SRS resource being configured in the (activated) SRS resource set using the higher layer parameter spatialRelationInfo, the wireless device may assume that the reference RS (e.g., indicated by the ID of the reference RS) in the activation command overrides the second reference RS configured in the higher layer parameter spatialRelationInfo.

[0248] In one embodiment, the wireless device may receive a deactivation command (e.g., SP SRS Activation / Deactivation MAC CE) for one or more (activated) SRS resource sets from the base station. In one embodiment, the PDSCH may carry the deactivation command. In one embodiment, the wireless device may transmit a HARQ-ACK for the PDSCH in slot n. In one embodiment, in response to transmitting a HARQ-ACK for the PDSCH in slot n, the wireless device transmits a HARQ-ACK for the PDSCH in slot n.

number

[0249] In one embodiment, the wireless device may activate the semi-persistent SRS resource configuration on the uplink BWP of the serving cell in response to receiving an activation command for the semi-persistent SRS resource configuration from the base station. In one embodiment, the wireless device may not receive a deactivation command for the semi-persistent SRS resource configuration from the base station.

[0250] In one embodiment, the uplink BWP may be the active uplink BWP of the serving cell. In one embodiment, in response to the uplink BWP being the active uplink BWP of the serving cell and not receiving a deactivation command for the semi-persistent SRS resource configuration, the wireless device may consider the semi-persistent SRS resource configuration active. In one embodiment, in response to the consideration, the wireless device may transmit SRS transmissions over the uplink BWP of the serving cell in accordance with the semi-persistent SRS resource configuration.

[0251] In one embodiment, the uplink BWP may not be the active uplink BWP of the serving cell. In one embodiment, the uplink BWP not being the active uplink BWP may include the uplink BWP being deactivated in the serving cell. In response to not receiving a deactivation command for the semi-persistent SRS resource configuration and the uplink BWP being deactivated, the wireless device may assume that the semi-persistent SRS configuration is suspended in the UL BWP of the serving cell. In one embodiment, the semi-persistent SRS configuration being suspended in the UL BWP may include the wireless device reactivating the semi-persistent SRS configuration when the UL BWP becomes the active UL BWP of the serving cell.

[0252] In one example, a first SRS resource of an SRS resource set may have a first time-domain behavior (e.g., periodic, semi-persistent, aperiodic, etc.). In one example, a second SRS resource of an SRS resource set may have a second time-domain behavior (e.g., periodic, semi-persistent, aperiodic, etc.). In one example, in response to the first SRS resource and the second SRS resource being in the (same) SRS resource set, the wireless device may expect the first time-domain behavior and the second time behavior to be the same. In one example, in response to the first SRS resource and the second SRS resource being in the (same) SRS resource set, the wireless device may not expect the first time-domain behavior and the second time behavior to be different.

[0253] In one example, an SRS resource of an SRS resource set may have a first time-domain behavior (e.g., periodic, semi-persistent, aperiodic, etc.). In one example, an SRS resource set may have a second time-domain behavior (e.g., periodic, semi-persistent, aperiodic, etc.). In one example, in response to an SRS resource being associated with an SRS resource set, the wireless device may expect the first time-domain behavior and the second time-domain behavior to be the same. In one example, in response to an SRS resource being associated with an SRS resource set, the wireless device may expect the first time-domain behavior and the second time-domain behavior to be different. In one example, associating an SRS resource with an SRS resource set may include the SRS resource set including the SRS resource. In one example, associating an SRS resource with an SRS resource set may include the SRS resource being an element of the SRS resource set.

[0254] In one embodiment, a base station may configure a wireless device with a PUCCH on at least one first symbol on a carrier (e.g., SUL, NUL). In one embodiment, the PUCCH may carry / include one or more CSI reports. In one embodiment, the PUCCH may carry / include one or more L1-RSRP reports. In one embodiment, the PUCCH may carry / include HARQ-ACK and / or SR. In one embodiment, a base station may configure a wireless device with an SRS configuration on the carrier. In one embodiment, the SRS configuration may be a semi-persistent SRS configuration. In one embodiment, the SRS configuration may be a periodic SRS configuration. In one embodiment, a wireless device may determine that SRS transmissions of the PUCCH and the SRS configuration overlap by at least one symbol. In one embodiment, a wireless device may determine that at least one first symbol of the PUCCH and at least one second symbol of an SRS transmission of the SRS configuration may overlap by at least one symbol. In one embodiment, in response to determining, the wireless device may not perform an SRS transmission on the carrier on at least one symbol.

[0255] In one embodiment, the base station may configure the wireless device with a PUCCH on at least one first symbol on a carrier (e.g., SUL, NUL). In one embodiment, the PUCCH may carry / include HARQ-ACK and / or SR. In one embodiment, the base station may trigger an SRS configuration on the carrier. In one embodiment, the SRS configuration may be an aperiodic SRS configuration. In one embodiment, the wireless device may determine that SRS transmissions of the PUCCH and the SRS configuration overlap by at least one symbol. In one embodiment, the wireless device may determine that at least one first symbol of the PUCCH and at least one second symbol of the SRS transmission of the SRS configuration may overlap by at least one symbol. In one embodiment, in response to determining, the wireless device may not perform an SRS transmission on the carrier on the at least one symbol.

[0256] In one embodiment, not transmitting the SRS may include dropping the SRS transmission on at least one symbol. In one embodiment, the wireless device may transmit the SRS transmission on at least one third symbol of the at least one second symbol. The at least one third symbol may not overlap with the at least one symbol.

[0257] In one embodiment, the base station may configure the wireless device with a PUCCH on at least one first symbol on a carrier (e.g., SUL, NUL). In one embodiment, the PUCCH may carry / include one or more semi-persistent CSI reports. In one embodiment, the PUCCH may carry / include one or more periodic CSI reports. In one embodiment, the PUCCH may carry / include one or more semi-persistent L1-RSRP reports. In one embodiment, the PUCCH may carry / include one or more periodic L1-RSRP reports. In one embodiment, the base station may trigger an SRS configuration on the carrier. In one embodiment, the SRS configuration may be an aperiodic SRS configuration. In one embodiment, the wireless device may determine that SRS transmissions of the PUCCH and the SRS configuration overlap by at least one symbol. In one embodiment, the wireless device may determine that at least one first symbol of the PUCCH and at least one second symbol of the SRS transmission of the SRS configuration are aperiodic SRS configurations may overlap by at least one symbol. In one embodiment, in response to determining, the wireless device may not transmit the PUCCH on the carrier on the at least one symbol.

[0258] In one embodiment, in intra-band carrier aggregation (CA) or intra-band CA band-band combination, the wireless device may not simultaneously transmit SRS and PUCCH / PUSCH. In one embodiment, in response to not simultaneously transmitting SRS and PUCCH / PUSCH, the base station may not configure the wireless device with SRS transmission from the first carrier and PUCCH / PUSCH (e.g., PUSCH / UL DM-RS / UL PT-RS / PUCCH format) on the second carrier in the same symbol. In one embodiment, the first carrier may be different from the second carrier.

[0259] In one embodiment, in intra-band carrier aggregation (CA) or intra-band CA band-band combination, the wireless device may not simultaneously transmit the SRS and the PRACH. In one embodiment, in response to not simultaneously transmitting the SRS and the PRACH, the wireless device may not simultaneously transmit the SRS from the first carrier and the PRACH from the second carrier. In one embodiment, the first carrier may be different from the second carrier.

[0260] In one embodiment, a base station may configure a wireless device with periodic SRS transmission on at least one symbol (e.g., OFDM symbol). In one embodiment, a base station may configure SRS resources with the higher layer parameter resourceType set as "aperiodic." In one embodiment, a base station may trigger SRS resources on at least one symbol. In one embodiment, in response to SRS resources being triggered with periodic SRS transmission on at least one symbol configured with the higher layer parameter resourceType set as "aperiodic," a wireless device may transmit (aperiodic) SRS resources on at least one (overlapped) symbol. In one embodiment, in response to SRS resources being triggered with periodic SRS transmission on at least one symbol configured with the higher layer parameter resourceType set as "aperiodic," a wireless device may not perform periodic SRS transmission on at least one symbol. In one example, not performing periodic SRS transmission may include the wireless device not transmitting an SRS associated with the periodic SRS transmission on at least one (overlapping) symbol.

[0261] In one embodiment, a base station may configure a wireless device with semi-persistent SRS transmission on at least one symbol (e.g., an OFDM symbol). In one embodiment, a base station may configure SRS resources with the higher layer parameter resourceType set as “aperiodic.” In one embodiment, a base station may trigger SRS resources on at least one symbol. In one embodiment, in response to SRS resources being triggered on at least one symbol configured with semi-persistent SRS transmission with the higher layer parameter resourceType set as “aperiodic,” a wireless device may transmit (aperiodic) SRS resources on at least one (overlapped) symbol. In one embodiment, in response to SRS resources being triggered on at least one symbol configured with semi-persistent SRS transmission with the higher layer parameter resourceType set as “aperiodic,” a wireless device may not perform semi-persistent SRS transmission on the at least one symbol. In one example, not performing a semi-persistent SRS transmission may include that the wireless device may not transmit an SRS associated with the semi-persistent SRS transmission on at least one (overlapping) symbol.

[0262] In one embodiment, a base station may configure a wireless device with periodic SRS transmission on at least one symbol (e.g., OFDM symbol). In one embodiment, a base station may configure SRS resources with the higher layer parameter resourceType set as "semi-persistent". In one embodiment, a base station may trigger SRS resources on at least one symbol. In one embodiment, in response to SRS resources being triggered with periodic SRS transmission on at least one symbol configured with the higher layer parameter resourceType set as "semi-persistent", a wireless device may transmit the (semi-persistent) SRS resources on at least one (overlapped) symbol. In one embodiment, in response to SRS resources being triggered with periodic SRS transmission on at least one symbol configured with the higher layer parameter resourceType set as "semi-persistent", a wireless device may not perform periodic SRS transmission on at least one symbol. In one example, not performing periodic SRS transmission may include the wireless device not transmitting an SRS associated with the periodic SRS transmission on at least one (overlapping) symbol.

[0263] In one embodiment, a wireless device may be configured with one or more serving cells by a base station. In one embodiment, the base station may activate one or more secondary serving cells of the one or more serving cells. In one embodiment, the base station may configure each activated serving cell of the one or more secondary serving cells with a respective PDCCH monitor. In one embodiment, the wireless device may monitor a set of PDCCH candidates in one or more CORESETs on the active DL BWP of each activated serving cell configured with the respective PDCCH monitor. In one embodiment, the wireless device may monitor a set of PDCCH candidates in one or more CORESETs according to a corresponding search space set. In one embodiment, the monitoring may include decoding each PDCCH candidate of the set of PDCCH candidates according to the monitored DCI format.

[0264] In one embodiment, the set of PDCCH candidates for a wireless device to monitor may be defined in terms of a PDCCH search space set, which may be a common search space (CSS) set or a UE-specific search space (USS) set.

[0265] In one embodiment, one or more PDCCH monitoring opportunities may be associated with an SS / PBCH block. In one embodiment, the SS / PBCH block may be quasi-co-located with the CSI-RS. In one embodiment, the TCI state of an active BWP may include the CSI-RS. In one embodiment, the active BWP may include a CORESET identified by an index equal to zero (e.g., CORESET zero, or CORESET#0, etc.). In one embodiment, the wireless device may determine the TCI state by an indicator from a MAC-CE activation command or the most recent random access procedure not initiated by a PDCCH command that triggers a non-contention-based random access procedure. In one embodiment, for a DCI format having a CRC scrambled by the C-RNTI, the wireless device may monitor corresponding PDCCH candidates in one or more PDCCH monitoring opportunities in response to one or more PDCCH monitoring opportunities being associated with the SS / PBCH block.

[0266] In one embodiment, a base station may configure a wireless device with one or more DL BWPs in a serving cell. In one embodiment, for one or more DL BWPs, the wireless device may provide one or more (e.g., two or three) control resource sets (CORESETs) to the wireless device via higher layer signaling. For a CORESET among the one or more CORESETs, the base station may provide, via higher layer parameter ControlResourceSet, a CORESET index (e.g., provided by higher layer parameter controlResourceSetId), a DMRS scrambling sequence initialization value (e.g., provided by higher layer parameter pdcch-DMRS-ScramblingID), a number of consecutive symbols (e.g., provided by higher layer parameter duration), a set of resource blocks (e.g., provided by higher layer parameter frequencyDomainResources and (e.g., provided by the upper layer parameter TCI-PresentInDCI), a CCE-to-REG mapping parameter (e.g., provided by the higher layer parameter cce-REG-MappingType), a quasi-coordinated location of antenna ports (e.g., from a set of quasi-coordinated locations of antenna ports provided by the first higher layer parameter tci-StatesPDCCH-ToAddList and the second higher layer parameter tci-StatesPDCCH-ToReleaseList), and an indicator for the presence or absence of a TCI (e.g., transmission configuration indicator, etc.) field for a DCI format (e.g., DCI format 1_1) carried by the PDCCH in the CORESET (e.g., provided by the higher layer parameter TCI-PresentInDCI). In one embodiment, the quasi-coordinated location of antenna ports may indicate quasi-coordinated location information of one or more DM-RS antenna ports for PDCCH reception in the CORESET. In one embodiment, the CORESET index may be unique among one or more DL BWPs of the serving cell.In one embodiment, if the higher layer parameter TCI-PresentInDCI is not present, the wireless device may assume that the TCI field is absent / disabled in the DCI format.

[0267] In one example, the first higher layer parameter tci-StatesPDCCH-ToAddList and the second higher layer parameter tci-StatesPDCCH-ToReleaseList may provide a subset of the TCI states defined in pdsch-Config. In one example, the wireless device may use the subset of TCI states to provide one or more QCL relationships between one or more RSs in the TCI states of the subset of TCI states and one or more DM-RS ports of PDCCH reception in the CORESET.

[0268] In one embodiment, the base station may configure a CORESET for the wireless device. In one embodiment, the CORESET index (e.g., provided by the upper layer parameter controlResourceSetId) of the CORESET may not be zero. In one embodiment, the base station may not provide the wireless device with configuration of one or more TCI states for the CORESET via the first upper layer parameter tci-StatesPDCCH-ToAddList and / or the second upper layer parameter tci-StatesPDCCH-ToReleaseList. In one embodiment, in response to not providing configuration of one or more TCI states for the CORESET, the wireless device may assume that one or more DMRS antenna ports for PDCCH reception within the CORESET are quasi-co-located with the RS (e.g., SS / PBCH block). In one embodiment, the wireless device may identify the RS during the initial access procedure.

[0269] In one embodiment, a base station may configure a CORESET for a wireless device. In one embodiment, the CORESET index (e.g., provided by the upper layer parameter controlResourceSetId) of the CORESET may not be zero. In one embodiment, the base station may provide an initial configuration of at least two TCI states to the wireless device for the CORESET via the first upper layer parameter tci-StatesPDCCH-ToAddList and / or the second upper layer parameter tci-StatesPDCCH-ToReleaseList. In one embodiment, the wireless device may receive an initial configuration of at least two TCI states from the base station. In one embodiment, the wireless device may not receive a MAC CE activation command for at least one of the at least two TCI states for the CORESET. In one embodiment, in response to being provided with an initial configuration for the CORESET and not receiving a MAC CE activation command for the CORESET, the wireless device may assume that one or more DMRS antenna ports for PDCCH reception within the CORESET are quasi-co-located with the RS (e.g., SS / PBCH block). In one embodiment, the wireless device may identify the RS during the initial access procedure.

[0270] In one embodiment, the base station may configure a CORESET for the wireless device. In one embodiment, the CORESET index (e.g., provided by the higher layer parameter controlResourceSetId) of the CORESET may be equal to zero. In one embodiment, the wireless device may not receive a MAC CE activation command for the TCI state of the CORESET. In response to not receiving a MAC CE activation command, the wireless device may assume that one or more DMRS antenna ports for PDCCH reception in the CORESET are quasi-co-located with the RS (e.g., SS / PBCH block). In one embodiment, the wireless device may identify the RS during an initial access procedure. In one embodiment, the wireless device may identify the RS from a most recent random access procedure. In one embodiment, the wireless device may not initiate a most recent random access procedure in response to receiving a PDCCH command triggering a non-contention-based random access procedure.

[0271] In one embodiment, a base station may provide a wireless device with a single TCI state for CORESET. In one embodiment, the base station may provide the single TCI state via a first upper layer parameter tci-StatesPDCCH-ToAddList and / or a second upper layer parameter tci-StatesPDCCH-ToReleaseList. In response to providing a single TCI state for CORESET, the wireless device may assume that one or more DM-RS antenna ports for PDCCH reception in CORESET are quasi-co-located with one or more DL RSs configured by the single TCI state.

[0272] In one embodiment, a base station may configure a CORESET for a wireless device. In one embodiment, the base station may provide the wireless device with a configuration of at least two TCI states for the CORESET via a first upper layer parameter tci-StatesPDCCH-ToAddList and / or a second upper layer parameter tci-StatesPDCCH-ToReleaseList. In one embodiment, the wireless device may receive the configuration of at least two TCI states from the base station. In one embodiment, the wireless device may receive a MAC-CE activation command for at least one of the at least two TCI states in the CORESET. In response to receiving the MAC-CE activation command for at least one of the at least two TCI states, the wireless device may assume that one or more DM-RS antenna ports for PDCCH reception in the CORESET are quasi-co-located with one or more DL RSs configured by at least one of the at least two TCI states.

[0273] In one embodiment, a base station may configure a CORESET for a wireless device. In one embodiment, a CORESET index (e.g., provided by the higher layer parameter controlResourceSetId) of the CORESET may be equal to zero. In one embodiment, a base station may provide a configuration of at least two TCI states for the CORESET to a wireless device. In one embodiment, a wireless device may receive a configuration of at least two TCI states from a base station. In one embodiment, a wireless device may receive a MAC CE activation command for at least one of the at least two TCI states of the CORESET. In one embodiment, in response to the CORESET index being equal to zero, the wireless device may expect a QCL type (e.g., QCL-Type D) of a first RS (e.g., CSI-RS) in at least one of the at least two TCI states to be provided by a second RS (e.g., SS / PBCH block). In one example, in response to the CORESET index being equal to zero, the wireless device may expect that the QCL type (e.g., QCL-type D) of the first RS (e.g., CSI-RS) in at least one of the at least two TCI states is spatially QCL-ed with the second RS (e.g., SS / PBCH block).

[0274] In one embodiment, the wireless device may receive a MAC CE activation command for at least one of the at least two TCI states for CORESET. In one embodiment, the PDSCH may provide the MAC CE activation command. In one embodiment, the wireless device may transmit HARQ-ACK information for the PDSCH in the slot. In one embodiment, when the wireless device receives a MAC CE activation command for at least one of the at least two TCI states for CORESET, in response to the transmission of the HARQ-ACK information in the slot, the wireless device may apply a MAC CE activation command X milliseconds (e.g., 3 milliseconds, 5 milliseconds) after the slot. In one embodiment, when the wireless device applies a MAC CE activation command in a second slot, the first BWP may be active in the second slot. In response to the first BWP being active in the second slot, the first BWP may be an active BWP.

[0275] In one embodiment, a base station can configure a wireless device with one or more DL BWPs in a serving cell. In one embodiment, for one or more DL BWPs, the wireless device can be provided by higher layers with one or more (e.g., 3, 5, 10) search space sets. In one embodiment, for a search space set of one or more search space sets, the wireless device may be provided by the higher layer parameter SearchSpace with at least one of: a search space set index (e.g., provided by the higher layer parameter searchSpaceId), an association between the search space set and a CORESET (e.g., provided by the higher layer parameter controlResourceSetId), a PDCCH monitoring periodicity of a first number of slots and a PDCCH monitoring offset of a second number of slots (e.g., provided by the higher layer parameter monitoringSlotPeriodicityAndOffset), a PDCCH monitoring pattern within a slot indicating a first symbol of a CORESET within a slot for PDCCH monitoring (e.g., provided by the higher layer parameter monitoringSymbolsWithinSlot), a period of a third number of slots (e.g., provided by the higher layer parameter period), a number of PDCCH candidates, and an indication that the search space set is either a common search space set or a UE-specific search space set (e.g., provided by the higher layer parameter searchSpaceType). In one embodiment, the period may indicate a number of slots in which the search space set may reside.

[0276] In one embodiment, the wireless device may not expect two PDCCH monitoring opportunities on an active DL BWP for the same or different search space sets in the same CORESET to be separated by a non-zero number of symbols less than the CORESET duration.

[0277] In one embodiment, the wireless device may determine a PDCCH monitoring opportunity on the active DL BWP based on the PDCCH monitoring periodicity, the PDCCH monitoring offset, and the PDCCH monitoring pattern within the slot. In one embodiment, for a search space set, the wireless device may determine that a PDCCH monitoring opportunity exists in the slot. In one embodiment, the wireless device may monitor at least one PDCCH for the search space set for a duration of a third number of slots starting from the slot (consecutively).

[0278] In one embodiment, the wireless device may monitor one or more PDCCH candidates in a UE-specific search space (USS) set on the serving cell's active DL BWP. In one embodiment, the base station may not configure the wireless device with a carrier indicator field. In response to not being configured with the carrier indicator field, the wireless device may monitor one or more PDCCH candidates without the carrier indicator field.

[0279] In one embodiment, the wireless device may monitor one or more PDCCH candidates in a USS set on an active DL BWP of a serving cell. In one embodiment, the base station may configure the wireless device with a carrier indicator field. In response to being configured with the carrier indicator field, the wireless device may monitor one or more PDCCH candidates having the carrier indicator field.

[0280] In one example, a base station may configure a wireless device to monitor one or more PDCCH candidates having a carrier indicator field in a first cell. In one example, the carrier indicator field may indicate a second cell. In one example, the carrier indicator field may correspond to the second cell. In response to monitoring the one or more PDCCH candidates in the first cell with the carrier indicator field indicating the second cell, the wireless device may not expect to monitor one or more PDCCH candidates on an active DL BWP of the second cell.

[0281] In one example, the wireless device may monitor one or more PDCCH candidates on an active DL BWP of the serving cell. In response to monitoring one or more PDCCH candidates on the active DL BWP of the serving cell, the wireless device may monitor one or more PDCCH candidates for the serving cell.

[0282] In one embodiment, the wireless device may monitor one or more PDCCH candidates on an active DL BWP of the serving cell. In response to monitoring one or more PDCCH candidates on the active DL BWP of the serving cell, the wireless device may monitor at least one PDCCH candidate for the serving cell. In one embodiment, the wireless device may monitor one or more PDCCH candidates for the serving cell and at least a second serving cell.

[0283] In one embodiment, a base station can configure a wireless device with one or more cells. In one embodiment, when the number of the one or more cells is one, the base station can configure the wireless device for single-cell operation. In one embodiment, when the number of the one or more cells is greater than one, the base station can configure the wireless device for operation with carrier aggregation in the same frequency band (e.g., intra-band).

[0284] In one embodiment, a wireless device may monitor one or more PDCCH candidates in multiple CORESETs on an active DL BWP of one or more cells in overlapping PDCCH monitoring opportunities. In one embodiment, the multiple CORESETs may have different QCL-Type D characteristics.

[0285] In one example, a first PDCCH monitoring opportunity in a first CORESET of the multiple CORESETs of a first cell of the one or more cells may overlap with a second PDCCH monitoring opportunity in a second CORESET of the multiple CORESETs of the first cell. In one example, the wireless device may monitor at least one first PDCCH candidate in the first PDCCH monitoring opportunity on an active downlink BWP of the first cell. In one example, the wireless device may monitor at least one second PDCCH candidate in the second PDCCH monitoring opportunity on an active downlink BWP of the first cell.

[0286] In one example, a first PDCCH monitoring opportunity in a first CORESET of the multiple CORESETs for a first cell of the one or more cells may overlap with a second PDCCH monitoring opportunity in a second CORESET of the multiple CORESETs for a second cell of the one or more cells. In one example, the wireless device may monitor at least one first PDCCH candidate in a first PDCCH monitoring opportunity on a first active DL BWP of an active DL BWP of the first cell. In one example, the wireless device may monitor at least one second PDCCH candidate in a second PDCCH monitoring opportunity on a second active DL BWP of an active DL BWP of the second cell.

[0287] In one embodiment, a first QCL type characteristic (eg, QCL-type D) of a first CORESET may be different from a second QCL type characteristic (eg, QCL-type D) of a second CORESET.

[0288] In one example, in response to monitoring one or more PDCCH candidates in overlapping PDCCH monitoring opportunities in multiple CORESETs for a CORESET determination rule and the multiple CORESETs having different QCL-Type D characteristics, the wireless device may determine a selected CORESET among the multiple CORESETs for a cell of one or more cells. In one example, in response to the determination, the wireless device may monitor at least one PDCCH candidate in overlapping PDCCH monitoring opportunities in the selected CORESET on an active DL BWP of the cell. In one example, the selected CORESET may be associated with a search space set (e.g., an association provided by a higher layer parameter controlResourceSetId).

[0289] In one embodiment, one or more CORESETs of the plurality of CORESETs may be associated with a common search space (CSS) set. In one embodiment, associating one or more CORESETs of the plurality of CORESETs with a CSS set may include at least one search space set of a CORESET of the one or more CORESETs (e.g., an association between at least one search space set and a CORESET provided by a higher layer parameter controlResourceSetId) having at least one PDCCH candidate in an overlapping PDCCH monitoring opportunity and / or in a CSS set.

[0290] In one embodiment, a first CORESET may be associated with a first CSS set. In one embodiment, a first CORESET may be associated with a first USS set. In one embodiment, a second CORESET may be associated with a second CSS set. In one embodiment, a second CORESET may be associated with a second USS set. In one embodiment, associating a CORESET (e.g., first CORESET, second CORESET) with a CSS set (e.g., first CSS set, second CSS set) may include at least one search space of the CORESET being a CSS set. In one embodiment, associating a CORESET (e.g., first CORESET, second CORESET) with a USS set (e.g., first USS set, second USS set) may include at least one search space of the CORESET being a USS set.

[0291] In one embodiment, the one or more CORESETs may include a first CORESET and a second CORESET, where a first CORESET is associated with a first CSS set and a second CORESET is associated with a second CSS set.

[0292] In one embodiment, when the one or more CORESETs include a first CORESET and a second CORESET, the one or more selected cells may include the first cell and the second cell in response to the first CORESET being configured in the first cell and the second CORESET being configured in the second cell.

[0293] In one example, if the one or more CORESETs include a first CORESET and a second CORESET, the one or more selected cells may include the first cell in response to the first CORESET being configured in the first cell and the second CORESET being configured in the first cell. In one example, at least one CORESET may include the first CORESET and the second CORESET. In one example, a first search space set of the first CORESET of the at least one CORESET may be identified by a unique index of the first search space set (e.g., provided by the higher layer parameter searchSpaceId). In one example, the wireless device may monitor at least one first PDCCH candidate in a first PDCCH monitoring opportunity in a first CORESET associated with the first search space set (e.g., an association provided by the higher layer parameter controlResourceSetId). In one embodiment, a second search space set of a second CORESET of the at least one CORESET may be identified by a unique index of the second search space set (e.g., provided by the higher layer parameter searchSpaceId). In one embodiment, the wireless device may monitor at least one second PDCCH candidate in a second PDCCH monitoring opportunity in a second CORESET associated with the second search space set (e.g., an association provided by the higher layer parameter controlResourceSetId). In one embodiment, the unique index of the first search space set may be lower than the unique index of the second search space set. In response to the unique index of the first search space set being lower than the unique index of the second search space set, for the CORESET decision rule, the wireless device may select the first search space set. In one embodiment, in response to the selection, for the CORESET decision rule, the wireless device may monitor at least one first PDCCH candidate in a first PDCCH monitoring opportunity in the first CORESET on the active DL BWP of the first cell.In one example, in response to the selection, for a CORESET decision rule, the wireless device may stop monitoring at least one second PDCCH candidate in a second PDCCH monitoring opportunity in a second CORESET on the active DL BWP of the first cell. In one example, in response to the selection, the wireless device may drop monitoring at least one second PDCCH candidate in a second PDCCH monitoring opportunity in the second CORESET on the active DL BWP of the first cell.

[0294] In one embodiment, the first cell may be identified by a first cell-specific index. In one embodiment, the second cell may be identified by a second cell-specific index. In one embodiment, the first cell-specific index may be lower than the second cell-specific index. In one embodiment, when the one or more selected cells include the first cell and the second cell, the wireless device may select the first cell in response to the first cell-specific index being lower than the second cell-specific index.

[0295] In one embodiment, if the first CORESET is associated with a first CSS set and the second CORESET is associated with a second USS set, the one or more CORESETs may include the first CORESET. In one embodiment, if the one or more CORESETs include the first CORESET, the one or more selected cells may include the first cell in response to the first CORESET being configured in the first cell.

[0296] In one embodiment, if a first CORESET is associated with a first USS set and a second CORESET is associated with a second CSS set, the one or more CORESETs may include the second CORESET. In one embodiment, if the one or more CORESETs include the second CORESET, the one or more selected cells may include the first cell in response to the second CORESET being configured in the first cell. In one embodiment, if the one or more CORESETs include the second CORESET, the one or more selected cells may include the second cell in response to the second CORESET being configured in the second cell.

[0297] In one embodiment, the wireless device may determine that one or more CORESETs are associated with one or more selected cells of the one or more cells. In one embodiment, the base station may configure a first CORESET of the one or more CORESETs in a first cell of the one or more selected cells. In one embodiment, the base station may configure a second CORESET of the one or more CORESETs in the first cell. In one embodiment, the base station may configure a third CORESET of the one or more CORESETs in a second cell of the one or more selected cells. In one embodiment, the first cell and the second cell may be different.

[0298] In one embodiment, the wireless device may receive one or more configuration parameters from a base station. The one or more configuration parameters may indicate cell-specific indexes (e.g., provided by a higher layer parameter servCellIndex) for one or more cells. In one embodiment, each cell of the one or more cells may be identified by a respective one of the cell-specific indexes. In one embodiment, the cell-specific index of the one or more selected cells may be the lowest among the cell-specific indexes of the one or more selected cells.

[0299] In one embodiment, if the wireless device determines that one or more CORESETs are associated with one or more selected cells of the one or more cells, for a CORESET determination rule, the wireless device may select a cell in response to a cell-specific index of the cell that is lowest among the cell-specific indexes of the one or more selected cells.

[0300] In one embodiment, the base station may configure at least one CORESET of one or more CORESETs in a (selected) cell, where at least one search space set of the at least one CORESET may have at least one PDCCH candidate in an overlapping PDCCH monitoring opportunity and / or may be a CSS set.

[0301] In one embodiment, the one or more configuration parameters may indicate a search space set-specific index (e.g., provided by the higher layer parameter searchSpaceId) for at least one search space set of the cell. In one embodiment, each search space set of the at least one search space set may be identified by a search space set-specific index for each of the search space set's unique indices. In one embodiment, the wireless device may determine that the search space set's search space-specific index of the at least one search space set is lowest among the search space set-specific indices of the at least one search space set. In response to determining that the search space set's unique index is lowest among the search space set's unique indices of the at least one search space set, for a CORESET determination rule, the wireless device may select a search space set. In one embodiment, the search space set may be associated with the selected CORESET of the at least one CORESET (e.g., association provided by the higher layer parameter controlResourceSetId).

[0302] In one embodiment, when a wireless device monitors one or more PDCCH candidates at overlapping PDCCH monitoring opportunities in multiple CORESETs and the multiple CORESETs have different QCL-Type D characteristics, the wireless device may monitor at least one PDCCH in a selected CORESET of the multiple CORESETs on an active DL BWP of one or more cells in response to selecting a cell and / or selecting a search space set associated with the selected CORESET. In one embodiment, the wireless device may select a selected CORESET associated with a cell of the search space set and CORESET decision rule.

[0303] In one embodiment, the selected CORESET may have a first QCL-Type D characteristic. In one embodiment, a second CORESET of the plurality of CORESETs may have a second QCL-Type D characteristic. In one embodiment, the selected CORESET and the second CORESET may be different.

[0304] In one example, the first QCL-Type D characteristic and the second QCL-Type D characteristic may be the same. In one example, the wireless device may monitor at least one second PDCCH candidate in a second CORESET of the multiple CORESETs (in an overlapping PDCCH monitoring opportunity) in response to the first QCL-Type D characteristic of the selected CORESET and the second QCL-Type D characteristic of the second CORESET being the same.

[0305] In one embodiment, the first QCL-Type D characteristic and the second QCL-Type D characteristic may be different. In one embodiment, the wireless device may stop monitoring at least one second PDCCH candidate (in the overlapping PDCCH monitoring opportunity) in a second CORESET of the multiple CORESETs in response to the first QCL-Type D characteristic of the selected CORESET and the second QCL-Type D characteristic of the second CORESET being different. In one embodiment, the wireless device may drop monitoring at least one second PDCCH candidate (in the overlapping PDCCH monitoring opportunity) in a second CORESET of the multiple CORESETs in response to the first QCL-Type D characteristic of the selected CORESET and the second QCL-Type D characteristic of the second CORESET being different.

[0306] In one embodiment, for the CORESET decision rule, the wireless device may consider that the first QCL type (e.g., QCL Type D) characteristics of the first RS (e.g., SS / PBCH block) are different from the second QCL type (e.g., QCL Type D) characteristics of the second RS (CSI-RS).

[0307] In one example, for a CORESET decision rule, a first RS (e.g., a CSI-RS) may be associated (e.g., QCL-ed) with an RS (e.g., an SS / PBCH block) in a first cell. In one example, a second RS (e.g., a CSI-RS) may be associated (e.g., QCL-ed) with an RS in a second cell. In response to the first RS and the second RS being associated with the RS, the wireless device may consider the first QCL type (e.g., QCL Type D) characteristics of the first RS and the second QCL type (e.g., QCL Type D) characteristics of the second RS to be the same.

[0308] In one embodiment, the wireless device may determine several active TCI states from multiple CORESETs.

[0309] In one embodiment, a wireless device may monitor multiple search space sets associated with different CORESETs for one or more cells (e.g., single-cell operation or operation with carrier aggregation in the same frequency band). In one embodiment, at least two monitoring occasions of at least two search space sets of the multiple search space sets may overlap in time (e.g., by at least one symbol, at least one slot, subframe, etc.). In one embodiment, the at least two search space sets may be associated with at least two first CORESETs. The at least two first CORESETs may have different QCL-Type D characteristics. In one embodiment, for a CORESET decision rule, the wireless device may monitor at least one search space set associated with a selected CORESET in an active DL BWP of the cell. In one embodiment, at least one search space set may be a CSS set. In one embodiment, the cell-specific index of a cell may be the lowest of the cell-specific indexes of one or more cells that include the cell. In one embodiment, at least two second CORESETs of a cell may include a CSS set. In response to the at least two second CORESETs of the cell including the CSS set, the wireless device may select a selected CORESET of the at least two second CORESETs in response to a search space-specific index of the search space set associated with the selected CORESET being the lowest among the search space-specific indices of the search space sets associated with the at least two second CORESETs. In one embodiment, the wireless device may monitor the search space set in at least two monitoring occasions.

[0310] In one embodiment, the wireless device may determine that the at least two first CORESETs may not be associated with a CSS set. In one embodiment, the wireless device may determine that each CORESET of the at least two first CORESETs may not be associated with a CSS set. In one embodiment, for a CORESET determination rule, in response to the determination, the wireless device may monitor at least one search space set associated with the selected CORESET in an active DL BWP of the cell. In one embodiment, the at least one search space set may be a USS set. In one embodiment, the cell-specific index of the cell may be lowest among the cell-specific indices of one or more cells including the cell. In one embodiment, at least two second CORESETs of the cell may include a USS set. In response to the at least two second CORESETs of the cell including a USS set, the wireless device may select a selected CORESET of the at least two second CORESETs in response to the search space-specific index of the search space set associated with the selected CORESET being lowest among the search space-specific indices of the search space sets associated with the at least two second CORESETs. In one embodiment, the wireless device monitors the search space set in at least two monitoring occasions.

[0311] In one embodiment, the base station may indicate to the wireless device the TCI status for PDCCH reception for the CORESET of the serving cell by transmitting a TCI status indicator for the UE-specific PDCCH MAC CE. In one embodiment, when the MAC entity of the wireless device receives a TCI status indicator for the UE-specific PDCCH MAC CE on / for the serving cell, the MAC entity may indicate information regarding the TCI status indicator for the UE-specific PDCCH MAC CE to lower layers (e.g., PHY).

[0312] In one embodiment, the TCI status indicator for the UE-specific PDCCH MAC CE may be identified by a MAC PDU subheader with an LCID. The TCI status indicator for the UE-specific PDCCH MAC CE may have a fixed size of 16 bits and include one or more fields. In one embodiment, the one or more fields may include a serving cell ID, a CORESET ID, a TCI status ID, and a reserved bit.

[0313] In one embodiment, the serving cell ID may indicate the identity of the serving cell to which the TCI status indicator for the UE-specific PDCCH MAC CE applies. The length of the serving cell ID may be n bits (eg, n=5 bits).

[0314] In one embodiment, the CORESET ID may indicate a control resource set. The control resource set may be identified by a control resource set ID (e.g., ControlResourceSetId). The TCI state is indicated in the control resource set ID. The length of the CORESET ID may be n3 bits (e.g., n3=4 bits).

[0315] In one embodiment, the TCI State ID may indicate a TCI state identified by the TCI-StateId. The TCI state may be applicable to a control resource set identified by the CORESET ID. The length of the TCI State ID may be n4 bits (e.g., n4=6 bits).

[0316] The information element ControlResourceSet may be used to configure the time / frequency control resource set (CORESET) for searching for downlink control information.

[0317] The information element TCI-State may associate one or two DL reference signals with corresponding quasi-co-location (QCL) types. The information element TCI-State may include one or more fields including TCI-StateId and QCL-Info. QCL-Info may include one or more second fields. The one or more second fields may include a serving cell index, a BWP ID, a reference signal index (e.g., SSB-Index, NZP-CSI-RS-Resource ID), and a QCL type (e.g., QCL-Type A, QCL-Type B, QCL-Type C, QCL-Type D). In one embodiment, TCI-StateID may identify the configuration of the TCI state.

[0318] In one embodiment, the serving cell index may indicate the serving cell in which the reference signal indicated by the reference signal index is located. If a serving cell index is not present in the information element TCI-State, the information element TCI-State may apply to the serving cell for which the information element TCI-State is configured. The reference signal may be located on a second serving cell other than the serving cell for which the information element TCI-State is configured only if the QCL-type is configured as a first type (e.g., Type D, Type A, Type B). In one embodiment, the BWP ID may indicate the downlink BWP of the serving cell in which the reference signal is located.

[0319] The information element SearchSpace may define how / where to search for PDCCH candidates in a search space. A search space may be identified by a searchSpaceId field in the information element SearchSpace. Each search space may be associated with a control resource set (e.g., ControlResourceSetId). A control resource set may be identified by the controlResourceSetId field of the information element SearchSpace. The controlResourceSetId field may indicate the control resource set (CORESET) that is applicable to the SearchSpace.

[0320] In one example, a base station may configure a wireless device with one or more aperiodic trigger states (e.g., 1, 64, or 128 aperiodic trigger states) using an information element (IE) CSI-AperiodicTriggerStateList. A codepoint of a CSI request field in a DCI may be associated with (or indicate) an aperiodic trigger state among the one or more aperiodic trigger states. In an example, an aperiodic trigger state may include one or more report configurations (e.g., 1, 8, or 16 report configurations provided by the higher layer parameter associatedReportConfigInfoList). Based on receiving a DCI with a CSI request field indicating an aperiodic trigger state, the wireless device may perform CSI-RS measurements and aperiodic reporting according to the one or more report configurations (e.g., associatedReportConfigInfoList) for the aperiodic trigger state.

[0321] In one embodiment, a certain report configuration (e.g., provided by the higher layer parameter CSI-AssociatedReportConfigInfo) of one or more report configurations may be identified / associated with a report configuration index (e.g., provided by the higher layer parameter CSI-ReportConfigId). In one embodiment, a report configuration may include one or more CSI-RS resources (e.g., 1, 8, or 16 CSI-RS resources). In one embodiment, a certain aperiodic CSI-RS resource of the one or more CSI-RS resources may be associated with a TCI state of one or more TCI-State configurations (provided by the higher layer parameter qcl-info of the IE CSI-AperiodicTriggerStateList). The TCI state may provide a QCL assumption (e.g., RS, RS source, SS / PBCH block, CSI-RS). The TCI state may provide a QCL type (e.g., QCL-Type A, QCL-Type D, etc.).

[0322] In one embodiment, a wireless device may receive a DCI having a CSI request field from a base station. The wireless device may receive the DCI on a PDCCH. The wireless device may receive the DCI when monitoring a PDCCH. In one embodiment, a DCI having a CSI request field may initiate / index / trigger one or more aperiodic trigger conditions. In one embodiment, a codepoint of the CSI request field in the DCI may indicate the aperiodic trigger condition. In one embodiment, the aperiodic trigger condition may include one or more reporting configurations (e.g., a list of NZP-CSI-RS-ResourceSet). In one embodiment, a reporting configuration (e.g., NZP-CSI-RS-ResourceSet) with one or more reporting configurations may include one or more CSI resources (e.g., aperiodic CSI-RS resources, NZP-CSI-RS-Resources).

[0323] In one embodiment, the base station may not configure the reporting configuration using the higher layer parameter trs-Info. In one embodiment, configuring the reporting configuration without the higher layer parameter trs-Info may include a first antenna port for a first aperiodic CSI-RS resource of the one or more CSI-RS resources being different from a second antenna port for a second aperiodic CSI-RS resource of the one or more CSI-RS resources. In one embodiment, configuring the reporting configuration without the higher layer parameter trs-Info may include a different antenna port for each aperiodic CSI-RS resource of the one or more CSI-RS resources. In one embodiment, the base station may not configure the reporting configuration using the repetition of the higher layer parameter. In one embodiment, the scheduling offset between the last symbol of the PDCCH carrying DCI and the first symbol of the one or more CSI-RS resources in the reporting configuration may be less than a second threshold (e.g., beamSwitchTiming). In one embodiment, the wireless device may report the second threshold. In one embodiment, the second threshold may be a first value (e.g., 14, 28, 48 symbols).

[0324] In one embodiment, an aperiodic CSI-RS resource of the one or more CSI-RS resources may be associated with a first TCI state of one or more TCI-State configurations. In one embodiment, the first TCI state may indicate at least one first RS. In one embodiment, the first TCI state may indicate at least one first QCL type. In one embodiment, associating the aperiodic CSI-RS resource with the first TCI state may include the wireless device receiving an aperiodic CSI-RS of the aperiodic CSI-RS resource using the at least one first RS (indicated by the first TCI state) for the at least one first QCL type indicated by the first TCI state.

[0325] In one embodiment, the base station may transmit a downlink signal having a second TCI state. In one embodiment, the second TCI state may indicate at least one second RS. In one embodiment, the second TCI state may indicate at least one second QCL type. The wireless device may receive the downlink signal with one or more first symbols. The wireless device may receive an aperiodic CSI-RS for the aperiodic CSI-RS resource with one or more second symbols. In one embodiment, the one or more first symbols and the one or more second symbols may overlap (e.g., fully or partially). In one embodiment, the downlink signal and the aperiodic CSI-RS (or the aperiodic CSI-RS resource) may overlap based on the overlap of the one or more first symbols and the one or more second symbols.

[0326] In one embodiment, the downlink signal and the aperiodic CSI-RS (or aperiodic CSI-RS resource) may overlap for a duration. In one embodiment, the duration may be at least one symbol. In one embodiment, the duration may be at least one slot. In one embodiment, the duration may be at least one subframe. In one embodiment, the duration may be at least one minislot. In one embodiment, the duration may be one or more second symbols. In one embodiment, the duration may be one or more first symbols.

[0327] In an example, the downlink signal may be a PDSCH scheduled with an offset equal to or greater than a first threshold (e.g., Threshold-Sched-Offset, timeDurationForQCL). In an example, the downlink signal may be a second aperiodic CSI-RS scheduled with an offset equal to or greater than a second threshold (e.g., beamSwitchTiming) when the second threshold is a first value (e.g., 14, 28, 48 symbols). In one embodiment, the downlink signal may be an RS (e.g., periodic CSI-RS, semi-persistent CSI-RS, SS / PBCH block, etc.).

[0328] In one example, if the scheduling offset between the last symbol and the first symbol of the PDCCH is less than a second threshold based on overlap of the aperiodic CSI-RS (or aperiodic CSI-RS resource) with a downlink signal having a second TCI state, the wireless device may apply the QCL assumptions provided / indicated by the second TCI state when receiving the aperiodic CSI-RS. In one example, applying the QCL assumptions (provided / indicated by the second TCI state) when receiving the aperiodic CSI may include the wireless device receiving the aperiodic CSI-RS with at least one second RS (indicated by the second TCI state) for at least one second QCL type indicated by the second TCI state.

[0329] In one example, a scheduling offset between the last symbol of the PDCCH carrying the DCI and the first symbol of one or more CSI-RS resources in the reporting configuration may be greater than or equal to a second threshold (e.g., beamSwitchTiming). In one example, the wireless device may report the second threshold. In one example, the second threshold may be a first value (e.g., 14, 28, 48 symbols). Based on the scheduling offset being greater than or equal to the second threshold, the wireless device may apply a QCL assumption (provided by the first TCI state) to aperiodic CSI-RS resources of the one or more CSI-RS resources in the reporting configuration. In one example, applying the QCL assumption (provided by the first TCI state) to the aperiodic CSI-RS resources may include the wireless device receiving aperiodic CSI-RS of the aperiodic CSI-RS resources having at least one first RS (indicated by the first TCI state) for at least one first QCL type indicated by the first TCI state.

[0330] In one embodiment, two transmission schemes for the uplink may be supported for the Physical Uplink Shared Channel (PUSCH): codebook-based transmission and non-codebook-based transmission. When the higher layer parameter txConfig in pusch-Config is set to “codebook,” the wireless device may be configured for codebook-based transmission. When the higher layer parameter txConfig is set to “nonCodebook,” the wireless device may be configured for non-codebook-based transmission. When the higher layer parameter txConfig is not set, the wireless device may not expect to be scheduled by DCI format 0_1 ​​or 0_2. When the PUSCH is scheduled by DCI format 0_0, PUSCH transmission may be based on a single antenna port. Unless the higher layer parameter enableDefaultBeamPlForPUSCH0_0 is set to “enabled,” the wireless device may not expect a PUSCH scheduled by DCI format 0_0 in BWP without a configured PUCCH resource using PUCCH-SpatialRelationInfo in frequency range 2 in RRC connected mode.

[0331] For codebook-based transmission, in one embodiment, the PUSCH may be scheduled in DCI format 0_0, DCI format 0_1, DCI format 0_2, or by being semi-statically configured. When the PUSCH is scheduled in DCI format 0_1, DCI format 0_2, or by being semi-statically configured, the wireless device may determine its PUSCH transmit precoder based on an SRS resource indicator (SRI), a transmit precoding matrix indicator (TPMI), and a transmission rank, where the SRI, TPMI, and transmission rank may be given by the “SRS resource indicator” and “Precoding information and number of layers” or srs-ResourceIndicator and precodingAndNumberOfLayers for DCI formats 0_1 and 0_2. In one embodiment, the SRS-ResourceSet applicable to the PUSCH scheduled by DCI format 0_1 ​​and DCI format 0_2 may be defined by entries of the higher layer parameters srs-ResourceSetToAddModList and srs-ResourceSetToAddModList-ForDCIFormat0_2 in SRS-Config, respectively. TPMI may be used to indicate a precoder that applies across layers {0...v-1} and corresponds to the SRS resource selected by SRI when multiple SRS resources are configured, or may be used to indicate a precoder that applies across layers {0...v-1} and corresponds to the SRS resource when a single SRS resource is configured. The transmit precoder may be selected from an uplink codebook with a number of antenna ports equal to the higher layer parameter nrofSRS-Ports in SRS-Config. When the wireless device is configured with the higher layer parameter txConfig set to “codebook,” the wireless device may be configured with at least one SRS resource.In one embodiment, the indicated SRI in slot n may be associated with the most recent transmission of the SRS resource identified by the SRI, where the SRS resource precedes the PDCCH carrying the SRI.

[0332] For non-codebook-based transmission, in one embodiment, a PUSCH may be configured and scheduled in DCI format 0_0, DCI format 0_1, DCI format 0_2, or semi-statically. When this PUSCH is configured in DCI format 0_1, DCI format 0_2, or semi-statically, the wireless device may determine its PUSCH precoder and transmission rank based on the SRI when multiple SRS resources are configured, where the SRI is given by the DCI field of "SRS resource indicator" in the DCI for DCI format 0_1 ​​and DCI format 0_2, or the SRI is given by the srs-ResourceIndicator. In one embodiment, the SRS-ResourceSet applicable to PUSCHs scheduled by DCI format 0_1 ​​and DCI format 0_2 may be defined by entries of the higher layer parameters srs-ResourceSetToAddModList and srs-ResourceSetToAddModList-ForDCIFormat0_2 in SRS-Config, respectively. A wireless device may use one or more SRS resources for SRS transmission. In an SRS resource set, a maximum number of SRS resources may be configured in the wireless device for simultaneous transmission in the same symbol, and the maximum number of SRS resources may be the capability of the wireless device. In one embodiment, simultaneously transmitted SRS resources may occupy the same RB. In one embodiment, at least one SRS port may be configured for the SRS resources. In one embodiment, one SRS resource set may be configured with the higher layer parameter usage in SRS-ResourceSet set to "nonCodebook." The SRI indicated in slot n may be associated with the most recent transmission of the SRS resource identified by the SRI, where the SRS transmission precedes the PDCCH carrying the SRI.The wireless device may perform a one-to-one mapping from the indicated SRI to the indicated demodulation RS (DMRS) ports and their corresponding PUSCH layers {0...v-1} given by DCI format 0_1 ​​or in ascending order by configuredGrantConfig.

[0333] 22 illustrates an example of transmission and reception with multiple transmit reception points (TRPs) and / or multiple panels. In one embodiment, a base station may include more than one TRP (e.g., TRP1 and TRP2). A wireless device may include more than one panel (e.g., Panel1 and Panel2). Transmission and reception using multiple TRPs and / or multiple panels may improve system throughput and / or transmission robustness for wireless communication at high frequencies (e.g., above 6 GHz).

[0334] In one embodiment, a TRP among a plurality of TRPs of a base station may be identified by at least one of a TRP identifier (ID), a cell index, or a reference signal index. In one embodiment, the TRP ID of a TRP may include a control resource set group (or pool) index of a control resource set group (e.g., CORESETPoolIndex) of a control resource set group from which a DCI is transmitted from the base station of the control resource set. In one embodiment, the TRP ID of a TRP may include a TRP index indicated in the DCI. In one embodiment, the TRP ID of a TRP may include a TCI state group index of a TCI state group. The TCI state group may include at least one TCI state in which a wireless device receives a downlink transport block (TB) or in which a base station transmits a downlink TB.

[0335] In one embodiment, a base station may include multiple TRPs. The base station may transmit one or more RRC messages including configuration parameters of multiple CORESETs on a cell (or a BWP of the cell) to a wireless device. A CORESET of the multiple CORESETs may be identified using a CORESET index and associated with (or configured with) a CORESET pool (or group) index. One or more CORESETs of the multiple CORESETs having the same CORESET pool index may indicate that DCI received in one or more CORESETs is transmitted from the same TRP of the base station. The wireless device may determine a receive beam (or spatial domain filter) for the PDCCH / PDSCH based on the TCI indicator (e.g., DCI) and the CORESET pool index associated with the CORESET for the DCI.

[0336] In one example, a wireless device may receive multiple PDCCHs scheduling full / partial / non-overlapping PDSCHs in the time and frequency domains when receiving one or more RRC messages (e.g., PDCCH-Config IE) including a first CORESET pool index (e.g., CORESETPoolIndex) value and a second CORESET pool index in a ControlResourceSet IE. The wireless device may determine reception of full / partially overlapped PDSCHs in the time domain when the PDCCHs scheduling the two PDSCHs are associated with different ControlResourceSets having different values ​​of CORESETPoolIndex.

[0337] In one embodiment, a wireless device may assume (or determine) that a ControlResourceSet is assigned a CORESETPoolIndex as 0 for a ControlResourceSet without a CORESETPoolIndex. When a wireless device is scheduled with a PDSCH that is fully / partially / non-overlapping in the time and frequency domain, scheduling information for receiving the PDSCH is indicated and carried by the corresponding PDCCH. The wireless device is expected to be scheduled with the same active BWP and the same SCS. In one embodiment, a wireless device can be scheduled with a maximum of two codewords simultaneously when the wireless device is scheduled with a PDSCH that is fully / partially overlapped in the time and frequency domain.

[0338] In one embodiment, when PDCCHs scheduling two PDSCHs are associated with different Control Resource Sets with different values ​​of CORESETPoolIndex, a wireless device is permitted to perform the following operation: for any two HARQ process IDs in a given scheduled cell, if the wireless device is scheduled to start receiving a first PDSCH starting at symbol j via a PDCCH associated with a value of CORESETpoolIndex ending at symbol i, the wireless device can be scheduled to receive a PDSCH that starts earlier than the end of the first PDSCH using a PDCCH associated with a different value of CORESETpoolIndex that ends later than symbol i, in the given scheduled cell, the wireless device can receive the first PDSCH in slot i using a corresponding HARQ-ACK assigned to be transmitted in slot j, and can receive a second PDSCH associated with a value of CORESETpoolIndex different from the value of the first PDSCH that starts later than the first PDSCH using its corresponding HARQ-ACK assigned to be transmitted in a slot prior to slot j.

[0339] In one example, when a wireless device is configured with the higher layer parameter PDCCH-Config, which includes two different values ​​of CORESETPoolIndex in ControlResourceSet, for both cases where tci-PresentInDCI is set to “enabled” and where tci-PresentInDCI is not configured in RRC connected mode, if the offset between reception of the DL DCI and the corresponding PDSCH is less than the threshold timeDurationForQCL, the wireless device may assume that the DM-RS port of the PDSCH associated with the value of CORESETPoolIndex of the serving cell is quasi-co-located with the RS with respect to the QCL parameter used for the PDCCH quasi-co-location index of the CORESET associated with the monitored search space with the lowest CORESET-ID among the CORESETs, and the PDCCH scheduling the PDSCH in the active BWP of the serving cell and one or more CORESETs associated with the same value of CORESETPoolIndex are configured with the same value of CORESETPoolIndex as the PDCCH scheduling the PDSCH in the latest slot monitored by the wireless device. If the offset between reception of the DL DCI and the corresponding PDSCH is less than a threshold timeDurationForQCL, and at least one configured TCI state for the serving cell of the scheduled PDSCH includes "QCL-TypeD", and at least one TCI codepoint indicates two TCI states, the wireless device may assume that the DM-RS port of the PDSCH of the serving cell is quasi-co-located using the RS for the QCL parameter associated with the TCI state that corresponds to the lowest codepoint among the TCI codepoints that include two different TCI states.

[0340] In one embodiment, when a wireless device is configured with multiple panels, it may decide to activate (or select) one of the multiple panels to receive a downlink signal / channel transmitted from one of the base station's multiple TRPs. The activation / selection of one of the multiple panels may be based on receiving downlink signaling indicating the activation / selection, or may be done automatically based on measuring the downlink channel quality of one or more reference signals transmitted from the base station.

[0341] In one embodiment, the wireless device may apply a spatial domain filter and transmit from a panel of the plurality of panels to one of the plurality of TRPs of the base station, the panel and spatial domain filter being determined based on at least one of a UL TCI indicator of the DCI, a panel ID of the DCI, an SRI indicator of the DCI, a CORESET pool index of the CORESET for receiving the DCI, and the like.

[0342] In one embodiment, upon receiving a DCI indicating an uplink grant, a wireless device may determine a panel and a transmission beam (or spatial-domain transmission filter) on the panel. The panel may be explicitly indicated by a panel ID included in the DCI. The panel may be implicitly indicated by an SRS ID (or SRS group / pool index), a UL TCI pool index of the UL TCI for uplink transmission, and / or a CORESET pool index of the CORESET for receiving the DCI.

[0343] The amount of data traffic carried over cellular networks can be expected to increase over the coming years. More spectrum may be needed for cellular operators to meet the growing demand for various services, such as video streaming, large files, or images. To meet market demand, there is growing interest from operators in deploying complementary access services utilizing unlicensed spectrum to accommodate traffic growth. This is evidenced by the large number of Wi-Fi networks deployed by operators and the 3GPP standardization of LTE / WLAN interworking solutions. This interest indicates that the presence of unlicensed spectrum can effectively complement mobile operators' licensed spectrum, helping to address traffic explosion in some scenarios, such as hotspot areas. Licensed Assisted Access (LAA) provides operators with an alternative means to utilize unlicensed spectrum while still managing a single wireless network, offering new possibilities for optimizing network efficiency.

[0344] In one embodiment, listen-before-talk (LBT) may be implemented for transmissions in LAA cells. In the LBT procedure, before using a channel, an equipment (e.g., a device or a base station) may apply a clear channel assessment (CCA) check. For example, CCA may utilize at least energy detection to determine the presence or absence of other signals on the channel to determine whether the channel is occupied or clear, respectively. For example, regulations in Europe and Japan mandate the use of LBT in unlicensed bands. Apart from regulatory requirements, carrier sensing via LBT is one way to fairly share unlicensed spectrum.

[0345] In one embodiment, discontinuous transmission on an unlicensed carrier with a limited maximum transmission duration may be enabled. Some of these functions may be supported by one or more signals transmitted from the start of the discontinuous LAA downlink transmission. Channel reservation is enabled by the transmission of a signal by an LAA node after obtaining channel access via a successful LBT operation, and other nodes receiving the transmitted signal with energy above a certain threshold may sense the occupied channel. Functions that need to be supported by one or more signals for LAA operation with discontinuous downlink transmission include one or more of the following: detection of LAA downlink transmission (including cell identification) by the UE; and time / frequency synchronization of the UE.

[0346] In one embodiment, the DL LAA design may use subframe boundary alignment according to the LTE-A carrier aggregation timing relationship across serving cells aggregated by CA. This may not mean that base station transmissions can only start at subframe boundaries. LAA may support the transmission of PDSCH when not all OFDM symbols in a subframe can be transmitted according to LBT. Delivery of control information required for PDSCH may also be supported.

[0347] The LBT procedure may be used to ensure fair and friendly coexistence between the LAA and other operators and technologies operating in the unlicensed spectrum. The LBT procedure for a node attempting to transmit on a carrier in the unlicensed spectrum requires the node to perform CCA to determine whether the channel is available for use. The LBT procedure may include at least energy detection to determine whether the channel is available for use. For example, regulatory requirements in some regions, such as Europe, specify an energy detection threshold such that if the node receives energy above this threshold, the node assumes the channel is not available. A node may comply with such regulatory requirements and, optionally, use a lower threshold for energy detection than that specified by the regulatory requirements. In one embodiment, the LAA may employ a mechanism to adaptively change the energy detection threshold. For example, the LAA may employ a mechanism to adaptively lower the energy detection threshold from an upper limit. The adaptation mechanism may not prevent static or semi-static setting of the threshold. In one embodiment, a Category 4 LBT mechanism or another type of LBT mechanism may be implemented.

[0348] Various example LBT mechanisms may be implemented. In one embodiment, for some signals, in some implementation scenarios, in some situations, and / or at some frequencies, the LBT procedure may not be performed by the transmitting entity. In one embodiment, Category 2 (e.g., LBT without random backoff, or short LBT, etc.) may be implemented. The duration for which the channel is sensed idle before the transmitting entity transmits may be deterministic. In one embodiment, Category 3 (e.g., LBT with random backoff using a fixed-size contention window) may be implemented. The LBT procedure may include the following steps as one of its components: The transmitting entity may draw a random number N within a contention window. The size of the contention window may be specified by a minimum and a maximum value of N. The size of the contention window may be fixed. The random number N may be used in the LBT procedure to determine the duration for which the channel is sensed idle before the transmitting entity transmits on the channel. In one embodiment, Category 4 (e.g., LBT with random backoff using a variable-size contention window) may be implemented. The transmitting entity may draw a random number N within the contention window. The size of the contention window can be specified by a minimum and a maximum value of N. A transmitting entity can change the size of the contention window when drawing a random number N. The random number N is used in the LBT procedure to determine the duration for which the channel is perceived to be idle before the transmitting entity transmits on the channel.

[0349] The LAA may use uplink (UL) LBT in the wireless device. The UL LBT may differ from the downlink (DL) LBT scheme (e.g., by using different LBT mechanisms or parameters), for example, because the LAA UL is based on scheduled access, which affects the channel contention opportunities of the wireless device. Other considerations motivating different UL LBT schemes include, but are not limited to, multiplexing of multiple UEs in a single subframe.

[0350] In one embodiment, a DL transmission burst may be a continuous transmission from a DL transmitting node without an immediately preceding or following transmission from the same node on the same CC. A UL transmission burst from the perspective of a wireless device may be a continuous transmission from the same wireless device on the same CC without an immediately preceding or following transmission from the same wireless device. In one embodiment, a UL transmission burst may be defined from the perspective of a wireless device. In one embodiment, a UL transmission burst may be defined from the perspective of a base station. In one embodiment, when a base station operates a DL+UL LAA on the same unlicensed carrier, DL transmission bursts and UL transmission bursts on an LAA may be scheduled in a TDM manner on the same unlicensed carrier. For example, a given time may be part of a DL transmission burst or a UL transmission burst.

[0351] In one embodiment, single and multiple DL-to-UL and UL-to-DL switches within a shared gNB (e.g., base station) channel occupation time (COT) may be supported. In one embodiment, gap lengths and / or single or multiple switching points may have different LBT requirements. In one embodiment, LBT may not be used for gaps less than 16 us. One-shot LBT may be used for gaps equal to or greater than 16 us and less than 25 us. In one embodiment, one-shot LBT may be used for single switching points and gaps from DL transmission to UL transmission greater than 25 us, and one-shot LBT may be used for multiple switching points and gaps from DL transmission to UL transmission greater than 25 us.

[0352] In one embodiment, signals detected by a wireless device with low complexity may help the wireless device save power, improve coexistence with other systems, achieve at least spatial reuse within the same operator network, and / or perform serving cell transmission burst acquisition, etc.

[0353] In one embodiment, new radio operation in unlicensed bands (NR-U) can use a signal that can include at least SS / PBCH block burst set transmissions. In one embodiment, other channels and signals can be transmitted together as part of the signal. The design of this signal can take into account that there are no gaps in the time span over which the signal is transmitted, at least within the beam. In one embodiment, gaps can be required for beam switchin...

Claims

1. A wireless device, one or more processors; A memory that stores instructions Equipped with The instructions, when executed by the one or more processors, receiving a medium access control control element (MAC CE) indicating activation of one or more transmission configuration indicator (TCI) states, the one or more TCI states including a first TCI state, the MAC CE comprising: a first TCI state identifier (ID) for the first TCI state; Link indicator and a first value of the link indicator indicating that the first TCI state ID is from a first list of one or more first TCI state IDs for a downlink and a second value of the link indicator indicating that the first TCI state ID is from a second list of one or more second TCI state IDs for an uplink; communicating with a base station based on the first TCI state indicated by the first TCI state ID and the link indicator; The wireless device is caused to perform the above.

2. The wireless device of claim 1, wherein the instructions further cause the wireless device to activate the first TCI state in response to receiving the MAC CE indicating activation of the first TCI state.

3. The wireless device of claim 1, wherein the instructions further cause the wireless device to receive downlink control information (DCI) including a TCI field, a code point of the TCI field indicating the first TCI state ID.

4. The wireless device of claim 3, wherein the wireless device communicates with the base station based on the first TCI state, the first TCI state being indicated by the first TCI state ID corresponding to the code point of the TCI field of the DCI.

5. The instructions further cause the wireless device to receive one or more radio resource control (RRC) messages, the RRC messages comprising: a first list of one or more first TCI conditions for a downlink, each of the one or more first TCI conditions in the first list being associated with a corresponding TCI condition ID of the first list of the one or more first TCI conditions; a second list of one or more second TCI conditions for an uplink, each of the one or more second TCI conditions in the second list being associated with a corresponding TCI condition ID of the second list of the one or more second TCI conditions; The wireless device of claim 1 , further comprising a configuration parameter:

6. The configuration parameters include, for each TCI in the first list of one or more first TCI states or the second list of one or more second TCI states: A cell index, A bandwidth fraction index; a reference signal (RS) index indicating at least one of a channel state information reference signal (CSI-RS) index or a synchronization signal block (SSB) index; Quasi-coordinate type indicator and 6. The wireless device of claim 5, further comprising:

7. communicating with the base station based on the first TCI state includes, in response to the link indicator being set to the first value, receiving a downlink signal and a channel using a spatial domain filter determined based on the activated TCI state; The downlink signal and the channel are: Physical Downlink Shared Channel (PDSCH); A physical downlink control channel (PDCCH), or Channel State Information Reference Signal (CSI-RS) The wireless device of claim 1 , comprising at least one of:

8. The method of claim 7, further comprising: communicating with the base station based on the first TCI state, in response to the link indicator being set to the second value, transmitting an uplink signal and a channel using a spatial domain filter determined based on the activated TCI state; The uplink signal and channel are: Physical Uplink Shared Channel (PUSCH); A physical uplink control channel (PUCCH), or Sounding Reference Signal (SRS) The wireless device of claim 1 , comprising at least one of:

9. A base station, one or more processors; A memory that stores instructions Equipped with The instructions, when executed by the one or more processors, transmitting a medium access control control element (MAC CE) to a wireless device indicating activation of one or more transmission configuration indicator (TCI) states, the one or more TCI states including a first TCI state, the MAC CE comprising: a first TCI state identifier (ID) for the first TCI state; Link indicator and a first value of the link indicator indicating that the first TCI state ID is from a first list of one or more first TCI state IDs for a downlink and a second value of the link indicator indicating that the first TCI state ID is from a second list of one or more second TCI state IDs for an uplink; communicating with the wireless device based on the first TCI state indicated by the first TCI state ID and the link indicator; A base station that causes the base station to perform the above.

10. The base station of claim 9, wherein the instructions further cause the base station to activate the first TCI state in response to transmitting the MAC CE indicating activation of the first TCI state.

11. The base station of claim 9, wherein the instructions further cause the base station to transmit downlink control information (DCI) including a TCI field, a code point of the TCI field indicating the first TCI state ID.

12. The base station of claim 11, wherein the base station communicates with the wireless device based on the first TCI state, the first TCI state being indicated by the first TCI state ID corresponding to the code point of the TCI field of the DCI.

13. The instructions further cause the base station to transmit one or more radio resource control (RRC) messages, the RRC messages comprising: a first list of one or more first TCI conditions for a downlink, each of the one or more first TCI conditions in the first list being associated with a corresponding TCI condition ID of the first list of the one or more first TCI conditions; a second list of one or more second TCI conditions for an uplink, each of the one or more second TCI conditions in the second list being associated with a corresponding TCI condition ID of the second list of the one or more second TCI conditions; The base station of claim 9, further comprising the configuration parameters:

14. The configuration parameters include, for each TCI in the first list of one or more first TCI states or the second list of one or more second TCI states: A cell index, A bandwidth fraction index; a reference signal (RS) index indicating at least one of a channel state information reference signal (CSI-RS) index or a synchronization signal block (SSB) index; Quasi-coordinate type indicator and The base station according to claim 13, wherein:

15. Communicating with the wireless device based on the first TCI state includes, in response to the link indicator being set to the first value, transmitting a downlink signal and a channel using a spatial domain filter determined based on the activated TCI state; The downlink signal and the channel are: Physical Downlink Shared Channel (PDSCH); A physical downlink control channel (PDCCH), or Channel State Information Reference Signal (CSI-RS) The base station of claim 9, comprising at least one of:

16. Communicating with the wireless device based on the first TCI state includes, in response to the link indicator being set to the second value, receiving an uplink signal and a channel using a spatial domain filter determined based on the activated TCI state; The uplink signal and channel are: Physical Uplink Shared Channel (PUSCH); A physical uplink control channel (PUCCH), or Sounding Reference Signal (SRS) The base station of claim 9, comprising at least one of:

17. A non-transitory computer-readable medium containing instructions that, when executed by one or more processors of a wireless device, receiving a medium access control control element (MAC CE) indicating activation of one or more transmission configuration indicator (TCI) states, the one or more TCI states including a first TCI state, the MAC CE comprising: a first TCI state identifier (ID) for the first TCI state; Link indicator and a first value of the link indicator indicating that the first TCI state ID is from a first list of one or more first TCI state IDs for a downlink and a second value of the link indicator indicating that the first TCI state ID is from a second list of one or more second TCI state IDs for an uplink; communicating with a base station based on the first TCI state indicated by the first TCI state ID and the link indicator; A non-transitory computer-readable medium that causes the wireless device to 18. The non-transitory computer-readable medium of claim 17, wherein the instructions further cause the wireless device to activate the first TCI state in response to receiving the MAC CE indicating activation of the first TCI state.

19. The non-transitory computer-readable medium of claim 17, wherein the instructions further cause the wireless device to receive downlink control information (DCI) including a TCI field, a code point of the TCI field indicating the first TCI state ID.

20. The non-transitory computer-readable medium of claim 19, wherein the wireless device communicates with the base station based on the first TCI state, the first TCI state being indicated by the first TCI state ID corresponding to the code point of the TCI field of the DCI.

Images