Methods for using default path loss reference signal and beam

Abstract

This disclosure provides systems, apparatus, devices, and methods for determining a default beam or default path loss reference signal (PL-RS), including a computer program encoded on a storage medium. A UE (102) receives (304) control signaling from a network entity (104) configuring at least one RA procedure from a plurality of random access (RA) procedures and configuring a list of transmission configuration indicator (TCI) states. Prior to activation of at least one TCI state from the list of TCI states or a UE-initiated beam, the UE communicates (306) with the network entity (104) using at least one of a default beam or a default path loss reference signal (PL-RS) based on at least one of: quasi-co-address (QCL) parameters for a first downlink reference signal, or an uplink spatial transmission filter associated with at least one RA procedure and a path loss associated with a second downlink reference signal.

Description

Technical Field

[0001] This disclosure generally relates to wireless communication, and more specifically, to a default beam and default path loss reference signal (PL-RS). Background Technology

[0002] The 3rd Generation Partnership Project (3GPP) specifies a radio interface known as Fifth Generation (5G) New Radio (NR) (5G NR). The architecture of a 5G NR wireless communication system includes a 5G core (5GC) network, a 5G radio access network (5G-RAN), and user equipment (5G UE). Compared to previous generations of cellular communication systems, the 5G NR architecture aims to provide increased data rates, reduced latency, and / or increased capacity.

[0003] Generally, wireless communication systems provide various telecommunications services (e.g., telephony, video, data, messaging, etc.) based on multiple access technologies (such as Orthogonal Frequency Division Multiple Access (OFDMA)) that support communication with multiple UEs. Improvements in mobile broadband have perpetuated this development of wireless communication technologies. For example, the Unified Transport Configuration Indicator (TCI) scheme is designed to simplify beam management for multi-beam operations. The unified TCI scheme can lead to multiple scenarios that require highly efficient beam management processes to handle. Summary of the Invention

[0004] The following is a simplified overview of one or more aspects to provide a basic understanding of such aspects. This overview is not a comprehensive summary of all anticipated aspects. It neither identifies key or important elements of all aspects nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as an introduction to the more detailed descriptions that follow.

[0005] Next-generation communication systems (e.g., fifth-generation (5G) and sixth-generation (6G) wireless technologies) utilize beam management techniques to enhance throughput and meet the demands of wireless users. Beam management is becoming increasingly complex due to the adoption of higher frequency bands, user mobility, and increased antenna counts. Specifically, in frequency range 2 (FR 2) based communications, the overhead associated with beam management operations and new beam reporting can increase, potentially leading to reduced communication reliability. To overcome this reliability issue, the Unified Transport Configuration Indicator (TCI) scheme is designed to simplify beam management for multi-beam operations. The unified TCI scheme enables network entities to transmit at least one joint TCI state or a unified TCI state to user equipment (UE). Network entities configure the joint or uplink unified TCI state during initial radio control resource (RRC) configuration or RRC reconfiguration.

[0006] However, the unified TCI scheme can lead to multiple scenarios that require highly efficient beam management procedures to handle. For example, in one scenario, the unified TCI scheme needs to consider a two-step random access procedure, where the UE transmits message A (MsgA) including the Physical Random Access Channel (PRACH) and the Physical Uplink Shared Channel (PUSCH), and receives a Random Access Response (RAR) from the network entity, without transmitting message 3 (Msg3).

[0007] This disclosure addresses the aforementioned and other deficiencies by implementing a default beam and path loss reference signal (PL-RS) technique for handling multiple scenarios. In one example, the UE receives a configuration for configuring a random access (RA) procedure from a network entity. This configuration also configures the TCI state. Therefore, the UE communicates with the network entity based on a default beam or a default PL-RS determined based on quasi-co-location (QCL) parameters of a first downlink reference signal, or an uplink spatial transmission filter associated with at least one RA procedure and a path loss associated with a second downlink reference signal.

[0008] In this way, network entities do not need to transmit beam indication signaling. Network entities and UEs can communicate based on the default beam and PL-RS, which reduces the overhead of beam indication signaling operations. In addition, network entities and UEs can communicate without the possibility of beam mismatch, which can improve downlink and uplink channel performance before the UE applies the indicated TCI state.

[0009] According to some aspects, the UE receives control signaling from a network entity configuring at least one RA procedure from a plurality of RA procedures and configuring a list of TCI states. Before the activation of at least one TCI state from the list of TCI states or the UE-initiated beam, the UE communicates with the network entity using at least one of a default beam or a default PL-RS, which is based on at least one of: QCL parameters for a first downlink reference signal, or an uplink spatial transmission filter associated with at least one RA procedure and a path loss associated with a second downlink reference signal.

[0010] According to some aspects, the network entity transmits control signaling to the UE to configure at least one RA procedure from a plurality of RA procedures and to configure a list of TCI states. Prior to the activation of at least one TCI state from the list of TCI states or a UE-initiated beam, the network entity communicates with the UE using at least one of a default beam or a default PL-RS, which is based on at least one of: QCL parameters for a first downlink reference signal, or an uplink spatial transmission filter associated with at least one RA procedure and a path loss associated with a second downlink reference signal. Attached Figure Description

[0011] Figure 1 An illustration of a wireless communication system according to an embodiment is shown, the wireless communication system including a plurality of user equipments (UEs) and network entities communicating through one or more cells.

[0012] Figure 2 This is an example of uplink (UL) and downlink (DL) beam determination prior to the Transport Configuration Indication (TCI) state indicated by the network entity and the UE application, according to an embodiment.

[0013] Figure 3 This is a signaling diagram illustrating the communication between a UE and a network entity according to an embodiment regarding the process of using the default beam and path loss reference signal (PL-RS) for DL ​​and UL channels.

[0014] Figure 4 This is an example of default beam determination based on the Synchronization Signal Block / Channel State Information-Reference Signal (SSB / CSI-RS) resource index, according to an embodiment.

[0015] Figure 5 This is an example of default beam determination based on the time-domain location of SSB / CSI-RS according to an embodiment.

[0016] Figure 6 This is an example of default beam determination based on network entity-based configuration according to an embodiment.

[0017] Figure 7 This is an example of default beam determination based on UE reports according to an embodiment.

[0018] Figure 8 This is an example of default beam determination based on the time-domain location of the Physical Uplink Shared Channel (PUSCH) of message A (MsgA) or message 3 (Msg3) according to an embodiment.

[0019] Figure 9 This is an example of default beam determination based on network entity-based configuration according to an embodiment.

[0020] Figure 10 This is an example of default beam determination based on UE reports according to an embodiment.

[0021] Figure 11 This is a flowchart of a wireless communication method at the UE according to an embodiment.

[0022] Figure 12 This is a flowchart of a method for wireless communication at a network entity according to an embodiment.

[0023] Figure 13 This is a diagram illustrating a hardware implementation of an example UE device according to some embodiments.

[0024] Figure 14 This is a diagram illustrating a hardware implementation of one or more example network entities according to some embodiments. Detailed Implementation

[0025] Figure 1 A diagram 100 illustrates a wireless communication system associated with multiple cells 190. The wireless communication system includes user equipment (UE) 102 and base station / network entity 104. Some base stations may include an aggregated base station architecture, while others may include a decomposed base station architecture. The aggregated base station architecture utilizes a radio protocol stack physically or logically integrated within a single radio access network (RAN) node. The decomposed base station architecture utilizes a protocol stack physically or logically distributed across two or more units (e.g., radio unit (RU) 106, distributed unit (DU) 108, central unit (CU) 110). For example, CU 110 is implemented within a RAN node, and one or more DU 108s may be located in the same location as CU 110, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DU 108 may be implemented to communicate with one or more RU 106s. Any of RU 106, DU 108, and CU 110 can be implemented as a virtual unit, such as a virtual radio unit (VRU), a virtual distributed unit (VDU), or a virtual central unit (VCU). Base station / network entity 104 (e.g., an aggregated base station or a decomposed unit of a base station, such as RU 106 or DU 108) can be referred to as a transmit receiver point (TRP).

[0026] The operation and / or network design of base station 104 can be based on the aggregation characteristics of base station functionality. For example, a decomposed base station architecture can be utilized in an Integrated Access Backhaul (IAB) network, an Open Radio Access Network (O-RAN) network, or a Virtual Radio Access Network (vRAN) (which may also be referred to as a Cloud Radio Access Network (C-RAN)). Decomposition can include distributing functionality among two or more units located in various physical locations, as well as virtually distributing the functionality of at least one unit, which enables flexibility in network design. Various units of the decomposed base station architecture or decomposed RAN architecture can be configured to communicate with at least one other unit via wired or wireless communication. For example, base stations 104d, 104e and / or RUs 106a, 106b, 106c, 106d can communicate with UEs 102a, 102b, 102c, 102d and / or 102s via one or more radio frequency (RF) access links based on a Uu interface. In the example, multiple RUs 106 and / or base stations 104 can simultaneously serve UE 102, such as through intra-cell and / or inter-cell access links between UE 102 and RUs 106 / base stations 104.

[0027] RU 106, DU 108, and CU 110 may include (or may be coupled to) one or more interfaces configured to transmit or receive information / signals via wired or wireless transmission media. For example, a wired interface may be configured to transmit or receive information / signals via a wired transmission medium—such as a fronthaul link 160 between RU 106d and a baseband unit (BBU) 112 of base station 104d associated with cell 190d. BBU 112 includes DU 108 and CU 110, and may also have a wired interface (e.g., a midhaul link) configured between DU 108 and CU 110 for transmitting or receiving information / signals between DU 108 and CU 110. In a further example, a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) is configured to transmit and / or receive information / signals via a wireless transmission medium (such as information for transmission between RU 106a in cell 190a and base station 104e in cell 190e via inter-cell communication beams 136-138 of RU 106a and base station 104e).

[0028] RU 106 can be configured to implement low-level functionality. For example, RU 106 is controlled by DU 108 and can correspond to a logical node that manages RF processing functions or low-level PHY functionality, such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction, and filtering. The functionality of RU 106 can be based on functional partitioning, such as low-level functional partitioning.

[0029] RU 106 can transmit or receive over-the-air (OTA) communications with one or more UEs 102. For example, RU 106b of cell 190b communicates with UE 102b of cell 190b via a first communication beamset 132 of RU 106b and a second communication beamset 134b of UE 102b, which may correspond to inter-cell communication beamsets or, in some examples, inter-cell communication beamsets. For example, UE 102b of cell 190b can communicate with RU 106a of cell 190a via a third communication beamset 134a of UE 102b and a fourth communication beamset 136 of RU 106a. DU 108 can control the real-time and non-real-time characteristics of control plane and user plane communications of RU 106.

[0030] Any combination or individual reference to RU 106, DU 108, and CU 110 may correspond to base station 104. Therefore, base station 104 may include at least one of RU 106, DU 108, or CU 110. Base station 104 provides UE 102 with access to the core network. Base station 104 may relay communication between UE 102 and the core network (not shown). Base station 104 may be associated with macro cells of high-power cellular base stations and / or small cells of low-power cellular base stations. For example, cell 190e may correspond to a macro cell, while cells 190a-190d may correspond to small cells. Small cells include femtocells, picocells, microcells, etc. A network including at least one macro cell and at least one small cell may be referred to as a "heterogeneous network".

[0031] Transmissions from UE 102 to base station 104 / RU 106 are referred to as uplink (UL) transmissions, while transmissions from base station 104 / RU 106 to UE 102 are referred to as downlink (DL) transmissions. Uplink transmissions can also be referred to as reverse link transmissions, and downlink transmissions can also be referred to as forward link transmissions. For example, RU 106d utilizes the antenna of base station 104d in cell 190d to transmit downlink / forward link communication to UE 102d, or receive uplink / reverse link communication from UE 102d, based on the Uu interface associated with the access link between UE 102d and base station 104d / RU 106d.

[0032] The communication link between UE 102 and base station 104 / RU 106 can be based on multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link can be associated with one or more carriers. UE 102 and base station 104 / RU 106 can utilize up to a total of Yx Each carrier allocated in MHz carrier aggregation Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, 800 MHz, 1600 MHz, 2000 MHz, etc.) spectrum bandwidth, of which x Each component carrier (CC) is used for communication in each of the uplink and downlink directions. The carriers may be adjacent to each other along the spectrum, or they may not be adjacent to each other. In the example, uplink and downlink carriers may be allocated asymmetrically, with more or fewer carriers allocated to the uplink or downlink. A component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be associated with a primary cell (PCell), and the secondary component carrier may be associated with a secondary cell (SCell).

[0033] Some UEs 102 (such as UEs 102a and 102s) can perform device-to-device (D2D) communication via sidelinks. For example, sidelink communication / D2D links utilize the spectrum of the Wireless Wide Area Network (WWAN) associated with uplink and downlink communication. Such sidelink / D2D communication can be performed by various wireless communication systems such as Wi-Fi, Bluetooth, LTE, and NR.

[0034] UE 102 and base station 104 / RU 106 may each include multiple antennas. These multiple antennas may correspond to antenna elements, antenna panels, and / or antenna arrays that facilitate beamforming operation. For example, RU 106b transmits downlink beamforming signals to UE 102b based on a first communication beamset 132 in one or more transmission directions of RU 106b. UE 102b may receive downlink beamforming signals from RU 106b based on a second communication beamset 134b in one or more reception directions of UE 102b. In a further example, UE 102b may also transmit uplink beamforming signals (e.g., sounding reference signals (SRS)) to RU 106b based on the second communication beamset 134b in one or more transmission directions of UE 102b. RU 106b may receive uplink beamforming signals from UE 102b in one or more reception directions of RU 106b. UE 102b can perform beamforming to determine the optimal reception and transmission directions for beamformed signals. The transmission and reception directions of UE 102 and base station 104 / RU 106 can be the same or different.

[0035] In a further example, the beamformed signal can be transmitted between the first base station / RU 106a and the second base station 104e. For example, base station 104e of cell 190e can transmit the beamformed signal to RU 106a based on communication beam 138 in one or more transmission directions of base station 104e. RU 106a can receive the beamformed signal from base station 104e of cell 190e based on RU communication beam 136 in one or more reception directions of RU 106a. In a further example, base station 104e transmits a downlink beamformed signal to UE 102e based on communication beam 138 in one or more transmission directions of base station 104e. UE 102e receives the downlink beamformed signal from base station 104e based on UE communication beam 130 in one or more reception directions of UE 102e. UE 102e can also transmit uplink beamforming signals to base station 104e in one or more transmission directions of UE 102e based on UE communication beam 130, so that base station 104e can receive uplink beamforming signals from UE 102e in one or more receiving directions of base station 104e.

[0036] Base station 104 may include and / or be referred to as a network entity. That is, a "network entity" may refer to base station 104 or at least one element of base station 104, such as RU 106, DU 108, and / or CU 110. Base station 104 may also include and / or be referred to as Next Generation Evolved Node B (ng-eNB), Next Generation NB (gNB), Evolved NB (eNB), access point, base transceiver, radio base station, radio transceiver, transceiver function, Basic Service Set (BSS), Extended Service Set (ESS), TRP, network node, network device, or other related terms. Base station 104 or entities at base station 104 may be implemented as an IAB node, relay node, sidelink node, aggregated (monolithic) base station, or a decomposed base station including one or more RU 106, DU 108, and / or CU 110. An aggregated or decomposed set of base stations may be referred to as a Next Generation Radio Access Network (NG-RAN). In some examples, UE 102a operates in dual connectivity (DC) with base station 104e and base station / RU 106a. In such a case, base station 104e can be the primary node, and base station / RU 106a can be the secondary node.

[0037] Still referencing Figure 1 In some respects, any of the UEs 102 may include a UE default beam management component 140, which is configured to receive control signaling from a network entity configuring at least one RA procedure from a plurality of RA procedures and configuring a list of TCI states; prior to activation of at least one TCI state from the list of TCI states or a UE-initiated beam, communicating with the network entity using at least one of a default beam or a default PL-RS, which is based on at least one of: QCL parameters for a first downlink reference signal, or an uplink spatial transmission filter associated with at least one RA procedure and a path loss associated with a second downlink reference signal.

[0038] In some aspects, any of the base stations 104 or the network entity of the base station 104 may include an NE default beam management component 150, which is configured to transmit control signaling to the UE to configure at least one RA procedure from a plurality of RA procedures and configure a list of TCI states; prior to the activation of at least one TCI state from the list of TCI states or a beam initiated by the UE, the UE is communicated using at least one of a default beam or a default PL-RS, which is based on at least one of: QCL parameters for a first downlink reference signal, or an uplink spatial transmission filter associated with at least one RA procedure and a path loss associated with a second downlink reference signal.

[0039] therefore, Figure 1 A wireless communication system that can be implemented in conjunction with aspects of one or more other accompanying figures described herein is described. Furthermore, although the following description may focus on 5G NR, the concepts described herein are applicable to other similar fields, such as 5G-Advanced and future versions, LTE, LTE-advanced (LTE-A), and other wireless technologies such as 6G.

[0040] For a Multiple-Input Multiple-Output (MIMO) system, network entity 104 and UE 102 can maintain multiple beams, and a good beam pair between network entity 104 and UE 102 can provide a good link budget to improve coverage. Typically, network entity 104 can configure a list of Transmission Configuration Indication (TCI) states for each Bandwidth Part (BWP) via Radio Resource Control (RRC) signaling and transmit a Media Access Control (MAC) control element (CE) to activate at least one TCI state corresponding to at least one TCI code point in the Downlink Control Information (DCI). If network entity 104 activates the TCI state corresponding to the TCI code point, network entity 104 and UE can communicate based on the TCI state activated by the MAC CE after the MAC CE's activation time. Otherwise, network entity 104 can further transmit Downlink Control Information (DCI) indicating the TCI state corresponding to one of the TCI code points, and network entity 104 and UE 102 can communicate based on the TCI state indicated by the TCI code point in the DCI after the DCI's activation time.

[0041] Figure 2 Illustration 200 shows the process for determining the uplink (UL) and downlink (DL) beams prior to the TCI state indicated by the network entity and UE application.

[0042] refer to Figure 2 UE 102 selects a random access (RA) preamble from a predefined set of preambles. After selecting the preamble, UE 102 transmits the preamble on message 1 (Msg1): PRACH 224.

[0043] In response to receiving Msg1, network entity 104 transmits a RA response referred to as Msg2 226. Msg2 includes information such as a time advance (TA) command for timing adjustment, a random access radio network temporary identifier (RA-RNTI), and an initial uplink clearance for the UE.

[0044] UE 102 transmits Msg3 228 on the Physical Uplink Shared Channel (PUSCH). Msg3 may include RRC messages or only data.

[0045] Network entity 104 transmits RRC reconfiguration 230. RRC reconfiguration can indicate a list of Transmission Configuration Indication (TCI) statuses.

[0046] Network entity 104 transmits TCI indication 232 from one or more TCI states of the configured TCI state list.

[0047] Beam 236 is applied after the acknowledgment (ACK) feedback 234 of TCI indication 232. The 236 TCI status is applied based on the time of action following the ACK feedback associated with the DCI format conveying the TCI status.

[0048] UE 102 receives the Physical Downlink Control Channel (PDCCH) / Physical Downlink Shared Channel (PDSCH) and the Channel State Information Reference Signal (CSI-RS) of the application-indicated TCI state based on the beamforming SSB / CSI-RS associated with PRACH. UE 102 transmits the PUSCH / Physical Uplink Control Channel (PUCCH) and the SRS of the application-indicated TCI state based on the beamforming as indicated in Msg3.

[0049] When a unified TCI state is configured (after an initial RRC reconfiguration of at least one TCI state in the configured TCI list or an RRC reconfiguration with a synchronization procedure and before the TCI state indicated by the application on UE 102), UE 102 can use the beam (i.e., the uplink (UL) transmission (TX) spatial filter) scheduled by RAR for message 3 (Msg3) to transmit PUSCH, PUCCH, and SRS of the TCI state indicated by the application. UE 102 can receive the demodulation reference signal (DM-RS) of PDSCH, the DM-RS of PDCCH, and the CSI-RS of the TCI state indicated by the application during the RA procedure based on the quasi-co-location (QCL) parameters as a synchronization signal physical broadcast channel (SS / PBCH) block (SSB) or CSI-RS resource associated with PRACH. In one example, the corresponding specification is defined in Section 5.1.5 of 3GPP TS 38.214 as follows: When UE 102 receives a signal having at least one TCI-State of dl-OrJointTCI-StateListAfter the initial higher-layer configuration, and before applying the indicated TCI state from the configured TCI state, UE 102 assumes that the DM-RS of PDSCH and the DM-RS of PDCCH, as well as the CSI-RS of the applied indicated TCI state, are QCLs with the SS / PBCH block identified by UE 102 during the initial access procedure.

[0050] When UE 102 receives a signal having at least one TCI-State of dl-OrJointTCI-StateList or having at least one TCI-UL-State of ul-TCI-StateList After the initial higher-level configuration, and before applying the indicated TCI state from the configured TCI state, UE 102 assumes that the UL TX spatial filters (if applicable) used for PUSCH and PUCCH based on dynamic grant and configuration grant, and for SRS for applying the indicated TCI state, are the same as the UL TX spatial filters used for PUSCH transmissions scheduled by RAR UL grant during the initial access procedure.

[0051] When UE 102 receives a signal having at least one TCI-State of dl-OrJointTCI-StateList After a higher-level configuration (as part of a reconfiguration with a synchronization procedure as described in [3GPP TS 38.331]), and before applying the indicated TCI state from the configured TCI state, UE 102 assumes that the DM-RS of PDSCH and the DM-RS of PDCCH, as well as the CSI-RS with the indicated TCI state, are QCLs with the SS / PBCH block or CSI-RS resource identified by UE 102 during the RA procedure initiated by the reconfiguration with a synchronization procedure as described in [3GPP TS 38.331].

[0052] When UE 102 receives a signal having at least one TCI-State or at least TCI-UL-State of dl- OrJointTCI-StateList After a higher-level configuration (as part of a reconfiguration with a synchronization procedure as described in [3GPP TS 38.331]) and before applying the indicated TCI state from the configured TCI state, UE102 assumes that the UL TX spatial filters (if applicable) used for PUSCH and PUCCH based on dynamic granting and configuration granting, and for SRS for applying the indicated TCI state, are the same as those used for PUSCH transmissions scheduled by RAR UL granting during the RA procedure initiated by the reconfiguration with a synchronization procedure as described in [3GPP TS 38.331].

[0053] Additionally, if network entity 104 does not configure a path loss reference signal (PL-RS) in the RRC signaling, or before providing dedicated RRC parameters to UE 102, UE 102 calculates path loss based on the SSB used by UE 102 to decode the Master Information Block (MIB) in the PCell or the SSB used by UE 102 to obtain time and frequency synchronization for the SCell.

[0054] Furthermore, for uplink channels (e.g., PUCCH or SRS), if network entity 104 does not configure PL-RS and spatial relationship information (e.g., PUCCH-SpatialRelationInfo or SRS-SpatialRelationInfo If so, network entity 104 can configure UE 102 to determine the beam and PL-RS based on the periodic DL RS configured in the TCI state of the CORESET with the lowest control resource set (CORESET) identifier (ID) in the same serving cell as PUCCH or SRS. In one example, network entity 104 uses the RRC parameters used for PUCCH and SRS respectively. enableDefaultBeamPL-ForPUCCH and enableDefaultBeamPL-ForSRS To provide configuration.

[0055] When more than one joint or uplink unified TCI state is configured in an initial RRC reconfiguration or an RRC reconfiguration with a synchronization process, the determination of UE beam and PL-RS is not resolved for the following scenario after UE 102 receives the RRC reconfiguration and before UE 102 applies the indicated TCI state.

[0056] Scenario 1: The RA process is based on a 2-step RA, in which UE 102 transmits message A (MsgA) including PRACH and PUSCH and receives RAR from network entity 104, without transmitting Msg3.

[0057] Scenario 2: Default beam for SCell. SCell and PCell can be in different frequency bands, and for UE102, it is not possible to use the same beam and PL-RS for the SCell channel as for the PCell.

[0058] Scenario 3: In RRC reconfiguration, network entity 104 enables the default beam and PL-RS for some UL channels (e.g., PUSCH, PUCCH, and SRS) based on TCI / QCL for CORESET.

[0059] Scenario 4: Network entity 104 configures multiple transmit and receive point (mTRP) operations in RRC reconfiguration. For example, network entity 104 configures an mTRP transmission scheme for at least one DL or UL channel, such as spatial multiplexing (SDM), single-frequency network (SFN), frequency multiplexing (FDM), time multiplexing (TDM), or coherent joint transmission (CJT), or network entity 104 configures two CORESET pool indices (or network entity 104 configures CORESET pool index 1).

[0060] Scenario 5: The PRACH in the RA process can be associated with at least one SSB / CSI-RS resource.

[0061] Scenario 6: UE 102 can transmit Msg3 PUSCH based on at least one beam.

[0062] Scenario 7: In the RRC configuration, network entity 104 does not provide PL-RS and does not enable the default beam and PL-RS for some UL channels (e.g., PUSCH, PUCCH, and SRS).

[0063] Scenario 8: When UE-initiated beam switching is enabled, UE 102 may apply the UE-initiated beam or TCI state instead of the indicated TCI state. This occurs after UE 102 receives the initial RRC reconfiguration or an RRC reconfiguration with a synchronization procedure, and before UE 102 applies the UE-initiated beam or TCI state.

[0064] With the default beam and PL-RS technology determined to address the scenarios mentioned above, network entity 104 does not need to transmit beam indication signaling. Network entity 104 and UE 102 can communicate based on the default beam and PL-RS, which may reduce the overhead for beam indication signaling. Using this technology, network entity 104 and UE 102 can communicate without beam mismatch, which may also improve the performance of the DL and UL channels before UE 102 applies the indicated TCI state.

[0065] In summary, this technique proposes a method for determining the default beam and PL-RS for the aforementioned scenarios before applying the first indicated TCI state to UE 102 after initial access or after handover (with synchronized RRC reconfiguration). This method can also be extended to lower-layer triggered mobility (LTM) scenarios where the TCI is not indicated in the cell handover command (CSC), including: the default beam for DL ​​channel / RS reception; and the default beam and PL-RS for UL channel / RS transmission. It should be understood that the technique described herein can also be applied to other scenarios for determining the default beam and PL-RS for communication before UE 102 applies the first indicated TCI state.

[0066] Figure 3 Signaling diagram 300 illustrates communication between UE 102 and network entity 104 according to an embodiment regarding the default beam and PL-RS process for DL ​​and UL channels. Network entity 104 may correspond to a base station or a unit of a base station (such as RU 106, DU 108, CU 110, etc.).

[0067] The DL channel may include at least one of PDSCH, PDCCH, or CSI-RS. The UL channel may include at least one of PUSCH, PUCCH, or SRS. Note that the PUCCH in the PCell also indicates the PUCCH in the primary / secondary cell (PSCell) or the PUCCH-SCell (the SCell configured with PUCCH). The joint TCI indication is in... dl-OrJointTCI-StateList The TCI status configured in the configuration. The active TCI used for CORESET indicates the TCI indicated by MAC CE or DCI.

[0068] Network entity 104 and UE 102 perform random access (RA) procedure 302 based on a 2-step random access channel (RACH) procedure or a 4-step RACH procedure.

[0069] UE 102 can receive control signaling 304 (which network entity 104 can transmit) from network entity 104 for RRC reconfiguration corresponding to RA procedure 302. In some implementations, the control signaling can be RRC reconfiguration. In some other implementations, the control signaling can be the CSC that triggers cell handover by updating or reconfiguring RRC parameters.

[0070] Following control signaling for RRC reconfiguration and before network entity 104 and UE 102 apply the indicated TCI state or UE-initiated beam or TCI state, network entity 104 and UE 102 determine a default beam for at least one DL channel or a default beam and PL-RS for at least one UL channel. Network entity 104 and UE 102 may determine the default beam and / or PL-RS based on at least one of the following: an SSB for decoding the MIB, an SSB / CSI-RS identified during the RA procedure, an SSB for time / frequency acquisition, a beam for Msg3 or MsgA PUSCH, a DL RS in the TCI for at least one CORESET, or a TCI state from a configured TCI state list.

[0071] After network entity 104 and UE 102 apply the indicated TCI state or UE-initiated beam or TCI state 308, network entity 104 and UE can further communicate 310 based on the beam corresponding to the indicated TCI state or UE-initiated beam or TCI state (e.g., at least one DL channel or at least one UL channel).

[0072] In this disclosure, unless otherwise specified, RRC signaling may instruct an RRC reconfiguration message from the gNB to the UE, or a System Signal Block (SIB), where the SIB may be an existing SIB (e.g., SIB1) or a new SIB transmitted by the gNB (e.g., SIB J, where J is an integer greater than 21). In some implementations, network entity 104 may receive UE capabilities from the UE, from the core network (e.g., the Access and Mobility Management Function (AMF), or from another network entity.

[0073] Figures 1 to 3 The default beam and PL-RS technology used for DL ​​and UL channels are shown. Figures 4 to 12 The following diagram illustrates the implementation. Figures 1 to 3 One or more aspects of the method. In particular, Figure 11 The UE 102 is shown to be paired with Figures 1 to 3 The implementation of one or more aspects. Figure 12 104 pairs of network entities are shown. Figures 1 to 3 The implementation of one or more aspects.

[0074] In an embodiment, when more than one joint or uplink unified TCI state is configured in the initial RRC reconfiguration corresponding to a 2-step RA procedure or in an RRC reconfiguration with a synchronization procedure, after UE 102 receives the RRC reconfiguration and before UE 102 applies the indicated TCI state, or before UE 102 applies a UE-initiated beam or TCI state, UE 102 transmits at least one UL channel based on a UL TX spatial filter for the MsgA PUSCH. The UL channel may include a Dynamic Grant PUSCH, a Configuration Grant PUSCH, a PUCCH, and an SRS for applying the indicated TCI state.

[0075] In one example, UE 102 receives more than one TCI-State of dl-OrJointTCI- StateList or has more than one TCI-UL-State of ul-TCI-StateList After the initial higher-level configuration, and before applying the indicated TCI state from the configured TCI state, UE 102 assumes that the UL TX spatial filters (if applicable) used for PUSCH and PUCCH based on dynamic grant and configuration grant, and for SRS used to apply the indicated TCI state, are the same as the UL Tx spatial filters used for PUSCH transmissions or MsgA PUSCH transmissions scheduled by RAR UL grant during the initial access procedure.

[0076] In another example, when UE 102 receives more than one TCI-State or more than one TCI-UL- State of dl-OrJointTCI-StateList After a higher-level configuration (as part of a reconfiguration with a synchronization procedure as described in [3GPP TS 38.331]) and before applying the indicated TCI state from the configured TCI state, UE 102 assumes that the UL TX spatial filters (if applicable) for PUSCH and PUCCH based on dynamic granting and configuration granting, and for SRS for applying the indicated TCI state, are the same as those for PUSCH transmissions or MsgA PUSCH transmissions scheduled by RAR UL granting during the RA procedure initiated by a reconfiguration with a synchronization procedure as described in [3GPP TS 38.331].

[0077] In another example, when UE 102 receives more than one TCI-State of dl-OrJointTCI- StateList or has more than one TCI-UL-State of ul-TCI-StateListAfter the initial higher-level configuration, and before applying the indicated TCI state from the configured TCI state or applying the UE-initiated beam or TCI state, UE 102 assumes that the UL TX spatial filters (if applicable) used for PUSCH and PUCCH based on dynamic grant and configuration grant, and for SRS used to apply the indicated TCI state, are the same as the UL TX spatial filters used for PUSCH transmissions or MsgA PUSCH transmissions scheduled by RAR UL grant during the initial access procedure.

[0078] In another example, when UE 102 receives more than one TCI-State or more than one TCI-UL- State of dl-OrJointTCI-StateList After a higher-level configuration (as part of a reconfiguration with a synchronization procedure as described in [3GPP TS 38.331]), and before applying the indicated TCI state from the configured TCI state or applying a UE-initiated beam or TCI state, UE 102 assumes that the UL TX spatial filters (if applicable) used for PUSCH and PUCCH based on dynamic granting and configuration granting, and for SRS for applying the indicated TCI state, are the same as those used for PUSCH transmissions or MsgA PUSCH transmissions scheduled by RAR UL granting during an RA procedure initiated by a reconfiguration with a synchronization procedure as described in [3GPP TS 38.331].

[0079] In an embodiment, when at least one joint or uplink unified TCI state is configured in the initial RRC reconfiguration corresponding to a 2-step RA procedure or in an RRC reconfiguration with a synchronization procedure, after UE 102 receives the RRC reconfiguration and before UE 102 applies the indicated TCI state, or before UE 102 applies a UE-initiated beam or TCI state, UE 102 transmits at least one UL channel based on a UL TX spatial filter for MsgA PRACH. The UL channel may include a Dynamic Grant PUSCH, a Configuration Grant PUSCH, a PUCCH, and an SRS applying the indicated TCI state.

[0080] In one example, when UE 102 receives a message with more than one TCI-State... dl-OrJointTCI- StateList Or having more than one TCI-UL-State ul-TCI-StateListAfter the initial higher-level configuration, and before applying the indicated TCI state from the configured TCI state, UE 102 assumes that the UL TX spatial filters (if applicable) used for PUSCH and PUCCH based on dynamic grant and configuration grant, and for SRS for applying the indicated TCI state, are the same as the UL TX spatial filters used for PUSCH transmissions or MsgA PRACH transmissions scheduled by RAR UL grant during the initial access procedure.

[0081] In another example, when UE 102 receives more than one TCI-State or more than one TCI-UL- State of dl-OrJointTCI-StateList After a higher-level configuration (as part of a reconfiguration with a synchronization procedure as described in [3GPP TS 38.331]) and before applying the indicated TCI state from the configured TCI state, UE 102 assumes that the UL TX spatial filters (if applicable) for PUSCH and PUCCH based on dynamic granting and configuration granting, and for SRS for applying the indicated TCI state, are the same as the UL TX spatial filters for PUSCH transmissions or MsgA PRACH transmissions scheduled by RAR UL granting during the RA procedure initiated by a reconfiguration with a synchronization procedure as described in [3GPP TS 38.331].

[0082] In another example, when UE 102 receives a device with at least one TCI-State of dl-OrJointTCI- StateList Or having at least one TCI-UL-State ul-TCI-StateList After the initial higher-level configuration, and before applying the indicated TCI state from the configured TCI state or applying the UE-initiated beam or TCI state, UE 102 assumes that the UL TX spatial filters (if applicable) used for PUSCH and PUCCH based on dynamic grant and configuration grant, and for SRS used to apply the indicated TCI state, are the same as the UL TX spatial filters used for PUSCH transmissions or MsgA PRACH transmissions scheduled by RAR UL grant during the initial access procedure.

[0083] In another example, when UE 102 receives more than one TCI-State or more than one TCI-UL- State of dl-OrJointTCI-StateListAfter a higher-level configuration (as part of a reconfiguration with a synchronization procedure as described in [3GPP TS 38.331]), and before applying the indicated TCI state from the configured TCI state or applying a UE-initiated beam or TCI state, UE 102 assumes that the UL TX spatial filters (if applicable) used for PUSCH and PUCCH based on dynamic granting and configuration granting, and for SRS for applying the indicated TCI state, are the same as the UL TX spatial filters used for PUSCH transmissions or MsgA PRACH transmissions scheduled by RAR UL granting during an RA procedure initiated by a reconfiguration with a synchronization procedure as described in [3GPP TS 38.331].

[0084] In an embodiment, when at least one joint or uplink unified TCI state is configured in an initial RRC reconfiguration corresponding to a 2-step RA procedure or an RRC reconfiguration with a synchronization procedure, after UE 102 receives the RRC reconfiguration and before UE 102 applies the indicated TCI state or before UE 102 applies a UE-initiated beam or TCI state, UE 102 transmits at least one UL channel based on a UL TX spatial filter for a first joint or uplink TCI state configured in the TCI state list. The UL channel may include a Dynamic Grant PUSCH, a Configuration Grant PUSCH, a PUCCH, and an SRS for applying the indicated TCI state. In other examples, UE 102 transmits at least one UL channel based on a UL TX spatial filter for the joint or uplink TCI state with the lowest TCI state ID configured in the TCI state list. In yet another example, UE 102 transmits at least one UL channel based on a UL TX spatial filter for a first activated joint or uplink TCI state.

[0085] In an embodiment, when at least one joint or uplink unified TCI state is configured in the initial RRC reconfiguration corresponding to a 2-step RA procedure or an RRC reconfiguration with a synchronization procedure, after UE 102 receives the RRC reconfiguration and before UE applies the indicated TCI state, or before UE 102 applies a UE-initiated beam or TCI state, UE 102 transmits at least one UL channel based on a UL TX spatial filter that serves as a DL receive (RX) spatial filter for receiving SSB / CSI-RS associated with PRACH. The UL channel may include a Dynamic Grant PUSCH, a Configuration Grant PUSCH, a PUCCH, and an SRS that applies the indicated TCI state. In other examples, UE 102 transmits at least one UL channel based on a UL TX spatial filter that serves as a DL receive (RX) spatial filter for receiving MsgB RAR reception. In yet another example, UE 102 transmits at least one UL channel based on a UL TX spatial filter that serves as a DL RX spatial filter for receiving MsgB PDSCH reception.

[0086] In an embodiment, when at least one joint or uplink unified TCI state is configured in the initial RRC reconfiguration corresponding to a 2-step RA procedure or in an RRC reconfiguration with a synchronization procedure, after UE 102 receives the RRC reconfiguration and before UE 102 applies the indicated TCI state or before UE 102 applies a UE-initiated beam or TCI state, UE 102 transmits at least one UL channel based on a default beam configured by network entity 104. Network entity 104 may configure the default beam based on one of the following: a beam for MsgA PUSCH, a beam for MsgA PRACH, a first TCI state in the configured TCI state list, or a beam for SSB / CSI-RS identified during the RA procedure. The UL channel may include a dynamically granted PUSCH, a configured granted PUSCH, a PUCCH, and an SRS applying the indicated TCI state.

[0087] Furthermore, UE 102 may report UE capabilities indicating the supported default beam based on the beam used for MsgA PUSCH, the beam used for MsgA PRACH, the first TCI state in the configured TCI state list, or the beam used for the SSB / CSI-RS identified during the RA process, or at least one of the above methods.

[0088] In an embodiment, when at least one joint or uplink / downlink unified TCI state is configured in an initial RRC reconfiguration or an RRC reconfiguration with a synchronization process, after UE 102 receives the RRC reconfiguration and before UE 102 applies the indicated TCI state, or before UE 102 applies a UE-initiated beam or TCI state, for SCell, UE 102 receives at least one DL channel based on QCL parameters derived from the SSB for time and frequency synchronization, or transmits at least one UL channel based on a UL TX spatial filter as a DL RX spatial filter for receiving the SSB for time and frequency synchronization. The DL channel may include PDSCH, PDCCH, and CSI-RS for applying the indicated TCI state. The UL channel may include Dynamic Grant PUSCH, Configuration Grant PUSCH, PUCCH, and SRS for applying the indicated TCI state.

[0089] In one example, UE 102 receives more than one TCI-State of dl-OrJointTCI- StateList After the initial higher-layer configuration, and before applying the indicated TCI state from the configured TCI state, UE 102 assumes that the DM-RS of PDSCH and the DM-RS of PDCCH, as well as the CSI-RS with the indicated TCI state, are quasi-co-located with the SS / PBCH block identified by the UE during the initial access procedure or the SS / PBCH block for which the UE has obtained time and frequency synchronization for SCell.

[0090] In another example, when UE 102 receives more than one TCI-State of dl-OrJointTCI- StateList or has more than one TCI-UL-State of ul-TCI-StateList After the initial higher-layer configuration, and before applying the indicated TCI state from the configured TCI state, UE 102 assumes that the UL TX spatial filter (if applicable) for PUSCH and PUCCH based on dynamic grant and configuration grant, and for SRS for applying the indicated TCI state, is the same as the UL TX spatial filter for PUSCH transmissions scheduled by RAR UL grant during the initial access procedure, or the DL RX spatial filter for UE 102 to obtain time and frequency synchronized SS / PBCH blocks for SCell.

[0091] In another example, when UE 102 receives more than one TCI-State of dl-OrJointTCI- StateListAfter a higher-level configuration (as part of a reconfiguration with a synchronization procedure as described in [3GPP TS 38.331]), and before applying the TCI state indicated from the configured TCI state, UE 102 assumes that the DM-RS of PDSCH and the DM-RS of PDCCH, as well as the CSI-RS with the indicated TCI state, are QCLs with the SS / PBCH block or CSI-RS resource identified by UE 102 during the RA procedure initiated by the reconfiguration with a synchronization procedure as described in [3GPP TS 38.331] or the SS / PBCH block for which UE 102 has obtained time and frequency synchronization for SCell.

[0092] In another example, when UE 102 receives more than one TCI-State or more than one TCI-UL- State of dl-OrJointTCI-StateList After a higher-level configuration (as part of a reconfiguration with a synchronization procedure as described in [3GPP TS 38.331]) and before applying the indicated TCI state from the configured TCI state, UE 102 assumes that the UL TX spatial filter (if applicable) for PUSCH and PUCCH based on dynamic granting and configuration granting, and for SRS for applying the indicated TCI state, is the same as the UL TX spatial filter for PUSCH transmissions scheduled by RAR UL granting during the RA procedure initiated by the reconfiguration with a synchronization procedure as described in [3GPP TS 38.331], or the DL RX spatial filter for SS / PBCH blocks for which the UE has obtained time and frequency synchronization for SCell.

[0093] In another example, when UE 102 receives a device with at least one TCI-State of dl-OrJointTCI- StateList After the initial higher-level configuration, and before applying the indicated TCI state from the configured TCI state or applying the UE-initiated beam or TCI state, UE 102 assumes that the DM-RS of PDSCH and the DM-RS of PDCCH, as well as the CSI-RS of the indicated TCI state, are QCLs with the SS / PBCH block identified by UE 102 during the initial access procedure or the SS / PBCH block for which UE 102 has obtained time and frequency synchronization for SCell.

[0094] In another example, when UE 102 receives more than one TCI-State of dl-OrJointTCI- StateList or has more than one TCI-UL-State oful-TCI-StateList After the initial higher-level configuration, and before applying the indicated TCI state from the configured TCI state or applying the UE-initiated beam or TCI state, UE 102 assumes that the UL TX spatial filter (if applicable) for the PUSCH and PUCCH based on dynamic grant and configuration grant, and for the SRS for applying the indicated TCI state, is the same as the UL TX spatial filter for the PUSCH transmission scheduled by RAR UL grant during the initial access procedure or the DL RX spatial filter for the UE to obtain the SS / PBCH block for time and frequency synchronization for the SCell.

[0095] In another example, when UE 102 receives more than one TCI-State of dl-OrJointTCI- StateList After a higher-level configuration (as part of a reconfiguration with a synchronization procedure as described in [3GPP TS 38.331]), and before applying the indicated TCI state from the configured TCI state or applying a UE-initiated beam or TCI state, UE 102 assumes that the DM-RS of PDSCH and the DM-RS of PDCCH, as well as the CSI-RS with the indicated TCI state, are quasi-co-located with the SS / PBCH block or CSI-RS resource identified by UE 102 during the RA procedure initiated by the reconfiguration with a synchronization procedure as described in [3GPP TS 38.331] or the SS / PBCH block for which UE 102 has obtained time and frequency synchronization for SCell.

[0096] In another example, when UE 102 receives more than one TCI-State or more than one TCI-UL- State of dl-OrJointTCI-StateList After a higher-level configuration (as part of a reconfiguration with a synchronization procedure as described in [3GPP TS 38.331]), and before applying the indicated TCI state from the configured TCI state or applying a UE-initiated beam or TCI state, UE 102 assumes that the UL TX spatial filter (if applicable) for PUSCH and PUCCH based on dynamic granting and configuration granting, and for SRS for applying the indicated TCI state, is the same as the UL TX spatial filter for PUSCH transmissions scheduled by RAR UL granting during the RA procedure initiated by a reconfiguration with a synchronization procedure as described in [3GPP TS 38.331], or the DL RX spatial filter for SS / PBCH blocks for which UE 102 has obtained time and frequency synchronization for SCell.

[0097] In an embodiment, when at least one joint or downlink / uplink unified TCI state is configured in an initial RRC reconfiguration or an RRC reconfiguration with a synchronization process, after the UE receives the RRC reconfiguration and before the UE 102 applies the indicated TCI state, or before the UE 102 applies a UE-initiated beam or TCI state, for an SCell, the UE 102 receives at least one DL channel based on a first joint or downlink TCI state configured in a list of joint or downlink TCI states in the BWP (e.g., active BWP, initial BWP, or first BWP) for the SCell, or transmits at least one UL channel based on a UL TX spatial filter of a first joint or uplink TCI state configured in a list of joint or uplink TCI states in the BWP (e.g., active BWP, initial BWP, or first BWP) for the SCell. The DL channel may include PDSCH, PDCCH, and CSI-RS of the TCI state indicated by the application. The UL channel may include Dynamic Grant PUSCH, Configuration Grant PUSCH, PUCCH, and SRS of the TCI state indicated by the application.

[0098] In an embodiment, when at least one joint or downlink / uplink unified TCI state is configured in an initial RRC reconfiguration or an RRC reconfiguration with a synchronization process, after the UE receives the RRC reconfiguration and before the UE102 applies the indicated TCI state or before the UE102 applies the UE-initiated beam or TCI state, for the SCell, the UE receives at least one DL channel or transmits at least one UL channel based on the configured default beam. The DL channel may include the PDSCH, PDCCH, and CSI-RS of the TCI state indicated by the application. The UL channel may include the Dynamic Grant PUSCH, Configuration Grant PUSCH, PUCCH, and SRS of the TCI state indicated by the application.

[0099] Network entity 104 can configure a default beam based on one of the following: the beam for SSB used for time and frequency synchronization, the first TCI state in the configured TCI state list, or the beam identified during the RA process for SSB / CSI-RS or MsgA / Msg3 PUSCH. Network entity 104 can transmit the configuration via RRC signaling or MAC CE (e.g., MAC CE for activating SCell).

[0100] Furthermore, in some implementations, UE 102 may report UE capabilities indicating the supported default beam based on at least one of the beam of the SSB used for time and frequency synchronization, the first TCI state in the configured TCI state list, or the beam for SSB / CSI-RS or MsgA / Msg3 PUSCH identified in the RA process.

[0101] In the embodiment, when at least one joint or uplink unified TCI state is configured in the initial RRC reconfiguration or RRC reconfiguration with a synchronization process and for at least one UL channel (e.g., enableDefaultBeamPL- ForPUSCH0-0 , enableDefaultBeamPL-ForPUCCH and enableDefaultBeamPL-ForSRS When the default beam and PL-RS are enabled, after UE 102 receives the RRC reconfiguration and before UE 102 applies the indicated TCI state or before UE 102 applies the UE-initiated beam or TCI state, UE 102 transmits at least one UL channel based on the DL RX spatial filter of the DL RS in the TCI state of the lowest ID CORESET used in the active BWP. The UL channel may include a Dynamic Grant PUSCH, a Configuration Grant PUSCH, a PUCCH, and an SRS applying the indicated TCI state. In one example, the TCI state refers to either the indicated TCI state or the UE-initiated beam or TCI state applied to the CORESET. In another example, when determining the CORESET with the lowest ID, the UE only considers / selects the CORESET applying the indicated TCI state. In another example, when the default beam and PL-RS are enabled for at least one UL channel during an initial RRC reconfiguration or an RRC reconfiguration with a synchronization process, network entity 104 should ensure that the active BWP has the TCI status indicated by the CORESET application with the lowest ID.

[0102] In one example, UE 102 receives more than one TCI-State of dl-OrJointTCI- StateList or has more than one TCI-UL-State of ul-TCI-StateList After the initial higher-level configuration, and before applying the indicated TCI state from the configured TCI state, UE 102 assumes that PUSCH is used for dynamic authorization and configuration authorization (if not provided). enableDefaultBeamPL-ForPUSCH0-0 ) and PUCCH (if not provided) enableDefaultBeamPL-ForPUCCH ) and the SRS used to apply the indicated TCI status (if not provided) enableDefaultBeamPL-ForSRS The UL TX spatial filter (if applicable) is the same as the UL TX spatial filter used for PUSCH transmissions scheduled by RAR UL authorization during the initial access process.

[0103] In another example, when UE 102 receives more than one TCI-State or more than one TCI-UL- State of dl-OrJointTCI-StateList After higher-level configuration (as part of a reconfiguration with a synchronization process as described in [3GPP TS 38.331]), and before applying the indicated TCI state from the configured TCI state, UE 102 assumes that PUSCH (if not provided) is used for dynamic granting and configuration granting. enableDefaultBeamPL-ForPUSCH0-0 ) and PUCCH (if not provided) enableDefaultBeamPL- ForPUCCH ) and the SRS used to apply the indicated TCI status (if not provided) enableDefaultBeamPL- ForSRS The UL TX spatial filter (if applicable) is the same as the UL TX spatial filter used for PUSCH transmissions scheduled by RAR UL authorization during a RA process initiated by a reconfiguration with a synchronization process as described in [3GPP TS 38.331].

[0104] In another example, when UE 102 receives more than one TCI-State of dl-OrJointTCI- StateList or has more than one TCI-UL-State of ul-TCI-StateList After the initial higher-level configuration, and before applying the indicated TCI state from the configured TCI state or applying the UE-initiated beam or TCI state, UE 102 assumes that PUSCH is used for dynamic authorization and configuration authorization (if not provided). enableDefaultBeamPL-ForPUSCH0-0 ) and PUCCH (if not provided) enableDefaultBeamPL- ForPUCCH ) and the SRS used to apply the indicated TCI status (if not provided) enableDefaultBeamPL- ForSRS The UL TX spatial filter (if applicable) is the same as the UL TX spatial filter used for PUSCH transmissions scheduled by RAR UL authorization during the initial access process.

[0105] In another example, when UE 102 receives more than one TCI-State or more than one TCI-UL- State of dl-OrJointTCI-StateList After higher-level configuration (as part of a reconfiguration with a synchronization procedure as described in [3GPP TS 38.331]), and before applying the TCI state indicated by the configured TCI state or the UE-initiated beam or TCI state, UE 102 assumes that PUSCH based on dynamic granting and configuration granting (if not provided) is used. enableDefaultBeamPL-ForPUSCH0-0 ) and PUCCH (if not provided) enableDefaultBeamPL-ForPUCCH ) and the SRS used to apply the indicated TCI status (if not provided) enableDefaultBeamPL-ForSRS The UL TX spatial filter (if applicable) is the same as the UL TX spatial filter used for PUSCH transmissions scheduled by RAR UL authorization during a RA process initiated by a reconfiguration with a synchronization process as described in [3GPPTS 38.331].

[0106] In another example, if UE 102 is not provided pathlossReferenceRS Not provided PUCCH- SpatialRelationInfo and was provided enableDefaultBeamPL-ForPUCCH And no instructions were given. TCI-State or TCI-UL-State If a coresetPoolIndex value of 1 for any CORESET is not provided in the ControlResourceSet, or a coresetPoolIndex value of 1 for all CORESETs is provided, and no code point of any TCI field in DCI format (if any) in the search space set is mapped to two TCI states, then UE102 determines the PL-RS resource index q_d for providing PUCCH power control with a periodic RS resource configured with qcl-Type, which is set to "typeD" in the TCI state or QCL assumption of the CORESET with the lowest index in the active DL BWP of the primary cell. If the CORESET has two active TCI states, the UE determines the RS resource index q_d based on the first active TCI state. For PUCCH transmissions on multiple time slots, the same q_d is applied to PUCCH transmissions in each of the multiple time slots.

[0107] In another example, if UE 102 is in PUCCH-PowerControl Not provided pathlossReferenceRS Provided enableDefaultBeamPL-ForPUCCH And it was not provided. PUCCH- SpatialRelationInfo And not instructed to have TCI-State or TCI-UL-State And in ControlResourceSet Not provided with a value of 1 for any CORESET coresetPoolIndex The value, or a value of 1 provided for all CORESETs. coresetPoolIndex The code points of the TCI fields (if any) in DCI format without any search space set are mapped to two TCI states. The spatial setting for PUCCH transmission from UE 102 is the same as the spatial setting for PDCCH reception by UE in the CORESET with the lowest ID on the active DL BWP of the PCell. If the CORESET has two active TCI states, UE 102 determines the spatial setting for PUCCH transmission based on the first active TCI state. For PUCCH transmissions on multiple time slots, the same spatial setting is applied to PUCCH transmissions in each of the multiple time slots.

[0108] In another example, if the UE is not provided pathlossReferenceRS or SRS- PathlossReferenceRS-Id Not provided spatialRelationInfo and was provided enableDefaultBeamPL-ForSRS And not instructed to have TCI-State or TCI-UL-State If a coresetPoolIndex value of 1 for any CORESET is not provided in the ControlResourceSet, or a coresetPoolIndex value of 1 for all CORESETs is provided, and there are no code points in the DCI format of any search space set (if any) mapped to the two TCI states, then if a CORESET is provided in the active DL BWP of the serving cell, UE 102 determines that it is used to provide the configured coresetPoolIndex. qcl-Type Index of PL-RS resources for SRS power control of periodic RS resources The qcl-Type is set to "typeD" under the TCI state or QCL assumption of the lowest indexed CORESET in the active DL BWP. If the CORESET has two active TCI states, UE 102 determines the RS resource index based on the first TCI state; if no CORESET is provided in the active DL BWP of the serving cell, the RS resource index is determined based on the active PDSCH TCI state with the lowest ID in the active DL BWP. .

[0109] In another example, when higher-level parameters enableDefaultBeamPL-ForSRS When set to "Enabled", and if no higher-level parameters for SRS resources are configured in frequency range (FR) 2 (e.g., frequency ranges above 7 GHz or 28 GHz). spatialRelationInfo (besides the higher-level parameters in SRS-ResourceSet) usage SRS resources set to "beamManagement" or in the configuration associatedCSI-RS In the case of higher-level parameters in SRS-ResourceSet usage SRS resources set to "nonCodebook" or by higher-level parameters SRS-PosResourceSet (In addition to the configured SRS resources), and if UE 102 is not configured with higher-level parameters. pathlossReferenceRS Furthermore, if UE 102 is not configured with a distinct value for coresetPoolIndex in ControlResourceSets, and is not provided with at least one TCI code point mapped to two TCI states, and if UE 102 is not indicated to have SRS resources... TCI-State or TCI-UL-State Then UE 102 should (i) transmit the target SRS resource in the active UL BWP of the CC according to the spatial relationship of the RS configured with qcl-Type (if applicable), which has the lowest qcl-Type in the active DL BWP of the component carrier (CC). controlResourceSetId The QCL of the CORESET is assumed to be set to "typeD" accordingly. If the CORESET is activated with two TCI states, the configuration... sfnSchemePdcch And UE 102 supports sfn-DefaultUL-BeamSetup-r17 If UE 102 does not have any CORESET in an active DL BWP with CC configured, UE 102 shall (ii) use the first TCI state as the QCL assumption based on the spatial relationship of RS with qcl-Type configured (if applicable), which is set to "typeD" in the active TCI state of the PDSCH in the active DL BWP with the lowest ID applicable to CC.

[0110] In the embodiment, when at least one joint or uplink unified TCI state is configured in the initial RRC reconfiguration or RRC reconfiguration with a synchronization process and for at least one UL channel (e.g., enableDefaultBeamPL- ForPUSCH0-0 , enableDefaultBeamPL-ForPUCCH and enableDefaultBeamPL-ForSRS When the default beam and PL-RS are enabled, after UE 102 receives the RRC reconfiguration and before UE 102 applies the indicated TCI state, or before UE 102 applies the UE-initiated beam or TCI state, UE 102 transmits at least one UL channel based on a UL TX spatial filter as MsgA PUSCH or Msg3PUSCH. This UL channel may include a Dynamic Grant PUSCH, a Configuration Grant PUSCH, a PUCCH, and an SRS for the applied TCI state.

[0111] In some implementations, when no unified TCI state is configured by network entity 104, UE 102 only applies the enabled default beam or PL-RS. In some examples, when network entity 104 does not configure a unified TCI state for UE 102, network entity 104 simply configures / instructs UE 102 to enable or use the default beam or PL-RS. In some other implementations, network entity 104 avoids enabling the default beam (e.g., configuring...). enableDefaultBeamPL-ForPUSCH0- 0、enableDefaultBeamPL-ForPUCCH or enableDefaultBeamPL-ForSRS And configure a unified TCI state for the same serving cell or BWP. Therefore, UE 102 does not expect network entity 104 to enable the default beam (e.g., configure...). enableDefaultBeamPL-ForPUSCH0-0、enableDefaultBeamPL-ForPUCCH or enableDefaultBeamPL-ForSRS Configure a unified TCI status for the same serving cell or BWP.

[0112] In one example, if UE 102 is not provided pathlossReferenceRS And it was not provided. PUCCH- SpatialRelationInfo and was provided enableDefaultBeamPL-ForPUCCH And it was not provided. dl- OrJointTCI-StateList In TCI-State or TCI-UL-State If, in ControlResourceSe, a coresetPoolIndex value of 1 for any CORESET is not provided, or a coresetPoolIndex of 1 for all CORESETs is provided, and there are no code points in the DCI format of any search space set (if any) mapped to the two TCI states, then UE 102 determines that the configuration is used to provide the coresetPoolIndex value. qcl-Type PL-RS resource index for periodic RS resource PUCCH power control The qcl-Type is set to "typeD" in the TCI state or QCL assumption of the CORESET with the lowest index in the active DL BWP of the primary cell. If the CORESET has two active TCI states, UE 102 determines the RS resource index based on the first active TCI state. For PUCCH transmissions across multiple time slots, the same PUCCH transmission is applied to each of the multiple time slots.

[0113] In another example, if UE 102 is in PUCCH-PowerControl Not provided pathlossReferenceRS Provided enableDefaultBeamPL-ForPUCCH And it was not provided. PUCCH- SpatialRelationInfo And it was not provided. dl-OrJointTCI-StateList In TCI-State or TCI-UL-State, and in ControlResourceSet Not provided with a value of 1 for any CORESET coresetPoolIndex The value, or a value of 1 provided for all CORESETs. coresetPoolIndex The code points of the TCI field (if any) in DCI format, which are not in any search space set, are mapped to two TCI states. The spatial setting for PUCCH transmission from UE 102 is the same as the spatial setting for PDCCH reception by the UE in the CORESET with the lowest ID on the active DL BWP on the PCell. If the CORESET has two active TCI states, the UE determines the spatial setting for PUCCH transmission based on the first TCI state. For PUCCH transmissions on multiple time slots, the same spatial setting is applied to PUCCH transmissions in each of the multiple time slots.

[0114] In another example, if UE 102 is not provided pathlossReferenceRS or SRS- PathlossReferenceRS-Id Not provided spatialRelationInfo and was provided enableDefaultBeamPL-ForSRS And it was not provided. dl-OrJointTCI-StateList In TCI-State or TCI-UL-State If a coresetPoolIndex value of 1 for any CORESET is not provided in the ControlResourceSet, or a coresetPoolIndex value of 1 for all CORESETs is provided, and there are no code points in the DCI format of any search space set (if any) mapped to the two TCI states, then if a CORESET is provided in the active DL BWP of the serving cell, the UE determines that it is used to provide the configured coresetPoolIndex. qcl-Type Index of PL-RS resources for SRS power control of periodic RS resources The qcl-Type is set to "typeD" under the TCI state or QCL assumption of the lowest indexed CORESET in (i) the active DL BWP. If the CORESET has two active TCI states, the UE determines the RS resource index based on the first TCI state; (ii) if the active DL BWP of the serving cell does not provide a CORESET, the RS resource index is determined based on the active PDSCH TCI state with the lowest ID in the active DL BWP. .

[0115] In another example, when higher-level parameters enableDefaultBeamPL-ForSRS When set to "Enabled", and if no higher-level parameters for SRS resources are configured in frequency range (FR) 2 (e.g., frequency ranges above 7 GHz or 28 GHz). spatialRelationInfo (Apart from SRS-ResourceSet Higher-level parameters usage SRS resources set to "beamManagement" or in the configuration associatedCSI-RS In the case of SRS- ResourceSet Higher-level parameters usage SRS resources set to "nonCodebook" or by higher-level parameters SRS-PosResourceSet (In addition to the configured SRS resources), and if UE 102 is not configured with higher-level parameters. pathlossReferenceRS Furthermore, if UE 102 is not configured with distinct values ​​for coresetPoolIndex in ControlResourceSets, and is not provided with at least one TCI code point mapped to both TCI states, and if UE 102 is not provided with dl-OrJointTCI-StateList In TCI-State or TCI-UL-State Then UE102 should (i) have according to the reference configuration qcl-TypeThe spatial relationship of the RS (if applicable) in the active ULBWP of the CC transmits the target SRS resources, the qcl-Type of which has the lowest qcl-type in the active DLBWP of the component carrier (CC). controlResourceSetId The QCL of the CORESET is assumed to be set to "typeD" accordingly. If the CORESET is activated with two TCI states, the configuration... sfnSchemePdcch And UE supports sfn-DefaultUL-BeamSetup-r17 If the UE is not configured with any core set in the active DL BWP of CC, the UE should be configured according to the reference configuration. qcl-Type The spatial relationship of RS (if applicable) uses the first TCI state as the QCL assumption, which is set to "typeD" in the active TCI state of the PDSCH in the active DL BWP with the lowest ID applicable to CC.

[0116] In an embodiment, when more than one joint or uplink unified TCI state and mTRP operation for at least one DL channel or UL channel are configured in an initial RRC reconfiguration or an RRC reconfiguration with a synchronization process, after the UE receives the RRC reconfiguration and before the UE applies the indicated TCI state or before the UE applies the UE-initiated beam or TCI state, the UE receives at least one DL channel or transmits a UL channel based on more than one default beam.

[0117] In some implementations, network entity 104 configures mTRP operation for UL or DL ​​channels by configuring at least one CORESET pool index, or by configuring an mTRP scheme (e.g., SDM / FDM / TDM / SFN) for UL or DL ​​channels, or by configuring a link between two search spaces for mTRP PDCCH. UL channels may include PUSCH and PUCCH. DL channels may include PDSCH and PDCCH.

[0118] In some implementations, network entity 104 and UE 102 can determine more than one default beam based on N (N>1, e.g., N=2) TCI states reconfigured via RRC, such as the first N TCI states in a configured joint or uplink or downlink TCI state list, or N TCI states configured by network entity 104. For channels configured with mTRP operation, UE 102 applies the N TCI states. For channels not configured with mTRP operation, UE 102 can apply one of the N TCI states configurable via RRC signaling, such as the RRC signaling instructing UE 102 to apply either the first or second TCI state, or UE 102 can apply the SSB / CSI-RS for the RA procedure identifier for QCL determination of the DL channel, or apply the MsgA or Msg3 PUSCH beam to the UL TX spatial filter for the UL channel.

[0119] In some implementations, network entity 104 and UE 102 may determine a default beam for a channel corresponding to a CORESET pool index. Network entity 104 and UE 102 may determine the default beam for the CORESET pool based on the DL RS in the TCI state or the QCL corresponding to a CORESET in the CORESET pool (e.g., the CORESET with the lowest ID among the CORESETs in the CORESET pool). If two DL RSs are configured for a CORESET in the TCI state, network entity 104 and UE 102 determine the default beam based on the DL RS used for the QCL-TypeD indication. If more than one TCI state exists for a CORESET indication (e.g., two TCI states), network entity 104 and UE 102 may determine the default beam based on a predefined TCI state (e.g., the first indicated TCI state, or a TCI state among more than one TCI state configured by network entity 104).

[0120] In an embodiment, when at least one joint or uplink unified TCI state and mTRP operation for at least one DL channel or UL channel are configured in an initial RRC reconfiguration or an RRC reconfiguration with a synchronization process, after UE 102 receives the RRC reconfiguration and before UE 102 applies the indicated TCI state or before UE 102 applies a UE-initiated beam or TCI state, network entity 104 avoids scheduling at least one DL channel or UL channel with an mTRP operation. Network entity 104 can schedule at least one DL channel or UL channel based on a single TRP operation. Therefore, after UE 102 receives the initial RRC reconfiguration or an RRC reconfiguration with a synchronization process and before UE applies the indicated TCI state or before UE applies a UE-initiated beam or TCI state, UE 102 may not expect network entity 104 to schedule at least one DL channel or UL channel with an mTRP operation.

[0121] In some other implementations, network entity 104 can avoid scheduling at least one DL channel or UL channel using mTRP operations that require the UE to perform simultaneous transmission and / or simultaneous reception with two different TCI states or QCL assumptions (e.g., SDM scheme, SFN scheme, FDM scheme, or channels from different CORESET pools that overlap in the time domain).

[0122] Figure 4 Illustration 400 shows an example of default beam determination based on SSB / CSI-RS resource indexes (e.g., SSB / CSI-RS 1, SSB / CSI-RS 2, ..., SSB / CSI-RS K) according to an embodiment.

[0123] UE 102 transmits a PRACH (also referred to as Msg1 or RA preamble) associated with SSB / CSI-RS 1 424A, and another PRACH (also referred to as Msg1 or RA preamble) associated with SSB / CSI-RS K 424B. In response to receiving Msg1, network entity 104 transmits an RA response (RAR) referred to as Msg2 426. UE 102 transmits Msg3 428 on the PUSCH. Network entity 104 transmits an RRC reconfiguration 430 indicating a list of TCI states (configured TCI states). Network entity 104 transmits a TCI indication (e.g., MAC-CE or DCI) 432 indicating at least one TCI state from the list of TCI states. UE 102 transmits an ACK 434 for TCI indication 432. UE 102 applies the beam corresponding to at least one TCI state based on the time of action following the ACK transmission.

[0124] In some implementations, after UE 102 receives RRC reconfiguration 430 and before UE 102 applies the indicated TCI state 436, or before UE 102 applies a UE-initiated beam or TCI state, the default beam can be determined based on (e.g., associated with PRACH transmissions 424A, 424B) the SSB / CSI-RS resource index. For example, when more than one joint unified TCI state is configured in the initial RRC reconfiguration 430 corresponding to an RA procedure that identifies more than one SSB / CSI-RS, or in an RRC reconfiguration 430 with a synchronization procedure, UE 102 receives at least one DL channel based on one of the SSB / CSI-RS identified during the RA procedure. In some other implementations, the SSB / CSI-RS used for default beam determination can be predefined, configured by a network entity, or reported by UE 102.

[0125] In some implementations, network entity 104 and UE 102 can determine the default beam based on the SSB / CSI-RS resource index. For example, network entity 104 and UE 102 determine the default beam based on the lowest or highest SSB / CSI-RS resource index identified during the RA procedure. (See reference) Figure 4 Network entity 104 and UE 102 determine the default beam based on the SSB / CSI-RS with a resource index of 1 associated with PRACH transmission 424A (e.g., based on the lowest SSB / CSI-RS resource index). In other implementations, the network entity and UE determine the default beam based on the SSB / CSI-RS with a resource index of K associated with PRACH transmission 424B (e.g., based on the highest SSB / CSI-RS resource index).

[0126] In one example, UE 102 receives more than one TCI-State of dl-OrJointTCI- StateList After the initial higher-layer configuration, and before applying the indicated TCI state from the configured TCI state, UE 102 assumes that the DM-RS of PDSCH and the DM-RS of PDCCH, as well as the CSI-RS of applying the indicated TCI state, are quasi-co-located with the SS / PBCH blocks identified by UE 102 during the initial access procedure, and if more than one SS / PBCH block is identified, the SS / PBCH block with the lowest SS / PBCH index among the identified SS / PBCH blocks is selected.

[0127] In another example, when UE 102 receives more than one TCI-State ofdl-OrJointTCI- StateList After a higher-level configuration (as part of a reconfiguration with a synchronization procedure as described in [3GPP TS 38.331]), and before applying the indicated TCI state from the configured TCI state, UE 102 assumes that the DM-RS of PDSCH and the DM-RS of PDCCH, as well as the CSI-RS with the indicated TCI state, are quasi-co-located with the SS / PBCH block or CSI-RS resource identified by the UE during the RA procedure initiated by the reconfiguration with a synchronization procedure as described in [3GPP TS 38.331], and if more than one SS / PBCH block or CSI-RS resource is identified, the SS / PBCH block or CSI-RS resource with the lowest SS / PBCH or CSI-RS resource index among the identified SS / PBCH blocks or CSI-RS resources is selected.

[0128] Figure 5 Illustration 500 shows an example of default beam determination based on SSB / CSI-RS time-domain location according to an embodiment.

[0129] UE 102 transmits a PRACH (also known as Msg1 or RA preamble) associated with SSB / CSI-RS 1 524A, and another PRACH (also known as Msg1 or RA preamble) associated with SSB / CSI-RS K 524B. In response to receiving Msg1, network entity 104 transmits an RA response (RAR) known as Msg2 526. UE 102 transmits Msg3 528 on the PUSCH.

[0130] Network entity 104 transmits an RRC reconfiguration 530 indicating a list of TCI states (configured TCI states). Network entity 104 transmits a TCI indication (e.g., MAC-CE or DCI) 532 for indicating at least one TCI state from the list of TCI states. UE 102 transmits an ACK 534 for the TCI indication 532. UE 102 applies the beam corresponding to at least one TCI state based on the time of action following the ACK transmission. 536 The TCI state is applied based on the time of action following the ACK feedback 534 associated with the DCI format conveying the TCI state.

[0131] In some implementations, network entity 104 and UE 102 can determine the default beam based on the time-domain location of the SSB / CSI-RS (e.g., the first or last SSB / CSI-RS associated with PRACH transmissions 524A and 524B). (See reference.) Figure 5Network entity 104 and UE 102 determine the default beam based on the last ending SSB / CSI-RS (e.g., SSB / CSI-RS K associated with PRACH transmission 524B). In other implementations, the network and UE determine the default beam based on the first starting SSB / CSI-RS (e.g., SSB / CSI-RS 1 associated with PRACH transmission 524A).

[0132] In one example, UE 102 receives more than one TCI-State of dl-OrJointTCI- StateList After the initial higher-layer configuration, and before applying the indicated TCI state from the configured TCI state, UE 102 assumes that the DM-RS of the PDSCH and the DM-RS of the PDCCH, as well as the CSI-RS of the applied indicated TCI state, are QCLs with the SS / PBCH block identified by the UE during the initial access procedure. If more than one SS / PBCH block is identified, the SS / PBCH block that ends later is selected.

[0133] In another example, when the UE receives more than one TCI-State of dl-OrJointTCI-StateList Following higher-level configuration (as part of a reconfiguration with a synchronization procedure as described in [3GPP TS 38.331]) and before applying the indicated TCI state from the configured TCI state, the UE assumes that the DM-RS of the PDSCH and the DM-RS of the PDCCH are quasi-co-located. The UE also assumes that the CSI-RS with the indicated TCI state applied is quasi-co-located with the SS / PBCH block or CSI-RS resource identified by the UE during the RA procedure initiated by the reconfiguration with a synchronization procedure as described in [3GPP TS 38.331]. If more than one SS / PBCH block or CSI-RS resource is identified, the SS / PBCH block or CSI-RS resource that ends later is selected.

[0134] Figure 6 Illustration 600 shows an example of default beam determination based on network entity configuration according to an embodiment.

[0135] UE 102 transmits a PRACH (also known as Msg1 or RA preamble) associated with SSB / CSI-RS 1 624A and another PRACH (also known as Msg1 or RA preamble) associated with SSB / CSI-RS K 624B. In response to receiving Msg1, network entity 104 transmits an RA response (RAR) referred to as Msg2 626. Network entity 104 transmits an RRC reconfiguration 630 indicating a list of TCI states (configured TCI states). The RRC reconfiguration 630 also indicates the default beam based on SSB / CSI-RS x (therefore UE 102 uses this default beam for communication before the action time of 636). Network entity 104 transmits a TCI indication (e.g., MAC-CE or DCI) 632 indicating at least one TCI state from the list of TCI states. UE 102 transmits an ACK 634 for TCI indication 632. UE 102 applies the beam corresponding to at least one TCI state based on the time of action following the ACK transmission. The 636 TCI state is applied based on the time of action following the ACK feedback 634 associated with the DCI format conveying the TCI state.

[0136] In some implementations, network entity 104 and UE 102 can determine the SSB / CSI-RS used for default beamforming based on network entity configuration. In one example, network entity 104 transmits an RRC reconfiguration 630, which configures or indicates the SSB / CSI-RS resource index for default beamforming among the identified SSB / CSI-RS resources. (See reference...) Figure 6In RRC reconfiguration 630, the network entity indicates the SSB / CSI-RS resource index x (e.g., SSB / CSI-RS resource index 1 associated with PRACH transmission 624A or SSB / CSI-RS resource index K associated with PRACH transmission 624B) used to determine the default beam. Network entity 104 can transmit configuration / indication via RRC reconfiguration, MAC-CE, or DCI. In one example, network entity 104 transmits configuration via RAR 626. In another example, network entity 104 transmits configuration / indication via DCI scheduling of the UL or DL ​​channel. Alternatively, network entity 104 and UE 102 determine the SSB / CSI-RS based on the location of the RAR (e.g., time-domain and frequency-domain location) or message 4 (Msg4) from network entity 104 in response to Msg3. The associated SSB / CSI-RS for each candidate location of Msg2 or Msg4 can be configured by network entity 104 or can be predefined. In one example, network entity 104 and UE 102 determine the SSB / CSI-RS based on the SSB / CSI-RS with Msg2 or Msg4 QCL.

[0137] In one example, UE 102 receives more than one TCI-State of dl-OrJointTCI- StateList After the initial higher-layer configuration, and before applying the indicated TCI state from the configured TCI state, UE 102 assumes that the DM-RS of the PDSCH and the DM-RS of the PDCCH, as well as the CSI-RS with the indicated TCI state, are quasi-co-located with the SS / PBCH block. UE 102 identifies the SS / PBCH block during the initial access procedure. If more than one SS / PBCH block is identified, the SS / PBCH block is selected by [the appropriate SS / PBCH block]. ssbIndexForDefaultBeam Configured SS / PBCH.

[0138] In another example, when UE 102 receives more than one TCI-State of dl-OrJointTCI- StateListFollowing higher-level configuration (as part of a reconfiguration with a synchronization procedure as described in [3GPP TS 38.331]), and before applying the indicated TCI state from the configured TCI state, UE 102 assumes that the DM-RS of the PDSCH and the DM-RS of the PDCCH, as well as the CSI-RS with the indicated TCI state, are quasi-co-located with the SS / PBCH block or CSI-RS resource. UE 102 identifies the SS / PBCH block or CSI-RS resource during the RA procedure initiated by the reconfiguration with a synchronization procedure as described in [3GPP TS 38.331]. If more than one SS / PBCH block or CSI-RS resource is identified, the resource selected by the DM-RS of the PDSCH and the CSI-RS with the synchronization procedure as described in [3GPP TS 38.331] is selected. ssbriCriForDefaultBeam Configured SS / PBCH blocks or CSI-RS resources.

[0139] Figure 7 Illustration 700 shows an example of default beam determination based on UE report according to an embodiment.

[0140] UE 102 transmits a PRACH (also known as Msg1 or RA preamble) associated with SSB / CSI-RS 1 724A and another PRACH (also known as Msg1 or RA preamble) associated with SSB / CSI-RS K 724B. In response to receiving Msg1, network entity 104 transmits an RA response (RAR) known as Msg2 726. UE 102 transmits PUSCH (Msg3) 728 using the beam associated with SSB / CSI-RS resource index x. Msg3 728 also indicates the default beam (based on SSB / CSI-RS x) that UE 102 will use prior to the action time of 736. Network entity 104 transmits an RRC reconfiguration 730 indicating a list of TCI states (configured TCI states). Network entity 104 transmits a TCI indication (e.g., MAC-CE or DCI) 732 for indicating at least one TCI state from a list of TCI states. UE 102 transmits an ACK 734 for the TCI indication 732. UE 102 applies a beam corresponding to at least one TCI state based on the time of action following the ACK transmission. 736 The TCI state is applied based on the time of action following the ACK feedback 734 associated with the DCI format conveying the TCI state.

[0141] In some implementations, network entity 104 and UE 102 determine the SSB / CSI-RS for default beam determination based on a UE report from UE 102. (See reference) Figure 7Network entity 104 and UE 102 determine the SSB / CSI-RS used for determining the default beam based on the UE report. In one example, UE 102 reports the SSB / CSI-RS resource index for default beam determination among the identified SSB / CSI-RS resources (e.g., SSB / CSI-RS resource index 1 associated with PRACH transmission 724A, SSB / CSI-RS resource index K associated with PRACH transmission 724B). In some implementations, UE 102 can transmit the report via RRC message 730, MAC CE, or uplink control information. In one example, UE 102 transmits the report via Msg3. In another example, UE 102 transmits the report via an RRC reconfiguration complete message. Alternatively, network entity 104 and UE 102 determine the SSB / CSI-RS based on the Msg3 location (time domain and / or frequency domain resources). The association between each Msg3 location and the SSB or CSI-RS can be configured by network entity 104 or can be predefined.

[0142] In one example, UE 102 receives more than one TCI-State of dl-OrJointTCI- StateList After the initial higher-layer configuration, and before applying the indicated TCI state from the configured TCI state, UE 102 assumes that the DM-RS of the PDSCH and the DM-RS of the PDCCH, as well as the CSI-RS with the indicated TCI state, are quasi-co-located with the SS / PBCH block. UE 102 identifies the SS / PBCH block during the initial access procedure. If more than one SS / PBCH block is identified, the SS / PBCH block reported by UE 102 is selected.

[0143] In another example, when UE 102 receives more than one TCI-State of dl-OrJointTCI- StateListFollowing higher-level configuration (as part of a reconfiguration with a synchronization procedure as described in [3GPP TS 38.331]), and before applying the indicated TCI state from the configured TCI state, UE 102 assumes that the DM-RS of the PDSCH and the DM-RS of the PDCCH, as well as the CSI-RS with the indicated TCI state, are quasi-co-located with the SS / PBCH block or CSI-RS resource. UE 102 identifies the SS / PBCH block or CSI-RS resource during the RA procedure initiated by the reconfiguration with a synchronization procedure as described in [3GPP TS 38.331]. If more than one SS / PBCH block or CSI-RS resource is identified, the SS / PBCH block or CSI-RS resource reported by the UE is selected.

[0144] In an embodiment, when more than one joint unified TCI state is configured in an initial RRC reconfiguration corresponding to an RA procedure that identifies more than one SSB / CSI-RS or an RRC reconfiguration with a synchronization procedure, UE 102 receives at least one DL channel based on one of the configured TCI states after UE 102 receives the RRC reconfiguration and before UE 102 applies the indicated TCI state or before UE 102 applies a UE-initiated beam or TCI state. In some implementations, the TCI state may be predefined, such as a first TCI state configured in a TCI state list or a first TCI state configured by network entity 104. In some other implementations, the TCI state may be a joint TCI state with the lowest TCI state ID configured in a TCI state list. In still other implementations, the TCI state may be the first activated TCI state. Network entity 104 may transmit the configuration via RRC reconfiguration or MAC CE or DCI. In one example, network entity 104 transmits the configuration via RAR. In another example, network entity 104 transmits configuration via DCI scheduling of UL or DL ​​channels.

[0145] Figure 8 Illustration 800 shows an example of default beam determination based on the time-domain position of MsgA or Msg3 PUSCH according to an embodiment.

[0146] refer to Figure 8After selecting the RA preamble based on SSB / CSI-RS measurements, UE 102 transmits an RS preamble called Message 1 (Msg1) on the PRACH. For example, UE 102 transmits a PRACH associated with SSB / CSI-RS 1 824A (also referred to as Msg1 or the RA preamble) and another PRACH associated with SSB / CSI-RS K 824B (also referred to as Msg1 or the RA preamble).

[0147] In response to receiving Msg1 824A and 824B, network entity 104 transmits a RA response (RAR) referred to as Msg2 826. UE 102 uses the beam associated with SSB / CSI-RS resource index 1 to transmit PUSCH (Msg3) 828A and uses the beam associated with SSB / CSI-RS resource index K to transmit another PUSCH (Msg3) 828B. In some implementations, UE 102 may use a similar technique when transmitting multiple MsgA PUSCHs for a two-step RA procedure. Network entity 104 transmits an RRC reconfiguration 830 indicating a list of TCI states (configured TCI states). Network entity 104 transmits a TCI indication (e.g., MAC-CE or DCI) 832 indicating at least one TCI state from the list of TCI states. UE 102 transmits an ACK 834 for TCI indication 832. UE 102 applies the beam corresponding to at least one TCI state based on the time of action following the ACK transmission. The 836 TCI state is applied based on the time of action following the ACK feedback 834 associated with the DCI format conveying the TCI state.

[0148] In some implementations, when more than one joint or uplink unified TCI state is configured in the initial RRC reconfiguration corresponding to an RA procedure with more than one UL TX spatial filter applied to the Msg3 PUSCH or MsgA PUSCH, or in an RRC reconfiguration with a synchronization procedure, after UE 102 receives the RRC reconfiguration and before UE 102 applies the indicated TCI state or before UE applies the UE-initiated beam or TCI state, UE 102 transmits at least one UL channel during the RA procedure based on one of the UL TX spatial filters used for the Msg3 PUSCH or MsgA PUSCH. In some implementations, the timing of the transmission of the Msg3 PUSCH or MsgA PUSCH for default beam determination can be predefined or configured by network entity 104 or reported by UE 102.

[0149] In some implementations, UE 102 can determine the default beam for the UL channel based on the time-domain position of Msg3 PUSCH or MsgA PUSCH (e.g., the first or last Msg3 PUSCH or MsgA PUSCH to start or end). Reference Figure 8 UE 102 determines the default beam for the UL channel based on the time-domain position of the last ending Msg3 PUSCH 828B. In other implementations, UE 102 determines the default beam for the UL channel based on the time-domain position of the first starting Msg3 PUSCH 828A.

[0150] In one example, UE 102 receives more than one TCI-State of dl-OrJointTCI- StateList or has more than one TCI-UL-State of ul-TCI-StateList After the initial higher-layer configuration, and before applying the indicated TCI state from the configured TCI state, UE 102 assumes that the UL TX spatial filters (if applicable) used for PUSCH and PUCCH based on dynamic granting and configuration granting, and for SRS using the indicated TCI state, are the same as the UL TX spatial filters used for PUSCH transmissions scheduled by RAR UL granting during the initial access procedure. If UE 102 uses more than one UL TX spatial filter to transmit PUSCH, the UL TX spatial filter that ends later for PUSCH is selected.

[0151] In another example, when UE 102 receives more than one TCI-State or more than one TCI-UL- State of dl-OrJointTCI-StateList Following higher-level configuration (as part of a reconfiguration with a synchronization procedure as described in [3GPP TS 38.331]) and before applying the indicated TCI state from the configured TCI state, UE 102 assumes that the UL TX spatial filters (if applicable) used for PUSCH and PUCCH based on dynamic granting and configuration granting, and for SRS for applying the indicated TCI state, are the same as those used for PUSCH transmissions scheduled by RAR UL granting during the RA procedure initiated by the reconfiguration with a synchronization procedure as described in [3GPP TS 38.331]. If UE 102 uses more than one UL TX spatial filter to transmit PUSCH, the UL TX spatial filter that ends later for PUSCH is selected.

[0152] Figure 9Illustration 900 shows an example of default beam determination based on network entity configuration according to an embodiment.

[0153] UE 102 transmits a PRACH (also known as Msg1 or RA preamble) associated with SSB / CSI-RS 1 924A, and another PRACH (also known as Msg1 or RA preamble) associated with SSB / CSI-RS K 924B. In response to receiving Msg1, network entity 104 transmits an RA response (RAR) known as Msg2 926. UE 102 uses the beam associated with SSB / CSI-RS resource index 1 to transmit PUSCH (Msg3) 928A, and uses the beam associated with SSB / CSI-RS resource index K to transmit another PUSCH (Msg3) 928B. In some implementations, UE 102 may use a similar technique when transmitting multiple MsgA PUSCHs for a two-step RA procedure.

[0154] Network entity 104 transmits an RRC reconfiguration 930 indicating a list of TCI states (configured TCI states). The RRC reconfiguration 930 also indicates a default beam based on SSB / CSI-RS x (therefore UE 102 uses this default beam for communication before the action time 936). Network entity 104 transmits a TCI indication (e.g., MAC-CE or DCI) 932 indicating at least one TCI state from the list of TCI states. UE 102 transmits an ACK 934 for the TCI indication 932. UE 102 applies the beam corresponding to at least one TCI state based on the action time following the ACK transmission. The TCI state is applied 936 based on the action time following the ACK feedback 934 associated with the DCI format conveying the TCI state.

[0155] In some implementations, network entity 104 and the UE determine the default beam based on a configuration from network entity 104. In one example, network entity 104 configures an SSB / CSI-RS resource index (e.g., 924A, 924B) for default beam determination within the SSB / CSI-RS resources associated with Msg3 or MsgA PUSCH. (See reference...) Figure 9Network entity 104 configures an SSB / CSI-RS resource index (e.g., 924A) associated with the Msg3 PUSCH (e.g., 928A) for determining the default beam. Network entity 104 can transmit configuration / instructions via RRC reconfiguration, MAC CE, or DCI. In one example, network entity 104 transmits configuration / instructions via RAR. In another example, network entity 104 transmits configuration via DCI scheduling of the UL or DL ​​channel. Figure 11 An example of default beam determination based on network entity configuration is shown.

[0156] In one example, when the UE receives more than one TCI-State of dl-OrJointTCI-StateList or has more than one TCI-UL-State of ul-TCI-StateList After the initial higher-level configuration, and before applying the indicated TCI state from the configured TCI state, UE 102 assumes that the UL TX spatial filters (if applicable) used for PUSCH and PUCCH based on dynamic granting and configuration granting, and for SRS using the indicated TCI state, are the same as the UL TX spatial filters used for PUSCH transmission scheduled by RAR UL granting during the initial access procedure. If UE 102 uses more than one UL TX spatial filter to transmit PUSCH, the filter selected is the one used with the TCI state indicated by the configuration. ssbIndexForDefaultBeam The UL TX spatial filter of the PUSCH associated with the configured SS / PBCH block.

[0157] In another example, when UE 102 receives more than one TCI-State or more than one TCI-UL- State of dl-OrJointTCI-StateList After a higher-level configuration (as part of a reconfiguration with a synchronization procedure as described in [3GPP TS 38.331]) and before applying the indicated TCI state from the configured TCI state, UE 102 assumes that the UL TX spatial filter (if applicable) used for PUSCH and PUCCH based on dynamic granting and configuration granting, and for SRS for applying the indicated TCI state, is the same as the UL TX spatial filter used for PUSCH transmission scheduled by RAR UL granting during the RA procedure initiated by the reconfiguration with a synchronization procedure as described in [3GPP TS 38.331]. If UE 102 uses more than one UL TX spatial filter to transmit PUSCH, the one selected is the one used with the same UL TX spatial filter as described in [3GPP TS 38.331]. ssbriCriForDefaultBeam The UL TX spatial filter of the PUSCH associated with the configured SS / PBCH block or CSI-RS resource.

[0158] Figure 10 Illustration 1000 shows an example of default beam determination based on UE report according to an embodiment.

[0159] refer to Figure 10 After selecting the RA preamble based on SSB / CSI-RS measurements, UE 102 transmits an RS preamble called Message 1 (Msg1) on the PRACH. For example, UE 102 transmits a PRACH associated with SSB / CSI-RS 1 1024A (also referred to as Msg1 or the RA preamble) and another PRACH associated with SSB / CSI-RS K 1024B (also referred to as Msg1 or the RA preamble).

[0160] In response to receiving Msg1 1024A and 1024B, network entity 104 transmits a RA response (RAR) referred to as Msg2 1026. UE 102 uses the beam associated with SSB / CSI-RS resource index 1 to transmit PUSCH (Msg3) 1028A, and uses the beam associated with SSB / CSI-RS resource index K to transmit another PUSCH (Msg3) 1028B. In some implementations, UE 102 may use a similar technique when transmitting multiple MsgA PUSCHs for a two-step RA procedure. Network entity 104 transmits a TCI indication (e.g., MAC-CE or DCI) 1032 indicating at least one TCI state from a list of TCI states. UE 102 transmits an ACK 1034 for TCI indication 1032. UE 102 applies the beam corresponding to at least one TCI state based on the time of action following the ACK transmission. The 1036 TCI state is applied based on the action time following the ACK feedback 1034 associated with the DCI format that conveys the TCI state.

[0161] Network entity 104 transmits RRC reconfiguration 1030A, and UE 102 transmits RRC reconfiguration complete 1030B. Network entity 104 transmits RRC reconfiguration 1030A indicating a list of TCI states (configured TCI states). RRC reconfiguration complete message 1030B includes a UE report (based on SSB / CSI-RS x for the default beam) about which default beam UE 102 will use.

[0162] In some implementations, network entity 104 and UE 102 can determine the default beam based on a UE report from UE 102. In one example, UE 102 reports the SSB / CSI-RS resource index (e.g., 1024A, 1024B) for default beam determination within the SSB / CSI-RS resources associated with MsgA or Msg3 PUSCH. UE 102 can transmit the UE report via RRC messages, MAC CE, or uplink control information. In one example, UE 102 transmits the UE report via an RRC reconfiguration complete message. (See reference) Figure 10 Network entity 104 and UE 102 determine the default beam based on the UE report transmitted via RRC reconfiguration after 1030B transmission.

[0163] In one example, UE 102 receives more than one TCI-State of dl-OrJointTCI- StateList or has more than one TCI-UL-State of ul-TCI-StateList After the initial higher-layer configuration, and before applying the indicated TCI state from the configured TCI state, UE 102 assumes that the UL TX spatial filters (if applicable) used for PUSCH and PUCCH based on dynamic granting and configuration granting, and for SRS using the indicated TCI state, are the same as the UL TX spatial filters used for PUSCH transmission scheduled by RAR UL granting during the initial access procedure. If UE 102 uses more than one UL TX spatial filter to transmit PUSCH, the UL TX spatial filter selected is the one associated with the PUSCH block reported by the UE.

[0164] In another example, when the UE receives more than one TCI-State or more than one TCI-UL-State of dl-OrJointTCI-StateListFollowing higher-level configuration (as part of a reconfiguration with a synchronization procedure as described in [3GPP TS 38.331]) and before applying the indicated TCI state from the configured TCI state, UE 102 assumes that the UL TX spatial filters (if applicable) used for PUSCH and PUCCH based on dynamic granting and configuration granting, and for SRS for applying the indicated TCI state, are the same as those used for PUSCH transmissions scheduled by RAR UL granting during the RA procedure initiated by the reconfiguration with a synchronization procedure as described in [3GPP TS 38.331]. If UE 102 uses more than one UL TX spatial filter to transmit PUSCH, the UL TX spatial filter selected is the one associated with the PUSCH in the SS / PBCH block or CSI-RS resource reported by the UE.

[0165] In some implementations, network entity 104 and UE 102 may determine the default beam based on the SSB / CSI-RS identified by the UE during the RA procedure. Network entity 104 and UE 102 may determine the SSB / CSI-RS based on at least one of the following: SSB / CSI-RS resource index; the time-domain location of the SSB / CSI-RS; and whether the SSB / CSI-RS is used by UE 102 for time and frequency synchronization.

[0166] In an embodiment, when more than one joint or uplink unified TCI state is configured in an initial RRC reconfiguration corresponding to an RA procedure with more than one Msg3PUSCH or MsgA PUSCH having applied more than one UL TX spatial filter, or an RRC reconfiguration with a synchronization procedure, after the UE receives the RRC reconfiguration and before the UE applies the indicated TCI state, or before the UE 102 applies a UE-initiated beam or TCI state, the UE 102 transmits at least one UL channel based on one of the configured TCI states. The TCI state can be predefined, such as a first TCI state configured in a TCI state list, or a first TCI state configured by network entity 104. In other cases, the TCI state can be a joint TCI state or uplink TCI state configured in a TCI state list with the lowest TCI state ID. In still other cases, the TCI state can be the first activated TCI state. Network entity 104 can transmit the configuration via RRC reconfiguration or MAC CE or DCI. In one example, network entity 104 transmits configuration via RAR. In another example, network entity 104 transmits configuration via DCI scheduling of UL or DL ​​channels.

[0167] In an embodiment, if network entity 104 is not configured with a PL-RS for PUCCH or PUSCH, and network entity 104 disables the default beam / PL-RS, for example, if network entity 104 does not provide... enableDefaultBeamPL-ForPUCCH and enableDefaultBeamPL-for RS Then UE 102 determines path loss based on the SSB of the MIB used for PCell decoded by UE 102 or the SSB used by UE 102 to obtain time and frequency synchronization for SCell.

[0168] In the example, for PUCCH, if UE 102 is not provided... pathlossReferenceRS and enableDefaultBeamPL-ForPUCCH Or, before UE 102 is provided with dedicated higher-layer parameters, UE 102 Used from UE 102 to obtain MIB The path loss is calculated by obtaining RS resources from SS / PBCH blocks with the same SS / PBCH block index as the SS / PBCH block index, or by using UE 102 to obtain SS / PBCH blocks for time and frequency synchronization of SCell.

[0169] In another example, for SRS, if UE 102 is not provided pathlossReferenceRS or SRS- PathlossReferenceRS-Id and enableDefaultBeamPL-ForSRS Or, before the UE is provided with dedicated higher-layer parameters, UE 102 Used from UE 102 to obtain MIB The path loss is calculated by using the RS resources obtained from the SS / PBCH block index of the same SS / PBCH block index, or by using the SS / PBCH block obtained by the UE for time and frequency synchronization of the SCell.

[0170] In the example, for PUCCH, if UE 102 is not provided... pathlossReferenceRS and enableDefaultBeamPL-ForPUCCH And if the UE reports support for the default path loss RS used for PUCCH, then the UE Used from UE 102 to obtain MIB The path loss is calculated by obtaining RS resources from SS / PBCH blocks with the same SS / PBCH block index as the SS / PBCH block index, or by using UE 102 to obtain SS / PBCH blocks for time and frequency synchronization of SCell.

[0171] In another example, for SRS, if UE 102 is not provided pathlossReferenceRS or SRS- PathlossReferenceRS-Id and enableDefaultBeamPL-ForSRS And if the UE reports support for the default path loss RS used for SRS, UE 102 Use from the UE to obtain MIB The path loss is calculated by using the RS resources obtained from the SS / PBCH block index of the same SS / PBCH block index, or by using the SS / PBCH block obtained by the UE for time and frequency synchronization of the SCell.

[0172] Figure 11 A flowchart 1100 illustrating a wireless communication method at the UE is shown. (Reference) Figures 1 to 10 This method can be executed by UE 102.

[0173] In an embodiment, UE 102 receives control signaling from network entity 104 1104 configuring at least one RA procedure from multiple RA procedures and configuring a list of TCI states. In some implementations, the control signaling may include a first RRC message for configuring the RA procedure and a second RRC message for configuring the list of TCI states. In some other implementations, the control signaling may include a single RRC message. In some implementations, at least one RA procedure includes a 2-step RA procedure. Multiple RA procedures include 2-step RA procedures and 4-step RA procedures. For example, refer to... Figure 3 UE 102 receives control signaling 304 for RRC reconfiguration. In some implementations, UE 102 may perform the RA procedure configured in the control signaling together with network entity 104.

[0174] In an embodiment, prior to activation of at least one TCI state from a list of TCI states or a UE-initiated beam, UE 102 communicates with network entity (104) 1110 using at least one of a default beam or a default path loss reference signal (PL-RS), which is based on at least one of 1106: quasi-co-location (QCL) parameters for a first downlink reference signal, or an uplink spatial transmission filter associated with at least one RA procedure and a path loss associated with a second downlink reference signal. For example, reference Figure 3The UE communicates with network entity 104 310 on at least one DL channel based on a default beam or at least one UL channel based on a default beam and a default PL-RS in PCell and / or SCell, the default beam and default PL-RS being based on at least one of the following 306: an SSB for decoding MIB, an SSB / CSI-RS identified during RA procedure, an SSB for time / frequency acquisition, a beam for Msg3 or MsgA PUSCH, a DL RS in a TCI for at least one CORESET, or a TCI state from a configured TCI state list.

[0175] In this embodiment, UE 102 can switch from a default beam switch 1108 to a UE-initiated beam or a TCI state indicated by network entity 104. For example, refer to Figure 3 UE 102 switches from the default beam switch 308 to a beam switch initiated by the TCI indication from network entity 104 or by the UE.

[0176] In an embodiment, UE 102 may communicate with network entity 104 based on a UE-initiated beam or an indicated TCI state. For example, refer to... Figure 3 UE 102 communicates with network entity 104 using at least one DL channel or at least one UL channel based on a beam indicated by network entity 104 or initiated by UE 102 310.

[0177] Figure 11 A method executed from the UE side of the wireless communication link is described, and Figure 12 A method for execution from the network side of a wireless communication link is described.

[0178] Figure 12 This is a flowchart 1200 showing a method for wireless communication at a network entity. (Reference) Figures 1 to 10 The method can be performed by one or more network entities 104, which may correspond to a base station or a unit of a base station, such as RU 106, DU 108 and / or CU 110.

[0179] In an embodiment, network entity 104 transmits control signaling to UE 102 1204 to configure at least one RA procedure from multiple RA procedures and to configure a list of TCI states. In some implementations, the control signaling may include a first RRC message for configuring the RA procedure and a second RRC message for configuring the list of TCI states. In some other implementations, the control signaling may include a single RRC message. In some implementations, at least one RA procedure includes a 2-step RA procedure. Multiple RA procedures include 2-step RA procedures and 4-step RA procedures. For example, refer to... Figure 3 Network entity 104 transmits control signaling 304 for RRC reconfiguration. In some implementations, network entity 104 may perform the RA procedure configured in the control signaling together with UE 102.

[0180] In an embodiment, prior to activation of at least one TCI state from a list of TCI states or a UE-initiated beam, network entity 104 communicates with UE 102 1206 using at least one of a default beam or a default path loss reference signal (PL-RS), which is based on at least one of: quasi-co-location (QCL) parameters for a first downlink reference signal, or an uplink spatial transmission filter associated with at least one RA procedure and a path loss associated with a second downlink reference signal. For example, reference Figure 3 Network entity 104 communicates with UE 102 310 on at least one DL channel based on a default beam or at least one UL channel based on a default beam and a default PL-RS in PCell and / or SCell, wherein the default beam or the default PL-RS is based on at least one of the following 306: an SSB for decoding MIB, an SSB / CSI-RS identified during RA procedure, an SSB for time / frequency acquisition, a beam for Msg3 or MsgA PUSCH, a DL RS in a TCI for at least one CORESET, or a TCI state from a configured TCI state list.

[0181] In an embodiment, network entity 104 can switch from a default beam switch 1208 to a beam initiated by the UE or a TCI state indicated by network entity 104. For example, refer to Figure 3 Network entity 104 switches from default beam switching 308 to beam switching initiated by TCI indication from network entity 104 or UE.

[0182] In an embodiment, network entity 104 may communicate with UE 102 1210 based on a beam initiated by the UE or an indicated TCI state. For example, refer to Figure 3 Network entity 104 communicates with UE 102 using at least one DL channel or at least one UL channel based on a beam indicated by network entity 104 or initiated by UE 102.

[0183] like Figure 13 As described herein, UE device 1302 can execute the method of flowchart 1100. For example... Figure 14 As described in the document, one or more network entities 104 can execute the methods of flowchart 1200.

[0184] Figure 13 Illustration 1300 illustrates an example of a hardware implementation of UE device 1302. UE device 1302 may be UE 102, a component of UE 102, or may implement UE functions. UE device 1302 may include application processor 1306, which may have on-chip memory 1306'. In the example, application processor 1306 may be coupled to secure digital (SD) card 1308 and / or display 1310. Application processor 1306 may also be coupled to sensor module 1312, power supply 1314, additional memory module 1316, camera 1318, and / or other related components.

[0185] UE device 1302 may further include a wireless baseband processor 1326, which may be referred to as a modem. The wireless baseband processor 1326 may have on-chip memory 1326'. Together with and similarly to application processor 1306, wireless baseband processor 1326 may also be coupled to sensor module 1312, power supply 1314, additional memory module 1316, camera 1318, and / or other related components. Wireless baseband processor 1326 may additionally be coupled to one or more subscriber identity module (SIM) cards 1320 and / or one or more transceivers 1330 (e.g., wireless RF transceivers).

[0186] Within one or more transceivers 1330, the UE device 1302 may include a Bluetooth module 1332, a WLAN module 1334, an SPS module 1336 (e.g., a GNSS module), and / or a cellular module 1338. The Bluetooth module 1332, WLAN module 1334, SPS module 1336, and cellular module 1338 may each include an on-chip transceiver (TRX), or in some cases, only a transmitter (TX) or only a receiver (RX). The Bluetooth module 1332, WLAN module 1334, SPS module 1336, and cellular module 1338 may each include a dedicated antenna and / or utilize antenna 1340 to communicate with one or more other nodes. For example, UE device 1302 can communicate with another UE (e.g., sidelink communication) and / or with network entity 104 (e.g., uplink / downlink communication) via transceiver 1330 and antenna 1340, where network entity 104 may correspond to a base station or a unit of a base station, such as RU 106, DU 108 or CU 110.

[0187] The wireless baseband processor 1326 and application processor 1306 may each include computer-readable media / memory 1326' and 1306', respectively. An additional memory module 1316 may also be considered a computer-readable media / memory. Each computer-readable media / memory 1326', 1306', and 1316 may be non-transitory. The wireless baseband processor 1326 and application processor 1306 may each be responsible for general processing, including executing software stored on the computer-readable media / memory 1326', 1306', and 1316. When executed by the wireless baseband processor 1326 / application processor 1306, this software causes the wireless baseband processor 1326 / application processor 1306 to perform the various functions described herein. The computer-readable media / memory may also be used to store data manipulated by the wireless baseband processor 1326 / application processor 1306 during software execution. The wireless baseband processor 1326 / application processor 1306 may be a component of UE 102. UE device 1302 may be a processor chip (e.g., a modem and / or an application) and includes only the wireless baseband processor 1326 and / or the application processor 1306. In other examples, UE device 1302 may be the entire UE 102 and may include additional modules for device 1302.

[0188] like Figure 1 The discussion and about Figure 11 Implemented, the UE default beam management component 140 is configured to receive control signaling from a network entity to configure at least one RA procedure from a plurality of RA procedures and to configure a list of TCI states; prior to the activation of at least one TCI state from the list of TCI states or a UE-initiated beam, the UE communicates with the network entity using at least one of a default beam or a default PL-RS, the default beam or the default PL-RS being based on at least one of: QCL parameters for a first downlink reference signal, or an uplink spatial transmission filter associated with at least one RA procedure and a path loss associated with a second downlink reference signal.

[0189] The UE default beam management component 140 may be located within the application processor 1306 (e.g., at 140a), within the wireless baseband processor 1326 (e.g., at 140b), or within both the application processor 1306 and the wireless baseband processor 1326. The UE default beam management components 140a to 140b may be one or more hardware components specifically configured to perform the stated procedures / algorithms, implemented by one or more processors configured to perform the stated procedures / algorithms, stored in a computer-readable medium for implementation by one or more processors, or a combination thereof.

[0190] Figure 14Illustration 1400 illustrates an example of a hardware implementation of one or more network entities 104. The one or more network entities 104 may be a base station, a component of a base station, or may implement base station functions. The one or more network entities 104 may include or correspond to at least one of RU 106, DU 108, or CU 110. CU 110 may include a CU processor 1446, which may have on-chip memory 1446'. In some aspects, CU 110 may further include an additional memory module 1456 and / or a communication interface 1448, both of which may be coupled to the CU processor 1446. CU 110 may communicate with DU 108 via a midhaul link 162 (such as an F1 interface between the communication interface 1448 of CU 110 and the communication interface 1428 of DU 108).

[0191] DU 108 may include a DU processor 1426, which may have on-chip memory 1426'. In some aspects, DU 108 may further include an additional memory module 1436 and / or a communication interface 1428, both of which may be coupled to the DU processor 1426. DU 108 may communicate with RU 106 via a frontlink 160 between DU 108's communication interface 1428 and RU 106's communication interface 1408.

[0192] RU 106 may include an RU processor 1406, which may have on-chip memory 1406'. In some aspects, RU 106 may further include an additional memory module 1416, a communication interface 1408, and one or more transceivers 1430, all of which may be coupled to the RU processor 1406. RU 106 may further include an antenna 1440, which may be coupled to one or more transceivers 1430, such that RU 106 can communicate with UE 102 via the antenna 1440 through one or more transceivers 1430.

[0193] On-chip memories 1406', 1426', 1446' and additional memory modules 1416, 1436, 1456 can each be considered as computer-readable media / memory. Each computer-readable medium / memory can be non-transitory. Each of processors 1406, 1426, 1446 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor 1406, 1426, 1446, the software causes the processor 1406, 1426, 1446 to perform the various functions described herein. The computer-readable medium / memory can also be used to store data manipulated by the processors 1406, 1426, 1446 during software execution. In the example, the NE default beam management component 150 can be located at any of one or more network entities 104, such as at CU 110; at both CU 110 and DU 108; at each of CU 110, DU 108 and RU 106; at DU 108; at both DU 108 and RU 106; or at RU 106.

[0194] like Figure 1 The discussion and about Figure 12 Implemented, the NE default beam management component 150 is configured to transmit control signaling to the UE to configure at least one RA procedure from a plurality of RA procedures and configure a list of TCI states; prior to the activation of at least one TCI state from the list of TCI states or the UE-initiated beam, at least one of a default beam or a default PL-RS is used to communicate with the UE, the default beam or default PL-RS being based on at least one of: QCL parameters for a first downlink reference signal, or an uplink spatial transmission filter associated with at least one RA procedure and a path loss associated with a second downlink reference signal.

[0195] The NE default beam management component 150 may reside within one or more processors of one or more network entities 104, such as within the RU processor 1406 (e.g., at 150a), within the DU processor 1426 (e.g., at 150b), and / or within the CU processor 1446 (e.g., at 150c). The NE default beam management components 150a-150c may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors 1406, 1426, 1446 configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors 1406, 1426, 1446, or a combination thereof.

[0196] The specific order or hierarchy of the boxes in the processes and flowcharts disclosed herein is an illustration of the exemplary methods. Therefore, the specific order or hierarchy of the boxes in the processes and flowcharts can be rearranged. Some boxes can also be combined or deleted. Dashed lines may indicate optional elements in the illustrations. The appended method claims present the elements of each box in the exemplary order and are not limited to the specific order or hierarchy presented in the claims, processes, and flowcharts.

[0197] The detailed descriptions presented herein, in conjunction with accompanying drawings, illustrate various configurations and do not represent the only configuration in which the concepts described herein can be practiced. These detailed descriptions include specific details used to provide a comprehensive explanation of the various concepts. However, these concepts can be practiced without using these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0198] Various aspects of wireless communication systems (such as telecommunications systems) are presented with reference to various devices and methods. These devices and methods are described in the following detailed description and are shown in the accompanying drawings by various boxes, components, circuits, processes, call flows, systems, algorithms, etc. (collectively, "elements"). These elements can be implemented using electronic hardware, computer software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and design constraints imposed on the system as a whole.

[0199] An element, or any part of an element, or any combination of elements, can be implemented as a “processing system” including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other similar hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in a processing system can execute software, which may be referred to as software, firmware, middleware, microcode, hardware description languages, or others. Software should be interpreted broadly as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

[0200] If the functionality described herein is implemented in software, then such functionality may be stored on or encoded as one or more instructions or code on a computer-readable medium, such as a non-transitory computer-readable storage medium. Computer-readable media include computer storage media and may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures accessible by a computer. The storage medium can be any available medium accessible to a computer.

[0201] The aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, form factors, sizes, and package arrangements. For example, aspects, implementations, and / or use cases can be generated via integrated chip implementations and other devices based on non-modular components, such as end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / procurement devices, medical devices, devices supporting artificial intelligence (AI), devices supporting machine learning (ML), etc. The scope of aspects, implementations, and / or use cases can range from chip-level or modular components to non-modular or non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies described herein.

[0202] Apparatus incorporating the aspects and features described herein may also include additional components and features for implementing and practicing the claimed and described aspects and features. For example, the transmission and reception of wireless signals necessarily include numerous components for analog and digital purposes, such as hardware components, antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc. The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or decomposed components, end-user devices, etc., in various configurations.

[0203] The description herein is provided to enable those skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the aspects described herein, but should be interpreted in light of the full scope of this disclosure consistent with the language of the claims.

[0204] Unless explicitly stated otherwise, references to singular elements do not imply "one and only one," but rather "one or more." Terms such as "if," "when," and "at" do not imply an immediate temporal relationship or response. That is, these phrases (e.g., "when") do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that an action will occur if a certain condition is met, without requiring a specific or immediate temporal constraint on the occurrence of the action. The terms "may," "may," and "can" as used in this disclosure generally carry certain connotations. For example, "may" refers to a permissible feature that may or may not occur, "may" refers to a feature that is likely to occur, and "can" refers to a capability (e.g., being able to). The phrase "for example" generally carries a similar connotation to "may," and therefore, "may" is sometimes excluded from sentences that include "for example" or other similar phrases.

[0205] Unless otherwise expressly stated, the term "some" means one or more. Combinations such as "at least one of A, B, or C" or "one or more of A, B, or C" include any combination of A, B, and / or C, such as A and B, A and C, B and C, or A and B and C, and may include multiple A, multiple B, and / or multiple C, or may include only A, only B, or only C. A set should be interpreted as a set of elements having a number of one or more elements. Terms or articles such as "a," "an," and / or "the / said" may refer to one of the items, features, elements, etc., following that term or article, or may refer to more than one of the items, features, elements, etc., following that term or article. For example, the expression "a small component" does not exclude references to a plurality of said components, because "a plurality of components" necessarily includes "a small component." Therefore, the expression "a small component" can be interpreted as "at least one small component," or similarly, as "one or more components."

[0206] Unless otherwise explicitly indicated, ordinal terms such as “first” and “second” do not necessarily imply order in time, sequence, numerical value, etc., but are used to distinguish different instances of the term or phrase that follows each ordinal term.

[0207] As used in the specification and drawings, reference numerals are sometimes cross-referenced across drawings to indicate the same or similar features. Features that are identical in multiple drawings may be labeled with the same reference numerals in multiple drawings. Features that are similar but not identical across multiple drawings may be labeled with reference numerals that have different leading numerals but share one or more of the same trailing numerals (e.g., 206, 306, 406, etc. may refer to similar features in the drawings). Therefore, the same numerals may refer to the same action.

[0208] Structural and functional equivalents of elements of all aspects described throughout this disclosure, known or subsequently learned by those skilled in the art, are expressly incorporated herein by reference and are covered by the claims. The terms “module,” “mechanism,” “element,” “device,” etc., may not be substitutes for the term “component.” Therefore, no claim element shall be construed as means plus function unless explicitly stated using the phrase “component for…”. As used herein, the phrase “based on” should not be construed as a reference to a closed set of information, one or more conditions, one or more factors, etc. In other words, unless expressly stated otherwise, the phrase “based on A” (where “A” can be information, conditions, factors, etc.) shall be construed as “at least based on A”.

[0209] The following examples are illustrative only and may be combined with other examples or teachings described herein without limitation.

[0210] Example 1 is a method for wireless communication at a UE, comprising: receiving control signaling from a network entity configuring at least one RA procedure from a plurality of RA procedures and configuring a list of TCI states; and communicating with the network entity using at least one of a default beam or a default PL-RS prior to activation of at least one TCI state from the list of TCI states or a UE-initiated beam, the default beam or the default PL-RS being based on at least one of the following: QCL parameters used for the first downlink reference signal, or The uplink spatial transmission filter associated with the at least one RA process and the path loss associated with the second downlink reference signal.

[0211] Example 2 can be combined with Example 1, and further includes: at least one RA process is a 2-step RA process, and further includes: the communication using the default beam is based on at least one of the following: MsgA PUSCH, MsgA PRACH, at least one TCI state from the list of TCI states, an SSB or CSI-RS associated with the at least one RA procedure, or a configuration for the default beam.

[0212] Example 3 can be combined with Example 1 and further includes: the default beam is used for SCell, and wherein the communication using the default beam is based on at least one of the following: a first SSB for time and frequency synchronization, a second SSB for the at least one TCI state from the list of TCI states, or a configuration for the default beam.

[0213] Example 4 can be combined with Example 1 and further includes: the default beam is a default beam that supports the network, and wherein the communication using the default beam is based on the default beam, which is at least one of the following: activated by the network entity or indicated by the network entity during the at least one RA process.

[0214] Example 5 can be combined with Example 1 and further includes the control signaling indication mTRP, wherein the default beam is included in a plurality of default beams associated with a plurality of TCI states.

[0215] Example 6 can be combined with Example 1 and further includes: the at least RA procedure is associated with multiple SSB or CSI-RS resources, and wherein the communication using the default beam is based on at least one of: an SSB or CSI-RS resource index, the time-domain location of the SSB or CSI-RS, the control signaling, a UE report to the SSB or CSI-RS, or the at least one TCI state from a list of TCI states.

[0216] Example 7 can be combined with Example 1 and further includes: the at least RA procedure includes multiple beams associated with MsgA or Msg3, and wherein the communication using the default beam is based on at least one of the following: the time-domain location of MsgA PUSCH or Msg3 PUSCH, the control signaling, the UE report to SSB or CSI-RS, the SSB or CSI-RS and a predefined protocol, or the at least one TCI state from the list of TCI states.

[0217] Example 8 can be combined with Example 1 and further includes: the control signaling omits the configuration for the default PL-RS and at least one of the following: disabling the default beam or the default PL-RS, based on the path loss of the SSB used for decoding the MIB or acquiring time and frequency synchronization.

[0218] Example 9 may be combined with any of Examples 1 to 8, and further includes: switching from the default beam (308) to a beam initiated by the UE or a TCI state indicated by the network entity.

[0219] Example 10 is a method for wireless communication at a network entity, comprising: transmitting to a UE control signaling that configures at least one RA procedure from a plurality of RA procedures and a list of TCI states; and communicating with the UE using at least one of a default beam or a default PL-RS prior to activation of at least one TCI state from the list of TCI states or a beam initiated by the UE, the default beam or the default PL-RS being based on at least one of: QCL parameters for a first downlink reference signal, or an uplink spatial transmission filter associated with the at least one RA procedure and a path loss associated with a second downlink reference signal.

[0220] Example 11 can be combined with Example 10 and further includes: at least one RA process is a 2-step RA process, and further includes: the communication using the default beam is based on at least one of: MsgA PUSCH, MsgA PRACH, the at least one TCI state from the list of TCI states, The SSB or CSI-RS associated with the at least one RA procedure, or the configuration for the default beam.

[0221] Example 12 may be combined with Example 10 and further includes: the default beam is used for SCell, and wherein the communication using the default beam is based on at least one of the following: a first SSB for time and frequency synchronization, a second SSB for the at least one TCI state from the list of TCI states, or a configuration for the default beam.

[0222] Example 13 can be combined with Example 10 and further includes: the default beam is a default beam supporting the network, and wherein the communication using the default beam is based on the default beam, which is at least one of the following: activated by the network entity or indicated by the network entity during the at least one RA process.

[0223] Example 14 can be combined with Example 10 and further includes: the control signaling instructs mTRP, and wherein the default beam is included in a plurality of default beams associated with a plurality of TCI states.

[0224] Example 15 can be combined with Example 10 and further includes the control signaling indication mTRP, and further includes excluding the default beam from among the multiple default beams associated with multiple TCI states.

[0225] Example 16 can be combined with Example 10 and further includes: the at least RA procedure is associated with multiple SSB or CSI-RS resources, and wherein the communication using the default beam is based on at least one of: an SSB or CSI-RS resource index, the time-domain location of the SSB or CSI-RS, the control signaling, a UE report to the SSB or CSI-RS, or the at least one TCI state from a list of TCI states.

[0226] Example 17 can be combined with Example 10 and further includes: the at least RA procedure includes multiple beams associated with MsgA or Msg3, and wherein the communication using the default beam is based on at least one of the following: the time-domain location of MsgA PUSCH or Msg3 PUSCH, the control signaling, the UE report to SSB or CSI-RS, the SSB or CSI-RS and a predefined protocol, or the at least one TCI state from the list of TCI states.

[0227] Example 18 can be combined with Example 10 and further includes: the control signaling omits the configuration for the default PL-RS and includes at least one of the following: disabling the default beam or the default PL-RS, and the path loss being based on the SSB used for decoding the MIB or obtaining time and frequency synchronization.

[0228] Example 20 may be combined with any of Examples 10 to 18, and further includes: switching from the default beam to a beam initiated by the UE or a TCI state indicated by the network entity.

[0229] Example 21 is a device for implementing wireless communication as described in any one of Examples 1 to 20.

[0230] Example 22 is a device for wireless communication, including components for implementing the method as described in any one of Examples 1 to 20.

[0231] Example 23 is a non-transitory computer-readable medium storing computer-executable code that, when executed by a processor, causes the processor to perform the method as described in any one of Examples 1 to 20.

Claims

1. A method for wireless communication at a user equipment (UE) (102), comprising: Receive (304) control signaling from network entity (104) to configure at least one RA procedure from a plurality of random access RA procedures and to configure a list of Transmission Configuration Indicator (TCI) states; as well as Before activation of at least one TCI state from the list of TCI states or a UE-initiated beam, communication (306) is conducted with the network entity (104) using at least one of a default beam or a default path loss reference signal PL-RS, wherein the default beam or the default path loss reference signal PL-RS is based on at least one of the following: Quasi-co-address QCL parameters used for the first downlink reference signal, or The uplink spatial transmission filter associated with the at least one RA process and the path loss associated with the second downlink reference signal.

2. The method as described in claim 1, wherein, The at least one RA process is a two-step RA process, and wherein the communication (306) using the default beam is based on at least one of the following: Message A MsgA Physical Uplink Shared Channel (PUSCH). MsgA Physical Random Access Channel (PRACH) The at least one TCI state from the list of TCI states, The synchronization signal block SSB or channel state information reference signal CSI-RS associated with the at least one RA process, or Configuration for the default beam.

3. The method as described in claim 1, wherein, The default beam is used for the secondary cell SCell, and the communication (306) using the default beam is based on at least one of the following: The first synchronization signal block SSB used for time and frequency synchronization A second SSB for the at least one TCI state from the list of TCI states, or Configuration for the default beam.

4. The method of claim 1, wherein, The default beam is a default beam that supports the network, and the communication (306) performed using the default beam is based on the default beam, which is at least one of the following: Activated by the network entity (104), or Instructed by the network entity (104) during the at least one RA process.

5. The method of claim 1, wherein, The control signaling indicates multiple Transmitter Receiver Points (mTRPs), and the default beam is included in multiple default beams associated with multiple TCI states.

6. The method of claim 1, wherein, The at least RA process is associated with multiple synchronization signal blocks (SSBs) or channel state information reference signals (CSI-RS) resources, and wherein the communication (306) using the default beam is based on at least one of the following: SSB or CSI-RS resource index The time-domain location of the SSB or CSI-RS, The control signaling. UE reports to the SSB or CSI-RS, or The at least one TCI state from the list of TCI states.

7. The method of claim 1, wherein, The at least RA process includes multiple beams associated with MsgA or message 3 Msg3, and wherein the communication (306) using the default beam is based on at least one of the following: The time-domain location of MsgA physical uplink shared channel PUSCH or Msg3 PUSCH. The control signaling. UE reports on synchronization signal block (SSB) or channel state information reference signal (CSI-RS) The SSB or CSI-RS and predefined protocols, or The at least one TCI state from the list of TCI states.

8. The method of claim 1, wherein, The control signaling omits the configuration for the default PL-RS, and at least one of the following: disabling the default beam or the default PL-RS, and path loss based on the synchronization signal block SSB used for decoding the master information block (MIB) or acquiring time and frequency synchronization.

9. The method of any one of claims 1 to 8, further comprising: From the default beam switch (308) to the beam initiated by the UE or the TCI state indicated by the network entity (104).

10. A method for wireless communication at a network entity (104), comprising: Transmit (304) control signaling to the user equipment (UE) (102) to configure at least one RA procedure from a plurality of random access RA procedures and configure a list of transmission configuration indicator TCI states; as well as Before activation of at least one TCI state from the list of TCI states or before a UE-initiated beam, communication (306) is made with the UE (102) using at least one of a default beam or a default path loss reference signal PL-RS, the default beam or the default path loss reference signal PL-RS being based on at least one of the following: Quasi-co-address QCL parameters used for the first downlink reference signal, or The uplink spatial transmission filter associated with the at least one RA process and the path loss associated with the second downlink reference signal.

11. The method of claim 10, wherein, The at least one RA process is a two-step RA process, and wherein the communication (306) using the default beam is based on at least one of the following: Message A MsgA Physical Uplink Shared Channel (PUSCH). MsgA Physical Random Access Channel (PRACH) The at least one TCI state from the list of TCI states, The synchronization signal block SSB or channel state information reference signal CSI-RS associated with the at least one RA process, or Configuration for the default beam.

12. The method of claim 10, wherein, The default beam is for the secondary cell SCell, and the communication (306) using the default beam is based on at least one of the following: The first synchronization signal block SSB used for time and frequency synchronization A second SSB for the at least one TCI state from the list of TCI states, or Configuration for the default beam.

13. The method of claim 10, wherein, The at least one RA process is associated with a plurality of Synchronization Signal Blocks (SSBs) or Channel State Information Reference Signals (CSI-RS) resources, and wherein the communication (306) using the default beam is based on at least one of the following: SSB or CSI-RS resource index The time-domain location of the SSB or CSI-RS, The control signaling. UE reports to the SSB or CSI-RS, or The at least one TCI state from the list of TCI states.

14. The method of claim 10, wherein, The control signaling omits the configuration for the default PL-RS, and at least one of the following: disabling the default beam or the default PL-RS, and path loss based on the synchronization signal block SSB used for decoding the master information block (MIB) or acquiring time and frequency synchronization.

15. An apparatus for wireless communication, the apparatus comprising a memory, a transceiver, and a processor, the processor being coupled to the memory and the transceiver, the apparatus being configured to implement the method as claimed in any one of claims 1 to 14.

Images