Synchronization for multiple transmit-receive point communications in non-terrestrial networks

Abstract

Methods, systems, and devices for wireless communication are described. Some wireless communication systems may support non-terrestrial network (NTN) signaling between both terrestrial and non-terrestrial devices. A user equipment (UE) supporting such NTN signaling may receive a downlink message indicating a first configuration for a first transmit-receive point corresponding to a first cell of the NTN and a second configuration for a second transmit-receive point corresponding to a second cell of the NTN. The UE may then perform one or more synchronization measurements to synchronize uplink communications with the first transmit-receive point and the second transmit-receive point, and to perform multiple transmit-receive point communications in the NTN. The UE may then transmit one or more uplink messages to the first transmit-receive point, the second transmit-receive point, or both according to the one or more synchronization measurements.

Description

[0001] Cross-reference

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 057,630, entitled "SYNCHRONIZATION FOR MULTI-TRANSMISSION RECEPTION POINT COMMUNICATIONS IN NON-TERRESTRIAL NETWORKS", filed on November 21, 2022, by Liu et al., which is assigned to the assignee of the present application and is hereby incorporated by reference in its entirety. Technical Field

[0003] The following relates to wireless communications, including synchronization for multi-transmission reception point (mTRP) communications in non-terrestrial networks (NTNs). Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, etc. These systems may be capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multi-access systems include fourth-generation (4G) systems (such as Long-Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ techniques such as code-division multiple access (CDMA), time-division multiple access (TDMA), frequency-division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency-division multiplexing (DFT-S-OFDM). A wireless multi-access communication system may include one or more base stations, each of which supports wireless communication of communication devices, which may be referred to as user equipment (UE). Summary of the Invention

[0005] The described techniques relate to improved methods, systems, devices, and apparatuses for supporting synchronization for multi-transmit receive point (mTRP) communications in a non-terrestrial network (NTN). For example, the described techniques provide support for increased coverage and signaling support for mTRP communications in an NTN. For example, a network entity may utilize information to configure a user equipment (UE) to perform mTRP communications for an NTN. Such information may include one or more downlink messages that include a configuration for a serving cell (associated with a first NTN TRP) and additional NTN-related configurations for non-serving cells or virtual cells (associated with one or more secondary NTN TRPs). Such mTRP NTN configuration information may allow the UE to perform one or more synchronization measurements with the serving cell and non-serving cells and, accordingly, convey uplink signaling to multiple TRPs present in the NTN.

[0006] A method for wireless communication at a UE is described. The method may include: receiving a downlink message that indicates a first configuration for a first TRP corresponding to a first cell of an NTN and a second configuration for a second TRP corresponding to a second cell of the NTN; performing one or more synchronization measurements for synchronizing uplink communication with the first TRP and the second TRP based on the first configuration and the second configuration of the downlink message; and sending one or more uplink messages to the first TRP, the second TRP, or both based on the one or more synchronization measurements.

[0007] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus: to receive a downlink message that indicates a first configuration for a first TRP corresponding to a first cell of an NTN and a second configuration for a second TRP corresponding to a second cell of the NTN; to perform one or more synchronization measurements for synchronizing uplink communication with the first TRP and the second TRP based on the first configuration and the second configuration of the downlink message; and to send one or more uplink messages to the first TRP, the second TRP, or both based on the one or more synchronization measurements.

[0008] Describes another apparatus for wireless communication at a UE. The apparatus may include: means for receiving a downlink message that indicates a first configuration for a first TRP corresponding to a first cell of an NTN and a second configuration for a second TRP corresponding to a second cell of the NTN; means for performing one or more synchronization measurements for synchronizing uplink communication with the first TRP and the second TRP based on the first configuration and the second configuration of the downlink message; and means for sending one or more uplink messages to the first TRP, the second TRP, or both according to the one or more synchronization measurements.

[0009] Describes a non-transitory computer-readable medium storing code for wireless communication at a UE. The code may include instructions executable by a processor to perform the following operations: receive a downlink message that indicates a first configuration for a first TRP corresponding to a first cell of an NTN and a second configuration for a second TRP corresponding to a second cell of the NTN; perform one or more synchronization measurements for synchronizing uplink communication with the first TRP and the second TRP based on the first configuration and the second configuration of the downlink message; and send one or more uplink messages to the first TRP, the second TRP, or both according to the one or more synchronization measurements.

[0010] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the downlink message includes a control resource set (CORESET) configuration message, and the methods, apparatuses, and non-transitory computer-readable media may include additional operations, features, means, or instructions for the following actions: receive an indication of the first TRP based on a first CORESET pool index of the CORESET configuration message, and receive an indication of the second TRP based on a second CORESET pool index of the CORESET configuration message.

[0011] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for the following actions: decode first transmission configuration indicator (TCI) state information associated with the first CORESET pool index and second TCI state information associated with the second CORESET pool index, where the first TCI state information includes the first configuration for the first TRP and the second TCI state information includes the second configuration for the second TRP.

[0012] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the downlink message further includes a unified TCI status information message, and the methods, apparatuses, and non-transitory computer-readable media may include additional operations, features, components, or instructions for the following actions: receiving the first configuration for the first TRP and the second configuration for the second TRP based on the unified TCI status information message.

[0013] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the unified TCI status information message includes combined downlink and uplink TCI status information, or separate downlink and uplink TCI status information, synchronization signal block (SSB)-machine type communication (MTC) information, or any combination thereof.

[0014] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for the following actions: performing one or more synchronization measurements on one or more SSBs associated with the first cell and the second cell of the NTN based on the unified TCI status information message by applying corresponding timing advance to the one or more synchronization measurements.

[0015] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the downlink message includes a spatial relation information message, and the methods, apparatuses, and non-transitory computer-readable media may include additional operations, features, components, or instructions for the following actions: receiving the first configuration for the first TRP and the second configuration for the second TRP based on the spatial relation information message.

[0016] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the spatial relation information message includes an SSB information field corresponding to the first cell, the second cell, or both, and the SSB information field indicates the first configuration for the first TRP, the second configuration for the second TRP, or both.

[0017] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the spatial relation information message includes sounding reference signal (SRS) positioning information corresponding to the first configuration for the first TRP and the second configuration for the second TRP.

[0018] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the spatial relation information message includes an indication of a sounding reference signal (SRS) corresponding to the first configuration for the first TRP and the second configuration for the second TRP.

[0019] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the spatial relation information message includes an indication of a physical uplink control channel corresponding to the first configuration for the first TRP and the second configuration for the second TRP.

[0020] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for the following actions: sending a message to a network entity, the message indicating the UE's ability to communicate with the first TRP and the second TRP in the NTN.

[0021] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the second configuration includes a configuration of a virtual cell, and performing the one or more synchronization measurements may include operations, features, components, or instructions for the following actions: performing the one or more synchronization measurements with respect to the virtual cell spatially located between the first TRP and the second TRP to at least partially synchronize the uplink communication with the first TRP and the second TRP; and sending the one or more uplink messages to the first TRP and the second TRP based on performing the one or more synchronization measurements with respect to the virtual cell.

[0022] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving the downlink message may include operations, features, components, or instructions for the following actions: receiving a third configuration for a third TRP corresponding to a third cell of the NTN; and based on the third configuration, performing the one or more synchronization measurements to synchronize the uplink communication with the first TRP, the second TRP, and the third TRP.

[0023] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first configuration for the first TRP and the second configuration for the second TRP include timing information, non-terrestrial network configuration information, physical cell identifiers, virtual cell identifiers, or any combination thereof.

[0024] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the one or more synchronization measurements include Doppler frequency shift pre-compensation measurements associated with the first TRP and the second TRP in the NTN.

[0025] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first configuration for the first TRP includes a first physical cell identifier or a first virtual cell identifier, and the second configuration for the second TRP includes a second physical cell identifier or a second virtual cell identifier.

[0026] Describes a method for wireless communication at a network entity. The method may include: sending a downlink message to a UE, the downlink message indicating a first configuration for a first TRP corresponding to a first cell of an NTN and a second configuration for a second TRP corresponding to a second cell of the NTN; based on the first configuration and the second configuration of the downlink message, performing one or more synchronization measurements for synchronizing communication with the first TRP, the second TRP, and the UE; and receiving one or more uplink messages from the UE according to the one or more synchronization measurements.

[0027] Describes an apparatus for wireless communication at a network entity. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: send a downlink message to a UE, the downlink message indicating a first configuration for a first TRP corresponding to a first cell of an NTN and a second configuration for a second TRP corresponding to a second cell of the NTN; based on the first configuration and the second configuration of the downlink message, perform one or more synchronization measurements for synchronizing communication with the first TRP, the second TRP, and the UE; and receive one or more uplink messages from the UE according to the one or more synchronization measurements.

[0028] Describes another apparatus for wireless communication at a network entity. The apparatus may include: means for sending a downlink message to a UE, the downlink message indicating a first configuration for a first TRP corresponding to a first cell of an NTN and a second configuration for a second TRP corresponding to a second cell of the NTN; means for performing one or more synchronization measurements for synchronizing communication with the first TRP, the second TRP, and the UE based on the first configuration and the second configuration of the downlink message; and means for receiving one or more uplink messages from the UE according to the one or more synchronization measurements.

[0029] Describes a non-transitory computer-readable medium storing code for wireless communication at a network entity. The code may include instructions executable by a processor to perform the following operations: send a downlink message to a UE, the downlink message indicating a first configuration for a first TRP corresponding to a first cell of an NTN and a second configuration for a second TRP corresponding to a second cell of the NTN; based on the first configuration and the second configuration of the downlink message, perform one or more synchronization measurements for synchronizing communication with the first TRP, the second TRP, and the UE; and receive one or more uplink messages from the UE according to the one or more synchronization measurements.

[0030] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the downlink message includes a CORESET configuration message, and the methods, apparatuses, and non-transitory computer-readable media may include additional operations, features, components, or instructions for the following actions: sending an indication of the first TRP to the UE based on a first CORESET pool index of the CORESET configuration message, and sending an indication of the second TRP to the UE based on a second CORESET pool index of the CORESET configuration message.

[0031] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the downlink message further includes first TCI state information associated with the first CORESET pool index and second TCI state information associated with the second CORESET pool index, and the first TCI state information includes the first configuration for the first TRP and the second TCI state information includes the second configuration for the second TRP.

[0032] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the downlink message further includes a unified TCI state information message, and the methods, apparatuses, and non-transitory computer-readable media may include additional operations, features, components, or instructions for the following actions: sending the first configuration for the first TRP and the second configuration for the second TRP to the UE based on the unified TCI state information message.

[0033] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the unified TCI state information message includes combined downlink and uplink TCI state information, or separate downlink and uplink TCI state information, SSB-machine type communication information, or a combination thereof.

[0034] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the downlink message includes a spatial relation information message, and the methods, apparatuses, and non-transitory computer-readable media may include additional operations, features, components, or instructions for the following actions: sending the first configuration for the first TRP and the second configuration for the second TRP to the UE based on the spatial relation information message.

[0035] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the spatial relation information message includes an SSB information field corresponding to the first cell, the second cell, or both, and the SSB information field indicates the first configuration for the first TRP, the second configuration for the second TRP, or both.

[0036] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the spatial relation information message includes SRS positioning information corresponding to the first configuration for the first TRP and the second configuration for the second TRP.

[0037] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for the following actions: receiving a message that indicates the UE's ability to communicate with the first TRP and the second TRP in the NTN.

[0038] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the second configuration includes a configuration of a virtual cell, and the methods, apparatuses, and non-transitory computer-readable media may include additional operations, features, components, or instructions for the following actions: receiving, from the UE, one or more uplink messages synchronized to the virtual cell; and performing one or more post-processing procedures to synchronize the one or more uplink messages to the timing of the first cell and the second cell.

[0039] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving the downlink message may include operations, features, components, or instructions for the following actions: transmitting a third configuration for a third TRP corresponding to a third cell of the NTN; and based on the third configuration, performing the one or more synchronization measurements to synchronize the communication with the first TRP, the second TRP, the third TRP, and the UE. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Figure 1 、 Figure 2 and Figure 3 illustrate examples of wireless communication systems supporting synchronization for multi-transmit receive point (mTRP) communication in a non-terrestrial network (NTN) in accordance with one or more aspects of the present disclosure.

[0041] Figure 4 illustrate examples of process flows supporting synchronization for mTRP communication in an NTN in accordance with one or more aspects of the present disclosure.

[0042] Figure 5 and Figure 6 illustrate block diagrams of devices supporting synchronization for mTRP communication in an NTN in accordance with one or more aspects of the present disclosure.

[0043] Figure 7 illustrate block diagrams of communication managers supporting synchronization for mTRP communication in an NTN in accordance with one or more aspects of the present disclosure.

[0044] Figure 8Illustrates a diagram of a system including a device that supports synchronization for mTRP communication in NTN according to one or more aspects of the present disclosure.

[0045] Figure 9 and Figure 10 Illustrates a block diagram of a device that supports synchronization for mTRP communication in NTN according to one or more aspects of the present disclosure.

[0046] Figure 11 Illustrates a block diagram of a communication manager that supports synchronization for mTRP communication in NTN according to one or more aspects of the present disclosure.

[0047] Figure 12 Illustrates a diagram of a system including a device that supports synchronization for mTRP communication in NTN according to one or more aspects of the present disclosure.

[0048] Figures 13 to 17 Illustrates a flowchart showing a method that supports synchronization for mTRP communication in NTN according to one or more aspects of the present disclosure. Detailed Description

[0049] Some wireless communication systems may support multi-transmit receive point TRP (mTRP) communication, which enables network entities to communicate with user equipment (UE) using more than one TRP. Such mTRP communication can improve overall network performance and coverage, improve mobility between cells, and reduce signaling overhead. To communicate effectively with multiple TRPs, a UE may synchronize with different cells associated with multiple different TRPs, for example, by applying different timing advances to communications received from or transmitted to multiple TRPs. Such a synchronization process for mTRP communication is relatively accurate in a terrestrial-based network, where Doppler drift and other timing issues are relatively small.

[0050] However, in a non-terrestrial network (NTN), mTRP synchronization becomes challenging due to increased Doppler drift and timing mismatches between devices that are further apart from each other (e.g., relative to the distances between devices in a conventional terrestrial-based network). Thus, NTN networks may support various different techniques to accurately compensate for such differences between terrestrial-based networks and NTNs to support mTRP communication.

[0051] In some specific implementations, a network entity may utilize information to configure a UE to perform mTRP communication for NTN. For example, the UE may receive configuration information of a serving cell and additional NTN-related configurations for non-serving cells, TRPs, or virtual cells, and the additional NTN-related configurations may allow the UE to communicate with multiple TRPs existing in the NTN. In such specific implementations, the network entity may configure the UE by using multiple NTN mTRP configurations instead of a single NTN TRP configuration.

[0052] In some examples, the network entity may signal serving cell information and non-serving cell information for mTRP in a downlink transmission configuration indicator (TCI) state associated with a control resource set (CORESET) message. In some other examples, the network entity may use a unified TCI framework message to signal serving cell information and non-serving cell information for mTRP. In some other examples, the network entity may use an uplink spatial relation information message to signal serving cell information and non-serving cell information for mTRP. Additionally or alternatively, the UE may use NTN mTRP configuration information to synchronize with a virtual cell or a reference point between multiple TRPs, such that the UE transmits an average signal to two TRPs instead of synchronizing with the two TRPs separately.

[0053] Aspects of the present disclosure have been initially described in the context of a wireless communication system (e.g., a wireless communication system in an NTN setup). Aspects of the present disclosure are further illustrated by process flows, device diagrams, system diagrams, and flowcharts related to synchronization for mTRP communication in NTN and are described with reference to these process flows, device diagrams, system diagrams, and flowcharts.

[0054] Figure 1 An example of a wireless communication system 100 supporting synchronization for mTRP communication in NTN in accordance with one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to other systems and radio technologies including future systems and radio technologies not explicitly mentioned herein.

[0055] Network entity 105 can be dispersed throughout a geographical area to form a wireless communication system 100 and can include devices in different forms or having different capabilities. In various examples, network entity 105 can be referred to as a network element, a mobility element, a radio access network (RAN) node, or network equipment, among other designations. In some examples, network entity 105 and UE 115 can communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 can support a coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 can establish one or more communication links 125. Coverage area 110 can be an example of a geographical area within which network entity 105 and UE 115 can support signal communication according to one or more radio access technologies (RATs).

[0056] UE 115 can be dispersed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be a device in different forms or having different capabilities. Figure 1 Some example UEs 115 are illustrated. The UEs 115 described herein may be capable of communicating with various types of devices (such as other UEs 115 or network entity 105 as Figure 1 shown).

[0057] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) can be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, a device, an equipment, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node can be a UE 115. As another example, the node can be a network entity 105. As yet another example, a first node can be configured to communicate with a second node or a third node. In one aspect of this example, the first node can be a UE 115, the second node can be a network entity 105, and the third node can be a UE 115. In another aspect of this example, the first node can be a UE 115, the second node can be a network entity 105, and the third node can be a network entity 105. In other aspects of this example, the first node, the second node, and the third node can be different from these examples. Similarly, references to the UE 115, the network entity 105, the device, the equipment, the computing system, etc. can include the disclosure of the UE 115, the network entity 105, the device, the equipment, the computing system, etc. as nodes. For example, the disclosure that the UE 115 is configured to receive information from the network entity 105 also discloses that the first node is configured to receive information from the second node.

[0058] In some examples, the network entity 105 can communicate with the core network 130, or with each other, or both. For example, the network entity 105 can communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to the S1, N2, N3, or other interface protocols). In some examples, the network entity 105 can communicate with each other directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130) via the backhaul communication link 120 (e.g., according to the X2, Xn, or other interface protocols). In some examples, the network entity 105 can communicate with each other via the midhaul communication link 162 (e.g., according to the midhaul interface protocol) or the fronthaul communication link 168 (e.g., according to the fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, the midhaul communication link 162, or the fronthaul communication link 168 can be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), etc. or various combinations thereof. The UE 115 can communicate with the core network 130 via the communication link 155.

[0059] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, Node B, evolved Node B (eNB), next generation Node B or gigabit Node B (any of which may be referred to as gNB), 5G NB, next generation eNB (ng-eNB), home Node B, home evolved Node B, or other suitable terms). In some examples, the network entity 105 (e.g., base station 140) may be implemented in an integrated (e.g., monolithic, stand-alone) base station architecture that may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0060] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., disaggregated base station architecture, disaggregated RAN architecture) that may be configured to utilize a protocol stack physically or logically distributed between two or more network entities 105 (such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN))). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, an intelligent radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the disaggregated RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0061] The functional split between the CU 160, DU 165, and RU 170 is flexible and can support different functions, depending on which functions are performed at the CU 160, DU 165, or RU 170 (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof). For example, a functional split of the protocol stack can be employed between the CU 160 and DU 165 such that the CU 160 can support one or more layers of the protocol stack and the DU 165 can support one or more different layers of the protocol stack. In some examples, the CU 160 can host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functions and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 can be connected to one or more DU 165s or RU 170s, and one or more DU 165s or RU 170s can host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, media access control (MAC) layer) functions and signaling, and can each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack can be employed between the DU 165 and RU 170 such that the DU 165 can support one or more layers of the protocol stack and the RU 170 can support one or more different layers of the protocol stack. The DU 165 can support one or more different cells (e.g., via one or more RU 170s). In some cases, the functional split between the CU 160 and DU 165 or between the DU 165 and RU 170 can be within a protocol layer (e.g., some functions of a protocol layer can be performed by one of the CU 160, DU 165, or RU 170, while other functions of that protocol layer are performed by a different one of the CU 160, DU 165, or RU 170). The CU 160 can be further functionally split into a CU control plane (CU-CP) and a CU user plane (CU-UP) function. The CU 160 can be connected to one or more DU 165s via an intermediate transport communication link 162 (e.g., F1, F1-c, F1-u), and the DU 165 can be connected to one or more RU 170s via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the intermediate transport communication link 162 or the fronthaul communication link 168 can be implemented according to the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via these communication links.

[0062] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 104) may be controlled in part by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via the supported access and backhaul links (e.g., backhaul communication link 120). An IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate antenna set for relaying communication with the UE 115 or may share the same antenna (e.g., of an RU 170 of the IAB node 104) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) with the access network. In such cases, one or more components of the split RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0063] In the context of the techniques described herein being applied to a split RAN architecture, one or more components of the split RAN architecture may be configured to support synchronization for mTRP communication in NTN as described herein. For example, some operations described as being performed by the UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the split RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0064] The UE 115 may include or may be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or some other suitable term, where "device" may also be referred to as a unit, station, terminal, or client, etc. The UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, the UE 115 may include or may be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances, vehicles, meters, etc.

[0065] The UE 115 described herein may be capable of communicating with various types of devices, such as other UE 115s that may sometimes act as relays, and network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc., as Figure 1 shown.

[0066] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" may refer to a set of RF spectral resources having a defined physical layer structure for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion (e.g., bandwidth part (BWP)) of an RF spectral band that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operation, user data, or other signaling. The wireless communication system 100 may support communication with the UE 115 using carrier aggregation or multi-carrier operation. According to the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any part (e.g., entity, sub-entity) of the network entity 105. For example, the terms "transmit", "receive", or "communicate" when referring to the network entity 105 may refer to any part of the network entity 105 of the RAN (e.g., base station 140, CU 160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0067] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may refer to the resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier. In this case, the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., during the transmission duration) and a relatively high-order modulation scheme may correspond to a relatively high communication rate. The wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity for communication with UE 115.

[0068] One or more parameter sets of a carrier may be supported, and the parameter set may include subcarrier spacing (Δf) and cyclic prefix. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, UE 115 may be configured with multiple BWPs. In some examples, a single BWP of a carrier may be active at a given time, and the communication of UE 115 may be restricted to one or more active BWPs.

[0069] The time interval for a network entity 105 or UE 115 may be expressed as a multiple of a basic time unit, which may refer to, for example, the sampling period T s = 1 / (Δf max ·N f ) seconds, where Δf max may represent the supported subcarrier spacing, and N f may represent the supported discrete Fourier transform (DFT) size. The time intervals of communication resources may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0070] Each frame may include a plurality of consecutively numbered sub - frames or time slots, and each sub - frame or time slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into sub - frames, and each sub - frame may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the sub - carrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, a time slot may be further divided into a plurality of mini - slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f

[0071]

[0072]

[0073] sub - frames, time slots, mini - slots, or symbols may be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).Physical channels may be multiplexed according to various techniques for communication using a carrier. For example, one or more of time - division multiplexing (TDM) techniques, frequency - division multiplexing (FDM) techniques, or hybrid TDM - FDM techniques may be used to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region of a physical control channel (e.g., a control resource set (CORESET)) may be defined by a set of symbol periods and may extend across the system bandwidth of a carrier or a subset of that system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more of the UEs 115 may monitor or search a control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with the coded information for a control information format with a given payload size. The search space set may include: a common search space set configured to transmit control information to a plurality of UEs 115, and a UE - specific search space set for transmitting control information to a specific UE 115.​Network entity 105 may provide communication coverage via one or more cells (such as macro cells, small cells, hotspots, or other types of cells or any combination thereof). The term "cell" may refer to a logical communication entity for communicating with network entity 105 (e.g., using a carrier), and may be associated with an identifier for distinguishing adjacent cells (e.g., physical cell identifier (PCID), virtual cell identifier (VCID), or other identifier). In some examples, a cell may also refer to the coverage area 110 or a portion of the coverage area 110 (e.g., a sector) on which the logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the scope of such cells may range from a smaller area (e.g., a structure, a subset of a structure) to a larger area. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping the coverage areas 110, etc.

[0074] Macro cells generally cover a relatively large geographical area (e.g., with a radius of several kilometers) and may allow unrestricted access to UEs 115 having a service subscription with the network provider supporting the macro cell. Small cells may be associated with a lower power network entity 105 (e.g., a lower power base station 140) (compared to macro cells), and small cells may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UEs 115 having a service subscription with the network provider, or may provide restricted access to UEs 115 associated with the small cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). Network entity 105 may support one or more cells and may also use one or more component carriers to support communication via one or more cells.

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

[0076] In some examples, the network entity 105 (e.g., base station 140, RU 170) can be movable and thus provide communication coverage for a moving coverage area 110. In some examples, different coverage areas 110 associated with different technologies can overlap, but the different coverage areas 110 can be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies can be supported by different network entities 105. The wireless communication system 100 can include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

[0077] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, the network entities 105 (e.g., base stations 140) can have similar frame timings, and transmissions from different network entities 105 can be approximately aligned in time. For asynchronous operation, the network entities 105 can have different frame timings, and in some examples, transmissions from different network entities 105 can be misaligned in time. The techniques described herein can be used for either synchronous operation or asynchronous operation.

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

[0079] In some examples, UE 115 may be configured to support communicating directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 performing D2D communication in a group may be located within the coverage area 110 of a network entity 105 (e.g., base station 140, RU 170), and the network entity may support aspects of such D2D communication configured (e.g., scheduled) by the network entity 105. In some examples, one or more UEs 115 in such a group may be located outside the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, where each UE 115 transmits to each of the other UEs 115 in the group. In some examples, the network entity 105 may facilitate the scheduling of resources for D2D communication. In some other examples, D2D communication may be performed between UEs 115 without involving the network entity 105.

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

[0081] The wireless communication system 100 may operate using one or more frequency bands that can be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or the decimeter band because, in terms of length, the wavelength range is from approximately one decimeter to one meter. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clutter), but these waves may be sufficient to penetrate structures so that the macro cell can serve the UE 115 located indoors. Compared with communications using smaller frequencies and longer wavelengths in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers).

[0082] The wireless communication system 100 may also operate using the super-high frequency (SHF) band (which can be in the range of 3 GHz to 30 GHz (also referred to as the centimeter band)) or using the extremely high frequency (EHF) band of the spectrum (e.g., from 30 GHz to 300 GHz) (also referred to as the millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between the UE 115 and the network entity 105 (such as the base station 140, RU 170), and the EHF antennas of the corresponding devices may be smaller and closer spaced compared to UHF antennas. In some examples, such techniques may be facilitated using antenna arrays within the devices. However, the propagation of EHF transmissions may be affected by even greater attenuation and shorter ranges than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions using one or more different frequency regions, and the use of frequency bands designated across these frequency regions may vary by country or regulatory body.

[0083] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may use an unlicensed band (such as the 5 GHz industrial, scientific, and medical (ISM) band) to employ licensed-assisted access (LAA), long term evolution unlicensed (LTE-U) radio access technology, or NR technology. When operating using an unlicensed RF spectrum band, devices such as the network entity 105 and the UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operations using an unlicensed band may be based on a carrier aggregation configuration (e.g., LAA) in combination with a component carrier operating using a licensed band. Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, peer-to-peer (P2P) transmissions, device-to-device (D2D) transmissions, and so on.

[0084] The network entity 105 (e.g., base station 140, RU 170) or the UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the network entity 105 or the UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as at an antenna tower. In some examples, the antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a set of antenna ports arranged in multiple rows and columns that the network entity 105 may use for beamforming to support communication with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0085] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., network entity 105, UE 115) to shape or steer an antenna beam (e.g., transmit beam, receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals communicated via the antenna elements of an antenna array such that some signals propagating in a particular direction relative to the antenna array experience constructive interference while other signals experience destructive interference. The adjustment of the signals communicated via the antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to the signals carried via the antenna elements associated with the device. The adjustment associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).

[0086] The wireless communication system 100 may support NTN communication between various network nodes of the wireless communication system 100. For example, the wireless communication system 100 may be an example of an NTN that supports communication between each NTN node and each terrestrial network node. For example, as described herein, the network entity 105 may refer to a terrestrial communication device (such as the base station 140) or a non-terrestrial communication device (such as the satellite 185, balloon, drone, non-terrestrial node, high-altitude platform (HAP) station, or another non-terrestrial device). In some examples, the NTN network entity 105 may be connected to (e.g., communicate with) the terrestrial network entity 105 via a gateway. In some examples, the NTN network entity 105 may correspond to a first cell type (e.g., NTN cell type), and the terrestrial network entity 105 may correspond to a second cell type different from the first cell type (e.g., terrestrial cell type).

[0087] In some examples, the NTN network entity 105 may provide coverage to areas where the terrestrial network entity 105 may not be available. The channel corresponding to the NTN network entity 105 is characterized by strong line-of-sight conditions because the signal provided by the NTN network entity 105 may be reflected in the sky (e.g., as opposed to the signal corresponding to the terrestrial network entity 105 that may travel on the ground). The coverage area of the beam radiated from the NTN network entity 105 may have relatively clear boundaries (e.g., compared to the beam boundaries of the terrestrial network entity 105), and the UE 115 may operate within a single beam service area (e.g., except when the UE 115 is located at the boundary between two service areas). In some examples, the service area of the beam corresponding to the NTN network entity 105 may be larger than the service area of the beam corresponding to the terrestrial network entity 105.

[0088] The NTN network entity 105 (such as the satellite 185) may move over time and support various coverage scenarios. For example, the NTN network entity 105 may support a mobile cell or beam coverage scenario, where the cell coverage area or beam coverage area moves together with the satellite 185. Alternatively, the NTN network entity 105 may support a quasi-geostationary cell or beam coverage scenario, where the cell coverage area of the beam coverage area remains static for a certain period of time while the NTN network entity 105 moves through space.

[0089] Additionally or alternatively, the wireless communication system 100 may support one or more non-terrestrial nodes 190. For the purposes of this disclosure, the non-terrestrial node 190 may include but is not limited to aircraft, UAVs, drones, HAPs, etc. For example, as Figure 1 shown, the UE115 may be communicatively coupled to the satellite 185 (e.g., NTN node), the non-terrestrial node 190, or both via one or more communication links 125.

[0090] The wireless communication system 100 may support mTRP-based communication such that the base station or network entity 105 can communicate with the UE 115 using more than one TRP. Such mTRP communication can improve network performance, reliability, and throughput. In some examples, the wireless communication system may support mTRP-based uplink communication, such as mTRP-based PUCCH and PUSCH in a terrestrial network or NTN. In a terrestrial network scenario, the wireless communication system 100 may support intra-cell mTRP communication, where two or more TRPs may share the same physical cell identifier (PCI). In such cases, two TRPs may be mapped to different control resource set (CORESET) pool values (e.g., coresetPoolIndex values) corresponding to different associated TRPs, cells, or both, and the control resource set (CORESET) pool values may include one or more values configured in the CORESET of a downlink control channel configuration message (e.g., PDCCH-Config).

[0091] In some other specific implementations, the wireless communication system 100 may support inter-cell mTRP, where two or more TRPs may have different TRP / cell identifiers (e.g., physical cell ID (PCI)) and may be associated with a single timing advance value. In such specific implementations, the wireless communication system 100 may support time division multiplexing for reliable mTRP uplink repetition, and the serving cell PCI and the neighboring cell PCI may be mapped to different CORESET values (e.g., coresetPoolIndex values) by using the associated downlink TCI state, which includes additional TRP identification information, cell identification information (e.g., additionalPCI-r17 information), or both. Additionally or alternatively, for uplink configuration, mTRP serving cell communication may be based on the spatial relationship information of PUCCH or SRS signaling.

[0092] In some specific implementations, the wireless communication system 100 may use mTRP technology to support simultaneous uplink multi-panel transmission within a frequency range (e.g., FR1 or FR2) to improve system capacity. Additionally or alternatively, the wireless communication system 100 may support spatial division multiplexing, frequency division multiplexing, single-frequency network communication, or any combination thereof for PUSCH and PUCCH. mTRP communication may also support two TAs for inter-cell multi-DCI uplink mTRP, where the timing difference between mTRPs may be relatively similar to the timing difference of inter-band carrier aggregation.

[0093] In some other specific implementations, the wireless communication system 100 may support mTRP-based communication in NTN (e.g., mTRP-based PUCCH and PUSCH) to increase coverage and extend the unified TCI framework for mTRP communication to improve overall network performance and coverage, improve mobility between cells, and reduce signaling overhead. To communicate effectively with multiple TRPs, the UE 115 may synchronize with different cells associated with multiple different TRPs. However, in NTN, mTRP synchronization may be associated with increased Doppler drift and timing mismatches between devices that are further apart from each other compared to a terrestrial network. Therefore, the NTN network may support various different techniques to accurately compensate for such differences and support mTRP communication.

[0094] In some specific implementations, the network entity 105 may utilize information to configure the UE 115 to perform mTRP communication for NTN. For example, the network entity 105 may send configuration information of the serving cell and additional NTN-related configurations for non-serving cells, TRPs, or virtual cells, and the additional NTN-related configurations may allow the UE 115 to communicate with multiple TRPs (e.g., satellite 185 or non-terrestrial node 190) present in NTN. In some examples, the network entity 105 may signal the serving cell information and non-serving cell information for mTRP in the downlink TCI state associated with the CORESET message. In some other examples, the network entity 105 may use the unified TCI framework message to signal the serving cell information and non-serving cell information for mTRP. In some other examples, the network entity 105 may use the uplink spatial relation information message to signal the serving cell information and non-serving cell information for mTRP.

[0095] Figure 2 An example of a wireless communication system 200 that supports synchronization for mTRP communication in NTN in accordance with one or more aspects of the present disclosure is illustrated. For example, Figure 2 Communication between the UE 115-a, the network entity 105-a, the first satellite or the first NTN TRP 205-a, the second satellite or the second NTN TRP 205-b, or any combination thereof may be illustrated. In some examples, the network entity 105-a may be an example of a terrestrial network entity or a non-terrestrial network entity. Additionally or alternatively, the first NTN TRP 205-a and the second NTN TRP 205-b may be examples of NTN network entities in some cases and may be associated with coverage areas or cells 210-a and 210-b, respectively.

[0096] To support accurate frame timing and synchronization for uplink communication between UE 115-a and NTN TRP, UE 115-a may perform various timing compensation and pre-compensation techniques to account for the timing differences per NTN TRP, which can be expressed as:

[0097] T TA =(N TA +N TA,UE-specific +N TA,common +N TA,offset )×T c ,

[0098] where T TA is the timing advance applied by UE 115-a (e.g., open-loop timing advance). N TA is the network-selected timing advance value received by UE115-a via control signaling and can be defined as 0 for the physical random access channel (PRACH) and can be updated or accumulated based on the timing advance command field in the control signaling (e.g., msg2 / msgB and MAC CE timing advance command). N TA,UE-specific is the UE-specific timing advance, which is self-estimated by UE 115-a based on the location information and ephemeris information (e.g., EphemerisInfo) of UE 115-a to pre-compensate for the service link delay. N TA,common is the network-controlled common timing advance for pre-compensating the link delay between the SRP and the satellite based on the one-way propagation delay:

[0099]

[0100] N TA,offset is the timing advance offset derived from the n-TimingAdvanceOffset configured in the ServingCellConfigCommon information element, and T c is a constant timing parameter. In such embodiments, based on the relatively large distances between NTN TRPs (compared to the distances between terrestrial TRPs), the timing differences per NTN TRP in the NTN scenario may be relatively greater than the timing differences per NTN TRP in the terrestrial network.

[0101] In addition, UE 115-a may compensate for the Doppler drift 215 per NTN TRP, which may be relatively greater than the Doppler drift 215 in a terrestrial setup due to the relatively large distances between NTN TRPs and the relatively high speeds of each NTN TRP relative to UE 115-a. For example, the Doppler frequency shift 215 for each NTN TRP (f d ) may be equal to:

[0102]

[0103] wherein UE 115-a transmits in the uplink at a certain frequency F c and v → represents the relative velocity of UE 115-a with respect to NTN TRP 205-a or NTN TRP 205-b, and θ is the angle of the relative velocity vector v → .

[0104] UE 115-a can perform various pre-compensation measurements to support accurate time and frequency pre-compensation for inter-satellite mTRP uplink communication. For example, UE 115-a can be configured with two different timing advance values for communicating with NTN TRP 205-a and NTN TRP 205-b. Additionally or alternatively, UE 115-a can identify the positions of each NTN TRP to estimate v → / θ. In some examples, UE 115-a can receive a downlink NTN configuration message (e.g., NTN-Config message) that includes various parameters that UE 115-a can use to perform timing and frequency pre-compensation in the wireless communication system 200. For example, the NTN configuration message can include epoch timing information, validity duration information, cell-specific offset timing information, timing advance information, polarization information, ephemeris information, or a combination thereof. In some examples, UE 115-a can utilize the scheduling offsets K offset and K mac , and calculate and pre-compensate for uplink Doppler drift in the serving link based on the ephemeris information (e.g., EphemerisInfo) of NTN TRP 205-a, NTN TRP 205-b, or both. UE 115-a can receive the NTN configuration message for each serving cell and each neighboring cell via a system information block (SIB) such as SIB19. Additionally or alternatively, UE 115-a can receive the NTN configuration message for the serving cell in a serving cell common configuration message (e.g., ServingCellConfigCommon), and UE 115-a can receive this NTN configuration message via dedicated signaling.

[0105] To support mTRP communication in the wireless communication system 200, the network entity 105-a may use more than one TRP to communicate with the UE 115-a. Such mTRP communication may improve network performance and robustness while reducing signaling overhead, and may improve beam selection efficiency to enhance mobility between cells. To effectively communicate with the NTN TRP 205-a and the NTN TRP 205-b (and potentially a large number of additional NTN TRPs), the UE 115-a may synchronize communication with the cell 210-a (associated with the NTN TRP 205-a) and the cell 210-b (associated with the NTN TRP 205-b). For example, the UE 115-a may perform pre-compensation by applying different timing advances to communications received from or transmitted to multiple NTN TRPs to account for different Doppler drifts and other time and frequency mismatches. In such examples, the UE 115-a may receive information related to both the serving cell (e.g., the cell 210-a associated with the first NTN TRP 205-a) and the non-serving cell (e.g., the cell 210-b associated with the NTN TRP 205-b), and the UE 115-a may use this information to perform time and frequency pre-compensation for mTRP NTN communication.

[0106] In some examples, the network entity 105-a may send multiple NTN configurations (e.g., instead of a single configuration for sTRP) to the UE 115-a for mTRP communication. The multiple NTN configurations may include information that the UE 115-a may use to synchronize with the NTN TRP 205-a and the NTN TRP 205-b and perform mTRP communication with these NTN TRPs. For example, the UE may receive configuration information for NTN communication of the cell 210-b (which may be a non-serving cell), the second NTN TRP 205-b (e.g., NTN configuration 220), information about virtual cells or reference points associated with the serving cell or non-serving cell, or any combination thereof. The NTN configuration information may enable the UE 115-a to perform uplink transmission using dynamic sTRP, mTRP, or multi-point receive diversity in the wireless communication system 200.

[0107] The network entity 105-a may indicate in the NTN configuration 220 the NTN configuration for an additional cell (e.g., a non-serving cell), the NTN configuration for an additional TRP, the NTN configuration for a reference point or for a virtual cell, or any combination thereof, which the UE 115-a may use to calculate a timing advance value and perform Doppler pre-compensation for NTN mTRP uplink synchronization, where the additional cell is in the same carrier as the serving cell. In some examples, the network entity 105-a may indicate the NTN configuration 220 using downlink TCI state information associated with a CORESET configuration (e.g., via a CORESETPoolIndex). In some other examples, the network entity 105-a may indicate the NTN configuration 220 using a unified TCI state information message. In some other examples, the network entity 105-a may indicate the NTN configuration 220 using uplink spatial relation information.

[0108] In some examples, the network entity 105-a may include information on additional NTN configurations for NTN mTRP uplink communication in the downlink TCI state field included in the CORESET message (e.g., in the CORESETPoolIndex). For example, two NTN TRPs (e.g., NTN TRP 205-a and NTN TRP 205-b) may have different physical cell identifiers (PCIs), which may be mapped to different coresetPoolIndex values associated with different downlink TCI states. For example, the CORESET message may include a CORESET identifier and one or more TCI state identifiers corresponding to the NTN TRP. The CORESET message may also include a CORESET pool index, which includes indices of multiple NTN TRPs. Additionally, the CORESET message may include a TCI state field, which includes an additional PCI (e.g., additionalPCI-r17) and an additional PCI index (e.g., additionalPCIIndex-r17) for the NTN TRP corresponding to the non-serving cell. Additionally or alternatively, the NTN configuration for the additional cell may be configured using the PDCCH downlink TCI state. For example, a synchronization signal block (SSB) machine type communication (MTC) message configured for the additional PCI (e.g., SSB-MTC-AdditionalPCI-r17) may include a field (e.g., additionalPCIIndex-r17) identifying the additional PCI for the additional NTN TRP. Additionally, the configuration for the additional NTN TRP may include additional timing information, such as timing advance offset information (e.g., n-TimingAdvanceOffset), timing advance group information (e.g., TAG-Id), additional NTN configuration information (e.g., ntn-Config, ntn-Config-r17), or any combination thereof.

[0109] In some other examples, network entity 105-a may use a unified TCI state framework to include information on additional NTN configurations for NTN mTRP uplink communication (e.g., including uplink TCI state or combined uplink and downlink TCI state information). For example, UE 115-a may be configured to measure SSBs from additional cells or non-serving cells using the same timing advance as the serving cell for inter-cell beam management. In such examples, additional PCI (e.g., additional PCI) for the additional cell or non-serving cell may be configured to be associated with the downlink or combined TCI state, or the uplink TCI state, or both. For the downlink or combined TCI state (e.g., TCI-State) and for the uplink TCI state (e.g., TCI-UL-State-r17), additional cell information or non-serving cell information may be included as AdditionalPCI and AdditionalPCIIndex information fields. In some examples, the additional PCI and NTN configuration information for the additional cell or non-serving cell may be included in the SSB-MTC information message associated with the downlink / combined TCI state or the uplink TCI state. Additionally, the configuration for the additional NTN TRP may include additional timing information in the SSB-MTC information message, such as timing advance offset information (e.g., n-TimingAdvanceOffset), timing advance group information (e.g., TAG-Id), additional NTN configuration information (e.g., ntn-Config, ntn-Config-r17), or any combination thereof.

[0110] In some other examples, network entity 105-a may use uplink spatial relation information to include information on additional NTN configurations for NTN mTRP uplink communication. In some specific implementations, the positioning of the sounding reference signal (SRS) for the serving cell or non-serving cell may be configured via SRS-SpatialRelationInfoPos, which may be associated with the SSB of the serving cell or non-serving cell and may further be associated with the CSI-RS of the serving cell. To configure both the serving cell and non-serving cell for NTN mTRP, the NTN configuration for the additional cell may be configured to be associated with each PUCCH spatial relation or SRS spatial relation using ssb-InfoNcell. For example, the NTN non-serving cell may be used for SRS positioning, and the SRS spatial relation information message (e.g., SRS-SpatialRelationInfoPos-r16) may include an N-cell information field (e.g., ssb-NCell, SSB-InfoNCell), which may include the NTN mTRP configuration for the additional cell. Additionally or alternatively, the NTN non-serving cell may be used for PUCCH and SRS, and the PUCCH spatial relation information message (e.g., PUCCH-SpatialRelationInfo), SRS spatial relation information message (e.g., SRS-SpatialRelationInfo) may include the synchronization signal block configuration (e.g., ssb-NCell, SSB-InfoNCell) for the adjacent TRP / cell information field, which may include the NTN mTRP configuration for the additional cell. Furthermore, the configuration for the additional NTN TRP may include additional timing information in the N-cell information field, such as timing advance offset information (e.g., n-TimingAdvanceOffset), timing advance group information (e.g., TAG-Id), additional NTN configuration information (e.g., ntn-Config, ntn-Config-r17), or any combination thereof.

[0111] UE 115-a may receive an NTN configuration 220 from a network entity 105-a, and the NTN configuration may include serving cell and non-serving cell information for mTRP communication. As described herein, the network entity 105-a may configure the NTN mTRP configuration in a downlink transmission configuration TCI state associated with a CORESET message, using a unified TCI framework message, in an uplink spatial relation information message, or a combination thereof. UE 115-a may use the NTN mTRP configuration to synchronize communication with a first NTN TRP 205-a and a second NTN TRP 205-b and to effectively perform mTRP communication in the NTN network.

[0112] Figure 3 An example of a wireless communication system 300 that supports synchronization for mTRP communication in NTN in accordance with one or more aspects of the present disclosure is illustrated. For example, Figure 3 Communication between UE 115-b, network entity 105-b, a first satellite or first NTN TRP 305-a, a second satellite or second NTN TRP 305-b, or any combination thereof may be illustrated. In some examples, the network entity 105-b may be an example of a terrestrial network entity or a non-terrestrial network entity. Additionally or alternatively, the first NTN TRP 305-a and the second NTN TRP 305-b may be examples of NTN network entities in some cases and may be associated with a first coverage area or first cell 310-a and a second coverage area or second cell 310-b, respectively. In some examples, the wireless communication system 300 may include a cell 310-c or a TRP 305-c, which may be examples of a virtual cell or a reference point.

[0113] To support mTRP communication in the wireless communication system 300, the network entity 105-b may communicate with the UE 115-b using more than one TRP. For example, the UE 115-b may signal a capability indication to the network entity 105-b, the capability indication indicating the number of TRPs that the UE 115-b can use for mTRP communication support. To communicate effectively with the NTN TRP 205-a and the NTN TRP 205-b (and possibly a large number of additional NTN TRPs, such as the NTN TRP 305-c), the UE 115-b may synchronize communication with the first cell 310-a (associated with the first NTN TRP 305-a), the second cell 310-b (associated with the NTN TRP 305-b), and the cell 310-c (associated with the NTN TRP 305-c). For example, the UE 115-b may perform pre-compensation by applying different timing advances to communication received from or transmitted to multiple NTN TRPs to account for different Doppler drifts and other time and frequency mismatches. In such examples, the UE 115-a may receive information related to both the serving cell (e.g., the first cell 310-a associated with the first NTN TRP 305-a) and additional non-serving cells (e.g., the second cell 310-b associated with the NTN TRP 305-b and the cell 310-c associated with the third NTN TRP 305-c), and the UE 115-a may use this information to perform time and frequency pre-compensation for mTRP NTN communication.

[0114] In some examples, the network entity 105-b may send the NTN mTRP configuration 315 for mTRP communication to the UE 115-b (e.g., instead of a single configuration for sTRP). The multiple NTN configurations may include information that the UE 115-b can use to synchronize with the first NTN TRP 305-a, the NTN TRP 305-b, and the NTN TRP 305-c and perform mTRP communication with these NTN TRPs. For example, the UE may receive configuration information for NTN communication for the second cell 310-b and the cell 310-c (e.g., the NTN mTRP configuration 315). The NTN configuration information may enable the UE 115-b to perform uplink transmissions in the wireless communication system 300.

[0115] In some other examples, cell 310-c can be a virtual cell that UE 115-b can use to perform synchronization for both the first cell 310-a and the second cell 310-b. For example, UE 115-b can receive an NTN mTRP configuration 315 (which can include the virtual cell ID of virtual cell 310-c), and can synchronize communication and transmit communication based on synchronization with virtual cell 310-c or a reference point spatially located between the first NTN TRP 305-a and the second NTN TRP 305-b. In such cases, UE 115-b can transmit only to the reference point or the virtual cell, rather than to both cells, which can reduce overall complexity and signaling overhead. Additionally, in some examples, the NTN TRPs (e.g., the first NTN TRP 305-a and the second NTN TRP 305-b) can receive communication from UE 115-b that has been synchronized with virtual cell 310-c, and the NTN TRPs (e.g., the first NTN TRP 305-a and the second NTN TRP 305-b) can perform post-reception processing to account for possible inaccuracies based on virtual cell synchronization.

[0116] Figure 4 An example of a process flow 400 that supports synchronization for mTRP communication in NTN in accordance with one or more aspects of the present disclosure is illustrated. For example, process flow 400 can support communication between UE 115-c, network entity 105-c, first TRP 405-a, and second TRP 405-b in an NTN wireless communication network, which can be examples of the corresponding devices described herein.

[0117] In the following description of process flow 400, the operations between UE 115-c, network entity 105-c, first TRP 405-a, and second TRP 405-b can be sent in an order different from the order shown, or other operations can be added or removed from process flow 400. For example, some operations can also be omitted from process flow 400, or can be performed in a different order or at different times, or other operations can be added to process flow 400. Although UE 115-c, network entity 105-c, first TRP 405-a, and second TRP 405-b are shown performing the operations of process flow 400, some aspects of some operations can also be performed by one or more wireless devices or network devices.

[0118] At 410, UE 115-c may receive a downlink message that indicates a first configuration for a first TRP (e.g., first TRP 405-a) corresponding to a first cell of the NTN and a second configuration for a second TRP (e.g., second TRP 405-b) corresponding to a second cell of the NTN. For example, the first configuration for the first TRP 405-a and the second configuration for the second TRP 405-b may include timing information, NTN configuration information, one or more PCIDs, one or more virtual cell identifiers, or any combination thereof.

[0119] In some examples, the downlink message may be a CORESET configuration message, and UE 115-c may receive an indication of the first TRP 405-a based on a first CORESET pool index of the CORESET configuration message. UE 115-c may also receive an indication of the second TRP 405-b based on a second CORESET pool index of the CORESET configuration message. Then, UE 115-c may decode first TCI state information associated with the first CORESET pool index and second TCI state information associated with the second CORESET pool index. In such examples, the first TCI state information may include the first configuration for the first TRP 405-a and the second TCI state information may include the second configuration for the second TRP 405-b.

[0120] In some other examples, the downlink message may be a TCI state information message, and UE 115-c may receive the first configuration for the first TRP 405-a and the second configuration for the second TRP 405-b based on the unified TCI state information message. In such examples, the unified TCI state information message may include combined downlink and uplink TCI state information, or separate downlink and uplink TCI state information, SSB-MTC information, or any combination thereof.

[0121] In some other examples, the downlink message may be a spatial relation information message, and UE 115-c may receive the first configuration for the first TRP 405-a and the second configuration for the second TRP 405-b based on the spatial relation information message. In some examples, the spatial relation information message includes an SSB information field corresponding to the first cell, the second cell, or both, and the SSB information field indicates the first configuration for the first TRP 405-a, the second configuration for the second TRP 405-b, or both. In some other examples, the spatial relation information message may include SRS positioning information corresponding to the first configuration for the first TRP 405-a and the second configuration for the second TRP 405-b. Additionally, the spatial relation information message may include an indication of the SRS corresponding to the first configuration for the first TRP 405-a and the second configuration for the second TRP 405-b. Additionally or alternatively, the spatial relation information message may include an indication of the PUCCH corresponding to the first configuration for the first TRP 405-a and the second configuration for the second TRP 405-b.

[0122] At 415, UE 115-c may perform one or more synchronization measurements (e.g., Doppler shift pre-compensation measurements) for synchronizing uplink communication with the first TRP 405-a and the second TRP 405-b based on the first configuration and the second configuration of the downlink message. In some examples, UE 115-c may perform the one or more synchronization measurements on one or more SSBs associated with the first cell and the second cell of the NTN by applying corresponding timing advance amounts to the one or more synchronization measurements.

[0123] At 420, UE 115-c may send one or more uplink messages to the first TRP 405-a, the second TRP 405-b, or both according to the one or more synchronization measurements.

[0124] In some examples, UE 115-c may send a message to network entity 105-c, and the message indicates the ability of UE 115-c to communicate with the first TRP 405-a, the second TRP 405-b, and one or more additional TRPs in the NTN.

[0125] In some other examples, the second configuration may include a configuration for a virtual cell, and UE 115-c may perform the one or more synchronization measurements with respect to the virtual cell that is spatially located between the first TRP 405-a and the second TRP 405-b to at least partially synchronize the uplink communication with the first TRP 405-a and the second TRP 405-b. Then, UE 115-c may send the one or more uplink messages to the first TRP 405-a and the second TRP 405-b based on performing the one or more synchronization measurements with respect to the virtual cell. In some other examples, UE 115-c may receive a third configuration for a third TRP corresponding to a third cell of the NTN and may perform the one or more synchronization measurements to synchronize the uplink communication with the first TRP 405-a, the second TRP 405-b, and the third TRP.

[0126] Figure 5 Block diagram 500 illustrates a device 505 that supports synchronization for mTRP communication in an NTN, in accordance with one or more aspects of the present disclosure. Device 505 may be an example of aspects of UE 115 as described herein. Device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. Device 505 may also include a processor. Each of these components may communicate with one another (e.g., via one or more buses).

[0127] Receiver 510 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to synchronization for mTRP communication in an NTN). The information may be passed to other components of device 505. Receiver 510 may utilize a single antenna or a set of multiple antennas.

[0128] Transmitter 515 may provide components for transmitting signals generated by other components of device 505. For example, transmitter 515 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to synchronization for mTRP communication in an NTN). In some examples, transmitter 515 may be co-located with receiver 510 in a transceiver module. Transmitter 515 may utilize a single antenna or a set of multiple antennas.

[0129] The communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof or their various components can be examples of components for performing various aspects of synchronization for mTRP communication in NTN as described herein. For example, the communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof or their components can support methods for performing one or more of the functions described herein.

[0130] In some examples, the communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof or their components can be implemented in hardware (e.g., in a communication management circuit). The hardware can include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof that are configured as or otherwise support components for performing the functions described in this disclosure. In some examples, the processor and the memory coupled to the processor can be configured to perform one or more of the functions described herein (e.g., by the processor executing instructions stored in the memory).

[0131] Additionally or alternatively, in some examples, the communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof or their components can be implemented in code executed by a processor (e.g., implemented as communication management software or firmware). If implemented in code executed by a processor, the functions of the communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof or their components can be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices that are configured as or otherwise support components for performing the functions described in this disclosure.

[0132] In some examples, the communication manager 520 can be configured to use or otherwise cooperate with the receiver 510, the transmitter 515, or both to perform various operations (e.g., receive, obtain, monitor, output, transmit). For example, the communication manager 520 can receive information from the receiver 510, convey information to the transmitter 515, or integrate in combination with the receiver 510, the transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.

[0133] According to an example as disclosed herein, the communication manager 520 may support wireless communication at a UE. For example, the communication manager 520 may be configured as or otherwise support a component for receiving a downlink message that indicates a first configuration for a first transmit-receive point corresponding to a first cell of a non-terrestrial network and a second configuration for a second transmit-receive point corresponding to a second cell of the non-terrestrial network. The communication manager 520 may be configured as or otherwise support a component for performing one or more synchronization measurements for synchronizing uplink communication with the first transmit-receive point and the second transmit-receive point based on the first configuration and the second configuration of the downlink message. The communication manager 520 may be configured as or otherwise support a component for sending one or more uplink messages to the first transmit-receive point, the second transmit-receive point, or both according to one or more synchronization measurements.

[0134] By including or configuring the communication manager 520 according to an example as described herein, a device 505 (e.g., a control receiver 510, a transmitter 515, the communication manager 520, or a combination thereof or a processor otherwise coupled thereto) may support techniques for more efficiently utilizing communication resources and increasing the capacity and coverage of an NTN system.

[0135] Figure 6 Block diagram 600 illustrates a device 605 that supports synchronization for mTRP communication in an NTN according to one or more aspects of the present disclosure. The device 605 may be an example of aspects of the device 505 or the UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may communicate with one another (e.g., via one or more buses).

[0136] The receiver 610 may provide a component for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to synchronization for mTRP communication in an NTN). The information may be passed to other components of the device 605. The receiver 610 may utilize a single antenna or an array of multiple antennas.

[0137] The transmitter 615 may provide components for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to synchronization for mTRP communication in NTN). In some examples, the transmitter 615 may be co-located with the receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or an array of multiple antennas.

[0138] The device 605 or its various components may be examples of components for performing various aspects of synchronization for mTRP communication in NTN as described herein. For example, the communication manager 620 may include the mTRP communication component 625, the uplink synchronization component 630, or any combination thereof. The communication manager 620 may be an example of aspects of the communication manager 520 as described herein. In some examples, the communication manager 620 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise in cooperation with the receiver 610, the transmitter 615, or both. For example, the communication manager 620 may receive information from the receiver 610, convey information to the transmitter 615, or integrate in combination with the receiver 610, the transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0139] According to examples disclosed herein, the communication manager 620 may support wireless communication at the UE. The mTRP communication component 625 may be configured as or otherwise support a component for receiving a downlink message that indicates a first configuration for a first transmit-receive point corresponding to a first cell of a non-terrestrial network and a second configuration for a second transmit-receive point corresponding to a second cell of the non-terrestrial network. The uplink synchronization component 630 may be configured as or otherwise support a component for performing one or more synchronization measurements for synchronizing uplink communication with the first transmit-receive point and the second transmit-receive point based on the first configuration and the second configuration of the downlink message. The mTRP communication component 625 may be configured as or otherwise support a component for transmitting one or more uplink messages to the first transmit-receive point, the second transmit-receive point, or both according to one or more synchronization measurements.

[0140] Figure 7Block diagram 700 illustrates a communication manager 720 that supports synchronization for mTRP communication in NTN in accordance with one or more aspects of the present disclosure. The communication manager 720 may be an example of the communication manager 520, the communication manager 620, or aspects of both as described herein. The communication manager 720 or its various components may be examples of components for performing various aspects of synchronization for mTRP communication in NTN as described herein. For example, the communication manager 720 may include an mTRP communication component 725, an uplink synchronization component 730, a CORESET configuration component 735, a TCI state configuration component 740, a spatial relationship information component 745, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0141] In accordance with examples as disclosed herein, the communication manager 720 may support wireless communication at a UE. The mTRP communication component 725 may be configured as or otherwise support a component for receiving a downlink message that indicates a first configuration for a first transmit-receive point corresponding to a first cell of a non-terrestrial network and a second configuration for a second transmit-receive point corresponding to a second cell of the non-terrestrial network. The uplink synchronization component 730 may be configured as or otherwise support a component for performing one or more synchronization measurements for synchronizing uplink communication with the first transmit-receive point and the second transmit-receive point based on the first configuration and the second configuration of the downlink message. In some examples, the mTRP communication component 725 may be configured as or otherwise support a component for sending one or more uplink messages to the first transmit-receive point, the second transmit-receive point, or both based on one or more synchronization measurements.

[0142] In some examples, the downlink message includes a control resource set configuration message, and the CORESET configuration component 735 may be configured as or otherwise support a component for receiving an indication of the first transmit-receive point based on a first control resource set pool index of the control resource set configuration message and an indication of the second transmit-receive point based on a second control resource set pool index of the control resource set configuration message.

[0143] In some examples, the CORESET configuration component 735 may be configured as or otherwise support a component for decoding first transmit configuration indicator status information associated with the first control resource set pool index and second transmit configuration indicator status information associated with the second control resource set pool index, where the first transmit configuration indicator status information includes the first configuration for the first transmit-receive point and the second transmit configuration indicator status information includes the second configuration for the second transmit-receive point.

[0144] In some examples, the downlink message includes a unified transmission configuration indicator status information message, and the TCI status configuration component 740 can be configured as or otherwise support a component for receiving the first configuration for the first transmit-receive point and the second configuration for the second transmit-receive point based on the unified transmission configuration indicator status information message.

[0145] In some examples, the unified transmission configuration indicator status information message includes combined downlink and uplink transmission configuration indicator status information, or separate downlink and uplink transmission configuration indicator status information, synchronization signal block - machine type communication information, or any combination thereof.

[0146] In some examples, the TCI status configuration component 740 can be configured as or otherwise support a component for performing one or more synchronization measurements on one or more synchronization signal blocks associated with the first cell and the second cell of the non-terrestrial network based on the unified transmission configuration indicator status information message by applying corresponding timing advance to the one or more synchronization measurements.

[0147] In some examples, the downlink message includes a spatial relation information message, and the spatial relation information component 745 can be configured as or otherwise support a component for receiving the first configuration for the first transmit-receive point and the second configuration for the second transmit-receive point based on the spatial relation information message.

[0148] In some examples, the spatial relation information message includes a synchronization signal block information field corresponding to the first cell, the second cell, or both, the synchronization signal block information field indicating the first configuration for the first transmit-receive point, the second configuration for the second transmit-receive point, or both.

[0149] In some examples, the spatial relation information message includes sounding reference signal positioning information corresponding to the first configuration for the first transmit-receive point and the second configuration for the second transmit-receive point.

[0150] In some examples, the spatial relation information message includes an indication of a sounding reference signal corresponding to the first configuration for the first transmit-receive point and the second configuration for the second transmit-receive point.

[0151] In some examples, the spatial relation information message includes an indication of a physical uplink control channel corresponding to the first configuration for the first transmit-receive point and the second configuration for the second transmit-receive point.

[0152] In some examples, the mTRP communication component 725 may be configured as or otherwise support a component for sending a message to a network entity indicating the UE's ability to communicate with the first transmit-receive point and the second transmit-receive point in the non-terrestrial network.

[0153] In some examples, the second configuration includes the configuration of a virtual cell, and in order to support the performance of the one or more synchronization measurements, the uplink synchronization component 730 may be configured as or otherwise support a component for performing the one or more synchronization measurements with respect to the virtual cell spatially located between the first transmit-receive point and the second transmit-receive point to at least partially synchronize the uplink communication with the first transmit-receive point and the second transmit-receive point. In some examples, the second configuration includes the configuration of a virtual cell, and in order to support the performance of the one or more synchronization measurements, the mTRP communication component 725 may be configured as or otherwise support a component for sending the one or more uplink messages to the first transmit-receive point and the second transmit-receive point based on performing the one or more synchronization measurements with respect to the virtual cell.

[0154] In some examples, in order to support receiving the downlink message, the mTRP communication component 725 may be configured as or otherwise support a component for receiving a third configuration for a third transmit-receive point corresponding to a third cell in the non-terrestrial network. In some examples, in order to support receiving the downlink message, the uplink synchronization component 730 may be configured as or otherwise support a component for performing the one or more synchronization measurements to synchronize the uplink communication with the first transmit-receive point, the second transmit-receive point, and the third transmit-receive point based on the third configuration.

[0155] In some examples, the first configuration for the first transmit-receive point and the second configuration for the second transmit-receive point include timing information, non-terrestrial network configuration information, physical cell identifiers, virtual cell identifiers, or any combination thereof.

[0156] In some examples, the one or more synchronization measurements include Doppler frequency shift pre-compensation measurements associated with the first transmit-receive point and the second transmit-receive point in the non-terrestrial network.

[0157] In some examples, the first configuration for the first transmit-receive point includes a first physical cell identifier or a first virtual cell identifier, and the second configuration for the second transmit-receive point includes a second physical cell identifier or a second virtual cell identifier.

[0158] Figure 8FIG. illustrates a system 800 including a device 805 that supports synchronization for mTRP communication in NTN in accordance with one or more aspects of the present disclosure. The device 805 may be an example of the device 505, the device 605, or the UE 115 as described herein, or include components thereof. The device 805 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). The device 805 may include components for two-way voice and data communication, including components for sending and receiving communication, such as a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, a memory 830, code 835, and a processor 840. These components may communicate electronically or otherwise be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 845).

[0159] The I / O controller 810 may manage input signals and output signals of the device 805. The I / O controller 810 may also manage peripheral devices not integrated into the device 805. In some cases, the I / O controller 810 may represent a physical connection or port to an external peripheral device. In some cases, the I / O controller 810 may utilize an operating system, such as or another known operating system. Additionally or alternatively, the I / O controller 810 may represent or interact with a modem, a keyboard, a mouse, a touch screen, or similar devices. In some cases, the I / O controller 810 may be implemented as part of a processor (such as the processor 840). In some cases, a user may interact with the device 805 via the I / O controller 810 or via hardware components controlled by the I / O controller 810.

[0160] In some cases, the device 805 may include a single antenna 825. However, in some other cases, the device 805 may have more than one antenna 825, and the more than one antenna may be capable of concurrently sending or receiving multiple wireless transmissions. The transceiver 815 may communicate bidirectionally via one or more antennas 825, a wired link, or a wireless link as described herein. For example, the transceiver 815 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 815 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 825 for transmission; and demodulating packets received from one or more antennas 825. The transceiver 815 or the transceiver 815 and one or more antennas 825 may be examples of the transmitter 515, the transmitter 615, the receiver 510, the receiver 610, or any combination thereof or components thereof as described herein.

[0161] The memory 830 may include a random access memory (RAM) and a read-only memory (ROM). The memory 830 may store computer-readable, computer-executable code 835 including instructions that, when executed by the processor 840, cause the device 805 to perform the various functions described herein. The code 835 may be stored in a non-transitory computer-readable medium (such as the system memory or another type of memory). In some cases, the code 835 may not be directly executable by the processor 840 but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 830 may also contain a basic input / output system (BIOS), etc., which may control basic hardware or software operations, such as interactions with peripheral components or devices.

[0162] The processor 840 may include intelligent hardware devices (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, the processor 840 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 840. The processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 830) to cause the device 805 to perform various functions (e.g., support the functions or tasks for synchronizing the uplink communication for mTRP communication in NTN). For example, the device 805 or components of the device 805 may include the processor 840 and the memory 830 coupled to or coupled with the processor 840, and the processor 840 and the memory 830 are configured to perform the various functions described herein.

[0163] According to an example as disclosed herein, the communication manager 820 may support wireless communication at the UE. For example, the communication manager 820 may be configured as or otherwise support a component for receiving a downlink message indicating a first configuration for a first transmit-receive point corresponding to a first cell of a non-terrestrial network and a second configuration for a second transmit-receive point corresponding to a second cell of the non-terrestrial network. The communication manager 820 may be configured as or otherwise support a component for performing one or more synchronization measurements for synchronizing the uplink communication with the first transmit-receive point and the second transmit-receive point based on the first configuration and the second configuration of the downlink message. The communication manager 820 may be configured as or otherwise support a component for sending one or more uplink messages to the first transmit-receive point, the second transmit-receive point, or both according to one or more synchronization measurements.

[0164] By including or configuring a communication manager 820 according to examples as described herein, the device 805 may support techniques for improving communication reliability, reducing latency, more efficiently utilizing communication resources, improving coordination between devices, and increasing the capacity and coverage of the NTN system.

[0165] In some examples, the communication manager 820 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise in concert with the transceiver 815, one or more antennas 825, or any combination thereof. Although the communication manager 820 is illustrated as a separate component, in some examples, one or more of the functions described with reference to the communication manager 820 may be supported or performed by the processor 840, the memory 830, the code 835, or any combination thereof. For example, the code 835 may include instructions that, when executed by the processor 840, cause the device 805 to perform various aspects of synchronization for mTRP communication in NTN as described herein, or the processor 840 and the memory 830 may otherwise be configured to perform or support such operations.

[0166] Figure 9 A block diagram 900 of a device 905 supporting synchronization for mTRP communication in NTN according to one or more aspects of the present disclosure is illustrated. The device 905 may be an example of aspects of the network entity 105 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with one another (e.g., via one or more buses).

[0167] The receiver 910 may provide components for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of the device 905. In some examples, the receiver 910 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 910 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0168] The transmitter 915 can provide components for outputting (e.g., transmitting, providing, conveying, delivering) information generated by other components of the device 905. For example, the transmitter 915 can output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 915 can support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, the transmitter 915 can support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 915 and the receiver 910 can be co-located in a transceiver, which can include a modem or be coupled to a modem.

[0169] The communication manager 920, the receiver 910, the transmitter 915, or various combinations or various components thereof can be examples of components for performing various aspects of synchronization for mTRP communication in NTN as described herein. For example, the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof can support methods for performing one or more of the functions described herein.

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

[0171] Additionally or alternatively, in some examples, the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof can be implemented in code executed by a processor (e.g., implemented as communication management software or firmware). If implemented in code executed by a processor, the functions of the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof can be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting components for performing the functions described in this disclosure).

[0172] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise in concert with the receiver 910, the transmitter 915, or both. For example, the communication manager 920 may receive information from the receiver 910, convey information to the transmitter 915, or integrate in combination with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0173] According to examples disclosed herein, the communication manager 920 may support wireless communication at a network entity. For example, the communication manager 920 may be configured as or otherwise support a component for sending a downlink message to a UE, the downlink message indicating a first configuration for a first transmission reception point corresponding to a first cell of a non-terrestrial network and a second configuration for a second transmission reception point corresponding to a second cell of the non-terrestrial network. The communication manager 920 may be configured as or otherwise support a component for performing one or more synchronization measurements for synchronizing communication with the first transmission reception point, the second transmission reception point, and the UE based on the first configuration and the second configuration of the downlink message. The communication manager 920 may be configured as or otherwise support a component for receiving one or more uplink messages from the UE according to the one or more synchronization measurements.

[0174] By including or configuring a communication manager 920 according to examples described herein, a device 905 (e.g., a processor that controls the receiver 910, the transmitter 915, the communication manager 920, or a combination thereof or is otherwise coupled thereto) may support techniques for more efficiently utilizing communication resources and increasing the capacity and coverage of an NTN system.

[0175] Figure 10 Block diagram 1000 illustrates a device 1005 supporting synchronization for mTRP communication in an NTN according to one or more aspects of the present disclosure. The device 1005 may be an example of aspects of the device 905 or the network entity 105 described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with one another (e.g., via one or more buses).

[0176] The receiver 1010 may provide components for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of the device 1005. In some examples, the receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0177] The transmitter 1015 may provide components for outputting (e.g., transmitting, providing, conveying, delivering) information generated by other components of the device 1005. For example, the transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, the transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1015 and the receiver 1010 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0178] The device 1005 or its various components may be examples of components for performing various aspects of synchronization for mTRP communication in NTN as described herein. For example, the communication manager 1020 may include an mTRP communication configuration component 1025, a synchronization component 1030, an uplink communication component 1035, or any combination thereof. The communication manager 1020 may be an example of aspects of the communication manager 920 as described herein. In some examples, the communication manager 1020 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise in cooperation with the receiver 1010, the transmitter 1015, or both. For example, the communication manager 1020 may receive information from the receiver 1010, convey information to the transmitter 1015, or integrate in combination with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0179] According to an example as disclosed herein, the communication manager 1020 may support wireless communication at a network entity. The mTRP communication configuration component 1025 may be configured as or otherwise support a component for sending a downlink message to a UE, the downlink message indicating a first configuration for a first transmit-receive point corresponding to a first cell of a non-terrestrial network and a second configuration for a second transmit-receive point corresponding to a second cell of the non-terrestrial network. The synchronization component 1030 may be configured as or otherwise support a component for performing one or more synchronization measurements for synchronizing communication with the first transmit-receive point, the second transmit-receive point, and the UE based on the first configuration and the second configuration of the downlink message. The uplink communication component 1035 may be configured as or otherwise support a component for receiving one or more uplink messages from the UE according to the one or more synchronization measurements.

[0180] Figure 11 Block diagram 1100 illustrates a communication manager 1120 that supports synchronization for mTRP communication in NTN according to one or more aspects of the present disclosure. The communication manager 1120 may be an example of aspects of the communication manager 920, the communication manager 1020, or both as described herein. The communication manager 1120 or its various components may be examples of components for performing various aspects of synchronization for mTRP communication in NTN as described herein. For example, the communication manager 1120 may include an mTRP communication configuration component 1125, a synchronization component 1130, an uplink communication component 1135, a CORESET configuration component 1140, a TCI state configuration component 1145, a spatial relationship information component 1150, a virtual cell configuration component 1155, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), and this communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of the protocol stack (e.g., between protocol layers of the protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0181] According to examples disclosed herein, the communication manager 1120 may support wireless communication at a network entity. The mTRP communication configuration component 1125 may be configured as or otherwise support a component for sending a downlink message to a UE, the downlink message indicating a first configuration for a first transmit-receive point corresponding to a first cell of a non-terrestrial network and a second configuration for a second transmit-receive point corresponding to a second cell of the non-terrestrial network. The synchronization component 1130 may be configured as or otherwise support a component for performing one or more synchronization measurements for synchronizing communication with the first transmit-receive point, the second transmit-receive point, and the UE based on the first configuration and the second configuration of the downlink message. The uplink communication component 1135 may be configured as or otherwise support a component for receiving one or more uplink messages from the UE according to the one or more synchronization measurements.

[0182] In some examples, the downlink message includes a control resource set configuration message, and the CORESET configuration component 1140 may be configured as or otherwise support a component for sending an indication of the first transmit-receive point to the UE based on a first control resource set pool index of the control resource set configuration message and an indication of the second transmit-receive point to the UE based on a second control resource set pool index of the control resource set configuration message.

[0183] In some examples, the downlink message further includes first transmit configuration indicator status information associated with the first control resource set pool index and second transmit configuration indicator status information associated with the second control resource set pool index. In some examples, the first transmit configuration indicator status information includes the first configuration for the first transmit-receive point and the second transmit configuration indicator status information includes the second configuration for the second transmit-receive point.

[0184] In some examples, the downlink message includes a unified transmit configuration indicator status information message, and the TCI status configuration component 1145 may be configured as or otherwise support a component for sending the first configuration for the first transmit-receive point and the second configuration for the second transmit-receive point to the UE based on the unified transmit configuration indicator status information message.

[0185] In some examples, the unified transmit configuration indicator status information message includes combined downlink and uplink transmit configuration indicator status information, or separate downlink and uplink transmit configuration indicator status information, synchronization signal block - machine type communication information, or a combination thereof.

[0186] In some examples, the downlink message includes a spatial relation information message, and the spatial relation information component 1150 may be configured as or otherwise support a component for sending the first configuration for the first transmit-receive point and the second configuration for the second transmit-receive point to the UE based on the spatial relation information message.

[0187] In some examples, the spatial relation information message includes a synchronization signal block information field corresponding to the first cell, the second cell, or both, and the synchronization signal block information field indicates the first configuration for the first transmit-receive point, the second configuration for the second transmit-receive point, or both.

[0188] In some examples, the spatial relation information message includes sounding reference signal positioning information corresponding to the first configuration for the first transmit-receive point and the second configuration for the second transmit-receive point.

[0189] In some examples, the mTRP communication configuration component 1125 may be configured as or otherwise support a component for receiving a message indicating the UE's ability to communicate with the first transmit-receive point and the second transmit-receive point in the non-terrestrial network.

[0190] In some examples, the second configuration includes a configuration of a virtual cell, and the virtual cell configuration component 1155 may be configured as or otherwise support a component for receiving from the UE one or more uplink messages synchronized to the virtual cell. In some examples, the second configuration includes a configuration of a virtual cell, and the synchronization component 1130 may be configured as or otherwise support a component for performing one or more post-processing procedures to synchronize the one or more uplink messages to the timing of the first cell and the second cell.

[0191] In some examples, to support receiving the downlink message, the mTRP communication configuration component 1125 may be configured as or otherwise support a component for sending a third configuration for a third transmit-receive point corresponding to a third cell in the non-terrestrial network. In some examples, to support receiving the downlink message, the synchronization component 1130 may be configured as or otherwise support a component for performing the one or more synchronization measurements to synchronize the communication with the first transmit-receive point, the second transmit-receive point, the third transmit-receive point, and the UE based on the third configuration.

[0192] Figure 12FIG. illustrates a system 1200 including a device 1205 that supports synchronization for mTRP communication in NTN, in accordance with one or more aspects of the present disclosure. The device 1205 may be an example of the device 905, the device 1005, or the network entity 105 as described herein, or include components thereof. The device 1205 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and the communication may include communication via one or more wired interfaces, via one or more wireless interfaces, or any combination thereof. The device 1205 may include components that support outputting and obtaining communication, such as a communication manager 1220, a transceiver 1210, an antenna 1215, a memory 1225, code 1230, and a processor 1235. These components may communicate electronically or otherwise be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1240).

[0193] The transceiver 1210 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1210 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1210 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1205 may include one or more antennas 1215, which may be capable of sending or receiving wireless transmissions (e.g., concurrently). The transceiver 1210 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1215, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1215, from a wired receiver); and demodulating the signal. In some implementations, the transceiver 1210 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1215 configured to support various receiving or obtaining operations, or one or more interfaces coupled to one or more antennas 1215 configured to support various transmitting or outputting operations, or a combination thereof. In some implementations, the transceiver 1210 may include or be configured to be coupled to one or more processors or memory components, which are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1210, or the transceiver 1210 and one or more antennas 1215, or the transceiver 1210 and one or more antennas 1215 and one or more processors or memory components (e.g., processor 1235 or memory 1225 or both) may be included in a chip or chip assembly installed in the device 1205. In some examples, the transceiver may be operable to support communications via one or more communication links (eg, communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0194] The memory 1225 may include RAM and ROM. The memory 1225 may store computer-readable, computer-executable code 1230 including instructions that, when executed by the processor 1235, cause the device 1205 to perform the various functions described herein. The code 1230 may be stored in a non-transitory computer-readable medium (such as system memory or another type of memory). In some cases, the code 1230 may not be directly executable by the processor 1235 but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 1225 may also contain a BIOS or the like, which may control basic hardware or software operations, such as interactions with peripheral components or devices.

[0195] Processor 1235 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1235 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1235. Processor 1235 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1225) to cause device 1205 to perform various functions (e.g., support various functions or tasks for synchronization of mTRP communication in NTN). For example, device 1205 or components of device 1205 may include processor 1235 and memory 1225 coupled to processor 1235, and processor 1235 and memory 1225 are configured to perform the various functions described herein. Processor 1235 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that may host functions for performing the functions of device 1205 (e.g., by executing code 1230). Processor 1235 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1205 (such as within memory 1225). In some specific implementations, processor 1235 may be a component of a processing system. A processing system generally may refer to a system or series of machines or components that receive inputs and process these inputs to produce a set of outputs (which may be passed to other systems or components of, for example, device 1205). For example, the processing system of device 1205 may refer to a system that includes various other components or sub-components of device 1205 (such as processor 1235, or transceiver 1210, or communication manager 1220, or a combination of other components or components of device 1205). The processing system of device 1205 may interface with other components of device 1205 and may process information (such as inputs or signals) received from other components or output information to other components. For example, a chip or modem of device 1205 may include a processing system and one or more interfaces for outputting information or for obtaining information or both. One or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information or the same interface configured to output information and obtain information, as well as other specific implementations. In some specific implementations, one or more interfaces may refer to an interface between the processing system of a chip or modem and a transmitter such that device 1205 may transmit information output from the chip or modem.Additionally or alternatively, in some embodiments, one or more interfaces may be an interface between a processing system of a chip or modem and a receiver such that the device 1205 can obtain information or signal input, and the information can be passed to the processing system. One of ordinary skill in the art will readily recognize that the first interface may also obtain information or signal input, and the second interface may also output information or signal output.

[0196] In some examples, the bus 1240 may support communication within a protocol layer of a protocol stack (e.g., within the protocol layer). In some examples, the bus 1240 may support communication associated with a logical channel of a protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of the device 1205 or communication performed between different components of the device 1205 that may be co-located or located at different positions (e.g., where the device 1205 may refer to a system where one or more of the communication manager 1220, transceiver 1210, memory 1225, code 1230, and processor 1235 may be located in one of different components or divided between different components).

[0197] In some examples, the communication manager 1220 may manage aspects of communication with the core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communication manager 1220 may manage the delivery of data communication of client devices such as one or more UEs 115. In some examples, the communication manager 1220 may manage communication with other network entities 105 and may include a controller or scheduler for coordinating with other network entities 105 to control communication with the UEs 115. In some examples, the communication manager 1220 may support the X2 interface within the LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0198] According to examples disclosed herein, the communication manager 1220 may support wireless communication at a network entity. For example, the communication manager 1220 may be configured as or otherwise support a component for sending a downlink message to a UE that indicates a first configuration for a first transmission reception point corresponding to a first cell of a non-terrestrial network and a second configuration for a second transmission reception point corresponding to a second cell of the non-terrestrial network. The communication manager 1220 may be configured as or otherwise support a component for performing one or more synchronization measurements for synchronizing communication with the first transmission reception point, the second transmission reception point, and the UE based on the first configuration and the second configuration of the downlink message. The communication manager 1220 may be configured as or otherwise support a component for receiving one or more uplink messages from the UE based on the one or more synchronization measurements.

[0199] By including or configuring a communication manager 1220 according to examples as described herein, device 1205 may support techniques for improving communication reliability, reducing latency, more efficiently utilizing communication resources, improving coordination between devices, and increasing the capacity and coverage of an NTN system.

[0200] In some examples, communication manager 1220 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise in cooperation with transceiver 1210, one or more antennas 1215 (e.g., where applicable), or any combination thereof. Although communication manager 1220 is illustrated as a separate component, in some examples, one or more of the functions described with reference to communication manager 1220 may be supported or performed by transceiver 1210, processor 1235, memory 1225, code 1230, or any combination thereof. For example, code 1230 may include instructions that, when executed by processor 1235, cause device 1205 to perform various aspects of synchronization for mTRP communication in an NTN as described herein, or processor 1235 and memory 1225 may otherwise be configured to perform or support such operations.

[0201] Figure 13 A flowchart of a method 1300 for supporting synchronization for mTRP communication in an NTN in accordance with one or more aspects of the present disclosure is illustrated. Operations of method 1300 may be implemented by a UE or components thereof as described herein. For example, operations of method 1300 may be performed by UE 115 as described with reference to Figures 1 to 8 In some examples, the UE may execute an instruction set to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0202] At 1305, the method may include: receiving a downlink message that indicates a first configuration for a first transmit receive point corresponding to a first cell of a non-terrestrial network and a second configuration for a second transmit receive point corresponding to a second cell of the non-terrestrial network. The operation of 1305 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operation of 1305 may be performed by an mTRP communication component 725 as described with reference to Figure 7 In some examples, aspects of the operation of 1310 may be performed by an mTRP communication component 725 as described with reference to

[0203] At 1310, the method may include: based on the first configuration and the second configuration of the downlink message, performing one or more synchronization measurements for synchronizing uplink communication with the first transmit receive point and the second transmit receive point. The operation of 1310 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operation of 1310 may be performed by an mTRP communication component 725 as described with reference to Figure 7Performed by the uplink synchronization component 730 described above.

[0204] At 1315, the method may include: sending one or more uplink messages to the first transmit-receive point, the second transmit-receive point, or both based on one or more synchronization measurements. The operation at 1315 may be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1315 may be performed by the mTRP communication component 725 as described with reference to Figure 7 The mTRP communication component 725 described above.

[0205] Figure 14 FIG. illustrates a flow chart of a method 1400 for supporting synchronization for mTRP communication in NTN according to one or more aspects of the present disclosure. The operations of method 1400 may be implemented by a UE or its components as described herein. For example, the operations of method 1400 may be performed by the UE 115 as described with reference to Figures 1 to 8 The UE 115 described above. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0206] At 1405, the method may include: receiving a downlink message that indicates a first configuration for a first transmit-receive point corresponding to a first cell of a non-terrestrial network and a second configuration for a second transmit-receive point corresponding to a second cell of the non-terrestrial network. The operation at 1405 may be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1405 may be performed by the mTRP communication component 725 as described with reference to Figure 7 The mTRP communication component 725 described above.

[0207] At 1410, the method may include: receiving an indication of the first transmit-receive point based on a first control resource set pool index of a control resource set configuration message, and receiving an indication of the second transmit-receive point based on a second control resource set pool index of the control resource set configuration message. The operation at 1410 may be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1410 may be performed by the CORESET configuration component 735 as described with reference to Figure 7 The CORESET configuration component 735 described above.

[0208] At 1415, the method may include: performing one or more synchronization measurements for synchronizing uplink communication with the first transmit-receive point and the second transmit-receive point based on the first configuration and the second configuration of the downlink message. The operation at 1415 may be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1415 may be performed by the uplink synchronization component 730 as described with reference to Figure 7 The uplink synchronization component 730 described above.

[0209] At 1420, the method may include: sending one or more uplink messages to the first transmit-receive point, the second transmit-receive point, or both, based on the one or more synchronization measurements. The operations at 1420 may be performed according to examples disclosed herein. In some examples, aspects of the operations at 1420 may be performed by the mTRP communication component 725 as described with reference to Figure 7 the mTRP communication component 725 described.

[0210] Figure 15 FIG. illustrates a flowchart of a method 1500 for supporting synchronization for mTRP communication in NTN according to one or more aspects of the present disclosure. The operations of method 1500 may be implemented by a UE or its components as described herein. For example, the operations of method 1500 may be performed by the UE 115 as described with reference to Figures 1 to 8 the UE 115 described. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0211] At 1505, the method may include: receiving a downlink message that indicates a first configuration for a first transmit-receive point corresponding to a first cell of a non-terrestrial network and a second configuration for a second transmit-receive point corresponding to a second cell of the non-terrestrial network. The operations at 1505 may be performed according to examples disclosed herein. In some examples, aspects of the operations at 1505 may be performed by the mTRP communication component 725 as described with reference to Figure 7 the mTRP communication component 725 described.

[0212] At 1510, the method may include: receiving the first configuration for the first transmit-receive point and the second configuration for the second transmit-receive point based on a unified transmit configuration indicator status information message. The operations at 1510 may be performed according to examples disclosed herein. In some examples, aspects of the operations at 1510 may be performed by the TCI state configuration component 740 as described with reference to Figure 7 the TCI state configuration component 740 described.

[0213] At 1515, the method may include: performing one or more synchronization measurements for synchronizing uplink communication with the first transmit-receive point and the second transmit-receive point, based on the first configuration and the second configuration of the downlink message. The operations at 1515 may be performed according to examples disclosed herein. In some examples, aspects of the operations at 1515 may be performed by the uplink synchronization component 730 as described with reference to Figure 7 the uplink synchronization component 730 described.

[0214] At 1520, the method may include: sending one or more uplink messages to the first transmit-receive point, the second transmit-receive point, or both based on the one or more synchronization measurements. The operations at 1520 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1520 may be performed by the mTRP communication component 725 as described with reference to Figure 7 The mTRP communication component 725 described in

[0215] Figure 16 FIG. 1600 is a flow diagram illustrating a method 1600 for supporting synchronization for mTRP communication in an NTN in accordance with one or more aspects of the present disclosure. The operations of method 1600 may be implemented by a UE or its components as described herein. For example, the operations of method 1600 may be performed by the UE 115 as described with reference to Figures 1 to 8 The UE 115 described in

[0216] At 1605, the method may include: receiving a downlink message that indicates a first configuration for a first transmit-receive point corresponding to a first cell of a non-terrestrial network and a second configuration for a second transmit-receive point corresponding to a second cell of the non-terrestrial network. The operations at 1605 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1605 may be performed by the mTRP communication component 725 as described with reference to Figure 7 The mTRP communication component 725 described in

[0217] At 1610, the method may include: receiving the first configuration for the first transmit-receive point and the second configuration for the second transmit-receive point based on a spatial relationship information message. The operations at 1610 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1610 may be performed by the spatial relationship information component 745 as described with reference to Figure 7 The spatial relationship information component 745 described in

[0218] At 1615, the method may include: performing one or more synchronization measurements for synchronizing uplink communication with the first transmit-receive point and the second transmit-receive point based on the first configuration and the second configuration of the downlink message. The operations at 1615 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1615 may be performed by the uplink synchronization component 730 as described with reference to Figure 7 The uplink synchronization component 730 described in

[0219] At 1620, the method may include: sending one or more uplink messages to the first transmit-receive point, the second transmit-receive point, or both based on the one or more synchronization measurements. The operation at 1620 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operation at 1620 may be performed by the mTRP communication component 725 as described with reference to Figure 7 and

[0220] Figure 17 FIG. 1700 is a flow diagram of a method 1700 for supporting synchronization for mTRP communication in an NTN in accordance with one or more aspects of the present disclosure. The operations of method 1700 may be implemented by a network entity or its components as described herein. For example, the operations of method 1700 may be performed by a network entity as described with reference to Figures 1 to 4 and Figures 9 to 12 In some examples, the network entity may execute an instruction set to control functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functions.

[0221] At 1705, the method may include: sending a downlink message to the UE, the downlink message indicating a first configuration for a first transmit-receive point corresponding to a first cell of a non-terrestrial network and a second configuration for a second transmit-receive point corresponding to a second cell of the non-terrestrial network. The operation at 1705 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operation at 1705 may be performed by the mTRP communication configuration component 1125 as described with reference to Figure 11 and

[0222] At 1710, the method may include: performing one or more synchronization measurements for synchronizing communication with the first transmit-receive point, the second transmit-receive point, and the UE based on the first configuration and the second configuration of the downlink message. The operation at 1710 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operation at 1710 may be performed by the synchronization component 1130 as described with reference to Figure 11 and

[0223] At 1715, the method may include: receiving one or more uplink messages from the UE based on the one or more synchronization measurements. The operation at 1715 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operation at 1715 may be performed by the uplink communication component 1135 as described with reference to Figure 11 and

[0224] A summary of aspects of the present disclosure is provided below:

[0225] Aspect 1: A method for wireless communication at a UE, the method comprising: receiving a downlink message indicating a first configuration for a first TRP corresponding to a first cell of an NTN and a second configuration for a second TRP corresponding to a second cell of the NTN; performing one or more synchronization measurements for synchronizing uplink communication with the first TRP and the second TRP at least in part based on the first configuration and the second configuration of the downlink message; and sending one or more uplink messages to the first TRP, the second TRP, or both according to the one or more synchronization measurements.

[0226] Aspect 2: The method according to aspect 1, wherein the downlink message comprises a CORESET configuration message, and the method further comprises: receiving an indication of the first TRP at least in part based on a first CORESET pool index of the CORESET configuration message, and receiving an indication of the second TRP at least in part based on a second CORESET pool index of the CORESET configuration message.

[0227] Aspect 3: The method according to aspect 2, the method further comprising: decoding first TCI state information associated with the first CORESET pool index and second TCI state information associated with the second CORESET pool index, wherein the first TCI state information comprises the first configuration for the first TRP and the second TCI state information comprises the second configuration for the second TRP.

[0228] Aspect 4: The method according to any one of aspects 1 to 3, wherein the downlink message comprises a unified TCI state information message, and the method further comprises: receiving the first configuration for the first TRP and the second configuration for the second TRP at least in part based on the unified TCI state information message.

[0229] Aspect 5: The method according to aspect 4, wherein the unified TCI state information message comprises combined downlink and uplink TCI state information, or separate downlink and uplink TCI state information, SSB-MTC information, or any combination thereof.

[0230] Aspect 6: The method according to any one of aspects 4 to 5, the method further comprising: performing the one or more synchronization measurements on one or more SSBs associated with the first cell and the second cell of the NTN at least in part based on the unified TCI state information message by applying corresponding timing advance amounts to the one or more synchronization measurements.

[0231] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the downlink message includes a spatial relation information message, and the method further includes: receiving the first configuration for the first TRP and the second configuration for the second TRP at least partially based on the spatial relation information message.

[0232] Aspect 8: The method according to Aspect 7, wherein the spatial relation information message includes an SSB information field corresponding to the first cell, the second cell, or both, and the SSB information field indicates the first configuration for the first TRP, the second configuration for the second TRP, or both.

[0233] Aspect 9: The method according to any one of Aspects 7 to 8, wherein the spatial relation information message includes SRS positioning information corresponding to the first configuration for the first TRP and the second configuration for the second TRP.

[0234] Aspect 10: The method according to any one of Aspects 7 to 9, wherein the spatial relation information message includes an indication of the SRS corresponding to the first configuration for the first TRP and the second configuration for the second TRP.

[0235] Aspect 11: The method according to any one of Aspects 7 to 10, wherein the spatial relation information message includes an indication of the physical uplink control channel corresponding to the first configuration for the first TRP and the second configuration for the second TRP.

[0236] Aspect 12: The method according to any one of Aspects 1 to 11, the method further includes: sending a message to a network entity, the message indicating the UE's ability to communicate with the first TRP and the second TRP in the NTN.

[0237] Aspect 13: The method according to any one of Aspects 1 to 12, wherein the second configuration includes a configuration of a virtual cell, and performing the one or more synchronization measurements further includes: performing the one or more synchronization measurements with respect to the virtual cell spatially located between the first TRP and the second TRP to at least partially synchronize the uplink communication with the first TRP and the second TRP; and sending the one or more uplink messages to the first TRP and the second TRP at least partially based on performing the one or more synchronization measurements with respect to the virtual cell.

[0238] Aspect 14: The method according to any one of Aspects 1 to 13, wherein receiving the downlink message further includes: receiving a third configuration for a third TRP corresponding to a third cell of the NTN; and performing the one or more synchronization measurements to synchronize the uplink communication with the first TRP, the second TRP, and the third TRP at least in part based on the third configuration.

[0239] Aspect 15: The method according to any one of Aspects 1 to 14, wherein the first configuration for the first TRP and the second configuration for the second TRP include timing information, non-terrestrial network configuration information, physical cell identifiers, virtual cell identifiers, or any combination thereof.

[0240] Aspect 16: The method according to any one of Aspects 1 to 15, wherein the one or more synchronization measurements include Doppler shift pre-compensation measurements associated with the first TRP and the second TRP in the NTN.

[0241] Aspect 17: The method according to any one of Aspects 1 to 16, wherein the first configuration for the first TRP includes a first physical cell identifier or a first virtual cell identifier, and the second configuration for the second TRP includes a second physical cell identifier or a second virtual cell identifier.

[0242] Aspect 18: A method for wireless communication at a network entity, the method including: sending a downlink message to a UE, the downlink message indicating a first configuration for a first TRP corresponding to a first cell of an NTN and a second configuration for a second TRP corresponding to a second cell of the NTN; performing one or more synchronization measurements for synchronizing communication with the first TRP, the second TRP, and the UE at least in part based on the first configuration and the second configuration of the downlink message; and receiving one or more uplink messages from the UE according to the one or more synchronization measurements.

[0243] Aspect 19: The method according to Aspect 18, wherein the downlink message includes a CORESET configuration message, and the method further includes: sending an indication of the first TRP to the UE at least in part based on a first CORESET pool index of the CORESET configuration message, and sending an indication of the second TRP to the UE at least in part based on a second CORESET pool index of the CORESET configuration message.

[0244] Aspect 20: The method according to aspect 19, wherein the downlink message further includes first TCI state information associated with the first CORESET pool index and second TCI state information associated with the second CORESET pool index, and the first TCI state information includes the first configuration for the first TRP and the second TCI state information includes the second configuration for the second TRP.

[0245] Aspect 21: The method according to any one of aspects 18 to 20, wherein the downlink message includes a unified TCI state information message, and the method further includes: sending the first configuration for the first TRP and the second configuration for the second TRP to the UE at least partially based on the unified TCI state information message.

[0246] Aspect 22: The method according to aspect 21, wherein the unified TCI state information message includes combined downlink and uplink TCI state information, or separate downlink and uplink TCI state information, SSB machine type communication information, or a combination thereof.

[0247] Aspect 23: The method according to any one of aspects 18 to 22, wherein the downlink message includes a spatial relation information message, and the method further includes: sending the first configuration for the first TRP and the second configuration for the second TRP to the UE at least partially based on the spatial relation information message.

[0248] Aspect 24: The method according to aspect 23, wherein the spatial relation information message includes an SSB information field corresponding to the first cell, the second cell, or both, and the SSB information field indicates the first configuration for the first TRP, the second configuration for the second TRP, or both.

[0249] Aspect 25: The method according to any one of aspects 23 to 24, wherein the spatial relation information message includes SRS positioning information corresponding to the first configuration for the first TRP and the second configuration for the second TRP.

[0250] Aspect 26: The method according to any one of aspects 18 to 25, the method further includes: receiving a message indicating the UE's ability to communicate with the first TRP and the second TRP in the NTN.

[0251] Aspect 27: The method according to any one of aspects 18 to 26, wherein the second configuration includes a configuration of a virtual cell, and the method further includes: receiving, from the UE, one or more uplink messages synchronized to the virtual cell; and performing one or more post-processing procedures to synchronize the one or more uplink messages to the timing of the first cell and the second cell.

[0252] Aspect 28: The method according to any one of aspects 18 to 27, wherein receiving the downlink message further includes: sending a third configuration for a third TRP corresponding to a third cell of the NTN; and performing the one or more synchronization measurements at least partially based on the third configuration to synchronize the communication with the first TRP, the second TRP, the third TRP, and the UE.

[0253] Aspect 29: An apparatus for wireless communication at a UE, the apparatus includes: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to any one of aspects 1 to 17.

[0254] Aspect 30: An apparatus for wireless communication at a UE, the apparatus includes: at least one component for performing the method according to any one of aspects 1 to 17.

[0255] Aspect 31: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code includes instructions executable by a processor to perform the method according to any one of aspects 1 to 17.

[0256] Aspect 32: An apparatus for wireless communication at a network entity, the apparatus includes: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to any one of aspects 18 to 28.

[0257] Aspect 33: An apparatus for wireless communication at a network entity, the apparatus includes: at least one component for performing the method according to any one of aspects 18 to 28.

[0258] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code includes instructions executable by a processor to perform the method according to any one of aspects 18 to 28.

[0259] Note that the methods described herein depict possible specific implementations, and the operations and steps may be rearranged or otherwise modified and other specific implementations are possible. Additionally, aspects from two or more methods may be combined.

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

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

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

[0263] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these items. The features implementing the functions can also be physically located at different positions, including being distributed such that different portions of the functions are implemented at different physical locations.

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

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

[0266] The term "determine" encompasses a variety of actions, and thus, "determine" can include operations, calculations, processing, derivation, research, lookups (such as looking up via a table, database, or other data structure), ascertaining, and similar actions. Additionally, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Further, "determine" can include parsing, obtaining, selecting, choosing, establishing, and other such similar actions.

[0267] In the drawings, like components or features may have the same reference numerals. Additionally, various components of the same type can be distinguished by adding a dash and a second label used to differentiate between like components after the reference numeral. If only the first reference numeral is used in the specification, the description can apply to any of the like components having the same first reference numeral, regardless of the second reference numeral or other subsequent reference numerals.

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

[0269] The description provided herein enables a person of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure are obvious to a person of ordinary skill in the art, and the general principles defined herein can be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a User Equipment (UE), the method comprising: Receive a downlink message that indicates a first configuration for a first transmission reception point corresponding to a first cell of a non-terrestrial network and a second configuration for a second transmission reception point corresponding to a second cell of the non-terrestrial network; Perform one or more synchronization measurements for synchronizing uplink communication with the first transmission reception point and the second transmission reception point, at least in part based on the first configuration and the second configuration of the downlink message; and Send one or more uplink messages to the first transmission reception point, the second transmission reception point, or both, according to the one or more synchronization measurements.

2. The method according to claim 1, wherein the downlink message comprises a control resource set configuration message, the method further comprising: Receive an indication of the first transmission reception point at least in part based on a first control resource set pool index of the control resource set configuration message, and receive an indication of the second transmission reception point at least in part based on a second control resource set pool index of the control resource set configuration message.

3. The method according to claim 2, the method further comprising: Decode first transmission configuration indicator status information associated with the first control resource set pool index and second transmission configuration indicator status information associated with the second control resource set pool index, wherein the first transmission configuration indicator status information includes the first configuration for the first transmission reception point and the second transmission configuration indicator status information includes the second configuration for the second transmission reception point.

4. The method according to claim 1, wherein the downlink message comprises a unified transmission configuration indicator status information message, the method further comprising: Receive the first configuration for the first transmission reception point and the second configuration for the second transmission reception point at least in part based on the unified transmission configuration indicator status information message.

5. The method according to claim 4, wherein the unified transmission configuration indicator status information message comprises combined downlink and uplink transmission configuration indicator status information, or separate downlink and uplink transmission configuration indicator status information, synchronization signal block - machine type communication information, or any combination thereof.

6. The method according to claim 4, the method further comprising: Perform the one or more synchronization measurements on one or more synchronization signal blocks associated with the first cell and the second cell of the non-terrestrial network, at least in part based on the unified transmission configuration indicator status information message, by applying respective timing advance amounts to the one or more synchronization measurements.

7. The method according to claim 1, wherein the downlink message comprises a spatial relation information message, the method further comprising: Receive the first configuration for the first transmission reception point and the second configuration for the second transmission reception point at least in part based on the spatial relationship information message.

8. The method according to claim 7, wherein the spatial relation information message comprises a synchronization signal block information field corresponding to the first cell, the second cell, or both, the synchronization signal block information field indicating the first configuration for the first transmit - receive point, the second configuration for the second transmit - receive point, or both.

9. The method according to claim 7, wherein the spatial relation information message comprises sounding reference signal positioning information corresponding to the first configuration for the first transmit - receive point and the second configuration for the second transmit - receive point.

10. The method according to claim 7, wherein the spatial relation information message comprises an indication of a sounding reference signal corresponding to the first configuration for the first transmit - receive point and the second configuration for the second transmit - receive point.

11. The method according to claim 7, wherein the spatial relation information message includes an indication of a physical uplink control channel corresponding to the first configuration for the first transmit-receive point and the second configuration for the second transmit-receive point.

12. The method according to claim 1, the method further comprising: Send a message to a network entity that indicates the UE's ability to communicate with the first transmission reception point and the second transmission reception point in the non-terrestrial network.

13. The method according to claim 1, wherein the second configuration includes a configuration of a virtual cell, and performing the one or more synchronization measurements further includes: Perform the one or more synchronization measurements with respect to a virtual cell that is spatially located between the first transmission reception point and the second transmission reception point to at least in part synchronize the uplink communication with the first transmission reception point and the second transmission reception point; and Send the one or more uplink messages to the first transmission reception point and the second transmission reception point at least in part based on performing the one or more synchronization measurements with respect to the virtual cell.

14. The method according to claim 1, wherein receiving the downlink message further includes: Receive a third configuration for a third transmission reception point corresponding to a third cell of the non-terrestrial network; and Perform the one or more synchronization measurements to synchronize the uplink communication with the first transmission reception point, the second transmission reception point, and the third transmission reception point, at least in part based on the third configuration.

15. The method according to claim 1, wherein the first configuration for the first transmit-receive point and the second configuration for the second transmit-receive point include timing information, non-terrestrial network configuration information, a physical cell identifier, a virtual cell identifier, or any combination thereof.

16. The method according to claim 1, wherein the one or more synchronization measurements include Doppler frequency shift pre-compensation measurements associated with the first transmit-receive point and the second transmit-receive point in the non-terrestrial network.

17. The method according to claim 1, wherein the first configuration for the first transmit-receive point includes a first physical cell identifier or a first virtual cell identifier, and the second configuration for the second transmit-receive point includes a second physical cell identifier or a second virtual cell identifier.

18. A method for wireless communication at a network entity, the method comprising: Send a downlink message to a user equipment (UE), the downlink message indicating a first configuration for a first transmission reception point corresponding to a first cell of a non-terrestrial network and a second configuration for a second transmission reception point corresponding to a second cell of the non-terrestrial network; Perform one or more synchronization measurements for synchronizing communications with the first transmission reception point, the second transmission reception point, and the UE, at least in part based on the first configuration and the second configuration of the downlink message; and Receive one or more uplink messages from the UE according to the one or more synchronization measurements.

19. The method according to claim 18, wherein the downlink message includes a control resource set configuration message, the method further comprising: Send an indication of the first transmission reception point to the UE at least in part based on a first control resource set pool index of the control resource set configuration message, and send an indication of the second transmission reception point to the UE at least in part based on a second control resource set pool index of the control resource set configuration message.

20. The method according to claim 19, wherein the downlink message further comprises first transmission configuration indicator status information associated with the first control resource set pool index and second transmission configuration indicator status information associated with the second control resource set pool index, and the first transmission configuration indicator status information comprises the first configuration for the first transmit-receive point and the second transmission configuration indicator status information comprises the second configuration for the second transmit-receive point.

21. The method according to claim 18, wherein the downlink message comprises a unified transmission configuration indicator status information message, and the method further comprises: Send the first configuration for the first transmission reception point and the second configuration for the second transmission reception point to the UE at least in part based on the unified transmission configuration indicator status information message.

22. The method according to claim 21, wherein the unified transmission configuration indicator status information message comprises combined downlink and uplink transmission configuration indicator status information, or separate downlink and uplink transmission configuration indicator status information, synchronization signal block - machine type communication information, or a combination thereof.

23. The method according to claim 18, wherein the downlink message comprises a spatial relation information message, and the method further comprises: Send the first configuration for the first transmission reception point and the second configuration for the second transmission reception point to the UE at least in part based on the spatial relationship information message.

24. The method according to claim 23, wherein the spatial relation information message comprises a synchronization signal block information field corresponding to the first cell, the second cell, or both, and the synchronization signal block information field indicates the first configuration for the first transmit-receive point, the second configuration for the second transmit-receive point, or both.

25. The method according to claim 23, wherein the spatial relation information message comprises sounding reference signal positioning information corresponding to the first configuration for the first transmit-receive point and the second configuration for the second transmit-receive point.

26. The method according to claim 18, the method further comprises: Receive a message indicating the ability of the UE to communicate with the first transmission reception point and the second transmission reception point in the non-terrestrial network.

27. The method according to claim 18, wherein the second configuration comprises a configuration for a virtual cell, and the method further comprises: Receive the one or more uplink messages synchronized to the virtual cell from the UE; and Perform one or more post-processing procedures to synchronize the one or more uplink messages to the timing of the first cell and the second cell.

28. The method according to claim 18, wherein receiving the downlink message further comprises: Send a third configuration for a third transmission reception point corresponding to a third cell of the non-terrestrial network; and Perform the one or more synchronization measurements to synchronize the communications with the first transmission reception point, the second transmission reception point, the third transmission reception point, and the UE at least in part based on the third configuration.

29. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: A processor; A memory coupled to the processor; and Instructions stored in the memory and executable by the processor to cause the device to: Receive a downlink message indicating a first configuration for a first transmission reception point corresponding to a first cell of a non-terrestrial network and a second configuration for a second transmission reception point corresponding to a second cell of the non-terrestrial network; Perform one or more synchronization measurements for synchronizing uplink communications with the first transmission reception point and the second transmission reception point, at least in part based on the first configuration and the second configuration of the downlink message; and Send one or more uplink messages to the first transmission reception point, the second transmission reception point, or both according to the one or more synchronization measurements.

30. An apparatus for wireless communication at a network entity, the apparatus comprising: A processor; A memory coupled to the processor; and Instructions stored in the memory and executable by the processor to cause the device to: Send a downlink message to a user equipment (UE), the downlink message indicating a first configuration for a first transmission reception point corresponding to a first cell of a non-terrestrial network and a second configuration for a second transmission reception point corresponding to a second cell of the non-terrestrial network; Perform one or more synchronization measurements for synchronizing communication with the first transmission reception point, the second transmission reception point, and the UE, at least partially based on the first configuration and the second configuration of the downlink message; And Receive one or more uplink messages from the UE according to the one or more synchronization measurements.

Images