Method and apparatus for ta adjustments under asymmetric DL STRP and UL MTRP scenarios

Abstract

A method performed by a UE under asymmetric DL sTRP and UL mTRP scenarios is provided. The method when at least one TCI state is associated with PL offset and DCI indicates first index, transmits PRACH using first TCI state associated with PL offset, receives RAR by assuming first DM-RS antenna ports of RAR being quasi co-located with second DM-RS antenna ports of PDCCHs, transmits PUSCH based on first TCI state, and receives PDSCH by assuming third DM-RS antenna ports of PDSCH being quasi co-located with second DM-RS antenna ports. The method when DCI indicates second index, transmits PRACH based on second TCI state not associated with PL offset, receives RAR by assuming first DM-RS antenna ports being quasi co-located with second DM-RS antenna ports, transmits PUSCH based on second TCI state, and receives PDSCH by assuming third DM-RS antenna ports being quasi co-located with second DM-RS antenna ports.

Description

METHOD AND APPARATUS FOR TA ADJUSTMENTS UNDER ASYMMETRIC DL STRP AND UL MTRP SCENARIOS

[0001] The present disclosure is related to wireless communication and, more specifically, to a User Equipment (UE), Base Station (BS), and method for timing advance (TA) adjustments under asymmetric downlink (DL) single transmission and reception point (sTRP) and uplink (UL) multiple transmission and reception point (mTRP) scenarios in the wireless communication networks.

[0002] Various efforts have been made to improve different aspects of wireless communication for the cellular wireless communication systems, such as the 5thGeneration (5G) New Radio (NR), by improving data rate, latency, reliability, and mobility. The 5G NR system is designed to provide flexibility and configurability to optimize network services and types, accommodating various use cases, such as enhanced Mobile Broadband (eMBB), massive Machine-Type Communication (mMTC), and Ultra-Reliable and Low-Latency Communication (URLLC). As the demand for radio access continues to grow, however, there exists a need for further improvements in the next-generation wireless communication systems, such as improvements in a beam management procedure.

[0003] The present disclosure is related to a UE, a BS, and a method for TA adjustments under asymmetric DL sTRP and UL mTRP scenarios in the wireless communication networks.

[0004] In a first aspect of the present disclosure, a UE for TA adjustments under asymmetric DL sTRP and UL mTRP scenarios is provided. The UE includes at least one processor and at least one non-transitory computer-readable medium that is coupled to the at least one processor and that stores one or more computer-executable instructions. The computer-executable instructions, when executed by the at least one processor, cause the UE to: receive, from a Base Station (BS), configuration information configuring a transmission configuration indication (TCI) state list; receive, from the BS, downlink control information (DCI) for initiating a Random Access (RA) procedure, where the DCI includes a physical random access channel (PRACH) association field; in response to determining that at least one TCI state included in the TCI state list is associated with a path loss (PL) offset and the PRACH association field indicates a first bit field index: transmit, to the BS, a PRACH based on a first TCI state that is associated with the PL offset; receive, from the BS, a random access response (RAR) by assuming that first demodulation reference signal (DM-RS) antenna ports of the RAR are quasi co-located with second DM-RS antenna ports associated with Physical Downlink Control Channel (PDCCH) receptions in a control resource set (CORESET) for a Type1-PDCCH common search space (CSS) set; transmit, to the BS, a physical uplink shared channel (PUSCH) scheduled by the RAR based on the first TCI state; and receive, from the BS, a Physical Downlink Shared Channel (PDSCH) in response to the PUSCH by assuming that third DM-RS antenna ports of the PDSCH are quasi co-located with the second DM-RS antenna ports; and in response to determining that the at least one TCI state included in the TCI state list is associated with the PL offset and the PRACH association field indicates a second bit field index: transmit, to the BS, the PRACH based on a second TCI state that is not associated with the PL offset; receive, from the BS, the RAR by assuming that the first DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports; transmit, to the BS, the PUSCH scheduled by the RAR based on the second TCI state; and receive, from the BS, the PDSCH in response to the PUSCH by assuming that the third DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports.

[0005] In some implementations of the first aspect, the first bit field index corresponds to a first bit value, and the second bit field index corresponds to a second bit value.

[0006] In some implementations of the first aspect, receiving, from the BS, the RAR by assuming that the first DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports includes receiving, from the BS, the RAR by assuming that the first DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports with respect to doppler shift, doppler spread, average delay, delay spread, and spatial receiver (RX) parameters, and receiving, from the BS, the PDSCH in response to the PUSCH by assuming that the third DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports includes receiving, from the BS, the PDSCH in response to the PUSCH by assuming that the third DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports with respect to doppler shift, doppler spread, average delay, delay spread, and spatial RX parameters.

[0007] In some implementations of the first aspect, the configuration information further configures a first timing advance group (TAG) and a second TAG.

[0008] In some implementations of the first aspect, the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to: in response to determining that (i) the first TAG and the second TAG are configured and (ii) the at least one TCI state included in the TCI state list is associated with the PL offset: receive, from the BS, a first information element (IE) configuring a first TA offset for transmissions using a first spatial filter that is associated with the first TCI state, and receive, from the BS, a second IE configuring a second TA offset for transmissions using a second spatial filter that is associated with the second TCI state.

[0009] In some implementations of the first aspect, the PRACH association field further indicates whether the first TCI state or the second TCI state is applied for a path loss calculation.

[0010] In some implementations of the first aspect, the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to: in response to determining that the PRACH association field indicates that the first TCI state is applied for the path loss calculation, calculate a first path loss based on the first TCI state; and in response to determining that the PRACH association field indicates that the second TCI state is applied for the path loss calculation, calculate a second path loss based on the second TCI state.

[0011] In a second aspect of the present disclosure, a method performed by a user equipment (UE) for TA adjustments under asymmetric DL sTRP and UL mTRP scenarios is provided. The method includes: receiving, from a Base Station (BS), configuration information configuring a transmission configuration indication (TCI) state list; receiving, from the BS, downlink control information (DCI) for initiating a Random Access (RA) procedure, wherein the DCI includes a physical random access channel (PRACH) association field; in response to determining that at least one TCI state included in the TCI state list is associated with a path loss (PL) offset and the PRACH association field indicates a first bit field index: transmitting, to the BS, a PRACH based on a first TCI state that is associated with the PL offset; receiving, from the BS, a random access response (RAR) by assuming that first demodulation reference signal (DM-RS) antenna ports of the RAR are quasi co-located with second DM-RS antenna ports associated with Physical Downlink Control Channel (PDCCH) receptions in a control resource set (CORESET) for a Type1-PDCCH common search space (CSS) set; transmitting, to the BS, a physical uplink shared channel (PUSCH) scheduled by the RAR based on the first TCI state; and receiving, from the BS, a Physical Downlink Shared Channel (PDSCH) in response to the PUSCH by assuming that third DM-RS antenna ports of the PDSCH are quasi co-located with the second DM-RS antenna ports; and in response to determining that the at least one TCI state included in the TCI state list is associated with the PL offset and the PRACH association field indicates a second bit field index: transmitting, to the BS, the PRACH based on a second TCI state that is not associated with the PL offset; receiving, from the BS, the RAR by assuming that the first DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports; transmitting, to the BS, the PUSCH scheduled by the RAR based on the second TCI state; and receiving, from the BS, the PDSCH in response to the PUSCH by assuming that the third DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports.

[0012] In a third aspect of the present application, a BS for TA adjustments under asymmetric DL sTRP and UL mTRP scenarios is provided. The BS includes at least one processor and at least one non-transitory computer-readable medium that is coupled to the at least one processor and that stores one or more computer-executable instructions. The computer-executable instructions, when executed by the at least one processor, cause the BS to: transmit, to a user equipment (UE), configuration information configuring a transmission configuration indication (TCI) state list; and transmit, to the UE, downlink control information (DCI) for initiating a Random Access (RA) procedure, where the DCI includes a physical random access channel (PRACH) association field. The configuration information and the DCI cause the UE to: in response to determining that at least one TCI state included in the TCI state list is associated with a path loss (PL) offset and the PRACH association field indicates a first bit field index: transmit, to the BS, a PRACH based on a first TCI state that is associated with the PL offset; receive, from the BS, a random access response (RAR) by assuming that first demodulation reference signal (DM-RS) antenna ports of the RAR are quasi co-located with second DM-RS antenna ports associated with Physical Downlink Control Channel (PDCCH) receptions in a control resource set (CORESET) for a Type1-PDCCH common search space (CSS) set; transmit, to the BS, a physical uplink shared channel (PUSCH) scheduled by the RAR based on the first TCI state; and receive, from the BS, a Physical Downlink Shared Channel (PDSCH) in response to the PUSCH by assuming that third DM-RS antenna ports of the PDSCH are quasi co-located with the second DM-RS antenna ports; and in response to determining that the at least one TCI state included in the TCI state list is associated with the PL offset and the PRACH association field indicates a second bit field index: transmit, to the BS, the PRACH based on a second TCI state that is not associated with the PL offset; receive, from the BS, the RAR by assuming that the first DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports; transmit, to the BS, the PUSCH scheduled by the RAR based on the second TCI state; and receive, from the BS, the PDSCH in response to the PUSCH by assuming that the third DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports.

[0013] Aspects of the present disclosure are best understood from the following detailed disclosure when read with the accompanying drawings. Various features are not drawn to scale. Dimensions of various features may be arbitrarily increased or reduced for clarity of discussion.

[0014] FIG. 1 is a diagram illustrating a heterogeneous network deployment, according to an example implementation of the present disclosure.

[0015] FIG. 2A is a diagram illustrating an asymmetric DL sTRP and UL mTRP deployment scenario, according to an example implementation of the present disclosure.

[0016] FIG. 2B is a diagram illustrating an asymmetric DL sTRP and UL mTRP deployment scenario, according to an example implementation of the present disclosure.

[0017] FIG. 3 is a flowchart illustrating a method / process performed by a UE for TA adjustments under asymmetric DL sTRP and UL mTRP scenarios, according to an example implementation of the present disclosure.

[0018] FIG. 4 is a flowchart illustrating a method / process performed by a BS for TA adjustments under asymmetric DL sTRP and UL mTRP scenarios, according to an example implementation of the present disclosure.

[0019] FIG. 5 is a block diagram illustrating a node for wireless communication, according to an example implementation of the present disclosure.

[0020] Some of the abbreviations used in the present disclosure include: Abbreviation　　　　Full name 3GPP　　　　3rdGeneration Partnership Project 5G　　　　5thGeneration 5GC　　　　5G Core 6GC　　　　6G Core BWP　　　　Band Width Part BS　　　　Base Station CN　　　　Core Network CORESET　　　　Control resource set CE　　　　Control Element CLPC　　　　Closed Loop Power Control CP　　　　Cyclic Prefix CRC　　　　Cyclic Redundancy Check C-RNTI　　　　Cell Radio Network Temporary Identifier CSS　　　　Common Search Space DCI　　　　Downlink Control Information DL　　　　Downlink DM-RS　　　　Demodulation Reference Signal HARQ　　　　Hybrid Automatic Repeat Request IE　　　　Information Element LTE　　　　Long Term Evolution LTE-A　　　　LTE-Advanced MAC　　　　Medium Access Control MCG　　　　Master Cell Group MCS　　　　Modulation Coding Scheme MR-DC 　　　　Multi-RAT Dual Connectivity multi-TRP　　　　multiple Transmission and Reception Point NR　　　　New RAT / Radio NTC　　　　Network Timing Control NW　　　　Network OFDM　　　　Orthogonal Frequency-Division Multiplexing PCell　　　　Primary Cell PCI　　　　Physical Cell Identity PSCell　　　　Primary Secondary Cell PBCH　　　　Physical Broadcast Channel PDCCH　　　　Physical Downlink Control Channel PDSCH　　　　Physical Downlink Shared Channel PL　　　　Path Loss PRACH　　　　Physical Random Access Channel PUSCH　　　　Physical Uplink Shared Channel QCL　　　　Quasi Co-Location RA　　　　Random Access RAN　　　　Radio Access Network RAR　　　　Random Access Response RAT　　　　Radio Access Technology Rel　　　　Release RF　　　　Radio Frequency RNTI　　　　Radio Network Temporary Identifier RRC　　　　Radio Resource Control RS　　　　Reference Signal RX　　　　Receiver SCell　　　　Secondary Cell SCG　　　　Secondary Cell Group SL　　　　Sidelink SN　　　　Secondary Node SpCell　　　　Special Cell SRS　　　　Sounding Reference Signal SS　　　　Synchronization Signal SSB　　　　Synchronization Signal Block sTRP　　　　Single Transmission and Reception Point TA　　　　Timing Advance TAG　　　　Timing Advance Group TB　　　　Transport Block TCI　　　　Transmission Configuration Indication TRP　　　　Transmission and Reception Point TTI　　　　Transmission Time Interval UE　　　　User Equipment UL　　　　Uplink URLLC　　　　Ultra Reliable Low Latency Communication W-CDMA　　　　Wideband-Code Division Multiple Access

[0021] The following contains specific information related to implementations of the present disclosure. The drawings and their accompanying detailed disclosure are merely directed to implementations. However, the present disclosure is not limited to these implementations. Other variations and implementations of the present disclosure will be obvious to those skilled in the art.

[0022] Unless noted otherwise, like or corresponding elements among the drawings may be indicated by like or corresponding reference numerals. Moreover, the drawings and illustrations in the present disclosure are generally not to scale and are not intended to correspond to actual relative dimensions.

[0023] For the purposes of consistency and ease of understanding, like features may be identified (although, in some examples, not illustrated) by the same numerals in the drawings. However, the features in different implementations may be different in other respects and may not be narrowly confined to what is illustrated in the drawings.

[0024] References to “one implementation,” “an implementation,” “example implementation,” “various implementations,” “some implementations,” “implementations of the present application,” etc., may indicate that the implementation(s) of the present application so described may include a particular feature, structure, or characteristic, but not every possible implementation of the present application necessarily includes the particular feature, structure, or characteristic. Further, repeated use of the phrase “In some implementations,” or “in an example implementation,” “an implementation,” do not necessarily refer to the same implementation, although they may. Moreover, any use of phrases like “implementations” in connection with “the present application” are never meant to characterize that all implementations of the present application must include the particular feature, structure, or characteristic, and should instead be understood to mean “at least some implementations of the present application” includes the stated particular feature, structure, or characteristic. The term “coupled” is defined as connected, whether directly or indirectly through intervening components, and is not necessarily limited to physical connections. The term “comprising,” when utilized, means “including, but not necessarily limited to”; it specifically indicates open-ended inclusion or membership in the so-described combination, group, series, and the equivalent.

[0025] The expression “at least one of A, B and C” or “at least one of the following: A, B and C” means “only A, or only B, or only C, or any combination of A, B and C.” The terms “system” and “network” may be used interchangeably. The term “and / or” is only an association relationship for describing associated objects and represents that three relationships may exist such that A and / or B may indicate that A exists alone, A and B exist at the same time, or B exists alone. The character “ / ” generally represents that the associated objects are in an “or” relationship.

[0026] For the purposes of explanation and non-limitation, specific details, such as functional entities, techniques, protocols, and standards, are set forth for providing an understanding of the disclosed technology. In other examples, detailed disclosure of well-known methods, technologies, systems, and architectures are omitted so as not to obscure the present disclosure with unnecessary details.

[0027] Persons skilled in the art will immediately recognize that any network function(s) or algorithm(s) disclosed may be implemented by hardware, software, or a combination of software and hardware. Disclosed functions may correspond to modules which may be software, hardware, firmware, or any combination thereof.

[0028] A software implementation may include computer executable instructions stored on a computer-readable medium, such as memory or other type of storage devices. One or more microprocessors or general-purpose computers with communication processing capability may be programmed with corresponding executable instructions and perform the disclosed network function(s) or algorithm(s).

[0029] The microprocessors or general-purpose computers may include Application-Specific Integrated Circuits (ASICs), programmable logic arrays, and / or one or more Digital Signal Processor (DSPs). Although some of the disclosed implementations are oriented to software installed and executing on computer hardware, alternative implementations implemented as firmware, as hardware, or as a combination of hardware and software are well within the scope of the present disclosure. The computer-readable medium includes but is not limited to Random Access Memory (RAM), Read Only Memory (ROM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), flash memory, Compact Disc Read-Only Memory (CD-ROM), magnetic cassettes, magnetic tape, magnetic disk storage, or any other equivalent medium capable of storing computer-readable instructions.

[0030] A radio communication network architecture such as a Long-Term Evolution (LTE) system, an LTE-Advanced (LTE-A) system, an LTE-Advanced Pro system, or a 5G NR Radio Access Network (RAN) typically includes at least one base station (BS), at least one UE, and one or more optional network elements that provide connection within a network. The UE communicates with the network such as a Core Network (CN), an Evolved Packet Core (EPC) network, an Evolved Universal Terrestrial RAN (E-UTRAN), a 5G Core (5GC), a 6G Core (6GC), or an internet via a RAN established by one or more BSs.

[0031] A UE may include, but is not limited to, a mobile station, a mobile terminal or device, or a user communication radio terminal. The UE may be a portable radio equipment that includes, but is not limited to, a mobile phone, a tablet, a wearable device, a sensor, a vehicle, or a Personal Digital Assistant (PDA) with wireless communication capability. The UE is configured to receive and transmit signals over an air interface to one or more cells in a RAN.

[0032] The BS may be configured to provide communication services according to at least a Radio Access Technology (RAT) such as Worldwide Interoperability for Microwave Access (WiMAX), Global System for Mobile communications (GSM) that is often referred to as 2G, GSM Enhanced Data rates for GSM Evolution (EDGE) RAN (GERAN), General Packet Radio Service (GPRS), Universal Mobile Telecommunication System (UMTS) that is often referred to as 3G based on basic wideband-code division multiple access (W-CDMA), high-speed packet access (HSPA), LTE, LTE-A, evolved LTE (eLTE) that is LTE connected to 5GC, NR (often referred to as 5G), and / or LTE-A Pro. However, the scope of the present disclosure is not limited to these protocols.

[0033] The BS may include, but is not limited to, a node B (NB) in the UMTS, an evolved node B (eNB) in LTE or LTE-A, a radio network controller (RNC) in UMTS, a BS controller (BSC) in the GSM / GERAN, an ng-eNB in an Evolved Universal Terrestrial Radio Access (E-UTRA) BS in connection with 5GC, a next generation Node B (gNB) in the 5G-RAN, or any other apparatus capable of controlling radio communication and managing radio resources within a cell. The BS may serve one or more UEs via a radio interface. Although the gNB is used as an example in some implementations within the present disclosure, it should be noted that the disclosed implementations may also be applied to other types of base stations.

[0034] The BS may be operable to provide radio coverage to a specific geographical area using multiple cells forming the RAN. The BS may support the operations of the cells. Each cell may be operable to provide services to at least one UE within its radio coverage.

[0035] Each cell (may often referred to as a serving cell) may provide services to one or more UEs within the cell’s radio coverage, such that each cell schedules the DL (and optionally UL resources) to at least one UE within its radio coverage for DL (and optionally UL packet transmissions from the UE). The BS may communicate with one or more UEs in the radio communication system via the cells.

[0036] A cell may allocate sidelink (SL) resources for supporting the Proximity Services (ProSe) or Vehicle to Everything (V2X) services. Each cell may have overlapped coverage areas with other cells.

[0037] In Multi-RAT Dual Connectivity (MR-DC) cases, the primary cell of a Master Cell Group (MCG) or a Secondary Cell Group (SCG) may be referred to as a Special Cell (SpCell). A Primary Cell (PCell) may include the SpCell of an MCG. A Primary SCG Cell (PSCell) may include the SpCell of an SCG. MCG may include a group of serving cells associated with the Master Node (MN), including the SpCell and optionally one or more Secondary Cells (SCells). An SCG may include a group of serving cells associated with the Secondary Node (SN), including the SpCell and optionally one or more SCells.

[0038] As discussed above, the frame structure for NR may support flexible configurations for accommodating various next generation (e.g., 5G) communication requirements, such as Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), and Ultra-Reliable and Low-Latency Communication (URLLC), while fulfilling high reliability, high data rate, and low latency requirements. The Orthogonal Frequency-Division Multiplexing (OFDM) technology in the 3GPP may serve as a baseline for an NR waveform. The scalable OFDM numerology, such as adaptive sub-carrier spacing, channel bandwidth, and Cyclic Prefix (CP), may also be used.

[0039] Two coding schemes may be considered for NR, specifically, Low-Density Parity-Check (LDPC) code and Polar Code. The coding scheme adaption may be configured based on channel conditions and / or service applications.

[0040] At least the DL transmission data, a guard period, and UL transmission data should be included in a transmission time interval (TTI) of a single NR frame. The respective portions of the DL transmission data, the guard period, and the UL transmission data should also be configurable based on, for example, the network dynamics of NR. SL resources may also be provided in an NR frame to support ProSe services or V2X services.

[0041] Any two or more than two of the following paragraphs, (sub)-bullets, points, actions, behaviors, terms, or claims described in the present disclosure may be combined logically, reasonably, and properly to form a specific method.

[0042] Any sentence, paragraph, (sub)-bullet, point, action, behaviors, terms, or claims described in the present disclosure may be implemented independently and separately to form a specific method.

[0043] Dependency, e.g., “based on”, “more specifically”, “preferably”, “in one embodiment”, “in some implementations”, etc., in the present disclosure is just one possible example which would not restrict the specific method.

[0044] In some implementations, all the designs / embodiment / implementations introduced within this disclosure are not limited to be applied for dealing with the problems discussed within this disclosure. For example, the described embodiments may be applied to solve other problems that exist in the RAN of wireless communication systems. In some implementations, all of the numbers listed within the designs / embodiment / implementations introduced within this disclosure are just examples and for illustration, for example, of how the described methods are executed.

[0045] The term “A and / or B” within the present disclosure means “A”, “B”, or “A and B”. The term “A and / or B and / or C” within the present disclosure means “A”, “B”, “C”, “A and B”, “A and C”, “B and C”, or “A and B and C”. The term “A / B” within the present disclosure means “A” or “B”.

[0046] Examples of some selected terms in the present disclosure are provided as follows.

[0047] Antenna Panel: A conceptual term for a UE antenna implementation. It may be assumed that a panel is an operational unit for controlling a transmitting spatial filter (beam). A panel may typically include multiple antenna elements. In one implementation, a beam may be formed by a panel, and in order to form two beams simultaneously, two panels may be needed. Such simultaneous beamforming from multiple panels may be subject to UE capability. A similar definition for “panel” may be applicable by applying spatial receiving filtering characteristics.

[0048] Beam: The term “beam” may be replaced by the spatial filter. For example, when the UE reports a preferred gNB TX beam, the UE may be essentially selecting a spatial filter used by the gNB. The term “beam information” may be used to provide information about which beam / spatial filter is used / selected. In one example, individual reference signals may be transmitted by applying individual beams (e.g., spatial filters). Thus, the term beam or beam information may be represented by reference signal resource index(es).

[0049] DCI: DCI may include downlink control information, and there may be various DCI formats used in a PDCCH. The DCI format may be a predefined format in which the downlink control information may be packed / formed and transmitted in a PDCCH.

[0050] TCI state: A TCI state may include parameters for configuring a QCL relationship between one or more DL reference signals and a target reference signal set. For example, a target reference signal set may include the DMRS ports of a PDSCH or a PDCCH.

[0051] HARQ: A functionality that ensures the delivery between peer entities at Layer 1 (e.g., Physical Layer). A single HARQ process supports one Transport Block (TB) when the physical layer is not configured for the downlink / uplink spatial multiplexing, and when the physical layer is configured for downlink / uplink spatial multiplexing, a single HARQ process may support one or more TBs. There is one HARQ entity per serving cell. Each HARQ entity may support a parallel (number of) DL and UL HARQ process.

[0052] In 3GPP RAN#105 meeting, asymmetric downlink (DL) sTRP / uplink (UL) mTRP deployment scenarios have been approved to study in the 3GPP Rel-19 NR. The details for studying may include the following (a) and (b). (a) Two closed-loop PC adjustment states for SRS, both separate from PUSCH; and path loss offset configurations for path loss calculation to UL TRP(s), when the path loss RS is from DL sTRP. (b) Two TAs through reusing Rel-18 specification of two TAs for multi-DCI-based multi-TRP and removing the restriction that coresetPoolIndex needs to be configured, assuming legacy PRACH resources.

[0053] In order to improve the UL throughput, the heterogenous network may be used. Generally, the heterogenous network may be constructed by the various types of cells (e.g., the macro cell, micro cell, pico cell, and femto cell). Each type of cells may have different coverage ranges. For example, macro cells may have the largest coverage range. The coverage range of micro cells may be within the converge range of a macro cell. FIG. 1 is a diagram illustrating a heterogeneous network deployment 100, according to an example implementation of the present disclosure. As illustrated in FIG. 1, there may be one macro cell 102, and there may be two micro cells 104, 106 having been deployed in the coverage 112 of the macro cell 102. In addition, a UE 108 may be located in the coverage 112, 114, 116 of the macro cell 102 and micro cells 104, 106.

[0054] In this example, the UE may transmit UL signals to either the macro cell gNB or the non-co-located micro cell nodes. Due to the limited UE transmit power, the UE may transmit UL signals to the micro cell node(s) in order to maximize UL throughput. For DL transmission, since the macro cell gNB may have a larger power rating than the micro cell, it may not matter whether the UE receives the DL signals from the macro gNB or micro cells. However, the network may reduce or even turn off DL transmission(s) from micro cell(s) to reduce network energy consumption if the UE (always) receives the DL signals from the macro cell gNB. Based on the consideration above, no matter for the UE or the network, it may be beneficial that the UE receives the DL signal(s) from the macro cell gNB and transmits the UL signal(s) to the micro cell node(s). Accordingly, how to achieve the asymmetric DL single TRP and UL multi-TRP deployment scenarios may be discussed in the present disclosure. For the asymmetric DL single TRP and UL multi-TRP deployment scenarios, the scenarios may be identified in the present disclosure as below.

[0055] Scenario: The UE may only receive DL signals from the TRP#1 but transmit UL signals to both TRP#1 and TRP#2

[0056] FIG. 2A is a diagram illustrating an asymmetric DL sTRP and UL mTRP deployment scenario 200A, according to an example implementation of the present disclosure. FIG. 2B is a diagram illustrating an asymmetric DL sTRP and UL mTRP deployment scenario 200B, according to an example implementation of the present disclosure. As illustrated in FIGs. 2A and 2B, the UE 202 may receive DL signals from TRP#1 (e.g., which is referred to as a regular TRP) and transmit UL signals to both TRP#1 and TRP#2 (e.g., which is referred to as an UL TRP). The regular TRP may transmit the DL signals to the UE and receive the UL signals from the UE. The UL TRP may receive the UL signals from the UE. In addition, the UL TRP may not transmit DL signals to the UE. That is, the UE may not expect to receive any DL signals from the UL TRP.

[0057] Based on the scenario illustrated in FIGs. 2A and 2B, one of the critical issues may be the beam determination corresponding to the UL transmission toward UL TRP. Generally, a UE may determine / derive the spatial properties (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial RX parameters) based on DL reference signals from gNB / TRP. Since UL TRP may not transmit DL reference signals to the UE, the UE may not be able to determine / derive the spatial properties for the corresponding beam for UL transmission toward UL TRP. So, in the present disclosure, how to determine the UL beam may be discussed.

[0058] If the CRC of the DCI format 1_0 is scrambled by the C-RNTI and the “Frequency domain resource assignment” field are of all ones, the DCI format 1_0 may be used for random access procedure initiated by a PDCCH order.

[0059] The first SRS resource set mentioned in the present disclosure may be referred to as the SRS resource set associated with the TRP#1 or TRP#2 in FIGs. 2A and 2B. In addition, the first SRS resource set may be referred to as the SRS resource set with the lowest index.

[0060] The second SRS resource set mentioned in the present disclosure may be referred to as the SRS resource set associated with the TRP#1 or TRP#2 in FIGs. 2A and 2B. In addition, the second SRS resource set may be referred to as the SRS resource set with a larger index than all configured SRS resource sets.

[0061] The first TCI state (e.g., the joint TCI state or UL TCI state) mentioned in the present disclosure may be referred to as the TCI state (e.g., the joint TCI state or UL TCI state) applied to the UL transmission toward the TRP#1 or TRP#2 in FIGs. 2A and 2B. In addition, the first TCI state (e.g., the joint TCI state or UL TCI state) may be referred to as the TCI state (e.g., the joint TCI state or UL TCI state) indicated in the first TCI field included in DL DCI or the TCI state (e.g., the joint TCI state or UL TCI state) indicated by an RRC field / IE / parameter.

[0062] The second TCI state (e.g., the joint TCI state or UL TCI state) mentioned in the present disclosure may be referred to as the TCI state (e.g., the joint TCI state or UL TCI state) applied for the UL transmission toward the TRP#1 or TRP#2 in FIGs. 2A and 2B. In addition, the second TCI state (e.g., the joint TCI state or UL TCI state) may be referred to as the TCI state (e.g., the joint TCI state or UL TCI state) indicated in the second TCI field included in DL DCI or the TCI state (e.g., joint TCI state or UL TCI state) indicated by an RRC field / IE / parameter.

[0063] The predefined path loss offset (or predefined PL offset) mentioned in the present disclosure may be P dB or P dBm, where P may be an integer.

[0064] Beam Determination for the PDCCH Initiated RACH

[0065] While a UE is in the RRC_CONNECTED state, the UE may be indicated to initiate a random access procedure by a DCI format transmitted by the gNB, where the DCI format may be DCI format 1_0. If the DCI format is for random access procedure initiated by a PDCCH order, the CRC of the DCI format 1_0 may be scrambled by the C-RNTI or a special RNTI, and the “Frequency domain resource assignment” field may be of all ones. The special RNTI may be the RNTI dedicated for or associated with the asymmetric DL sTRP and UL mTRP scenario, and the special RNTI may be configured to the UE by RRC signaling.

[0066] In some implementations, the UE may determine that the PDCCH ordered RACH is applied for the asymmetric DL sTRP / UL mTRP scenarios and / or the UE may be under the asymmetric DL sTRP and UL mTRP scenarios if at least one of the following conditions (a)-(g) is met.

[0067] (a) Condition#1: The UE receives one or more RRC configurations (e.g., path loss offset) used for the asymmetric DL sTRP and UL mTRP scenarios.

[0068] (b) Condition#2: The UE receives an RRC parameter informing the UE that it is under the asymmetric DL sTRP and UL mTRP scenarios.

[0069] (c) Condition#3: The UE is configured with one or more TCI state configurations (e.g., the DL TCI state configurations, UL TCI state configurations or joint TCI state configurations), where at least one TCI state configuration may include a field indicating a path loss offset value.

[0070] (d) Condition#4: The UE is indicated two TCI states (e.g., the UL TCI states or joint TCI states) for performing the UL transmission, where at least one TCI state may be associated with a path loss offset value. The TCI states may be indicated to the UE via DCI or RRC signaling.

[0071] (e) Condition#5: The UE receives a DCI format used for scheduling the UL transmission or initiating a RA procedure, where the CRC of the DCI format may be scrambled by a special RNTI. The special RNTI may be associated with the asymmetric DL sTRP and UL mTRP scenarios.

[0072] (f) Condition#6: The UE is configured with two separate SRS CLPC adjustment states.

[0073] (g) Condition#7: The UE is configured with a special preamble index for corresponding CFRA together with path loss offset configuration.

[0074] Whether a UE is under the asymmetric DL sTRP and UL mTRP scenarios in the present disclosure may be determined at least based on one of the Conditions #1 to #7 listed above.

[0075] In some implementations, the DCI format 1_0 used to initiate an RA procedure for the asymmetric DL sTRP and UL mTRP scenario may include at least one of the following DCI fields (A)-(F).

[0076] (A) Frequency domain resource assignment: Frequency domain resource assignment field may be of all ones if the DCI format 1_0 is for the RA procedure initiated by a PDCCH order.

[0077] (B) Random Access Preamble index

[0078] (C) UL / SUL indicator: If the Cell indicator is absent or the Cell indicator field indicates a serving cell, and if the value of the “PRACH Access Preamble index” is not all zeros and the UE is configured with the supplementaryUplink IE in the ServingCellConfig IE, the UL / SUL indicator field may be used to indicate which UL carrier (e.g., the normal UL carrier or supplementary UL carrier) in the serving cell to transmit the PRACH. The bit field index of the UL / SUL indicator ‘0’ may indicate the non-supplementary uplink, and the bit field index of the UL / SUL indicator ‘1’ may indicate the supplementary uplink.

[0079] (D) SS / PBCH index: If the value of the “PRACH Access Preamble index” is not all zeros, the SS / PBCH index field may be used to determine the RACH occasion for the PRACH transmission. Otherwise, this field may be reserved.

[0080] (E) PRACH Mask index: If the value of the “PRACH Access Preamble index” is not all zeros, the PRACH Mask index field may indicate the RACH occasion associated with the SS / PBCH indicated by the “SS / PBCH index” for the PRACH transmission. Otherwise, this field may be reserved.

[0081] (F) PRACH association indicator: The size of PRACH association indicator field may be 1 bit or 0 bit. If at least one of the following conditions (i)-(viii) is met, the size of PRACH association indicator field may be 1 bit. Otherwise, the size of PRACH association indicator field may be 0 bit.

[0082] (i) If the UE is provided with the tag2-Id IE and the UE is not provided the coresetPoolIndex IE, the size of PRACH association indicator field may be 1 bit.

[0083] (ii) If the UE is provided with the tag2-Id IE and the TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE for UL transmission is associated with a path loss offset value, the size of PRACH association indicator field may be 1 bit.

[0084] (iii) If the UE is provided with the tag2-Id IE and the UE is configured with an RRC parameter informing the UE that it is under the asymmetric DL sTRP and UL mTRP scenarios, the size of PRACH association indicator field may be 1 bit.

[0085] (iv) If the UE is configured with an RRC parameter informing the UE that it is under the asymmetric DL sTRP and UL mTRP scenarios, the size of PRACH association indicator field may be 1 bit.

[0086] (v) If the TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE for the UL transmission is associated with a path loss offset value, the size of PRACH association indicator field may be 1 bit.

[0087] (vi) If the UE is provided with the tag2-Id IE, if the UE is provided with the coresetPoolIndex IE with value 0 for the first CORESET, and if UE is provided with the coresetPoolIndex IE with value 1 for the second CORESET, the size of PRACH association indicator field may be 1 bit.

[0088] (vii) If the UE is configured with two separate SRS CLPC adjustment states, the size of PRACH association indicator field may be 1 bit.

[0089] (viii) If the UE is configured with SCells and each SCell is applied for either 2TA or asymmetric DL sTRP and UL mTRP scenario, the UE may interpret the received DCI from the PCell or SCell on the PRACH association indicator field based on the corresponding configurations.

[0090] In some implementations, the PRACH association indicator field may indicate the PL-RS for the PRACH transmission if the UE performs the PRACH transmission under the asymmetric DL sTRP and UL mTRP scenarios. The bit field index 0 of the PRACH association indicator field may be mapped to the DL RS that the DM-RS of the PDCCH order is quasi co-located with, and the bit field index 1 of the PRACH association indicator field may be mapped to the DL RS (e.g., the source RS or PL RS) associated with the TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE to perform the UL transmission toward the UL TRP. In addition, the bit field index 1 of the PRACH association indicator field may indicate the UE to calculate path loss based on the DL RS (e.g., the source RS or PL RS) and PL offset associated with the TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE to perform the UL transmission toward the UL TRP.

[0091] In some implementations, the PRACH association indicator field may indicate whether the UE to apply the PL offset for path loss calculation if the UE performs the PRACH transmission under the asymmetric DL sTRP and UL mTRP scenarios. The bit field index 0 of the PRACH association indicator field may indicate the UE to calculate the path loss without the PL offset. The PL RS used for the path loss calculation may be the DL RS that the DM-RS of the PDCCH order is quasi co-located with. The bit field index 1 of the PRACH association indicator field may indicate the UE to calculate the path loss with a PL offset associated with TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE to perform the UL transmission toward the UL TRP. The PL RS used for the path loss calculation may be the DL RS that the DM-RS of the PDCCH order is quasi co-located with or the DL RS (e.g., the source RS or PL RS) associated with the TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE to perform the UL transmission toward the UL TRP.

[0092] In some implementations, the PRACH indicator field may indicate the UE to calculate the path loss based on which PL offset if the UE performs the PRACH transmission under the asymmetric DL sTRP and UL mTRP scenarios. The bit field index 0 of the PRACH association indicator field may indicate the UE to calculate the path loss based on the PL offset associated with the TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE to perform the UL transmission toward the regular TRP. The PL RS used for the path loss calculation may be the DL RS that the DM-RS of the PDCCH order is quasi co-located with. The PDCCH order may be transmitted to the UE from the regular TRP. The bit field index 1 of the PRACH association indicator field may indicate the UE to calculate the path loss based on the PL offset associated with the TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE to perform the UL transmission toward the UL TRP. The PL RS used for the path loss calculation may be the DL RS that the DM-RS of the PDCCH order is quasi co-located with or the DL RS (e.g., the source RS or PL RS) associated with the TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE to perform the UL transmission toward the UL TRP.

[0093] In some implementations, the size of PRACH association indicator field may be more than 1 bit (e.g., 2 bits). If at least one of the following conditions (a) and (b) is met, the size of PRACH association indicator field may be more than 1 bit.

[0094] (a) If the UE is respectively indicated two joint / UL TCI states associated with two regular TRPs (e.g., the TCI state which is not configured with the PL offset or the TCI state configured with the PL offset with value 0), and if the UE is indicated one joint / UL TCI state associated with a UL TRP, the size of PRACH association indicator field may be 2 bits.

[0095] The bit field index 0 of the PRACH association indicator field may indicate the UE to calculate the path loss based on the first TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE or the DL RS associated with the PDCCH order, where the first indicated TCI state may be used to perform the UL transmission towards the first regular TRP (e.g., the TRP transmits the PDCCH order). The bit field index 1 of the PRACH association indicator field may indicate the UE to calculate the path loss based on the second TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE to perform the UL transmission toward the second regular TRP. The bit field index 2 of the PRACH association indicator field may indicate the UE to calculate the path loss based on the PL offset associated with the TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE to perform the UL transmission toward the UL TRP.

[0096] The first indicated TCI state and the second indicated TCI state may include a PL RS used for the path loss calculation. In addition, the first indicated TCI state and the second indicated TCI state may not include a PL offset used for the path loss calculation, or the first indicated TCI state and the second indicated TCI state may include a PL offset with zero value used for the path loss calculation. The TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE to perform the UL transmission toward the UL TRP may include a PL RS and / or a PL offset for the path loss calculation. If the TCI state does not include a PL RS for the path loss calculation, the UE may determine that the PL RS is the DL RS that the DM-RS of the PDCCH order is quasi co-located with or the DL RS. The bit field index 3 of the PRACH association indicator field may be reserved.

[0097] (b) If the UE is respectively indicated two joint / UL TCI states associated with two UL TRPs (e.g., the TCI state configured with a PL offset), and if the UE is indicated one joint / UL TCI state associated with a regular TRPs (e.g., the TCI state which is not configured with the PL offset or the TCI state configured with the PL offset with value 0), the size of the PRACH association indicator field may be 2 bits.

[0098] The bit field index 0 of the PRACH association indicator field may indicate the UE to calculate the path loss based on the TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE for the UL transmission towards a regular TRP (e.g., the TRP transmits the PDCCH order) or the DL RS associated with the PDCCH order. The bit field index 1 of the PRACH association indicator field may indicate the UE to calculate the path loss based on the PL offset associated with the first TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE to perform the UL transmission towards the first UL TRP. The bit field index 2 of the PRACH association indicator field may indicate the UE to calculate the path loss based on the PL offset associated with the second TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE to perform the UL transmission towards the second UL TRP.

[0099] The TCI state indicated to the UE to perform the UL transmission towards the regular TRP (e.g., the TRP transmits the PDCCH order) may include a PL RS used for the path loss calculation. In addition, the TCI state indicated to the UE to perform the UL transmission towards the regular TRP (e.g., the TRP transmits the PDCCH order) may not include a PL offset used for the path loss calculation or the TCI state indicated to the UE to perform the UL transmission towards the regular TRP (e.g., the TRP transmits the PDCCH order) may include a PL offset with zero value used for the path loss calculation. The first TCI state and the second TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE to perform the UL transmission toward the first UL TRP and the second UL TRP may include a PL RS and / or a PL offset for the path loss calculation. If the TCI state does not include a PL RS for the path loss calculation, the UE may determine that the PL RS is the DL RS that the DM-RS of the PDCCH order is quasi co-located with or the DL RS. The bit field index 3 of the PRACH association indicator field may be reserved.

[0100] In some implementations, the size of PRACH association indicator field may be 1 bit. If at least one of the following conditions (a) and (b) is met, the size of PRACH association indicator field may be more than 1 bit.

[0101] (a) If more than one UL only TRP is deployed under a regular TRP coverage (e.g., three TRPs, where one is regular DL TRP and the other two are UL TRPs), and if gNB configures two separate PL offsets without 2TAG configurations, the size of the PRACH association indicator field may be 1 bit.

[0102] The bit field index 0 of the PRACH association indicator field may be mapped to the DL RS that the DM-RS of the PDCCH order is quasi co-located with, and the bit field index 1 of the PRACH association indicator field may be mapped to the DL RS (e.g., the source RS or PL RS) associated with the TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE to perform the UL transmission toward any UL TRPs. In addition, the bit field index 1 of the PRACH association indicator field may indicate UE to calculate the path loss based on the DL RS (e.g., the source RS or PL RS) and the maximum of configured PL offset (e.g., the maximum candidate value of PL offset) associated with the TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE to perform the UL transmission toward the UL TRP.

[0103] (b) If the UE is respectively indicated two joint / UL TCI states associated with two regular TRPs (e.g., the TCI state which is not configured with the PL offset or the TCI state configured with the PL offset with value 0), and if the UE is indicated one joint / UL TCI state associated with a UL TRP, the size of PRACH association indicator field may be 1 bits but the gNB may require to use different PRACH index for the 2TA scenario and the asymmetric DL sTRP and UL mTRP scenario .

[0104] The bit field index 0 of the PRACH association indicator field may indicate the UE to calculate the path loss based on the first TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE or the DL RS associated with the PDCCH order, where the first indicated TCI state may be used to perform the UL transmission towards the first regular TRP (e.g., the TRP transmits the PDCCH order). If the bit field index 1 of the PRACH association indicator field and the preamble index sets to the value as configured with the 2TA configuration, it may indicate the UE to calculate the path loss based on the second TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE to perform the UL transmission toward the second regular TRP. The bit field index 1 of the PRACH association indicator field and the PRACH index sets to the value as configured with the PL offset configuration, it may indicate the UE to calculate the path loss based on the PL offset associated with the TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE to perform the UL transmission toward the UL TRP.

[0105] The DCI field may be used for the asymmetric DL sTRP and UL mTRP scenarios. In some implementations, when the UE performs the PDCCH order initiating RA procedure under the asymmetric DL sTRP and UL mTRP scenarios, the DCI format 1_0 may include one DCI field dedicated for the asymmetric DL sTRP and UL mTRP scenarios. The DCI field may include at least one of the following properties (a)-(c).

[0106] (a) The size of the DCI field used for the asymmetric DL sTRP and UL mTRP scenarios may be 0 or 1 bit. If the TCI state indicated to the UE for performing the UL transmission is associated with a PL offset, the size of the DCI field used for the asymmetric DL sTRP and UL mTRP scenarios may be 1 bit. Otherwise, the size of the DCI field used for the asymmetric DL sTRP and UL mTRP scenarios may be 0 bit. If the UE is configured with an RRC parameter informing the UE that it is under the asymmetric DL sTRP and UL mTRP scenarios, the DCI field used for the asymmetric DL sTRP and UL mTRP scenarios may be 1 bit. Otherwise, the size of the DCI field used for the asymmetric DL sTRP and UL mTRP scenarios may be 0 bit. If the UE is configured with two separate SRS CLPC adjustment states, the DCI field used for the asymmetric DL sTRP and UL mTRP scenarios may be 1 bit. Otherwise, the size of the DCI field used for the asymmetric DL sTRP and UL mTRP scenarios may be 0 bit.

[0107] (b) The DCI field used for the asymmetric DL sTRP and UL mTRP scenarios may be used to indicate the UE to apply which PL offset for the corresponding PRACH transmission. The bit field index 0 of the DCI field dedicated for the asymmetric DL sTRP and UL mTRP scenarios may indicate the UE to calculate the path loss based on the PL offset associated with the TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE to perform the UL transmission toward the regular TRP. The PL RS used for the path loss calculation may be the DL RS that the DM-RS of the PDCCH order is quasi co-located with. The PDCCH order may be transmitted to the UE from the regular TRP. The bit field index 1 of the DCI field dedicated for the asymmetric DL sTRP and UL mTRP scenarios may indicate the UE to calculate the path loss based on the PL offset associated with the TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE to perform the UL transmission toward the UL TRP. The PL RS used for the path loss calculation may be the DL RS that the DM-RS of the PDCCH order is quasi co-located with or the DL RS (e.g., the source RS or PL RS) associated with the TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE to perform the UL transmission toward the UL TRP.

[0108] (c) The DCI field used for the asymmetric DL sTRP and UL mTRP scenarios may indicate whether the UE to apply the PL offset for the path loss calculation if the UE performs the PRACH transmission under the asymmetric DL sTRP and UL mTRP scenarios. The bit field index 0 of the DCI field dedicated for the asymmetric DL sTRP and UL mTRP scenarios may indicate the UE to calculate the path loss without the PL offset. The bit field index 1 of the DCI field dedicated for the asymmetric DL sTRP and UL mTRP scenarios may indicate the UE to calculate the path loss with a PL offset associated with TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE to perform the UL transmission toward the UL TRP. The PL RS used for the path loss calculation may be the DL RS that the DM-RS of the PDCCH order is quasi co-located with or the DL RS (e.g., the source RS or PL RS) associated with the TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE to perform the UL transmission toward the UL TRP.

[0109] The size of the DCI field used for the asymmetric DL sTRP and UL mTRP scenarios may be more than 1 bit (e.g., 2 bits), if at least one of the following conditions (a) and (b) is met, the size of PRACH association indicator field may be more than 1 bit.

[0110] (a) If the UE is respectively indicated two joint / UL TCI states associated with two regular TRPs (e.g., the TCI state which is not configured with the PL offset or the TCI state configured with the PL offset with value 0), and if the UE is indicated one joint / UL TCI state associated with a UL TRP, the size of the DCI field used for the asymmetric DL sTRP and UL mTRP scenarios may be 2 bits.

[0111] The bit field index 0 of the DCI field used for the asymmetric DL sTRP and UL mTRP scenarios may indicate the UE to calculate the path loss based on the first TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE or the DL RS associated with the PDCCH order, where the first indicated TCI state may be used to perform the UL transmission towards the first regular TRP (e.g., the TRP transmits the PDCCH order). The bit field index 1 of the DCI field used for the asymmetric DL sTRP and UL mTRP scenarios may indicate the UE to calculate the path loss based on the second TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE to perform UL transmission toward the second regular TRP. The bit field index 2 of the DCI field used for the asymmetric DL sTRP and UL mTRP scenarios may indicate the UE to calculate the path loss based on the PL offset associated with the TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE to perform the UL transmission toward the UL TRP.

[0112] The first indicated TCI state and the second indicated TCI state may include a PL RS used for the path loss calculation. In addition, the first indicated TCI state and the second indicated TCI state may not include a PL offset used for the path loss calculation or the first indicated TCI state and the second indicated TCI state may include a PL offset with zero value used for the path loss calculation. The TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE to perform the UL transmission toward the UL TRP may include a PL RS and / or a PL offset for the path loss calculation. If the TCI state does not include a PL RS for the path loss calculation, the UE may determine that the PL RS is the DL RS that the DM-RS of the PDCCH order is quasi co-located with or the DL RS. The bit field index 3 of the DCI field used for the asymmetric DL sTRP and UL mTRP scenarios may be reserved.

[0113] (b) If the UE is respectively indicated two joint / UL TCI states associated with two UL TRPs (e.g., the TCI state configured with a PL offset), and if the UE is indicated one joint / UL TCI state associated with a regular TRPs (e.g., the TCI state which is not configured with the PL offset or the TCI state configured with PL offset with value 0), the size of the DCI field used for the asymmetric DL sTRP and UL mTRP scenarios may be 2 bits.

[0114] The bit field index 0 of the DCI field used for the asymmetric DL sTRP and UL mTRP scenarios may indicate the UE to calculate the path loss based on the TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE for the UL transmission towards a regular TRP (e.g., the TRP transmits the PDCCH order) or the DL RS associated with the PDCCH order. The bit field index 1 of the DCI field used for the asymmetric DL sTRP and UL mTRP scenarios may indicate the UE to calculate the path loss based on the PL offset associated with the first TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE to perform the UL transmission towards the first UL TRP. The bit field index 2 of the DCI field used for the asymmetric DL sTRP and UL mTRP scenarios may indicate the UE to calculate the path loss based on the PL offset associated with the second TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE to perform the UL transmission towards the second UL TRP.

[0115] The TCI state indicated to the UE to perform the UL transmission towards the regular TRP (e.g., the TRP transmits the PDCCH order) may include a PL RS used for the path loss calculation. In addition, the TCI state indicated to the UE to perform the UL transmission towards the regular TRP (e.g., the TRP transmits the PDCCH order) may not include a PL offset used for the path loss calculation or the TCI state indicated to the UE to perform the UL transmission towards the regular TRP (e.g., the TRP transmits the PDCCH order) may include a PL offset with zero value used for the path loss calculation. The first TCI state and the second TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE to perform the UL transmission toward the first UL TRP and the second UL TRP may include a PL RS and / or a PL offset for the path loss calculation. If the TCI state does not include a PL RS for the path loss calculation, the UE may determine that the PL RS is the DL RS that the DM-RS of the PDCCH order is quasi co-located with or the DL RS. The bit field index 3 of the DCI field used for the asymmetric DL sTRP and UL mTRP scenarios may be reserved.

[0116] In some implementations, if more than one UL TRP is deployed under a regular TRP converge (e.g., three TRPs, where one is regular DL TRP and the other two are UL TRPs), and if the gNB configures two separate PL offsets without 2TAG configurations, the size of PRACH association indicator field may be 1 bit. The bit field index 0 of the PRACH association indicator field may be mapped to the DL RS that the DM-RS of the PDCCH order is quasi co-located with, and the bit field index 1 of the PRACH association indicator field may be mapped to the DL RS (e.g., the source RS or PL RS) associated with the TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE to perform the UL transmission toward any UL TRPs. In addition, the bit field index 1 of the PRACH association indicator field may indicate the UE to calculate the path loss based on the DL RS (e.g., the source RS or PL RS) and the maximum of configured PL offset (e.g., the maximum candidate value of the PL offset) associated with the TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE to perform the UL transmission toward the UL TRP.

[0117] In some implementations, if the UE is respectively indicated two joint / UL TCI states associated with two regular TRPs (e.g., the TCI state which is not configured with the PL offset or the TCI state configured with the PL offset with value 0), and if the UE is indicated one joint / UL TCI state associated with a UL TRP, the size of PRACH association indicator field may be 1 bits but the gNB may require to use different preamble index for the 2TA scenario and the asymmetric DL sTRP and UL mTRP scenario. The bit field index 0 of the PRACH association indicator field may indicate the UE to calculate the path loss based on the first TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE or the DL RS associated with the PDCCH order, where the first indicated TCI state may be used to perform the UL transmission towards the first regular TRP (e.g., the TRP transmits the PDCCH order). If the bit field index 1 of the PRACH association indicator field and the PRACH index sets to the value as configured with the 2TA configuration, it may indicate the UE to calculate the path loss based on the second TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE to perform the UL transmission toward the second regular TRP. The bit field index 1 of the PRACH association indicator field and the preamble index sets to the value as configured with the PL offset configuration, it may indicate the UE to calculate the path loss based on the PL offset associated with the TCI state (e.g., the joint TCI state or UL TCI state) indicated to the UE to perform the UL transmission toward the UL TRP.

[0118] In some implementations, when a UE receives a DCI format 1_0 used to initiate an RA procedure for the asymmetric DL sTRP and UL mTRP scenarios, the UE may transmit a PRACH based on the instructions indicated in the DCI format 1_0.

[0119] For example, if a PRACH transmission from a UE is in response to a detection of a PDCCH order by the UE that triggers a contention-free random access procedure, the UE may perform the PRACH transmission (e.g., determine the UL spatial filter for the PRACH transmission) based on the DL RS that the DM-RS of the PDCCH order is quasi co-located with under at least one of the following conditions (a)-(c).

[0120] (a) When the specific DCI field (e.g., the PRACH association indicator field or a DCI field dedicated for the asymmetric DL sTRP and UL mTRP scenarios) is not present in the PDCCH order.

[0121] (b) When the specific DCI field (e.g., the PRACH association indicator field or a DCI field dedicated to the asymmetric DL sTRP and UL mTRP scenarios) indicates ‘0’ if the UE performs the PRACH transmission under the asymmetric DL sTRP and UL mTRP scenarios.

[0122] (c) When the specific DCI field (e.g., the PRACH association indicator field or a DCI field dedicated for the asymmetric DL sTRP and UL mTRP scenarios) indicates ‘0’ if the UE is not provided with the SSB-NTC-AdditionalPCI IE.

[0123] For example, if a PRACH transmission from a UE is in response to a detection of a PDCCH order by the UE that triggers a contention-free random access procedure, the UE may perform the PRACH transmission (e.g., determine the UL spatial filter for the PRACH transmission) based on the indicated TCI state (e.g., the joint TCI state or UL TCI state) associated with the UL TRP under at least one of the following conditions (a) and (b).

[0124] (a) When the specific DCI field (e.g., the PRACH association indicator field or a DCI field dedicated for the asymmetric DL sTRP and UL mTRP scenarios) indicates ‘1’ if the UE performs the PRACH transmission under the asymmetric DL sTRP and UL mTRP scenarios.

[0125] (b) When the specific DCI field (e.g., the PRACH association indicator field or a DCI field dedicated for the asymmetric DL sTRP and UL mTRP scenarios) indicates ‘1’ if the UE is not provided with the SSB-NTC-AdditionalPCI IE.

[0126] In some implementations, the UE may assume the DL-RS antenna port quasi co-location properties of the CORESET associated with the Type1-PDCCH CSS set for receiving the PDCCH that includes the DCI format 1_0 and the PDSCH scheduled by the DCI format 1_0 under at least one of the following conditions (a)-(c).

[0127] (a) When a UE is under the asymmetric DL sTRP and UL mTRP scenarios (e.g., the indicated TCI state (e.g., the joint TCI state or UL TCI state) is associated with a PL offset).

[0128] (b) When the UE is configured with two TAGs for a cell and the CORESET in which the UE receives the PDCCH order triggering a contention-free random access procedure does not correspond to the TRP that transmits the PDCCH order.

[0129] (c) When the UE is configured with two TAGs and the specific DCI field (e.g., the PRACH association indicator field or a DCI field dedicated for the asymmetric DL sTRP and UL mTRP scenarios) indicates ‘1’.

[0130] In some implementations, when a UE is under the asymmetric DL sTRP and UL mTRP scenarios, (e.g., no matter what the PRACH association indicator field indicate) and if the UE attempts to detect the DCI format 1_0 with the CRC scrambled by the corresponding RA-RNTI to a PRACH transmission initiated by a PDCCH order that triggers a contention-free random access procedure, the UE may assume that the PDCCH that include the DCI format 1_0 and the PDCCH order have the same DM-RS antenna port quasi co-location properties.

[0131] In some implementations, when a UE is under the asymmetric DL sTRP and UL mTRP scenarios, (e.g., no matter what the PRACH association indicator field indicate) and if the UE attempts to detect the DCI format 1_0 with the CRC scrambled by the corresponding RA-RNTI to a PRACH transmission initiated by a PDCCH order that triggers a contention-free random access procedure, the UE may apply the indicated TCI state (e.g., the DL TCI state or joint TCI state) associated with the regular TRP (e.g., the TRP transmits the PDCCH order) for receiving the PDCCH that includes the DCI format 1_0.

[0132] In some implementations, when a UE is under the asymmetric DL sTRP and UL mTRP scenarios, (e.g., no matter what the PRACH association indicator field indicate) and if the UE attempts to detect the DCI format 1_0 with the CRC scrambled by the corresponding RA-RNTI to a PRACH transmission initiated by a PDCCH order that triggers a contention-free random access procedure, the UE may apply the TCI state configured to receive the PDCCH order (e.g., the DL / joint TCI state configured in the CORESET configuration, DL / joint TCI state indicated in the MAC CE for the PDCCH reception, or DL / joint TCI state indicated by the DCI) for receiving the PDCCH that includes the DCI format 1_0.

[0133] In some implementations, if a UE is under the asymmetric DL sTRP and UL mTRP scenarios, (e.g., no matter what the PRACH association indicator field indicate) and when the UE receives a PDSCH scheduled with the RA-RNTI in response to a random access procedure triggered by a PDCCH order which triggers the contention-free random access procedure, the UE may assume that the DM-RS ports of the received PDSCH are quasi co-located with the DM-RS antenna port associated with PDCCH receptions in the CORESET for the Type1-PDCCH CSS set with respect to Doppler shift, Doppler spread, average delay, delay spread, and spatial RX parameters when applicable.

[0134] In some implementations, if a UE is under the asymmetric DL sTRP and UL mTRP scenarios, (e.g., no matter what the PRACH association indicator field indicate) and when the UE receives a PDSCH scheduled with the RA-RNTI in response to a random access procedure triggered by a PDCCH order which triggers the contention-free random access procedure, the UE may assume that the DM-RS ports of the received PDSCH are quasi co-located with the DM-RS antenna port associated with PDCCH receptions in the CORESET associated with the regular TRP (e.g., the TRP transmits the PDCCH order) with respect to Doppler shift, Doppler spread, average delay, delay spread, and spatial RX parameters when applicable.

[0135] In some implementations, if a UE is under the asymmetric DL sTRP and UL mTRP scenarios, (e.g., no matter what the PRACH association indicator field indicate,) when the UE receives a PDSCH scheduled with the RA-RNTI in response to a random access procedure triggered by a PDCCH order which triggers the contention-free random access procedure, the UE may receive the PDSCH based on the indicated TCI state (e.g., the DL TCI state or joint TCI state) associated with the regular TRP (e.g., the TRP transmits the PDCCH order) or the TCI state configured to receive the PDCCH order (e.g., the DL / joint TCI state configured in the CORESET configuration, DL / joint TCI state indicated in the MAC CE for the PDCCH reception, or DL / joint TCI state indicated by the DCI).

[0136] In some implementations, if a UE is under the asymmetric DL sTRP and UL mTRP scenarios and when the UE receives a RAR in response to a PRACH transmission, the UE may transmit a PUSCH scheduled by the RAR UL grant. The UE may transmit the PUSCH scheduled by the RAR UL grant with the same UL spatial filter used for the PRACH transmission.

[0137] For example, if a PUSCH transmission from a UE is in response to a detection of a RAR in response to a PRACH transmission by the UE, the UE may perform the PUSCH transmission (e.g., determine the UL spatial filter for the PUSCH transmission) based on the DL RS that the DM-RS of the PDCCH order is quasi co-located with under at least one of the following conditions (a)-(c).

[0138] (a) When the specific DCI field (e.g., the PRACH association indicator field or a DCI field dedicated for the asymmetric DL sTRP and UL mTRP scenarios) is not present in the PDCCH order.

[0139] (b) When the specific DCI field (e.g., the PRACH association indicator field or a DCI field dedicated for the asymmetric DL sTRP and UL mTRP scenarios) indicates ‘0’ and the UE performs PRACH transmission under the asymmetric DL sTRP and UL mTRP scenarios.

[0140] (c) When the specific DCI field (e.g., the PRACH association indicator field or a DCI field dedicated for the asymmetric DL sTRP and UL mTRP scenarios) indicates ‘0’ and the UE is not provided with the SSB-NTC-AdditionalPCI IE.

[0141] For example, if a PUSCH transmission from a UE is in response to a detection of a RAR in response to a PRACH transmission by the UE, the UE may perform the PUSCH transmission (e.g., determine the UL spatial filter for PUSCH transmission) based on the indicated TCI state (e.g., the joint TCI state or UL TCI state) associated with the UL TRP under at least one of the following conditions (a) and (b).

[0142] (a) When the specific DCI field (e.g., the PRACH association indicator field or a DCI field dedicated for the asymmetric DL sTRP and UL mTRP scenarios) indicates ‘1’ and the UE performs the PRACH transmission under the asymmetric DL sTRP andUL mTRP scenarios.

[0143] (b) When the specific DCI field (e.g., the PRACH association indicator field or a DCI field dedicated for the asymmetric DL sTRP and UL mTRP scenarios) indicates ‘1’ and the UE is not provided with the SSB-NTC-AdditionalPCI IE.

[0144] In some implementations, if a UE is under the asymmetric DL sTRP and UL mTRP scenarios, (e.g., no matter what the PRACH association indicator field indicate) and when the UE receives the PDSCH in response to a PUSCH transmission scheduled by a RAR UL grant or corresponding PUSCH retransmission, the UE may assume that the DM-RS ports of the received PDSCH are quasi co-located with the DM-RS antenna port associated with PDCCH receptions in the CORESET for the Type1-PDCCH CSS set with respect to Doppler shift, Doppler spread, average delay, delay spread, and spatial RX parameters when applicable.

[0145] In some implementations, if a UE is under the asymmetric DL sTRP and UL mTRP scenarios, (e.g., no matter what the PRACH association indicator field indicate) and when the UE receives a PDSCH in response to a PUSCH transmission scheduled by a RAR UL grant or corresponding PUSCH retransmission, the UE may assume that the DM-RS ports of the received PDSCH are quasi co-located with the DM-RS antenna port associated with PDCCH receptions in the CORESET associated with the regular TRP (e.g., the TRP transmits the PDCCH order) with respect to Doppler shift, Doppler spread, average delay, delay spread, and spatial RX parameters when applicable.

[0146] In some implementations, if a UE is under the asymmetric DL sTRP and UL mTRP scenarios, (e.g., no matter what the PRACH association indicator field indicate) and when the UE receives a PDSCH in response to a PUSCH transmission scheduled by a RAR UL grant or corresponding PUSCH retransmission, the UE may receive the PDSCH based on the indicated TCI state (e.g., the DL TCI state or joint TCI state) associated with the regular TRP (e.g., the TRP transmits the PDCCH order) or the TCI state configured to receive the PDCCH order (e.g., the DL / joint TCI state configured in the CORESET configuration, DL / joint TCI state indicated in the MAC CE for PDCCH reception, or DL / joint TCI state indicated by the DCI).

[0147] In some implementations, a UE may be configured with an RRC parameter dedicated for the asymmetric DL sTRP and UL mTRP scenarios (e.g., the power ramping step dedicated for the asymmetric DL sTRP and UL mTRP scenarios) by gNB / NW, where the power ramping step dedicated for the asymmetric DL sTRP and UL mTRP scenarios may be different from the power ramping step used for the legacy PRACH transmission. The RRC parameter dedicated for the asymmetric DL sTRP and UL mTRP scenarios may be absent if the UE is not under the asymmetric DL sTRP and UL mTRP scenarios (e.g., no TCI states included in the TCI state list configured to the UE are associated with a PL offset, no asymmetric DL sTRP and UL mTRP scenarios-specific RRC parameter(s) configured to the UE, no TCI states indicted to the UE for performing the UL transmission are associated with the PL offset, and / or the UE is not configured with two SRS CLPC adjustment states). The RRC parameter may be present (only) if the UE is under the asymmetric DL sTRP and UL mTRP scenarios.

[0148] In some implementations, the different PRACH transmission power formula (e.g., from existing Rel-18 specification) may be used if the PRACH association indicator field set to “1” while no 2TAG configuration but with the path loss offset configuration. The maximum transmission power and the target transmission power may be the same regardless of the PRACH association indicator field being set to “1” or “0” but the UE may be required to add path loss offset in the formula while the PRACH association indicator field set to “1”. Consequently, the power ramping step may be the same parameter for the 2TAG and asymmetric scenario.

[0149] In some implementations, the different PRACH transmission power formula (e.g., from existing Rel-18 specification) may be used if the PRACH association indicator field set to “1” while no 2TAG configuration but with the path loss offset configuration. The maximum transmission power and the target transmission power may be different based on the PRACH association indicator field being set to “1” or “0” and the UE may be required to add the path loss offset and apply different parameter values in the formula while the PRACH association indicator field set to “1”. Consequently, the power ramping step may be the different parameters for the 2TAG and asymmetric scenario.

[0150] In some implementations, the different PRACH transmission power formula (e.g., from existing Rel-18 specification) may be used if the PRACH association indicator field set to “1” while the gNB configures the 2TAG configuration and also the path loss offset configuration. The maximum transmission power and the target transmission power may be the same regardless of the PRACH association indicator field being set to “1” or “0” but the UE may be required to add the path loss offset in the formula while the PRACH association indicator field set to “1”.

[0151] In some implementations, the different PRACH transmission power formula (e.g., from existing Rel-18 specification) may be used if the PRACH association indicator field set to “1” while no 2TAG configuration and also the path loss offset configuration. The maximum transmission power and the target transmission power may be different based on the PRACH association indicator field being set to “1” or “0” and the UE may be required to add the path loss offset and apply different parameter values in the formula while the PRACH association indicator field set to “1”. Consequently, the power ramping step may be the different parameters for the 2TAG and asymmetric scenario.

[0152] Two TAs under Asymmetric DL sTRP and UL mTRP Scenarios

[0153] In some implementations, if a UE is under the asymmetric DL sTRP and UL mTRP scenarios, and if the UE is configured with the twoTAGs IE and is configured with join TCI state list (e.g., the dl-OrJointTCI-StateList IE) or UL TCI state list (e.g., the ul-TCI-StateList IE or TCI-UL-State IE) for a serving cell, each TCI-State IE (e.g., the joint TCI state) or TCI-UL-State IE (e.g., the joint TCI state) may be associated with a TAG ID for determining the timing adjustment for a corresponding UL transmission, and each TCI-State IE (e.g., the joint TCI state) or TCI-UL-State IE (e.g., the joint TCI state) corresponding to UL TRP may be associated with a PL offset for determining the path loss compensation (or UL power) for the corresponding UL transmission.

[0154] In some implementations, the UE may not expect that the TCI-states IE (e.g., the joint TCI states) or the TCI-UL-States IE (e.g., the UL TCI states) associated with one PL offset corresponds to two TAGs. In some implementations, the UE may not expect that the TCI-states IE (e.g., the joint TCI states) or the TCI-UL-States IE (e.g., the UL TCI states) associated with one TRP (e.g., the regular TRP or UL TRP) corresponds to two TAGs. In some implementations, the UE may not expect that indicated TCI states (e.g., the joint TCI states indicated to perform the UL transmission toward the regular TRP or UL TRP) or indicated TCI-UL-States IE (e.g., the UL TCI states indicated to perform the UL transmission toward the regular TRP or UL TRP) correspond to two TAGs. In some implementations, the UE may not expect that the TCI-states IE (e.g., the joint TCI states) or the TCI-UL-States IE (e.g., the UL TCI states) associated with one SRS resource set corresponds to two TAGs.

[0155] In some implementations, if the UE is configured with the twoTAGs IE and is configured with the joint TCI state list (e.g., the dl-OrJointTCI-StateList IE) or the UL TCI state list (e.g., the ul-TCI-StateList IE or the TCI-UL-State IE) for a serving cell, and if at least one TCI-State IE (e.g., the joint TCI state) or TCI-UL-State IE (e.g., the joint TCI state) is configured with a PL offset, each TCI-State IE (e.g., the joint TCI state) or TCI-UL-State IE (e.g., the joint TCI state) may be associated with a TAG ID for determining the timing adjustment for a corresponding UL transmission.

[0156] In some implementations, the UE may not expect that the TCI-states IE (e.g., the joint TCI states) or the TCI-UL-States IE (e.g., the UL TCI states) associated with one PL offset corresponds to two TAGs. In some implementations, the UE may not expect that the TCI-states IE (e.g., the joint TCI states) or the TCI-UL-States IE (e.g., the UL TCI states) associated with one TRP (e.g., the regular TRP or UL TRP) corresponds to two TAGs. In some implementations, the UE may not expect that indicated TCI states (e.g., the joint TCI states indicated to perform the UL transmission toward the regular TRP or UL TRP) or indicated TCI-UL-States IE (e.g., the UL TCI states indicated to perform the UL transmission toward the regular TRP or UL TRP) correspond to two TAGs. In some implementations, the UE may not expect that the TCI-states IE (e.g., the joint TCI states) or the TCI-UL-States IE (e.g., the UL TCI states) associated with one SRS resource set corresponds to two TAGs.

[0157] In some implementations, if a UE operates with two TAGs on an active UL BWP of a serving cell, and if at least one of the indicated TCI state (e.g., the indicated joint TCI state or indicated UL TCI state) associated with a first TAG or a second TAG is associated with a PL offset, the UE may expect that the first downlink timing associated with the first TAG is the same as the second downlink timing associated with the second TAG.

[0158] In some implementations, the first downlink timing and the second downlink timing may be the downlink timing associated with the indicated TCI state (e.g., the indicated joint TCI state or indicated UL TCI state) which is not configured with a PL offset. In some implementations, the first downlink timing and the second downlink timing may be the downlink timing associated with the indicated TCI state (e.g., the indicated joint TCI state or indicated UL TCI state) configured with a zero PL offset (e.g., the PL offset value is equal to 0).

[0159] In some implementations, if a UE operates with two TAGs on an active UL BWP of a serving cell, and if at least one of the indicated TCI state associated with a first TAG or a second TAG is associated with a PL offset, the UE may expect that a difference between a first downlink timing associated with the first TAG and a second downlink timing associated with the second TAG is not larger / greater than the CP length for the active UL BWP unless the UE indicates the larger-thanCP-capability IE. The downlink timing associated with the indicated TCI state (e.g., the indicated joint TCI state or indicated UL TCI state) which is not configured with a PL offset or which is configured with a zero PL offset (e.g., the PL offset is equal to 0) may be an actual downlink timing. The downlink timing associated with the indicated TCI state (e.g., the indicated joint TCI state or indicated UL TCI state) configured with a non-zero PL offset (e.g., the PL offset is not equal to 0) may be a reference downlink timing.

[0160] The difference between the actual downlink timing and reference timing may be determined by the UE (e.g., based on the UE implementations), or the difference between the actual downlink timing and reference downlink timing may be configured by the NW / gNB via RRC signaling. The actual downlink timing may be associated with the regular TRP, indicated TCI state without the PL offset, and / or indicated TCI state with the PL offset value that is equal to 0. The reference downlink timing may be associated with the UL TRP, indicated TCI state with the PL offset, and / or indicated TCI state with the PL offset value that is not equal to 0. In some implementations, since the UL TRP may not transmit any DL signals to the UE, the UE may not obtain the DL timing based on the real DL transmission for the UL TRP. Hence, the DL timing (e.g., the reference DL timing) associated with the UL TRP may be derived by the DL timing (e.g., the actual DL timing) associated with the regular TRP.

[0161] In some implementations, if a UE operates with two TAGs on an active UL BWP of a serving cell, and / or if at least one TCI-State IE (e.g., the joint TCI state) or TCI-UL-State IE (e.g., the joint TCI state) is configured with a PL offset (e.g., the UE is under the asymmetric DL sTRP and UL mTRP scenarios), the UE may be provided with first and second NTA,offsetvalues by the n-TimingAdvanceOffset IE and the n-TimingAdvanceOffset2 IE for transmissions with first and second spatial filters associated with first and second TCI states for the regular TRP and UL TRP (or for the first and second SRS resource sets), respectively. A UE may be provided with a second NTA,offsetvalue for transmissions with second spatial domain filters corresponding to the second TCI states (e.g., associated with the UL TRP) in addition to a first NTA,offsetvalue for transmissions with first spatial domain filters corresponding to first TCI state (e.g., associated with regular TRP) or corresponding to the first SS / PBCH block receptions associated with the serving cell. The first and second NTA,offsetvalues corresponding to first and second TAGs indicated in the respective MAC RARs may have an association with the first and second joint TCI states provided by the joint TCI state list (e.g., the dl-OrJointTCI-StateList IE) or the first and second UL TCI states provided by the UL TCI state list (e.g., the ul-TCI-State-List IE). The association may be indicated by the tag-Id-ptr IE. If the UE is not provided with the n-TimingAdvanceOffset IE for a serving cell, the UE may determine a default value NTA,offsetof the timing advance offset for the serving cell.

[0162] In some implementations, if a UE operates with two TAGs on an active UL BWP of a serving cell, and / or if at least one TCI-State IE (e.g., the joint TCI state) or TCI-UL-State IE (e.g., the joint TCI state) is configured with a PL offset (e.g., the UE is under the asymmetric DL sTRP and UL mTRP scenarios), the UE may be provided with the NTA,offsetvalue(s) by the n-TimingAdvanceOffset IE for transmissions with first and second spatial filters associated with first and second TCI states for the regular TRP and UL TRP (or for the first and second SRS resource sets), respectively. A UE may be provided with a NTA,offsetvalue for transmissions with second spatial domain filters corresponding to the second TCI states (e.g., associated with the UL TRP) and for transmissions with first spatial domain filters corresponding to the first TCI state (e.g., associated with the regular TRP) or corresponding to first SS / PBCH block receptions associated with the serving cell. The NTA,offsetvalues corresponding to first and second TAGs indicated in the respective MAC RARs may have an association with the first and second joint TCI states provided by the joint TCI state list (e.g., the dl-OrJointTCI-StateList IE) or the first and second UL TCI states provided by the UL TCI state list (e.g., the ul-TCI-State-List IE). The association may be indicated by the tag-Id-ptr IE. If the UE is not provided with the n-TimingAdvanceOffset IE for a serving cell, the UE may determine a default value NTA,offsetof the timing advance offset for the serving cell.

[0163] FIG. 3 is a flowchart illustrating a method / process 300 performed by a UE for timing advance (TA) adjustments under asymmetric downlink (DL) single transmission and reception point (sTRP) and uplink (UL) multiple transmission and reception point (mTRP) scenarios, according to an example implementation of the present disclosure.

[0164] In the action 302, the process 300 may start by receiving, from a Base Station (BS), configuration information configuring a transmission configuration indication (TCI) state list.

[0165] In the action 304, the process 300 may receive, from the BS, downlink control information (DCI) for initiating a Random Access (RA) procedure, where the DCI may include a physical random access channel (PRACH) association field.

[0166] In the action 306, the process 300 may in response to determining that at least one TCI state included in the TCI state list is associated with a path loss (PL) offset and the PRACH association field indicates a first bit field index: transmit, to the BS, a PRACH based on a first TCI state that is associated with the PL offset; receive, from the BS, a random access response (RAR) by assuming that first demodulation reference signal (DM-RS) antenna ports of the RAR are quasi co-located with second DM-RS antenna ports associated with Physical Downlink Control Channel (PDCCH) receptions in a control resource set (CORESET) for a Type1-PDCCH common search space (CSS) set; transmit, to the BS, a physical uplink shared channel (PUSCH) scheduled by the RAR based on the first TCI state; and receive, from the BS, a Physical Downlink Shared Channel (PDSCH) in response to the PUSCH by assuming that third DM-RS antenna ports of the PDSCH are quasi co-located with the second DM-RS antenna ports.

[0167] In the action 308, the process 300 may in response to determining that the at least one TCI state included in the TCI state list is associated with the PL offset and the PRACH association field indicates a second bit field index: transmit, to the BS, the PRACH based on a second TCI state that is not associated with the PL offset; receive, from the BS, the RAR by assuming that the first DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports; transmit, to the BS, the PUSCH scheduled by the RAR based on the second TCI state; and receive, from the BS, the PDSCH in response to the PUSCH by assuming that the third DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports. The process 300 may then end.

[0168] In some implementations, the first bit field index may correspond to a first bit value, and the second bit field index may correspond to a second bit value.

[0169] In some implementations, receiving, from the BS, the RAR by assuming that the first DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports may include receiving, from the BS, the RAR by assuming that the first DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports with respect to doppler shift, doppler spread, average delay, delay spread, and spatial receiver (RX) parameters, and receiving, from the BS, the PDSCH in response to the PUSCH by assuming that the third DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports may include receiving, from the BS, the PDSCH in response to the PUSCH by assuming that the third DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports with respect to doppler shift, doppler spread, average delay, delay spread, and spatial RX parameters.

[0170] In some implementations, the configuration information may further configure a first timing advance group (TAG) and a second TAG. The process 300 may further in response to determining that (i) the first TAG and the second TAG are configured and (ii) the at least one TCI state included in the TCI state list is associated with the PL offset: receive, from the BS, a first information element (IE) configuring a first TA offset for transmissions using a first spatial filter that is associated with the first TCI state, and receive, from the BS, a second IE configuring a second TA offset for transmissions using a second spatial filter that is associated with the second TCI state.

[0171] In some implementations, the PRACH association field may further indicate whether the first TCI state or the second TCI state is applied for a path loss calculation. The process 300 may in response to determining that the PRACH association field indicates that the first TCI state is applied for the path loss calculation, calculate a first path loss based on the first TCI state; and in response to determining that the PRACH association field indicates that the second TCI state is applied for the path loss calculation, calculate a second path loss based on the second TCI state.

[0172] The steps / actions shown in FIG. 3 should not be construed as necessarily order dependent. The order in which the process is described is not intended to be construed as a limitation. Moreover, some of the actions shown in FIG. 3 may be omitted in some implementations and one or more actions shown in FIG. 3 may be combined.

[0173] The technical problem addressed by the method illustrated in FIG. 3 is how to properly manage timing advance adjustments and transmission parameters in asymmetric DL sTRP and UL mTRP scenarios where different transmission paths may have varying path loss characteristics. Specifically, the problem involves determining the appropriate TCI states and quasi co-location assumptions for different stages of the random access procedure (e.g., PRACH transmission, RAR reception, PUSCH transmission, and PDSCH reception) when some TCI states are associated with path loss offsets while others are not, and when the downlink control information provides different bit values in the PRACH association field. The advantageous technical effect achieved by the method illustrated in FIG. 3 is the optimization of transmission efficiency and reliability in asymmetric DL sTRP and UL mTRP scenarios by dynamically selecting the most appropriate TCI states based on path loss offset associations and DCI indications. This method ensures that the user equipment can adaptively choose between TCI states with or without path loss offsets depending on the signaled bit values, thereby enabling better path loss compensation, improved power control, and enhanced spatial parameter alignment through proper quasi co-location assumptions across different transmission stages, ultimately leading to more robust communication performance in asymmetric DL sTRP and UL mTRP scenarios.

[0174] FIG. 4 is a flowchart illustrating a method / process 400 performed by a BS for timing advance (TA) adjustments under asymmetric downlink (DL) single transmission and reception point (sTRP) and uplink (UL) multiple transmission and reception point (mTRP) scenarios, according to an example implementation of the present disclosure.

[0175] In the action 402, the process 400 may start by transmitting, to a user equipment (UE), configuration information configuring a transmission configuration indication (TCI) state list.

[0176] In the action 404, the process 400 may transmit, to the UE, downlink control information (DCI) for initiating a Random Access (RA) procedure, where the DCI may include a physical random access channel (PRACH) association field. The configuration information and the DCI may cause the UE to: in response to determining that at least one TCI state included in the TCI state list is associated with a path loss (PL) offset and the PRACH association field indicates a first bit field index: transmit, to the BS, a PRACH based on a first TCI state that is associated with the PL offset; receive, from the BS, a random access response (RAR) by assuming that first demodulation reference signal (DM-RS) antenna ports of the RAR are quasi co-located with second DM-RS antenna ports associated with Physical Downlink Control Channel (PDCCH) receptions in a control resource set (CORESET) for a Type1-PDCCH common search space (CSS) set; transmit, to the BS, a physical uplink shared channel (PUSCH) scheduled by the RAR based on the first TCI state; and receive, from the BS, a Physical Downlink Shared Channel (PDSCH) in response to the PUSCH by assuming that third DM-RS antenna ports of the PDSCH are quasi co-located with the second DM-RS antenna ports; and in response to determining that the at least one TCI state included in the TCI state list is associated with the PL offset and the PRACH association field indicates a second bit field index: transmit, to the BS, the PRACH based on a second TCI state that is not associated with the PL offset; receive, from the BS, the RAR by assuming that the first DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports; transmit, to the BS, the PUSCH scheduled by the RAR based on the second TCI state; and receive, from the BS, the PDSCH in response to the PUSCH by assuming that the third DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports. The process 400 may then end.

[0177] In some implementations, the first bit field index may correspond to a first bit value, and the second bit field index may correspond to a second bit value.

[0178] In some implementations, receiving, from the BS, the RAR by assuming that the first DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports may include receiving, from the BS, the RAR by assuming that the first DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports with respect to doppler shift, doppler spread, average delay, delay spread, and spatial receiver (RX) parameters, and receiving, from the BS, the PDSCH in response to the PUSCH by assuming that the third DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports may include receiving, from the BS, the PDSCH in response to the PUSCH by assuming that the third DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports with respect to doppler shift, doppler spread, average delay, delay spread, and spatial RX parameters.

[0179] In some implementations, the configuration information may further configure a first timing advance group (TAG) and a second TAG. The configuration information and the DCI may further cause the UE to: in response to determining that (i) the first TAG and the second TAG are configured and (ii) the at least one TCI state included in the TCI state list is associated with the PL offset: receive, from the BS, a first information element (IE) configuring a first TA offset for transmissions using a first spatial filter that is associated with the first TCI state, and receive, from the BS, a second IE configuring a second TA offset for transmissions using a second spatial filter that is associated with the second TCI state.

[0180] In some implementations, the PRACH association field may further indicate whether the first TCI state or the second TCI state is applied for a path loss calculation. The configuration information and the DCI further cause the UE to: in response to determining that the PRACH association field indicates that the first TCI state is applied for the path loss calculation, calculate a first path loss based on the first TCI state; and in response to determining that the PRACH association field indicates that the second TCI state is applied for the path loss calculation, calculate a second path loss based on the second TCI state.

[0181] The steps / actions shown in FIG. 4 should not be construed as necessarily order dependent. The order in which the process is described is not intended to be construed as a limitation. Moreover, some of the actions shown in FIG. 4 may be omitted in some implementations and one or more actions shown in FIG. 4 may be combined.

[0182] The method illustrated in FIG. 4 is similar to that in FIG. 3, except that it is described from the perspective of the BS (instead of the UE).

[0183] FIG. 5 is a block diagram illustrating a node 500 for wireless communication in accordance with various aspects of the present disclosure. As illustrated in FIG. 5, a node 500 may include a transceiver 520, a processor 528, a memory 534, one or more presentation components 538, and at least one antenna 536. The node 500 may also include a radio frequency (RF) spectrum band module, a BS communications module, a network communications module, and a system communications management module, Input / Output (I / O) ports, I / O components, and a power supply (not illustrated in FIG. 5).

[0184] Each of the components may directly or indirectly communicate with each other over one or more buses 540. The node 500 may be a UE or a BS that performs various functions disclosed with reference to FIGS. 1 through 4.

[0185] The transceiver 520 has a transmitter 522 (e.g., transmitting / transmission circuitry) and a receiver 524 (e.g., receiving / reception circuitry) and may be configured to transmit and / or receive time and / or frequency resource partitioning information. The transceiver 520 may be configured to transmit in different types of subframes and slots including, but not limited to, usable, non-usable, and flexibly usable subframes and slot formats. The transceiver 520 may be configured to receive data and control channels.

[0186] The node 500 may include a variety of computer-readable media. Computer-readable media may be any available media that may be accessed by the node 500 and include volatile (and / or non-volatile) media and removable (and / or non-removable) media.

[0187] The computer-readable media may include computer-storage media and communication media. Computer-storage media may include both volatile (and / or non-volatile media), and removable (and / or non-removable) media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or data.

[0188] Computer-storage media may include RAM, ROM, EPROM, EEPROM, flash memory (or other memory technology), CD-ROM, Digital Versatile Disks (DVD) (or other optical disk storage), magnetic cassettes, magnetic tape, magnetic disk storage (or other magnetic storage devices), etc. Computer-storage media may not include a propagated data signal. Communication media may typically embody computer-readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave, or other transport mechanisms and include any information delivery media.

[0189] The term “modulated data signal” may mean a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. Communication media may include wired media, such as a wired network or direct-wired connection, and wireless media, such as acoustic, RF, infrared, and other wireless media. Combinations of any of the above listed components should also be included within the scope of computer-readable media.

[0190] The memory 534 may include computer-storage media in the form of volatile and / or non-volatile memory. The memory 534 may be removable, non-removable, or a combination thereof. Example memory may include solid-state memory, hard drives, optical-disc drives, etc. As illustrated in FIG. 5, the memory 534 may store a computer-readable and / or computer-executable instructions 532 (e.g., software codes) that are configured to, when executed, cause the processor 528 to perform various functions disclosed herein, for example, with reference to FIGS. 1 through 4. Alternatively, the instructions 532 may not be directly executable by the processor 528 but may be configured to cause the node 500 (e.g., when compiled and executed) to perform various functions disclosed herein.

[0191] The processor 528 (e.g., having processing circuitry) may include an intelligent hardware device, e.g., a Central Processing Unit (CPU), a microcontroller, an ASIC, etc. The processor 528 may include memory. The processor 528 may process the data 530 and the instructions 532 received from the memory 534, and information transmitted and received via the transceiver 520, the baseband communications module, and / or the network communications module. The processor 528 may also process information to send to the transceiver 520 for transmission via the antenna 536 to the network communications module for transmission to a CN.

[0192] One or more presentation components 538 may present data indications to a person or another device. Examples of presentation components 538 may include a display device, a speaker, a printing component, a vibrating component, etc.

[0193] In view of the present disclosure, it is obvious that various techniques may be used for implementing the disclosed concepts without departing from the scope of those concepts. Moreover, while the concepts have been disclosed with specific reference to certain implementations, a person of ordinary skill in the art may recognize that changes may be made in form and detail without departing from the scope of those concepts. As such, the disclosed implementations are to be considered in all respects as illustrative and not restrictive. It should also be understood that the present disclosure is not limited to the particular implementations disclosed and many rearrangements, modifications, and substitutions are possible without departing from the scope of the present disclosure.

Claims

1. A user equipment (UE) for timing advance (TA) adjustments under asymmetric downlink (DL) single transmission and reception point (sTRP) and uplink (UL) multiple transmission and reception point (mTRP) scenarios, the UE comprising: 　　　　at least one processor; and 　　　　at least one non-transitory computer-readable medium coupled to at least one processor and storing one or more computer-executable instructions that, when executed by the at least one processor, cause the UE to: 　　　　　　　　receive, from a Base Station (BS), configuration information configuring a transmission configuration indication (TCI) state list; 　　　　　　　　receive, from the BS, downlink control information (DCI) for initiating a Random Access (RA) procedure, wherein the DCI comprises a physical random access channel (PRACH) association field; 　　　　　　　　in response to determining that at least one TCI state included in the TCI state list is associated with a path loss (PL) offset and the PRACH association field indicates a first bit field index: 　　　　　　　　　　　　transmit, to the BS, a PRACH based on a first TCI state that is associated with the PL offset; 　　　　　　　　　　　　receive, from the BS, a random access response (RAR) by assuming that first demodulation reference signal (DM-RS) antenna ports of the RAR are quasi co-located with second DM-RS antenna ports associated with Physical Downlink Control Channel (PDCCH) receptions in a control resource set (CORESET) for a Type1-PDCCH common search space (CSS) set; 　　　　　　　　　　　　transmit, to the BS, a physical uplink shared channel (PUSCH) scheduled by the RAR based on the first TCI state; and 　　　　　　　　　　　　receive, from the BS, a Physical Downlink Shared Channel (PDSCH) in response to the PUSCH by assuming that third DM-RS antenna ports of the PDSCH are quasi co-located with the second DM-RS antenna ports; and 　　　　　　　　in response to determining that the at least one TCI state included in the TCI state list is associated with the PL offset and the PRACH association field indicates a second bit field index: 　　　　　　　　　　　　transmit, to the BS, the PRACH based on a second TCI state that is not associated with the PL offset; 　　　　　　　　　　　　receive, from the BS, the RAR by assuming that the first DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports; 　　　　　　　　　　　　transmit, to the BS, the PUSCH scheduled by the RAR based on the second TCI state; and 　　　　　　　　　　　　receive, from the BS, the PDSCH in response to the PUSCH by assuming that the third DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports.

2. The UE of claim 1, wherein: 　　　　the first bit field index corresponds to a first bit value, and 　　　　the second bit field index corresponds to a second bit value.

3. The UE of claim 1, wherein: 　　　　receiving, from the BS, the RAR by assuming that the first DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports comprises receiving, from the BS, the RAR by assuming that the first DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports with respect to doppler shift, doppler spread, average delay, delay spread, and spatial receiver (RX) parameters, and 　　　　receiving, from the BS, the PDSCH in response to the PUSCH by assuming that the third DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports comprises receiving, from the BS, the PDSCH in response to the PUSCH by assuming that the third DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports with respect to doppler shift, doppler spread, average delay, delay spread, and spatial RX parameters.

4. The UE of claim 1, wherein the configuration information further configures a first timing advance group (TAG) and a second TAG.

5. The UE of claim 4, wherein the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to: 　　　　in response to determining that (i) the first TAG and the second TAG are configured and (ii) the at least one TCI state included in the TCI state list is associated with the PL offset: 　　　　　　　　receive, from the BS, a first information element (IE) configuring a first TA offset for transmissions using a first spatial filter that is associated with the first TCI state, and 　　　　　　　　receive, from the BS, a second IE configuring a second TA offset for transmissions using a second spatial filter that is associated with the second TCI state.

6. The UE of claim 1, wherein: 　　　　the PRACH association field further indicates whether the first TCI state or the second TCI state is applied for a path loss calculation.

7. The UE of claim 6, wherein the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to: 　　　　 in response to determining that the PRACH association field indicates that the first TCI state is applied for the path loss calculation, calculate a first path loss based on the first TCI state; and 　　　　in response to determining that the PRACH association field indicates that the second TCI state is applied for the path loss calculation, calculate a second path loss based on the second TCI state.

8. A method performed by a user equipment (UE) for timing advance (TA) adjustments under asymmetric downlink (DL) single transmission and reception point (sTRP) and uplink (UL) multiple transmission and reception point (mTRP) scenarios, the method comprising: 　　　　receiving, from a Base Station (BS), configuration information configuring a transmission configuration indication (TCI) state list; 　　　　receiving, from the BS, downlink control information (DCI) for initiating a Random Access (RA) procedure, wherein the DCI comprises a physical random access channel (PRACH) association field; 　　　　in response to determining that at least one TCI state included in the TCI state list is associated with a path loss (PL) offset and the PRACH association field indicates a first bit field index: 　　　　　　　　transmitting, to the BS, a PRACH based on a first TCI state that is associated with the PL offset; 　　　　　　　　receiving, from the BS, a random access response (RAR) by assuming that first demodulation reference signal (DM-RS) antenna ports of the RAR are quasi co-located with second DM-RS antenna ports associated with Physical Downlink Control Channel (PDCCH) receptions in a control resource set (CORESET) for a Type1-PDCCH common search space (CSS) set; 　　　　　　　　transmitting, to the BS, a physical uplink shared channel (PUSCH) scheduled by the RAR based on the first TCI state; and 　　　　　　　　receiving, from the BS, a Physical Downlink Shared Channel (PDSCH) in response to the PUSCH by assuming that third DM-RS antenna ports of the PDSCH are quasi co-located with the second DM-RS antenna ports; and 　　　　in response to determining that the at least one TCI state included in the TCI state list is associated with the PL offset and the PRACH association field indicates a second bit field index: 　　　　　　　　transmitting, to the BS, the PRACH based on a second TCI state that is not associated with the PL offset; 　　　　　　　　receiving, from the BS, the RAR by assuming that the first DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports; 　　　　　　　　transmitting, to the BS, the PUSCH scheduled by the RAR based on the second TCI state; and 　　　　　　　　receiving, from the BS, the PDSCH in response to the PUSCH by assuming that the third DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports.

9. A base station (BS) for timing advance (TA) adjustments under asymmetric downlink (DL) single transmission and reception point (sTRP) and uplink (UL) multiple transmission and reception point (mTRP) scenarios, the BS comprising: 　　　　at least one processor; and 　　　　at least one non-transitory computer-readable medium coupled to at least one processor and storing one or more computer-executable instructions that, when executed by the at least one processor, cause the BS to: 　　　　　　　　transmit, to a user equipment (UE), configuration information configuring a transmission configuration indication (TCI) state list; and 　　　　　　　　transmit, to the UE, downlink control information (DCI) for initiating a Random Access (RA) procedure, wherein the DCI comprises a physical random access channel (PRACH) association field, wherein the configuration information and the DCI cause the UE to: 　　　　　　　　　　　　in response to determining that at least one TCI state included in the TCI state list is associated with a path loss (PL) offset and the PRACH association field indicates a first bit field index: 　　　　　　　　　　　　　　　　transmit, to the BS, a PRACH based on a first TCI state that is associated with the PL offset; 　　　　　　　　　　　　　　　　receive, from the BS, a random access response (RAR) by assuming that first demodulation reference signal (DM-RS) antenna ports of the RAR are quasi co-located with second DM-RS antenna ports associated with Physical Downlink Control Channel (PDCCH) receptions in a control resource set (CORESET) for a Type1-PDCCH common search space (CSS) set; 　　　　　　　　　　　　　　　　transmit, to the BS, a physical uplink shared channel (PUSCH) scheduled by the RAR based on the first TCI state; and 　　　　　　　　　　　　　　　　receive, from the BS, a Physical Downlink Shared Channel (PDSCH) in response to the PUSCH by assuming that third DM-RS antenna ports of the PDSCH are quasi co-located with the second DM-RS antenna ports; and 　　　　　　　　　　　　in response to determining that the at least one TCI state included in the TCI state list is associated with the PL offset and the PRACH association field indicates a second bit field index: 　　　　　　　　　　　　　　　　transmit, to the BS, the PRACH based on a second TCI state that is not associated with the PL offset; 　　　　　　　　　　　　　　　　receive, from the BS, the RAR by assuming that the first DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports; 　　　　　　　　　　　　　　　　transmit, to the BS, the PUSCH scheduled by the RAR based on the second TCI state; and 　　　　　　　　　　　　　　　　receive, from the BS, the PDSCH in response to the PUSCH by assuming that the third DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports.

10. The BS of claim 9, wherein: 　　　　the first bit field index corresponds to a first bit value, and 　　　　the second bit field index corresponds to a second bit value.

11. The BS of claim 9, wherein: 　　　　receiving, from the BS, the RAR by assuming that the first DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports comprises receiving, from the BS, the RAR by assuming that the first DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports with respect to doppler shift, doppler spread, average delay, delay spread, and spatial receiver (RX) parameters, and 　　　　receiving, from the BS, the PDSCH in response to the PUSCH by assuming that the third DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports comprises receiving, from the BS, the PDSCH in response to the PUSCH by assuming that the third DM-RS antenna ports are quasi co-located with the second DM-RS antenna ports with respect to doppler shift, doppler spread, average delay, delay spread, and spatial RX parameters.

12. The BS of claim 9, wherein the configuration information further configures a first timing advance group (TAG) and a second TAG.

13. The BS of claim 12, wherein the configuration information and the DCI further cause the UE to: 　　　　in response to determining that (i) the first TAG and the second TAG are configured and (ii) the at least one TCI state included in the TCI state list is associated with the PL offset: 　　　　　　　　receive, from the BS, a first information element (IE) configuring a first TA offset for transmissions using a first spatial filter that is associated with the first TCI state, and 　　　　　　　　receive, from the BS, a second IE configuring a second TA offset for transmissions using a second spatial filter that is associated with the second TCI state.

14. The BS of claim 9, wherein: 　　　　the PRACH association field further indicates whether the first TCI state or the second TCI state is applied for a path loss calculation.

15. The BS of claim 14, wherein the configuration information and the DCI further cause the UE to: 　　　　 in response to determining that the PRACH association field indicates that the first TCI state is applied for the path loss calculation, calculate a first path loss based on the first TCI state; and 　　　　in response to determining that the PRACH association field indicates that the second TCI state is applied for the path loss calculation, calculate a second path loss based on the second TCI state.

Images