Downlink control channel repetition for downlink control channel command - Patents.com

Abstract

Methods, systems, and devices for wireless communications are described. A user equipment (UE) may receive an indication that a first downlink control channel candidate and a second downlink control channel candidate are linked for downlink control channel repetition. The UE may receive a downlink control channel command requesting the UE to participate in a random access procedure. In some examples, the downlink control channel command may be received via one or both of the first and second downlink control channel candidates, and the UE may perform the random access procedure according to one or more rules regarding reception of the downlink control channel command via the linked downlink control channel candidate. Additionally or alternatively, the UE may receive the downlink control channel command via a downlink control channel candidate that is not linked for downlink control channel repetition according to one or more rules.

Description

[Technical field]

[0001] cross reference

[0001] This patent application claims the benefit of U.S. Provisional Patent Application No. 63 / 169,663, by Khoshnevisan et al., entitled "DOWNLINK CONTROL CHANNEL REPETITION FOR A DOWNLINK CONTROL CHANNEL ORDER," filed on April 1, 2021, which is assigned to the assignee of this application, and U.S. Patent Application No. 17 / 708,178, by Khoshnevisan et al., entitled "DOWNLINK CONTROL CHANNEL REPETITION FOR A DOWNLINK CONTROL CHANNEL ORDER," filed on March 30, 2022.

[0002] The present disclosure relates to wireless communications including downlink control channel repetition for downlink control channel command. [Background technology]

[0003]

[0003] Wireless communication systems have been widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasts, and the like. These systems may be capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems, such as Long Term Evolution (LTE), LTE Advanced (LTE-A), or LTE-A Pro systems, and fifth generation (5G) systems, sometimes referred to as New Radio (NR) systems. These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Spread Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations or one or more network access nodes, each simultaneously supporting communication for multiple communication devices, sometimes known as user equipment (UE).

[0004] In some wireless communication systems, a base station may transmit a downlink control channel command to a UE requesting the UE to participate in a random access procedure. Summary of the Invention

[0005]

[0005] The described techniques relate to improved methods, systems, devices, and apparatuses supporting downlink control channel repetition for downlink control channel commands. Generally, the described techniques provide for a user equipment (UE) to receive downlink control channel commands via two or more downlink control channel candidates linked for repetition according to one or more rules for receiving downlink control channel commands via the linked downlink control channel candidates. The UE may receive an indication that a first downlink control channel candidate and a second downlink control channel candidate are linked for downlink control channel repetition. In some examples, the indication may be received via radio resource control (RRC) signaling. The UE may receive the downlink control channel commands via one or both of the first downlink control channel candidate and the second downlink control channel candidate according to one or more rules. The downlink control channel commands may be transmitted by a base station and may request the UE to participate in a random access procedure. The UE may perform a random access procedure associated with the downlink control channel commands according to one or more rules. In some examples, the one or more rules may indicate a threshold delay period between receiving a downlink control channel command at the UE and transmitting an uplink random access message by the UE. In some examples, the one or more rules may specify a guideline for identifying a quasi-co-location (QCL) assumption to be applied to receiving a downlink random access message. Additionally or alternatively, the one or more rules may relate to whether the UE may receive a downlink control channel command via a downlink control channel candidate that is linked. In some examples, the UE may receive a downlink control channel command via a downlink control channel candidate that is not linked with other downlink control channel candidates for repetition.

[0006] A method for wireless communications in a UE is described, which may include receiving an indication that a first downlink control channel candidate and a second downlink control channel candidate are linked for downlink control channel iteration, receiving a downlink control channel command via one or both of the first downlink control channel candidate and the second downlink control channel candidate requesting the UE to participate in a random access procedure, and performing a random access procedure associated with the downlink control channel command according to one or more rules regarding reception of the downlink control channel command via the linked downlink control channel candidate.

[0007] An apparatus for wireless communication in a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to receive an indication that a first downlink control channel candidate and a second downlink control channel candidate are linked for downlink control channel iteration, receive downlink control channel commands via one or both of the first downlink control channel candidate and the second downlink control channel candidate requesting the UE to participate in a random access procedure, and perform a random access procedure associated with the downlink control channel commands according to one or more rules regarding reception of the downlink control channel commands via the linked downlink control channel candidates.

[0008] Another apparatus for wireless communications in a UE is described, which may include means for receiving an indication that a first downlink control channel candidate and a second downlink control channel candidate are linked for downlink control channel iteration, means for receiving downlink control channel commands via one or both of the first downlink control channel candidate and the second downlink control channel candidate requesting the UE to participate in a random access procedure, and means for performing a random access procedure associated with the downlink control channel commands according to one or more rules regarding reception of the downlink control channel commands via the linked downlink control channel candidates.

[0009] A non-transitory computer-readable medium storing code for wireless communication in a UE is described, which may include instructions executable by a processor to receive an indication that a first downlink control channel candidate and a second downlink control channel candidate are linked for downlink control channel iteration, receive downlink control channel commands via one or both of the first downlink control channel candidate and the second downlink control channel candidate requesting the UE to participate in a random access procedure, and perform a random access procedure associated with the downlink control channel commands according to one or more rules regarding reception of the downlink control channel commands via the linked downlink control channel candidates.

[0010] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, performing a random access procedure may include operations, features, means, or instructions for determining a random access occasion for transmission of an uplink random access message in response to a downlink control channel command, and transmitting the uplink random access message during the random access occasion based on a first symbol of the random access occasion being after a threshold delay period that may be triggered by a reference downlink control channel candidate. In some examples, the reference downlink control channel candidate may be a second downlink control channel candidate as a result of the second downlink control channel candidate ending later in time than the first downlink control channel candidate, and the one or more rules may indicate that the threshold delay period begins after the last symbol of the second downlink control channel candidate.

[0011]

[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described in this specification may further include operations, features, means, or instructions for performing a random access procedure according to one or more rules, which may be independent of whether the downlink control channel command is received during a first downlink control channel candidate or a second downlink control channel candidate.

[0012]

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described in this specification, the threshold delay period includes a first time period for uplink shared channel preparation according to a UE capability, a second time period for random access preparation, a third time period for bandwidth portion (BWP) switching, a fourth time period for uplink switching, or a combination thereof.

[0013]

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining a random access occasion may include operations, features, means, or instructions for determining the timing of the random access occasion based on an indication in a downlink control channel command or based on a measured synchronization signal block (SSB).

[0014]

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, performing a random access procedure may include operations, features, means, or instructions for transmitting an uplink random access message in response to a downlink control channel command, where a first downlink control channel candidate may be associated with a first Transmission Configuration Indicator (TCI) state and a second downlink control channel candidate may be associated with a second TCI state, which may be different from the first TCI state; identifying a QCL assumption to be applied to receiving a downlink random access message in response to the uplink random access message according to one or more rules, where the QCL assumption is associated with at least one of the first TCI state or the second TCI state.

[0015]

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, identifying a QCL assumption may include operations, features, means, or instructions for selecting one of the first TCI state or the second TCI state as a basis for the QCL assumption in accordance with one or more rules, where the one or more rules specify that the selection of either the first TCI state or the second TCI state may be based on relative timing between the first downlink control channel candidate and the second downlink control channel candidate.

[0016]

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, identifying a QCL assumption may include operations, features, means, or instructions for selecting one of the first TCI state or the second TCI state as a basis for the QCL assumption in accordance with one or more rules, where the one or more rules specify that the selection of either the first TCI state or the second TCI state may be based on relative values ​​of a first search space set identifier (ID) of a first search space set corresponding to the first downlink control channel candidate and a second search space set ID of a second search space set corresponding to the second downlink control channel candidate.

[0017]

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, identifying a QCL assumption may include operations, features, means, or instructions for selecting one of the first TCI state or the second TCI state as a basis for the QCL assumption in accordance with one or more rules, where the one or more rules specify that the selection of either the first TCI state or the second TCI state may be based on relative values ​​of a first control resource set (CORESET) ID associated with a first search space set corresponding to the first downlink control channel candidate and a second CORESET ID associated with a second search space set corresponding to the second downlink control channel candidate.

[0018]

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, identifying a QCL assumption may include an operation, feature, means, or instruction for selecting one of the first TCI state or the second TCI state as a basis for the QCL assumption in accordance with one or more rules, where the one or more rules specify that the selection of either the first TCI state or the second TCI state may be based on a relative value of a first TCI state ID associated with the first TCI state and a second TCI state ID associated with the second TCI state.

[0019]

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, identifying a QCL assumption may include an operation, feature, means, or instruction for selecting both a first TCI state and a second TCI state as a basis for the QCL assumption in accordance with one or more rules, where the one or more rules specify that a downlink random access message to which the QCL assumption may apply may be a downlink control channel message that schedules a random access response (RAR) message, and the downlink control channel message is transmitted via a third downlink control channel candidate and a fourth downlink control channel candidate that may be linked for downlink control channel iteration.

[0020]

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, identifying a QCL assumption may include an operation, feature, means, or instruction for selecting both the first TCI state and the second TCI state as a basis for the QCL assumption in accordance with one or more rules, where the one or more rules specify that a downlink random access message to which the QCL assumption may apply may be a RAR message that may be a multi-TCI state downlink shared channel that varies in at least one of spatial division multiplexing (SDM), frequency division multiplexing (FDM), time division multiplexing (TDM), or a single frequency network scheme.

[0021]

[0021] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the downlink control channel command requests a contention-free random access (CFRA) procedure on a primary cell (PCell), or a primary secondary cell (PSCell), or both.

[0022]

[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described in this specification, the downlink random access message may either be a downlink control channel message that schedules a RAR message or may be a RAR message.

[0023] A method for wireless communication in a base station is described, which may include transmitting an indication to a UE that a first downlink control channel candidate and a second downlink control channel candidate are linked for downlink control channel repetition, transmitting a downlink control channel command to the UE via one or both of the first downlink control channel candidate and the second downlink control channel candidate requesting the UE to participate in a random access procedure, and receiving an uplink random access message from the UE related to the downlink control channel command according to one or more rules regarding transmission of the downlink control channel command via the linked downlink control channel candidate.

[0024] An apparatus for wireless communication in a base station is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to transmit an indication to a UE that a first downlink control channel candidate and a second downlink control channel candidate are linked for downlink control channel iteration, transmit downlink control channel commands to the UE via one or both of the first downlink control channel candidate and the second downlink control channel candidate requesting the UE to participate in a random access procedure, and receive an uplink random access message from the UE related to the downlink control channel commands according to one or more rules regarding transmission of the downlink control channel commands via the linked downlink control channel candidates.

[0025] Another apparatus for wireless communications in a base station is described, which may include means for transmitting an indication to a UE that a first downlink control channel candidate and a second downlink control channel candidate are linked for downlink control channel repetition, means for transmitting a downlink control channel command to the UE via one or both of the first downlink control channel candidate and the second downlink control channel candidate requesting the UE to participate in a random access procedure, and means for receiving an uplink random access message from the UE related to the downlink control channel command according to one or more rules for transmitting the downlink control channel command via the linked downlink control channel candidates.

[0026] A non-transitory computer-readable medium storing code for wireless communications in a base station is described, which may include instructions executable by a processor to transmit an indication to a UE that a first downlink control channel candidate and a second downlink control channel candidate are linked for downlink control channel iterations, transmit downlink control channel commands to the UE via one or both of the first downlink control channel candidate and the second downlink control channel candidate requesting the UE to participate in a random access procedure, and receive an uplink random access message from the UE related to the downlink control channel commands according to one or more rules for transmitting the downlink control channel commands via the linked downlink control channel candidates.

[0027] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving an uplink random access message may include operations, features, means, or instructions for receiving an uplink random access message during a random access occasion based on a first symbol of the random access occasion being after a threshold delay period that may be triggered by a reference downlink control channel candidate. In some examples, the reference downlink control channel candidate may be a second downlink control channel candidate as a result of the second downlink control channel candidate ending later in time than the first downlink control channel candidate, and one or more rules may indicate that the threshold delay period begins after the last symbol of the second downlink control channel candidate.

[0028]

[0028] Some examples of the methods, apparatus, and non-transitory computer-readable media described in this specification may further include operations, features, means, or instructions for receiving an uplink random access message according to one or more rules, which may be independent of whether the downlink control channel command may be transmitted during a first downlink control channel candidate or a second downlink control channel candidate.

[0029]

[0029] Some examples of the methods, apparatus, and non-transitory computer-readable media described in this specification may further include an operation, feature, means, or instruction for transmitting an indication of the timing of the random access occasion to the UE via a downlink control channel command or SSB.

[0030]

[0030] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for identifying a QCL assumption to be applied to transmitting a downlink random access message in response to the uplink random access message in accordance with one or more rules, the QCL assumption being associated with at least one of a first TCI state associated with a first downlink control channel candidate or a second TCI state associated with a second downlink control channel candidate, where the first TCI state may be different from the second TCI state.

[0031]

[0031] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, identifying a QCL assumption may include operations, features, means, or instructions for selecting both a first TCI state and a second TCI state as a basis for the QCL assumption in accordance with one or more rules, where the one or more rules specify that a downlink random access message to which the QCL assumption may apply may be a downlink control channel message that schedules a RAR message, and the downlink control channel message is transmitted via a third downlink control channel candidate and a fourth downlink control channel candidate that may be linked for downlink control channel repetition.

[0032]

[0032] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, identifying a QCL assumption may include an operation, feature, means, or instruction for selecting both the first TCI state and the second TCI state as a basis for the QCL assumption in accordance with one or more rules, where the one or more rules specify that the downlink random access message to which the QCL assumption may apply may be a RAR message, which may be a multi-TCI state downlink shared channel that varies in at least one of SDM, FDM, TDM, or single frequency network modalities. [Brief description of the drawings]

[0033] [Figure 1] FIG. 1 illustrates an example of a wireless communications system that supports downlink control channel repetition for downlink control channel commanding, according to an aspect of the present disclosure. [Diagram 2]

[0034] FIG. 1 illustrates an example of a wireless communication system that supports downlink control channel repetition for downlink control channel commanding, according to aspects of the present disclosure. [Figure 3A]

[0035] 10A-10C illustrate example search space set configurations that support downlink control channel iterations for downlink control channel commanding, in accordance with aspects of the present disclosure. [Figure 3B] 10A-10C illustrate example search space set configurations that support downlink control channel iterations for downlink control channel commanding, in accordance with aspects of the present disclosure. [Figure 4A]

[0036] 1 illustrates an example of a random access timeline supporting downlink control channel repetition for downlink control channel commanding, according to an aspect of the disclosure. [Figure 4B] 1 illustrates an example of a random access timeline supporting downlink control channel repetition for downlink control channel commanding, according to an aspect of the disclosure. [Diagram 5]

[0037] 1 illustrates an example of a process flow for supporting downlink control channel repetition for downlink control channel commanding, according to an aspect of the disclosure. [Figure 6]

[0038] 1 illustrates an example of a process flow for supporting downlink control channel repetition for downlink control channel commanding, according to an aspect of the disclosure. [Figure 7]

[0039] 1 is a block diagram of a device supporting downlink control channel repetition for downlink control channel commanding, according to an aspect of the disclosure. [Figure 8]1 is a block diagram of a device supporting downlink control channel repetition for downlink control channel commanding, according to an aspect of the disclosure. [Figure 9]

[0040] 1 illustrates a block diagram of a communications manager supporting downlink control channel repetition for downlink control channel command, according to an aspect of the disclosure. [Figure 10]

[0041] FIG. 1 illustrates an illustration of a system including a device that supports downlink control channel repetition for downlink control channel commanding, according to an aspect of the disclosure. [Figure 11]

[0042] 1 is a block diagram of a device supporting downlink control channel repetition for downlink control channel commanding, according to an aspect of the disclosure. [Figure 12] 1 is a block diagram of a device supporting downlink control channel repetition for downlink control channel commanding, according to an aspect of the disclosure. [Figure 13]

[0043] 1 illustrates a block diagram of a communications manager supporting downlink control channel repetition for downlink control channel command, according to an aspect of the disclosure. [Figure 14]

[0044] FIG. 1 illustrates an illustration of a system including a device that supports downlink control channel repetition for downlink control channel commanding, according to an aspect of the disclosure. [Figure 15]

[0045] 11 is a flow chart illustrating a method for supporting downlink control channel repetition for downlink control channel commanding, according to an aspect of the disclosure. [Figure 16] 11 is a flow chart illustrating a method for supporting downlink control channel repetition for downlink control channel commanding, according to an aspect of the disclosure. [Figure 17] 11 is a flow chart illustrating a method for supporting downlink control channel repetition for downlink control channel commanding, according to an aspect of the disclosure. [Figure 18]11 is a flow chart illustrating a method for supporting downlink control channel repetition for downlink control channel commanding, according to an aspect of the disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0034]

[0046] In some wireless communication systems, a user equipment (UE) may be configured with one or more control resource sets (CORESETs). Each CORESET may include time and frequency resources within a bandwidth portion (BWP) of a serving cell allocated to carry a physical downlink control channel (PDCCH). A CORESET may include one or more search space sets, each including one or more PDCCH candidates. The UE may be configured to monitor each PDCCH candidate for downlink control information (DCI). In some examples, a base station may transmit a PDCCH command requesting the UE to participate in a random access procedure via one or more PDCCH candidates linked for a PDCCH repetition. However, if the PDCCH command is associated with a linked PDCCH candidate, the UE may not be able to identify a timeline for transmitting an uplink random access message, such as a random access request message, after receiving the PDCCH command. Additionally or alternatively, if a PDCCH command is associated with linked PDCCH candidates each corresponding to a different transmission configuration indicator (TCI) state, the UE may not know which TCI state should be selected as the basis for a quasi-colocation (QCL) assumption to be applied to reception of one or more downlink random access messages corresponding to the PDCCH command.

[0035]

[0047] A UE described herein may be configured with a set of one or more rules for performing a random access procedure according to a PDCCH command received via a linked PDCCH candidate. Performing the random access procedure by the UE may include receiving a PDCCH command, transmitting an uplink random access message, and receiving a DCI via a PDCCH that schedules the downlink random access message received via a physical downlink shared channel (PDSCH). After receiving a PDCCH command within one or both of a first PDCCH candidate or a second PDCCH candidate linked to the first PDCCH candidate, the UE may wait for at least a delay period before transmitting an uplink random access message via a physical random access channel (PRACH). The one or more rules may indicate that the delay period starts after the last symbol of the linked PDCCH candidate that ends later in time.

[0036]

[0048] If the first PDCCH candidate and the second PDCCH candidate are associated with the same TCI state, the UE may use the TCI state as a basis for a QCL assumption to be applied to reception of the DCI, the downlink random access message, or both. In some examples, the first PDCCH candidate may correspond to a first TCI state, the second PDCCH candidate may correspond to a second TCI state different from the first TCI state, and the rule may specify one or more parameters for selecting one of the first TCI state or the second TCI state to be used as a basis for the QCL assumption. If the DCI that schedules the downlink random access message is associated with a linked PDCCH candidate, if the downlink random access message is received via a multi-TCI state PDSCH, or both, the one or more rules may specify that both the first TCI state and the second TCI state may be selected.

[0037]

[0049] Additionally or alternatively, the one or more rules may indicate that the UE may refrain from receiving a PDCCH command if the PDCCH command is associated with two or more linked PDCCH candidates. In such a case, the UE may receive a PDCCH command via a PDCCH candidate that is not linked with other PDCCH candidates for repetition. In one example, the one or more rules may allow reception of a PDCCH command via a linked PDCCH candidate if the linked PDCCH candidates correspond to the same TCI state, and the one or more rules may restrict reception of a PDCCH command if the linked PDCCH candidates correspond to different TCI states. Thus, the UE may be configured with one or more rules regarding reception of a PDCCH command via a linked PDCCH candidate to improve reliability and efficiency of a random access procedure corresponding to a PDCCH command.

[0038]

[0050] Aspects of the present disclosure are first described in the context of a wireless communication system. Additional aspects of the present disclosure are described with reference to search space set configurations, random access timelines, and process flows. Aspects of the present disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow charts relating to downlink control channel iterations for downlink control channel commanding.

[0039]

[0051] 1 illustrates an example of a wireless communication system 100 supporting downlink control channel repetition for downlink control channel commanding according to an aspect of the disclosure. The wireless communication system 100 may include one or more base stations 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, a LTE-Advanced (LTE-A) network, a LTE-A Pro network, or a New Radio (NR) network. In some examples, the wireless communication system 100 may support enhanced broadband communications, ultra-reliable (e.g., mission-critical) communications, low latency communications, communications with low-cost and low-complexity devices, or any combination thereof.

[0040]

[0052] The base stations 105 may be distributed throughout a geographic area to form a wireless communication system 100 and may be devices of different forms or with different capabilities. The base stations 105 and the UEs 115 may communicate wirelessly via one or more communication links 125. Each base station 105 may provide a coverage area 110 over which the UEs 115 and the base stations 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area over which the base stations 105 and the UEs 115 may support communication of signals according to one or more radio access technologies.

[0041]

[0053] The UEs 115 may be distributed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be fixed, or mobile, or both at different times. The UEs 115 may be devices of different forms or with different capabilities. Some example UEs 115 are shown in FIG. 1. The UEs 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, base stations 105, or network equipment (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network equipment), as shown in FIG. 1.

[0042]

[0054] The base stations 105 may communicate with the core network 130, with each other, or both. For example, the base stations 105 may interface with the core network 130 through one or more backhaul links 120 (e.g., via an S1, N2, N3, or other interface). The base stations 105 may communicate with each other over the backhaul links 120 (e.g., via an X2, Xn, or other interface) either directly (e.g., directly between the base stations 105) or indirectly (e.g., via the core network 130), or both. In some examples, the backhaul links 120 may be or include one or more wireless links.

[0043]

[0055] One or more of the base stations 105 described herein may include or be referred to by one skilled in the art as a base transceiver station, radio base station, access point, radio transceiver, Node B, eNode B (eNB), Next Generation Node B or Giga Node B (any of which may be referred to as a gNB), Home Node B, Home eNode B, or other suitable terminology.

[0044]

[0056] The UE 115 may include or be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where a "device" may also be referred to as a unit, a station, a terminal, or a client, among other examples. The UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, the UE 115 may include or be referred to as a Wireless Local Loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, among other examples, which may be implemented in various objects, such as an appliance, or a vehicle, a meter, among other examples.

[0045]

[0057] The UEs 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may act as relays at times, as shown in FIG. 1, as well as base stations 105 and network equipment, including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples.

[0046]

[0058] The UE 115 and the base station 105 may wirelessly communicate with each other via one or more communication links 125 on one or more carriers. The term “carrier” may refer to a set of radio frequency spectrum resources having a defined physical layer structure to support the communication link 125. For example, a carrier used for the communication link 125 may include a portion of a radio frequency spectrum band (e.g., BWP) operated according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling to coordinate the operation of the carrier, user data, or other signaling. The wireless communication system 100 may support communication with the UE 115 using carrier aggregation or multi-carrier operation. The UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplex (FDD) and time division duplex (TDD) component carriers.

[0047]

[0059] In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition or control signaling that coordinates operation for other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN)) and may be arranged according to a channel raster for discovery by the UE 115. A carrier may be operated in a standalone mode where initial acquisition and connection may be made by the UE 115 over the carrier, or a carrier may be operated in a non-standalone mode where a connection is established using a different carrier (e.g., of the same or different radio access technology).

[0048]

[0060] The communication links 125 shown in the wireless communication system 100 may include uplink transmissions from the UE 115 to the base station 105 or downlink transmissions from the base station 105 to the UE 115. A carrier may carry downlink or uplink communications (e.g., in FDD mode) or may be configured to carry downlink and uplink communications (e.g., in TDD mode).

[0049]

[0061] A carrier may be associated with a particular bandwidth of the radio frequency spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one of several determined bandwidths (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)) for a carrier of a particular radio access technology. The devices (e.g., the base station 105, the UE 115, or both) of the wireless communication system 100 may have a hardware configuration that supports communication on a particular carrier bandwidth or may be configurable to support communication on one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a base station 105 or UE 115 that supports simultaneous communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (e.g., a sub-band, BWP) or all of the carrier bandwidth.

[0050]

[0062] A signal waveform transmitted on a carrier may be composed of multiple subcarriers (e.g., using a multicarrier modulation (MCM) technique such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may consist of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and the subcarrier spacing are inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both). Thus, the more resource elements the UE 115 receives and the higher the order of the modulation scheme, the higher the data rate for the UE 115 may be. Wireless communication resources may refer to a combination of radio frequency spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers may further increase the data rate or data integrity for communication with the UE 115.

[0051]

[0063] One or more numerologies may be supported for a carrier, where the numerology may include a subcarrier spacing (Δf) and a cyclic prefix. A carrier may be divided into one or more BWPs having the same or different numerologies. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communication for the UE 115 may be limited to one or more active BWPs.

[0052]

[0064] The time interval for the base station 105 or the UE 115 may be, for example, T s =1 / (Δf max N f ) seconds, where Δf max may represent the maximum subcarrier spacing supported, and N fmay represent the maximum discrete Fourier transform (DFT) size supported. The communication resource time intervals may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0053]

[0065] Each frame may include multiple consecutively numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into several slots. Alternatively, each frame may include a variable number of slots, and the number of slots may depend on the subcarrier spacing. Each slot may include several symbol periods (e.g., depending on the length of a cyclic prefix prepended to each symbol period). In some wireless communications systems 100, a slot may be further divided into multiple minislots containing one or more symbols. Excluding the cyclic prefix, each symbol period may include one or more (e.g., N f A symbol period may include a sampling period of at least one symbol (symbol period). The duration of a symbol period may depend on the subcarrier spacing or the frequency operating band.

[0054]

[0066] A subframe, slot, minislot, or symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0055]

[0067] The physical channels may be multiplexed on the carriers according to various techniques. The physical control channels and the physical data channels may be multiplexed on the downlink carriers using, for example, one or more of a time division multiplexing (TDM), a frequency division multiplexing (FDM), or a hybrid TDM-FDM technique. A control region (e.g., CORESET) for the physical control channel may be defined by a number of symbol periods and may span the system bandwidth of the carrier or a subset of the system bandwidth. One or more control regions (e.g., CORESET) may be configured for a set of UEs 115. For example, one or more of the UEs 115 may monitor or search the control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates at one or more aggregation levels configured in a cascaded manner. The aggregation level for the control channel candidates may refer to a number of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for sending control information to multiple UEs 115 and a UE-specific search space set for sending control information to a specific UE 115.

[0056]

[0068] Each base station 105 may provide communication coverage via one or more cells, e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof. The term "cell" may refer to a logical communication entity used for communication with the base station 105 (e.g., on a carrier) and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other) to distinguish neighboring cells. In some examples, a cell may also refer to a geographic coverage area 110 or a portion (e.g., a sector) of a geographic coverage area 110 in which the logical communication entity operates. Such a cell may range from a smaller area (e.g., a structure, a subset of a structure) to a larger area depending on various factors such as the capabilities of the base station 105. For example, a cell may be or include a building, a subset of a building, or an exterior space between or overlapping with the geographic coverage area 110, among other examples.

[0057]

[0069] A macro cell generally covers a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UEs 115 subscribing to the service of a network provider supporting the macro cell. A small cell may be associated with a lower power base station 105 compared to a macro cell, and the small cell may operate in the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to UEs 115 subscribing to the service of a network provider, or may provide restricted access to UEs 115 having an association with a small cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with a user at home or in the office). A base station 105 may support one or more cells and may also support communication on one or more cells using one or more component carriers.

[0058]

[0070] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0059]

[0071] In some examples, the base stations 105 are mobile and may therefore provide communication coverage to moving geographic coverage areas 110. In some examples, different geographic coverage areas 110 associated with different technologies may overlap, but the different geographic coverage areas 110 may be supported by the same base station 105. In other examples, overlapping geographic coverage areas 110 associated with different technologies may be supported by different base stations 105. The wireless communication system 100 may include heterogeneous networks in which different types of base stations 105 provide coverage to various geographic coverage areas 110, e.g., using the same or different radio access technologies.

[0060]

[0072] The wireless communications system 100 may support synchronous or asynchronous operation. For synchronous operation, the base stations 105 may have similar frame timing and transmissions from different base stations 105 may be approximately aligned in time. For asynchronous operation, the base stations 105 may have different frame timing and transmissions from different base stations 105 may not be aligned in time, in some examples. The techniques described herein may be used for either synchronous or asynchronous operation.

[0061]

[0073] Some UEs 115, such as MTC devices or IoT devices, may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technologies that allow devices to communicate with each other or with the base station 105 without human intervention. In some examples, M2M communication or MTC may include communication from devices that incorporate sensors or meters to measure or capture information and relay such information to a central server or application program that utilizes the information or presents the information to a human interacting with the application program. Some UEs 115 may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business billing.

[0062]

[0074] Some UEs 115 may be configured to employ operating modes that reduce power consumption, such as half-duplex communication (e.g., a mode that supports one-way communication via transmission or reception, rather than transmission and reception simultaneously). In some examples, the half-duplex communication may be performed at a reduced peak rate. Other power saving techniques for the UE 115 include entering a power saving deep sleep mode when not engaged in active communication, operating on a limited bandwidth (e.g., pursuant to narrowband communication), or a combination of these techniques. For example, some UEs 115 may be configured for operation using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a guard band of the carrier, or outside of the carrier.

[0063]

[0075] The wireless communication system 100 may be configured to support ultra-reliable or low latency communications, or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low latency communications (URLLC) or mission-critical communications. The UE 115 may be designed to support ultra-reliable, low latency, or critical functions (e.g., mission-critical functions). Ultra-reliable communications may include private or group communications and may be supported by one or more mission-critical services, such as mission-critical push-to-talk (MCPTT), mission-critical video (MCVideo), or mission-critical data (MCData). Support for mission-critical functions may include service prioritization, and the mission-critical services may be used for public safety or general commercial applications. The terms ultra-reliable, low latency, mission-critical, and ultra-reliable low latency may be used interchangeably herein.

[0064]

[0076] In some examples, the UE 115 may also be able to communicate directly with other UEs 115 over a device-to-device (D2D) communication link 135 (e.g., using a peer-to-peer (P2P) or D2D protocol). One or more UEs 115 utilizing D2D communication may be within the geographic coverage area 110 of the base station 105. Other UEs 115 in such a group may be outside the geographic coverage area 110 of the base station 105 or otherwise unable to receive transmissions from the base station 105. In some examples, a group of UEs 115 communicating via D2D communication may utilize a one-to-many (1:M) system in which each UE 115 transmits to every other UE 115 in the group. In some examples, the base station 105 facilitates scheduling of resources for D2D communication. In other cases, D2D communication occurs between UEs 115 without the involvement of the base station 105.

[0065]

[0077] In some systems, the D2D communication link 135 may be an example of a communication channel, such as a sidelink communication channel, between vehicles (e.g., UE 115). In some examples, the vehicles may communicate using vehicle-to-anything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination thereof. The vehicles may signal information regarding traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some examples, the vehicles in a V2X system may communicate with roadside infrastructure, such as roadside units, and / or a network via one or more network nodes (e.g., base stations 105) using vehicle-to-network (V2N) communication.

[0066]

[0078] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) that manages access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) that routes packets or interconnection to external networks. The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management, for the UEs 115 served by the base stations 105 associated with the core network 130. User IP packets may be forwarded through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entities may be connected to IP services 150 for one or more network operators. The IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0067]

[0079] Some of the network devices, such as the base station 105, may include subcomponents, such as an access network entity 140, which may be an example of an access node controller (ANC). Each access network entity 140 may communicate with the UE 115 through one or more other access network transmitting entities 145, which may be referred to as a radio head, a smart radio head, or a transmit / receive point (TRP). Each access network transmitting entity 145 may include one or more antenna panels. In some configurations, various functions of each access network entity 140 or base station 105 may be distributed across various network devices (e.g., radio heads and ANCs) or integrated into a single network device (e.g., the base station 105).

[0068]

[0080] The wireless communication system 100 may operate using one or more frequency bands typically within the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately 1 decimeter to 1 meter in length. Although UHF waves may be blocked or redirected by buildings and environmental features, the waves may penetrate structures sufficiently for a macrocell to serve UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers) compared to transmissions using smaller frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0069]

[0081] The wireless communication system 100 may also operate in the Super High Frequency (SHF) region, using a frequency band from 3 GHz to 30 GHz, also known as the centimeter band, or the Extremely High Frequency (EHF) region of the spectrum, also known as the millimeter band (e.g., from 30 GHz to 300 GHz). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between the UE 115 and the base station 105, and the EHF antennas of the respective devices may be smaller and more closely spaced than the UHF antennas. In some examples, this may facilitate the use of antenna arrays within the devices. However, propagation of EHF transmissions may experience greater atmospheric attenuation and be shorter distances than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions using one or more different frequency regions, and the designated use of bands across these frequency regions may vary by country or regulatory body.

[0070]

[0082] The wireless communication system 100 may utilize both licensed and unlicensed radio frequency spectrum bands. For example, the wireless communication system 100 may employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band, such as the 5 GHz Industrial, Scientific, and Medical (ISM) band. When operating in an unlicensed radio frequency spectrum band, devices such as the base station 105 and the UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation in an unlicensed band may be based on a carrier aggregation configuration with a component carrier operating in a licensed band (e.g., LAA). Operation in an unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

[0071]

[0083] The base station 105 or UE 115 may be equipped with multiple antennas that may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the base station 105 or UE 115 may be located in one or more antenna arrays or antenna panels that may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located in an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with the base station 105 may be located in various geographic locations. The base station 105 may have an antenna array with several rows and columns of antenna ports that the base station 105 may use to support beamforming of communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panels may support radio frequency beamforming for signals transmitted through the antenna ports.

[0072]

[0084] A base station 105 or a UE 115 may use MIMO communications to exploit multipath signal propagation and increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such techniques may be referred to as spatial multiplexing. The multiple signals may be transmitted by a transmitting device, for example, via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry bits related to the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports used for channel measurements and reporting. MIMO techniques include single-user MIMO (SU-MIMO), in which multiple spatial layers are transmitted to the same receiving device, and multi-user MIMO (MU-MIMO), in which multiple spatial layers are transmitted to multiple devices.

[0073]

[0085] Beamforming, sometimes referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used in a transmitting or receiving device (e.g., base station 105, UE 115) to shape or steer an antenna beam (e.g., transmit beam, receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals communicated through antenna elements of an antenna array such that some signals propagating in a particular orientation relative to the antenna array experience constructive interference and others experience destructive interference. Adjustment of signals communicated through antenna elements may include a transmitting or receiving device applying an amplitude offset, a phase offset, or both to signals conveyed through an antenna element associated with the device. The adjustment associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., relative to the antenna array of the transmitting or receiving device, or to some other orientation).

[0074]

[0086] The base station 105 or the UE 115 may use beam sweeping techniques as part of a beamforming operation. For example, the base station 105 may use multiple antennas or antenna arrays (e.g., antenna panels) to perform a beamforming operation for directional communication with the UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times in different directions by the base station 105. For example, the base station 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. The transmissions in different beam directions may be used to identify beam directions (e.g., by a transmitting device such as the base station 105 or by a receiving device such as the UE 115) for subsequent transmission or reception by the base station 105.

[0075]

[0087] Some signals, such as data signals associated with a particular receiving device, may be transmitted by the base station 105 in a single beam direction (e.g., a direction associated with the receiving device, such as the UE 115). In some examples, the beam direction associated with the transmission along the single beam direction may be determined based on signals transmitted in one or more beam directions. For example, the UE 115 may receive one or more of the signals transmitted by the base station 105 in different directions and report to the base station 105 an indication of the signal received by the UE 115 with the best signal quality or an otherwise acceptable signal quality.

[0076]

[0088] In some examples, transmission by a device (e.g., by the base station 105 or the UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or radio frequency beamforming to generate a composite beam for transmission (e.g., from the base station 105 to the UE 115). The UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured number of beams across the system bandwidth or one or more subbands. The base station 105 may transmit a reference signal (e.g., cell-specific reference signal (CRS), channel state information reference signal (CSI-RS)), which may be precoded or amplicoded. The UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel type codebook, linear combination type codebook, port selection type codebook). Although these techniques have been described with respect to signals transmitted in one or more directions by the base station 105, the UE 115 may employ similar techniques for transmitting a signal multiple times in different directions (e.g., to identify a beam direction for subsequent transmission or reception by the UE 115) or for transmitting a signal in a single direction (e.g., to transmit data to a receiving device).

[0077]

[0089] A receiving device (e.g., UE 115) may attempt multiple receive configurations (e.g., directional listening) when receiving various signals from the base station 105, such as synchronization signals, reference signals, beam selection signals, or other control signals. For example, the receiving device may attempt multiple receive directions by receiving via different antenna subarrays, by processing the received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of the antenna array, or by processing the received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of the antenna array, any of which may be referred to as "listening" according to different receive configurations or receive directions. In some examples, the receiving device may use a single receive configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned in a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or otherwise acceptable signal quality based on listening according to multiple beam directions).

[0078]

[0090] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communication at the bearer or Packet Data Convergence Protocol (PDCP) layer may be IP-based. A Radio Link Control (RLC) layer may perform packet segmentation and reassembly to communicate over logical channels. A Medium Access Control (MAC) layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer may also use error detection, error correction, or both techniques to support retransmissions at the MAC layer to improve link efficiency. In the control plane, a Radio Resource Control (RRC) protocol layer may provide establishment, configuration, and maintenance of an RRC connection between the UE 115 and the base station 105 or core network 130, which supports radio bearers for user plane data. In the physical layer, transport channels may be mapped to physical channels.

[0079]

[0091] The UE 115 and the base station 105 may support retransmission of data to increase the likelihood that the data is successfully received. Hybrid Automatic Repeat Request (HARQ) feedback is one technique for increasing the likelihood that the data is accurately received on the communication link 125. HARQ may include a combination of error detection (e.g., using a Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ may improve throughput at the MAC layer in poor radio conditions (e.g., low signal-to-noise conditions). In some examples, a device may support same-slot HARQ feedback, where the device may provide HARQ feedback in a particular slot for data received in a previous symbol in that slot. In other cases, the device may provide HARQ feedback in a subsequent slot or according to some other time interval.

[0080]

[0092] In some examples, the UE 115 may receive a downlink control channel command via two or more downlink control channel candidates (e.g., PDCCH candidates, search spaces, or some other candidate time and / or frequency locations of downlink resources) that are linked for a downlink control channel repetition. The UE 115 may receive an indication that a first PDCCH candidate and a second PDCCH candidate are linked for a PDCCH repetition. In some examples, the indication may be received via RRC signaling. The UE 115 may receive a PDCCH command via one or both of the first and second PDCCH candidates. The PDCCH command may be transmitted by the base station 105 and may request the UE 115 to participate in a random access procedure. The UE 115 may perform a random access procedure associated with the PDCCH command according to one or more rules regarding reception of the PDCCH command via the linked PDCCH candidates. In some examples, the one or more rules may indicate a threshold delay period between receiving a PDCCH command at the UE 115 and transmitting a random access message by the UE 115 to the base station 105. In some examples, the one or more rules may indicate a rule for identifying a QCL assumption to be applied to receiving a downlink random access message. Additionally or alternatively, the one or more rules may relate to whether the UE 115 may receive a PDCCH command via a linked PDCCH candidate. The one or more rules may thereby reduce ambiguity associated with timing, TCI state selection, or both for performing a random access procedure in response to receiving a PDCCH command via a linked PDCCH candidate, which may improve reliability and efficiency of communications.

[0081]

[0093] FIG. 2 illustrates an example of a wireless communication system 200 supporting downlink control channel repetition for downlink control channel commands according to aspects of the disclosure. In some examples, the wireless communication system 200 may implement some aspects of the wireless communication system 100. For example, the wireless communication system 200 may include a base station 105-a and a UE 115-a, which may represent examples of the base station 105 and the UE 115 described with reference to FIG. 1. The base station 105-a and the UE 115-a may communicate within a geographic coverage area 110-a via an uplink communication link 205 and a downlink communication link 210 (e.g., a Uu link). In some examples, the base station 105-a may transmit a PDCCH command 225 to the UE 115-a via one or more PDCCH candidates linked for the PDCCH repetition, requesting the UE 115-a to participate in a random access procedure.

[0082]

[0094] The UE 115-a and the base station 105-b may perform a random access procedure to synchronize the uplink communication link 205, the downlink communication link 210, or both. In some cases, the UE 115-a may transmit a random access request message 230 (e.g., Msg1) to initiate the random access procedure. The random access request message 230 may be transmitted via a PRACH during a PRACH occasion. The random access procedure may correspond to a contention-based random access (CBRA) or a contention-free random access (CFRA). During the CBRA procedure, the UE 115-a may randomly select a preamble and a PRACH occasion for transmitting the random access request message 230 (e.g., based on a received synchronization signal block (SSB)). During the CFRA procedure, the UE 115-a may receive a random access preamble and / or a PRACH occasion assignment from the base station 105-a, and the UE 115-a may transmit a random access request message 230 according to the assigned preamble and PRACH occasion.

[0083]

[0095] If the random access request message 230 has not been transmitted by the UE 115-a and the base station 105-a identifies downlink data to be transmitted to the UE 115-a, the base station 105-a may transmit a PDCCH command 225 to the UE 115-a to request the UE 115-a to participate in the random access procedure. The UE 115-a may transmit the random access request message 230 in response to the PDCCH command 225. The UE 115-a may receive the PDCCH command 225 via a DCI (e.g., DCI format 1_0) having a CRC scrambled by a control radio network temporary identifier (C-RNTI). The UE 115-a may determine that the DCI corresponds to the PDCCH command 225 if each bit in a frequency domain resource allocation (FDRA) field of the DCI is set high (e.g., to “1”).

[0084]

[0096] The PDCCH command 225 may indicate one or more parameters associated with the random access procedure. For example, the PDCCH command 225 may include a random access preamble index (e.g., a 6-bit field) indicating a type of random access procedure. If the random access preamble index is 0, the PDCCH command may trigger a CBRA, and the UE 115-a may ignore the remaining fields in the PDCCH command 225. During the CBRA, the UE 115-a may measure one or more SSBs received from the base station 105-a and determine a PRACH occasion (e.g., a timing of the PRACH occasion, such as a start symbol of the PRACH occasion) for transmitting the random access request message 230 based on the measurement of the one or more SSBs. If the random access preamble is not zero, the PDCCH command triggers a CFRA. If a CFRA is triggered, the UE 115-a may decode one or more remaining fields in the PDCCH command 225 to identify the PRACH occasion and other parameters associated with the random access procedure.

[0085]

[0097] The one or more remaining fields in the PDCCH command 225 may include an uplink or supplemental uplink (SUL) indication field, an SSB index field, a PRACH mask index field, one or more other reserved fields, or any combination thereof. The uplink or SUL indication field may include a bit to indicate whether the UE 115-a may transmit the random access request message 230 over the uplink or SUL. The SSB index field may include an amount of bits (e.g., 6 bits) to indicate an SSB index associated with the CFRA. The PRACH mask field may include an amount of bits (e.g., 4 bits) to indicate a PRACH mask index associated with the CFRA. The UE 115-a may determine a PRACH occasion for transmitting the random access request message 230 based on the SSB index and the PRACH mask index. The one or more remaining bits in the DCI carrying the PDCCH command 225 may be reserved for other parameters or applications.

[0086]

[0098] A PRACH occasion indicated by a PDCCH command 225 (e.g., for CFRA) or associated with a measured SSB (e.g., for CBRA) may occur after a threshold delay period. The threshold delay period may start after the last symbol of the PDCCH command 225. That is, the first symbol of the PRACH occasion may occur at least the threshold delay period after the last symbol of the PDCCH command 225. The threshold delay period may take into account physical uplink shared channel (PUSCH) preparation, random access preparation, BWP switching, uplink switching, or any combination thereof according to the capabilities of the UE 115-a.

[0087]

[0099] The base station 105-a may receive the random access request message 230 during the PRACH occasion, and the base station 105-a may transmit one or more other random access messages as part of the random access procedure. For example, the base station 105-a may transmit a control message (e.g., DCI) via the PDCCH, a downlink random access response (RAR) message via the PDSCH, or both. In some cases, the UE 115-a may identify a QCL assumption to be applied to reception of the control message, the downlink RAR message, or both, based on a TCI state associated with the PDCCH command 225 (e.g., a beam used for reception of the PDCCH command 225). For example, the UE 115-a may use the TCI state associated with the PDCCH command 225 as a basis for a QCL assumption to be applied to reception of the downlink random access message (e.g., the UE 115-a may assume that the downlink random access message is QCLed with the PDCCH command 225). Additional aspects of the random access procedure messages and timelines may be further described elsewhere herein, including with reference to Figures 4A and 4B.

[0088]

[0100] The UE 115-a may be configured with one or more CORESETs (e.g., three, four, five, or some other amount of CORESETs in the BWP of the serving cell) for monitoring the PDCCH for the PDCCH command 225 (e.g., or for other downlink control messages). The amount of time and frequency resources (e.g., resource blocks in the frequency domain and OFDM symbols in the time domain) in each CORESET, as well as the active TCI state associated with each CORESET, may be RRC configured. Each CORESET may include one or more search space sets (e.g., up to 10 search space sets in the BWP of a component carrier (CC)), and each search space set may include one or more PDCCH candidates (e.g., according to a given aggregation level). The UE 115-a may perform blind decoding of the PDCCH candidates in each search space set to receive the DCI. That is, the UE 115-a may monitor each PDCCH candidate in the search space set for the DCI. The UE 115-a may successfully decode one or more of the PDCCH candidates (e.g., the CRC may pass) to obtain the DCI. In some examples, one or more search space sets and corresponding PDCCH candidates may be linked for a repetition of the DCI, which may be referred to as a PDCCH repetition or a downlink control channel repetition. Additional aspects of configurations for search space sets and PDCCH candidates may be further described elsewhere herein, including with reference to Figures 3A and 3B.

[0089]

[0101] In some cases, the base station 105-a may transmit the PDCCH command 225 over two or more PDCCH candidates that are linked for PDCCH repetition. The UE 115 may receive an indication 235 that the PDCCH candidates are linked, and the UE 115 may receive the PDCCH command 225 in response. However, in some cases, if the UE 115 receives the PDCCH command 225 over a linked PDCCH candidate, the UE 115 may not know when to start the threshold delay period to determine a PRACH occasion for transmitting the random access request message 230. Additionally or alternatively, the linked PDCCH candidates may correspond to different TCI states, and the UE 115 may not know which TCI state to use as a basis for the QCL assumption to be applied to the reception of the downlink random access message from the base station 105-a.

[0090]

[0102] As described herein, a UE 115, such as UE 115-a, may be configured with one or more rules regarding reception of a PDCCH command 225 via a linked PDCCH candidate. The UE 115-a may receive a PDCCH command 225 via a linked PDCCH candidate and perform a random access procedure in response to the PDCCH command 225 according to the one or more rules. The one or more rules may indicate a timeline for performing a random access procedure in response to a PDCCH command 225 received via a linked PDCCH candidate. For example, a rule may indicate that a threshold delay period after reception of a PDCCH command and before a PRACH occasion may start after the last symbol of a PDCCH candidate that ends later in time than other linked PDCCH candidates.

[0091]

[0103] The one or more rules may additionally or alternatively provide instructions for the UE 115-a to select one or more TCI states to use as a basis for QCL assumptions for receiving future downlink random access messages. That is, if the PDCCH command 225 is received via a PDCCH candidate associated with a different TCI state, the one or more rules may specify parameters for the UE 115-a to use for selection of one of the TCI states. Additionally or alternatively, the rules may specify that two or more of the TCI states may be selected if the UE 115-a receives an indication that the respective downlink random access message is received via a linked PDCCH candidate, via a multi-TCI state PDSCH, or via both. In some examples, the one or more selected TCI states may indicate one or more parameters for configuring a QCL relationship between demodulation reference signal (DMRS) ports for receiving the downlink random access message. If the PDCCH command 225 triggers a CBRA procedure, the UE 115-a may ignore the one or more rules for selecting a TCI state. The UE 115-a may instead determine the QCL assumption based on a measured SSB associated with the CBRA. That is, the one or more rules may apply to a CFRA procedure but may not be applicable to a CBRA procedure. Additionally or alternatively, the one or more rules may not apply to a CFRA procedure running on a secondary cell (SCell).

[0092]

[0104] In some examples, the one or more rules may indicate that the UE 115-a is not expected to receive the PDCCH command 225 via two PDCCH candidates that are linked for PDCCH repetition. In other words, if the UE 115-a receives an indication 235 that two or more PDCCH candidates are linked, the UE 115-a may refrain from receiving the PDCCH command 225 transmitted via the linked PDCCH candidate. In some examples, the rules may allow reception of the PDCCH command 225 via the linked PDCCH candidate if the PDCCH command 225 triggers a CBRA (e.g., the random access preamble index is 0), if the PDCCH command 225 triggers a CFRA on a SCell, or both. Additionally or alternatively, the rules may allow reception of the PDCCH command 225 via the linked PDCCH candidate if the linked PDCCH candidates correspond to respective search space sets associated with the same CORESET (e.g., the PDCCH candidates correspond to the same TCI state). In some examples, the rules may allow reception of a PDCCH command 225 via linked PDCCH candidates if the linked PDCCH candidates correspond to respective search space sets associated with different CORESETs, each associated with the same TCI state.

[0093]

[0105] Thereby, the UE 115 described herein may perform a random access procedure according to a configured set of rules for performing the random access procedure in response to a PDCCH command 225 received via a PDCCH candidate linked for PDCCH reception. The rules may specify instructions for performing the random access procedure by the UE 115, which may provide improved reliability, efficiency, and accuracy of the random access procedure corresponding to the PDCCH command.

[0094]

[0106] 3A and 3B illustrate example search space set configurations 300-a and 300-b supporting downlink control channel iteration for downlink control channel commanding according to aspects of the disclosure. The search space set configurations 300-a and 300-b may implement or be implemented by certain aspects of the wireless communication systems 100 or 200. For example, the search space set configurations 300-a and 300-b may represent example configurations for a UE 115, which may represent an example of a UE 115, as described with reference to FIGS. 1 and 2.

[0095]

[0107] The UE 115 may be configured to monitor one or more (e.g., up to five) CORESETs in the BWP of a CC. As described with reference to FIG. 2, a CORESET may include a quantity of search space sets 305 (e.g., up to ten search space sets 305 in the BWP of a CC). Thus, each search space set 305 may correspond to a single CORESET (e.g., and a single corresponding TCI state). The search space set 305 may be RRC configured and may include a set of time and frequency resources spanning one or more slots 320 in the time domain and one or more symbols 315 (e.g., OFDM symbols 315) in one or more subchannels in the frequency domain. The RRC configuration for each search space set 305 may indicate an associated CORESET, monitoring occasions 310 within the search space set 305, a type of search space set 305 (e.g., common search space (CSS) or UE-specific search space (USS)), one or more DCI formats for the UE 115 to monitor within the search space set 305, the amount of PDCCH candidates within the search space set 305 for each aggregation level, or any combination thereof. The resources in the search space set 305 may be contiguous or non-contiguous in time and frequency. For example, the monitoring occasions 310 within the search space set may be distributed across one or more symbols 315, slots 320, subchannels, or any combination thereof.

[0096]

[0108] The monitoring occasions 310 in the search space set 305 may be configured according to a monitoring slot periodicity, offset, and symbol 315 within the slot 320. That is, the UE 115 may identify a location of each monitoring occasion 310 in the search space set 305 based on an RRC configuration for the search space set 305. Each monitoring occasion 310 may include one or more PDCCH candidates, which may include time and frequency resources for reception of the DCI. Each PDCCH candidate may correspond to an aggregation level and may be configured with a candidate index in each search space set 305. As described with reference to FIG. 2, the UE 115 may perform blind decoding of each monitoring occasion 310 and the corresponding PDCCH candidate to receive the DCI.

[0097]

[0109] In some examples, two or more search space sets 305 may be linked for PDCCH repetition. The UE 115 may receive an indication of the linked search space sets via an RRC configuration. In some examples, the indication of the linked search space sets may indicate linked PDCCH candidates. For example, the UE 115 may identify linked monitoring occasions 310 in the search space sets 305 and linked PDCCH candidates in the monitoring occasions 310 according to one or more rules indicated in the RRC configuration. Figures 3A and 3B show example search space set configurations 300-a and 300-b for linked search space sets 305 including linked PDCCH candidates.

[0098]

[0110] 3A illustrates an example search space set configuration 300-a for a first search space set 305-a and a second search space set 305-b. The search space set configuration 300-a illustrates monitoring occasions 310-a of the first search space set and monitoring occasions 310-b of the second search space set within a slot 320-a. The monitoring occasions 310-a and 310-b may include subsets of time and frequency resources within the respective first search space set 305-a and second search space set 305-b.

[0099]

[0111] The UE 115 may receive an indication (e.g., via RRC signaling) that the first search space set 305-a and the second search space set 305-b are linked for PDCCH repetition. The UE 115 may determine that the monitoring occasions 310-a and 310-b are linked for PDCCH repetition based on one or more rules. For example, the rules may indicate a one-to-one mapping between the monitoring occasions 310 of the different search space sets 305.

[0100]

[0112] The UE 115 may determine one or more pairs of linked PDCCH candidates in the linked monitoring occasions 310-a and 310-b according to the aggregation level and candidate index of the respective PDCCH candidates. For example, each search space set 305 may be configured to include the same amount of PDCCH candidates for each aggregation level. Thus, the UE 115 may identify a first PDCCH candidate in the monitoring occasion 310-a that corresponds to a first aggregation level and a second PDCCH candidate in the monitoring occasion 310-b that also corresponds to the first aggregation level. The UE 115 may determine that the first PDCCH candidate and the second PDCCH candidate are linked for PDCCH repetition based on the RRC configuration, the one-to-one mapping between the monitoring occasions 310-a and 310-b, and the first aggregation level. In the example search space set configuration 300-a, the UE 115 may identify three sets of linked PDCCH candidates between the monitoring occasions 310-a of the first search space set 305-a and the monitoring occasions 310-b of the second search space set 305-b (e.g., as indicated by the three arrows between the monitoring occasions 310-a and 310-b). DCI may be transmitted via one or both PDCCH candidates of each linked PDCCH candidate pair.

[0101]

[0113] 3B illustrates a second exemplary search space set configuration 300-b for a first search space set 305-a and a second search space set 305-b. In the example search space set configuration 300-b, the first search space set 305-a may include two monitoring occasions 310-d and 310-e in a slot 320-b, and the second search space set 305-b may include two monitoring occasions 310-c and 310-f in the same slot 320-b.

[0102]

[0114] The UE 115 may receive an indication that the first search space set 305-a and the second search space set 305-b are linked for PDCCH repetitions, as described with reference to FIG. 3A. The UE 115 may identify a one-to-one mapping between monitoring occasions 310-c and 310-d and a one-to-one mapping between monitoring occasions 310-e and 310-f within slot 320-b.

[0103]

[0115] The UE 115 may determine one or more pairs of linked PDCCH candidates in each pair of linked monitoring occasions 310 according to the aggregation level and candidate index of each PDCCH candidate, as described with reference to FIG. 3A. For example, the UE 115 may identify three sets of linked PDCCH candidates between the monitoring occasion 310-d of the first search space set 305-a and the monitoring occasion 310-c of the second search space set 305-b (e.g., as indicated by the three arrows between the monitoring occasion 310-c and the monitoring occasion 310-d). The UE 115 may identify three sets of linked PDCCH candidates between the monitoring occasions 310-e of the first search space set 305-a and the monitoring occasions 310-f of the second search space set 305-b (e.g., as indicated by the three arrows between the monitoring occasions 310-e and 310-f). DCI may be transmitted via one or both PDCCH candidates of each linked PDCCH candidate pair.

[0104]

[0116] The search space set configurations 300-a and 300-b may thereby indicate intra-slot PDCCH repetition. In some example search space set configurations 300 that are different from the search space set configurations 300-a and 300-b, a first monitoring occasion 310 and a corresponding first PDCCH candidate in a first slot 320 may be linked to a second monitoring occasion 310 and a corresponding second PDCCH candidate in a second slot 320 (e.g., inter-slot PDCCH repetition).

[0105]

[0117] A UE 115 configured with either of the search space set configurations 300-a and 300-b may identify the linked search space set 305, the linked monitoring occasions 310, and the linked PDCCH candidates before decoding the DCI received via the linked PDCCH candidates. The UE 115 may or may not perform soft combining to decode the DCI received via the linked PDCCH candidates. In some examples, a PDCCH command may be transmitted to the UE 115 via the linked PDCCH candidates as described with reference to FIG. 2.

[0106]

[0118] If a PDCCH command is received by UE 115 via a linked PDCCH candidate, UE 115 may not know when to send a random access request message after receiving the PDCCH command, or UE 115 may not know which QCL assumption to use for receiving a downlink random access message, or both.

[0107]

[0119] To reduce the impact of PDCCH repetition on the random access procedure, the UE 115 described herein may be configured with a set of rules regarding reception of PDCCH commands via linked PDCCH candidates. The rules may indicate a timeline for transmission of a random access request message, one or more parameters for selecting a TCI state to be used as a basis for QCL assumptions for reception of one or more downlink random access messages, or both, which may improve the reliability of the random access procedure. Additionally or alternatively, the rules may indicate that the UE 115 may refrain from receiving PDCCH commands via linked PDCCH candidates. Aspects of the configured rules are described in further detail elsewhere herein, including with reference to Figures 4A and 4B.

[0108]

[0120] 4A and 4B illustrate examples of random access timelines 400-a and 400-b supporting downlink control channel repetition for downlink control channel commands according to aspects of the disclosure. The random access timelines 400-a and 400-b may implement or be implemented by some aspects of the wireless communication system 100 or 200 or the search space set configuration 300-a or 300-b. For example, the random access timelines 400-a and 400-b may illustrate example timelines for a random access procedure performed by the UE 115 and the base station 105, which may represent examples of the UE 115 and the base station 105 described with reference to FIGS. 1-3. In some examples, the UE 115 may receive PDCCH commands via linked PDCCH candidates 405, as described with reference to FIGS. 1-3. The UE 115 may perform a random access procedure corresponding to the PDCCH command in accordance with one or more rules related to receiving the PDCCH command via a linked PDCCH candidate, as illustrated by random access timelines 400-a and 400-b.

[0109]

[0121] 4A illustrates a first random access timeline 400-a supporting downlink control channel repetition for downlink control channel command according to an aspect of the disclosure. In the example of the random access timeline 400-a, the UE 115 may receive an indication via RRC signaling that the PDCCH candidates 405-a and 405-b are linked for PDCCH repetition. For example, the UE 115 may receive RRC signaling indicating two search space sets that are linked for PDCCH repetition. In response to receiving the RRC signaling, the UE 115 may identify linked monitoring occasions in the search space sets and identify linked PDCCH candidates 405-a and 405-b in the linked monitoring occasions according to one or more rules indicated via the RRC signaling, as described with reference to FIG. 3A and FIG. 3B. Additionally or alternatively, the UE 115 may identify the linked PDCCH candidates 405-a and 405-b based on a configuration or indication received via other control signaling (e.g., DCI, medium access control-control element (MAC-CE), or some other control signaling). The UE 115 may be configured to monitor the linked PDCCH candidates 405-a and 405-b for DCI. In some examples, the UE 115 may perform soft combining before receiving DCI via both the linked PDCCH candidates 405-a and 405-b. The PDCCH candidates 405-a and 405-b may each include a set of PDCCH resources 435 (e.g., time and frequency resources allocated for PDCCH). The PDCCH resources 435 of the first PDCCH candidate 405-a may or may not be contiguous in time and frequency with the PDCCH resources 435 of the second PDCCH candidate 405-b. In some examples, the PDCCH candidates 405 may be referred to as downlink control channel candidates.

[0110]

[0122] As described herein, the UE 115 may receive a PDCCH command via a first PDCCH candidate 405-a, a second PDCCH candidate 405-b linked with the first PDCCH candidate 405-a for PDCCH repetitions, or both (e.g., if the UE 115 soft-combines the PDCCH candidates 405) according to one or more rules regarding reception of a PDCCH command via the linked PDCCH candidate 405. The one or more rules may be configured (e.g., pre-configured) at the UE 115. Additionally or alternatively, the UE 115 may receive an indication of the one or more rules via control signaling from the base station 105 or some other network entity.

[0111]

[0123] In some examples, the one or more rules may indicate a timeline for the UE 115 to perform a random access procedure in response to a PDCCH command received via the linked PDCCH candidate 405. Performing the random access procedure may include transmitting, by the UE 115, an uplink random access message (e.g., Msg1) during a PRACH occasion 410-a (e.g., a set of PRACH resources 440 allocated for transmitting an uplink random access message). The uplink random access message may be an example of a random access request message 230 described with reference to FIG. 2.

[0112]

[0124] The one or more rules may indicate that the threshold delay period 420-a between the PDCCH command and the PRACH occasion 410-a starts after the last symbol of the reference PDCCH candidate 405 of the linked PDCCH candidate 405. That is, the reference PDCCH candidate 405 may trigger the threshold delay period 420-a. The reference PDCCH candidate 405 may, in some examples, correspond to a PDCCH candidate 405 that ends later in time. With reference to FIG. 4A, the second PDCCH candidate 405-b may end later in time than the first PDCCH candidate 405-a, and thus the threshold delay period 420-a may start after the last symbol of the second PDCCH candidate 405-b. The second PDCCH candidate 405-b may thereby be referred to as the reference PDCCH candidate 405-b. In some examples, the second PDCCH candidate 405-b may start earlier but end later in time than the first PDCCH candidate 405-a. The threshold delay period 420-a may start after the last symbol of the reference PDCCH candidate 405-b (e.g., the PDCCH candidate 405 that ends later in time), regardless of whether the first PDCCH candidate 405-a or the second PDCCH candidate 405-b starts earlier in time and regardless of whether a PDCCH command is received in the first PDCCH candidate 405-a, the second PDCCH candidate 405-b, or both.

[0113]

[0125] In some examples, the threshold delay period 420-a may be a first time period (e.g., N2) for PUSCH preparation according to the capability of the UE 115 (e.g., processing capability 1), a second time period (e.g., Δ Delay ) (e.g., a delay period of 0.5 ms for FR1, 0.25 ms for FR2, or some other delay period), a third time period for BWP switching (e.g., Δ BWPSwitching ), a fourth time period for uplink switching (e.g., T Switch ), or a combination thereof. In some examples, the third and / or fourth time periods may be 0 in the absence of a BWP switch or an uplink switch, respectively.

[0114]

[0126] The UE 115 may transmit an uplink random access message to the base station 105 via the PRACH resource 440 during the identified PRACH occasion 410-a. The PRACH occasion 410-a may start at or after expiration of the threshold delay period 420-a. If the PDCCH command triggers the CFRA, the UE 115 may determine the PRACH occasion 410-a (e.g., the timing of the PRACH occasion 410-a, such as the start symbol of the PRACH occasion 410-a) based on an indication received via the PDCCH command. For example, the PRACH occasion 410-a may be indicated via the SSB index field of the PDCCH command, the PRACH mask index field of the PDCCH command, or both, as described with reference to FIG. 2. If a PDCCH command triggers the CBRA, the UE 115 may determine the PRACH occasion 410-a (eg, the timing of the PRACH occasion 410-a, such as the starting symbol of the PRACH occasion 410-a) based on the measured SSB.

[0115]

[0127] In some examples, the linked PDCCH candidates 405-a and 405-b may correspond to the same TCI state. For example, the PDCCH candidates 405-a and 405-b may correspond to a first search space set and a second search space set associated with the same CORESET and corresponding TCI state, respectively. Additionally or alternatively, the first and second PDCCH candidates 405-a and 405-b may correspond to a first and a second search space set associated with a first and a second CORESET, respectively, each corresponding to the same TCI state. In such a case, the UE 115 may use the TCI state as a basis for the QCL assumption 425-a to be applied to the reception of one or more downlink random access messages. The TCI state may correspond to a beam used for the reception of control information via the respective PDCCH candidate 405.

[0116]

[0128] In another example, the first PDCCH candidate 405-a may be associated with a first TCI state and the second PDCCH candidate 405-b may be associated with a second TCI state that is different from the first TCI state (e.g., the PDCCH candidates 405 may correspond to different CORESETs associated with different TCI states), and the one or more rules may provide instructions for the UE 115 to identify a QCL assumption 425-a to be applied to reception of one or more downlink random access messages. The QCL assumption 425-a may be associated with at least one of the first TCI state and the second TCI state.

[0117]

[0129] The downlink random access message may include a DCI transmitted over a PDCCH candidate 405-c including a PDCCH resource 435, an RAR message transmitted over a PDSCH resource 445 during a PDSCH occasion 415-a, or both. The DCI (e.g., DCI format 1_0) may include a CRC scrambled by a random access radio network temporary identifier (RA-RNTI). The DCI may schedule a PDSCH occasion 415-a for transmission of the RAR message. The RAR message (e.g., a downlink RAR message) may be transmitted by the base station 105 in response to the uplink random access message.

[0118]

[0130] In the example random access timeline 400-a, one or more rules may instruct the UE 115 to select one of a first TCI state associated with a first PDCCH candidate 405-a or a second TCI state associated with a second PDCCH candidate 405-b as a basis for the QCL assumption 425-a based on one or more parameters. In one example, the rules may specify that the selection of the first or second TCI state is based on the relative timing of the first PDCCH candidate 405-a and the second PDCCH candidate 405-b. For example, the rules may specify that the selection of the TCI state is based on which PDCCH candidate 405 starts earlier in time, starts later in time, ends earlier in time, or ends later in time. In one example, if the rules specify that the selection is based on which PDCCH candidate 405 ends later in time, the UE 115 may select a second TCI state associated with the second PDCCH candidate 405-b as the basis for the QCL assumption 425-a.

[0119]

[0131] In another example, the rule may specify that the selection of the first or second TCI state is based on the relative value of a first search space set ID of a first search space set corresponding to (e.g., including) the first PDCCH candidate 405-a and a second search space set ID of a second search space set corresponding to (e.g., including) the second PDCCH candidate 405-b. The rule may specify that the selection of the TCI state is based on which search space set ID has a higher value or which search space set ID has a lower value. In one example, the value of the first search space set ID may be less than the value of the second search space set ID. If the rule specifies that the selection is based on which search space ID has a lower value, the UE 115 selects the first TCI state associated with the first PDCCH candidate 405-a as the basis for the QCL hypothesis 425-a.

[0120]

[0132] In another example, the rule may specify that the selection of the first or second TCI state is based on the relative values ​​of a first CORESET ID associated with a first search space set corresponding to (e.g., including) the first PDCCH candidate 405-a and a second CORESET ID associated with a second search space set corresponding to (e.g., including) the second PDCCH candidate 405-b. The rule may specify that the selection of the TCI state is based on which CORESET ID has a higher value or which CORESET ID has a lower value. In one example, the value of the second CORESET ID may be greater than the value of the first CORESET ID. If the rule specifies that the selection is based on which CORESET ID has a greater value, the UE 115 selects the second TCI state associated with the second PDCCH candidate 405-b as the basis for the QCL assumption 425-a.

[0121]

[0133] In another example, the rule may specify that the selection of the first or second TCI state is based on the relative value of a first TCI state ID associated with the first TCI state of the first PDCCH candidate 405-a and a second TCI state ID associated with the second TCI state of the second PDCCH candidate 405-b. The rule may specify that the selection of the TCI state is based on which TCI state ID has a higher value or which TCI state ID has a lower value. In one example, a first value of the first TCI state may be lower than a second value of the second TCI state. If the rule specifies that the selection is based on which TCI state ID has a lower value, the UE 115 selects the first TCI state associated with the first PDCCH candidate 405-a as the basis for the QCL assumption 425-a. Although four example parameters for selecting a TCI state are described, it should be understood that one or more rules may specify any amount of parameters or identifiers for selection of a TCI state to be used as the basis for QCL hypothesis 425-a.

[0122]

[0134] The one or more parameters for selecting a TCI state from a first TCI state associated with the first PDCCH candidate 405-a or a second TCI state associated with the second PDCCH candidate 405-b may be applicable if the PDCCH command triggers a CFRA on a primary cell (PCell), a primary secondary cell (PSCell), or both (e.g., a random access preamble index in the PDCCH command is not 0). Otherwise, the TCI state for identifying a QCL assumption 425-a for reception of a downlink message may not depend on one or more TCI states associated with the PDCCH command, and the UE 115 may identify the QCL assumption 425-a based on a measured SSB or some other signaling.

[0123]

[0135] For example, if a PDCCH command triggers CBRA, the dependency of the QCL assumption 425-a on a first TCI state associated with the first PDCCH candidate 405-a, a second TCI state associated with the second PDCCH candidate 405-b, or both may not be applicable, and the UE 115 may identify the QCL assumption 425-a based on a measured SSB associated with the CBRA procedure. If a PDCCH command triggers CBRA on a SCell, the PDCCH command may be received on the SCell, and a DCI with RA-RNTI and a corresponding RAR message may be received on the PCell. Thus, the TCI state associated with reception of the PDCCH command on the SCell may not apply to reception of the DCI, the RAR message, or both, on the PCell.

[0124]

[0136] Thus, in the example of FIG. 4A, the UE 115 may be configured with one or more rules for receiving a PDCCH command via the linked PDCCH candidates 405-a and 405-b and performing a random access procedure in response to the PDCCH command, as illustrated by the random access timeline 400-a. The one or more rules may indicate a timeline for performing a random access procedure in response to the PDCCH command. Additionally or alternatively, the one or more rules may specify guidelines for selecting a TCI state from a first TCI state or a second TCI state associated with the first and second linked PDCCH candidates 405-a and 405-b, respectively, to use as a basis for a QCL assumption 425-a to be applied to reception of one or more downlink random access messages.

[0125]

[0137] 4B illustrates a second random access timeline 400-b supporting downlink control channel repetition for downlink control channel commands according to an aspect of the disclosure. The random access timeline 400-b may be an example of the random access timeline 400-a described with reference to FIG. 4A. For example, the random access timeline 400-b may illustrate a timeline for receiving PDCCH commands, transmitting uplink random access messages, and receiving one or more downlink random access messages via at least one of the linked PDCCH candidates 405-d and 405-e according to the QCL assumption 425-b.

[0126]

[0138] The UE 115 may receive an indication that the first PDCCH candidate 405-d and the second PDCCH candidate 405-e are linked for PDCCH repetition, and the UE 115 may receive a PDCCH command via the first PDCCH candidate 405-d, the second PDCCH candidate 405-e, or both, according to one or more rules regarding reception of a PDCCH command via the linked PDCCH candidate 405. The one or more rules may specify that a threshold delay period 420-b between receiving a PDCCH command during a PRACH occasion 410-b and transmitting an uplink random access message may begin after the last symbol of a PDCCH candidate 405 that ends later in time (e.g., the second PDCCH candidate 405-e), as described with reference to FIG.

[0127]

[0139] The first PDCCH candidate 405-d may be associated with a first TCI state, and the second PDCCH candidate 405-e may be associated with a second TCI state that is different from the first TCI state (e.g., PDCCH commands may be received via different beams in each PDCCH candidate 405-d and 405-e). The UE 115 may identify a QCL assumption 425-b to be applied to reception of one or more downlink random access messages according to one or more rules. In the example of the random access timeline 400-b, the QCL assumption 425-b may correspond to both the first TCI state and the second TCI state according to one or more rules. The UE 115 may select both the first TCI state associated with the first PDCCH candidate 405-d and the second TCI state associated with the second PDCCH candidate 405-e as a basis for the QCL assumption 425-b to be applied to reception of the DCI, the reception of the RAR message, or both. For example, the one or more rules may specify that if a corresponding downlink random access message to which the first and second TCI states may apply is transmitted via two PDCCH candidates 405 that are linked for PDCCH repetition, via a multi-TCI state PDSCH, or both, then both the first and second TCI states associated with the linked first and second PDCCH candidates 405-d and 405-e may be used as a basis for the QCL assumption 425-b.

[0128]

[0140] In the random access timeline 400-b, DCI having an RA-RNTI may be received via the third PDCCH candidate 405-f, the fourth PDCCH candidate 405-g, or both, which are linked for PDCCH repetition. The UE 115 may receive an indication that the third PDCCH candidate 405-f and the fourth PDCCH candidate 405-g are linked. The UE 115 may accordingly select both the first TCI state associated with the first PDCCH candidate 405-d and the second TCI state associated with the second PDCCH candidate 405-e as a basis for the QCL assumption 425-b to be applied to reception of DCI via the third and fourth PDCCH candidates 405-f and 405-g.

[0129]

[0141] In some examples, the one or more rules may specify that if the RAR message is received over a multi-TCI state PDSCH that varies in one or more of spatial division multiplexing (SDM), FDM, TDM, or single frequency network manner, a first and second TCI state may be selected as a basis for the QCL assumption 425-b to be applied to the reception of the RAR message scheduled by the DCI with RA-RNTI (e.g., each DMRS port and each data layer of the PDSCH may be associated with a first and second TCI state). In the example of random access timeline 400-b, the RAR message may be received over a first PDSCH occasion 415-b including a first set of PDSCH resources 445 and a second PDSCH occasion 415-c including a second set of PDSCH resources 445. That is, in the example of FIG. 4B, the RAR message may be transmitted over a multi-TCI state PDSCH using TDM. The UE 115 may accordingly select both the first TCI state and the second TCI state as a basis for the QCL assumption 425-b, and the UE 115 may apply the QCL assumption 425-b to receiving the RAR message.

[0130]

[0142] The one or more rules for selecting the first and second TCI states as the basis for the QCL assumption 425-b may be applicable if the PDCCH command triggers a CFRA on the PCell, the PSCell, or both (e.g., the random access preamble index in the PDCCH command is not 0). Otherwise, as described in further detail with reference to FIG. 4A, the TCI state for identifying the QCL assumption 425-b for reception of the downlink message may not depend on the one or more TCI states associated with the PDCCH command, and the UE 115 may identify the QCL assumption 425-b based on a measured SSB, or some other signaling.

[0131]

[0143] Thus, the UE 115 described herein may be configured with one or more rules for receiving a PDCCH command via two or more linked PDCCH candidates and performing a random access procedure with the base station 105 corresponding to the PDCCH command. The one or more rules may indicate a timeline for performing a random access procedure in response to a PDCCH command received via a linked PDCCH candidate, as described with reference to random access timelines 400-a and 400-b, the one or more rules may specify a QCL assumption 425 to use for reception of a downlink random access message in response to a PDCCH command received via a linked PDCCH candidate, or both. That is, the one or more rules may relate to receiving, processing, and responding to a PDCCH command received via a linked PDCCH candidate.

[0132]

[0144] Additionally or alternatively, the one or more rules may specify whether a PDCCH command may be received by the UE 115 via a linked PDCCH candidate 405. For example, the one or more rules may specify that the UE 115 may not be expected to receive a PDCCH command via two PDCCH candidates 405 that are linked for repetition (e.g., a PDCCH command with PDCCH repetition may not be allowed). In such a case, the UE 115 may receive a PDCCH command via a PDCCH candidate 405 that is not linked with the other PDCCH candidate 405 for PDCCH repetition. Additionally or alternatively, the one or more rules may allow reception of a PDCCH command via two linked PDCCH candidates 405 if the PDCCH candidates correspond to the same TCI state, if the PDCCH command triggers a CBRA, if the PDCCH command triggers a CFRA on a SCell, or any combination thereof.

[0133]

[0145] 5 illustrates an example of a process flow 500 supporting downlink control channel repetition for downlink control channel commands according to aspects of the disclosure. The process flow 500 may implement or be implemented by certain aspects of the wireless communications systems 100 or 200. For example, the process flow 500 may include a UE 115-b and a base station 105-b, which may be examples of the UE 115 and the base station 105 described with reference to FIGS. 1-4. In some examples, the UE 115-b may be configured with one or more rules related to receiving PDCCH commands via linked PDCCH candidates.

[0134]

[0146] It should be understood that the devices and nodes described by process flow 500 may communicate with or be coupled to other devices or nodes not shown. For example, UE 115-b and base station 105-b may communicate with one or more other UEs 115, base stations 105, or other devices. Alternatives to the following may be implemented, with some steps performed in a different order than described, or not performed at all. In some cases, the steps may include additional features not described below, or further steps may be added.

[0135]

[0147] At 505, the base station 105-b may transmit, and the UE 115-b may receive, an indication of the linked downlink control channel candidates. For example, the UE 115-b may receive an indication that the first downlink control channel candidate and the second downlink control channel candidate are linked for a downlink control channel repetition (e.g., a PDCCH repetition).

[0136]

[0148] At 510, the base station 105-b may transmit a downlink control channel command requesting the UE 115-b to participate in the random access procedure, and the UE 115-b may receive the command. The downlink control channel command may be transmitted and received via one or both of the first downlink control channel candidate and the second downlink control channel candidate.

[0137]

[0149] At 515, the UE 115-b and the base station 105-b may perform a random access procedure related to the downlink control channel commands according to one or more rules regarding reception of the downlink control channel commands via the linked downlink control channel candidates. In some examples, performing the random access procedure at 515 may include transmitting, by the UE 115-b, an uplink random access message (e.g., Msg1) to the base station 105-b according to the one or more rules.

[0138]

[0150] 6 illustrates an example of a process flow 600 supporting downlink control channel repetition for downlink control channel commands according to aspects of the disclosure. The process flow 600 may implement or be implemented by certain aspects of the wireless communications systems 100 or 200. For example, the process flow 600 may include a UE 115-c and a base station 105-c, which may be examples of the UE 115 and the base station 105 described with reference to FIGS. 1-5. In some examples, the UE 115-c may be configured with one or more rules related to receiving PDCCH commands via linked PDCCH candidates.

[0139]

[0151] It should be understood that the devices and nodes described by process flow 600 may communicate with or be coupled to other devices or nodes not shown. For example, UE 115-c and base station 105-c may communicate with one or more other UEs 115, base stations 105, or other devices. Alternatives to the following may be implemented, with some steps performed in a different order than described, or not performed at all. In some cases, the steps may include additional features not described below, or further steps may be added.

[0140]

[0152] At 605, the base station 105-c may transmit a downlink control channel command requesting the UE 115-c to participate in the random access procedure, and the UE 115-c may receive the command. The downlink control channel command may be received according to one or more rules regarding reception of the downlink control channel command via multiple downlink control channel candidates linked for the downlink control channel repetition. In some examples, the UE 115-c may receive the downlink control channel command via a downlink control channel candidate that is not linked with other downlink control channel candidates for the repetition according to one or more rules. Additionally or alternatively, the UE 115-c may receive the downlink control channel command via at least one of the first downlink control channel candidate or the second downlink control channel candidate linked for the downlink control channel repetition according to one or more rules.

[0141]

[0153] At 610, the base station 105-c and the UE 115-c may perform a random access procedure based on the downlink control channel commands received according to one or more rules. In some examples, performing the random access procedure at 605 may include transmitting, by the UE 115-c, an uplink random access message to the base station 105-c.

[0142]

[0154] 7 illustrates a block diagram 700 of a device 705 supporting downlink control channel repetition for downlink control channel commanding according to an aspect of the disclosure. The device 705 may be an example of an aspect of a UE 115 described herein. The device 705 may include a receiver 710, a transmitter 715, and a communications manager 720. The device 705 may also include one or more processors, memory coupled to the one or more processors, and instructions stored in the memory executable by the one or more processors to enable the one or more processors to perform the functions of the downlink control channel repetition described herein. Each of these components may be in communication with one another (e.g., via one or more buses).

[0143]

[0155] The receiver 710 may provide a means for receiving information such as packets, user data, control information, or any combination thereof, associated with various information channels (e.g., control channels, data channels, information channels related to downlink control channel repetitions for downlink control channel commands). The information may be passed to other components of the device 705. The receiver 710 may utilize a single antenna or a set of multiple antennas.

[0144]

[0156] The transmitter 715 may provide a means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information such as packets associated with various information channels (e.g., a control channel, a data channel, an information channel related to a downlink control channel iteration for downlink control channel commands), user data, control information, or any combination thereof. In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a set of multiple antennas.

[0145]

[0157] The communications manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be examples of means for performing various aspects of downlink control channel repetition for downlink control channel command described herein. For example, the communications manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may support a method for performing one or more of the functions described herein.

[0146]

[0158] In some examples, the communications manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be implemented in hardware (e.g., in a communications management circuit). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as a means for performing or otherwise supporting the functions described in this disclosure. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor, instructions stored in the memory).

[0147]

[0159] Additionally or alternatively, in some examples, the communications manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communications management software or firmware). When implemented in code executed by a processor, the functions of the communications manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be performed by a general-purpose processor (e.g., configured as or otherwise supporting a means for performing the functions described in this disclosure), a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices.

[0148]

[0160] In some examples, the communications manager 720 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise cooperating with the receiver 710, the transmitter 715, or both. For example, the communications manager 720 may receive information from the receiver 710, send information to the transmitter 715, or be integrated in combination with the receiver 710, the transmitter 715, or both to receive information, transmit information, or perform various other operations described herein.

[0149]

[0161] The communications manager 720 may support wireless communications in the UE according to examples disclosed herein. For example, the communications manager 720 may be configured as or otherwise support a means for receiving an indication that a first downlink control channel candidate and a second downlink control channel candidate are linked for downlink control channel iterations. The communications manager 720 may be configured as or otherwise support a means for receiving a downlink control channel command requesting the UE to participate in a random access procedure via one or both of the first downlink control channel candidate and the second downlink control channel candidate. The communications manager 720 may be configured as or otherwise support a means for performing a random access procedure associated with the downlink control channel command according to one or more rules regarding reception of the downlink control channel command via the linked downlink control channel candidate.

[0150]

[0162] Additionally or alternatively, communications manager 720 may support wireless communications in a UE according to examples disclosed herein. For example, communications manager 720 may be configured as or otherwise support a means for receiving downlink control channel commands requesting the UE to participate in a random access procedure, the downlink control channel commands being received according to one or more rules regarding reception of the downlink control channel commands via multiple downlink control channel candidates linked for downlink control channel repetition. Communications manager 720 may be configured as or otherwise support a means for performing a random access procedure based on the downlink control channel commands being received according to the one or more rules.

[0151]

[0163] By including or configuring a communications manager 720 according to examples described herein, the device 705 (e.g., a processor controlling or otherwise coupled to the receiver 710, the transmitter 715, the communications manager 720, or a combination thereof) may support techniques for reduced processing and more efficient utilization of communications resources. For example, by performing a random access procedure according to one or more configured rules for the device 705, the processor of the device 705 may perform more accurate transmission and reception, which may improve the reliability of the random access procedure and thereby reduce processing (e.g., by reducing the amount of retransmissions). In some examples, the processor of the device 705 may receive and decode DCI received via a linked PDCCH candidate, which may improve the reliability of the DCI, enable more efficient utilization of communications resources, and reduce processing.

[0152]

[0164] 8 illustrates a block diagram 800 of a device 805 supporting downlink control channel repetition for downlink control channel commanding according to an aspect of the disclosure. The device 805 may be an example of an aspect of a device 705 or a UE 115 described herein. The device 805 may include a receiver 810, a transmitter 815, and a communications manager 820. The device 805 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0153]

[0165] The receiver 810 may provide a means for receiving information such as packets, user data, control information, or any combination thereof, associated with various information channels (e.g., control channels, data channels, information channels related to downlink control channel repetitions for downlink control channel commands). The information may be passed to other components of the device 805. The receiver 810 may utilize a single antenna or a set of multiple antennas.

[0154]

[0166] The transmitter 815 may provide a means for transmitting signals generated by other components of the device 805. For example, the transmitter 815 may transmit information such as packets associated with various information channels (e.g., a control channel, a data channel, an information channel related to a downlink control channel iteration for downlink control channel commands), user data, control information, or any combination thereof. In some examples, the transmitter 815 may be co-located with the receiver 810 in a transceiver module. The transmitter 815 may utilize a single antenna or a set of multiple antennas.

[0155]

[0167] The device 805, or various components thereof, may be an example of a means for performing various aspects of downlink control channel repetition for downlink control channel command described herein. For example, the communications manager 820 may include a linked PDCCH identification component 825, a PDCCH command component 830, a random access procedure component 835, or any combination thereof. The communications manager 820 may be an example of an aspect of the communications manager 720 described herein. In some examples, the communications manager 820, or various components thereof, may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or in cooperation with the receiver 810, the transmitter 815, or both. For example, the communications manager 820 may be integrated in combination with the receiver 810, the transmitter 815, or both to receive information from the receiver 810, send information to the transmitter 815, or receive information, transmit information, or perform various other operations described herein.

[0156]

[0168] The communications manager 820 may support wireless communications in the UE according to examples disclosed herein. The linked PDCCH identification component 825 may be configured as or otherwise support a means for receiving an indication that the first downlink control channel candidate and the second downlink control channel candidate are linked for downlink control channel repetition. The PDCCH command component 830 may be configured as or otherwise support a means for receiving a downlink control channel command requesting the UE to participate in a random access procedure via one or both of the first downlink control channel candidate and the second downlink control channel candidate. The random access procedure component 835 may be configured as or otherwise support a means for performing a random access procedure associated with the downlink control channel command according to one or more rules regarding reception of the downlink control channel command via the linked downlink control channel candidate.

[0157]

[0169] Additionally or alternatively, the communications manager 820 may support wireless communications in the UE according to examples disclosed herein. The PDCCH command component 830 may be configured as or otherwise support a means for receiving downlink control channel commands requesting the UE to participate in a random access procedure, the downlink control channel commands being received according to one or more rules regarding reception of the downlink control channel commands via multiple downlink control channel candidates linked for downlink control channel repetition. The random access procedure component 835 may be configured as or otherwise support a means for performing a random access procedure based on the downlink control channel commands being received according to one or more rules.

[0158]

[0170] In some cases, the linked PDCCH identification component 825, the PDCCH command component 830, the random access procedure component 835, or any combination thereof, may each be, or at least a part of, a processor (e.g., a transceiver processor, or a radio processor, or a transmitter processor, or a receiver processor). The processor may be coupled to a memory and execute instructions stored in the memory that enable the processor to perform or facilitate the functions of the linked PDCCH identification component 825, the PDCCH command component 830, and the random access procedure component 835 described herein. The transceiver processor may be co-located with and / or in communication with (e.g., direct the operation of) the transceiver of the device. The radio processor may be co-located with and / or in communication with (e.g., direct the operation of) the radio of the device (e.g., NR radio, LTE radio, Wi-Fi radio). The transmitter processor may be co-located with and / or in communication with (e.g., direct the operation of) the transmitter of the device. The receiver processor may be co-located with and / or in communication with (eg, may direct the operation of) the receiver of the device.

[0159]

[0171] FIG. 9 illustrates a block diagram 900 of a communications manager 920 supporting downlink control channel repetition for downlink control channel commanding according to an aspect of the disclosure. Communications manager 920 may be an example of an aspect of communications manager 720, communications manager 820, or both described herein. Communications manager 920, or various components thereof, may be an example of a means for performing various aspects of downlink control channel repetition for downlink control channel commanding described herein. For example, communications manager 920 may include a linked PDCCH identification component 925, a PDCCH command component 930, a random access procedure component 935, an uplink random access message component 940, a QCL assumption component 945, a downlink random access message component 950, a TCI selection component 955, or any combination thereof. Each of these components may communicate with one another directly or indirectly (e.g., via one or more buses).

[0160]

[0172] The communications manager 920 may support wireless communications in the UE according to examples disclosed herein. The linked PDCCH identification component 925 may be configured as or otherwise support a means for receiving an indication that the first downlink control channel candidate and the second downlink control channel candidate are linked for downlink control channel repetition. The PDCCH command component 930 may be configured as or otherwise support a means for receiving a downlink control channel command requesting the UE to participate in a random access procedure via one or both of the first downlink control channel candidate and the second downlink control channel candidate. The random access procedure component 935 may be configured as or otherwise support a means for performing a random access procedure associated with the downlink control channel command according to one or more rules regarding reception of the downlink control channel command via the linked downlink control channel candidate.

[0161]

[0173] In some examples, to support performing a random access procedure, the uplink random access message component 940 may be configured as or otherwise support a means for determining a random access occasion for transmission of an uplink random access message in response to a downlink control channel command. In some examples, to support performing a random access procedure, the uplink random access message component 940 may be configured as or otherwise support a means for transmitting an uplink random access message during a random access occasion based on a first symbol of the random access occasion that is after a threshold delay period that may be triggered by a reference downlink control channel candidate among the linked downlink control channel candidates. In some examples, the reference downlink control channel candidate may be a second downlink control channel candidate as a result of the second downlink control channel candidate ending later in time than the first downlink control channel candidate, and the one or more rules may indicate that the threshold delay period begins after the last symbol of the second downlink control channel candidate.

[0162]

[0174] In some examples, performing the random access procedure according to the one or more rules is independent of whether the downlink control channel command is received during the first downlink control channel candidate or the second downlink control channel candidate. In some examples, the threshold delay period includes a first time period for uplink shared channel preparation according to the UE's capabilities, a second time period for random access preparation, a third time period for BWP switching, a fourth time period for uplink switching, or a combination thereof. In some examples, to support determining the random access occasion, the uplink random access message component 940 may be configured as or otherwise support a means for determining the timing of the random access occasion based on an indication in the downlink control channel command or a measured SSB.

[0163]

[0175] In some examples, the downlink random access message component 950 may be configured with or otherwise support a means for receiving a downlink random access message in response to an uplink random access message, where the downlink random access message is either a downlink control channel message that schedules an RAR message or is an RAR message.

[0164]

[0176] In some examples, to support performing a random access procedure, the uplink random access message component 940 may be configured or otherwise support a means for transmitting an uplink random access message in response to a downlink control channel command, where a first downlink control channel candidate is associated with a first TCI state and a second downlink control channel candidate is associated with a second TCI state different from the first TCI state. In some examples, to support performing a random access procedure, the QCL assumption component 945 may be configured or otherwise support a means for identifying, according to one or more rules, a QCL assumption to be applied to reception of a downlink random access message in response to the uplink random access message, where the QCL assumption is associated with at least one of the first TCI state or the second TCI state.

[0165]

[0177] In some examples, to support identifying a QCL assumption, the TCI selection component 955 may be configured with or otherwise support a means for selecting one of the first TCI state or the second TCI state as a basis for the QCL assumption according to one or more rules, where the one or more rules specify that the selection of either the first TCI state or the second TCI state is based on the relative timing of the first downlink control channel candidate and the second downlink control channel candidate.

[0166]

[0178] In some examples, to support identifying a QCL assumption, the TCI selection component 955 may be configured with or otherwise support a means for selecting one of the first TCI state or the second TCI state as a basis for the QCL assumption according to one or more rules, where the one or more rules specify that the selection of either the first TCI state or the second TCI state is based on a relative value of a first search space set ID of a first search space set corresponding to a first downlink control channel candidate and a second search space set ID of a second search space set corresponding to a second downlink control channel candidate.

[0167]

[0179] In some examples, to support identifying a QCL assumption, the TCI selection component 955 may be configured with or otherwise support a means for selecting one of the first TCI state or the second TCI state as a basis for the QCL assumption according to one or more rules, where the one or more rules specify that the selection of either the first TCI state or the second TCI state is based on the relative values ​​of a first CORESET ID associated with a first search space set corresponding to a first downlink control channel candidate and a second CORESET ID associated with a second search space set corresponding to a second downlink control channel candidate.

[0168]

[0180] In some examples, to support identifying a QCL assumption, the TCI selection component 955 may be configured with or otherwise support a means for selecting one of the first TCI state or the second TCI state as a basis for the QCL assumption according to one or more rules, where the one or more rules specify that the selection of either the first TCI state or the second TCI state is based on the relative values ​​of a first TCI state ID associated with the first TCI state and a second TCI state ID associated with the second TCI state.

[0169]

[0181] In some examples, to support identifying a QCL assumption, the TCI selection component 955 may be configured with or otherwise support a means for selecting both the first TCI state and the second TCI state as a basis for the QCL assumption according to one or more rules, where the one or more rules specify that the downlink random access message to which the QCL assumption may be applied is a downlink control channel message that schedules a RAR message, and the downlink control channel message is transmitted via a third downlink control channel candidate and a fourth downlink control channel candidate that are linked for the downlink control channel repetition.

[0170]

[0182] In some examples, to support identifying a QCL assumption, the TCI selection component 955 may be configured with or otherwise support a means for selecting both the first TCI state and the second TCI state as a basis for the QCL assumption according to one or more rules, where the one or more rules specify that the downlink random access message to which the QCL assumption may be applied is a RAR message that is a multi-TCI state downlink shared channel that varies in at least one of spatial division multiplexing, FDM, TDM, or single frequency network schemes.

[0171]

[0183] In some examples, the downlink control channel command requests a CFRA procedure on the PCell or the PSCell, or both. In some examples, the downlink random access message is either a downlink control channel message that schedules a RAR message or is a RAR message.

[0172]

[0184] Additionally or alternatively, the communications manager 920 may support wireless communications in the UE according to examples disclosed herein. In some examples, the PDCCH command component 930 may be configured as or otherwise support a means for receiving downlink control channel commands requesting the UE to participate in a random access procedure, the downlink control channel commands being received according to one or more rules regarding reception of the downlink control channel commands via multiple downlink control channel candidates linked for downlink control channel repetition. In some examples, the random access procedure component 935 may be configured as or otherwise support a means for performing a random access procedure based on the downlink control channel commands being received according to one or more rules.

[0173]

[0185] In some examples, to support receiving downlink control channel commands according to one or more rules, the PDCCH command component 930 may be configured as or otherwise support a means for receiving downlink control channel commands via a downlink control channel candidate that is not linked with other downlink control channel candidates for repetition.

[0174]

[0186] In some examples, to support receiving downlink control channel commands according to one or more rules, the PDCCH command component 930 may be configured with or otherwise support a means for receiving downlink control channel commands via at least one of a first downlink control channel candidate or a second downlink control channel candidate linked for a downlink control channel iteration, where the first downlink control channel candidate corresponds to a first search space set associated with the CORESET and the second downlink control channel candidate corresponds to a second search space set associated with the CORESET.

[0175]

[0187] In some examples, to support receiving downlink control channel commands according to one or more rules, the PDCCH command component 930 may be configured with or otherwise support a means for receiving downlink control channel commands via at least one of a first downlink control channel candidate or a second downlink control channel candidate linked for a downlink control channel iteration, where the first downlink control channel candidate corresponds to a first search space set associated with a first CORESET having a TCI state and the second downlink control channel candidate corresponds to a second search space set associated with a second CORESET having a TCI state.

[0176]

[0188] In some examples, the downlink control channel command requests a CFRA procedure on the PCell or the PSCell, or both.

[0177]

[0189] In some cases, the linked PDCCH identification component 925, the PDCCH command component 930, the random access procedure component 935, the uplink random access message component 940, the QCL assumption component 945, the downlink random access message component 950, and the TCI selection component 955 may each be, or at least a part of, a processor (e.g., a transceiver processor, or a radio processor, or a transmitter processor, or a receiver processor). The processor may be coupled to a memory and execute instructions stored in the memory that enable the processor to perform or facilitate functions of the linked PDCCH identification component 925, the PDCCH command component 930, the random access procedure component 935, the uplink random access message component 940, the QCL assumption component 945, the downlink random access message component 950, and the TCI selection component 955 described herein.

[0178]

[0190] FIG. 10 illustrates a diagram of a system 1000 including a device 1005 supporting downlink control channel repetition for downlink control channel commanding according to an aspect of the disclosure. The device 1005 may be an example of or include a component of a device 705, a device 805, or a UE 115 described herein. The device 1005 may wirelessly communicate with one or more base stations 105, UEs 115, or any combination thereof. The device 1005 may include components for two-way voice and data communication, including components for transmitting and receiving communications, such as a communications manager 1020, an input / output (I / O) controller 1010, a transceiver 1015, an antenna 1025, a memory 1030, code 1035, and a processor 1040. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1045).

[0179]

[0191] The I / O controller 1010 may manage input and output signals for the device 1005. The I / O controller 1010 may also manage peripheral devices that are not built into the device 1005. In some cases, the I / O controller 1010 may represent a physical connection or port to an external peripheral device. In some cases, the I / O controller 1010 may utilize an operating system, such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. Additionally or alternatively, the I / O controller 1010 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, the I / O controller 1010 may be implemented as part of a processor, such as the processor 1040. In some cases, a user may interact with the device 1005 through the I / O controller 1010 or through hardware components controlled by the I / O controller 1010.

[0180]

[0192] In some cases, the device 1005 may include a single antenna 1025. However, in some other cases, the device 1005 may have two or more antennas 1025 that may be capable of simultaneously transmitting or receiving multiple wireless transmissions. The transceiver 1015 may communicate bidirectionally via one or more antennas 1025, wired links, or wireless links as described herein. For example, the transceiver 1015 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1015 may also include a modem for modulating packets and providing the modulated packets to the one or more antennas 1025 for transmission, and for demodulating packets received from the one or more antennas 1025. The transceiver 1015, or the transceiver 1015 and the one or more antennas 1025, may be an example of the transmitter 715, transmitter 815, receiver 710, receiver 810, or any combination or components thereof described herein.

[0181]

[0193] The memory 1030 may include random access memory (RAM) and read only memory (ROM). The memory 1030 may store computer readable, computer executable code 1035 including instructions that, when executed by the processor 1040, cause the device 1005 to perform various functions described herein. The code 1035 may be stored in a non-transitory computer readable medium, such as a system memory or another type of memory. In some cases, the code 1035 may not be directly executable by the processor 1040, but may (e.g., when compiled and executed) cause the computer to perform functions described herein. In some cases, the memory 1030 may include a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices, among other things.

[0182]

[0194] The processor 1040 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 1040 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be incorporated into the processor 1040. The processor 1040 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1030) to cause the device 1005 to perform various functions (e.g., functions or tasks supporting downlink control channel iterations related to downlink control channel commands). For example, the device 1005 or a component of the device 1005 may include the processor 1040 and the memory 1030 coupled to the processor 1040, where the processor 1040 and the memory 1030 are configured to perform various functions described herein.

[0183]

[0195] The communications manager 1020 may support wireless communications in the UE according to examples disclosed herein. For example, the communications manager 1020 may be configured as or otherwise support a means for receiving an indication that a first downlink control channel candidate and a second downlink control channel candidate are linked for downlink control channel iterations. The communications manager 1020 may be configured as or otherwise support a means for receiving a downlink control channel command requesting the UE to participate in a random access procedure via one or both of the first downlink control channel candidate and the second downlink control channel candidate. The communications manager 1020 may be configured as or otherwise support a means for performing a random access procedure associated with the downlink control channel command according to one or more rules regarding reception of the downlink control channel command via the linked downlink control channel candidate.

[0184]

[0196] Additionally or alternatively, the communications manager 1020 may support wireless communications in the UE according to examples disclosed herein. For example, the communications manager 1020 may be configured as or otherwise support a means for receiving downlink control channel commands requesting the UE to participate in a random access procedure, the downlink control channel commands being received according to one or more rules regarding reception of the downlink control channel commands via multiple downlink control channel candidates linked for downlink control channel repetition. The communications manager 1020 may be configured as or otherwise support a means for performing a random access procedure based on the downlink control channel commands being received according to the one or more rules.

[0185]

[0197] By including or configuring the communications manager 1020 according to examples described herein, the device 1005 may support techniques for improved communication reliability and improved coordination between devices. For example, the device 1005 may be configured with one or more rules regarding reception of PDCCH commands over linked PDCCH candidates. By receiving the PDCCH commands and performing a corresponding random access procedure according to the one or more rules, the device 1005 may accurately determine a timeline for performing the random access procedure, a QCL assumption for the random access procedure, or both, which may improve communication reliability and coordination between devices (e.g., between the UE 115 and the base station 105).

[0186]

[0198] In some examples, the communications manager 1020 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise cooperating with the transceiver 1015, one or more antennas 1025, or any combination thereof. Although the communications manager 1020 is shown as a separate component, in some examples, one or more functions described with reference to the communications manager 1020 may be supported by or performed by the processor 1040, the memory 1030, the code 1035, or any combination thereof. For example, the code 1035 may include instructions executable by the processor 1040 to cause the device 1005 to perform various aspects of downlink control channel iterations related to the downlink control channel commands described herein, or the processor 1040 and the memory 1030 may be configured to perform or support such operations, as the case may be.

[0187]

[0199] FIG. 11 illustrates a block diagram 1100 of a device 1105 supporting downlink control channel repetition for downlink control channel command according to an aspect of the disclosure. The device 1105 may be an example of an aspect of a base station 105 described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communications manager 1120. The device 1105 may also include one or more processors, memory coupled to the one or more processors, and instructions stored in the memory executable by the one or more processors to enable the one or more processors to perform the downlink control channel command repetition functionality described herein. Each of these components may be in communication with one another (e.g., via one or more buses).

[0188]

[0200] The receiver 1110 may provide a means for receiving information such as packets, user data, control information, or any combination thereof, associated with various information channels (e.g., control channels, data channels, information channels related to downlink control channel repetitions for downlink control channel commands). The information may be passed to other components of the device 1105. The receiver 1110 may utilize a single antenna or a set of multiple antennas.

[0189]

[0201] The transmitter 1115 may provide a means for transmitting signals generated by other components of the device 1105. For example, the transmitter 1115 may transmit information such as packets associated with various information channels (e.g., a control channel, a data channel, an information channel related to a downlink control channel iteration for downlink control channel commands), user data, control information, or any combination thereof. In some examples, the transmitter 1115 may be co-located with the receiver 1110 in a transceiver module. The transmitter 1115 may utilize a single antenna or a set of multiple antennas.

[0190]

[0202] The communications manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be examples of means for performing various aspects of downlink control channel repetition for downlink control channel command described herein. For example, the communications manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may support a method for performing one or more of the functions described herein.

[0191]

[0203] In some examples, the communications manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be implemented in hardware (e.g., in a communications management circuit). The hardware may include a processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting means for performing the functions described in this disclosure. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor, instructions stored in the memory).

[0192]

[0204] Additionally or alternatively, in some examples, the communications manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communications manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof or other programmable logic device (e.g., configured as or otherwise supporting a means for performing the functions described in this disclosure).

[0193]

[0205] In some examples, the communications manager 1120 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or in cooperation with the receiver 1110, the transmitter 1115, or both. For example, the communications manager 1120 may receive information from the receiver 1110, send information to the transmitter 1115, or be integrated in combination with the receiver 1110, the transmitter 1115, or both to receive information, transmit information, or perform various other operations described herein.

[0194]

[0206] The communications manager 1120 may support wireless communications in a base station according to examples disclosed herein. For example, the communications manager 1120 may be configured as or otherwise support a means for transmitting an indication to a UE that a first downlink control channel candidate and a second downlink control channel candidate are linked for downlink control channel iteration. The communications manager 1120 may be configured as or otherwise support a means for transmitting a downlink control channel command to a UE via one or both of the first downlink control channel candidate and the second downlink control channel candidate requesting the UE to participate in a random access procedure. The communications manager 1120 may be configured as or otherwise support a means for receiving an uplink random access message associated with the downlink control channel command from the UE according to one or more rules regarding the transmission of the downlink control channel command via the linked downlink control channel candidate.

[0195]

[0207] Additionally or alternatively, the communications manager 1120 may support wireless communications in the base station according to examples disclosed herein. For example, the communications manager 1120 may be configured as or otherwise support a means for transmitting a downlink control channel command to a UE requesting the UE to participate in a random access procedure, the downlink control channel command being transmitted according to one or more rules regarding reception of the downlink control channel command via multiple downlink control channel candidates linked for downlink control channel repetition. The communications manager 1120 may be configured as or otherwise support a means for receiving a random access message from the UE based on the downlink control channel command being transmitted according to the one or more rules.

[0196]

[0208] 12 illustrates a block diagram 1200 of a device 1205 supporting downlink control channel repetition for downlink control channel commanding according to an aspect of the disclosure. The device 1205 may be an example of an aspect of the device 1105 or base station 105 described herein. The device 1205 may include a receiver 1210, a transmitter 1215, and a communications manager 1220. The device 1205 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0197]

[0209] The receiver 1210 may provide a means for receiving information such as packets, user data, control information, or any combination thereof, associated with various information channels (e.g., control channels, data channels, information channels related to downlink control channel repetitions for downlink control channel commands). The information may be passed to other components of the device 1205. The receiver 1210 may utilize a single antenna or a set of multiple antennas.

[0198]

[0210] The transmitter 1215 may provide a means for transmitting signals generated by other components of the device 1205. For example, the transmitter 1215 may transmit information such as packets associated with various information channels (e.g., a control channel, a data channel, an information channel related to a downlink control channel iteration for downlink control channel commands), user data, control information, or any combination thereof. In some examples, the transmitter 1215 may be co-located with the receiver 1210 in a transceiver module. The transmitter 1215 may utilize a single antenna or a set of multiple antennas.

[0199]

[0211] The device 1205, or various components thereof, may be an example of a means for performing various aspects of downlink control channel repetition for downlink control channel command described herein. For example, the communications manager 1220 may include a linked PDCCH identification component 1225, a PDCCH command component 1230, an uplink random access message component 1235, or any combination thereof. The communications manager 1220 may be an example of an aspect of the communications manager 1120 described herein. In some examples, the communications manager 1220, or various components thereof, may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or in cooperation with the receiver 1210, the transmitter 1215, or both. For example, the communications manager 1220 may be integrated in combination with the receiver 1210, the transmitter 1215, or both to receive information from the receiver 1210, send information to the transmitter 1215, or receive information, transmit information, or perform various other operations described herein.

[0200]

[0212] The communications manager 1220 may support wireless communications in the base station according to examples disclosed herein. The linked PDCCH identification component 1225 may be configured as or otherwise support a means for transmitting an indication to the UE that the first downlink control channel candidate and the second downlink control channel candidate are linked for downlink control channel repetition. The PDCCH command component 1230 may be configured as or otherwise support a means for transmitting a downlink control channel command to the UE via one or both of the first downlink control channel candidate and the second downlink control channel candidate requesting the UE to participate in a random access procedure. The uplink random access message component 1235 may be configured as or otherwise support a means for receiving an uplink random access message associated with the downlink control channel command from the UE according to one or more rules regarding transmission of the downlink control channel command via the linked downlink control channel candidate.

[0201]

[0213] Additionally or alternatively, the communications manager 1220 may support wireless communications in the base station according to examples disclosed herein. The PDCCH command component 1230 may be configured as or otherwise support a means for transmitting a downlink control channel command to the UE requesting the UE to participate in a random access procedure, the downlink control channel command being transmitted according to one or more rules regarding reception of the downlink control channel command via multiple downlink control channel candidates linked for downlink control channel repetition. The uplink random access message component 1235 may be configured as or otherwise support a means for receiving a random access message from the UE based on the downlink control channel command being transmitted according to one or more rules.

[0202]

[0214] In some cases, the linked PDCCH identification component 1225, the PDCCH command component 1230, and the uplink random access message component 1235 may each be, or at least a part of, a processor (e.g., a transceiver processor, or a radio processor, or a transmitter processor, or a receiver processor). The processor may be coupled to a memory and may execute instructions stored in the memory that enable the processor to perform or facilitate the functions of the linked PDCCH identification component 1225, the PDCCH command component 1230, and the uplink random access message component 1235 described herein. The transceiver processor may be co-located with and / or in communication with (e.g., may direct the operation of) a transceiver of the device. The radio processor may be co-located with and / or in communication with (e.g., may direct the operation of) a radio (e.g., NR radio, LTE radio, Wi-Fi radio) of the device. The transmitter processor may be co-located with and / or in communication with (e.g., may direct the operation of) a transmitter of the device. The receiver processor may be co-located with and / or in communication with (eg, may direct the operation of) the receiver of the device.

[0203]

[0215] FIG. 13 illustrates a block diagram 1300 of a communications manager 1320 supporting downlink control channel repetition for downlink control channel commanding according to aspects of the disclosure. The communications manager 1320 may be an example of aspects of the communications manager 1120, the communications manager 1220, or both described herein. The communications manager 1320, or various components thereof, may be an example of a means for performing various aspects of the downlink control channel repetition for downlink control channel commanding described herein. For example, the communications manager 1320 may include a linked PDCCH identification component 1325, a PDCCH command component 1330, an uplink random access message component 1335, a QCL assumption component 1340, a downlink random access message component 1345, a TCI state selection component 1350, or any combination thereof. Each of these components may communicate with one another directly or indirectly (e.g., via one or more buses).

[0204]

[0216] The communications manager 1320 may support wireless communications in the base station according to examples disclosed herein. The linked PDCCH identification component 1325 may be configured as or otherwise support a means for transmitting an indication to the UE that the first downlink control channel candidate and the second downlink control channel candidate are linked for downlink control channel repetition. The PDCCH command component 1330 may be configured as or otherwise support a means for transmitting a downlink control channel command to the UE via one or both of the first downlink control channel candidate and the second downlink control channel candidate requesting the UE to participate in a random access procedure. The uplink random access message component 1335 may be configured as or otherwise support a means for receiving an uplink random access message associated with the downlink control channel command from the UE according to one or more rules regarding the transmission of the downlink control channel command via the linked downlink control channel candidate.

[0205]

[0217] In some examples, to support receiving an uplink random access message, the uplink random access message component 1335 may be configured as or otherwise support a means for receiving an uplink random access message during a random access occasion based on a first symbol of the random access occasion that is after a threshold delay period that may be triggered by a reference downlink control channel candidate among the linked downlink control channel candidates. In some examples, the reference downlink control channel candidate may be a second downlink control channel candidate as a result of the second downlink control channel candidate ending later in time than the first downlink control channel candidate, and one or more rules may indicate that the threshold delay period begins after the last symbol of the second downlink control channel candidate.

[0206]

[0218] In some examples, receiving an uplink random access message according to the one or more rules is independent of whether the downlink control channel command is transmitted during a first downlink control channel candidate or a second downlink control channel candidate. In some examples, the threshold delay period includes a first time period for uplink shared channel preparation according to a capability of the UE, a second time period for random access preparation, a third time period for BWP switching, a fourth time period for uplink switching, or a combination thereof.

[0207]

[0219] In some examples, the uplink random access message component 1335 may be configured as or otherwise support a means for transmitting an indication of the timing of a random access occasion to the UE via a downlink control channel command or SSB.

[0208]

[0220] In some examples, the downlink random access message component 1345 may be configured with or otherwise support a means for transmitting a downlink random access message in response to an uplink random access message, where the downlink random access message is either a downlink control channel message that schedules an RAR message or is an RAR message.

[0209]

[0221] In some examples, the QCL assumption component 1340 may be configured with or otherwise support a means for identifying, in accordance with one or more rules, a QCL assumption to be applied to a transmission of a downlink random access message in response to an uplink random access message, the QCL assumption being associated with at least one of a first TCI state associated with a first downlink control channel candidate or a second TCI state associated with a second downlink control channel candidate, where the first TCI state is different from the second TCI state.

[0210]

[0222] In some examples, the TCI state selection component 1350 may be configured with or otherwise support a means for selecting one of the first TCI state or the second TCI state as a basis for QCL assumptions according to one or more rules, where the one or more rules specify that the selection of either the first TCI state or the second TCI state is based on the relative timing of the first downlink control channel candidate and the second downlink control channel candidate.

[0211]

[0223] In some examples, the TCI state selection component 1350 may be configured with or otherwise support a means for selecting one of the first TCI state or the second TCI state as a basis for QCL assumptions according to one or more rules, where the one or more rules specify that the selection of either the first TCI state or the second TCI state is based on a relative value of a first search space set ID of a first search space set corresponding to a first downlink control channel candidate and a second search space set ID of a second search space set corresponding to a second downlink control channel candidate.

[0212]

[0224] In some examples, the TCI state selection component 1350 may be configured with or otherwise support a means for selecting one of the first TCI state or the second TCI state as a basis for QCL assumptions according to one or more rules, where the one or more rules specify that the selection of either the first TCI state or the second TCI state is based on the relative values ​​of a first CORESET ID associated with a first search space set corresponding to a first downlink control channel candidate and a second CORESET ID associated with a second search space set corresponding to a second downlink control channel candidate.

[0213]

[0225] In some examples, the TCI state selection component 1350 may be configured with or otherwise support a means for selecting one of the first TCI state or the second TCI state as a basis for QCL hypotheses according to one or more rules, where the one or more rules specify that the selection of either the first TCI state or the second TCI state is based on the relative values ​​of a first TCI state ID associated with the first TCI state and a second TCI state ID associated with the second TCI state.

[0214]

[0226] In some examples, to support identifying a QCL assumption, the TCI state selection component 1350 may be configured with or otherwise support a means for selecting both a first TCI state and a second TCI state as a basis for a QCL assumption according to one or more rules, where the one or more rules specify that a downlink random access message to which the QCL assumption may be applied is a downlink control channel message that schedules a RAR message, and the downlink control channel message is transmitted via a third downlink control channel candidate and a fourth downlink control channel candidate that are linked for the downlink control channel repetition.

[0215]

[0227] In some examples, to support identifying a QCL assumption, the TCI state selection component 1350 may be configured with or otherwise support a means for selecting both a first TCI state and a second TCI state as a basis for the QCL assumption according to one or more rules, where the one or more rules specify that a downlink random access message to which the QCL assumption may be applied is a RAR message that is a multi-TCI state downlink shared channel that varies in at least one of spatial division multiplexing, FDM, TDM, or single frequency network schemes.

[0216]

[0228] In some examples, the downlink control channel command requests a CFRA procedure on the PCell or the PSCell, or both. In some examples, the downlink random access message is either a downlink control channel message that schedules a RAR message or is a RAR message.

[0217]

[0229] Additionally or alternatively, the communications manager 1320 may support wireless communications in the base station according to examples disclosed herein. In some examples, the PDCCH command component 1330 may be configured as or otherwise support a means for transmitting a downlink control channel command to the UE requesting the UE to participate in a random access procedure, the downlink control channel command being transmitted according to one or more rules regarding reception of the downlink control channel command via multiple downlink control channel candidates linked for downlink control channel repetition. In some examples, the uplink random access message component 1335 may be configured as or otherwise support a means for receiving a random access message from the UE based on the downlink control channel command being transmitted according to one or more rules.

[0218]

[0230] In some examples, to support transmitting downlink control channel commands according to one or more rules, the PDCCH command component 1330 may be configured as or otherwise support a means for transmitting downlink control channel commands over a downlink control channel candidate that is not linked with other downlink control channel candidates for repetition.

[0219]

[0231] In some examples, to support transmitting downlink control channel commands according to one or more rules, the PDCCH command component 1330 may be configured with or otherwise support a means for transmitting downlink control channel commands via at least one of a first downlink control channel candidate or a second downlink control channel candidate linked for a downlink control channel iteration, where the first downlink control channel candidate corresponds to a first search space set associated with the CORESET and the second downlink control channel candidate corresponds to a second search space set associated with the CORESET.

[0220]

[0232] In some examples, to support transmitting downlink control channel commands according to one or more rules, the PDCCH command component 1330 may be configured with or otherwise support a means for transmitting downlink control channel commands via at least one of a first downlink control channel candidate or a second downlink control channel candidate linked for a downlink control channel iteration, where the first downlink control channel candidate corresponds to a first search space set associated with a first CORESET having a TCI state and the second downlink control channel candidate corresponds to a second search space set associated with a second CORESET having a TCI state.

[0221]

[0233] In some examples, the downlink control channel command requests a CFRA procedure on the PCell or the PSCell, or both.

[0222]

[0234] In some cases, the linked PDCCH identification component 1325, the PDCCH command component 1330, the uplink random access message component 1335, the QCL assumption component 1340, the downlink random access message component 1345, and the TCI state selection component 1350 may each be, or at least a part of, a processor (e.g., a transceiver processor, or a radio processor, or a transmitter processor, or a receiver processor). The processor may be coupled to a memory and execute instructions stored in the memory that enable the processor to perform or facilitate functions of the linked PDCCH identification component 1325, the PDCCH command component 1330, the uplink random access message component 1335, the QCL assumption component 1340, the downlink random access message component 1345, and the TCI state selection component 1350 described herein.

[0223]

[0235] FIG. 14 illustrates a diagram of a system 1400 including a device 1405 supporting downlink control channel repetition for downlink control channel commanding according to an aspect of the disclosure. The device 1405 may be or include an example of a component of a device 1105, device 1205, or base station 105 described herein. The device 1405 may wirelessly communicate with one or more base stations 105, UEs 115, or any combination thereof. The device 1405 may include components for two-way voice and data communication, including components for transmitting and receiving communications, such as a communications manager 1420, a network communications manager 1410, a transceiver 1415, an antenna 1425, a memory 1430, code 1435, a processor 1440, and an inter-station communications manager 1445. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1450).

[0224]

[0236] The network communications manager 1410 may manage communications with the core network 130 (e.g., via one or more wired backhaul links). For example, the network communications manager 1410 may manage the transfer of data communications for client devices, such as one or more UEs 115.

[0225]

[0237] In some cases, the device 1405 may include a single antenna 1425. However, in some other cases, the device 1405 may have two or more antennas 1425 that may be capable of simultaneously transmitting or receiving multiple wireless transmissions. The transceiver 1415 may communicate bidirectionally via one or more antennas 1425, wired links, or wireless links as described herein. For example, the transceiver 1415 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1415 may also include a modem for modulating packets and providing the modulated packets to the one or more antennas 1425 for transmission, and for demodulating packets received from the one or more antennas 1425. The transceiver 1415, or the transceiver 1415 and the one or more antennas 1425, may be an example of the transmitter 1115, the transmitter 1215, the receiver 1110, the receiver 1210, or any combination or components thereof described herein.

[0226]

[0238] The memory 1430 may include RAM and ROM. The memory 1430 may store computer-readable, computer-executable code 1435 including instructions that, when executed by the processor 1440, cause the device 1405 to perform various functions described herein. The code 1435 may be stored in a non-transitory computer-readable medium, such as a system memory or another type of memory. In some cases, the code 1435 may not be directly executable by the processor 1440, but may (e.g., when compiled and executed) cause the computer to perform functions described herein. In some cases, the memory 1430 may include a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices, among other things.

[0227]

[0239] The processor 1440 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 1440 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be incorporated into the processor 1440. The processor 1440 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1430) to cause the device 1405 to perform various functions (e.g., functions or tasks supporting downlink control channel iterations related to downlink control channel commands). For example, the device 1405 or a component of the device 1405 may include a processor 1440 and a memory 1430 coupled to the processor 1440, where the processor 1440 and the memory 1430 are configured to perform various functions described herein.

[0228]

[0240] The inter-station communications manager 1445 may manage communications with other base stations 105 and may include a controller or scheduler for controlling communications with the UE 115 in cooperation with the other base stations 105. For example, the inter-station communications manager 1445 may coordinate scheduling for transmissions to the UE 115 for various interference mitigation techniques, such as beamforming or joint transmission. In some examples, the inter-station communications manager 1445 may provide an X2 interface within the LTE / LTE-A wireless communications network technology to provide communications between the base stations 105.

[0229]

[0241] The communications manager 1420 may support wireless communications in a base station according to examples disclosed herein. For example, the communications manager 1420 may be configured as or otherwise support a means for transmitting an indication to a UE that a first downlink control channel candidate and a second downlink control channel candidate are linked for downlink control channel iteration. The communications manager 1420 may be configured as or otherwise support a means for transmitting a downlink control channel command to a UE via one or both of the first downlink control channel candidate and the second downlink control channel candidate requesting the UE to participate in a random access procedure. The communications manager 1420 may be configured as or otherwise support a means for receiving an uplink random access message associated with the downlink control channel command from the UE according to one or more rules regarding the transmission of the downlink control channel command via the linked downlink control channel candidate.

[0230]

[0242] Additionally or alternatively, the communications manager 1420 may support wireless communications in the base station according to examples disclosed herein. For example, the communications manager 1420 may be configured as or otherwise support a means for transmitting a downlink control channel command to a UE requesting the UE to participate in a random access procedure, the downlink control channel command being transmitted according to one or more rules regarding reception of the downlink control channel command via multiple downlink control channel candidates linked for downlink control channel repetition. The communications manager 1420 may be configured as or otherwise support a means for receiving a random access message from the UE based on the downlink control channel command being transmitted according to the one or more rules.

[0231]

[0243] In some examples, the communications manager 1420 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise cooperating with the transceiver 1415, one or more antennas 1425, or any combination thereof. Although the communications manager 1420 is shown as a separate component, in some examples, one or more functions described with reference to the communications manager 1420 may be supported by or performed by the processor 1440, the memory 1430, the code 1435, or any combination thereof. For example, the code 1435 may include instructions executable by the processor 1440 to cause the device 1405 to perform various aspects of downlink control channel iterations related to the downlink control channel commands described herein, or the processor 1440 and the memory 1430 may be configured to perform or support such operations, as the case may be.

[0232]

[0244] FIG. 15 illustrates a flow chart illustrating a method 1500 for supporting downlink control channel repetition for downlink control channel commanding according to an aspect of the disclosure. The operations of method 1500 may be implemented by a UE or components thereof as described herein. For example, the operations of method 1500 may be performed by the UE 115 described with reference to FIGS. 1-10. In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may perform aspects of the described functions using dedicated hardware.

[0233]

[0245] At 1505, the method may include receiving an indication that the first downlink control channel candidate and the second downlink control channel candidate are linked for downlink control channel repetition. The operations of 1505 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1505 may be performed by a linked PDCCH identification component 925 described with reference to FIG.

[0234]

[0246] At 1510, the method may include receiving a downlink control channel command via one or both of the first downlink control channel candidate and the second downlink control channel candidate requesting the UE to participate in a random access procedure. The operations of 1510 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1510 may be performed by a PDCCH command component 930 described with reference to FIG.

[0235]

[0247] At 1515, the method may include performing a random access procedure related to the downlink control channel commands in accordance with one or more rules regarding reception of the downlink control channel commands via the linked downlink control channel candidates. The operations of 1515 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1515 may be performed by the random access procedure component 935 described with reference to FIG.

[0236]

[0248] FIG. 16 illustrates a flow chart illustrating a method 1600 for supporting downlink control channel repetition for downlink control channel commanding according to an aspect of the disclosure. The operations of the method 1600 may be implemented by a base station or components thereof as described herein. For example, the operations of the method 1600 may be performed by the base station 105 described with reference to FIGS. 1-6 and 11-14. In some examples, the base station may execute a set of instructions to control functional elements of the base station to perform the described functions. Additionally or alternatively, the base station may perform aspects of the described functions using dedicated hardware.

[0237]

[0249] At 1605, the method may include transmitting an indication to the UE that the first downlink control channel candidate and the second downlink control channel candidate are linked for downlink control channel repetition. The operations of 1605 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1605 may be performed by the linked PDCCH identification component 1325 described with reference to FIG.

[0238]

[0250] At 1610, the method may include transmitting a downlink control channel command to the UE via one or both of the first downlink control channel candidate and the second downlink control channel candidate requesting the UE to participate in a random access procedure. The operations of 1610 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1610 may be performed by the PDCCH command component 1330 described with reference to FIG.

[0239]

[0251] At 1615, the method may include receiving, from the UE, an uplink random access message associated with the downlink control channel command in accordance with one or more rules regarding transmission of the downlink control channel command over the linked downlink control channel candidate. The operations of 1615 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1615 may be performed by the uplink random access message component 1335, as described with reference to FIG.

[0240]

[0252] FIG. 17 illustrates a flow chart illustrating a method 1700 for supporting downlink control channel repetition for downlink control channel commanding according to an aspect of the disclosure. The operations of method 1700 may be implemented by a UE or components thereof as described herein. For example, the operations of method 1700 may be performed by the UE 115 described with reference to FIGS. 1-10. In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may perform aspects of the described functions using dedicated hardware.

[0241]

[0253] At 1705, the method may include receiving a downlink control channel command requesting the UE to participate in a random access procedure, the downlink control channel command being received according to one or more rules regarding reception of the downlink control channel command over multiple downlink control channel candidates linked for downlink control channel repetition. The operations of 1705 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1705 may be performed by a PDCCH command component 930 described with reference to FIG. 9.

[0242]

[0254] At 1710, the method may include performing a random access procedure based on the downlink control channel commands being received according to one or more rules. The operations of 1710 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1710 may be performed by the random access procedure component 935 described with reference to FIG.

[0243]

[0255] FIG. 18 illustrates a flowchart illustrating a method 1800 for supporting downlink control channel repetition for downlink control channel commanding according to an aspect of the disclosure. The operations of method 1800 may be implemented by a base station or components thereof as described herein. For example, the operations of method 1800 may be performed by a base station 105 as described with reference to FIGS. 1-6 and 11-14. In some examples, the base station may execute a set of instructions to control functional elements of the base station to perform the described functions. Additionally or alternatively, the base station may perform aspects of the described functions using dedicated hardware.

[0244]

[0256] At 1805, the method may include transmitting a downlink control channel command to the UE requesting the UE to participate in a random access procedure, the downlink control channel command being transmitted according to one or more rules regarding reception of the downlink control channel command via multiple downlink control channel candidates linked for the downlink control channel repetition. The operations of 1805 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1805 may be performed by the PDCCH command component 1330 described with reference to FIG.

[0245]

[0257] At 1810, the method may include receiving, from the UE, a random access message based on the downlink control channel command being transmitted according to one or more rules. The operations of 1810 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1810 may be performed by an uplink random access message component 1335, as described with reference to FIG.

[0246]

[0258] The following provides an overview of aspects of the disclosure.

[0247]

[0259] Aspect 1: A method for wireless communications in a user equipment (UE), comprising: receiving an indication that a first downlink control channel candidate and a second downlink control channel candidate are linked for downlink control channel iteration; receiving a downlink control channel command via one or both of the first downlink control channel candidate and the second downlink control channel candidate requesting the UE to participate in a random access procedure; and performing a random access procedure associated with the downlink control channel command in accordance with one or more rules regarding reception of the downlink control channel command via the linked downlink control channel candidate.

[0248]

[0260] Aspect 2: The method of aspect 1, wherein performing the random access procedure further comprises determining a random access occasion for transmitting an uplink random access message in response to a downlink control channel command, and transmitting the uplink random access message during the random access occasion based at least in part on a first symbol of the random access occasion being after a threshold delay period triggered by a reference downlink control channel candidate among the linked downlink control channel candidates.

[0249]

[0261] Aspect 3: The method of aspect 2, wherein the reference downlink control channel candidate is a second downlink control channel candidate resulting from the second downlink control channel candidate ending later in time than the first downlink control channel candidate, and wherein the one or more rules indicate that the threshold delay period begins after the last symbol of the second downlink control channel candidate.

[0250]

[0262] Aspect 4: The method of aspect 2 or 3, wherein performing a random access procedure in accordance with one or more rules is independent of whether the downlink control channel command is received during a first downlink control channel candidate or a second downlink control channel candidate.

[0251]

[0263] Aspect 5: The method of any of aspects 2 to 4, wherein the threshold delay period comprises a first time period for uplink shared channel preparation according to a UE capability, a second time period for random access preparation, a third time period for bandwidth portion switching, a fourth time period for uplink switching, or a combination thereof.

[0252]

[0264] Aspect 6: The method of any of aspects 2 to 5, wherein determining the random access occasion comprises determining a timing of the random access occasion based at least in part on an indication in a downlink control channel command or a measured SSB.

[0253]

[0265] Aspect 7: The method of any of aspects 1 to 6, wherein performing the random access procedure further comprises: transmitting an uplink random access message in response to a downlink control channel command; and identifying a QCL assumption to be applied to receiving a downlink random access message in response to the uplink random access message according to one or more rules, where a first downlink control channel candidate is associated with a first TCI state and a second downlink control channel candidate is associated with a second TCI state different from the first TCI state, and the QCL assumption is associated with at least one of the first TCI state or the second TCI state.

[0254]

[0266] Aspect 8: The method of aspect 7, wherein identifying a QCL assumption comprises selecting one of a first TCI state or a second TCI state as a basis for the QCL assumption in accordance with one or more rules, wherein the one or more rules specify that the selection of either the first TCI state or the second TCI state is based at least in part on relative timing between the first downlink control channel candidate and the second downlink control channel candidate.

[0255]

[0267] Aspect 9: The method of aspect 7, wherein identifying a QCL assumption comprises selecting one of a first TCI state or a second TCI state as a basis for the QCL assumption in accordance with one or more rules, wherein the one or more rules specify that the selection of either the first TCI state or the second TCI state is based at least in part on a relative value of a first search space set ID of a first search space set corresponding to the first downlink control channel candidate and a second search space set ID of a second search space set corresponding to the second downlink control channel candidate.

[0256]

[0268] Aspect 10: The method of aspect 7, wherein identifying a QCL assumption comprises selecting one of a first TCI state or a second TCI state as a basis for the QCL assumption in accordance with one or more rules, wherein the one or more rules specify that the selection of either the first TCI state or the second TCI state is based at least in part on a relative value of a first CORESET ID associated with a first search space set corresponding to the first downlink control channel candidate and a second CORESET ID associated with a second search space set corresponding to the second downlink control channel candidate.

[0257]

[0269] Aspect 11: The method of aspect 7, wherein identifying a QCL assumption comprises selecting one of a first TCI state or a second TCI state as a basis for the QCL assumption in accordance with one or more rules, wherein the one or more rules specify that the selection of either the first TCI state or the second TCI state is based at least in part on a relative value of a first TCI state ID associated with the first TCI state and a second TCI state ID associated with the second TCI state.

[0258]

[0270] Aspect 12: The method of aspect 7, wherein identifying a QCL assumption comprises selecting both a first TCI state and a second TCI state as a basis for the QCL assumption according to one or more rules, wherein the one or more rules specify that the downlink random access message to which the QCL assumption applies is a downlink control channel message that schedules a RAR message, and the downlink control channel message is transmitted via a third downlink control channel candidate and a fourth downlink control channel candidate that are linked for the downlink control channel repetition.

[0259]

[0271] Aspect 13: The method of aspect 7 or 12, wherein identifying the QCL assumption comprises selecting both a first TCI state and a second TCI state as a basis for the QCL assumption according to one or more rules, wherein the one or more rules specify that the downlink random access message to which the QCL assumption applies is a RAR message that is a multi-TCI state downlink shared channel that varies in at least one of SDM, FDM, TDM, or single frequency network manner.

[0260]

[0272] Aspect 14: The method of any of aspects 7 to 13, wherein the downlink control channel command requests a CFRA procedure on a PCell or a PSCell, or both.

[0261]

[0273] Aspect 15: The method of any of aspects 7 to 14, wherein the downlink random access message is either a downlink control channel message that schedules a RAR message or a RAR message.

[0262]

[0274] Aspect 16: A method for wireless communications in a base station, comprising: transmitting an indication to a UE that a first downlink control channel candidate and a second downlink control channel candidate are linked for downlink control channel iteration; transmitting a downlink control channel command to the UE via one or both of the first downlink control channel candidate and the second downlink control channel candidate requesting the UE to participate in a random access procedure; and receiving an uplink random access message from the UE related to the downlink control channel command in accordance with one or more rules for transmitting the downlink control channel command via the linked downlink control channel candidates.

[0263]

[0275] Aspect 17: The method of aspect 26, wherein receiving the uplink random access message further comprises receiving the uplink random access message during the random access occasion based at least in part on a first symbol of the random access occasion being after a threshold delay period triggered by a reference downlink control channel candidate among the linked downlink control channel candidates.

[0264]

[0276] Aspect 18: The method of aspect 17, wherein the reference downlink control channel candidate is a second downlink control channel candidate that is a result of the second downlink control channel candidate ending later in time than the first downlink control channel candidate, and wherein the one or more rules indicate that the threshold delay period starts after the last symbol of the second downlink control channel candidate.

[0265]

[0277] Aspect 19: The method of aspect 17 or 18, wherein receiving an uplink random access message in accordance with one or more rules is independent of whether the downlink control channel command is transmitted during a first downlink control channel candidate or a second downlink control channel candidate.

[0266]

[0278] Aspect 20: The method of any of aspects 17 to 19, further comprising transmitting, to the UE, an indication of timing of the random access occasion via a downlink control channel command or SSB.

[0267]

[0279] Aspect 21: A method according to any of aspects 16 to 20, further comprising identifying a QCL assumption to be applied to a transmission of a downlink random access message in response to the uplink random access message in accordance with one or more rules, the QCL assumption being associated with at least one of a first TCI state associated with a first downlink control channel candidate or a second TCI state associated with a second downlink control channel candidate, wherein the first TCI state is different from the second TCI state.

[0268]

[0280] Aspect 22: The method of aspect 21, wherein identifying a QCL assumption comprises selecting both a first TCI state and a second TCI state as a basis for the QCL assumption according to one or more rules, wherein the one or more rules specify that the downlink random access message to which the QCL assumption applies is a downlink control channel message that schedules a RAR message, and the downlink control channel message is transmitted via a third downlink control channel candidate and a fourth downlink control channel candidate that are linked for the downlink control channel repetition.

[0269]

[0281] Aspect 23: The method of aspect 21 or 22, wherein identifying the QCL assumption comprises selecting both a first TCI state and a second TCI state as a basis for the QCL assumption according to one or more rules, wherein the one or more rules specify that the downlink random access message to which the QCL assumption applies is a RAR message that is a multi-TCI state downlink shared channel that varies in at least one of SDM, FDM, TDM, or single frequency network manner.

[0270]

[0282] Aspect 24: A method for wireless communications in a UE, comprising: receiving a downlink control channel command requesting the UE to participate in a random access procedure; and performing the random access procedure based on the downlink control channel command being received in accordance with one or more rules regarding reception of the downlink control channel command via a plurality of downlink control channel candidates linked for downlink control channel repetition.

[0271]

[0283] Aspect 25: The method of aspect 24, wherein receiving a downlink control channel command according to one or more rules comprises receiving a downlink control channel command via a downlink control channel candidate that is not linked with other downlink control channel candidates for the repetition.

[0272]

[0284] Aspect 26: The method of aspect 24, wherein receiving a downlink control channel command according to one or more rules comprises receiving a downlink control channel command via at least one of a first downlink control channel candidate or a second downlink control channel candidate linked for the downlink control channel iteration, wherein the first downlink control channel candidate corresponds to a first search space set associated with the CORESET, and the second downlink control channel candidate corresponds to a second search space set associated with the CORESET.

[0273]

[0285] Aspect 27: The method of aspect 24, wherein receiving a downlink control channel command according to one or more rules comprises receiving a downlink control channel command via at least one of a first downlink control channel candidate or a second downlink control channel candidate linked for the downlink control channel iteration, wherein the first downlink control channel candidate corresponds to a first search space set associated with a first CORESET having a TCI state, and the second downlink control channel candidate corresponds to a second search space set associated with a second CORESET having a TCI state.

[0274]

[0286] Aspect 28: The method of any of aspects 24 to 27, wherein the downlink control channel command requests a CFRA procedure on a PCell or a PSCell, or both.

[0275]

[0287] Aspect 29: A method for wireless communications in a base station, comprising: transmitting a downlink control channel command to a UE requesting the UE to participate in a random access procedure; and receiving from the UE a random access message based on the downlink control channel command being transmitted in accordance with one or more rules, wherein the downlink control channel command is transmitted in accordance with one or more rules regarding reception of the downlink control channel command via multiple downlink control channel candidates linked for downlink control channel repetition.

[0276]

[0288] Aspect 30: The method of aspect 29, wherein transmitting the downlink control channel command in accordance with the one or more rules comprises transmitting the downlink control channel command via a downlink control channel candidate that is not linked with other downlink control channel candidates for the repetition.

[0277]

[0289] Aspect 31: The method of aspect 29, wherein transmitting a downlink control channel command in accordance with one or more rules comprises transmitting a downlink control channel command via at least one of a first downlink control channel candidate or a second downlink control channel candidate linked for the downlink control channel iteration, wherein the first downlink control channel candidate corresponds to a first search space set associated with the CORESET, and the second downlink control channel candidate corresponds to a second search space set associated with the CORESET.

[0278]

[0290] Aspect 32: The method of aspect 29, wherein transmitting a downlink control channel command according to one or more rules comprises transmitting a downlink control channel command via at least one of a first downlink control channel candidate or a second downlink control channel candidate linked for the downlink control channel iteration, wherein the first downlink control channel candidate corresponds to a first search space set associated with a first CORESET having a TCI state, and the second downlink control channel candidate corresponds to a second search space set associated with a second CORESET having a TCI state.

[0279]

[0291] Aspect 33: An apparatus for wireless communication in a UE, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method as described in any of aspects 1 to 15.

[0280]

[0292] Aspect 34: An apparatus for wireless communication in a UE, comprising at least one means for performing the method described in any of aspects 1 to 15.

[0281]

[0293] Aspect 35: A non-transitory computer-readable medium storing code for wireless communication in a UE, the code comprising instructions executable by a processor to perform a method as described in any of aspects 1 to 15.

[0282]

[0294] Aspect 36: An apparatus for wireless communication in a base station, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method as described in any of aspects 16 to 23.

[0283]

[0295] Aspect 37: An apparatus for wireless communication in a base station, comprising at least one means for performing the method recited in any of aspects 16 to 23.

[0284]

[0296] Aspect 38: A non-transitory computer-readable medium storing code for wireless communication in a base station, the code comprising instructions executable by a processor to perform the method of any of aspects 16 to 23.

[0285]

[0297] Aspect 39: An apparatus for wireless communication in a UE, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method as described in any of aspects 24 to 28.

[0286]

[0298] Aspect 40: An apparatus for wireless communication in a UE, comprising at least one means for performing the method of any of aspects 24 to 28.

[0287]

[0299] Aspect 41: A non-transitory computer-readable medium storing code for wireless communication in a UE, the code comprising instructions executable by a processor to perform a method as described in any of aspects 24 to 28.

[0288]

[0300] Aspect 42: An apparatus for wireless communication in a base station, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method as described in any of aspects 29 to 32.

[0289]

[0301] Aspect 43: An apparatus for wireless communication in a base station, comprising at least one means for performing the method according to any of aspects 29 to 32.

[0290]

[0302] Aspect 44: A non-transitory computer-readable medium storing code for wireless communication in a base station, the code comprising instructions executable by a processor to perform the method described in any of aspects 29 to 32.

[0291]

[0303] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or possibly modified, and that other implementations are possible. Additionally, aspects from two or more of the methods may be combined.

[0292]

[0304] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described as examples, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may be applicable to other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0293]

[0305] The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0294]

[0306] The various example blocks and components described in connection with the disclosure herein may be implemented or performed using a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0295]

[0307] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or a combination thereof. When implemented in software executed by a processor, the functions may be stored on or transmitted via a computer-readable medium as one or more instructions or codes. Other examples and implementations are within the scope of this disclosure and the scope of the appended claims. For example, due to the nature of the software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features implementing the functions may also be physically located in various locations, including being distributed such that parts of the functions are implemented in different physical locations.

[0296]

[0308] Computer-readable media includes both non-transitory computer storage media and communication media, including any medium that facilitates transfer of a computer program from one place to another. Non-transitory storage media may be any available medium that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, Electrically Erasable Programmable ROM (EEPROM), Flash memory, Compact Disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general purpose or special purpose computer, or a general purpose or special purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer readable media. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disks typically reproduce data magnetically and discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer readable media.

[0297]

[0309] As used herein, including within the claims, "or" used in a list of items (e.g., a list of items ending with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, such as, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, the phrase "based on" as used herein is not to be construed as a reference to a closed set of conditions. For example, an exemplary step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, the phrase "based on" as used herein is to be construed in the same manner as the phrase "based at least in part on."

[0298]

[0310] The terms "determine" or "determining" encompass a wide variety of actions, and thus "determining" can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or another data structure), ascertaining, and the like. "Determining" can also include receiving (such as receiving information), accessing (such as accessing data in a memory), and the like. "Determining" can also include resolving, selecting, choosing, establishing, and other such similar activities.

[0299]

[0311] In the accompanying figures, similar components or features may have the same reference label. Furthermore, various components of the same type may be distinguished by following the reference label with a dash and a second label that distinguishes between the similar components. If only a first reference label is used herein, the description is applicable to any of the similar components having the same first reference label, regardless of the second reference label, or any other subsequent reference label.

[0300]

[0312] The description set forth herein with respect to the accompanying drawings describes exemplary configurations and does not necessarily represent all examples that may be implemented or are within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration" and does not mean "preferred" or "advantageous over other examples." The detailed description includes specific details for the purposes of providing an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0301]

[0313] The description herein is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications of the present disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication in a user equipment (UE), comprising: A processor; a memory coupled to the processor; instructions stored in said memory; and the instructions cause the device to: receiving an indication that a first downlink control channel candidate and a second downlink control channel candidate are linked for downlink control channel repetition; receiving a downlink control channel command via the linked downlink control channel candidate requesting the UE to participate in a random access procedure; performing the random access procedure associated with the downlink control channel command according to one or more rules regarding reception of the downlink control channel command via a linked downlink control channel candidate, wherein the one or more rules include: a threshold delay period after receipt of the downlink control channel command and before a first symbol of a random access occasion begins after a last symbol of a control channel candidate of the linked downlink control channel candidate that ends later in time; or one or more parameters for selecting a TCI state to be used for QCL assumptions for reception of a downlink random access message; Showing, The apparatus is executable by the processor to cause

2. The instruction: determining the random access occasion for transmission of an uplink random access message in response to the downlink control channel command; transmitting the uplink random access message during the random access occasion based at least in part on the first symbol of the random access occasion after the threshold delay period triggered by a reference downlink control channel candidate among the linked downlink control channel candidates; 2. The apparatus of claim 1, further executable by the processor to perform the random access procedure by being executable by the processor to:

3. 3. The apparatus of claim 2, wherein the reference downlink control channel candidate is a second downlink control channel candidate that is a result of the second downlink control channel candidate ending later in time than the first downlink control channel candidate, and wherein the one or more rules indicate that the threshold delay period begins after the last symbol of the second downlink control channel candidate.

4. 3. The apparatus of claim 2, wherein performing the random access procedure in accordance with the one or more rules is independent of whether the downlink control channel command is received during the first downlink control channel candidate or the second downlink control channel candidate.

5. 3. The apparatus of claim 2, wherein the threshold delay period comprises a first time period for uplink shared channel preparation according to a capability of the UE, a second time period for random access preparation, a third time period for bandwidth portion switching, a fourth time period for uplink switching, or a combination thereof.

6. The instruction: determining a timing of the random access occasion based at least in part on an indication in the downlink control channel command or a measured synchronization signal block; 3. The apparatus of claim 2, further comprising: a processor operable to determine the random access occasion by being operable by the processor to:

7. The instruction: transmitting an uplink random access message in response to the downlink control channel command, wherein the first downlink control channel candidate is associated with a first transmission configuration indicator state and the second downlink control channel candidate is associated with a second transmission configuration indicator state different from the first transmission configuration indicator state. identifying a quasi-co-location assumption to be applied to reception of a downlink random access message in response to the uplink random access message according to the one or more rules, the quasi-co-location assumption being associated with at least one of the first transmission configuration indicator state or the second transmission configuration indicator state.

2. The apparatus of claim 1, further executable by the processor to perform the random access procedure by being executable by the processor to:

8. The instruction: selecting one of the first transmission configuration indicator state or the second transmission configuration indicator state as a basis for the quasi-co-location assumption according to the one or more rules, wherein the one or more rules specify that selection of either the first transmission configuration indicator state or the second transmission configuration indicator state is based at least in part on relative timing of the first downlink control channel candidate and the second downlink control channel candidate.

8. The apparatus of claim 7, further executable by the processor to identify the quasi-collocation hypotheses by:

9. The instruction: selecting one of the first transmission configuration indicator state or the second transmission configuration indicator state as a basis for the quasi-co-location assumption according to the one or more rules, wherein the one or more rules specify that selection of either the first transmission configuration indicator state or the second transmission configuration indicator state is based at least in part on a relative value of a first search space set identifier of a first search space set corresponding to the first downlink control channel candidate and a second search space set identifier of a second search space set corresponding to the second downlink control channel candidate.

8. The apparatus of claim 7, further executable by the processor to identify the quasi-collocation hypotheses by:

10. The instruction: selecting one of the first transmission configuration indicator state or the second transmission configuration indicator state as a basis for the quasi-co-location assumption according to the one or more rules, wherein the one or more rules specify that selection of either the first transmission configuration indicator state or the second transmission configuration indicator state is based at least in part on a relative value of a first control resource set identifier associated with a first search space set corresponding to the first downlink control channel candidate and a second control resource set identifier associated with a second search space set corresponding to the second downlink control channel candidate.

8. The apparatus of claim 7, further executable by the processor to identify the quasi-collocation hypotheses by:

11. The instruction: selecting one of the first transmission configuration indicator state or the second transmission configuration indicator state as a basis for the quasi-collocation assumption in accordance with the one or more rules, wherein the one or more rules specify that selection of either the first transmission configuration indicator state or the second transmission configuration indicator state is based at least in part on a relative value of a first transmission configuration indicator state identifier associated with the first transmission configuration indicator state and a second transmission configuration indicator state identifier associated with the second transmission configuration indicator state.

8. The apparatus of claim 7, further executable by the processor to identify the quasi-collocation hypotheses by:

12. The instruction: selecting both the first transmission configuration indicator state and the second transmission configuration indicator state as a basis for the quasi-collocation assumption according to the one or more rules, wherein the one or more rules specify that the downlink random access message to which the quasi-collocation assumption applies is a downlink control channel message that schedules a random access response message, and the downlink control channel message is transmitted via a third downlink control channel candidate and a fourth downlink control channel candidate that are linked for downlink control channel repetition.

8. The apparatus of claim 7, further executable by the processor to identify the quasi-collocation hypotheses by:

13. The instruction: selecting both the first transmission configuration indicator state and the second transmission configuration indicator state as a basis for the quasi-co-location assumption according to the one or more rules, wherein the one or more rules specify that the downlink random access message to which the quasi-co-location assumption applies is a random access response message that is a multiple transmission configuration indicator state downlink shared channel that varies in at least one of a spatial division multiplexing, a frequency division multiplexing, a time division multiplexing, or a single frequency network manner.

8. The apparatus of claim 7, further executable by the processor to identify the quasi-collocation hypotheses by:

14. An apparatus for wireless communication in a base station, comprising: A processor; a memory coupled to the processor; instructions stored in said memory; and the instructions cause the device to: transmitting, to a user equipment (UE), an indication that the first downlink control channel candidate and the second downlink control channel candidate are linked for downlink control channel repetition; sending a downlink control channel command to the UE via one or both of the first downlink control channel candidate and the second downlink control channel candidate requesting the UE to participate in a random access procedure; receiving, from the UE, an uplink random access message associated with the downlink control channel command according to one or more rules regarding transmission of the downlink control channel command via a linked downlink control channel candidate, wherein the one or more rules include: a threshold delay period after receipt of the downlink control channel command at the UE and before a first symbol of a random access occasion begins after a last symbol of a control channel candidate of the linked downlink control channel candidate that ends later in time; one or more parameters for selecting a TCI state to be used for QCL assumptions for reception of a downlink random access message; Showing, The apparatus is executable by the processor to cause

15. 1. A method for wireless communication in a user equipment (UE), comprising: receiving an indication that a first downlink control channel candidate and a second downlink control channel candidate are linked for downlink control channel repetition; receiving a downlink control channel command via the linked downlink control channel candidate requesting the UE to participate in a random access procedure; performing the random access procedure associated with the downlink control channel command according to one or more rules regarding reception of the downlink control channel command via a linked downlink control channel candidate, wherein the one or more rules include: a threshold delay period after receipt of the downlink control channel command and before a first symbol of a random access occasion begins after a last symbol of a control channel candidate of the linked downlink control channel candidate that ends later in time; or one or more parameters for selecting a TCI state to be used for QCL assumptions for reception of a downlink random access message; Showing, A method comprising:

Images