Downlink control channel repetitions related to downlink control channel commands

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 interests of U.S. Provisional Patent Application No. 63 / 169,663, filed on April 1, 2021, by Khoshnevisan et al., titled "DOWNLINK CONTROL CHANNEL REPETITION FOR A DOWNLINK CONTROL CHANNEL ORDER," which was assigned to the assignee of this application, and U.S. Patent Application No. 17 / 708,178, filed on March 30, 2022, titled "DOWNLINK CONTROL CHANNEL REPETITION FOR A DOWNLINK CONTROL CHANNEL ORDER."

[0002]

[0002] This disclosure relates to wireless communications including downlink control channel repetitions relating to downlink control channel commands. [Background technology]

[0003]

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, and broadcast. These systems may be able to support 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®) systems, LTE Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth-generation (5G) systems, sometimes called New Radio (NR) systems. These systems may employ techniques 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, which may sometimes be known as user equipment (UEs).

[0004]

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

[0005]

[0005] The techniques described relate to improved methods, systems, devices, and apparatus for supporting downlink control channel iterations relating to downlink control channel commands. Generally, the techniques described provide a user equipment (UE) receiving downlink control channel commands over two or more downlink control channel candidates linked for iteration, in accordance with one or more rules relating to receiving downlink control channel commands over 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 iteration. In some examples, the indication may be received via radio resource control (RRC) signaling. The UE may receive downlink control channel commands over one or both of the first downlink control channel candidate and the second downlink control channel candidate, in accordance with one or more rules. 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 relating to the downlink control channel command, in accordance with one or more rules. In some examples, one or more rules may indicate a threshold delay period between the UE receiving a downlink control channel command and the UE transmitting an uplink random access message. In some examples, one or more rules may specify guidelines for identifying pseudo-collocation (QCL) assumptions that should apply to the reception of downlink random access messages. Additional or alternative, one or more rules may relate to whether the UE can receive a downlink control channel command via a linked downlink control channel candidate. In some examples, the UE can receive a downlink control channel command via a downlink control channel candidate that is not linked to other downlink control channel candidates for iteration.

[0006]

[0006] A method for wireless communication in a UE is described. The method 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 executing a random access procedure associated with the downlink control channel command in accordance with one or more rules relating to receiving the downlink control channel command via the linked downlink control channel candidates.

[0007]

[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 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; and execute a random access procedure associated with the downlink control channel command in accordance with one or more rules relating to the reception of the downlink control channel command via the linked downlink control channel candidates.

[0008]

[0008] Another device for wireless communication in the UE is described. This device 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 a downlink control channel command via one or both of the first downlink control channel candidate and the second downlink control channel candidate that requests the UE to participate in a random access procedure; and means for executing a random access procedure associated with the downlink control channel command in accordance with one or more rules relating to receiving the downlink control channel command via the linked downlink control channel candidates.

[0009]

[0009] A non-temporary computer-readable medium for storing code for wireless communication in a UE is described. The code may include processor-executable instructions 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; receiving a downlink control channel command through 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 executing a random access procedure associated with the downlink control channel command in accordance with one or more rules relating to the reception of the downlink control channel command through the linked downlink control channel candidates.

[0010]

[0010] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, performing a random access procedure may include operations, features, means, or instructions for determining a random access occasion for sending an uplink random access message in response to a downlink control channel command, and sending an uplink random access message during the random access occasion, based on the fact that a first symbol of the random access occasion is 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 a 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.

[0011]

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

[0012]

[0012] In some examples of the methods, apparatus, and non-transient computer-readable media described herein, the threshold delay period includes a first time period for uplink shared channel preparation according to the capabilities of the UE, 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-temporary computer-readable media described herein, determining random access occasions may include operations, features, means, or instructions for determining the timing of random access occasions based on indications in downlink control channel commands or based on measured synchronous signal blocks (SSBs).

[0014]

[0014] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, performing a random access procedure may include operations, features, means, or instructions for performing: transmitting an uplink random access message in response to a downlink control channel command, wherein a first downlink control channel candidate may be associated with a first transmit 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, and the QCL assumption to be applied to receiving a downlink random access message in response to an uplink random access message, wherein the QCL assumption is associated with at least one of the first or second TCI states.

[0015]

[0015] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, identifying a QCL assumption may include an operation, feature, means, or instruction for selecting one of a first TCI state or a second TCI state as the basis for a QCL assumption according to one or more rules, wherein one or more rules specify that the selection of either the first TCI state or the second TCI state may be based on the relative timing of a first downlink control channel candidate and a second downlink control channel candidate.

[0016]

[0016] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, identifying a QCL assumption may include an operation, feature, means, or instruction for selecting one of a first TCI state or a second TCI state as the basis for a QCL assumption according to one or more rules, wherein 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 between a first search space set identifier (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.

[0017]

[0017] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, identifying a QCL assumption may include an operation, feature, means, or instruction for selecting one of a first TCI state or a second TCI state as the basis for a QCL assumption according to one or more rules, wherein 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 between a first control resource set (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.

[0018]

[0018] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, identifying a QCL assumption may include an operation, feature, means, or instruction for selecting one of a first TCI state or a second TCI state as the basis for a QCL assumption according to one or more rules, wherein 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 between 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-temporary 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 the basis for a QCL assumption according to one or more rules, wherein one or more rules specify that a downlink random access message to which a QCL assumption may apply may be a downlink control channel message scheduling 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 which may be linked for downlink control channel iterations.

[0020]

[0020] In some examples of the methods, apparatus, and non-temporary 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 the basis for a QCL assumption according to one or more rules, wherein one or more rules specify that a downlink random access message to which a QCL assumption may apply may be a RAR message that is a multi-TCI state downlink shared channel that changes in at least one of spatial division multiplexing (SDM), frequency division multiplexing (FDM), time division multiplexing (TDM), or single-frequency network scheme.

[0021]

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

[0022]

[0022] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the downlink random access message can be either a downlink control channel message that schedules the RAR message or the RAR message itself.

[0023]

[0023] A method for wireless communication at a base station is described. The method may include transmitting, to a UE, an indication that a first downlink control channel candidate and a second downlink control channel candidate are linked for downlink control channel repetitions, transmitting, to the UE, 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, and 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 the linked downlink control channel candidate.

[0024]

[0024] An apparatus for wireless communication at 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, to a UE, an indication that a first downlink control channel candidate and a second downlink control channel candidate are linked for downlink control channel repetitions, transmit, to the UE, 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, and receive, 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 the linked downlink control channel candidate.

[0025]

[0025] Another device for wireless communication at a base station is described. This device may include means for transmitting to the UE 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 transmitting to the UE 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; and means for receiving uplink random access messages from the UE related to the downlink control channel command in accordance with one or more rules relating to the transmission of the downlink control channel command via the linked downlink control channel candidates.

[0026]

[0026] A non-temporary computer-readable medium for storing code for wireless communication at a base station is described. The code may include processor-executable instructions for sending an indication to the UE that a first downlink control channel candidate and a second downlink control channel candidate are linked for downlink control channel iteration; 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; and receiving an uplink random access message from the UE related to the downlink control channel command, in accordance with one or more rules relating to the transmission of the downlink control channel command via the linked downlink control channel candidates.

[0027]

[0027] In some examples of the methods, apparatuses, and non - transient 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 that the first symbol of the random - access occasion is after a threshold delay period that can be triggered by a reference downlink control channel candidate. In some examples, the reference downlink control channel candidate can be a second downlink control channel candidate as a result of the second downlink control channel candidate ending temporally after the first downlink control channel candidate, and one or more rules can indicate that the threshold delay period starts after the last symbol of the second downlink control channel candidate.

[0028]

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

[0029]

[0029] Some examples of the methods, apparatuses, and non - transient computer - readable media described herein may further include operations, features, means, or instructions for transmitting an indication of the timing of a random - access occasion to a UE via a downlink control channel command or an SSB.

[0030]

[0030] Some examples of methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for identifying QCL assumptions to be applied to the transmission of a downlink random access message in response to an uplink random access message, according to one or more rules, wherein the QCL assumption is related to 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 may be different from the second TCI state.

[0031]

[0031] In some examples of the methods, apparatus, and non-temporary 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 the basis for a QCL assumption according to one or more rules, wherein one or more rules specify that a downlink random access message to which a QCL assumption may apply may be a downlink control channel message scheduling 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 which may be linked for downlink control channel iterations.

[0032]

[0032] In some examples of the methods, apparatus, and non-temporary 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 the basis for a QCL assumption according to one or more rules, wherein one or more rules specify that a downlink random access message to which a QCL assumption may apply may be a RAR message that is a multi-TCI state downlink shared channel that changes in at least one of SDM, FDM, TDM, or single-frequency network schemes. [Brief explanation of the drawing]

[0033] [Figure 1]

[0033] A diagram showing an example of a wireless communication system that supports downlink control channel repetition with respect to downlink control channel commands according to an aspect of the present disclosure. [Figure 2]

[0034] A diagram illustrating an example of a wireless communication system that supports downlink control channel repetitions relating to downlink control channel commands according to an aspect of the present disclosure. [Figure 3A]

[0035] A figure illustrating an example of a search space set configuration that supports downlink control channel iterations for downlink control channel commands according to an aspect of this disclosure. [Figure 3B] A figure illustrating an example of a search space set configuration that supports downlink control channel iterations for downlink control channel commands according to an aspect of this disclosure. [Figure 4A]

[0036] A figure illustrating an example of a random access timeline supporting downlink control channel iterations with respect to downlink control channel commands, according to aspects of this disclosure. [Figure 4B] A figure illustrating an example of a random access timeline supporting downlink control channel iterations with respect to downlink control channel commands, according to aspects of this disclosure. [Figure 5]

[0037] A diagram illustrating an example of a process flow supporting downlink control channel iterations relating to downlink control channel commands according to an aspect of this disclosure. [Figure 6]

[0038] A diagram illustrating an example of a process flow supporting downlink control channel iterations relating to downlink control channel commands according to an aspect of this disclosure. [Figure 7]

[0039] A block diagram of a device supporting downlink control channel iterations relating to downlink control channel commands, according to an aspect of the present disclosure. [Figure 8]A block diagram of a device supporting downlink control channel iterations relating to downlink control channel commands, according to an aspect of the present disclosure. [Figure 9]

[0040] A block diagram of a communications manager supporting downlink control channel iterations relating to downlink control channel commands, according to an aspect of the present disclosure. [Figure 10]

[0041] A diagram of a system including a device that supports downlink control channel iterations relating to downlink control channel commands, according to an aspect of the present disclosure. [Figure 11]

[0042] A block diagram of a device supporting downlink control channel iterations relating to downlink control channel commands, according to an aspect of the present disclosure. [Figure 12] A block diagram of a device supporting downlink control channel iterations relating to downlink control channel commands, according to an aspect of the present disclosure. [Figure 13]

[0043] A block diagram of a communications manager supporting downlink control channel iterations relating to downlink control channel commands, according to an aspect of the present disclosure. [Figure 14]

[0044] A diagram of a system including a device that supports downlink control channel iterations relating to downlink control channel commands, according to an aspect of the present disclosure. [Figure 15]

[0045] A flowchart illustrating a method for supporting downlink control channel iterations with respect to downlink control channel commands according to an aspect of the present disclosure. [Figure 16] A flowchart illustrating a method for supporting downlink control channel iterations with respect to downlink control channel commands according to an aspect of the present disclosure. [Figure 17] A flowchart illustrating a method for supporting downlink control channel iterations with respect to downlink control channel commands according to an aspect of the present disclosure. [Figure 18]A flowchart illustrating a method for supporting downlink control channel iterations with respect to downlink control channel commands according to an aspect of the present disclosure. [Modes for carrying out the invention]

[0034]

[0046] In some wireless communication systems, a user equipment (UE) may consist of one or more control resource sets (CORESETs). Each CORESET may include time and frequency resources within the 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 containing 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 send a PDCCH command requesting the UE to participate in a random access procedure via one or more PDCCH candidates linked for PDCCH iterations. However, if the PDCCH command is associated with linked PDCCH candidates, the UE may not be able to identify a timeline for sending uplink random access messages, such as random access request messages, after receiving the PDCCH command. Additionally, if a PDCCH directive relates to 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 the quasi-colocation (QCL) assumption that should be applied to the reception of one or more downlink random access messages corresponding to the PDCCH directive.

[0035]

[0047] The UE described herein may consist of one or more sets of rules for executing a random access procedure in accordance with a PDCCH directive received via a linked PDCCH candidate. Executing a random access procedure by the UE may include receiving a PDCCH directive, transmitting an uplink random access message, and receiving a DCI via a PDCCH that schedules downlink random access messages received via a physical downlink shared channel (PDSCH). After receiving a PDCCH directive 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). One or more rules may indicate that the delay period begins after the last symbol of the linked PDCCH candidate, which ends later in time.

[0036]

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

[0037]

[0049] As an addition or alternative, one or more rules may indicate that the UE may refrain from receiving a PDCCH directive if the PDCCH directive is associated with two or more linked PDCCH candidates. In such a case, the UE may receive the PDCCH directive through a PDCCH candidate that is not linked with other PDCCH candidates for iteration. For example, one or more rules may allow receiving a PDCCH directive through linked PDCCH candidates if the linked PDCCH candidates correspond to the same TCI state, and one or more rules may restrict receiving a PDCCH directive if the linked PDCCH candidates correspond to different TCI states. Thus, the UE may be configured with one or more rules regarding the receiving of PDCCH directives through linked PDCCH candidates to improve the reliability and efficiency of random access procedures corresponding to PDCCH directives.

[0038]

[0050] Aspects of this disclosure are first described in the context of wireless communication systems. Additional aspects of this disclosure are described with reference to search space set configurations, random access timelines, and process flows. Aspects of this disclosure are further illustrated and described with reference to device diagrams, system diagrams, and flowcharts relating to downlink control channel iterations with respect to downlink control channel commands.

[0039]

[0051] Figure 1 shows an example of a wireless communication system 100 that supports downlink control channel iterations relating to downlink control channel commands according to an aspect of the present 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, an LTE Advanced (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some examples, the wireless communication system 100 may support extended broadband communication, ultra-high reliability (e.g., mission-critical) communication, low-latency communication, communication using low-cost and low-complexity devices, or any combination thereof.

[0040]

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

[0041]

[0053] The UE115 may be distributed throughout the coverage area 110 of the wireless communication system 100, and each UE115 may be stationary, mobile, or both at different times. The UE115 may be devices of different forms or with different capabilities. Several exemplary UE115 are shown in Figure 1. The UE115 described herein may be capable of communicating with various types of devices, such as other UE115, 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 Figure 1.

[0042]

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

[0043]

[0055] One or more of the base stations 105 described herein may include, or be referred to as, a base transceiver station, a radio base station, an access point, a radio transceiver, a node B, an e-node B (eNB), a next-generation node B or giganode B (any of which may be called a gNB), a home node B, a home e-node B, or other preferred terms.

[0044]

[0056] UE115 may include, or may be referred to as, a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other preferred term, where “device” may also be referred to as a unit, station, terminal, or client, among other examples. UE115 may also include, or may be referred to as, a personal electronic device such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE115 may include, or may be referred to as, a wireless local loop (WLL) station, an Internet of Things (IoT) device, any Internet of Things (IoE) device, or a machine-type communications (MTC) device, among other examples, which may be implemented in various objects such as equipment, vehicles, meters, etc.

[0045]

[0057] The UE115 described herein may be capable of communicating with other UE115s that can sometimes function as relays, as shown in Figure 1, as well as with various types of devices, including, among other examples, a macro eNB or gNB, a small cell eNB or gNB, or a base station 105 and network equipment including a relay base station.

[0046]

[0058] UE115 and base station 105 may wirelessly communicate with each other via one or more communication links 125 over one or more carriers. The term “carrier” may refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting communication links 125. For example, the carrier used for communication link 125 may include a portion of a radio frequency spectrum band (e.g., BWP) operating 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 carrier operation, user data, or other signaling. The wireless communication system 100 may support communication with UE115 using carrier aggregation or multi-carrier operation. UE115 may consist of multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation can be used with both frequency-division duplex (FDD) component carriers and time-division duplex (TDD) component carriers.

[0047]

[0059] In some examples (for instance, in carrier aggregation configurations), a carrier may also have acquisition or control signaling to coordinate the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Advanced Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN)) and may be positioned according to a channel raster for discovery by the UE115. A carrier may operate in a standalone mode where initial acquisition and connection are performed by the UE115 via the carrier, or it may operate in a non-standalone mode where the connection is established using different carriers (e.g., the same or different radio access technologies).

[0048]

[0060] The communication link 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. The carrier may carry downlink communications or uplink communications (for example, in FDD mode), or may be configured to carry downlink communications and uplink communications (for example, in TDD mode).

[0049]

[0061] A carrier may be associated with a specific 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 for the carrier of a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)). Devices of the wireless communication system 100 (e.g., base station 105, UE 115, or both) may have a hardware configuration that supports communication over a specific carrier bandwidth, or may be configurable to support communication over 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 over carriers associated with multiple carrier bandwidths. In some examples, each serviced UE 115 may be configured to operate over a portion (e.g., subband, BWP) or all of the carrier bandwidth.

[0050]

[0062] The signal waveform transmitted on a carrier can consist of multiple subcarriers (for example, using multicarrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM). In systems employing MCM techniques, a resource element may consist of one symbol period (e.g., duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier interval 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). Therefore, the more resource elements the UE115 receives, and the higher the order of the modulation scheme, the higher the data rate for the UE115 can be. Wireless communication resources can refer to a combination of radio frequency spectral resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers can further increase the data rate or data integrity for communication with the UE115.

[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, UE115 may consist of multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communication for UE115 may be limited to one or more active BWPs.

[0052]

[0064] The time interval for base station 105 or UE115 is, for example, T s = 1 / (Δf max ·N f It can refer to a sampling period of ) seconds, which can be expressed in multiples of basic time units, where Δf max This can represent the maximum supported subcarrier interval, N fThis may represent the maximum supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources 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 contain multiple sequentially numbered subframes or slots, each subframe or slot may have the same duration. In some examples, a frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into several slots. Alternatively, each frame may contain a variable number of slots, the number of slots may depend on the subcarrier interval. Each slot may contain several symbol periods (e.g., depending on the length of the cyclic prefix prepared for each symbol period). In some wireless communication systems 100, a slot may be further divided into several minislots, each containing one or more symbols. Except for the cyclic prefix, each symbol period may contain one or more (e.g., N) symbols. f It may include a sampling period of (1) units. The duration of the symbol period may depend on the subcarrier interval or frequency operating bandwidth.

[0054]

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

[0055]

[0067] Physical channels can be multiplexed on a carrier according to various techniques. Physical control channels and physical data channels can be multiplexed on a downlink carrier using, for example, one or more of the following techniques: time-division multiplexing (TDM), frequency-division multiplexing (FDM), or hybrid TDM-FDM. A control region (e.g., CORESET) for a physical control channel may be defined by several symbolic periods and may extend across the carrier's system bandwidth or a subset of the system bandwidth. One or more control regions (e.g., CORESET) may be configured for a set of UE115s. For example, one or more UE115s may monitor or search for control regions for control information according to one or more search space sets, each search space set may contain one or more control channel candidates in one or more cascaded aggregation levels. Aggregation levels for control channel candidates may refer to several control channel resources (e.g., control channel elements (CCEs)) related to encoded information for a control information format having a given payload size. The search space set may include a common search space set configured to send control information to multiple UE115s, and a UE-specific search space set for sending control information to a specific UE115.

[0056]

[0068] Each base station 105 may provide communication coverage through one or more cells, such as macrocells, small cells, hotspots, or other types of cells, or any combination thereof. The term “cell” may refer to a logical communication entity used for communication with base station 105 (for example, on a carrier) and may be associated with an identifier for distinguishing neighboring cells (for example, a physical cell identifier (PCID), a virtual cell identifier (VCID), or something else). In some examples, a cell may also refer to a geographical coverage area 110 or a portion of geographical coverage area 110 (for example, a sector) on which the logical communication entity operates. Such cells may span from smaller areas (for example, structures, subsets of structures) to larger areas, depending on various factors such as the capabilities of base station 105. For example, a cell may be, among other examples, a building, a subset of a building, or external space between or overlapping with geographical coverage areas 110, or include them.

[0057]

[0069] Macrocells generally cover relatively large geographical areas (e.g., a radius of several kilometers) and can enable unrestricted access by UE115s subscribed to the services of a network provider that supports macrocells. Small cells, compared to macrocells, may be associated with low-power base stations 105 and may operate in the same or different (e.g., licensed, unlicensed) frequency bands as macrocells. Small cells may provide unrestricted access to UE115s subscribed to the services of a network provider, or they may provide restricted access to UE115s associated with small cells (e.g., UE115s in limited subscriber groups (CSGs), UE115s associated with users in their homes or offices). 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 cases, 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 can provide access to different types of devices.

[0059]

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

[0060]

[0072] The wireless communication system 100 can support synchronous or asynchronous operation. In synchronous operation, base stations 105 may have similar frame timings, and transmissions from different base stations 105 may be approximately synchronized in time. In asynchronous operation, base stations 105 may have different frame timings, and transmissions from different base stations 105 may, in some cases, not be synchronized in time. The techniques described herein may be used for either synchronous or asynchronous operation.

[0061]

[0073] Some UE115s, such as MTC devices or IoT devices, may be low-cost or low-complexity devices that can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that enables devices to communicate with each other or with base stations 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, relay such information to a central server or application program that utilizes the information, or present the information to a human interacting with the application program. Some UE115s 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 detection, physical access control, and transaction-based business billing.

[0062]

[0074] Some UE115s may be configured to employ power-saving operating modes such as half-duplex communication (e.g., modes that support one-way communication via transmit or receive rather than transmit and receive simultaneously). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power-saving techniques for the UE115 include entering a power-saving deep sleep mode when not engaged in active communication, operating on a limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE115s may be configured for operation using narrowband protocol types associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within the carrier, within the carrier's protected band, or outside the carrier.

[0063]

[0075] The wireless communication system 100 may be configured to support ultra-high reliability communication, low latency communication, or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-high reliability low latency communication (URLLC) or mission-critical communication. The UE 115 may be designed to support ultra-high reliability functionality, low latency functionality, or critical functionality (e.g., mission-critical functionality). Ultra-high reliability communication may include private or group communication 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 functionality may include service prioritization, and mission-critical services may be used for public safety or general commercial applications. The terms ultra-high reliability, low latency, mission-critical, and ultra-high reliability low latency may be used interchangeably herein.

[0064]

[0076] In some examples, a UE115 may also be able to communicate directly with other UE115s over a device-to-device (D2D) communication link 135 (for example, using peer-to-peer (P2P) or D2D protocols). One or more UE115s utilizing D2D communication may be within the geographical coverage area 110 of the base station 105. Other UE115s in such a group may be outside the geographical 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 UE115s communicating via D2D communication may utilize a one-to-many (1:M) system where each UE115 transmits to any other UE115 in the group. In some examples, the base station 105 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication occurs between UE115s 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 side-link communication channel between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-anything (V2X) communication, vehicle-to-vehicle (V2V) communication, or any combination thereof. Vehicles may signal information about traffic conditions, signal scheduling, weather, safety, emergencies, or any other information related to the V2X system. In some examples, vehicles in the V2X system may communicate with roadside infrastructure such as roadside units, or with a network via one or more network nodes (e.g., base station 105) using vehicle-to-network (V2N) communication, or both.

[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 advanced packet core (EPC) or 5G core (5GC) that includes at least one control plane entity that manages access and mobility (e.g., a Mobility Management Entity (MME), an Access and Mobility Management Function (AMF)) and at least one user plane entity that routes packets or interconnections to the external network (e.g., a Serving Gateway (S-GW), a Packet Data Network (PDN) Gateway (P-GW), or a User Plane Function (UPF)). The control plane entity may manage non-access layer (NAS) functions, such as mobility, authentication, and bearer management, for UE 115 serviced by base station 105 associated with the core network 130. User IP packets may be forwarded through user plane entities that may provide IP address allocation and other functions. A user plane entity may be connected to an IP service 150 for one or more network operators. The IP service 150 may include access to the Internet, an intranet, an IP multimedia subsystem (IMS), or a packet-switched streaming service.

[0067]

[0079] Some of the network devices, such as the base station 105, may include sub-components such as access network entities 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 called radio heads, smart radio heads, or transmit / receive points (TRPs). Each access network transmitting entity 145 may include one or more antenna panels. In some configurations, the 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., base station 105).

[0068]

[0080] The wireless communication system 100 may typically operate using one or more frequency bands in 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, as wavelengths range from approximately 1 decimeter to 1 meter in length. While UHF waves may be blocked or redirected by buildings and environmental features, the waves may penetrate structures well enough for a macrocell to serve a UE 115 located indoors. Transmitting UHF waves may be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers) compared to transmissions using lower frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.

[0069]

[0081] The wireless communication system 100 may also operate in the ultra-high frequency (SHF) region, using a frequency band from 3 GHz to 30 GHz, also known as the centimeter band, or in 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) communication between a UE 115 and a base station 105, where the EHF antennas of each device may be smaller and more closely spaced than UHF antennas. In some examples, this may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be subject to greater atmospheric attenuation than SHF or UHF transmissions and may be over shorter distances. The techniques disclosed herein may be employed across transmissions using one or more different frequency domains, and the specified use of bands across these frequency domains 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 license-assisted access (LAA), unlicensed LTE (LTE-U) radio access technology, or NR technology in unlicensed bands such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in unlicensed radio frequency spectrum bands, devices such as base station 105 and UE 115 may employ carrier detection for collision detection and avoidance. In some examples, operation in unlicensed bands may be based on a carrier aggregation configuration with component carriers operating in licensed bands (e.g., LAA). Operation in unlicensed spectrums may include, among other examples, downlink transmission, uplink transmission, P2P transmission, or D2D transmission.

[0071]

[0083] Base station 105 or UE115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of base station 105 or UE115 may be located within one or more antenna arrays or antenna panels that can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be collated in an antenna assembly, such as an antenna tower. In some examples, the antennas or antenna arrays associated with base station 105 may be located in a variety of geographical locations. Base station 105 may have an antenna array with several rows and columns of antenna ports that base station 105 can use to support beamforming of communication with UE115. Similarly, UE115 may have one or more antenna arrays that can support various MIMO or beamforming operations. As an addition or alternative, an antenna panel may support radio frequency beamforming for signals transmitted through the antenna ports.

[0072]

[0084] A base station 105 or UE115 may use MIMO communication to leverage multipath signal propagation and increase spectral efficiency by transmitting or receiving multiple signals through different spatial layers. Such techniques are sometimes called spatial multiplexing. Multiple signals may be transmitted by a transmitting device through different antennas or different combinations of antennas, for example. Similarly, multiple signals may be received by a receiving device through different antennas or different combinations of antennas. Each of the multiple signals may be called 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 measurement 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 called spatial filtering, directional transmission, or directional reception, is a signal processing technique that can be used in a transmitting or receiving device (e.g., base station 105, UE115) to shape or steer an antenna beam (e.g., transmit beam, receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals communicated through the antenna elements of an antenna array such that several signals propagating in a particular orientation relative to the antenna array experience constructive interference and others experience destructive interference. Coordination of signals communicated through antenna elements may involve a transmitting or receiving device applying amplitude offset, phase offset, or both to the signals carried through the antenna elements associated with the device. Coordination associated with each antenna element 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 UE 115 may use beam sweeping techniques as part of its beamforming operation. For example, the base station 105 may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with the UE 115. Several signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by the base station 105 in different directions. For example, the base station 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. Transmissions in different beam directions may be used to identify the beam direction for subsequent transmission or reception by the base station 105 (e.g., by a transmitting device such as the base station 105, or by a receiving device such as the UE 115).

[0075]

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

[0076]

[0088] In some examples, transmission by a device (e.g., by base station 105 or UE115) 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 base station 105 to UE115). UE115 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. Base station 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel-state information reference signals (CSI-RS)) that can be precoded or amplified. UE115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook). While these techniques have been described in relation to signals transmitted by base station 105 in one or more directions, UE 115 may employ similar techniques for transmitting signals multiple times in different directions (for example, to identify beam directions for subsequent transmission or reception by UE 115) or for transmitting signals in a single direction (for example, to transmit data to a receiving device).

[0077]

[0089] A receiving device (e.g., UE115) may attempt multiple receiving configurations (e.g., directional listening) when receiving various signals from base station 105, such as synchronization signals, reference signals, beam selection signals, or other control signals. For example, a receiving device may attempt multiple receiving directions by receiving through different antenna subarrays, by processing the received signal according to different antenna subarrays, by receiving according to different sets of receive beamforming weights (e.g., different directional listening weight sets) applied to the received signal at multiple antenna elements of an antenna array, or by processing the received signal according to different sets of receive beamforming weights applied to the received signal at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, a receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receiving configuration can be matched in a beam direction determined based on listening according to different receiving configuration directions (for example, a beam direction determined to have the highest signal intensity, 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 operating 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. The Radio Link Control (RLC) layer may perform packet segmentation and reassembly for communication over logical channels. The Medium Access Control (MAC) layer may perform priority processing and multiplexing logical channels to transport channels. The MAC layer may also use error detection techniques, error correction techniques, or both to support retransmission at the MAC layer to improve link efficiency. In the control plane, the Radio Resource Control (RRC) protocol layer may provide the establishment, configuration, and maintenance of RRC connections between the UE 115 and the base station 105 or core network 130, supporting radio bearers for user plane data. At the physical layer, transport channels may be mapped to physical channels.

[0079]

[0091] UE115 and base station 105 may support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Retransmission Request (ARQ) feedback is one technique to increase the likelihood of accurate data reception on communication link 125. HARQ may include a combination of error detection (e.g., using cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Retransmission Request (ARQ)). HARQ may improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise conditions). In some examples, devices may support same-slot HARQ feedback, where the device may provide HARQ feedback in a particular slot for data received in the previous symbol in that slot. In other cases, the device may provide HARQ feedback in subsequent slots or according to some other time interval.

[0080]

[0092] In some examples, UE115 may receive a downlink control channel command via two or more downlink control channel candidates linked for downlink control channel iteration (e.g., PDCCH candidates, search space, or some other candidate time and / or frequency location of the downlink resource). UE115 may receive an indication that a first PDCCH candidate and a second PDCCH candidate are linked for PDCCH iteration. In some examples, the indication may be received via RRC signaling. UE115 may receive a PDCCH command via one or both of the first and second PDCCH candidates. A PDCCH command may be transmitted by base station 105, which may request UE115 to participate in a random access procedure. UE115 may perform a random access procedure related to the PDCCH command according to one or more rules regarding the reception of the PDCCH command via the linked PDCCH candidates. In some examples, one or more rules may indicate a threshold delay period between receiving a PDCCH command at UE115 and sending a random access message to base station 105 by UE115. In some examples, one or more rules may indicate rules for identifying QCL assumptions that should apply to receiving downlink random access messages. Additional or alternative, one or more rules may relate to whether UE115 can receive a PDCCH command via a linked PDCCH candidate. One or more rules may thereby reduce ambiguity related to timing, TCI state selection, or both for executing a random access procedure in response to receiving a PDCCH command via a linked PDCCH candidate, which may improve the reliability and efficiency of communication.

[0081]

[0093] Figure 2 shows an example of a wireless communication system 200 supporting downlink control channel iterations with respect to a downlink control channel command, according to aspects of the present 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 the example of the base station 105 and UE 115 described with reference to Figure 1. The base station 105-a and UE 115-a may communicate within a geographical 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 send a PDCCH command 225 to the UE 115-a via one or more PDCCH candidates linked for PDCCH iteration, requesting the UE 115-a to participate in a random access procedure.

[0082]

[0094] UE115-a and 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, UE115-a may send a random access request message 230 (e.g., Msg1) to initiate the random access procedure. The random access request message 230 may be sent via PRACH during a PRACH occasion. The random access procedure may be contention-based random access (CBRA) or contention-free random access (CFRA). During a CBRA procedure, UE115-a may randomly select a preamble and PRACH occasion for sending the random access request message 230 (e.g., based on a received synchronization signal block (SSB)). During the CFRA procedure, UE115-a may receive a random access preamble and / or PRACH occasion assignment from base station 105-a, and UE115-a may send a random access request message 230 according to the assigned preamble and PRACH occasion.

[0083]

[0095] If a random access request message 230 has not been sent by UE115-a, and base station 105-a has identified downlink data to send to UE115-a, base station 105-a may send a PDCCH command 225 to UE115-a to request that UE115-a participate in the random access procedure. UE115-a may send a random access request message 230 in response to the PDCCH command 225. UE115-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). If each bit in the Frequency Domain Resource Allocation (FDRA) field of the DCI is set to high (e.g., "1"), UE115-a may determine that the DCI corresponds to the PDCCH command 225.

[0084]

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

[0085]

[0097] One or more remaining fields in the PDCCH directive 225 may include an uplink or auxiliary uplink (SUL) indicator field, an SSB index field, a PRACH mask index field, one or more other reserved fields, or any combination thereof. The uplink or SUL indicator field may include bits to indicate whether UE115-a can send a random access request message 230 over the uplink or SUL. The SSB index field may include a number of bits (e.g., 6 bits) to indicate the SSB index associated with the CFRA. The PRACH mask field may include a number of bits (e.g., 4 bits) to indicate the PRACH mask index associated with the CFRA. Based on the SSB index and the PRACH mask index, UE115-a may determine a PRACH occasion for sending a random access request message 230. One or more remaining bits in the DCI carrying the PDCCH directive 225 may be reserved for other parameters or applications.

[0086]

[0098] PRACH occasions related to SSBs as indicated by PDCCH Directive 225 (for example, for CFRA) or measured (for example, for CBRA) may occur after a threshold delay period. The threshold delay period may begin after the last symbol of PDCCH Directive 225. That is, the first symbol of a PRACH occasion may occur at least after the threshold delay period of the last symbol of PDCCH Directive 225. The threshold delay period may consider physical uplink shared channel (PUSCH) preparation, random access preparation, BWP switching, uplink switching, or any combination thereof, in accordance with the capabilities of UE115-a.

[0087]

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

[0088]

[0100] UE115-a may be configured with one or more CORESETs (e.g., three, four, five, or any other amount of CORESETs in the BWP of a serving cell) for monitoring the PDCCH for the PDCCH directive 225 (e.g., 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) within each CORESET, as well as the active TCI state associated with each CORESET, may be configured in RRC. Each CORESET may contain 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 contain one or more PDCCH candidates (e.g., according to a given aggregation level). UE115-a may perform blind decoding of the PDCCH candidates in each search space set to receive the DCI. That is, UE115-a may monitor each PDCCH candidate in the search space set for the DCI. UE115-a may successfully decode one or more of the PDCCH candidates to obtain the DCI (for example, the CRC may pass). In some examples, one or more search space sets and corresponding PDCCH candidates may be linked for iterations of the DCI, sometimes referred to as PDCCH iterations or downlink control channel iterations. Additional embodiments of the configuration for the search space sets and PDCCH candidates may be described further elsewhere in this specification, including by reference to Figures 3A and 3B.

[0089]

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

[0090]

[0102] As described herein, a UE115, such as UE115-a, may consist of one or more rules relating to the reception of a PDCCH directive 225 via a linked PDCCH candidate. A UE115-a may receive a PDCCH directive 225 via a linked PDCCH candidate and execute a random access procedure in response to the PDCCH directive 225 according to one or more rules. One or more rules may indicate a timeline for executing a random access procedure in response to a PDCCH directive 225 received via a linked PDCCH candidate. For example, a rule may indicate that a threshold delay period after the reception of the PDCCH directive and before the PRACH occasion may begin after the last symbol of a PDCCH candidate that ends later in time than other linked PDCCH candidates.

[0091]

[0103] One or more rules may, in addition or alternatively, instruct UE115-a to select one or more TCI states to be used as the basis for QCL assumptions for receiving future downlink random access messages. That is, if PDCCH directive 225 is received via a PDCCH candidate associated with different TCI states, one or more rules may specify parameters for UE115-a to be used for the selection of one of the TCI states. In addition or alternatively, a rule may specify that two or more TCI states may be selected if UE115-a receives an indication that each downlink random access message is received via a PDCCH candidate to which it is linked, via a multi-TCI state PDSCH, or both. In some examples, one or more selected TCI states may represent one or more parameters for configuring a QCL relationship between demodulated reference signal (DMRS) ports for receiving downlink random access messages. If PDCCH directive 225 triggers the CBRA procedure, UE115-a may ignore one or more rules for selecting TCI states. UE115-a may instead determine QCL assumptions based on the measured SSB associated with the CBRA. That is, one or more rules may apply to a CFRA procedure but not to a CBRA procedure. In addition or alternatively, one or more rules may not apply to a CFRA procedure performed on a secondary cell (SCell).

[0092]

[0104] In some examples, one or more rules may indicate that UE115-a is not expected to receive PDCCH directive 225 via two PDCCH candidates linked for a PDCCH iteration. In other words, if UE115-a receives an indication 235 that two or more PDCCH candidates are linked, UE115-a may refrain from receiving PDCCH directive 225 transmitted via the linked PDCCH candidates. In some examples, a rule may allow reception of PDCCH directive 225 via linked PDCCH candidates if PDCCH directive 225 triggers a CBRA (e.g., the random access preamble index is 0), if PDCCH directive 225 triggers a CFRA on the SCell, or both. As an addition or alternative, a rule may allow reception of PDCCH directive 225 via linked PDCCH candidates if the linked PDCCH candidates correspond to their respective search space sets related to the same CORESET (e.g., the PDCCH candidates correspond to the same TCI state). In some examples, the rule may allow the reception of PDCCH directives 225 via linked PDCCH candidates if the linked PDCCH candidates correspond to their respective search space sets related to different CORESETs, each related to the same TCI state.

[0093]

[0105] Thereafter, the UE115 described herein may execute a random access procedure according to a configured set of rules for executing a random access procedure in response to a PDCCH instruction 225 received via a PDCCH candidate linked for PDCCH reception. The rules may specify instructions for the UE115 to execute the random access procedure, which may provide improved reliability, efficiency, and accuracy for the random access procedure corresponding to the PDCCH instruction.

[0094]

[0106] Figures 3A and 3B show examples of search space set configurations 300-a and 300-b supporting downlink control channel iterations with respect to downlink control channel commands, according to aspects of the present disclosure. Search space set configurations 300-a and 300-b implement, or may implement, several aspects of wireless communication systems 100 or 200. For example, search space set configurations 300-a and 300-b may represent exemplary configurations for UE115, which may represent an example of UE115, as described with reference to Figures 1 and 2.

[0095]

[0107] UE115 may be configured to monitor one or more (e.g., up to five) CORESETs in the CC's BWP. As illustrated with reference to Figure 2, a CORESET may contain a certain number of search space sets 305 (e.g., up to ten search space sets 305 in the CC's BWP). Thus, each search space set 305 may correspond to a single CORESET (e.g., and a single corresponding TCI state). A search space set 305 may be RRC-configured and may contain sets of time and frequency resources across one or more slots 320 in the time domain and one or more symbols 315 in one or more subchannels in the frequency domain (e.g., OFDM symbols 315). The RRC configuration for each exploration space set 305 may represent the associated CORESET, the monitoring occasions 310 within the exploration space set 305, the type of exploration 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 exploration space set 305, the amount of PDCCH candidates within the exploration space set 305 for each aggregation level, or any combination thereof. Resources within the exploration space set 305 may be continuous or discontinuous in time and frequency. For example, the monitoring occasions 310 within the exploration space set may be distributed across one or more symbols 315, slots 320, subchannels, or any combination thereof.

[0096]

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

[0097]

[0109] In some examples, two or more search space sets 305 may be linked for PDCCH iterations. UE115 may receive a representation of the linked search space sets via the RRC configuration. In some examples, the representation of the linked search space sets may indicate linked PDCCH candidates. For example, UE115 may identify linked watch occasions 310 within the search space set 305 and linked PDCCH candidates within the watch occasions 310 according to one or more rules indicated in the RRC configuration. Figures 3A and 3B show exemplary search space set configurations 300-a and 300-b for linked search space sets 305 containing linked PDCCH candidates.

[0098]

[0110] Figure 3A shows an exemplary 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 shows a monitoring occasion 310-a for the first search space set and a monitoring occasion 310-b for the second search space set in slot 320-a. Monitoring occasions 310-a and 310-b may include subsets of time and frequency resources in the first search space set 305-a and the second search space set 305-b, respectively.

[0099]

[0111] UE115 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 iterations. Based on one or more rules, UE115 may determine that the watchout occasions 310-a and 310-b are linked for PDCCH iterations. For example, the rules may indicate a one-to-one mapping between watchout occasions 310 of different search space sets 305.

[0100]

[0112] UE115 can determine one or more pairs of linked PDCCH candidates in linked monitoring occasions 310-a and 310-b according to the aggregation level and candidate index of each PDCCH candidate. For example, each search space set 305 may be configured to contain the same amount of PDCCH candidates for each aggregation level. Thus, UE115 can identify a first PDCCH candidate in monitoring occasion 310-a corresponding to a first aggregation level and a second PDCCH candidate in monitoring occasion 310-b, also corresponding to a first aggregation level. Based on the RRC configuration, the one-to-one mapping between monitoring occasions 310-a and 310-b, and the first aggregation level, UE115 can determine that the first and second PDCCH candidates are linked for PDCCH iterations. In the example of the search space set configuration 300-a, UE115 may identify three sets of linked PDCCH candidates between monitoring occasion 310-a of the first search space set 305-a and monitoring occasion 310-b of the second search space set 305-b (as indicated by three arrows between monitoring occasion 310-a and monitoring occasion 310-b, for example). DCI may be transmitted through one or both PDCCH candidates of each linked PDCCH candidate pair.

[0101]

[0113] Figure 3B shows 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 of search space set configuration 300-b, the first search space set 305-a may include two watch occasions 310-d and 310-e in slot 320-b, and the second search space set 305-b may include two watch occasions 310-c and 310-f in the same slot 320-b.

[0102]

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

[0103]

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

[0104]

[0116] Search space set configurations 300-a and 300-b may thereby represent intra-slot PDCCH iterations. In some exemplary search space set configurations 300 different from search space set configurations 300-a and 300-b, a first watch occasion 310 and its corresponding first PDCCH candidate in a first slot 320 may be linked to a second watch occasion 310 and its corresponding second PDCCH candidate in a second slot 320 (e.g., an inter-slot PDCCH iteration).

[0105]

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

[0106]

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

[0107]

[0119] To mitigate the impact of PDCCH iterations on random access procedures, the UE115 described herein may be configured with a set of rules regarding the reception of PDCCH directives via linked PDCCH candidates. The rules may specify a timeline for sending random access request messages, one or more parameters for selecting TCI states to be used as a basis for QCL assumptions for receiving 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 UE115 may refrain from receiving PDCCH directives via linked PDCCH candidates. Embodiments of configured rules are described in further detail elsewhere in this specification, including by reference to Figures 4A and 4B.

[0108]

[0120] Figures 4A and 4B show examples of random access timelines 400-a and 400-b supporting downlink control channel iterations with respect to downlink control channel commands, according to aspects of the present disclosure. Random access timelines 400-a and 400-b implement, or may implement, several embodiments of the wireless communication system 100 or 200 or the search space set configuration 300-a or 300-b. For example, random access timelines 400-a and 400-b may represent an example of a UE 115 and base station 105 described with reference to Figures 1 to 3, showing exemplary timelines for random access procedures performed by the UE 115 and base station 105. In some examples, the UE 115 may receive PDCCH commands via a linked PDCCH candidate 405, as described with reference to Figures 1 to 3. UE115 may execute a random access procedure corresponding to a PDCCH directive according to one or more rules relating to the reception of a PDCCH directive via a linked PDCCH candidate, as shown by random access timelines 400-a and 400-b.

[0109]

[0121] Figure 4A shows a first random access timeline 400-a supporting downlink control channel iterations relating to downlink control channel commands, according to an aspect of the present disclosure. In an example of random access timeline 400-a, UE115 may receive an indication via RRC signaling that PDCCH candidates 405-a and 405-b are linked for PDCCH iterations. For example, UE115 may receive RRC signaling indicating two search space sets linked for PDCCH iterations. In response to receiving the RRC signaling, UE115 may identify the linked monitoring occasions in the search space sets and identify the linked PDCCH candidates 405-a and 405-b within the linked monitoring occasions, according to one or more rules indicated via the RRC signaling, as described with reference to Figures 3A and 3B. As an addition or alternative, UE115 may identify linked PDCCH candidates 405-a and 405-b based on configuration or indication received via other control signaling (e.g., DCI, Media Access Control-Control Element (MAC-CE), or any other control signaling). UE115 may be configured to monitor linked PDCCH candidates 405-a and 405-b for DCI. In some examples, UE115 may perform soft combining before receiving DCI via both linked PDCCH candidates 405-a and 405-b. PDCCH candidates 405-a and 405-b may each include a set of PDCCH resources 435 (e.g., time and frequency resources allocated for the PDCCH). The PDCCH resources 435 of the first PDCCH candidate 405-a may or may not be contiguous in time and frequency with those of the second PDCCH candidate 405-b. In some cases, PDCCH candidate 405 is sometimes referred to as the downlink control channel candidate.

[0110]

[0122] As described herein, UE115 may receive PDCCH commands via a first PDCCH candidate 405-a, a second PDCCH candidate 405-b linked with the first PDCCH candidate 405-a for PDCCH iteration, or (for example, if UE115 soft combines the PDCCH candidates 405) both, in accordance with one or more rules relating to the reception of PDCCH commands via the linked PDCCH candidate 405. One or more rules may be configured (e.g., pre-configured) in UE115. Additionally or alternatively, UE115 may receive indications of one or more rules via control signaling from base station 105 or any other network entity.

[0111]

[0123] In some examples, one or more rules may indicate a timeline for UE115 to execute a random access procedure in response to a PDCCH directive received via the linked PDCCH candidate 405. Executing a random access procedure may involve UE115 sending an uplink random access message (e.g., Msg1) during a PRACH occasion 410-a (e.g., a set of PRACH resources 440 allocated to send uplink random access messages). An uplink random access message could be an example of a random access request message 230, as described with reference to Figure 2.

[0112]

[0124] One or more rules may indicate that a threshold delay period 420-a between a PDCCH order and a PRACH occasion 410-a starts after the last symbol of a reference PDCCH candidate 405 of the linked PDCCH candidates 405. That is, the reference PDCCH candidate 405 may trigger the threshold delay period 420-a. The reference PDCCH candidate 405 may correspond to a PDCCH candidate 405 that ends later in time in some examples. Referring to FIG. 4A, a second PDCCH candidate 405-b may end later in time than a 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 than the first PDCCH candidate 405-a but end later in time. The threshold delay period 420-a starts after the last symbol of the reference PDCCH candidate 405-b (e.g., a 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 the PDCCH order 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 is a first time period (e.g., N2) for PUSCH preparation according to the capabilities 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) for random access preparation by the UE 115, a third time period (e.g., Δ BWPSwitching ) for BWP switching, a fourth time period (e.g., T Switch ) for uplink switching, or a combination thereof. In some examples, the third and / or fourth time periods may each be 0 if there is no BWP switching or uplink switching.

[0114]

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

[0115]

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

[0116]

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

[0117]

[0129] A downlink random access message may include a DCI transmitted via PDCCH candidate 405-c, which includes PDCCH resource 435, a RAR message transmitted via PDSCH resource 445 during PDSCH occasion 415-a, or both. A 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 PDSCH occasion 415-a for the transmission of a RAR message. A RAR message (e.g., a downlink RAR message) may be transmitted by base station 105 in response to an uplink random access message.

[0118]

[0130] In the example of random access timeline 400-a, one or more rules may instruct UE 115 to select, based on one or more parameters, either 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 the basis for QCL assumption 425-a. In one example, the rule 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 rule 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. For example, if the rule specifies that the selection is based on which PDCCH candidate 405 terminates later in time, UE115 may select a second TCI state associated with a second PDCCH candidate 405-b as the basis for QCL assumption 425-a.

[0119]

[0131] In another example, the rule may specify that the selection of a first or second TCI state is based on the relative value between the first search space set ID of the first search space set corresponding to (e.g., including) the first PDCCH candidate 405-a and the second search space set ID of the second search space set corresponding to (e.g., including) the second PDCCH candidate 405-b. The rule may specify that the selection of a 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, UE115 selects the first TCI state associated with the first PDCCH candidate 405-a as the basis for QCL assumption 425-a.

[0120]

[0132] In another example, the rule may specify that the selection of a first or second TCI state is based on the relative value between a first CORESET ID associated with a first search space set corresponding to (e.g., including) a first PDCCH candidate 405-a, and a second CORESET ID associated with a second search space set corresponding to (e.g., including) a second PDCCH candidate 405-b. The rule may also specify that the selection of a 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 higher value, UE115 selects the second TCI state associated with the second PDCCH candidate 405-b as the basis for QCL assumption 425-a.

[0121]

[0133] In another example, the rule may specify that the selection of a first or second TCI state is based on the relative value between a first TCI state ID associated with a first TCI state of the first PDCCH candidate 405-a and a second TCI state ID associated with a second TCI state of the second PDCCH candidate 405-b. The rule may specify that the selection of a 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, the first value of the first TCI state may be lower than the 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, UE115 selects the first TCI state associated with the first PDCCH candidate 405-a as the basis for QCL assumption 425-a. Four exemplary parameters for selecting a TCI state are described, but it should be understood that one or more rules may specify any number of parameters or identifiers for the selection of a TCI state to be used as the basis for QCL assumption 425-a.

[0122]

[0134] One or more parameters for selecting a TCI state from 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, may be applicable when the PDCCH directive triggers a CFRA on a primary cell (PCell), a primary-secondary cell (PSCell), or both (for example, when the random access preamble index in the PDCCH directive is not zero). Otherwise, the TCI state for identifying QCL assumption 425-a for receiving downlink messages may not depend on one or more TCI states associated with the PDCCH directive, and UE115 may identify QCL assumption 425-a based on measured SSB or some other signaling.

[0123]

[0135] For example, when a PDCCH directive triggers a CBRA, the dependence of QCL assumption 425-a on a first TCI state associated with a first PDCCH candidate 405-a, a second TCI state associated with a second PDCCH candidate 405-b, or both, may not be applicable, and UE115 may identify QCL assumption 425-a based on the measured SSB associated with the CBRA procedure. When a PDCCH directive triggers a CBRA on a SCell, the PDCCH directive may be received on the SCell, and the DCI with RA-RNTI and the corresponding RAR message may be received on the PCell. Therefore, the TCI state associated with the reception of the PDCCH directive on the SCell may not be applicable to the reception of the DCI, RAR message, or both on the PCell.

[0124]

[0136] Therefore, in the example of Figure 4A, UE115 may be configured with one or more rules for receiving PDCCH commands via linked PDCCH candidates 405-a and 405-b, as shown by the random access timeline 400-a, and for executing random access procedures in response to the PDCCH commands. One or more rules may indicate a timeline for executing random access procedures in response to PDCCH commands. Additionally or alternatively, 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 be used as a basis for QCL assumption 425-a to be applied to the reception of one or more downlink random access messages.

[0125]

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

[0126]

[0138] UE115 may receive an indication that a first PDCCH candidate 405-d and a second PDCCH candidate 405-e are linked for a PDCCH iteration, and UE115 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 relating to the reception of a PDCCH command via the linked PDCCH candidate 405. One or more rules may specify that a threshold delay period 420-b between the reception of a PDCCH command in PRACH occasion 410-b and the transmission of an uplink random access message may begin after the last symbol of a PDCCH candidate 405 that terminates later in time (e.g., the second PDCCH candidate 405-e), as described with reference to Figure 4A.

[0127]

[0139] A first PDCCH candidate 405-d may be associated with a first TCI state, and a second PDCCH candidate 405-e may be associated with a second TCI state different from the first TCI state (for example, PDCCH commands may be received via different beams in each PDCCH candidate 405-d and 405-e). UE115 may identify QCL assumption 425-b to be applied to the reception of one or more downlink random access messages according to one or more rules. In the example of random access timeline 400-b, QCL assumption 425-b may correspond to both the first and second TCI states according to one or more rules. UE115 may select both a first TCI state associated with the first PDCCH candidate 405-d and a second TCI state associated with the second PDCCH candidate 405-e as the basis for QCL assumption 425-b to be applied to the reception of DCI, the reception of RAR messages, or both. For example, one or more rules may specify that if a corresponding downlink random access message to which a first and second TCI state may apply is transmitted via two PDCCH candidates 405 linked for PDCCH iterations, 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 the basis for QCL assumption 425-b.

[0128]

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

[0129]

[0141] In some examples, one or more rules may specify that when a RAR message is received via a multi-TCI state PDSCH that changes in one or more of the following spatial division multiplexing (SDM), FDM, TDM, or single-frequency network schemes, first and second TCI states may be selected as the basis for QCL assumption 425-b which should apply to the reception of RAR messages scheduled by DCI with RA-RNTI (for example, each DMRS port and each data layer of the PDSCH may be associated with the first and second TCI states). In the example of random access timeline 400-b, a RAR message may be received via a first PDSCH occasion 415-b which includes a first set 445 of PDSCH resources, and a second PDSCH occasion 415-c which includes a second set 445 of PDSCH resources. That is, in the example of Figure 4B, a RAR message may be transmitted via a multi-TCI state PDSCH using TDM. UE115 may, accordingly, select both the first and second TCI states as the basis for QCL assumption 425-b, and UE115 may apply QCL assumption 425-b to the reception of RAR messages.

[0130]

[0142] One or more rules for selecting the first and second TCI states as the basis for QCL assumption 425-b may be applicable when the PDCCH directive triggers a CFRA on PCell, PSCell, or both (for example, when the random access preamble index in the PDCCH directive is not zero). Otherwise, as will be further described with reference to Figure 4A, the TCI state for identifying QCL assumption 425-b for receiving a downlink message may not depend on one or more TCI states associated with the PDCCH directive, and UE115 may identify QCL assumption 425-b based on the measured SSB or some other signaling.

[0131]

[0143] Accordingly, the UE 115 described herein may be configured with one or more rules for receiving PDCCH commands via two or more linked PDCCH candidates and for performing random access procedures with base station 105 corresponding to the PDCCH commands. One or more rules may indicate a timeline for performing random access procedures in response to PDCCH commands received via linked PDCCH candidates, as described with reference to random access timelines 400-a and 400-b, one or more rules may specify QCL assumptions 425 to be used for receiving downlink random access messages in response to PDCCH commands received via linked PDCCH candidates, or both. That is, one or more rules may relate to receiving, processing, and responding to PDCCH commands received via linked PDCCH candidates.

[0132]

[0144] As an addition or alternative, one or more rules may specify whether a PDCCH directive can be received by UE115 via a linked PDCCH candidate 405. For example, one or more rules may specify that UE115 may not be expected to receive a PDCCH directive via two linked PDCCH candidates 405 for repetition (for example, a PDCCH directive with a PDCCH repetition may not be permitted). In such a case, UE115 may receive a PDCCH directive via a PDCCH candidate 405 that is not linked to another PDCCH candidate 405 for a PDCCH repetition. As an addition or alternative, one or more rules may permit the reception of a PDCCH directive via two linked PDCCH candidates 405 if the PDCCH candidates correspond to the same TCI state, the PDCCH directive triggers a CBRA, the PDCCH directive triggers a CFRA on the SCell, or any combination thereof.

[0133]

[0145] Figure 5 shows an example of a process flow 500 supporting downlink control channel iterations relating to downlink control channel commands according to an aspect of the present disclosure. The process flow 500 implements, or may be implemented by, several aspects of a wireless communication system 100 or 200. For example, the process flow 500 may include UE115-b and base station 105-b, which may be examples of UE115 and base station 105 described with reference to Figures 1 to 4. In some examples, UE115-b may consist of one or more rules relating to the reception of 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, UE115-b and base station 105-b may communicate with one or more other UE115s, base stations 105s, or other devices. Alternative examples of 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 mentioned below, or further steps may be added.

[0135]

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

[0136]

[0148] In 510, base station 105-b may transmit a downlink control channel command requesting UE 115-b to participate in a random access procedure, and 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] In 515, UE115-b and base station 105-b may perform a random access procedure related to a downlink control channel command in accordance with one or more rules relating to the reception of a downlink control channel command over a linked downlink control channel candidate. In some examples, performing a random access procedure in 515 may include UE115-b sending an uplink random access message (e.g., Msg1) to base station 105-b in accordance with one or more rules.

[0138]

[0150] Figure 6 shows an example of a process flow 600 supporting downlink control channel iterations relating to downlink control channel commands according to an aspect of the present disclosure. Process flow 600 implements, or may be implemented by, several aspects of a wireless communication system 100 or 200. For example, process flow 600 may include UE115-c and base station 105-c, which may be examples of UE115 and base station 105 described with reference to Figures 1 to 5. In some examples, UE115-c may consist of one or more rules relating to the reception of 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, UE115-c and base station 105-c may communicate with one or more other UE115s, base stations 105s, or other devices. Alternative examples of 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 mentioned below, or further steps may be added.

[0140]

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

[0141]

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

[0142]

[0154] Figure 7 shows a block diagram 700 of a device 705 supporting downlink control channel iterations with respect to downlink control channel commands, according to an aspect of the present disclosure. Device 705 may be an example of an aspect of the UE 115 described herein. Device 705 may include a receiver 710, a transmitter 715, and a communications manager 720. Device 705 may also include one or more processors, memory coupled to one or more processors, and instructions stored in the memory that are executable by one or more processors to enable one or more processors to perform the downlink control channel iteration functions described herein. Each of these components may communicate with one another (for example, via one or more buses).

[0143]

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

[0144]

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

[0145]

[0157] The communication manager 720, receiver 710, transmitter 715, or various combinations thereof or various components thereof may be examples of means for performing various forms of downlink control channel iteration for downlink control channel commands as described herein. For example, the communication manager 720, receiver 710, transmitter 715, or various combinations thereof 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 (for example, in communications management circuits). 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, which are configured to perform or otherwise support the functions described herein. In some examples, a processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (for example, by the processor executing instructions stored in the memory).

[0147]

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

[0148]

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

[0149]

[0161] The communications manager 720 may support wireless communications in the UE as illustrated in the examples disclosed herein. For example, the communications manager 720 may be configured to receive, or otherwise support, an indication that a first downlink control channel candidate and a second downlink control channel candidate are linked for downlink control channel iteration. The communications manager 720 may be configured to receive, or otherwise support, a downlink control channel command that requests 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 to perform, or otherwise support, a random access procedure associated with a downlink control channel command in accordance with one or more rules relating to the reception of the downlink control channel command via the linked downlink control channel candidate.

[0150]

[0162] As an addition or alternative, the communications manager 720 may support wireless communications in the UE, as illustrated in the examples disclosed herein. For example, the communications manager 720 may be configured or otherwise support means for receiving downlink control channel commands requesting the UE to participate in a random access procedure, the downlink control channel commands being received in accordance with one or more rules relating to the reception of downlink control channel commands via a plurality of downlink control channel candidates linked for downlink control channel iterations. The communications manager 720 may be configured or otherwise support means for executing a random access procedure based on the downlink control channel commands received in accordance with one or more rules.

[0151]

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

[0152]

[0164] Figure 8 shows a block diagram 800 of a device 805 supporting downlink control channel iterations with respect to downlink control channel commands, according to an aspect of the present disclosure. Device 805 may be an example of an aspect of device 705 or UE115 described herein. Device 805 may include a receiver 810, a transmitter 815, and a communications manager 820. Device 805 may also include a processor. Each of these components may communicate with one another (for example, via one or more buses).

[0153]

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

[0154]

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

[0155]

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

[0156]

[0168] The communications manager 820 may support wireless communications in the UE as illustrated in the examples disclosed herein. The linked PDCCH identification component 825 may be configured to receive, or otherwise support, an indication that a first downlink control channel candidate and a second downlink control channel candidate are linked for downlink control channel iteration. The PDCCH command component 830 may be configured to receive, or otherwise support, 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 to perform, or otherwise support, a random access procedure related to a downlink control channel command in accordance with one or more rules relating to the reception of the downlink control channel command via the linked downlink control channel candidate.

[0157]

[0169] As an addition or alternative, the communications manager 820 may support wireless communications in the UE, as illustrated in the examples disclosed herein. The PDCCH directive component 830 is configured, or may support, means for receiving a downlink control channel directive requesting the UE to participate in a random access procedure, the downlink control channel directive being received in accordance with one or more rules relating to the reception of the downlink control channel directive through a plurality of downlink control channel candidates linked for downlink control channel iterations. The random access procedure component 835 is configured, or may support, means for executing a random access procedure based on the downlink control channel directive received in accordance with one or more rules.

[0158]

[0170] In some cases, the linked PDCCH identification component 825, PDCCH command component 830, random access procedure component 835, or any combination thereof, may each be a processor (e.g., a transceiver processor, or a radio processor, or a transmitter processor, or a receiver processor), or at least part thereof. The processor may execute instructions stored in memory, coupled to memory, which enable the processor to perform or facilitate the functions of the linked PDCCH identification component 825, PDCCH command component 830, and random access procedure component 835 as described herein. A transceiver processor may be collated with and / or communicate with the device's transceiver (e.g., to direct its operation). A radio processor may be collated with and / or communicate with the device's radio (e.g., an NR radio, an LTE radio, or a Wi-Fi® radio) (e.g., to direct its operation). A transmitter processor may be collated with and / or communicate with the device's transmitter (e.g., to direct its operation). The receiver processor is associated with and / or can communicate with the device's receiver (for example, it can instruct its operation).

[0159]

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

[0160]

[0172] The communications manager 920 may support wireless communications in the UE as illustrated in the examples disclosed herein. The linked PDCCH identification component 925 may be configured to receive, or otherwise support, an indication that a first downlink control channel candidate and a second downlink control channel candidate are linked for downlink control channel iteration. The PDCCH command component 930 may be configured to receive, or otherwise support, 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 to perform, or otherwise support, a random access procedure related to a downlink control channel command in accordance with one or more rules relating to the reception of the downlink control channel command via the linked downlink control channel candidate.

[0161]

[0173] In some examples, to support the execution of a random access procedure, the uplink random access message component 940 may be configured, or otherwise support, for determining a random access occasion for sending an uplink random access message in response to a downlink control channel command. In some examples, to support the execution of a random access procedure, the uplink random access message component 940 may be configured, or otherwise support, for sending an uplink random access message during a random access occasion based on a first symbol of a random access occasion that lies after a threshold delay period that can 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 resulting from 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.

[0162]

[0174] In some examples, executing a random access procedure according to one or more rules is independent of whether the downlink control channel command is received between a first downlink control channel candidate or between 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 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 random access occasions, the uplink random access message component 940 is configured, or may otherwise support, for determining the timing of random access occasions based on the indication or measured SSB in the downlink control channel command.

[0163]

[0175] In some examples, the downlink random access message component 950 is configured as a means for receiving a downlink random access message in response to an uplink random access message, or may otherwise support it, wherein the downlink random access message is either a downlink control channel message scheduling a RAR message, or a RAR message itself.

[0164]

[0176] In some examples, to support the execution of a random access procedure, the uplink random access message component 940 is configured, or may support, a means for transmitting an uplink random access message in response to a downlink control channel command, wherein 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 the execution of a random access procedure, the QCL assumption component 945 is configured, or may support, a means for identifying a QCL assumption to be applied to the reception of a downlink random access message in response to an uplink random access message, according to one or more rules, wherein the QCL assumption is associated with at least one of the first or second TCI states.

[0165]

[0177] In some examples, to support the identification of a QCL assumption, the TCI selection component 955 may be configured, or otherwise support, for selecting one of a first TCI state or a second TCI state as the basis for a QCL assumption according to one or more rules, wherein 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 between a first downlink control channel candidate and a second downlink control channel candidate.

[0166]

[0178] In some examples, to support the identification of a QCL assumption, the TCI selection component 955 may be configured, or otherwise support, for selecting one of a first TCI state or a second TCI state as the basis for a QCL assumption according to one or more rules, wherein one or more rules specify that the selection of either the first TCI state or the second TCI state is based on the relative value between 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 the identification of a QCL assumption, the TCI selection component 955 may be configured, or otherwise support, for selecting one of a first TCI state or a second TCI state as a basis for a QCL assumption according to one or more rules, wherein 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 between 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 the identification of a QCL assumption, the TCI selection component 955 may be configured, or otherwise support, for selecting one of a first TCI state or a second TCI state as the basis for a QCL assumption according to one or more rules, wherein 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 between 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 the identification of a QCL assumption, the TCI selection component 955 may be configured, or otherwise support, for selecting both a first TCI state and a second TCI state as the basis for a QCL assumption according to one or more rules, wherein one or more rules specify that a downlink random access message to which a QCL assumption may apply is a downlink control channel message scheduling 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 linked for downlink control channel iterations.

[0170]

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

[0171]

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

[0172]

[0184] In addition or alternatively, the communications manager 920 may support wireless communications in the UE, as illustrated in the examples disclosed herein. In some examples, the PDCCH directive component 930 may be configured or otherwise support means for receiving a downlink control channel directive requesting the UE to participate in a random access procedure, the downlink control channel directive being received in accordance with one or more rules relating to the reception of the downlink control channel directive through a plurality of downlink control channel candidates linked for downlink control channel iterations. In some examples, the random access procedure component 935 may be configured or otherwise support means for executing a random access procedure based on a downlink control channel directive received in accordance with 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, or otherwise support, means for receiving downlink control channel commands via a downlink control channel candidate that is not linked to other downlink control channel candidates for iteration.

[0174]

[0186] In some examples, to support receiving downlink control channel commands according to one or more rules, the PDCCH command component 930 is configured, or may support, 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 downlink control channel iterations, where the first downlink control channel candidate corresponds to a first search space set associated with CORESET, and the second downlink control channel candidate corresponds to a second search space set associated with CORESET.

[0175]

[0187] In some examples, to support receiving downlink control channel commands according to one or more rules, the PDCCH command component 930 is configured, or may support, 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 downlink control channel iterations, wherein the first downlink control channel candidate corresponds to a first search space set associated with a first CORESET having TCI states, and the second downlink control channel candidate corresponds to a second search space set associated with a second CORESET having TCI states.

[0176]

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

[0177]

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

[0178]

[0190] Figure 10 shows a diagram of system 1000 including a device 1005 that supports downlink control channel iterations relating to downlink control channel commands, according to an aspect of the present disclosure. Device 1005 may be an example of, or include, a component of, device 705, device 805, or UE 115 as described herein. Device 1005 may wirelessly communicate with one or more base stations 105, UE 115, or any combination thereof. Device 1005 may include components for bidirectional voice and data communications, 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, a code 1035, and a processor 1040. These components may communicate electronically or be coupled (e.g., operably, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1045).

[0179]

[0191] The I / O controller 1010 can manage input and output signals for device 1005. The I / O controller 1010 can also manage peripheral devices not integrated into device 1005. In some cases, the I / O controller 1010 may represent physical connections or ports to external peripherals. 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, touchscreen, or similar device. In some cases, the I / O controller 1010 may be implemented as part of a processor, such as processor 1040. In some cases, the user may interact with the device 1005 via the I / O controller 1010 or via hardware components controlled by the I / O controller 1010.

[0180]

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

[0181]

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

[0182]

[0194] The processor 1040 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, 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 integrated into the processor 1040. The processor 1040 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1030) to cause device 1005 to perform various functions (e.g., functions or tasks supporting downlink control channel iterations with respect to downlink control channel commands). For example, device 1005 or components of device 1005 may include the processor 1040 and memory 1030 coupled to the processor 1040, and the processor 1040 and memory 1030 may be configured to perform various functions described herein.

[0183]

[0195] The communication manager 1020 may support wireless communication in the UE as illustrated in the examples disclosed herein. For example, the communication manager 1020 may be configured to receive, or otherwise support, an indication that a first downlink control channel candidate and a second downlink control channel candidate are linked for downlink control channel iteration. The communication manager 1020 may be configured to receive, or otherwise support, a downlink control channel command that requests 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 communication manager 1020 may be configured to perform, or otherwise support, a random access procedure associated with a downlink control channel command in accordance with one or more rules relating to the reception of the downlink control channel command via the linked downlink control channel candidate.

[0184]

[0196] As an addition or alternative, the communications manager 1020 may support wireless communications in the UE, as illustrated in the examples disclosed herein. For example, the communications manager 1020 may be configured or otherwise support means for receiving downlink control channel commands requesting the UE to participate in a random access procedure, the downlink control channel commands being received in accordance with one or more rules relating to the reception of downlink control channel commands via a plurality of downlink control channel candidates linked for downlink control channel iterations. The communications manager 1020 may be configured or otherwise support means for executing a random access procedure based on downlink control channel commands received in accordance with one or more rules.

[0185]

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

[0186]

[0198] In some examples, the communications manager 1020 may be configured to use or cooperate with the transceiver 1015, one or more antennas 1025, or any combination thereof, to perform various operations (e.g., receiving, monitoring, transmitting). 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, memory 1030, code 1035, or any combination thereof. For example, code 1035 may include instructions executable by the processor 1040 to cause device 1005 to perform various forms of downlink control channel iterations relating to the downlink control channel commands described herein, or the processor 1040 and memory 1030 may be configured to perform or support such operations, in some cases.

[0187]

[0199] Figure 11 shows a block diagram 1100 of a device 1105 supporting downlink control channel iteration with respect to downlink control channel commands, according to an aspect of the present disclosure. Device 1105 may be an example of an aspect of a base station 105 described herein. Device 1105 may include a receiver 1110, a transmitter 1115, and a communications manager 1120. Device 1105 may also include one or more processors, memory coupled to one or more processors, and instructions stored in the memory that are executable by one or more processors to enable one or more processors to perform the downlink control channel command iteration function described herein. Each of these components may communicate with one another (for example, via one or more buses).

[0188]

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

[0189]

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

[0190]

[0202] The communication manager 1120, receiver 1110, transmitter 1115, or various combinations thereof or various components thereof may be examples of means for performing various forms of downlink control channel iteration for downlink control channel commands as described herein. For example, the communication manager 1120, receiver 1110, transmitter 1115, or various combinations thereof 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 (for example, in communications management circuits). The hardware may include a processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, which are configured to perform or otherwise support the functions described herein. In some examples, a processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (for example, by the processor executing instructions stored in the memory).

[0192]

[0204] As an addition or alternative, in some examples, the communications manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be implemented in code executed by a processor (for example, as communications management software or firmware). When implemented in code executed by a processor, the functions of the communications manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, or any combination thereof or other programmable logic device (for example, configured as a means for performing or otherwise supporting 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 be integrated with the receiver 1110, the transmitter 1115, or both to receive information from the receiver 1110, send information to the transmitter 1115, or receive information, transmit information, or perform various other operations as described herein.

[0194]

[0206] The communication manager 1120 may support wireless communication at a base station as illustrated herein. For example, the communication manager 1120 may be configured to transmit to the UE an indication that a first downlink control channel candidate and a second downlink control channel candidate are linked for downlink control channel iteration, or may support such transmission. The communication manager 1120 may be configured to transmit to the UE 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, or may support such transmission. The communication manager 1120 may be configured to receive from the UE an uplink random access message related to the downlink control channel command, in accordance with one or more rules relating to the transmission of the downlink control channel command via the linked downlink control channel candidate, or may support such transmission.

[0195]

[0207] As an addition or alternative, the communications manager 1120 may support wireless communications at a base station, as illustrated in the examples disclosed herein. For example, the communications manager 1120 may be configured or otherwise support 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 relating to the reception of the downlink control channel command via a plurality of downlink control channel candidates linked for downlink control channel iterations. The communications manager 1120 may be configured or otherwise support means for receiving random access messages from the UE based on the downlink control channel command being transmitted according to one or more rules.

[0196]

[0208] Figure 12 shows a block diagram 1200 of a device 1205 that supports downlink control channel iterations with respect to downlink control channel commands, according to an aspect of the present disclosure. Device 1205 may be an example of an aspect of device 1105 or base station 105 as described herein. Device 1205 may include a receiver 1210, a transmitter 1215, and a communications manager 1220. Device 1205 may also include a processor. Each of these components may communicate with one another (for example, via one or more buses).

[0197]

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

[0198]

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

[0199]

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

[0200]

[0212] The communications manager 1220 may support wireless communications at a base station as illustrated herein. The linked PDCCH identification component 1225 is configured, or may support, means for transmitting to the UE an indication that a first downlink control channel candidate and a second downlink control channel candidate are linked for downlink control channel iteration. The PDCCH command component 1230 is configured, or may support, means for transmitting to the UE 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 uplink random access message component 1235 is configured, or may support, means for receiving from the UE an uplink random access message related to a downlink control channel command, in accordance with one or more rules relating to the transmission of downlink control channel commands via the linked downlink control channel candidate.

[0201]

[0213] As an addition or alternative, the communications manager 1220 may support wireless communications at a base station, as illustrated in the examples disclosed herein. The PDCCH command component 1230 is configured, or may support, 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 relating to the reception of the downlink control channel command via a plurality of downlink control channel candidates linked for downlink control channel iteration. The uplink random access message component 1235 is configured, or may support, means for receiving a random access message from the UE based on a downlink control channel command transmitted according to one or more rules.

[0202]

[0214] In some cases, the linked PDCCH identification component 1225, PDCCH command component 1230, and uplink random access message component 1235 may each be a processor (e.g., a transceiver processor, or a radio processor, or a transmitter processor, or a receiver processor), or at least part thereof. The processor may be coupled to memory and execute instructions stored in memory, enabling the processor to perform or facilitate the functions of the linked PDCCH identification component 1225, PDCCH command component 1230, and uplink random access message component 1235 as described herein. A transceiver processor may be collateralized with and / or communicate with the device's transceiver (e.g., to direct its operation). A radio processor may be collateralized with and / or communicate with the device's radio (e.g., an NR radio, an LTE radio, or a Wi-Fi radio) (e.g., to direct its operation). A transmitter processor may be collateralized with and / or communicate with the device's transmitter (e.g., to direct its operation). The receiver processor is associated with and / or can communicate with the device's receiver (for example, it can instruct its operation).

[0203]

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

[0204]

[0216] The communications manager 1320 may support wireless communications at a base station as illustrated herein. The linked PDCCH identification component 1325 may be configured or otherwise support means for transmitting to the UE an indication that a first downlink control channel candidate and a second downlink control channel candidate are linked for downlink control channel iteration. The PDCCH command component 1330 may be configured or otherwise support means for transmitting to the UE 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 uplink random access message component 1335 may be configured or otherwise support means for receiving from the UE an uplink random access message related to a downlink control channel command, in accordance with one or more rules relating to the transmission of downlink control channel commands via the linked downlink control channel candidate.

[0205]

[0217] In some examples, to support receiving uplink random access messages, the uplink random access message component 1335 may be configured, or otherwise support, means for receiving uplink random access messages during a random access occasion, based on a first symbol of the random access occasion 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 resulting from 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 one or more rules is independent of whether the downlink control channel command is sent during the first downlink control channel candidate or during 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.

[0207]

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

[0208]

[0220] In some examples, the downlink random access message component 1345 is configured as a means for sending a downlink random access message in response to an uplink random access message, or may otherwise support it, wherein the downlink random access message is either a downlink control channel message scheduling a RAR message, or a RAR message itself.

[0209]

[0221] In some examples, the QCL assumption component 1340 is configured, or may support, a means for identifying a QCL assumption to be applied to the transmission of a downlink random access message in response to an uplink random access message, according to one or more rules, wherein the QCL assumption is related to 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.

[0210]

[0222] In some examples, the TCI state selection component 1350 is configured, or may support, a means for selecting one of a first TCI state or a second TCI state as a basis for a QCL assumption according to one or more rules, wherein 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 between a first downlink control channel candidate and a second downlink control channel candidate.

[0211]

[0223] In some examples, the TCI state selection component 1350 may be configured or otherwise support a means for selecting one of a first TCI state or a second TCI state as a basis for a QCL assumption according to one or more rules, wherein 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 between 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 is configured or may support a means for selecting one of a first TCI state or a second TCI state as a basis for a QCL assumption according to one or more rules, wherein 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 between 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 is configured, or may support, a means for selecting one of a first TCI state or a second TCI state as a basis for a QCL assumption according to one or more rules, wherein 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 between 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 the identification of a QCL assumption, the TCI state selection component 1350 is configured, or may support, for selecting both a first TCI state and a second TCI state as the basis for a QCL assumption according to one or more rules, wherein one or more rules specify that a downlink random access message to which a QCL assumption may apply is a downlink control channel message scheduling 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 linked for downlink control channel iterations.

[0215]

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

[0216]

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

[0217]

[0229] In addition or alternatively, the communications manager 1320 may support wireless communications at a base station, as illustrated in the examples disclosed herein. In some examples, the PDCCH command component 1330 is configured, or may support, 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 relating to the reception of the downlink control channel command over a plurality of downlink control channel candidates linked for downlink control channel iteration. In some examples, the uplink random access message component 1335 is configured, or may support, for receiving a random access message from the UE based on a 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, or otherwise support, for transmitting downlink control channel commands over a downlink control channel candidate that is not linked to other downlink control channel candidates for iteration.

[0219]

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

[0220]

[0232] In some examples, to support transmitting downlink control channel commands according to one or more rules, the PDCCH command component 1330 is configured, or may support, 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 downlink control channel iteration, wherein the first downlink control channel candidate corresponds to a first search space set associated with a first CORESET having TCI states, and the second downlink control channel candidate corresponds to a second search space set associated with a second CORESET having TCI states.

[0221]

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

[0222]

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

[0223]

[0235] Figure 14 shows a diagram of a system 1400 including a device 1405 that supports downlink control channel iterations relating to downlink control channel commands, according to an aspect of the present disclosure. Device 1405 may be an example of, or include, a component of, device 1105, device 1205, or base station 105 as described herein. Device 1405 may wirelessly communicate with one or more base stations 105, UE 115, or any combination thereof. Device 1405 may include components for bidirectional voice and data communications, 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, a code 1435, a processor 1440, and an inter-station communications manager 1445. These components may communicate electronically or be coupled (e.g., operably, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1450).

[0224]

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

[0225]

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

[0226]

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

[0227]

[0239] The processor 1440 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, 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 integrated into the processor 1440. The processor 1440 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1430) to cause device 1405 to perform various functions (e.g., functions or tasks supporting downlink control channel iterations with respect to downlink control channel commands). For example, device 1405 or components of device 1405 may include the processor 1440 and memory 1430 coupled to the processor 1440, and the processor 1440 and memory 1430 may be configured to perform various functions described herein.

[0228]

[0240] The inter-station communication manager 1445 may manage communication with other base stations 105 and may include a controller or scheduler to coordinate communication with the UE 115 in cooperation with other base stations 105. For example, the inter-station communication 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 communication manager 1445 may provide an X2 interface within the LTE / LTE-A wireless communication network technology to provide communication between base stations 105.

[0229]

[0241] The communications manager 1420 may support wireless communications at a base station as illustrated herein. For example, the communications manager 1420 may be configured to transmit to the UE an indication that a first downlink control channel candidate and a second downlink control channel candidate are linked for downlink control channel iteration, or may support such transmission. The communications manager 1420 may be configured to transmit to the UE a downlink control channel command requesting the UE to participate in a random access procedure via one or both of the first and second downlink control channel candidates, or may support such transmission. The communications manager 1420 may be configured to receive from the UE an uplink random access message related to the downlink control channel command, in accordance with one or more rules relating to the transmission of the downlink control channel command via the linked downlink control channel candidates, or may support such transmission.

[0230]

[0242] As an addition or alternative, the communications manager 1420 may support wireless communications at a base station, as illustrated in the examples disclosed herein. For example, the communications manager 1420 may be configured or otherwise support 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 relating to the reception of the downlink control channel command via a plurality of downlink control channel candidates linked for downlink control channel iteration. The communications manager 1420 may be configured or otherwise support means for receiving random access messages from a UE based on the downlink control channel command being transmitted according to one or more rules.

[0231]

[0243] In some examples, the communications manager 1420 may be configured to use or cooperate with the transceiver 1415, one or more antennas 1425, or any combination thereof, to perform various operations (e.g., receiving, monitoring, transmitting). 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, memory 1430, code 1435, or any combination thereof. For example, code 1435 may include instructions executable by the processor 1440 to cause device 1405 to perform various forms of downlink control channel iterations relating to the downlink control channel commands described herein, or the processor 1440 and memory 1430 may be configured to perform or support such operations, in some cases.

[0232]

[0244] Figure 15 shows a flowchart illustrating a method 1500 supporting downlink control channel iterations relating to downlink control channel commands, according to an aspect of this disclosure. The operation of method 1500 may be implemented by a UE or its components as described herein. For example, the operation of method 1500 may be performed by UE 115 as described with reference to Figures 1 to 10. In some examples, the UE may execute a set of instructions to control a functional element of the UE to perform the described function. Additionally or alternatively, the UE may perform aspects of the described function using dedicated hardware.

[0233]

[0245] In 1505, the method 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. The operation of 1505 may be performed according to the examples disclosed herein. In some examples, the operation of 1505 may be performed by linked PDCCH identification component 925 as described with reference to Figure 9.

[0234]

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

[0235]

[0247] In 1515, the method may include executing a random access procedure related to a downlink control channel command in accordance with one or more rules relating to the reception of the downlink control channel command via a linked downlink control channel candidate. The operation of 1515 may be performed according to the examples disclosed herein. In some examples, the operation of 1515 may be performed by a random access procedure component 935 described with reference to Figure 9.

[0236]

[0248] Figure 16 shows a flowchart illustrating a method 1600 supporting downlink control channel iterations relating to downlink control channel commands, according to an aspect of this disclosure. The operation of method 1600 may be implemented by a base station or its components as described herein. For example, the operation of method 1600 may be performed by a base station 105 as described with reference to Figures 1-6 and 11-14. In some examples, the base station may execute a set of instructions to control the functional elements of the base station to perform the functions described. In addition or alternatively, the base station may perform aspects of the functions described using dedicated hardware.

[0237]

[0249] In 1605, the method may include transmitting a signal to the UE indicating that a first downlink control channel candidate and a second downlink control channel candidate are linked for downlink control channel iteration. The operation of 1605 may be performed according to the examples disclosed herein. In some examples, the operation of 1605 may be performed by the linked PDCCH identification component 1325 described with reference to Figure 13.

[0238]

[0250] In 1610, the method may include sending a downlink control channel command to the UE requesting the UE to participate in a random access procedure via one or both of the first and second downlink control channel candidates. The operation of 1610 may be performed according to the examples disclosed herein. In some examples, the operation of 1610 may be performed by the PDCCH command component 1330 described with reference to Figure 13.

[0239]

[0251] In 1615, the method may include receiving an uplink random access message related to a downlink control channel command from the UE in accordance with one or more rules relating to the transmission of the downlink control channel command over a linked downlink control channel candidate. The operation of 1615 may be performed according to the examples disclosed herein. In some examples, the operation of 1615 may be performed by the uplink random access message component 1335, as described with reference to Figure 13.

[0240]

[0252] Figure 17 shows a flowchart illustrating a method 1700 supporting downlink control channel iterations relating to downlink control channel commands, according to an aspect of the present disclosure. The operation of method 1700 may be implemented by a UE or its components as described herein. For example, the operation of method 1700 may be performed by UE 115 as described with reference to Figures 1 to 10. In some examples, the UE may execute a set of instructions to control a functional element of the UE to perform the described function. Additionally or alternatively, the UE may perform aspects of the described function using dedicated hardware.

[0241]

[0253] In 1705, the method may include receiving a downlink control channel directive requesting the UE to participate in a random access procedure, the downlink control channel directive being received in accordance with one or more rules relating to the reception of downlink control channel directives via a plurality of downlink control channel candidates linked for downlink control channel iterations. The operation of 1705 may be performed according to the examples disclosed herein. In some examples, the operation of 1705 may be performed by a PDCCH directive component 930 described with reference to Figure 9.

[0242]

[0254] In 1710, the method may include executing a random access procedure based on a downlink control channel command received in accordance with one or more rules. The operation of 1710 may be performed according to the examples disclosed herein. In some examples, the operation of 1710 may be performed by the random access procedure component 935 described with reference to Figure 9.

[0243]

[0255] Figure 18 shows a flowchart illustrating a method 1800 supporting downlink control channel iterations relating to downlink control channel commands, according to an aspect of this disclosure. The operation of method 1800 may be implemented by a base station or its components as described herein. For example, the operation of method 1800 may be performed by a base station 105 as described with reference to Figures 1-6 and 11-14. In some examples, the base station may execute a set of instructions to control the functional elements of the base station to perform the functions described. In addition or alternatively, the base station may perform aspects of the functions described using dedicated hardware.

[0244]

[0256] In 1805, the method may include sending a downlink control channel command to the UE requesting the UE to participate in a random access procedure, the downlink control channel command being sent in accordance with one or more rules relating to the reception of the downlink control channel command via a plurality of downlink control channel candidates linked for downlink control channel iterations. The operation of 1805 may be performed according to the examples disclosed herein. In some examples, the operation of 1805 may be performed by the PDCCH command component 1330 described with reference to Figure 13.

[0245]

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

[0246]

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

[0247]

[0259] Embodiment 1: A method for wireless communication in a user device (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 executing a random access procedure associated with the downlink control channel command in accordance with one or more rules relating to the reception of the downlink control channel command via the linked downlink control channel candidates.

[0248]

[0260] Embodiment 2: The method according to Embodiment 1, further comprising: executing a random access procedure determining a random access occasion for sending an uplink random access message in response to a downlink control channel command; and sending an uplink random access message during the random access occasion, at least in part on the fact that a first symbol of the random access occasion is after a threshold delay period triggered by a reference downlink control channel candidate among the downlink control channel candidates to be linked.

[0249]

[0261] Embodiment 3: The method according to Embodiment 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, wherein one or more rules indicate that the threshold delay period begins after the last symbol of the second downlink control channel candidate.

[0250]

[0262] Embodiment 4: The method according to Embodiment 2 or 3, wherein executing a random access procedure according to one or more rules is independent of whether the downlink control channel command is received between a first downlink control channel candidate or between a second downlink control channel candidate.

[0251]

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

[0252]

[0264] Embodiment 6: The method according to any one of embodiments 2 to 5, wherein determining random access occasions comprises determining the timing of random access occasions based at least in part on the indicated or measured SSB in the downlink control channel command.

[0253]

[0265] Embodiment 7: The method according to any one of embodiments 1 to 6, further comprising: executing a random access procedure, transmitting an uplink random access message in response to a downlink control channel command, identifying a QCL assumption to be applied to receiving a downlink random access message in response to an uplink random access message, according to one or more rules, wherein 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 or second TCI states.

[0254]

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

[0255]

[0267] Embodiment 9: The method of Embodiment 7, wherein identifying a QCL assumption comprises selecting one of a first TCI state or a second TCI state as the basis for a QCL assumption according to one or more rules, wherein one or more rules specify that the selection of either the first TCI state or the second TCI state is at least partially based on the relative value between 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.

[0256]

[0268] Embodiment 10: The method of Embodiment 7, wherein identifying a QCL assumption comprises selecting one of a first TCI state or a second TCI state as the basis for a QCL assumption according to one or more rules, wherein one or more rules specify that the selection of either the first TCI state or the second TCI state is at least partially based on a relative value between 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.

[0257]

[0269] Embodiment 11: The method of Embodiment 7, wherein identifying a QCL assumption comprises selecting one of a first TCI state or a second TCI state as the basis for a QCL assumption according to one or more rules, wherein one or more rules specify that the selection of either the first TCI state or the second TCI state is at least partially based on a relative value between 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] Embodiment 12: The method of Embodiment 7, wherein identifying a QCL assumption comprises selecting both a first TCI state and a second TCI state as the basis for a QCL assumption according to one or more rules, wherein one or more rules specify that a downlink random access message to which the QCL assumption applies is a downlink control channel message scheduling 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 linked for downlink control channel iterations.

[0259]

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

[0260]

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

[0261]

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

[0262]

[0274] Embodiment 16: A method for wireless communication at a base station, comprising: transmitting an indication to the 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 relating to the transmission of the downlink control channel command via the linked downlink control channel candidates.

[0263]

[0275] Embodiment 17: The method of Embodiment 26, further comprising receiving an uplink random access message during a random access occasion, at least in part on the basis that the first symbol of the random access occasion is after a threshold delay period triggered by a reference downlink control channel candidate among the downlink control channel candidates to be linked.

[0264]

[0276] Embodiment 18: The method of Embodiment 17, 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, wherein one or more rules indicate that the threshold delay period begins after the last symbol of the second downlink control channel candidate.

[0265]

[0277] Embodiment 19: The method according to Embodiment 17 or 18, wherein receiving an uplink random access message according to 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] Embodiment 20: The method according to any one of embodiments 17 to 19, further comprising transmitting a downlink control channel command or an indication of the timing of random access occasions to the UE.

[0267]

[0279] Embodiment 21: The method of any one of Embodiments 16 to 20, further comprising identifying a QCL assumption to be applied to the transmission of a downlink random access message in response to an uplink random access message, wherein the QCL assumption is related to 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] Embodiment 22: The method according to Embodiment 21, wherein identifying a QCL assumption comprises selecting both a first TCI state and a second TCI state as the basis for a QCL assumption according to one or more rules, wherein one or more rules specify that the downlink random access message to which the QCL assumption applies is a downlink control channel message scheduling 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 linked for downlink control channel iterations.

[0269]

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

[0270]

[0282] Embodiment 24: A method for wireless communication in a UE, comprising: receiving a downlink control channel command requesting the UE to participate in a random access procedure; and executing a random access procedure based on the fact that the downlink control channel command is received in accordance with one or more rules relating to the reception of the downlink control channel command via a plurality of downlink control channel candidates linked for downlink control channel iterations.

[0271]

[0283] Embodiment 25: The method of Embodiment 24, wherein receiving a downlink control channel command according to one or more rules is further comprising receiving a downlink control channel command via a downlink control channel candidate that is not linked with other downlink control channel candidates for iteration.

[0272]

[0284] Embodiment 26: The method of Embodiment 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 downlink control channel iteration, wherein the first downlink control channel candidate corresponds to a first search space set associated with CORESET, and the second downlink control channel candidate corresponds to a second search space set associated with CORESET.

[0273]

[0285] Embodiment 27: The method of Embodiment 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 downlink control channel iteration, wherein the first downlink control channel candidate corresponds to a first search space set associated with a first CORESET having TCI states, and the second downlink control channel candidate corresponds to a second search space set associated with a second CORESET having TCI states.

[0274]

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

[0275]

[0287] Aspect 29: A method for wireless communication in a base station, comprising: transmitting a downlink control channel command to a UE to request the UE to participate in a random access procedure; and receiving a random access message from the UE based on the downlink control channel command transmitted according to one or more rules, wherein the downlink control channel command is transmitted according to 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 repetitions.

[0276]

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

[0277]

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

[0278]

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

[0279]

[0291] Aspect 33: An apparatus for wireless communication in a UE, comprising a processor, a memory coupled to the processor, and instructions executable by the processor and stored in the memory to cause the apparatus to perform the method according to 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 according to 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 the method according to 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 executable by the processor and stored in the memory to cause the apparatus to perform the method according to 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 according to any of aspects 16 to 23.

[0284]

[0296] Embodiment 38: A non-temporary computer-readable medium for storing a code for wireless communication at a base station, wherein the code comprises instructions that can be executed by a processor to perform the method described in any of Embodiments 16 to 23.

[0285]

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

[0286]

[0298] Embodiment 40: An apparatus for wireless communication in a UE, comprising at least one means for carrying out any of the methods of Embodiments 24 to 28.

[0287]

[0299] Embodiment 41: A non-temporary computer-readable medium for storing code for wireless communication in a UE, wherein the code comprises instructions that can be executed by a processor to perform the method described in any of Embodiments 24 to 28.

[0288]

[0300] Embodiment 42: An apparatus for wireless communication at 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 any of the methods described in Embodiments 29 to 32.

[0289]

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

[0290]

[0302] Embodiment 44: A non-temporary computer-readable medium for storing a code for wireless communication at a base station, wherein the code comprises instructions that can be executed by a processor to perform the method described in any of Embodiments 29 to 32.

[0291]

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

[0292]

[0304] Embodiments of LTE, LTE-A, LTE-A Pro, or NR systems may be described as examples, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used for the majority of the description, however the techniques described herein are applicable to networks 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), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX®), IEEE 802.20, Flash-OFDM, as well as other systems and wireless technologies not expressly mentioned herein.

[0293]

[0305] The information and signals described herein may be represented using any of the following different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips which may be mentioned throughout this description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0294]

[0306] The various exemplary blocks and components described in relation to the disclosure herein may be implemented or run using general-purpose processors, DSPs, ASICs, CPUs, FPGAs or other programmable logic devices, individual gate or transistor logic, individual hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but alternatively, a 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 working 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 computer-readable media as one or more instructions or codes. Other examples and implementations fall within the scope of this disclosure and the accompanying claims. For example, depending on the nature of the software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or a combination thereof. Features implementing the functions may also be physically located in various locations, including the distribution of parts of the function so that they are implemented in different physical locations.

[0296]

[0308] Computer-readable media include both non-temporary computer storage media and communication media, including any media that facilitates the transfer of computer programs from one location to another. Non-temporary storage media can be any available media that can be accessed by a general-purpose or dedicated computer. Examples, but not limited to, non-temporary 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-temporary media that can be used to carry or store desired program code means in the form of instructions or data structures, and can be accessed by a general-purpose or dedicated computer or general-purpose or dedicated processor. Any connection is also appropriately referred to as computer-readable media. For example, if 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, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable media. As used herein, disk and disc include CD, LaserDisc®, OpticalDisc, Digital Multipurpose Disc (DVD), FloppyDisc®, and Blu-ray®, where disk typically reproduces data magnetically and disc optically reproduces data by laser. Combinations of the above are also included in the scope of computer-readable media.

[0297]

[0309] Throughout this specification, including within the claims, the term "or" as used in a list of items (e.g., a list of items that ends with phrases such as "at least one of" or "one or more of") indicates a non-exclusive listing, such that for example a listing 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 throughout this specification is not to be construed as referring to a closed set of conditions. For example, an exemplary step described as "based on condition A" may, without departing from the scope of this disclosure, be based on both condition A and condition B. In other words, the phrase "based on" as used throughout this specification is to be construed in the same manner as the phrase "at least partially based on".

[0298]

[0310] The term "determine" or "determining" encompasses a wide variety of actions, and thus "determining" can include calculating, computing, processing, deriving, investigating, looking up (e.g., via looking up in a table, database, or other data structure), ascertaining, etc. Also, "determining" can include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), etc. Further, "determining" can include resolving, selecting, choosing, establishing, and other such similar activities.

[0299]

[0311] In the accompanying drawings, like components or features may have the same reference label. Additionally, various components of the same type may be distinguished by following the reference label with a dash and a second label that differentiates between like components. If only the first reference label is used in this specification, the description applies to any of the like components having the same first reference label, regardless of the second reference label or any subsequent reference labels.

[0300]

[0312] The descriptions provided herein with respect to the accompanying drawings describe exemplary configurations and do not necessarily represent all examples that may be implemented or that fall within the scope of the claims. The term “example” as used herein means “to serve as an example, case, or illustration,” and does not imply “preferred” or “advantageous over other examples.” Detailed descriptions include specific details to provide an understanding of the techniques described. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the examples described.

[0301]

[0313] The descriptions herein are provided to enable those skilled in the art to create or use this disclosure. Various modifications of this disclosure will be obvious to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Accordingly, this disclosure is not limited to the examples and designs described herein, but should be given the broadest scope that conforms to the principles and novel features disclosed herein. The invention described in the original claims of this application is listed below. [1] A device for wireless communication in user equipment (UE), Processor and The memory coupled to the aforementioned processor, Instructions stored in the aforementioned memory and The device is equipped with the command, Receiving an indication that the first downlink control channel candidate and the second downlink control channel candidate are linked for downlink control channel iteration, 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, Execute the random access procedure associated with the downlink control channel command in accordance with one or more rules relating to the reception of the downlink control channel command via the linked downlink control channel candidate. A device that is executable by the processor in order to perform the following. [2] The aforementioned instruction is: In response to the downlink control channel command, determine a random access occasion for sending an uplink random access message, Sending the uplink random access message during the random access occasion, at least partially based on a first symbol of the random access occasion that lies after a threshold delay period triggered by a reference downlink control channel candidate among the linked downlink control channel candidates, and The apparatus according to [1], which is further executable by the processor to perform the random access procedure by being executable by the processor in order to do so. [3] The apparatus according to [2], wherein the reference downlink control channel candidate is the 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, wherein one or more rules indicate that the threshold delay period begins after the last symbol of the second downlink control channel candidate. [4] The apparatus according to [2], wherein executing the random access procedure in accordance with one or more of the rules is independent of whether the downlink control channel command is received between the first downlink control channel candidates or between the second downlink control channel candidates. [5] The apparatus according to [2], wherein the threshold delay period comprises a first time period for uplink shared channel preparation, a second time period for random access preparation, a third time period for bandwidth partial switching, a fourth time period for uplink switching, or a combination thereof, according to the capabilities of the UE. [6] The aforementioned instruction is: The timing of the random access occasion is determined based at least partially on the display in the downlink control channel command or on the measured synchronization signal block. The apparatus according to [2], which is further executable by the processor to determine the random access occasions by being executable by the processor. [7] The aforementioned instruction is: 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 transmit configuration indicator state, and the second downlink control channel candidate is associated with a second transmit configuration indicator state different from the first transmit configuration indicator state. Identifying a pseudo-collocation assumption to be applied to the reception of a downlink random access message in response to the uplink random access message, according to one or more of the aforementioned rules, and that the pseudo-collocation assumption is associated with at least one of the first transmit configuration indicator state or the second transmit configuration indicator state. The apparatus according to [1], which is further executable by the processor to perform the random access procedure by being executable by the processor in order to do so. [8] The aforementioned instruction is, Selecting one of the first transmit configuration indicator state or the second transmit configuration indicator state as the basis for the pseudo-collocation assumption in accordance with one or more of the rules, wherein the one or more rules specify that the selection of either the first transmit configuration indicator state or the second transmit configuration indicator state is at least partially based on the relative timing between the first downlink control channel candidate and the second downlink control channel candidate. The apparatus according to [7], which is further executable by the processor to identify the pseudo-collocation assumption by being executable by the processor to perform the following. [9] The aforementioned instruction is: Selecting one of the first transmit configuration indicator state or the second transmit configuration indicator state as the basis for the pseudo-collocation assumption in accordance with one or more of the rules, wherein the one or more rules specify that the selection of either the first transmit configuration indicator state or the second transmit configuration indicator state is at least partially based on the relative value between 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. The apparatus according to [7], which is further executable by the processor to identify the pseudo-collocation assumption by being executable by the processor to perform the following.

[10] The instruction is, Selecting one of the first transmit configuration indicator state or the second transmit configuration indicator state as the basis for the pseudo-collocation assumption in accordance with one or more of the rules, wherein the one or more rules specify that the selection of either the first transmit configuration indicator state or the second transmit configuration indicator state is at least partially based on the relative value between a first control resource set identifier associated with a first search space set corresponding to a first downlink control channel candidate and a second control resource set identifier associated with a second search space set corresponding to a second downlink control channel candidate. The apparatus according to [7], which is further executable by the processor to identify the pseudo-collocation assumption by being executable by the processor to perform the following.

[11] The aforementioned instruction is: Selecting one of the first transmit configuration indicator state or the second transmit configuration indicator state as the basis for the pseudo-collocation assumption in accordance with one or more of the rules, wherein the one or more rules specify that the selection of either the first transmit configuration indicator state or the second transmit configuration indicator state is at least partially based on the relative value between a first transmit configuration indicator state identifier associated with the first transmit configuration indicator state and a second transmit configuration indicator state identifier associated with the second transmit configuration indicator state. The apparatus according to [7], which is further executable by the processor to identify the pseudo-collocation assumption by being executable by the processor to perform the following.

[12] The aforementioned instruction is: Selecting both the first transmit configuration indicator state and the second transmit configuration indicator state as the basis for the pseudo-collocation assumption according to one or more of the rules, wherein the one or more rules specify that the downlink random access message to which the pseudo-collocation assumption applies is a downlink control channel message scheduling 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 linked for downlink control channel iterations. The apparatus according to [7], which is further executable by the processor to identify the pseudo-collocation assumption by being executable by the processor to perform the following.

[13] The aforementioned instruction is, Selecting both the first transmit configuration indicator state and the second transmit configuration indicator state as the basis for the pseudo-collocation assumption according to one or more of the rules, wherein the one or more rules specify that the downlink random access message to which the pseudo-collocation assumption applies is a random access response message that is a multi-transmit configuration indicator state downlink shared channel that changes in at least one of spatial division multiplexing, frequency division multiplexing, time division multiplexing, or single-frequency network schemes. The apparatus according to [7], which is further executable by the processor to identify the pseudo-collocation assumption by being executable by the processor to perform the following.

[14] The apparatus according to [7], wherein the downlink control channel command requests a non-conflicting random access procedure on the primary cell or the primary-secondary cell or both.

[15] The apparatus according to [7], wherein the downlink random access message is either a downlink control channel message scheduling a random access response message, or the random access response message itself.

[16] A device for wireless communications at a base station, Processor and The memory coupled to the aforementioned processor, Instructions stored in the aforementioned memory and The device is equipped with the command, To send a message to the user equipment (UE) indicating that the first downlink control channel candidate and the second downlink control channel candidate are linked for downlink control channel iteration, Sending a downlink control channel command to the UE 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, A device that can be operated by the processor to cause the UE to receive uplink random access messages related to the downlink control channel command in accordance with one or more rules relating to the transmission of the downlink control channel command via a linked downlink control channel candidate.

[17] The aforementioned instruction is, The uplink random access message is received during the random access occasion, at least in part, based on a first symbol of the random access occasion that lies after a threshold delay period triggered by a reference downlink control channel candidate among the linked downlink control channel candidates. The apparatus according to

[16] , which is further executable by the processor to receive the uplink random access message by being executable by the processor.

[18] The apparatus according to

[17] , wherein the reference downlink control channel candidate is the 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, wherein one or more rules indicate that the threshold delay period begins after the last symbol of the second downlink control channel candidate.

[19] The apparatus according to

[17] , wherein receiving the uplink random access message in accordance with one or more of the rules is independent of whether the downlink control channel command is transmitted between the first downlink control channel candidates or between the second downlink control channel candidates.

[20] The instruction is given to the device, Transmitting an indication of the timing of the random access occasion to the UE via the downlink control channel command or synchronization signal block. The apparatus according to

[17] , which is further executable by the processor to perform the following.

[21] The instruction is given to the device, Identifying a pseudo-collocation assumption to be applied to the transmission of a downlink random access message in response to the uplink random access message, according to one or more of the aforementioned rules, wherein the pseudo-collocation assumption is related to at least one of a first transmit configuration indicator state associated with a first downlink control channel candidate or a second transmit configuration indicator state associated with a second downlink control channel candidate, wherein the first transmit configuration indicator state is different from the second transmit configuration indicator state. The apparatus according to

[16] , which is further executable by the processor to perform the following.

[22] The aforementioned instruction is, Selecting both the first transmit configuration indicator state and the second transmit configuration indicator state as the basis for the pseudo-collocation assumption according to one or more of the rules, wherein the one or more rules specify that the downlink random access message to which the pseudo-collocation assumption applies is a downlink control channel message scheduling 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 linked for downlink control channel iterations. The apparatus according to

[21] , which is further executable by the processor to identify the pseudo-collocation assumption by being executable by the processor to perform the following.

[23] The aforementioned instruction is, Selecting both the first transmit configuration indicator state and the second transmit configuration indicator state as the basis for the pseudo-collocation assumption according to one or more of the rules, wherein the one or more rules specify that the downlink random access message to which the pseudo-collocation assumption applies is a random access response message that is a multi-transmit configuration indicator state downlink shared channel that changes in at least one of spatial division multiplexing, frequency division multiplexing, time division multiplexing, or single-frequency network schemes. The apparatus according to

[21] , which is further executable by the processor to identify the pseudo-collocation assumption by being executable by the processor to perform the following.

[24] A method for wireless communication in user equipment (UE), Receiving an indication that the first downlink control channel candidate and the second downlink control channel candidate are linked for downlink control channel iteration, 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, Execute the random access procedure associated with the downlink control channel command in accordance with one or more rules relating to the reception of the downlink control channel command via the linked downlink control channel candidate. A method that includes [a certain feature].

[25] Executing the aforementioned random access procedure is In response to the downlink control channel command, determine a random access occasion for sending an uplink random access message, Sending the uplink random access message during the random access occasion, at least partially based on a first symbol of the random access occasion that lies after a threshold delay period triggered by a reference downlink control channel candidate among the linked downlink control channel candidates, and The method described in

[24] further provides the following:

[26] The method according to

[25] , wherein the reference downlink control channel candidate is the 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, wherein one or more rules indicate that the threshold delay period begins after the last symbol of the second downlink control channel candidate.

[27] The method of

[25] , wherein executing the random access procedure according to one or more rules is independent of whether the downlink control channel command is received between the first downlink control channel candidates or between the second downlink control channel candidates.

[28] The method according to

[25] , wherein the threshold delay period comprises a first time period for uplink shared channel preparation according to the capabilities of the UE, a second time period for random access preparation, a third time period for bandwidth partial switching, a fourth time period for uplink switching, or a combination thereof.

[29] A method for wireless communication at a base station, To send a message to the user equipment (UE) indicating that the first downlink control channel candidate and the second downlink control channel candidate are linked for downlink control channel iteration, Sending a downlink control channel command to the UE 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, A method comprising receiving an uplink random access message associated with the downlink control channel command from the UE, in accordance with one or more rules relating to the transmission of the downlink control channel command via a linked downlink control channel candidate.

[30] Receiving the uplink random access message means that Receiving the uplink random access message during the random access occasion, at least in part, based on a first symbol of the random access occasion that lies after a threshold delay period triggered by a reference downlink control channel candidate among the linked downlink control channel candidates. The method described in

[29] further provides the following:

Claims

1. A device for wireless communication in user equipment (UE), One or more processors, A memory coupled to one or more processors, Instructions stored in the aforementioned memory and The device is equipped with the command, Receiving an indication that the first downlink control channel candidate and the second downlink control channel candidate are linked for downlink control channel iteration, As the first downlink control channel candidate and the second downlink control channel candidate are linked for the iteration of the downlink control channel, the UE receives a downlink control channel command through 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. Executing the random access procedure associated with the downlink control channel command in accordance with one or more rules relating to the reception of the downlink control channel command via the linked downlink control channel candidate, It is possible to perform the following by one or more processors: In order to execute the random access procedure, one or more processors in the apparatus In response to the downlink control channel command, it is configured to cause an uplink physical random access channel message to be transmitted during the random access occasion, at least in part, based on a first symbol of the random access occasion that lies after a threshold delay period triggered by a reference downlink control channel candidate among the linked downlink control channel candidates. The reference downlink control channel candidate is the second downlink control channel candidate as a result of the second downlink control channel candidate terminating later in time than the first downlink control channel candidate, wherein one or more rules indicate that the threshold delay period begins after the last symbol of the second downlink control channel candidate. Device.

2. The apparatus according to claim 1, wherein the downlink control channel command is received between the first downlink control channel candidates or between the second downlink control channel candidates.

3. The apparatus according to claim 1, wherein the threshold delay period comprises a first time period for preparing the uplink shared channel according to the capabilities of the UE, a second time period for preparing random access, a third time period for partial bandwidth switching, a fourth time period for uplink switching, or a combination thereof.

4. The instruction instructs the device to determine the random access occasion, The apparatus according to claim 1, further comprising one or more processors capable of determining the timing of the random access occasions based at least partially on the indication in the downlink control channel command or on a measured synchronous signal block.

5. The instruction instructs the device to determine the random access occasion, 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 transmit configuration indicator state, and the second downlink control channel candidate is associated with a second transmit configuration indicator state different from the first transmit configuration indicator state. Identifying a pseudo-collocation assumption to be applied to the reception of a downlink random access message in response to the uplink random access message, according to one or more of the aforementioned rules, and that the pseudo-collocation assumption is associated with at least one of the first transmit configuration indicator state or the second transmit configuration indicator state. The apparatus according to claim 1, further executable by one or more processors to perform the following.

6. In order to identify the pseudo-collocation assumption, the instruction shall be given to the device, Selecting one of the first transmit configuration indicator state or the second transmit configuration indicator state as the basis for the pseudo-collocation assumption in accordance with one or more of the rules, wherein the one or more rules specify that the selection of either the first transmit configuration indicator state or the second transmit configuration indicator state is at least partially based on the relative timing of the first downlink control channel candidate and the second downlink control channel candidate. The apparatus according to claim 5, further executable by one or more processors to perform the following.

7. The instruction instructs the device to identify the pseudo-collocation assumption, Selecting one of the first transmit configuration indicator state or the second transmit configuration indicator state as the basis for the pseudo-collocation assumption in accordance with one or more of the rules, wherein the one or more rules specify that the selection of either the first transmit configuration indicator state or the second transmit configuration indicator state is at least partially based on the relative value between 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. The apparatus according to claim 5, further executable by one or more processors to perform the following.

8. In order to identify the pseudo-collocation assumption, the instruction shall be given to the device, Selecting one of the first transmit configuration indicator state or the second transmit configuration indicator state as the basis for the pseudo-collocation assumption in accordance with one or more of the rules, wherein the one or more rules specify that the selection of either the first transmit configuration indicator state or the second transmit configuration indicator state is at least partially based on the relative value between a first control resource set identifier associated with a first search space set corresponding to a first downlink control channel candidate and a second control resource set identifier associated with a second search space set corresponding to a second downlink control channel candidate. The apparatus according to claim 5, further executable by one or more processors to perform the following.

9. In order to identify the pseudo-collocation assumption, the instruction shall be given to the device, Selecting one of the first transmit configuration indicator state or the second transmit configuration indicator state as the basis for the pseudo-collocation assumption in accordance with one or more of the rules, wherein the one or more rules specify that the selection of either the first transmit configuration indicator state or the second transmit configuration indicator state is at least partially based on the relative value between a first transmit configuration indicator state identifier associated with the first transmit configuration indicator state and a second transmit configuration indicator state identifier associated with the second transmit configuration indicator state. The apparatus according to claim 5, further executable by one or more processors to perform the following.

10. In order to identify the pseudo-collocation assumption, the instruction shall be given to the device, Selecting both the first transmit configuration indicator state and the second transmit configuration indicator state as the basis for the pseudo-collocation assumption according to one or more of the rules, wherein the one or more rules specify that the downlink random access message to which the pseudo-collocation assumption applies is a downlink control channel message scheduling 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 linked for downlink control channel iterations. The apparatus according to claim 5, further executable by one or more processors to perform the following.

11. In order to identify the pseudo-collocation assumption, the instruction shall be given to the device, Selecting both the first transmit configuration indicator state and the second transmit configuration indicator state as the basis for the pseudo-collocation assumption according to one or more of the rules, wherein the one or more rules specify that the downlink random access message to which the pseudo-collocation assumption applies is a random access response message that is a multi-transmit configuration indicator state downlink shared channel that changes in at least one of spatial division multiplexing, frequency division multiplexing, time division multiplexing, or single-frequency network schemes. The apparatus according to claim 5, further executable by one or more processors to perform the following.

12. A device for wireless communication at a base station, One or more processors, A memory coupled to one or more processors, Instructions stored in the aforementioned memory and The device is equipped with the command, To send a message to the user equipment (UE) indicating that the first downlink control channel candidate and the second downlink control channel candidate are linked for downlink control channel repetition, As the first downlink control channel candidate and the second downlink control channel candidate are linked for the iteration of the downlink control channel, a downlink control channel command is sent 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 UE receives an uplink physical random access channel message related to the downlink control channel command, in accordance with one or more rules relating to the transmission of the downlink control channel command via the linked downlink control channel candidate. It is possible to perform the following by one or more processors: In order to receive the uplink physical random access channel message, the instruction instructs the device to: The one or more processors can further cause the uplink physical random access channel messages to be received during the random access occasion, at least partially based on a first symbol of the random access occasion that lies after a threshold delay period triggered by a reference downlink control channel candidate among the linked downlink control channel candidates, The reference downlink control channel candidate is the second downlink control channel candidate as a result of the second downlink control channel candidate terminating later in time than the first downlink control channel candidate, wherein one or more rules indicate that the threshold delay period begins after the last symbol of the second downlink control channel candidate. Device.

13. A method for wireless communication in user equipment (UE), Receiving an indication that the first downlink control channel candidate and the second downlink control channel candidate are linked for downlink control channel iteration, As the first downlink control channel candidate and the second downlink control channel candidate are linked for the iteration of the downlink control channel, the UE receives a downlink control channel command through 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. Executing the random access procedure associated with the downlink control channel command in accordance with one or more rules relating to the reception of the downlink control channel command via the linked downlink control channel candidate, The system includes the ability to execute the random access procedure, The system includes transmitting an uplink physical random access channel message during a random access occasion, at least partially based on a first symbol of the random access occasion that lies after a threshold delay period triggered by a reference downlink control channel candidate among the linked downlink control channel candidates, in response to the downlink control channel command. The reference downlink control channel candidate is the second downlink control channel candidate as a result of the second downlink control channel candidate terminating later in time than the first downlink control channel candidate, wherein one or more rules indicate that the threshold delay period begins after the last symbol of the second downlink control channel candidate. method.

14. A method for wireless communication at a base station, To send a message to the user equipment (UE) indicating that the first downlink control channel candidate and the second downlink control channel candidate are linked for downlink control channel repetition, As the first downlink control channel candidate and the second downlink control channel candidate are linked for the iteration of the downlink control channel, a downlink control channel command is sent 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 UE receives an uplink physical random access channel message related to the downlink control channel command, in accordance with one or more rules relating to the transmission of the downlink control channel command via the linked downlink control channel candidate. The system is equipped with the ability to receive the uplink physical random access channel message, The system includes receiving the uplink physical random access channel message during the random access occasion, at least partially based on a first symbol of the random access occasion that lies after a threshold delay period triggered by a reference downlink control channel candidate among the linked downlink control channel candidates, The reference downlink control channel candidate is the second downlink control channel candidate as a result of the second downlink control channel candidate terminating later in time than the first downlink control channel candidate, wherein one or more rules indicate that the threshold delay period begins after the last symbol of the second downlink control channel candidate. method.

Images