Multiple transmission reception (TRP) operations based on multiple timing advance (TA)

Abstract

This application relates to uplink transmission using multiple TAs. In one example, the base station may configure the UE to use multiple TAGs in association with a non-uniform TCI framework and / or single DCI multi-TRP operation. The base station then transmits signaling information to the UE. The signaling information may activate the TCI state for multi-TRP uplink transmission and / or schedule multi-TRP uplink transmission. Based on the signaling information and configuration information, the UE determines a first TAG to be used for a first uplink transmission and a second TAG to be used for a second uplink transmission. Based on these two TAGs, the UE determines a first TA to be used for a first uplink transmission to a first TRP and a second TA to be used for a second uplink transmission to a second TRP.

Description

Cross-reference to related applications

[0001] This application claims priority to U.S. Non-Provisional Application No. 18 / 817,044, filed August 27, 2024, entitled “MULTIPLE TRANSMISSION ANDRECEPTION (TRP) OPERATIONS BASED ON MULTIPLE TIMING ADVANCES (TAS),” which claims the benefit and priority to U.S. Provisional Application No. 63 / 604,845, filed November 30, 2023, entitled “MULTIPLE TRANSMISSION ANDRECEPTION (TRP) OPERATIONS BASED ON MULTIPLE TIMING ADVANCES (TAS),” which are incorporated herein by reference in their entirety for all purposes. Background Technology

[0002] Fifth-generation mobile networks (5G) are a wireless standard designed to improve data transmission speed, reliability, availability, and more. While still under development, this standard includes many details related to communication between user equipment (UE) and the network's transmit / receive points (TRPs) for transmitting and receiving data. Communication may rely on one or more channels available from one or more beams provided by the TRP and detected by the UE. Attached Figure Description

[0003] Figure 1 Examples of network environments based on some implementation schemes are shown.

[0004] Figure 2 Examples of cells comprising multiple Transmitter Points (TRPs) according to some implementation schemes are illustrated.

[0005] Figure 3 Examples of propagation delays associated with multiple TRPs according to some implementation schemes are illustrated.

[0006] Figure 4 Examples of multiple timing advances (TAs) for uplink transmission to multiple TRPs are illustrated according to some implementation schemes.

[0007] Figure 5 Examples of sequence diagrams for using multiple TAs are illustrated according to some implementation schemes.

[0008] Figure 6Examples of configuring a user equipment (UE) to use multiple TAs are illustrated according to some implementation schemes.

[0009] Figure 7 Another example of configuring a UE to use multiple TAs is illustrated according to some implementation schemes.

[0010] Figure 8 Another example of configuring a UE to use multiple TAs is illustrated according to some implementation schemes.

[0011] Figure 9 Examples of Media Access Control (MAC) control elements (CEs) for indicating a TA to be used with Physical Uplink Control Channel (PUCCH) transmission are shown according to some implementation schemes.

[0012] Figure 10 An example of a MAC CE for indicating a TA to be used with a probe reference signal (SRS) transmission is shown according to some implementation schemes.

[0013] Figure 11 An example is shown of a single downlink control information (DCI) indicating the TA to be used in a multi-TRP transmission according to some implementation schemes.

[0014] Figure 12 Examples of how conflicts arise from the use of multiple TAs are illustrated in some implementation schemes.

[0015] Figure 13 Examples of operational flow / algorithm structures for UEs to use multiple TAs are illustrated according to some implementation schemes.

[0016] Figure 14 Examples of operational flow / algorithm structures for configuring a UE to use multiple TAs are illustrated according to some implementation schemes.

[0017] Figure 15 Examples of receiving components according to some implementation schemes are shown.

[0018] Figure 16 Examples of UEs according to some implementation schemes are shown.

[0019] Figure 17 Examples of base stations based on some implementation schemes are shown. Detailed Implementation

[0020] The following detailed description refers to the accompanying drawings. The same reference numerals may be used to identify the same or similar elements in different drawings. In the following description, specific details, such as particular structures, architectures, interfaces, technologies, etc., are set forth for illustrative and non-limiting purposes to provide a thorough understanding of various aspects of the various embodiments. However, it will be apparent to those skilled in the art that various aspects of the various embodiments may be practiced in other examples departing from these specific details. In some instances, descriptions of well-known devices, circuits, and methods have been omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of this document, the phrase "A or B" refers to (A), (B), or (A and B).

[0021] Generally, User Equipment (UE) can communicate with the network, such as with Transmit and Receive Points (TRPs) of a cell. To improve data throughput, a Multiple-Input Multiple-Output (MIMO) implementation can be used, where the UE can communicate with two or more TRPs of the cell. In a MIMO implementation, communication with a TRP may rely on one or more channels available from the TRP and detected by the UE. Given the relative position of the UE to each TRP, there may be different propagation delays. Therefore, if the UE transmits simultaneously to a TRP, the TRP's reception of such transmissions may not be time-synchronized due to the different propagation delays.

[0022] To address these and other challenges, embodiments of this disclosure involve the use of multiple timing advances (TAs). For example, the UE may transmit a first uplink transmission to a first TRP and a second uplink transmission to a second TRP. However, the two uplink transmissions may be based on two different timing advances that take into account the propagation delay between the UE and the two TRPs.

[0023] To enable multiple TA (Transmission Acquisition Group) usage, a base station comprising two TRPs can transmit configuration information to the UE. This configuration information indicates a TA group (TAG) and can be used with a Non-Unified Transmission Configuration Indication (TCI) framework and / or a Single Downlink Control Information (DCI) multi-TRP operation. Subsequently, the base station transmits signaling information to the UE. The signaling information can activate the TCI state for multi-TRP uplink transmission and / or schedule multi-TRP uplink transmission. For example, the signaling information includes activating the TCI state for multi-TRP uplink transmission and / or a Media Access Control (MAC) control element (CE) for a single DCI. Based on the signaling information and configuration information, the UE determines a first TAG to be used for the first uplink transmission and a second TAG to be used for the second uplink transmission. Based on these two TAGs, the UE determines a first TA to be used for the first uplink transmission and a second TA to be used for the second uplink transmission.

[0024] The following is a glossary of terms that may be used in this disclosure.

[0025] As used herein, the term "circuit" refers to, is part of, or includes the following: hardware components such as electronic circuits, logic circuits, processors (shared, dedicated, or grouped) or memories (shared, dedicated, or grouped), application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable system-on-chips (SoCs)), or digital signal processors (DSPs) configured to provide the described functionality. In some embodiments, the circuit may execute one or more software or firmware programs to provide at least some of the described functionalities. The term "circuit" may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) and program code for executing the functionality. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit.

[0026] As used herein, the term "processor circuit" means, is part of, or includes a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transmitting digital data. The term "processor circuit" may also refer to an application processor, baseband processor, central processing unit (CPU), graphics processing unit, single-core processor, dual-core processor, triple-core processor, quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions such as program code, software modules, and / or functional processes.

[0027] As used herein, the term "interface circuit" refers to, is part of, or includes a circuit that enables the exchange of information between two or more components or devices. The term "interface circuit" can refer to one or more hardware interfaces, such as buses, I / O interfaces, peripheral component interfaces, or network interface cards.

[0028] As used herein, the term "user equipment" or "UE" refers to equipment of a remote user that has radio communication capabilities and can describe network resources in a communication network. Furthermore, the term "user equipment" or "UE" can be considered synonymous and can be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Additionally, the term "user equipment" or "UE" can include any type of wireless / wired equipment or any computing device that includes a wireless communication interface.

[0029] As used herein, the term "TRP" refers to a device with radio communication capabilities, which is a network node (or more simply, the network) in a communication network and can be configured as an access node within the communication network. The UE's access to the communication network can be managed at least partially by the TRP, thereby connecting the UE to the TRP to access the communication network. Depending on the Radio Access Technology (RAT), the TRP may have multiple transmit and receive antenna elements that generate directional beams.

[0030] As used herein, the term "computer system" means any type of interconnected electronic device, computer device, or component thereof. Additionally, the term "computer system" or "system" may refer to various components of a computer that are communicatively coupled to each other. Furthermore, the term "computer system" or "system" may refer to multiple computer devices or multiple computing systems that are communicatively coupled to each other and configured to share computing resources or network resources.

[0031] As used herein, the term "resource" refers to physical or virtual devices, physical or virtual components within a computing environment, or physical or virtual components within a specific device, such as computer equipment, mechanical equipment, memory space, processor / CPU time, processor / CPU utilization, processor and accelerator load, hardware time or utilization, power supply, input / output operations, port or network sockets, channel / link allocation, throughput, memory utilization, storage, network, databases and applications, units of workload, etc. "Hardware resource" can refer to computing, storage, or networking resources provided by physical hardware components. "Virtualized resource" can refer to computing, storage, or networking resources provided by virtualization infrastructure to applications, devices, systems, etc. The terms "network resource" or "communication resource" can refer to resources that a computer device / system can access via a communication network. The term "system resource" can refer to any kind of shared entity providing a service and can include computing or network resources. System resources can be considered as a coherent set of functions, network data objects, or services that can be accessed through a server, wherein such system resources reside on a single host or multiple hosts and can be clearly identified.

[0032] As used herein, the term "channel" refers to any tangible or intangible transmission medium used to transmit data or data streams. The term "channel" may be synonymous or equivalent with "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," or any other similar term indicating a means or medium through which data is transmitted. Additionally, as used herein, the term "link" refers to a connection between two devices used for transmitting and receiving information.

[0033] As used in this article, the terms "instantiate" and "instantiate" refer to the creation of an instance. "Instance" also refers to the concrete occurrence of an object, which may occur, for example, during the execution of program code.

[0034] The term "connection" can refer to an established signaling relationship between two or more elements at a common communication protocol layer through a communication channel, link, interface, or reference point.

[0035] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as networked computers, network hardware, network equipment, network nodes, virtualized network functions, etc.

[0036] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to a single piece of content within an information element or a data element that contains content. An information element may include one or more additional information elements.

[0037] Figure 1 A network environment 100 according to some implementation schemes is illustrated. Network environment 100 may include UE 104 and gNB 108. gNB 108 may be a base station providing radio access, for example, a 3GPP New Radio (NR) cell through which UE 104 communicates with gNB 108. UE 104 and gNB 108 may communicate via an air interface compatible with 3GPP technical specifications, such as those defining the fifth-generation (5G) NR system standard. As further described in the following figure, gNB 108 may be deployed as a TRP in a cell comprising multiple TRPs.

[0038] The gNB 108 transmits information (e.g., data and control signaling) in the downlink direction by mapping logical channels onto transport channels and transport channels onto physical channels. Logical channels transmit data between the Radio Link Control (RLC) and MAC layers; transport channels transmit data between the MAC and PHY layers; and physical channels transmit information across the air interface. Physical channels may include the Physical Broadcast Channel (PBCH), the Physical Downlink Control Channel (PDCCH), and the Physical Downlink Shared Channel (PDSCH).

[0039] The PBCH can be used to broadcast system information that UE 104 can use for initial access to the serving cell. The PBCH can be transmitted in the SSB along with the Physical Synchronization Signal (PSS) and the Secondary Synchronization Signal (SSS). The SSB can be used by UE 104 during the cell search process (including cell selection and reselection) and for beam selection.

[0040] PDSCH can be used to transmit end-user application data, signaling radio bearer (SRB) messages, system information messages (other than MIBs), and SIs.

[0041] The PDCCH can transmit DCIs used by the gNB 108 scheduler to allocate both uplink and downlink resources. DCIs can also be used to provide uplink power control commands, configure time slot formats, or indicate that preemption has occurred.

[0042] gNB 108 can also transmit various reference signals to UE 104. These reference signals may include demodulation reference signals (DMRS) for PBCH, PDCCH, and PDSCH. UE 104 can compare the received version of the DMRS with the transmitted known DMRS sequence to estimate the impact of the propagation channel. UE 104 can then apply the inverse channel of the propagation channel during the demodulation process transmitted on the corresponding physical channel.

[0043] Reference signals may also include Channel State Information Reference Signals (CSI-RS). CSI-RS can be a multi-purpose downlink transmit signal used for CSI reporting, beam management, connection mode mobility, radio link failure detection, beam failure detection and recovery, and fine-tuning of time and frequency synchronization. Similarly, the UE may transmit reference signals to the gNB 108 for measurements to be performed by the gNB 108 (e.g., in applications where reciprocity is not assumed between downlink and uplink channels). These reference signals may include, for example, Sounding Reference Signals (SRS).

[0044] Reference signals and information from the physical channel can be mapped to resources in the resource grid. For a given antenna port, subcarrier spacing configuration, and transmission direction (e.g., downlink or uplink), there exists a resource grid. The basic unit of the NR downlink resource grid can be a resource element, which can be defined by a subcarrier in the frequency domain and an orthogonal frequency division multiplexing (OFDM) symbol in the time domain. Twelve consecutive subcarriers in the frequency domain can constitute a physical resource block (PRB). A resource element group (REG) can include a PRB in the frequency domain and an OFDM symbol in the time domain, for example, twelve resource elements. A control channel element (CCE) can represent a resource group used to transmit the PDCCH. One CCE can be mapped to multiple REGs, for example, six REGs.

[0045] UE 104 can use physical uplink channels to send data and control information to gNB 108. Different types of physical uplink channels are possible, including, for example, the Physical Uplink Control Channel (PUCCH) and the Physical Uplink Shared Channel (PUSCH). The PUCCH carries control information from UE 104 to gNB 108, such as uplink control information (UCI), while the PUSCH carries data traffic (e.g., end-user application data) and may carry UCI.

[0046] UE 104 and gNB 108 can perform beam management operations to identify and maintain the desired beams for transmission in both the uplink and downlink directions. Beam management can be applied to both PDSCH and PDCCH in the downlink direction, and both PUSCH and PUCCH in the uplink direction.

[0047] In one example, communication with the gNB 108 and / or the base station can utilize channels in Frequency Range 1 (FR1), Frequency Range 2 (FR2), and / or higher frequency ranges (FRH). The FR1 band includes licensed and unlicensed frequency bands. The NR unlicensed band (NR-U) includes spectrum shared with other types of Radio Access Technologies (RATs) (e.g., LTE-LAA, WiFi, etc.). A Listen-Before-Speak (LBT) process can be used to avoid or minimize conflicts between different RATs in the NR-U, whereby the device should apply a Clear Channel Assessment (CCA) check before using the channel.

[0048] Figure 2 Example 200 of a cell 210 comprising multiple TRPs according to some implementation schemes is illustrated. In this illustration, cell 210 includes two TRPs: a first TRP 201 and a second TRP 202 associated with the same base station (e.g., gNB 108). However, a larger number of TRPs per base station is also possible. Generally, cell 210 is a serving cell with MIMO communication enabled, where UE 204 (e.g., UE 104) can communicate simultaneously with TRP 201 and TRP 202 to simultaneously send and / or receive information (e.g., traffic data). Each TRP of cell 210 can transmit multiple directional beams ( Figure 2 Three beams labeled "0" to "2" (Synchronization Signal Block (SSB)) are illustrated, but a different number of directional beams are also possible) and can be extended to cover the area surrounding the TRP. Based on beam measurements (such as Reference Signal Received Power (RSRP) and / or Reference Signal Received Quality (RSRQ)), the UE 204 can select a specific beam transmitted by the TRP to support communication with that TRP. Figure 2In the example, UE 204 uses SSB2 to communicate with TRP 201 and uses SSB0 to communicate with TRP 202.

[0049] In carrier aggregation mode, the network can configure cell 210 as either a PCell or an SCell. In dual connectivity mode, the network can configure cell 210 as a PCell, PSCell, or SCell. SpCell refers to either a PCell or a PSCell.

[0050] The network can configure UE 204 to communicate with TRP 201 and TRP 202 by transmitting configuration information to UE 204 (e.g., via RRC signaling), as further described below. Once UE 204 is configured, UE 204 can determine timing advances based on the configuration information and possibly based on other signaling information (e.g., via MAC CE and / or DCI) to perform uplink transmissions to TRP 201 and TRP 202, as further described below.

[0051] Figure 3 Example 300 illustrates propagation delays associated with multiple TRPs according to some implementation schemes. Figure 2 As illustrated in the example, UE 304 (e.g., UE 104) may communicate with a first TRP 301 (e.g., TRP 201) and a second TRP 302 (e.g., TRP 202) associated with the same base station (e.g., gNB 108). Communication may include uplink transmission and downlink reception 310 between UE 304 and the first TRP 301, and uplink transmission and downlink reception 320 between UE 304 and the second TRP 302. Uplink transmission from UE 304 to the first TRP 301 may occur simultaneously with uplink transmission from UE 304 to the second TRP. Similarly, downlink reception from the first TRP 301 to UE 304 may occur simultaneously with downlink reception from the second TRP 302 to UE 304.

[0052] exist Figure 3In the example, UE 304 does not use any TA for multi-TRP uplink transmission 330 (e.g., uplink transmission to first TRP 301 and to second TRP 302). Alternatively, multi-TRP uplink transmission 330 is performed using the same TA. In both cases, there is a first propagation delay 351 for the first uplink transmission from UE 304 to first TRP 301, and a second propagation delay 352 for the second uplink transmission from UE 304 to second TRP 302. The two propagation delays 351 and 352 may differ due to various factors (e.g., the relative position of UE 304 to each of the two TRPs 301 and 302). Therefore, first TRP 301 can receive the first uplink transmission at the first moment (this reception is in Figure 3 (shown as UL receiver 341), and can receive a second uplink transmission at a second time different from the first time (this reception is in) Figure 3 (As shown in the diagram, UL receiver 342). In other words, the two receivers may not be time-synchronized, which could lead to a degraded quality of multi-TRP communication.

[0053] Figure 4 Examples of multiple TAs sent uplink to multiple TRPs are illustrated according to some implementation schemes. Figure 3 As illustrated in the example, UE 404 (e.g., UE 104) may communicate with a first TRP 401 (e.g., TRP 301) and a second TRP 402 (e.g., TRP 402) associated with the same base station (e.g., gNB 108). Communication may include uplink transmission and downlink reception 410 between UE 404 and the first TRP 401, and uplink transmission and downlink reception 420 between UE 404 and the second TRP 402. The UE may perform multiple TRP transmissions, such as simultaneously performing a first uplink transmission to the first TRP 401 431 and a second uplink transmission to the second TRP 402 432.

[0054] In one example, the first uplink transmit 431 is associated with the first TA 451, while the second uplink transmit 432 is associated with the second TA 452. TA 451 and TA 452 are different, allowing the first TRP 401 to be received in conjunction with the second uplink transmit 432 (this reception is in...). Figure 4 The same time (e.g., in a time-synchronized manner, as shown in UL receiving 442) Figure 4 The diagram shows the time synchronization (453) receiving the first uplink transmission (431) (this reception is in...). Figure 4(As shown in the diagram, UL receiver 441). In other words, the two TAs 451 and TA 452 take into account different propagation delays to produce time synchronization 453.

[0055] Generally, uplink transmission can be scheduled by the base station (e.g., via DCI and / or according to uplink permission). Scheduling can indicate (or be determined by the UE) the timing for starting uplink transmission (e.g., the time slot and symbols in the time slot on the uplink channel). This timing can be scheduled based on a number of parameters (including the TA to be used) (or determined by the UE based on these parameters).

[0056] Instead of maintaining a single TA per cell, sets of co-located cells can be grouped into the same TAG associated with a TA, making the TA applicable to cells belonging to that group. A TAG can be associated with one or more cells and a TA applicable to those cells. The cell-to-TA mapping is configured by RRC. Multiple TAGs (e.g., up to four TAGs) can also be configured via RRC.

[0057] In a multi-TRP scenario, the maximum transmission timing difference (MTTD) between different TRPs (e.g., TRP 401 and TRP 402) may be greater than the duration of the cyclic prefix (CP) for various reasons. One reason is a large timing synchronization error between two or more TRPs. Another reason is (e.g., in UE 404) significant spatial differences between different antenna panels or different TRPs.

[0058] To address such challenges in multi-TRP scenarios (including multiple-input multiple-output (MIMO) implementations), more than one TA can be used for different TRPs serving the same cell (e.g., associated with the same base station). For example, a single serving cell (e.g., Figure 2 The community 210 can be configured with two or more TAGs.

[0059] Return to reference Figure 4As illustrated, the first TRP 401 and the second TRP 402 are part of the same cell (e.g., cell 210). The cell may be configured with two TAGs (e.g., via RRC signaling). This configuration (e.g., TAG configuration) enables the UE to perform multiple TRP transmissions using the first TAG 451 and the second TAG 452. Specifically, the first uplink transmission 431 may be associated with the first TAG of the two configured TAGs, while the second uplink transmission 432 may be associated with the second TAG of the two configured TAGs. The first TAG is then associated with the first TAG 451, and the second TAG is associated with the second TAG 452. Based on the first TAG 451 and the second TAG 452, the first uplink transmission 431 and the second uplink transmission 432 are transmitted simultaneously. Simultaneous transmission may mean that there is at least some overlap (e.g., at least one symbol) between the transmissions in the time domain.

[0060] The following section further describes examples of TAG configuration. Additionally, the following section further describes examples of signaling information that enables the use of multiple TAGs for multi-TRP uplink transmissions in association with non-uniform TCI or single DCI multi-TRP uplink transmissions.

[0061] In the context of NR networks, a unified TCI was introduced in version 17 of the NR standard defined by 3GPP. A legacy TCI refers to a TCI defined prior to version 17, and this TCI continues to be supported in version 17 and newer versions of the NR standard. A non-unified TCI is used synonymously with legacy TCI in this document (e.g., to indicate that it is not a unified TCI introduced in version 17, but rather a TCI prior to version 17). A single DCI for multi-TRP uplink transmissions (also known as single-DCI multi-TRP operation or single-DCI-based multi-TRP operation) was also introduced, where the same DCI can indicate parameters used for uplink transmissions by the UE to multiple TRPs.

[0062] Figure 5 An example of a sequence diagram 500 for using multiple TAs according to some implementation schemes is illustrated. Specifically, base station 520 may include K One TRP, and UE 510 can be used with K One TRP communication, of which KThe value is a positive integer equal to or greater than two. In the first step of sequence diagram 300, UE 510 may transmit capability information to base station 520. The capability information may indicate several supported features. The first feature may relate to multi-TRP transmission. For example, UE 510 may indicate its support for single-DCI multi-TRP operations (such as single-DCI multi-TRP STx2P SDM PUSCH, single-DCI multi-TRP STx2P SFN PUSCH and single-DCI multi-TRP STx2P SFN PUCCH, single-DCI multi-TRP PUSCH / PUCCH repetition, etc., or all of them). The second feature may relate to TA. For example, UE 510 may indicate its support for dual-TA (or more generally, multi-TA) operations for PUSCH and / or PUCCH transmission. The third feature may relate to a combination of multi-TRP transmission and multi-TA operations. For example, UE 510 can report whether the network can be configured to use two (or more) TAs that can be used in combination with any or all of the following: Single DCI Multiple TRP STx2P SDM PUSCH, Single DCI Multiple TRP STx2P SFN PUSCH, Single DCI Multiple TRP STx2P SFNPUCCH, Single DCI Multiple TRP PUSCH / PUCCH repetition, etc.

[0063] Next, base station 520 may transmit configuration information to UE 510. This configuration information may be based on capability information. Assuming UE 510 supports multiple TRP transmissions and multiple TA operations, the configuration information may be related to multiple TRP transmissions and multiple TA operations. For example, the configuration information may include TAG configuration indicating multiple TAGs. The configuration information may also include TCI configuration indicating multiple TCI states. The configuration information may also include power control configuration for uplink transmissions (e.g., PUCCH, SRS, and / or PUSCH transmissions).

[0064] Once UE 510 is configured, BS 520 can send signaling information to UE 510 to trigger UE 510's multi-TRP transmission, allowing UE 510 to simultaneously execute... K In each TRP M Uplink transmission of TRPs, of which M =Equal to or greater than 2 and equal to or less than 2 K Positive integers. Signaling information may include, for example, MAC CE (e.g., for activating the TCI state of a configuration associated with one or more configuration TAGs) and / or a single DCI (e.g., for indicating one or more configuration TAGs).

[0065] Subsequently, UE 510 can determine which part to use for the first uplink transmission and to... M The first tag sent by the first TRP in the first TRP, to be used for the second uplink transmission and toM The second TAG of the second TRP in a TRP, and so on. The first TAG is the configured TAG associated with the first TA. Similarly, the second TAG is the configured TAG associated with the second TA. Then, UE 510 determines the timing adjustment required to transmit the first uplink transmission (e.g., equal to the first TA), and the timing adjustment required to transmit the second uplink transmission (e.g., equal to the second TA).

[0066] In one example, the UE supports multi-TA operation for uplink channels and / or uplink signals (such as PUCCH, PUSCH, and / or SRS) using a traditional TCI framework (e.g., a non-unified TCI framework). In this case, given the different RF attributes of FR1 and FR2, separate solutions can be considered for FR1 and FR2. Specifically, spatial relationships can be configured for FR2. TAG indexes (also referred to herein as TAG identifiers (IDs)) can be associated with spatial relationships, for example, in configuration information. For FR1, spatial relationships cannot be configured. Accordingly, TAG IDs cannot be associated with spatial relationships for FR1. Instead, other methods are also possible for FR1, as described further below. Such methods can be implemented for both FR1 and FR2, making a unified framework possible for both frequency ranges.

[0067] Figure 6 Example 600 illustrates configuring a UE to use multiple TAs according to some implementation schemes. In one example, the base station configures the UE by transmitting configuration information to the UE via RRC signaling 602. This configuration information may indicate the uplink resources (e.g., up to...) M One PUCCH resource, up to N One PUSCH resource and / or up to K One SRS resource, of which M , N , K Multiple power control configurations (shown as multiple power control configurations 610) may be equal or different; in one example, M equals 64. Each power configuration 610 may have an index and may include a TAG-specific information element (IE). The IE in the power control configuration 610 may include a TAG index 612. Therefore, each power control configuration 610 may link its TAG index to at least one uplink resource.

[0068] In one example, MAC CE 604 (or some other signaling information) can be used to activate a configured uplink resource (shown as Uplink Resource Activation 620). Specifically, MAC CE 604 can indicate the power control configuration index to be used for transmission of the uplink resource. The corresponding power control configuration includes an IE identifying the TAG. Figure 6 This correspondence is illustrated using dotted double-headed arrows. Given a TAG index, the UE uses the associated TA in the transmission of uplink resources. The use of MAC 604 and uplink resource activation 620 can be optional (and therefore in...). Figure 6 (shown as a dashed rectangle in the image), and can depend on uplink resources.

[0069] For illustration, consider three examples applicable to the traditional TCI framework: the PUCCH resource, the SRS resource, and the PUSCH resource. Two TRPs and two TAGs are also illustrated in these examples.

[0070] Starting with the PUCCH resource, power control configuration 610 corresponds to PUCCH power control set information (PUCCH-PowerControlSetInfo). An IE can be added to PUCCH-PowerControlSetInfo. This IE includes a TAG index (TAGIndex-r19) to indicate associated TAGs (e.g., whether the first TAG, the second TAG, are included in PUCCH-PowerControlSetInfo). An example is as follows: PUCCH-PowerControlSetInfo-r17 ::= SEQUENCE { pucch-PowerControlSetInfoId-r17 PUCCH-PowerControlSetInfoId-r17, p0-PUCCH-Id-r17 P0-PUCCH-Id, pucch-ClosedLoopIndex-r17 ENUMERATED { i0, i1}, pucch-PathlossReferenceRS-Id-r17 PUCCH-PathlossReferenceRS-Id-r17 TAGIndex-r19 INTEGER (0. .1) OPTIONAL, -- Need S } For each PUCCH resource, MAC-CE 604 can be used to activate a PUCCH resource with one or two PUCCH-PowerControlSetInfoIds. Therefore, MAC-CE 604 indirectly indicates one or two corresponding tags. The direct indication of a tag is having a corresponding identifier (PUCCH-PowerControlSetInfoId) in the PUCCH-PowerControlSetInfo.

[0071] In contrast, for SRS resources, power control configuration 610 corresponds to the reference signal (RS) configuration (PathlossReferenceRS-Config) for path loss reference. An IE can be added to PathlossReferenceRS-Config. This IE includes a TAG index (TAGIndex-r19) to indicate the associated TAGs (e.g., whether the first TAG, the second TAG, are included in PathlossReferenceRS-Config). An example is shown below: PathlossReferenceRS-Config ::= CHOICE { SSB-Index csi-RS-Index NZP-CSI-RS-ResourceId TAGIndex-r19 INTEGER (0..1) OPTIONAL, -- Need S } Here, one or more RRC messages can be used instead of MAC CE 604. Specifically, for each SRS resource set (SRS-ResourceSet), the RRC associates each SRS-ResourceSet with a different PathlossReferenceRS-Config. Therefore, each SRS-ResourceSet is associated with a TAG index (and thus this TAG index is included in the PathlossReferenceRS-Config). The UE can receive this RRC signaling, determine the configured SRS-ResourceSet, determine that the SRS resource belongs to this set, determine the TAG index of this set, and therefore determine the TA to be used to transmit the SRS resource. In this case, the network does not support the transmission of a single SRS resource with two different TAGs.

[0072] In the case of PUSCH resources, the power control configuration 610 corresponds to the SRS resource indicator (SRI-PUSCH-PowerControl) for PUSCH and / or the PUSCH reference signal (RS) configuration (PUSCH-PathlossReferenceRS-Config) for path loss reference. An IE can be added to SRI-PUSCH-PowerControl and / or an IE can be added to PUSCH-PathlossReferenceRS-Config. In both cases, the IE includes a TAG index (TAGIndex-r19) to indicate the associated TAGs (e.g., whether the first TAG and the second TAG are included in SRI-PUSCH-PowerControl and / or whether the first TAG and the second TAG are included in PUSCH-PathlossReferenceRS-Config).

[0073] An example of SRI-PUSCH-PowerControl is as follows: SRI-PUSCH-PowerControl ::= SEQUENCE { sri-PUSCH-PowerControlId SRI-PUSCH-PowerControlId, sri-PUSCH-PathlossReferenceRS-Id PUSCH-PathlossReferenceRS-Id, sri-P0-PUSCH-AlphaSetId P0-PUSCH-AlphaSetId, sri-PUSCH-ClosedLoopIndex ENUMERATED { i0, i1} TAGIndex-r19 INTEGER (0..1) OPTIONAL, -- Need S } The following is an example of PUSCH-PathlossReferenceRS-Config: PUSCH-PathlossReferenceRS ::= SEQUENCE { pusch-PathlossReferenceRS-Id PUSCH-PathlossReferenceRS-Id, referenceSignal CHOICE { SSB-Index csi-RS-Index NZP-CSI-RS-ResourceId } TAGIndex-r19 INTEGER (0..1) OPTIONAL, -- Need S } Similar to the example above, given SRI-PUSCH-PowerControl or PUSCH-PathlossReferenceRS-Config, network signaling can be used to (directly or indirectly) indicate the TAG index.

[0074] In one example, a tag applied to a PUSCH may follow a tag applied to the SRS associated with the PUSCH. Accordingly, PathlossReferenceRS-Config can be used to indicate the tag index of the SRS-ResourceSet. SRI-PUSCH-PowerControl and PUSCH-PathlossReferenceRS-Config do not need to indicate any tag index. Instead, the associated PUSCH transmission uses the tag corresponding to the tag indicated by the PathlossReferenceRS-Config of the SRS-ResourceSet.

[0075] Figure 7 Another example 700 illustrating the configuration of a UE to use multiple TAs according to some implementation schemes is shown. In one example, the base station configures the UE by transmitting configuration information to the UE via RRC signaling 702. This configuration information may indicate multiple uplink resource configurations and / or multiple uplink resource set configurations (shown as multiple uplink resource / resource set configurations 710). Each uplink resource / resource set configuration 710 may have an index and may include a TAG-specific IE. The IE in the uplink resource / resource set configuration 710 may include a TAG index 712. Thus, the uplink resource / resource set configuration 710 may directly link at least one uplink resource and / or uplink resource set to at least one TAG index.

[0076] In one example, once the UE is configured, it can be scheduled to transmit uplink resources (e.g., via DCI, uplink grant). Given a corresponding uplink resource / resource set configuration 710, the UE can determine the TAG index included in the IE of this uplink resource / resource set configuration 710. Given the TAG index, the UE determines the corresponding TA to use and transmits uplink resources based on this TA.

[0077] For illustration, consider two examples applicable to the traditional TCI framework: PUCCH resources and SRS resources, and PUSCH resources. In these examples, two TRPs and two TAGs are also illustrated. Regarding PUCCH resources, the base station can explicitly configure TAGs using RRC. RRC signaling can configure one TAG per PUCCH resource or PUCCH resource set (and specifically identify this TAG by its index, such that this identification corresponds to the network selection of one of the two TAGs) or two TAGs (shown in the figure as TAG 712 and TAG 714). Accordingly, when the UE needs to transmit PUCCH resources, the UE can determine the applicable PUCCH resource / resource set configuration, determine the TAG index from that configuration, and use the associated TAG for PUCCH uplink transmission.

[0078] Regarding SRS resources, base stations can use RRC to explicitly configure TAGs. RRC signaling can configure TAGs per SRS resource or SRS resource set (for SRS, only one TAG is possible; this is in...). Figure 7 (This is illustrated by adding a dashed line to TAG index 714 to indicate that TAG index 714 will not be used in the SRS case). Accordingly, when the UE needs to transmit SRS resources, the UE can determine the applicable SRS resource / resource set configuration, determine the TAG index from the configuration, and use the associated TA for SRS uplink transmission.

[0079] Figure 8 Another example 800 illustrating the configuration of a UE to use multiple TAs according to some implementation schemes is shown. In one example, the base station configures the UE by transmitting configuration information to the UE via RRC signaling 802. This configuration information may indicate multiple configurations, each configuration being specific to a list of uplink resources and / or uplink resource sets (shown as multiple configurations 810 for uplink resource lists). Each configuration 810 may have an index and may include a specific IE specific to a TAG. An IE in configuration 810 may include a TAG index 812. Thus, configuration 810 may at least directly link the TAG index to at least one list of configured uplink resources and / or configured uplink resource sets.

[0080] In one example, once the UE is configured, it can be scheduled to transmit uplink resources (e.g., via DCI, uplink grant). Given a corresponding configuration 810, the UE can determine the TAG index 812 included in the IE of this configuration 810. Given the TAG index 812, the UE determines the corresponding TA to use and transmits uplink resources based on this TA.

[0081] For illustration, consider two examples applicable to the traditional TCI framework: PUCCH resources and SRS resources. In these examples, two TRPs and two TAGs are also illustrated. Regarding PUCCH resources, the base station can use RRC to explicitly configure multiple lists of PUCCH resources. In each list, RRC signaling identifies the applicable TAG index. For example, the base station can configure three lists of PUCCH resources. All PUCCH resources indicated in the first list are configured to use the first configured TAG. All PUCCH resources indicated in the second list are configured to use the second configured TAG. All PUCCH resources indicated in the third list are configured to use both configured TAGs. Accordingly, when the UE needs to transmit PUCCH resources, the UE can determine the applicable list, determine the TAG index from that list, and use the relevant TAG for PUCCH uplink transmission.

[0082] Regarding SRS resources, base stations can use RRC to explicitly configure multiple lists of SRS resource sets and / or SRS resources. For example, RRC signaling can configure two lists. All SRS resource sets and / or SRS resources indicated in the first list are configured to use the first configured TAG. All SRS resource sets and / or SRS resources indicated in the second list are configured to use the second configured TAG. No third list is configured (this is in...). Figure 8 (This is illustrated by adding a dashed line to the third list). Accordingly, when the UE needs to transmit SRS resources, the UE can determine the applicable list, identify the TAG index from the list, and use the relevant TA to transmit SRS uplink.

[0083] Figure 9 An example of a Media Access Control (MAC) CE 900 for indicating a TA to be used with PUCCH transmission, according to some implementation schemes, is shown. Here, it can be used with... Figures 6 to 8 The method uses similar RRC signaling to configure the association between uplink resources and TAGs, but it is not mandatory. Instead, the MAC CE 900 itself can provide such associations. The MAC CE900 can support the traditional TCI framework for multi-TRP transmission using multiple TAGs. Figure 9The description mentions using two configured TAGs (although a larger number of TAGs is also possible). The MAC CE 900 can explicitly activate one or two TAGs per PUCCH resource using the "TAG" bit and the control "C" bit. The value of the "TAG" bit indicates which of the two TAGs to use (e.g., "0" indicates the first configured TAG, and "1" indicates the second configured TAG). The value of the "C" bit can be considered as overriding. Specifically, for example, if the value of the "C" bit is "1", it means that both configured TAGs are to be used. Otherwise (e.g., the value of the "C" bit is "0"), it means that the "TAG" bit is controlled.

[0084] exist Figure 9 In the example, MAC CE 900 includes a set of bits for the serving cell ID (e.g., the identifier of the serving cell), a set of bits for the BWP ID (e.g., the identifier of the bandwidth portion), a set of bits for identifying the per-PUCCH resource ID (e.g., PUCCH-ResourceId) of the PUCCH resource, a "C" bit for each PUCCH resource ID, a "TAG" bit for each PUCCH resource ID, and a reserved "R" bit. For a PUCCH resource ID (e.g., assuming ID is "1"), the corresponding "C" bit and "TAG" bit are used to explicitly activate one or both configured tags for the PUCCH resource with the PUCCH resource ID. If the "C" bit is set to "0", a configured tag is activated. This tag is indicated by the "TAG" bit (e.g., if the "TAG" bit is set to "0", the first configured tag is activated; otherwise, the second configured tag is activated). If the "C" bit is set to "1", both configured TAGs are activated, and the "TAG" bit can be omitted or ignored.

[0085] Figure 10 An example of a MAC CE1000 for indicating a TA to be used with SRS transmission is shown according to some implementation schemes. Here, it can be used with... Figures 6 to 8 The method uses similar RRC signaling to configure the association between uplink resources and TAGs, but it is not mandatory. Instead, the MAC CE 1000 itself can provide such associations. The MAC CE 1000 supports the traditional TCI framework for multi-TRP transmission using multiple TAGs. Figure 10 The description describes the use of two configured TAGs, although a larger number of TAGs is also possible. The MAC CE 1000 can explicitly activate the TAGs for each SRS resource by using the “TAG” bit associated with the SRS resource. The value of the “TAG” bit indicates which of the two TAGs to use (e.g., “0” indicates the TAG of the first configuration and “1” indicates the TAG of the second configuration).

[0086] exist Figure 10 In the example, MAC CE 1000 includes a set of bits for the serving cell ID (e.g., the identifier of the serving cell), a set of bits for the BWP ID (e.g., the identifier of the bandwidth portion), a set of bits for identifying the per SRS resource set ID of the resource set (e.g., SRS-ResourceSetId), a "TAG" bit for each SRS resource set ID, and a reserved "R" bit. For an SRS resource set ID (e.g., assuming ID is "1"), the "TAG" bit is used to explicitly activate one of two configured TAGs belonging to the SRS resource (or the entire SRS resource set). For example, if the "TAG" bit is set to "0", the first configured TAG is activated. Otherwise, the second configured TAG is activated.

[0087] In one example, the UE may support one or more types of multi-TRP operations. For example, the UE may support single-DCI multi-TRP PUSCH / PUCCH repetition, single-DCI multi-TRP simultaneous transmission across two panels (STx2P) spatial multiplexing (SDM) PUSCH, single-DCI multi-TRP STx2P single-frequency network (SFN) PUSCH, and / or single-DCI multi-TRP STx2P SFN PUCCH. Regarding single-DCI multi-TRP PUSCH / PUCCH repetition, the UE may support repetition type A (e.g., slot-based or sub-slot-based repetition) or repetition type B (e.g., back-to-back repetition). For the unified TCI framework, the UE may also support single-DCI multi-TRP UL operations with two or more TAs. The following figures illustrate the methods used for this support.

[0088] Figure 11 Example 1100 illustrates a single DCI indicating the TA to be used in a multi-TRP transmission according to some implementation schemes. In one example, the UE may be configured to use multiple TCI states, each of which may be applicable to multiple channels. Such TCI states may be referred to herein as a unified TCI state.

[0089] A unified TCI state can be a joint TCI state that can be used for both downlink and uplink channels. Alternatively, a unified TCI state can be a downlink TCI state that can be used for downlink channels and an uplink TCI state that can be used for uplink channels. Multiple such unified TCI states can be activated (e.g., via DCI or MAC CE).

[0090] In one example, the base station configures the UE by transmitting configuration information to the UE via RRC signaling 1102. This configuration information may indicate uplink transmission configuration 1110 (e.g., for PUSCH and / or PUCCH transmission). Transmission configuration 1110 may indicate a unified TCI state 1112 (multiple such states are possible), which may be a joint TCI state, a downlink TCI state, or an uplink TCI state. Transmission configuration 1110 may also indicate a TAG index 1114 (multiple such indices are possible), which corresponds to one of multiple configured TAGs (e.g., a TAG of a first configuration or a TAG of a second configuration). Furthermore, transmission configuration 1110 may associate TAG index 1114 with unified TCI state 1112. Figure 11 In the example, this relationship is shown using a dotted double-headed arrow.

[0091] Once configured, the UE can receive a single DCI 1104 for multi-TRP operation. This DCI can indicate TCI state activation 1120, thereby activating at least one of the configured unified TCI states. Figure 11 In the example, TCI state activation 1120 activates (as shown by the dotted double-headed arrow) to unify TCI state 1112. Given the corresponding TAG index association, a single DCI 1104 indirectly indicates that TAG index 1114 will be used for the uplink channel to which TCI state 1112 applies. Accordingly, the UE can determine whether to use a first configured TAG or a second configured TAG (although more than two TAGs can be configured) for uplink transmissions on these channels (e.g., for PUSCH transmission and / or PUCCH transmission).

[0092] Figure 11 Example 1100 is one approach for supporting the unified TCI framework. Other approaches for this support are also possible. For example, Figures 6 to 10 The method described in [the document] is also possible for a unified TCI framework.

[0093] Figure 12 Examples of handling conflicts arising from the use of multiple TAs are illustrated according to some implementation schemes. The UE can support multiple TRP PUSCH / PUCCH repetitions with a single DCI. Figure 12On the left, example 1200 illustrates uplink resource (e.g., PUSCH and / or PUCCH) duplication. Solid rectangles correspond to uplink retransmissions to the first TRP (1) (shown as "actual / nominal duplication (0)" and "actual / nominal duplication (2)"). Dashed, dotted rectangles correspond to uplink retransmissions to the second TRP (2) (shown as "actual / nominal duplication (1)" and "actual / nominal duplication (3)"). A collision occurs when an uplink transmission to one of the two TRPs overlaps at least partially in the time domain with an uplink transmission to the other of the two TRPs (e.g., by overlap with at least one symbol). In example 1200, two collisions are illustrated: "actual / nominal duplication (1)" collides with "actual / nominal duplication (0)", and "actual / nominal duplication (3)" collides with "actual / nominal duplication (2)". The possible cause of the conflict may be the use of different Ta (e.g., when the Ta used for TRP(2) is greater than the Ta used for TRP(1), the conflict between "actual / nominal duplicate(1)" and "actual / nominal duplicate(0)" and / or the conflict between "actual / nominal duplicate(3)" and "actual / nominal duplicate(2)" becomes possible).

[0094] exist Figure 12 On the right, examples of solutions for handling conflicts are illustrated. The first example 1210 is designed to avoid any conflicts. Specifically, for a UE supporting single-DCI multi-TRP UL operation with two or more TAs, for PUSCH / PUCCH repetitions, the base station (or more generally, the network) ensures that there are no conflicts due to different TAs between different repetitions. For example, the base station may configure sufficient gaps between adjacent repetitions. For illustration, for type A repetitions, the gap between two time slots can be at least one symbol long, where the first time slot is used for uplink transmission to the first TRP, and the second time slot is used for uplink transmission to the second TRP. For type B repetitions, the gap can be within one time slot or within two time slots. For example, at least one symbol (e.g., at the end of the first time slot or at the beginning of the next adjacent time slot) is configured as a blank symbol (e.g., a symbol that does not carry PUSCH and / or PUCCH information; the first thirteen symbols in the first time slot may carry first uplink transmission and / or the last thirteen symbols in the second adjacent time slot may carry second uplink transmission). Accordingly, when the base station configures uplink resources for the UE, and this configuration may indicate the beginning and / or end of symbols within a time slot available for uplink transmission, taking into account gaps, the base station may determine potential conflicts that could actually occur due to the configured time difference (TA) and the scheduling of uplink transmissions. Alternatively, the base station may determine that the time difference between the configured TAs is less than a threshold (e.g., the percentage of the duration of the cyclic prefix) and configure the UE accordingly to avoid potential conflicts.

[0095] In the second example 1220, collisions are permitted. For a UE supporting single-DCI multi-TRP UL operation with two or more TAs, the UE can completely discard the conflicting uplink transmissions for PUSCH / PUCCH duplication. The UE can discard either the earlier or later conflicting duplication. Figure 12 The example illustrates the discarding of later conflicts. Specifically, the UE determines that "actual / nominal duplicate (1)" conflicts with "actual / nominal duplicate (0)" and "actual / nominal duplicate (3)" conflicts with "actual / nominal duplicate (2)". Accordingly, the UE discards "actual / nominal duplicate (1)" and "actual / nominal duplicate (3)". Discarding duplicates may involve the UE abandoning the corresponding uplink transmission via its RF chain or at baseband (e.g., by not processing the duplicate). The UE may determine the actual conflicts that might occur due to the scheduling of configured TAs and uplink transmissions. Alternatively, the UE may determine that the time difference between configured TAs is less than a threshold (e.g., the percentage of the duration of the cyclic prefix) and accordingly determine to discard the later (or earlier) duplicate.

[0096] In the third example 1230, collisions are also permitted. For a UE supporting single DCI multi-TRP UL operation with two or more TAs, the UE may partially discard conflicting uplink transmissions for PUSCH / PUCCH duplications. The UE may partially discard either an earlier or later conflicting duplication. Partial discarding means discarding only the conflicting symbol (e.g., a symbol found in a later or earlier slot that conflicts with a symbol in another earlier or later slot). Figure 12 The example illustrates the discarding of later conflicts. Specifically, the UE determines that "actual / nominal duplicate (1)" conflicts with "actual / nominal duplicate (0)" and "actual / nominal duplicate (3)" conflicts with "actual / nominal duplicate (2)". Accordingly, the UE partially discards "actual / nominal duplicate (1)" by discarding only the first few initial symbols that conflict with "actual / nominal duplicate (0)". Similarly, the UE partially discards "actual / nominal duplicate (3)" by discarding only the first few initial symbols that conflict with "actual / nominal duplicate (2)". Discarding symbols may involve the UE abandoning the corresponding uplink transmission through its RF chain or at baseband (e.g., by not processing the symbol).

[0097] In Example 1240, collision mitigation is implemented. For a UE supporting single-DCI multi-TRP UL operation with two or more TAs, for PUSCH / PUCCH repetition, the UE can shift the conflicting uplink transmission in the time domain to prevent further collisions. Generally, the UE will offset the later collision by an integer number of symbols (e.g., one symbol, two symbols, etc.). The integer number of symbols can represent the minimum duration to avoid the collision (i.e., a multiple of the symbol duration). The delay can be implemented at the baseband level (e.g., by using different starting symbols for the relevant uplink transmissions). Figure 12 In the example, the UE determines that "actual / nominal repetition (1)" conflicts with "actual / nominal repetition (0)" and "actual / nominal repetition (3)" conflicts with "actual / nominal repetition (2)". Accordingly, the UE delays "actual / nominal repetition (1)" by a certain number of symbols so that it no longer conflicts with "actual / nominal repetition (0)". Similarly, the UE delays "actual / nominal repetition (3)" by a certain number of symbols so that it no longer conflicts with "actual / nominal repetition (2)".

[0098] In one example, to support single-DCI multi-TRP UL operation with two TAs, different approaches can be implemented for single-DCI multi-TRP STx2P SDM PUSCH, single-DCI multi-TRP STx2P SFN PUSCH, and / or single-DCI multi-TRP STx2P SFN PUCCH. In the example approach, two or more TAs are not permitted. For example, a UE might not be configured to use more than one TAG for a serving cell with two or more TRPs. In another example approach, two or more TAs may be permitted. Whether such use is permitted may depend on one or more factors. One example factor could be the time difference between the two TAs. For example, two TAs may only be permitted if the time difference is within a threshold. In one example, the threshold could be a predefined default value or a percentage of the cyclic prefix duration (e.g., 50% of the CP). For each subcarrier interval, the default value is predefined in the specification, or the CP duration is known from the specification. If the time difference is less than the applicable value for a given SCS, the UE may not be permitted to use two TAs; otherwise, it is permitted. Allow / disallow status can be implemented via RRC (e.g., by configuring the UE to use or not use both TAs) and / or via other network signaling (e.g., MAC CE or DCI). Another example factor is UE capability. Specifically, the UE can additionally report whether it supports two TA operations for uplink scheduling (e.g., PUSCH and / or PUCCH scheduling), such as... Figure 5As described in the documentation. For example, the UE reports whether it supports two or more TAs. The UE also reports whether it supports single-DCI multiple TRP STx2P SDM PUSCH, single-DCI multiple TRP STx2P SFN PUSCH, and / or single-DCI multiple TRP STx2P SFN PUCCH. The UE further reports its support for combinations of these two capabilities (e.g., whether the network is configurable to use two or more TAs with single-DCI multiple TRP STx2P SDM PUSCH, single-DCI multiple TRP STx2P SFN PUSCH, and / or single-DCI multiple TRP STx2P SFN PUCCH). If the UE supports combinations, the base station can (e.g., via RRC signaling) configure the UE to use two or more TAs, and the use of these TAs can be triggered via a single DCI.

[0099] Figure 13 Examples of operational flow / algorithm structures 1300 for a UE to use multiple TAs are illustrated according to some implementation schemes. The operational flow / algorithm structure 1300 may be executed or implemented by a UE (such as any UE described herein) or its components (e.g., processor 1604).

[0100] The operation flow / algorithm structure 1300 may include, at 1302, processing configuration information transmitted by the base station that indicates a first index of the first timing advance group (TAG) and a second index of the second TAG, wherein the base station is associated with a first transmit / receive point (TRP) and a second TRP. For example, the configuration information corresponds to Figures 6 to 11 Any configuration information described herein.

[0101] The operation flow / algorithm structure 1300 may include, at 1304, processing signaling information transmitted by the base station that indicates at least one of a Non-Unified Transmission Configuration Indication (TCI) associated with a multi-TRP uplink transmission or a single downlink control information (DCI) associated with the multi-TRP uplink transmission. For example, the signaling information corresponds to... Figures 6 to 11 Either the MAC CE or a single DCI described herein. In another example, the signaling information may correspond to one or more DCIs, each DCI having a format for scheduling uplink transmissions (including, for example, multiple DCIs for multi-TRP operations).

[0102] The operation flow / algorithm structure 1300 may include, at 1306, determining, based on configuration information and signaling information, that a first index will be used for a first uplink transmission to a first TRP, and a second index will be used for a second uplink transmission to a second TRP. For example, determining the association between the configured uplink resource to be transmitted and the TAG index of the configured TAG. This association can be directly indicated in the configuration information. In this case, signaling information can be used to determine that the configured uplink transmission is scheduled, but may not be used for the purpose of determining the association. Alternatively, this association can be indirectly indicated in the configuration information. In this case, signaling information can be used not only to determine that the configured uplink transmission is scheduled, but also to determine the association.

[0103] The operation flow / algorithm structure 1300 may include at 1308, causing a first uplink transmission to the first TRP to occur based on the first TAG. For example, relevant information from configuration information and signaling information is processed by the UE (e.g., at its baseband processor) to subsequently schedule and transmit the first uplink resources via the UE's first RF chain (or at least the first antenna panel).

[0104] The operation flow / algorithm structure 1300 may include at 1310, enabling a second uplink transmission to the second TRP based on the second TAG. For example, relevant information from configuration information and signaling information is processed by the UE (e.g., at its baseband processor) to subsequently schedule and transmit the second uplink resources via the UE's second RF chain (or at least the second antenna panel).

[0105] Figure 14 An example of an operational flow / algorithm structure 1400 for configuring a UE to use multiple TAs according to some implementation schemes is illustrated. The operational flow / algorithm structure 1400 may be executed or implemented by a base station (such as any base station described herein) or its components (e.g., processor 1704).

[0106] The operation flow / algorithm structure 1400 may include, at 1402, transmitting configuration information to the user equipment (UE) indicating a first index of the first timing advance group (TAG) and a second index of the second TAG. For example, the configuration information corresponds to... Figures 6 to 11 Any configuration information described herein, and transmitted using RRC signaling.

[0107] The operation flow / algorithm structure 1400 may include, at 1404, transmitting signaling information to the UE, which indicates at least one of a Non-Unified Transmit Configuration Indication (TCI) associated with a Multiple Transmit Receive Point (TRP) uplink transmission or a Single Downlink Control Information (DCI) associated with a Multiple TRP uplink transmission. For example, the signaling information corresponds to... Figures 6 to 11 Either the MAC CE or a single DCI described herein. In another example, the signaling information may correspond to one or more DCIs, each DCI having a format for scheduling uplink transmissions (including, for example, multiple DCIs for multi-TRP operations).

[0108] The operation flow / algorithm structure 1400 may include, at 1406, the first TRP of the base station receiving a first uplink transmission based on a first TAG from the UE. For example, relevant information from configuration information and signaling information is processed by the UE (e.g., at its baseband processor) to subsequently schedule and transmit the first uplink resources via the UE's first RF chain (or at least the first antenna panel).

[0109] The operation flow / algorithm structure 1400 may include, at 1408, the second TRP of the base station receiving a second uplink transmission based on a second TAG from the UE. For example, relevant information from configuration information and signaling information is processed by the UE (e.g., at its baseband processor) to subsequently schedule and transmit the second uplink resources via the UE's second RF chain (or at least the second antenna panel).

[0110] Figure 15 Example of UE 104 according to some implementation schemes (e.g., Figure 1 The receiving component 1500 (UE 104 and any other UE described herein) may include an antenna panel 1504 comprising a plurality of antenna elements. Panel 1504 is shown as having four antenna elements, but other embodiments may include a different number of antenna elements. Multiple antenna panels may also be included.

[0111] Antenna panel 1504 may be coupled to an analog beamforming (BF) assembly, which includes a plurality of phase shifters 1508(1) to 1508(4). Phase shifters 1508(1) to 1508(4) may be coupled to a radio frequency (RF) chain 1509. RF chain 1509 may amplify the received analog RF signal, down-convert the RF signal to baseband, and convert the analog baseband signal into a digital baseband signal, which may be provided to a baseband processor for further processing.

[0112] In various implementations, control circuitry residing in the baseband processor may provide BF weights (e.g., W1-W4) to phase shifters 1508(1)-1508(4) to provide a receive beam at antenna panel 1504; these BF weights may represent phase shift values. These BF weights may be determined based on channel-based beamforming.

[0113] Figure 16 An example of UE 1600 according to some implementation schemes is shown. UE 1600 may be similar to Figure 1 UE 104 and any other UE described herein, and are substantially interchangeable with them.

[0114] Similar to the description of UE 104 above, UE 1600 can be any mobile or non-mobile computing device, such as a mobile phone, computer, tablet, industrial wireless sensors (e.g., microphones, carbon dioxide sensors, pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, laser scanners, fluid level sensors, inventory sensors, voltmeters / ammeters, and actuators), video surveillance / monitoring devices (e.g., cameras and camcorders), wearable devices, or relaxed IoT devices. In some implementations, the UE can be a reduced-capacity UE or an NR lightweight UE.

[0115] UE 1600 may include a processor 1604, RF interface circuitry 1608, memory / storage device 1609, user interface 1616, sensor 1620, driver circuitry 1622, power management integrated circuit (PMIC) 1624, and battery 1628. The components of UE 1600 may be implemented as integrated circuits (ICs), portions of integrated circuits, discrete electronic devices, or other modules, such as logic components, hardware, software, firmware, or combinations thereof. Figure 16 The block diagram is intended to show a high-level view of some of the components of the UE 1600. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other specific implementations.

[0116] The components of UE 1600 can be coupled to a variety of other components via one or more interconnects 1632, which can represent any type of interface, input / output, bus (local, system or extended bus), transmit line, trace, optical connection, etc., allowing various circuit components (on common or different chips or chipsets) to interact with each other.

[0117] Processor 1604 may include processor circuitry such as baseband processor circuitry (BB) 1604A, central processing unit circuitry (CPU) 1604B, and graphics processing unit circuitry (GPU) 1604C. Processor 1604 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions (such as program code, software modules, or functional procedures from memory / storage device 1609) to cause UE 1600 to perform the operations described herein.

[0118] In some implementations, the baseband processor circuit 1604A can access the communication protocol stack 1636 in the memory / storage device 1609 to communicate over a 3GPP-compliant network. Generally, the baseband processor circuit 1604A can access the communication protocol stack to perform user plane functions at the PHY, MAC, RLC, PDCP, SDAP, and PDU layers; and control plane functions at the PHY, MAC, RLC, PDCP, RRC, and Non-Access Stratum (NAS) layers. In some implementations, PHY layer operations may additionally / optionally be performed by components of the RF interface circuit 1608.

[0119] The baseband processor circuit 1604A can generate or process baseband signals or waveforms carrying information in a 3GPP-compliant network. In some implementations, the waveforms used for NR can be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and Discrete Fourier Transform Extended OFDM (DFT-S-OFDM) in the uplink.

[0120] The baseband processor circuit 1604A can also access group information 1624 from memory / storage device 1609 to determine multiple repeated search space groups in which PDCCH can be sent.

[0121] The memory / storage device 1612 may include any type of volatile or non-volatile memory that can be distributed throughout the UE 1600. In some embodiments, some of the memory / storage devices 1612 may be located on the processor 1604 itself (e.g., L1 cache and L2 cache), while other memory / storage devices 1612 may be located outside the processor 1604 but accessible via a memory interface. The memory / storage device 1612 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0122] RF interface circuitry 1608 may include transceiver circuitry and a radio frequency front-end module (RFEM) that allows UE 1600 to communicate with other devices via a radio access network. RF interface circuitry 1608 may include various components arranged in the transmit or receive path. These components may include switches, mixers, amplifiers, filters, synthesizer circuitry, control circuitry, etc.

[0123] In the receiving path, the RFEM can receive the radiated signal from the air interface via antenna 1624 and continue to filter and amplify the signal (using a low-noise amplifier). This signal can be provided to the receiver of the transceiver, which downconverts the RF signal into a baseband signal that is provided to the baseband processor of processor 1604.

[0124] In the transmission path, the transceiver's transmitter up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM can then amplify the RF signal using a power amplifier before it is radiated across the air interface via antenna 1624.

[0125] In various implementations, the RF interface circuit 1608 can be configured to transmit / receive signals in a manner compatible with NR access technologies.

[0126] Antenna 1624 may include multiple antenna elements, each of which converts an electrical signal into radio waves for propagation through the air and converts received radio waves back into electrical signals. These antenna elements may be arranged in one or more antenna panels. Antenna 1624 may have omnidirectional, directional, or combinations thereof antenna panels to enable beamforming and multiple-input / multiple-output communication. Antenna 1624 may include a microstrip antenna, a printed antenna fabricated on the surface of one or more printed circuit boards, a patch antenna, a phased array antenna, etc. Antenna 1624 may have one or more panels designed for a specific frequency band including the frequency bands in FR1 or FR2.

[0127] User interface circuitry 1616 includes various input / output (I / O) devices designed to enable users to interact with UE 1600. User interface 1616 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual components for accepting input, particularly including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, a headset, etc. Output device circuitry includes any physical or virtual components for displaying information or otherwise conveying information, such as sensor readings, actuator positions, or other similar information. Output device circuitry may include any number or combination of audio or visual displays, particularly including one or more simple visual outputs / indicators (e.g., binary status indicators such as light-emitting diodes (LEDs)) and multi-character visual outputs or more complex outputs such as display devices or touchscreens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.), wherein the output of characters, graphics, multimedia objects, etc., is generated or produced by the operation of UE 1600.

[0128] Sensor 1620 may include a device, module, or subsystem designed to detect events or changes in its environment and transmit information about the detected events (sensor data) to another device, module, subsystem, etc. Examples of such sensors include, in particular, inertial measurement units, which include: accelerometers; gyroscopes or magnetometers; microelectromechanical systems or nanoelectromechanical systems including: triaxial accelerometers; triaxial gyroscopes; or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless aperture sensors); light detection and ranging sensors; proximity sensors (e.g., infrared radiation detectors, etc.); depth sensors; ambient light sensors; ultrasonic transceivers; microphones or other similar audio capture devices; and so on.

[0129] The driving circuitry 1622 may include software and hardware elements that operate to control a specific device embedded in, attached to, or otherwise communicatively coupled to the UE 1600. The driving circuitry 1622 may include various drivers that allow other components to interact with or control various input / output (I / O) devices that may exist within or be connected to the UE 1600. For example, the driving circuitry 1622 may include: a display driver for controlling and allowing access to a display device; a touchscreen driver for controlling and allowing access to a touchscreen interface; a sensor driver for obtaining sensor readings of sensor circuitry 1620 and controlling and allowing access to sensor circuitry 1620; a driver for obtaining actuator positions of electromechanical components or controlling and allowing access to electromechanical components; a camera driver for controlling and allowing access to an embedded image capture device; or an audio driver for controlling and allowing access to one or more audio devices.

[0130] The PMIC 1624 manages the power supplied to various components of the UE 1600. Specifically, relative to the processor 1604, the PMIC 1624 controls power source selection, voltage scaling, battery charging, or DC-DC conversion.

[0131] In some implementations, the PMIC 1624 can control or otherwise become part of various power-saving mechanisms of the UE 1600. For example, if the platform UE is in the RRC_Connected state, where it remains connected to the RAN node as it anticipates receiving traffic soon, then after a period of inactivity, the platform UE can enter a state known as Discontinuous Receive Mode (DRX). During this state, the UE 1600 can power down for short intervals to conserve power. If there is no data traffic activity during an extended period, the UE 1600 can transition to the RRC_Idle state, where the UE disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The UE 1600 enters a very low-power state and performs paging, where the UE periodically wakes up again to listen to the network, and then power down again. The UE 1600 cannot receive data in this state; to receive data, the UE must transition back to the RRC_Connected state. An additional power-saving mode renders the device unusable for a period exceeding the paging interval (from seconds to hours). During this time, the device is completely unconnected to the network and may be completely powered off. Any data transmitted during this period will incur significant latency, which is assumed to be acceptable.

[0132] Battery 1628 can power UE 1600, but in some examples, UE 1600 may be installed and deployed in a fixed location and may have a power source coupled to the power grid. Battery 1628 may be a lithium-ion battery, a metal-air battery (such as zinc-air batteries, aluminum-air batteries, lithium-air batteries, etc.). In some specific implementations, such as in vehicle-based applications, battery 1628 may be a typical lead-acid automotive battery.

[0133] Figure 17 An example of a gNB 1700 according to some implementation schemes is shown. The gNB node 1700 may be similar to and substantially interchangeable with a base station (e.g., gNB 108), and / or its components may be included in the TRP.

[0134] The gNB 1700 may include a processor 1704, an RF interface circuit 1708, a core network (CN) interface circuit 1712, and a memory / storage device circuit 1716.

[0135] Components of the gNB 1700 can be coupled to various other components via one or more interconnects 1728.

[0136] The processor 1704, RF interface circuit 1708, memory / storage device circuit 1716 (including communication protocol stack 1710), antenna 1724, and interconnect 1728 are similar to those in the reference. Figure 15 and Figure 16 Similar named elements are shown and described.

[0137] The CN interface circuit 1712 provides connectivity to a core network, such as a 5GC-compatible network interface protocol, like Carrier Ethernet or some other suitable protocol. Network connectivity can be provided to / from the gNB 1700 via fiber optic or wireless backhaul. The CN interface circuit 1712 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 1712 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0138] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0139] For one or more embodiments, at least one of the components illustrated in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods described in the Embodiments section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples below. As another example, circuitry associated with the UE, base station, network element, etc., described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the embodiments described below in the Embodiments section.

[0140] Example Further exemplary implementations are provided in the following sections.

[0141] Example 1 includes a method implemented by a user equipment (UE), the method comprising: processing configuration information transmitted by a base station and indicating a first index of a first timing advance group (TAG) and a second index of a second TAG, wherein the base station is associated with a first transmit-receive point (TRP) and a second TRP; processing signaling information transmitted by the base station and indicating at least one of a non-uniform transmit configuration indication (TCI) associated with a multi-TRP uplink transmission or a single downlink control information (DCI) associated with the multi-TRP uplink transmission; determining, based on the configuration information and the signaling information, that the first index will be used for a first uplink transmission to the first TRP and the second index will be used for a second uplink transmission to the second TRP; causing a first uplink transmission to the first TRP to occur based on the first TAG; and causing a second uplink transmission to occur to the second TRP based on the second TAG.

[0142] Example 2 includes a method implemented by a base station, the method comprising: transmitting configuration information to a user equipment (UE), the configuration information indicating a first index of a first timing advance group (TAG) and a second index of a second TAG; transmitting signaling information to the UE, the signaling information indicating at least one of a non-uniform transmission configuration indication (TCI) associated with a multiple transmit receive point (TRP) uplink transmission or a single downlink control information (DCI) associated with the multiple TRP uplink transmission; receiving a first uplink transmission based on the first TAG from the UE by a first TRP of the base station; and receiving a second uplink transmission based on the second TAG from the UE by a second TRP of the base station.

[0143] Example 3 includes the method according to any one of the preceding examples, wherein the configuration information indicates a spatial relationship configuration transmitted for the multi-TRP uplink in a frequency range between 24.25 GHz and 52.6 GHz, and wherein the first index and the second index are associated with the spatial relationship configuration.

[0144] Example 4 includes the method according to any one of the preceding examples, wherein the configuration information indicates a power control configuration transmitted for the multi-TRP uplink, and wherein the first index and the second index are associated with the power control configuration.

[0145] Example 5 includes the method according to Example 4, wherein the power control configuration includes Physical Uplink Control Channel (PUCCH) Power Control Set Information (PUCCH-PowerControlSetInfo), and wherein the information element (IE) of the PUCCH-PowerControlSetInfo includes the first index.

[0146] Example 6 includes the method according to Example 5, wherein the signaling information includes a Media Access Control (MAC) control element (CE), the MAC CE indicating a PUCCH-PowerControlSetInfo for transmitting PUCCH resources, wherein the first index is determined based on the MAC CE information according to the PUCCH-PowerControlSetInfo, and wherein the first uplink transmission includes the transmission of the PUCCH resources.

[0147] Example 7 includes the method according to Example 4, wherein the power control configuration includes pathlossReferenceRS-Config information associated with a set of sounding reference signals (SRS) resources, and wherein the information element (IE) of the pathlossReferenceRS-Config information includes the first index.

[0148] Example 8 includes the method according to Example 7, wherein the first index is determined based on the PathlossReferenceRS-Config information, and wherein the first uplink transmission includes the transmission of SRS resources.

[0149] Example 9 includes the method according to Example 7, wherein the first index is determined based on the PathlossReferenceRS-Config information, and wherein the first uplink transmission includes the transmission of Physical Uplink Shared Channel (PUSCH) resources.

[0150] Example 10 includes the method according to Example 4, wherein the power control configuration includes a sounding reference signal (SRS) resource indicator (SRI) for the physical uplink shared channel (PUSCH) and configuration information of the SRI-to-PUSCH power control configuration mapping (SRI-PUSCH-PowerControl) or a PUSCH reference signal (RS) configuration information for path loss reference (PUSCH-PathlossReferenceRS-Config), and wherein the information element (IE) of the SRI-PUSCH-PowerControl information or the PUSCH-PathlossReferenceRS-Config information includes the first index.

[0151] Example 11 includes the method according to any one of the preceding examples, wherein the configuration information is received based on Radio Resource Control (RRC) signaling, indicating the configuration of uplink resources or uplink resource sets, and associating the first index with the configuration, wherein the uplink resources are at least one of Physical Uplink Control Channel (PUCCH) resources or Sounding Reference (SRS) resources, and wherein the uplink resource set is at least one of a PUCCH resource set or an SRS resource set.

[0152] Example 12 includes the method according to any one of Examples 1 to 10 above, wherein the configuration information is received based on Radio Resource Control (RRC) signaling, indicating a first configuration of a first list of Physical Uplink Control Channel (PUCCH) resources, a second configuration of a second list of PUCCH resources, and a third configuration of a third list of PUCCH resources, and associating the first index with the first list, associating the second index with the second list, and associating the first index and the second index with the third list.

[0153] Example 13 includes the method according to any one of Examples 1 to 10 above, wherein the signaling information includes a Media Access Control (MAC) control element (CE), the MAC CE identifying a first Physical Uplink Control Channel (PUCCH) resource to be transmitted, and indicating whether the first PUCCH resource is associated only with the first index, only with the second index, or with both the first index and the second index.

[0154] Example 14 includes the method according to any one of Examples 1 to 10 above, wherein the configuration information is received based on Radio Resource Control (RRC) signaling, indicating a first configuration of a first list of Sounding Reference Signals (SRS) resources and a second configuration of a second list of SRS resources, and associating the first index only with the first list, and associating the second index only with the second list.

[0155] Example 15 includes the method according to any one of Examples 1 to 10 above, wherein the signaling information includes a Media Access Control (MAC) control element (CE), the MAC CE identifying a first Probe Reference Signal (SRS) resource set and a second SRS resource set, and indicating that the first SRS resource set is associated only with the first index and the second SRS resource set is associated only with the second index.

[0156] Example 16 includes the method according to any of the preceding examples, wherein the single DCI associates the first index with the uplink joint TCI state.

[0157] Example 17 includes the method according to any one of the preceding examples, the method further comprising: determining that the first index will be used with a third uplink transmission to the first TRP and that the second index will be used with a fourth uplink transmission to the second TRP; determining a conflict between the third uplink transmission and the fourth uplink transmission based on the first TAG and the second TAG; causing the third uplink transmission to the first TRP to occur; and causing the third uplink transmission to be discarded.

[0158] Example 18 includes the method according to any one of Examples 1 to 16 above, the method further comprising: determining that the first index will be used with a third uplink transmission to the first TRP, and that the second index will be used with a fourth uplink transmission to the second TRP; determining that a first set of symbols for the fourth uplink transmission conflicts with the third uplink transmission; causing the third uplink transmission to the first TRP to occur; and causing the remaining set of symbols for the fourth uplink transmission to be transmitted and the first set of symbols to be discarded.

[0159] Example 19 includes the method according to any one of Examples 1 to 16 above, the method further comprising: determining that the first index will be used with a third uplink transmission to the first TRP, and that the second index will be used with a fourth uplink transmission to the second TRP; determining a conflict between the third uplink transmission and the fourth uplink transmission based on the first TAG and the second TAG; determining a delay in the fourth uplink transmission such that the conflict is avoided; causing the third uplink transmission to the first TRP to occur; and causing the fourth uplink transmission to be transmitted based on the delay.

[0160] Example 20 includes the method according to any one of the preceding examples, the method further comprising: causing capability information to be sent to the base station, wherein the capability information indicates that the UE supports the single DCI for transmission on the multi-TRP uplink and supports multiple TAGs, and wherein the capability information further indicates whether the UE supports the multiple TAGs in association with the single DCI.

[0161] Example 21 includes the method according to any one of the preceding examples, the method further comprising: determining a gap between a third uplink transmission using the first TAG and a fourth uplink transmission using the second TAG, such that a conflict between the third uplink transmission and the fourth uplink transmission is avoided, wherein the signaling information schedules the third uplink transmission and the fourth uplink transmission based on the gap.

[0162] Example 22 includes the method according to any one of the preceding examples, the method further comprising: determining a time difference between a first timing advance (TA) associated with the first TAG and a second TA associated with the second TAG, wherein the time difference indicates that the multi-TRP uplink transmission is using the first TA and the second TA is permitted, and wherein the configuration information is transmitted based on the time difference.

[0163] Example 23 includes a user equipment (UE) comprising: one or more processors; and one or more memories storing instructions that, when executed by the one or more processors, configure the UE to perform the method according to any of the preceding embodiments.

[0164] Example 24 includes one or more computer-readable media storing instructions that, when executed on a user equipment (UE), cause the UE to perform operations including the methods according to any one of the preceding examples.

[0165] Example 25 includes an apparatus comprising one or more elements for performing the methods described in or related to any of the foregoing embodiments.

[0166] Example 26 includes one or more non-transitory computer-readable media, the one or more non-transitory computer-readable media including instructions to cause a device to perform one or more elements of the methods described in or related to any of the embodiments in the foregoing embodiments when the instructions are executed by one or more processors of the device.

[0167] Example 27 includes an apparatus comprising one or more elements of a logic component, module, or circuit for performing a method described in or associated with any of the preceding embodiments.

[0168] Example 28 includes an apparatus comprising: one or more processors and one or more computer-readable media, the one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the methods described in or related to any of the embodiments in the foregoing embodiments.

[0169] Example 29 includes a system comprising one or more elements for performing the methods described in or related to any of the foregoing embodiments.

[0170] Example 30 includes an apparatus comprising: processing circuitry for performing one or more elements of the methods described or associated with any of the foregoing embodiments or any other methods or processes described herein; and interface circuitry coupled to the processing circuitry, the interface circuitry communicatively coupling the processing circuitry to one or more components of a computing platform.

[0171] Unless otherwise expressly stated, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. In view of the teachings above, modifications and variations are possible, or modifications and variations may be obtained from practice of various embodiments.

[0172] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the above disclosure is fully understood. It is intended that the following claims be construed as encompassing all such variations and modifications.

Claims

1. An apparatus, the apparatus comprising: Processing circuit, the processing circuit being configured to: The system processes configuration information transmitted by a base station that indicates a first index of a first timing advance group (TAG) and a second index of a second TAG, wherein the base station is associated with a first transmit-receive point (TRP) and a second TRP. Processing signaling information transmitted by the base station, the signaling information indicating at least one of a non-uniform transmission configuration indication (TCI) associated with a multi-TRP uplink transmission or a single downlink control information (DCI) associated with the multi-TRP uplink transmission; Based on the configuration information and the signaling information, it is determined that the first index will be used for a first uplink transmission to the first TRP, and the second index will be used for a second uplink transmission to the second TRP. The first uplink transmission to the first TRP is caused based on the first TAG; as well as The second uplink transmission to the second TRP is caused based on the second TAG.

2. The apparatus of claim 1, wherein the configuration information indicates a spatial relationship configuration transmitted for the multi-TRP uplink in a frequency range between 24.25 GHz and 52.6 GHz, and wherein the first index and the second index are associated with the spatial relationship configuration.

3. The apparatus of claim 1, wherein the configuration information indicates a power control configuration for transmission of the multi-TRP uplink, and wherein the first index and the second index are associated with the power control configuration.

4. The apparatus of claim 3, wherein the power control configuration includes Physical Uplink Control Channel (PUCCH) Power Control Set Information (PUCCH-PowerControlSetInfo), and wherein the information element (IE) of the PUCCH-PowerControlSetInfo includes the first index.

5. The apparatus of claim 4, wherein the signaling information includes a Media Access Control (MAC) control element (CE), the MAC control element (CE) indicating a PUCCH-PowerControlSetInfo for transmitting PUCCH resources, wherein the first index is determined based on the MAC CE information according to the PUCCH-PowerControlSetInfo, and wherein the first uplink transmission includes the transmission of the PUCCH resources.

6. The apparatus of claim 3, wherein the power control configuration includes pathlossReferenceRS-Config information associated with a set of sounding reference signals (SRS) resources, and wherein the information element (IE) of the pathlossReferenceRS-Config information includes the first index.

7. The apparatus of claim 6, wherein the first index is determined based on the PathlossReferenceRS-Config information, and wherein the first uplink transmission includes the transmission of SRS resources.

8. The apparatus of claim 6, wherein the first index is determined based on the PathlossReferenceRS-Config information, and wherein the first uplink transmission includes the transmission of Physical Uplink Shared Channel (PUSCH) resources.

9. The apparatus of claim 3, wherein the power control configuration includes a sounding reference signal (SRS) resource indicator (SRI) for a physical uplink shared channel (PUSCH) and configuration information for mapping SRI to PUSCH power control configuration (SRI-PUSCH-PowerControl) or configuration information for a PUSCH reference signal (RS) for path loss reference (PUSCH-PathlossReferenceRS-Config), and wherein the information element (IE) of the SRI-PUSCH-PowerControl information or the PUSCH-PathlossReferenceRS-Config information includes the first index.

10. The apparatus of claim 1, wherein the configuration information is received based on Radio Resource Control (RRC) signaling, indicating the configuration of uplink resources or uplink resource sets, and associating the first index with the configuration, wherein the uplink resources are at least one of Physical Uplink Control Channel (PUCCH) resources or Sounding Reference (SRS) resources, and wherein the uplink resource set is at least one of a PUCCH resource set or an SRS resource set.

11. The apparatus of claim 1, wherein the configuration information is received based on Radio Resource Control (RRC) signaling, indicating a first configuration of a first list of Physical Uplink Control Channel (PUCCH) resources, a second configuration of a second list of PUCCH resources, and a third configuration of a third list of PUCCH resources, and associating the first index with the first list, associating the second index with the second list, and associating the first index and the second index with the third list.

12. The apparatus of claim 1, wherein the signaling information includes a Media Access Control (MAC) control element (CE), the MAC control element (CE) identifying a first Physical Uplink Control Channel (PUCCH) resource to be transmitted, and indicating whether the first PUCCH resource is associated with only the first index, only the second index, or both the first index and the second index.

13. The apparatus of claim 1, wherein the configuration information is received based on Radio Resource Control (RRC) signaling, indicating a first configuration of a first list of Sounding Reference Signals (SRS) resources and a second configuration of a second list of SRS resources, and associating the first index only with the first list, and associating the second index only with the second list.

14. The apparatus of claim 1, wherein the signaling information includes a media access control (MAC) control element (CE), the MAC control element (CE) identifying a first probe reference signal (SRS) resource set and a second SRS resource set, and indicating that the first SRS resource set is associated only with the first index and the second SRS resource set is associated only with the second index.

15. One or more computer-readable storage media storing instructions that, when executed by one or more processors, cause the one or more processors to perform operations, the operations including: The system processes configuration information transmitted by a base station that indicates a first index of a first timing advance group (TAG) and a second index of a second TAG, wherein the base station is associated with a first transmit-receive point (TRP) and a second TRP. Processing signaling information transmitted by the base station, the signaling information indicating at least one of a non-uniform transmission configuration indication (TCI) associated with a multi-TRP uplink transmission or a single downlink control information (DCI) associated with the multi-TRP uplink transmission; Based on the configuration information and the signaling information, it is determined that the first index will be used for a first uplink transmission to the first TRP, and the second index will be used for a second uplink transmission to the second TRP. The first uplink transmission to the first TRP is caused based on the first TAG; as well as The second uplink transmission to the second TRP is caused based on the second TAG.

16. The one or more computer-readable storage media of claim 15, wherein the single DCI associates the first index with the uplink joint TCI state.

17. The one or more computer-readable storage media of claim 15, wherein the operation further comprises: It is determined that the first index will be used with the third uplink transmission to the first TRP, and the second index will be used with the fourth uplink transmission to the second TRP; The conflict between the third uplink transmission and the fourth uplink transmission is determined based on the first TAG and the second TAG; This causes the third uplink transmission to occur to the first TRP; as well as This causes the third uplink transmission to be discarded.

18. The one or more computer-readable storage media of claim 15, wherein the operation further comprises: It is determined that the first index will be used with the third uplink transmission to the first TRP, and the second index will be used with the fourth uplink transmission to the second TRP; The first set of symbols transmitted by the fourth uplink is determined to conflict with the transmission of the third uplink; This causes the third uplink transmission to occur to the first TRP; as well as This causes the remaining set of symbols transmitted by the fourth uplink to be sent and the first set of symbols to be discarded.

19. The one or more computer-readable storage media of claim 15, wherein the operation further comprises: It is determined that the first index will be used with the third uplink transmission to the first TRP, and the second index will be used with the fourth uplink transmission to the second TRP; The conflict between the third uplink transmission and the fourth uplink transmission is determined based on the first TAG and the second TAG; Determine the delay of the fourth uplink transmission to avoid the collision; This causes the third uplink transmission to occur to the first TRP; as well as The fourth uplink transmission is made based on the aforementioned delay.

20. The one or more computer-readable storage media of claim 15, wherein the operation further comprises: This enables the UE to send capability information to the base station, wherein the capability information indicates that the UE supports the single DCI for transmission on the multi-TRP uplink and supports multiple TAGs, and wherein the capability information further indicates whether the UE supports the multiple TAGs in association with the single DCI.

21. A method, the method comprising: Configuration information is transmitted to the user equipment (UE), the configuration information indicating a first index of a first timing advance group (TAG) and a second index of a second TAG; The signaling information is transmitted to the UE, the signaling information indicating at least one of a non-uniform transmission configuration indication (TCI) associated with a multiple transmit receive point (TRP) uplink transmission or a single downlink control information (DCI) associated with the multiple TRP uplink transmission; Process first information corresponding to a first uplink transmission received from the UE by a first TRP, the first uplink transmission being based on the first TAG; as well as Process second information corresponding to a second uplink transmission received from the UE by a second TRP, the second uplink transmission being based on the second TAG.

22. The method according to claim 21, further comprising: A gap is determined between a third uplink transmission using the first TAG and a fourth uplink transmission using the second TAG to avoid conflicts between the third uplink transmission and the fourth uplink transmission, wherein the signaling information schedules the third uplink transmission and the fourth uplink transmission based on the gap.

23. The method according to claim 21, further comprising: Determine the time difference between a first timing advance (TA) associated with the first TAG and a second TA associated with the second TAG, wherein the time difference indicates that the multi-TRP uplink transmission is using the first TA and the second TA is allowed, and wherein the configuration information is transmitted based on the time difference.

Images