Use dual timing to determine the reference timing in advance.

By receiving the TA value and downlink timing reference of multiple TRPs, and combining the TCI status and PDCCH command, the problem of uplink transmission timing in multiple TRP communication is solved, and the communication reliability and synchronization are improved.

CN123126009APending Publication Date: 2026-11-17APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202480090609.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-04-03
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

Existing technologies have failed to effectively solve the problem of UE determining uplink transmission timing in multi-transmitter/receiver point (TRP) wireless communication networks, resulting in insufficient reliability of multi-TRP multi-DCI communication.

Method used

By receiving timing advance (TA) values ​​and downlink timing references corresponding to multiple TRPs, and combining them with TCI status and PDCCH commands, the uplink transmission timing is determined, and different timing reference points are used to handle different types of uplink transmissions.

Benefits of technology

It improves the reliability and synchronization of multi-TRP multi-DCI communication, ensuring accurate transmission of uplink signals.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123126009A_ABST
    Figure CN123126009A_ABST
Patent Text Reader

Abstract

A method is provided. The method includes: receiving multiple timing advance (TA) values ​​corresponding to multiple transmit / receive points (TRPs). The method includes: determining multiple downlink timing reference signals corresponding to the multiple TRPs from a list of transmit configuration indication (TCI) states. The method includes: determining multiple uplink transmission timings based on the multiple TAs and the multiple downlink timing reference signals. The method includes: transmitting at least one uplink signal to the multiple TRPs according to the multiple uplink transmission timings. One or more processors, user equipment (UE), and non-transitory computer-readable media are also provided.
Need to check novelty before this filing date? Find Prior Art

Description

Background Technology

[0001] Wireless communication networks provide an integrated communication platform and telecommunications services to wireless user equipment. Example telecommunications services include telephone, data (e.g., voice, audio, and / or video data), messaging, and / or other services. Wireless communication networks have wireless access nodes that exchange wireless signals with wireless user equipment using wireless network protocols, such as those described in various telecommunications standards issued by the 3rd Generation Partnership Project (3GPP). Example wireless communication networks include Time Division Multiple Access (TDMA) networks, Frequency Division Multiple Access (FDMA) networks, Orthogonal Frequency Division Multiple Access (OFDMA) networks, Long Term Evolution (LTE), and 5G New Radio (5G NR). Wireless communication networks use technologies such as OFDM, Multiple-Input Multiple-Output (MIMO), Advanced Channel Coding, Massive MIMO, beamforming, and / or other features to facilitate mobile broadband services. Summary of the Invention

[0002] According to one aspect of this disclosure, a method is provided. The method includes: receiving a plurality of timing advance (TA) values ​​corresponding to a plurality of transmit / receive points (TRPs). The method includes: determining a plurality of downlink timing references corresponding to the plurality of TRPs from a list of transmit configuration indication (TCI) states. The method includes: determining a plurality of uplink transmission timings based on the plurality of TAs and the plurality of downlink timing references. The method includes: transmitting at least one uplink signal to the plurality of TRPs according to the plurality of uplink transmission timings.

[0003] In some specific implementations, for each TRP, determining the downlink timing reference includes: receiving a beam indication signal indicating a TCI state for uplink transmission, wherein the TCI state corresponds to the downlink reference timing; and determining the downlink timing reference based on the downlink reference signal.

[0004] In some specific implementations, the downlink reference signal is received first in time among multiple downlink reference signals indicating the TCI state.

[0005] In some specific implementations, the downlink timing reference corresponds to the downlink reference signal.

[0006] In some specific implementations, the downlink timing reference corresponds to the signal that is quasi-co-located with the downlink reference signal in Type A or Type C.

[0007] In some specific implementations, this TCI state is either a combined TCI state or an uplink TCI state.

[0008] In some implementations, the beam indication signal includes a Media Access Control (MAC) control element (CE) or a Downlink Control Information (DCI) signal.

[0009] In some specific implementations, determining the downlink timing reference for each TRP includes: receiving a MAC CE that activates multiple TCI states for uplink transmission, wherein the multiple TCI states correspond to multiple downlink reference signals; and determining the downlink timing reference based on the multiple downlink reference signals.

[0010] In some specific implementations, the downlink timing reference corresponds to one of the multiple downlink reference signals.

[0011] In some specific implementations, the downlink timing reference corresponds to a quasi-co-located signal of one of the plurality of downlink reference signals in type A or type C.

[0012] In some specific implementations, these multiple TCI states include a combined TCI state or an uplink TCI state.

[0013] In some implementations, the method also includes receiving the list of TCI states via Radio Resource Control (RRC) signaling.

[0014] In some specific implementations, the multiple uplink signals include at least one of the following: Physical Uplink Shared Channel (PUSCH) signal, Physical Uplink Control Channel (PUCCH) signal, or Sound Reference Signal (SRS).

[0015] In some implementations, these multiple uplink signals include the Random Access Channel (RACH) signal during a contention-free random access process.

[0016] According to another aspect of this disclosure, a method is provided. The method includes: receiving a first TA value corresponding to a first TRP. The method includes: receiving a Physical Downlink Control Channel (PDCCH) command from the first TRP. The method includes: performing a random access procedure with a second TRP in response to the PDCCH command. The method includes: receiving a random access response from the first TRP, wherein the random access response includes a second TA value corresponding to the second TRP. The method includes: determining a first uplink transmission timing based on the first TA value and a first timing reference point corresponding to the first TRP, and determining a second uplink transmission timing based on the second TA value corresponding to the second TRP and the second timing reference point. The second timing reference point is equal to the timing indicated by the synchronization signal block (SSB) index in the PDCCH command. The method includes: transmitting a first uplink signal to the first TRP according to the first uplink transmission timing. The method includes: transmitting a second uplink signal to the second TRP according to the second uplink transmission timing.

[0017] In some implementations, the PDCCH command includes a physical cell identifier (PCI) that identifies the second TRP.

[0018] In some implementations, the PDCCH command includes a Synchronization Signal Block (SSB) index that indicates the timing of the Random Access Channel (RACH) for the random access procedure.

[0019] In some specific implementations, the first timing reference point is equal to the timing of the serving cell corresponding to the first TRP.

[0020] In some specific implementations, the method further includes: determining a first coresetPoolIndex value corresponding to the first TRP, and determining a second coresetPoolIndex value corresponding to the second TRP.

[0021] In some specific implementations, the first coresetPoolIndex value is equal to the second coresetPoolIndex value.

[0022] In some specific implementations, the first coresetPoolIndex value is different from the second coresetPoolIndex value.

[0023] The above method can be implemented as instructions stored in a non-transitory computer-readable medium containing stored instructions. The instructions can be executed by one or more processors of a communication device (such as a UE).

[0024] Details of one or more specific embodiments of these systems and methods are set forth in the accompanying drawings and the following description. Other features, objects, and advantages of these systems and methods will be apparent from the specification, the drawings, and the claims. Attached Figure Description

[0025] Figure 1 Examples of wireless networks based on some specific implementations are shown.

[0026] Figures 2A to 2D Each example illustrates a scenario for TCI status activation and indication based on a specific implementation.

[0027] Figure 3 An example is given of a process, according to some specific implementations, for a UE to obtain a TA value by performing random access with the TRP.

[0028] Figure 4A and Figure 4B Each example is illustrated with a flowchart based on a specific implementation.

[0029] Figure 5 Example UEs based on some specific implementations are shown.

[0030] Figure 6 Example access nodes are shown according to some specific implementations. Detailed Implementation

[0031] Some wireless communication networks support multiple transmit / receive point (multiple TRP) operation to increase network coverage, reliability, and data rates. In these networks, one or more base stations can act as or otherwise utilize multiple TRPs to communicate with user equipment (UE). In multiple TRP operation, one or more base stations can trigger the UE to perform two uplink transmissions to two separate TRPs based on two downlink control information (DCI) signals. This type of transmission is called a multiple DCI transmission. Each of the two DCI signals can independently configure the uplink transmission from the UE to the TRP, where each uplink transmission is associated with a timing advance (TA) value (or timing advance group (TAG)) provided by the network. Uplink transmissions can be, for example, physical random access channel (PRACH) transmissions, sounding reference signal (SRS) transmissions, physical uplink control channel (PUCCH) transmissions, or physical uplink shared channel (PUSCH) transmissions.

[0032] The network can indicate two TAs to the UE via one or more base stations under a Unified Transport Configuration Indication (TCI) framework, which provides uplink and downlink beam indication to the UE. Under the unified TCI framework (which, according to the 3GPP standard, has been extended from single-TRP scenarios to multi-TRP scenarios), the network can configure a list of up to, for example, 64 or 128 TCI states via Radio Resource Control (RRC) signaling, where each TCI state corresponds to a TA or TAG. The list of TCI states can include uplink TCI states and downlink TCI states individually, or it can include a combined TCI state for both uplink and downlink transmissions. Therefore, by indicating the uplink or combined TCI state to be used by the UE, the network can instruct the UE to use the TA corresponding to the TCI state when transmitting uplink signals to two TRPs.

[0033] In addition to the TA (Target Aspect Ratio), the UE also requires a timing reference point, which serves as the time when the UE receives the downlink reference signal for calculating the uplink transmission time. However, existing technology does not specify which signals the UE should use as reference signals. This lack of specificity in current technology allows the network to configure signals corresponding to any of the 64 or 128 configured TCI states as downlink reference signals. Because the UE has difficulty monitoring signals corresponding to all configured TCI states, it lacks the ability to determine the timing for uplink transmissions. This can compromise the reliability of multi-TRP multi-DCI communication.

[0034] Furthermore, uplink transmissions can be PRACH, SRS, PUCCH, or PUSCH. Existing technologies do not distinguish between these types of transmissions; therefore, uplink timing determination may not be applicable to certain types of uplink transmissions.

[0035] In view of the foregoing, this disclosure provides a technique that allows a UE to determine the timing reference points required for uplink transmissions of two TAs. Furthermore, this disclosure considers different types of uplink transmissions, thus allowing the UE to apply appropriate methods to determine uplink transmission timing. Utilizing one or more of the features described above, specific implementations of this disclosure can advantageously improve the reliability of multi-TRP multi-DCI communication.

[0036] Figure 1 A wireless network 100 according to some specific implementation is illustrated. The wireless network 100 includes a UE 102 and a base station 104 connected via one or more channels 106A, 106B across an air interface 108. The UE 102 and the base station 104 communicate using a system that supports control for managing the UE 102's access to the network via the base station 104.

[0037] In some implementations, Wireless Network 100 may be a non-standalone (NSA) network combining Long Term Evolution (LTE) and Fifth Generation (5G) New Radio (NR) communication standards as defined by the 3rd Generation Partnership Project (3GPP) technical specifications. For example, Wireless Network 100 may be an E-UTRA (Evolved Universal Terrestrial Radio Access)-NR Dual Connectivity (EN-DC) network or an NR-EUTRA Dual Connectivity (NE-DC) network. In some other implementations, Wireless Network 100 may be a standalone (SA) network combining only 5G NR. In addition, other types of communication standards are possible, including future 3GPP systems (e.g., sixth generation (6G)), IEEE 802.11 technologies (e.g., IEEE 802.11a; IEEE 802.11b; IEEE 802.11g; IEEE 802.11-2007; IEEE 802.11n; IEEE 802.11-2012; IEEE 802.11ac; or other currently or future IEEE 802.11 technologies), IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.). While this document may use terminology commonly associated with 5G NR to describe the aspects, the aspects of this disclosure can be applied to other systems, such as 3G, 4G, and / or systems beyond 5G (e.g., 6G).

[0038] In wireless network 100, UE 102 and any other UE in the system can be, for example, a laptop computer, smartphone, tablet computer, machine-type device (such as a smart meter or dedicated device for healthcare), intelligent transportation system, or any other wireless device. In network 100, base station 104 provides UE 102 with network connectivity to a wider network (not shown). This UE 102 connectivity is provided via air interface 108 within the base station service area provided by base station 104. In some implementations, this wider network can be a wide area network operated by a cellular network provider, or it can be the Internet. Each base station service area associated with base station 104 is supported by one or more antennas integrated with base station 104. The service area can be divided into several sectors associated with one or more specific antennas. Such sectors can be physically associated with one or more fixed antennas, or can be assigned to a physical area having one or more tunable antennas or antenna configurations that can be adjusted during beamforming to direct signals to a specific sector.

[0039] UE 102 includes control circuitry 110 coupled to transmit circuitry 112 and receive circuitry 114. Transmit circuitry 112 and receive circuitry 114 may each be coupled to one or more antennas. Control circuitry 110 may include various combinations of dedicated circuitry and baseband circuitry. Transmit circuitry 112 and receive circuitry 114 may be adapted to transmit and receive data respectively, and may include radio frequency (RF) circuitry and / or front-end module (FEM) circuitry.

[0040] In various specific implementations, aspects of the transmission circuit 112, the receiving circuit 114, and the control circuit 110 may be integrated in various ways to implement the operations described herein. The control circuit 110 may be adapted to or configured to perform various operations, such as the various UE-related operations described elsewhere in this disclosure. For example, the control circuit 110 may control the transmission circuit 112 and the receiving circuit 114 to receive downlink signals from the base station 104, determine timing for uplink transmission, and transmit uplink signals according to the timing.

[0041] The transmission circuit 112 can use multiple multiplexed uplink physical channels for transmission. These multiple uplink physical channels can be multiplexed, for example, according to time division multiplexing (TDM) or frequency division multiplexing (FDM) and carrier aggregation. The transmission circuit 112 can be configured to receive block data from the control circuit 110 for transmission across the air interface 108.

[0042] Receiver circuit 114 can receive multiple multiplexed downlink physical channels from air interface 108 and relay these physical channels to control circuit 110. These multiple downlink physical channels can be multiplexed, for example, according to TDM or FDM and carrier aggregation. Transmitter circuit 112 and receiver circuit 114 can respectively transmit and receive structured control data and content data (e.g., messages, images, video, etc.) within data blocks carried by the physical channels.

[0043] Figure 1 Base station 104 is also illustrated. In some implementations, base station 104 may be a 5G radio access network (RAN), a next-generation RAN, an E-UTRAN, a non-terrestrial cell, or a traditional RAN (such as UTRAN). As used herein, the term "5GRAN" and the like may refer to base station 104 operating in an NR or 5G wireless network 100, and the term "E-UTRAN" and the like may refer to base station 104 operating in an LTE or 4G wireless network 100. UE 102 utilizes connections (or channels) 106A and 106B, each connection including a physical communication interface or layer.

[0044] The base station 104 circuitry may include control circuitry 116 coupled to transmission circuitry 118 and receiving circuitry 120. Transmission circuitry 118 and receiving circuitry 120 may each be coupled to one or more antennas, which may be used for communication via air interface 108. Transmission circuitry 118 and receiving circuitry 120 may be adapted to transmit data to and receive data from any UE connected to base station 104. Receiving circuitry 120 may receive multiple uplink physical channels from one or more UEs, including UE 102.

[0045] exist Figure 1 In this embodiment, one or more channels 106A, 106B are exemplified as air interfaces for implementing communication coupling and may conform to cellular communication protocols such as UMTS, 3GPP LTE, LTE-A, LTE-based Unlicensed Spectrum Access (LTE-U), 5G, NR, NR-based Unlicensed Spectrum Access (NR-U), and / or any other communication protocol. In a specific implementation, UE 102 may exchange communication data directly with another UE (not shown) via the ProSe interface. The ProSe interface may alternatively be referred to as a sidelink (SL) interface and may include one or more logical channels, including but not limited to the Physical Sidelink Control Channel (PSCCH), Physical Sidelink Discovery Channel (PSDCH), and Physical Sidelink Broadcast Channel (PSBCH).

[0046] Figures 2A to 2D Each example illustrates a scenario for TCI status activation and indication based on a specific implementation. Figures 2A to 2D The scenario illustrated herein is consistent with a unified TCI framework for multi-TRP multi-DCI communication involving UEs (such as UE 102) in a network operated by base stations (such as base station 104). As described below, depending on one or more specific implementations, the UE can determine a timing reference point based on an activated or indicated TCI state and perform uplink transmissions accordingly. This improves communication reliability in multi-TRP multi-DCI communication.

[0047] exist Figure 2A and Figure 2C In the scenario illustrated, the TCI state is configured as a joint TCI state, meaning that the same TCI state can indicate both the uplink and downlink beams. In contrast, in... Figure 2B and Figure 2D In the scenario illustrated, each TCI state is configured to indicate either an uplink TCI state for an uplink beam or a downlink TCI state for a downlink beam.

[0048] exist Figure 2AIn this scenario, the network configures a list 201 of joint TCI states and notifies the UE of this list via RRC signaling. List 201 may include up to, for example, 64 or 128 TCI states. For each TCI state in list 201, the network may notify the UE of the identifier of the associated TAG, enabling the UE to determine TA information based on the TCI state.

[0049] The network can activate one or more TCI states from list 201 and use MAC CE to notify the UE of the activated TCI states. For example, the network can generate one or more code points based on the activated TCI states and identify the code points in the MAC CE. Therefore, the UE can monitor the reference signal corresponding to the activated TCI state according to the MAC CE. The number of activated TCI states depends on the UE's monitoring capabilities and is typically between one and eight.

[0050] exist Figure 2A In this scenario, network activation occurs only in one TCI state 211, and this activation is notified to the UE via the MAC CE. Therefore, the MAC CE also serves as an indication of what the UE should expect to receive in the downlink reference signal corresponding to TCI state 211. Figure 2A And similar Figures 2B to 2D In the context of TCI state, “activation” typically means that the UE is instructed to monitor the downlink reference signal corresponding to the activated TCI state, while “instruction” typically means that the UE is instructed to use the indicated TCI state when performing uplink transmission and / or downlink reception. Figure 2A In this scenario, since only one TCI state 211 is activated, the same TCI state 211 is also indicated to the UE.

[0051] exist Figure 2B In this scenario, the network configures lists 202 of uplink and downlink TCI states and notifies the UE of these lists via RRC signaling. The network activates only one uplink TCI state 212 and only one downlink TCI state 212' and notifies the UE of these activations via MAC CE. Because only one TCI state is activated for each transport link, MAC CE is therefore also used as an indication of uplink TCI state 212 and downlink TCI state 212'.

[0052] exist Figure 2CIn this scenario, the network configures a list 203 of joint TCI states and notifies the UE of this list via RRC signaling. The network also activates a subset 213 of the TCI states in list 203 (the four activated TCI states shown in the figure) and notifies the UE of this activation via MAC CE. Within the TCI states in subset 213, the network indicates a TCI state 223 to the UE via DCI. Therefore, the TCI states in subset 213 are activated according to MAC CE and indicated to the UE according to DCI.

[0053] exist Figure 2D In this scenario, the network configures lists 204 of uplink and downlink TCI states and notifies the UE of this list via RRC signaling. The network also activates a subset of TCI states by generating four TCI code points 1 to 4 and notifies the UE of this activation via MAC CE. As shown in the figure, TCI code points 1 and 4 each have one uplink TCI state and one downlink TCI state, while TCI code points 2 and 3 each have one downlink TCI state and one uplink TCI state. From the activated TCI states, the network indicates the TCI state in TCI code point 1 to the UE via DCI, namely, uplink TCI state 224 and downlink TCI state 224'.

[0054] The UE can determine the timing reference for uplink transmission based on the activated or indicated TCI state. Based on the timing indicated by the timing reference (e.g., the time to receive the corresponding downlink reference signal), the UE can calculate the time for transmitting uplink signals to the corresponding TRP, taking into account the TA value of the TRP. This calculation may involve one or more parameters, such as N. TA and N TA,偏移 As provided in the 3GPP standard, this enables uplink transmission synchronization to multiple TRPs.

[0055] In some specific implementations, the timing reference is determined based on the indicated joint or uplink TCI state, such as... Figures 2A to 2DThe TCI states are 211 (indicated by MAC CE when only one joint TCI state is active), 212 (indicated by MAC CE when only one uplink TCI state is active), 223 (indicated by DCI when multiple joint TCI states are active), or 224 (indicated by DCI when multiple uplink TCI states are active). For example, the UE may use the downlink reference signal corresponding to the indicated joint or uplink TCI state as a timing reference. Alternatively or otherwise, the UE may use any signal in Type A or Type C quasi-co-located (QCL-ed) corresponding to the indicated joint or uplink TCI state as a timing reference.

[0056] In some specific implementations, the timing reference is determined based on one or more activated TCI states, such as... Figures 2A to 2D The TCI states include: TCI state 211 (a single joint TCI state activated by MAC CE), TCI state 212 (a single uplink TCI state activated by MAC CE), any one of subset 213 (any one of the four joint TCI states activated by MAC CE), or any one of TCI code points 1, 3, and 4 (any one of the uplink TCI states activated by MAC CE and identified in TCI code points 1 to 4). For example, the UE may use the downlink reference signal corresponding to the activated joint or uplink TCI state as a timing reference. Alternatively or otherwise, the UE may use any QCL-ed downlink reference signal corresponding to the activated joint or uplink TCI state under type A or type C as a timing reference.

[0057] In some specific implementations, the UE may receive multiple downlink reference signals corresponding to the same TCI state. In this scenario, the UE can determine the timing reference point based on the downlink reference signal that is received first in time among the multiple downlink reference signals.

[0058] The TCI-based method described above (e.g., using a downlink reference signal as a reference point for determining uplink transmission timing) can be applied to uplink transmissions of PUSCH, PUCCH, or SRS signals.

[0059] For uplink RACH signal transmission, the TCI state-based method can be used to determine the timing reference point in contention-free random access. However, for uplink RACH transmission in contention-based random access, the UE can use different methods to determine the timing reference point, such as using cell-specific timing as the reference point. Furthermore, for uplink RACH transmission during initial access, such as when the UE and gNB establish synchronization, the TCI state-based method may not be applicable because the UE has not yet been configured with the parameters required by the TCI state-based method during initial access. Therefore, the UE can use different methods to determine the timing reference point, such as using cell-specific timing as the reference point.

[0060] In some specific implementations, the UE obtains the TA value and determines the uplink transmission timing to multiple TRPs based on PDCCH commands. For example, the UE can perform a random access procedure with a first TRP (TRP1) to obtain the TA value corresponding to TRP1. When the UE is configured to perform uplink transmission with a second TRP (TRP2), TRP1 can command the UE to perform another random access procedure with TRP2 to obtain the TA value corresponding to TRP2. Figure 3 The operation is illustrated in the example.

[0061] Figure 3 An example 300 illustrates a process by which a user equipment (UE) obtains a TA value by performing a random access with TRP2 to enable multi-TRP communication with both TRP1 and TRP2, according to some specific implementations.

[0062] At position 312, TRP1 sends a PDCCH command to the UE. The PDCCH command may include configurations for the UE to perform a random access procedure with TRP2. For example, the PDCCH command may include a Physical Cell Identifier (PCI) that identifies the cell corresponding to TRP2, so that the UE knows to use TRP2 to perform the random access procedure. In addition to the random access configuration and PCI, the PDCCH command may also include a Synchronization Signal Block (SSB) index that indicates the timing of the Random Access Channel (RACH) procedure.

[0063] At 314, the UE performs a random access procedure in accordance with the PDCCH command by sending a PRACH signal to TRP2.

[0064] At 316, TRP2 estimates the TA value based on the PRACH signal received from the UE.

[0065] At point 318, TRP2 sends the estimated TA value to TRP1. This TA value, which will be used for uplink transmission between the UE and TRP2, is referred to as the "new TA" in contrast to the TA value initially provided to the UE by TRP1.

[0066] At position 320, TRP1 sends a new TA to the UE in a random access response message. Therefore, the UE obtains the TA values ​​for both TRP1 and TRP2. Using the TA values ​​and timing reference points, the UE can perform uplink communication with both TRP1 and TRP2.

[0067] The UE can determine the timing reference point based on the serving cells of TRP1 and TRP2. For example, the UE can determine a first coresetPoolIndex value corresponding to the first TRP and a second coresetPoolIndex value corresponding to the second TRP from the configuration received during a random access using TRP1 and / or TRP2, where each of the two coresetPoolIndex values ​​identifies the resource set used to transmit DCI signals from the two TRPs respectively. If the two coresetPoolIndex values ​​are equal, the UE can determine that TRP1 and TRP2 belong to the same serving cell. This scenario is called inter-cell multiple TRPs. If the two coresetPoolIndex values ​​are different, the UE can determine that TRP1 and TRP2 belong to different cells. This scenario is called intra-cell multiple TRPs.

[0068] For both intra-cell and inter-cell multi-TRP multi-DCI communication, uplink transmission may require different timing reference points. In inter-cell scenarios, each of the two TRPs is associated with a coresetPoolIndex value, which can be used to distinguish the two TRPs and their corresponding timing reference points. However, current techniques for determining uplink timing do not have a mechanism to distinguish between two TRPs in intra-cell scenarios (i.e., when the TRPs are within the same serving cell).

[0069] To address this technical issue, in some implementations, the UE uses the timing corresponding to the serving cell (e.g., the cell corresponding to TRP1) as the timing reference point for TRP1. Therefore, the UE can use the serving cell timing and the initial TA value to communicate with TRP1. Additionally, the UE uses the timing indicated by the SSB index in the PDCCH command as the timing reference point for TRP2, regardless of whether TRP2 is in the same cell as TRP1. Therefore, the UE can use the SSB index timing and the new TA value to communicate with TRP2. In this way, the UE can correctly determine the timing of uplink transmissions to both TRPs, regardless of whether the transmission is inter-cell or intra-cell.

[0070] Figure 4A A flowchart illustrating an example method 400A according to some specific implementation is provided. For clarity, the following description generally describes method 400A within the context of the other figures in this specification. For example, method 400A may be derived from… Figure 1 The method is executed by UE 102. It should be understood that method 400A may be executed, for example, by any suitable system, environment, software, hardware, or a combination of system, environment, software, and hardware. In some specific implementations, the individual steps of method 400A may run in parallel, in combination, in cycles, or in any order.

[0071] At 402, method 400A includes: receiving a plurality of TA values ​​corresponding to a plurality of TRPs. The TRPs may be implemented as... Figure 1 One or more base stations similar to base station 104 or that can be managed by one or more base stations.

[0072] At 404, method 400A includes: determining multiple downlink timing references corresponding to the multiple TRPs from a list of TCI states. The list of TCI states can be compared with... Figures 2A to 2D The list shown in the example is similar.

[0073] At 406, method 400A includes: determining multiple uplink transmission timings based on the multiple TAs and the multiple downlink timing references.

[0074] At 408, method 400A includes transmitting at least one uplink signal to the plurality of TRPs according to the plurality of uplink transmission timings. The at least one uplink signal may include one or more of the following: a PUSCH signal, a PUCCH signal, an SRS or a PRACH signal.

[0075] Figure 4B A flowchart illustrating an example method 400B according to some specific implementation is provided. For clarity, the following description generally describes method 400B within the context of the other figures in this specification. For example, method 400B may be derived from… Figure 1 The method is executed by UE 102. It should be understood that method 400B may be executed, for example, by any suitable system, environment, software, hardware, or a combination of system, environment, software, and hardware. In some specific implementations, the individual steps of method 400B may run in parallel, in combination, in cycles, or in any order.

[0076] At 452, method 400B relates to: receiving a first TA value corresponding to a first TRP. The first TA value can be received from a random access procedure associated with the first TRP.

[0077] At 454, method 400B relates to: receiving a PDCCH command from a first TRP.

[0078] At 456, method 400B relates to performing a random access procedure with a second TRP in response to a PDCCH command. The random access procedure may include sending a PRACH signal to the second TRP, which enables the second TRP to estimate a second TA value.

[0079] At 458, method 400B relates to: receiving a random access response from the first TRP, wherein the random access response includes a second TA value corresponding to the second TRP.

[0080] At 460, method 400B involves determining a first uplink transmission timing and a second uplink transmission timing based on: a first TA value, a second TA value, a first timing reference point corresponding to the first TRP, and a second timing reference point corresponding to the second TRP. The second timing reference point is equal to the timing indicated by the synchronization signal block (SSB) index in the PDCCH command.

[0081] At 462, method 400B relates to transmitting a first uplink signal to a first TRP according to a first uplink transmission timing.

[0082] At 464, method 400B relates to transmitting a second uplink signal to a second TRP according to a second uplink transmission timing.

[0083] Figure 5 An example UE 500 according to some specific implementations is illustrated. UE 500 may be similar to Figure 1 The UE 102 is essentially interchangeable with it.

[0084] UE 500 can be any mobile or non-mobile computing device, such as mobile phones, computers, tablets, industrial wireless sensors (e.g., microphones, pressure sensors, thermometers, motion sensors, accelerometers, stock sensors, voltmeters / ammeters, etc.), video devices (e.g., cameras, camcorders, etc.), wearable devices (e.g., smartwatches), and loosely coupled IoT devices.

[0085] UE 500 may include a processor 502, RF interface circuitry 504, memory / storage device 506, user interface 508, sensor 510, drive circuitry 512, power management integrated circuit (PMIC) 514, one or more antennas 516, and battery 518. The components of UE 500 may be implemented as integrated circuits (ICs), portions of integrated circuits, discrete electronic devices or other modules, logic components, hardware, software, firmware, or combinations thereof. Figure 5The block diagram is intended to show a high-level view of some of the components in the UE 500. However, some of the components shown may be omitted, additional components may exist, some components may be physically merged or further split into multiple components, and different arrangements of the components shown may occur in other specific implementations.

[0086] The components of UE 500 can be coupled to various other components via one or more interconnects 520, which can represent any type of interface, input / output, bus (local, system, or extension), transmission line, trace, optical connection, etc., allowing various circuit components (on common or different chips or chipsets) to interact with each other.

[0087] Processor 502 may include processor circuitry, such as, for example, baseband processor circuitry (BB) 522A, central processing unit circuitry (CPU) 522B, and graphics processing unit circuitry (GPU) 522C. Processor 502 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 processes from memory / storage device 506) to cause UE 500 to perform the operations described herein.

[0088] In some implementations, the baseband processor circuit 522A can access the communication protocol stack 524 in the memory / storage device 506 to communicate over a 3GPP-compatible network. Generally, the baseband processor circuit 522A can access the communication protocol stack to perform user plane functions at the Physical (PHY) layer, Medium Access Control (MAC) layer, Radio Link Control (RLC) layer, Packet Data Convergence Protocol (PDCP) layer, Serving Data Adaptation Protocol (SDAP) layer, and PDU layer; and to perform control plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and non-access strata. In some implementations, PHY layer operations may additionally / optionally be performed by components of the RF interface circuit 504. The baseband processor circuit 522A can generate or process baseband signals or waveforms carrying information in a 3GPP-compatible network. In some specific implementations, the waveform used for NR can be based on Cyclic Prefix Orthogonal Frequency Division Multiplexing (OFDM) "CP-OFDM" in the uplink or downlink, and Discrete Fourier Transform Extended OFDM "DFT-S-OFDM" in the uplink.

[0089] Memory / storage device 506 may include one or more non-transitory computer-readable media, including instructions (e.g., a communication protocol stack 524) that can be executed by one or more processors in processor 502 to cause UE 500 to perform the various operations described herein. Memory / storage device 506 includes any type of volatile or non-volatile memory that can be distributed throughout UE 500. In some specific implementations, some memory / storage devices in memory / storage device 506 may be located on processor 502 itself (e.g., L1 cache and L2 cache), while other memory / storage devices 506 may be located external to processor 502 but accessible via a memory interface. Memory / storage device 506 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.

[0090] RF interface circuitry 504 may include transceiver circuitry and a radio frequency front-end module (RFEM) that allows UE 500 to communicate with other devices via a radio access network. RF interface circuitry 504 may include various components arranged in the transmission or reception path. These components may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, control circuitry, etc.

[0091] In the receiving path, the RFEM can receive the radiated signal from the air interface via antenna 516 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 down-converts the RF signal into a baseband signal, which is then provided to the baseband processor of processor 502.

[0092] 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 amplify the RF signal via a power amplifier before it is radiated across the air interface via antenna 516. In various specific implementations, the RF interface circuitry 504 can be configured to transmit / receive signals in a manner compatible with NR access technologies.

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

[0094] User interface 508 includes various input / output (I / O) devices designed to enable a user to interact with UE 500. User interface 508 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 positioning, 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 through the operation of UE 500.

[0095] Sensor 510 may include devices, modules, or subsystems intended to detect events or changes in their environment and transmit information about the detected events (sensor data) to other devices, modules, subsystems, etc. Examples of such sensors include, in particular, inertial measurement units (IMUs) including accelerometers, gyroscopes, or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) including 3-axis accelerometers, 3-axis gyroscopes, or magnetometers; level sensors; temperature sensors (e.g., thermistors); pressure sensors; image capture devices (e.g., cameras or lensless aperture devices); 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.

[0096] The driving circuit 512 may include software and hardware elements that operate to control specific devices embedded in, attached to, or otherwise communicatively coupled to the UE 500. The driving circuit 512 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 500. For example, the driving circuit 512 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 510 and controlling and allowing access to sensor 510; a driver for obtaining actuator positioning 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; and an audio driver for controlling and allowing access to one or more audio devices.

[0097] The PMIC 514 manages the power supplied to various components of the UE 500. Specifically, relative to the processor 502, the PMIC 514 controls power source selection, voltage scaling, battery charging, or DC-DC conversion.

[0098] In some implementations, the PMIC 514 may control various power-saving mechanisms of the UE 500 or otherwise become part of those mechanisms. The battery 518 may power the UE 500, but in some examples, the UE 500 may be installed in a fixed location and may have a power source coupled to the grid. The battery 518 may be a lithium-ion battery, a metal-air battery (such as zinc-air, aluminum-air, lithium-air, etc.). In some implementations, such as in vehicle-based applications, the battery 518 may be a typical lead-acid automotive battery.

[0099] Figure 6 An example access node 600 (e.g., a base station or gNB) according to some specific implementation is illustrated. Access node 600 may be similar to and substantially interchangeable with base station 104. Access node 600 may include processor 602, RF interface circuitry 604, core network (CN) interface circuitry 606, memory / storage device circuitry 608, and one or more antennas 610.

[0100] Components of access node 600 can be coupled to various other components via one or more interconnects 612. Processor 602, RF interface circuitry 604, memory / storage device circuitry 608 (including communication protocol stack 614), antenna 610, and interconnects 612 can be analogous to those of other components. Figure 5Elements with similar names as shown and described. For example, processor 602 may include processor circuitry such as, for example, baseband processor circuitry (BB) 616A, central processing unit circuitry (CPU) 616B, and graphics processing unit circuitry (GPU) 616C.

[0101] The CN interface circuit 506 can provide connectivity to a core network (e.g., a 5GC using a 5G core network (5GC) compatible network interface protocol, such as carrier Ethernet or some other suitable protocol). Network connectivity can be provided to / from access node 600 via fiber optic or wireless backhaul. The CN interface circuit 606 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 606 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0102] As used herein, the terms "access node," "access point," etc., can describe equipment that provides radio baseband functionality for data and / or voice connections between a network and one or more users. These access nodes can be referred to as BS, gNB, RAN node, eNB, NodeB, RSU, TRxP, or TRP, etc., and can include ground stations (e.g., ground access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms "NG RAN node," etc., can refer to an access node 600 (e.g., a gNB) operating in an NR or 5G system, and the terms "E-UTRAN node," etc., can refer to an access node 600 (e.g., an eNB) operating in an LTE or 4G system. Depending on various specific implementations, the access node 600 can be implemented as one or more of the following: dedicated physical equipment such as a macrocell base station, and / or a low-power (LP) base station for providing a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macrocell.

[0103] In some specific implementations, all or part of the access node 600 may be implemented as one or more software entities running on a server computer as part of a virtual network, which may be referred to as a CRAN and / or a virtual baseband unit pool (vBBUP). In a V2X scenario, the access node 600 may be a "roadside unit" or act as a "roadside unit". The term "roadside unit" or "RSU" may refer to any traffic infrastructure entity used for V2X communication. An RSU may be implemented or be implemented by a suitable RAN node or a UE that is stationed (or relatively stationed) therein, wherein an RSU implemented or be implemented by a UE may be referred to as a "UE-type RSU", an RSU implemented or be implemented by an eNB may be referred to as an "eNB-type RSU", an RSU implemented or be implemented by a gNB may be referred to as a "gNB-type RSU", and so on.

[0104] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to". Statements describing a component as configured to perform one or more tasks are explicitly intended not to invoke the interpretation of 35 USC § 112(f) for that component.

Claims

1. A method, the method comprising: Receive multiple timing advance (TA) values ​​corresponding to multiple transmit / receive points (TRPs); Determine multiple downlink timing references corresponding to the multiple TRPs from the list of Transmission Configuration Indication (TCI) states; Multiple uplink transmission timings are determined based on the multiple TAs and the multiple downlink timing references; as well as At least one uplink signal is transmitted to the plurality of TRPs according to the plurality of uplink transmission timings.

2. The method of claim 1, wherein determining the downlink timing reference for each TRP comprises: Receive a beam indication signal that indicates the TCI state for uplink transmission, wherein the TCI state corresponds to a downlink reference signal; as well as The downlink timing reference is determined based on the downlink reference signal.

3. The method of claim 2, wherein the downlink reference signal is received first in time among a plurality of downlink reference signals indicating the TCI state.

4. The method according to claim 2, wherein the downlink timing reference corresponds to the downlink reference signal.

5. The method of claim 2, wherein the downlink timing reference corresponds to a quasi-co-located signal of the downlink reference signal in type A or type C.

6. The method according to claim 2, wherein the TCI state is a combined TCI state or an uplink TCI state.

7. The method of claim 2, wherein the beam indication signal includes a Medium Access Control (MAC) element (CE) or a Downlink Control Information (DCI) signal.

8. The method of claim 1, wherein determining the downlink timing reference for each TRP comprises: Receive a Media Access Control (MAC) control element (CE) that activates multiple TCI states for uplink transmission, wherein the multiple TCI states correspond to multiple downlink reference signals; as well as The downlink timing reference is determined based on the multiple downlink reference signals.

9. The method of claim 8, wherein the downlink timing reference corresponds to one of the plurality of downlink reference signals.

10. The method of claim 8, wherein the downlink timing reference corresponds to a quasi-co-located signal of one of the plurality of downlink reference signals in type A or type C.

11. The method of claim 8, wherein the plurality of TCI states includes a joint TCI state or an uplink TCI state.

12. The method of claim 1, further comprising receiving the list of TCI states via Radio Resource Control (RRC) signaling.

13. The method of claim 1, wherein the plurality of uplink signals includes at least one of the following: a Physical Uplink Shared Channel (PUSCH) signal, a Physical Uplink Control Channel (PUCCH) signal, or a Sound Reference Signal (SRS).

14. The method of claim 1, wherein the plurality of uplink signals include a Random Access Channel (RACH) signal in a contention-free random access process.

15. A method comprising: Receive the first timing advance (TA) value corresponding to the first transmit / receive point (TRP); Receive physical downlink control channel (PDCCH) commands from the first TRP; In response to the PDCCH command, a random access procedure is performed with the second TRP; Receive a random access response from the first TRP, wherein the random access response includes a second TA value corresponding to the second TRP; A first uplink transmission timing is determined based on the first TA value and a first timing reference point corresponding to the first TRP, and a second uplink transmission timing is determined based on the second TA value and a second timing reference point corresponding to the second TRP, wherein the second timing reference point is equal to the timing indicated by the synchronization signal block (SSB) index in the PDCCH command; The first uplink signal is transmitted to the first TRP according to the first uplink transmission timing. as well as The second uplink signal is transmitted to the second TRP according to the second uplink transmission timing.

16. The method of claim 15, wherein the PDCCH command includes a physical cell identifier (PCI) that identifies the second TRP.

17. The method of claim 15, wherein the PDCCH command includes a synchronization signal block (SSB) index, the SSB index indicating the timing of the random access channel (RACH) of the random access procedure.

18. The method of claim 15, wherein the first timing reference point is equal to the timing of the serving cell corresponding to the first TRP.

19. The method of claim 15, further comprising: Determine the first coresetPoolIndex value corresponding to the first TRP, and determine the second coresetPoolIndex value corresponding to the second TRP.

20. The method of claim 19, wherein the first coresetPoolIndex value is equal to the second coresetPoolIndex value.

21. The method of claim 19, wherein the first coresetPoolIndex value is different from the second coresetPoolIndex value.

22. One or more processors, the one or more processors including circuitry configured to execute instructions to cause a communication device to perform the method according to any one of claims 1 to 21.

23. A user equipment (UE) comprising one or more processors configured to perform the method according to any one of claims 1 to 21.

24. A non-transitory computer-readable medium storing instructions that, when executed, cause one or more processors to perform the method according to any one of claims 1 to 21.