Prach timing in asymmetric dl strp / ul mtrp deployment

By introducing two timing advance groups and a PL offset mechanism in the asymmetric DL sTRP/UL mTRP deployment, the problem of timing error in uplink transmission of UL TRP alone is solved, thereby improving transmission accuracy and network detection success rate.

CN123075728APending Publication Date: 2026-11-10NOKIA TECHNOLOGIES OY
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202610610448.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2025-05-08
Filing Date
2026-05-06
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

In asymmetric DL sTRP/UL mTRP deployments, existing technologies cannot effectively solve the uplink transmission timing problem of UL TRP alone, resulting in large timing errors in PRACH preamble transmission, which may lead to interference and network detection failures.

Method used

Two timing advance groups (TAGs) and two timing advance adjustment mechanisms are introduced to allow the UE to monitor two DL reference timings and ensure UL transmission timing accuracy by configuring the TAG ID in the PL offset and TCI status IE.

Benefits of technology

It improves the accuracy of uplink transmission and network detection success rate in UL TRP scenarios only, reduces interference, and enhances system performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123075728A_ABST
    Figure CN123075728A_ABST
Patent Text Reader

Abstract

Example embodiments of this disclosure relate to PRACH timing in asymmetric DL STRP / UL MTRP deployments. An apparatus is proposed configured to: determine a random access preamble to be transmitted to an uplink-only transmission and reception point; determine timing for transmitting the random access preamble to the uplink-only transmission and reception point based at least in part on a forced timing offset; and transmit the random access preamble to the uplink-only transmission and reception point based at least in part on the determined timing. An apparatus is also configured to: transmit a forced timing offset to a user equipment associated with transmitting the random access preamble to the uplink-only transmission and reception point; and transmit an indication to the user equipment for transmitting the random access preamble to the uplink-only transmission and reception point.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The exemplary and non-limiting embodiments generally relate to uplink transmission timing, and more specifically, to uplink transmission timing for transmission to UL-only transmission and receiving points. Background Technology

[0002] In asymmetric DL sTRP / UL mTRP deployments, it is known to use a single downlink reference timing for both TRPs with DL / UL capabilities and UL-only TRPs. Summary of the Invention

[0003] The following description is intended to be illustrative only. It is not intended to limit the scope of the claims.

[0004] The independent claims provide the subject matter for several aspects. Additional aspects are defined in the dependent claims. Attached Figure Description

[0005] The foregoing aspects and other features are explained in the following description in conjunction with the accompanying drawings, wherein: Figure 1 This is a block diagram of one possible and non-limiting example system in which exemplary embodiments can be practiced; Figure 2 This is a diagram illustrating the features as described herein; Figure 3 This is a diagram illustrating the features as described herein; Figure 4 This is a diagram illustrating the features as described herein; Figure 5 This is a diagram illustrating the features as described herein; Figure 6 This is a diagram illustrating the steps described herein; Figure 7 This is a flowchart illustrating the steps described herein; Figure 8 This is a flowchart illustrating the steps described herein; Figure 9 This is a flowchart illustrating the steps described herein; and Figure 10 This is a flowchart illustrating the steps described herein. Detailed Implementation

[0006] The following abbreviations, which can be found in the instruction manual and / or accompanying drawings, are defined as follows: 3GPP Third Generation Partnership Project 5G fifth generation 5GC 5G Core Network AI (Artificial Intelligence) AMF access and mobility management functions BWP bandwidth portion CBRA (Contest-Based Random Access) CC component carrier CFRA Contention-Free Random Access CLPC closed-loop power control CP loop prefix cRAN Cloud Radio Access Network CSI Channel Status Information CU Central Unit DCI downlink control information DL downlink DU Distributed Unit eNB (or eNodeB) evolved Node B (e.g., LTE base station) EN-DCE-UTRA-NR Dual Connection The en-gNB or En-gNB node provides the UE with NR user plane and control plane protocol termination and acts as a secondary node in the EN-DC. E-UTRA evolved universal terrestrial radio access, i.e., LTE radio access technology FR frequency range gNB (or gNodeB) refers to a 5G / NR base station, specifically a node that provides NR user plane and control plane protocol termination to the UE and connects to the 5GC via the NG interface. GP protection period IE Information Elements I / F interface L1 Floor 1 LTE Long Term Evolution MAC Media Access Control MIMO (Multiple Input Multiple Output) ML machine learning MME Mobility Management Entity mTRP Multiple Transmitter and Receiver Points ng or NG next generation ng-eNB or NG-eNB next-generation eNB NN Neural Network NR New Radio N / W or NW network O-RAN Open Radio Access Network PBCH Physical Broadcast Channel PCID (Physical Cell Identifier) PDCCH Physical Downlink Control Channel PDCP Packet Data Convergence Protocol PDSCH Physical Downlink Shared Channel PHY physical layer PL path loss PLRS path loss reference signal PUCCH (Physical Uplink Control Channel) PUSCH Physical Uplink Shared Channel PRACH Physical Random Access Channel QCL Quasi-co-addressable RA Random Access RACH Random Access Channel RAN Radio Access Network RAR Random Access Response RF radio frequency RLC Radio Link Control RRC Radio Resource Control RRH Remote Radio Header RS reference signal RSRP reference signal received power RSSI Received Signal Strength Indicator RU radio unit Rx receiver SDAP Service Data Adaptation Protocol SCS subcarrier spacing SGW Service Gateway SMF Session Management Function SRS detection reference signal SSB Synchronization Signal / PBCH Block sTRP Single Transmitter Receiver STxMP Simultaneous Multi-Panel Transmission TA scheduled in advance TAC timed advance command TAE time alignment error TAG Timed Advance Group TCI Transport Configuration Indicator TRP Transmitter / Receiver Point Tx transmitter UE (User Equipment) (e.g., wireless, typically mobile device) UL uplink UPF User Plane Functions VNR Virtualization Network Function Go to Figure 1 The figure illustrates a block diagram of one possible and non-limiting example in which practical examples can be implemented. It shows a user equipment (UE) 110, a radio access network (RAN) node 170, and network elements 190. Figure 1In the example, User Equipment (UE) 110 wirelessly communicates with Wireless Network 100. The UE is a wireless device that can access Wireless Network 100. UE 110 includes one or more processors 120, one or more memories 125, and one or more transceivers 130 interconnected via one or more buses 127. Each of the one or more transceivers 130 includes a receiver Rx 132 and a transmitter Tx 133. The one or more buses 127 may be address, data, or control buses and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optic cables, or other optical communication devices. "Circuit" may include dedicated hardware or hardware associated with software that can be executed thereon. The one or more transceivers 130 are connected to one or more antennas 128. The one or more memories 125 include computer-readable code 123. UE 110 includes a module 140, which includes one or both of portions 140-1 and / or portions 140-2, which may be implemented in various ways. Module 140 may be implemented in hardware as module 140-1, such as being implemented as part of one or more processors 120. Module 140-1 may also be implemented as an integrated circuit or by other hardware such as a programmable gate array. In another example, module 140 may be implemented as module 140-2, which is implemented as computer-readable code 123 and executed by one or more processors 120. For example, one or more memories 125 and computer-readable code 123 may be configured to perform one or more operations as described herein with the user device 110 using one or more processors 120. UE 110 communicates with one or more RAN nodes 170 via wireless link 111.

[0007] In this example, RAN node 170 is a base station that provides access to wireless network 100 for wireless devices such as UE 110. RAN node 170 can be, for example, a base station for 5G (also known as New Radio (NR)). In 5G, RAN node 170 can be an NG-RAN node, which is defined as a gNB or ng-eNB. A gNB is a node that provides NR user plane and control plane protocol termination to the UE and is connected to the 5GC (e.g., multiple network elements 190) via an NG interface. An ng-eNB is a node that provides E-UTRA user plane and control plane protocol termination to the UE and is connected to the 5GC via an NG interface. An NG-RAN node can include multiple gNBs, which can also include a central unit (CU) (gNB-CU) 196 and multiple distributed units (DUs) (gNB-DU), where DU 195 is shown. Note that a DU can include or be coupled to and control a radio unit (RU). A gNB-CU is a logical node that hosts the RRC, SDAP, and PDCP protocols of a gNB or controls the RRC and PDCP protocols of an en-gNB for the operation of one or more gNB-DUs. The gNB-CU terminates at an F1 interface connected to the gNB-DU. The F1 interface is shown as reference numeral 198, although reference numeral 198 also shows links between remote elements of RAN node 170 and centralized elements of RAN node 170 (such as between gNB-CU 196 and gNB-DU 195). A gNB-DU is a logical node that hosts the RLC, MAC, and PHY layers of a gNB or en-gNB, and its operation is partially controlled by the gNB-CU. One gNB-CU supports one or more cells. A cell is supported by only one gNB-DU. The gNB-DU terminates at F1 interface 198 connected to the gNB-CU. Note that DU 195 is considered to include transceiver 160, for example, as part of an RU; however, some examples may have transceiver 160 as part of a separate RU, for example, under the control of and connected to DU 195. RAN node 170 may also be an eNB (evolved NodeB) base station for LTE (Long Term Evolution), or any other suitable base station, access point, access node, or node.

[0008] RAN node 170 includes one or more processors 152, one or more memories 155, one or more network interfaces (N / WI / F) 161, and one or more transceivers 160 interconnected via one or more buses 157. Each of the one or more transceivers 160 includes a receiver Rx 162 and a transmitter Tx 163. The one or more transceivers 160 are connected to one or more antennas 158. The one or more memories 155 include computer-readable code 153. CU 196 may include processor(s) 152, memories 155, and network interfaces 161. Note that DU 195 may also include its own memories and processor(s) and / or other hardware, but these are not shown.

[0009] RAN node 170 includes module 150, which includes one or both of portions 150-1 and / or portions 150-2, and can be implemented in various ways. Module 150 can be implemented in hardware as module 150-1, such as being implemented as part of one or more processors 152. Module 150-1 can also be implemented as an integrated circuit or by other hardware such as a programmable gate array. In another example, module 150 can be implemented as module 150-2, which is implemented as computer-readable code 153 and executed by one or more processors 152. For example, one or more memories 155 and computer-readable code 153 are configured, together with one or more processors 152, to enable RAN node 170 to perform one or more operations as described herein. Note that the functionality of module 150 can be distributed, such as distributed between DU 195 and CU 196, or implemented only in DU 195.

[0010] One or more network interfaces 161 communicate via a network, such as via links 176 and 131. Two or more gNBs 170 can communicate using, for example, link 176. Link 176 can be wired, wireless, or both, and can implement, for example, an Xn interface for 5G, an X2 interface for LTE, or other suitable interfaces for other standards.

[0011] One or more buses 157 may be address, data, or control buses and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, optical fiber or other optical communication equipment, wireless channels, etc. For example, one or more transceivers 160 may be implemented as a Remote Radio Header (RRH) 195 for LTE or a Distributed Unit (DU) 195 for a gNB implementation of 5G, wherein other elements of the RAN node 170 may be physically located in a different location from the RRH / DU, and one or more buses 157 may be partially implemented as, for example, fiber optic cables or other suitable network connections to connect other elements of the RAN node 170 (e.g., Central Unit (CU), gNB-CU) to the RRH / DU 195. Reference numeral 198 also indicates those suitable network links(s).

[0012] Note that the description in this document indicates that a "cell" performs a function; however, it should be clear that the equipment forming the cell will perform the function. A cell constitutes part of a base station. That is, each base station can have multiple cells. For example, for a single carrier frequency and associated bandwidth, there can be three cells, each covering one-third of a 360-degree area, such that the coverage area of ​​a single base station is approximately elliptical or circular. Furthermore, each cell can correspond to a single carrier, and a base station can use multiple carriers. Therefore, if there are three 120-degree cells per carrier and two carriers exist, the base station has a total of six cells.

[0013] Wireless network 100 may include one or more network elements 190, which may include core network functions and provide connectivity to another network (such as a telephone network and / or a data communication network (e.g., the Internet)) via one or more links 181. Such core network functions for 5G may include Access and Mobility Management Functions (AMF) and / or User Plane Functions (UPF) and / or Session Management Functions (SMF). Such core network functions for LTE may include MME (Mobility Management Entity) / SGW (Serving Gateway) functions. These are merely illustrative functions that may be supported by network element(s) 190, and note that both 5G and LTE functions may be supported. RAN node 170 is coupled to network element 190 via link 131. Link 131 may be implemented as, for example, an NG interface for 5G, or an S1 interface for LTE, or other suitable interfaces for other standards. Network element 190 includes one or more processors 175, one or more memories 171, and one or more network interfaces (N / WI / F) 180 interconnected via one or more buses 185. One or more memories 171 include computer-readable code 173. The one or more memories 171 and computer-readable code 173 are configured to, together with one or more processors 175, cause the network element 190 to perform one or more operations.

[0014] Wireless network 100 can implement network virtualization, which is the process of combining hardware and software network resources and network functions into a single software-based managed entity (virtual network). Network virtualization involves platform virtualization, often combined with resource virtualization. Network virtualization is categorized as external, combining many networks or parts of networks into virtual units, or internal, providing network-like functionality to software containers on a single system. For example, a network can be deployed in a remote cloud, where Virtualized Network Functions (VNFs) run on, for example, data center servers. For instance, network core functions and / or (multiple) radio access networks (e.g., CloudRAN, O-RAN, edge cloud) can be virtualized. Note that the virtualized entity resulting from network virtualization is still implemented to some extent using hardware such as processors 152 or 175 and memories 155 and 171, and such virtualized entities also produce technical effects.

[0015] It should also be noted that the operation of the example embodiments of this disclosure may be performed by multiple cooperating devices (e.g., cRAN).

[0016] Computer-readable storage devices 125, 155, and 171 can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic storage devices and systems, optical storage devices and systems, fixed memory, and removable memory. Computer-readable storage devices 125, 155, and 171 can be components for performing storage functions. As a non-limiting example, processors 120, 152, and 175 can be of any type suitable for the local technical environment and can include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Processors 120, 152, and 175 can be components for performing functions such as controlling UE 110, RAN node 170, and other functions as described herein.

[0017] Typically, various example embodiments of user equipment 110 may include, but are not limited to, cellular phones (such as smartphones), tablet computers, personal digital assistants (PDAs) with wireless communication capabilities, portable computers with wireless communication capabilities, image capture devices (such as digital cameras with wireless communication capabilities), gaming devices with wireless communication capabilities, music storage and playback devices with wireless communication capabilities, internet devices that allow wireless internet access and browsing, tablet computers with wireless communication capabilities, and portable units or terminals that include a combination of these functions.

[0018] Therefore, a suitable but non-limiting technical context has been introduced for practicing exemplary embodiments of this disclosure, and the exemplary embodiments will now be described in more detail.

[0019] The features described herein can typically relate to 3GPP New Radio (NR) physical layer development. For example, the features described herein can typically relate to UE configurations for use with multiple transmit and / or receive points (multiple TRPs or mTRPs) at least in the uplink (UL) direction.

[0020] Multiple TRP schemes have been studied and specified in the last few versions of 3GPP. For example, Rel-16 focused on the Physical Downlink Shared Channel (PDSCH), and then Rel-17 introduced multiple TRP schemes that also apply to the Physical Downlink Control Channel (PDCCH), Physical Uplink Shared Channel (PUSCH), and Physical Uplink Control Channel (PUCCH), with two different main frameworks: Single Downlink Control Information (DCI) and Multiple DCI.

[0021] Now for reference Figure 2An example of a single DCI multi-TRP scenario is shown, which can be used to support scenarios with ideal backhaul available between TRPs, such as where joint scheduling decisions can be made. The PDSCH (250) is scheduled from two TRPs (210, 230) via a single DCI on the PDCCH (240), and the PDCCH (240) is transmitted to the UE (220) by only one of the two TRPs (210, 230). Uplink transmissions (260) (e.g., PUxCH, PUSCH, or PUCCH) can be scheduled for the two TRP links.

[0022] Now for reference Figure 3 An example of a multi-DCI, multi-TRP scenario is shown, which can be used to support scenarios with non-ideal backhaul between TRPs, where each TRP uses its own DCI to independently schedule downlink data transmission. The PDSCH (350) utilizes its own DCI on the PDCCH (340) transmitted from each TRP (310, 330) to the UE (320) for scheduling. Uplink transmissions (360) can be scheduled for two TRP links.

[0023] In this disclosure, the term UE can refer to any type of UE, including but not limited to UEs with NR enhanced mobile broadband capabilities, IoT devices, environmental IoT devices, degraded devices, smartphone devices, etc.

[0024] The features described herein typically relate to a Unified Transport Configuration Indicator (TCI) framework. Rel-17 introduced a “unified” TCI framework, meaning that TCI states providing quasi-co-location (QCL) assumptions for downlink (DL) signal and channel reception can also be used to provide spatial sources / resources for UL signal and channel transmission to determine UL transmitter (TX) spatial filters. In other words, the gNB can configure the UE with TCI states via RRC signaling, where each TCI state can have one or two source reference signals (RS) providing QCL parameters for the target RS. QCL information can also be used for beam indication provided by the gNB to configure the UE with the transmit / receive beams to be used for downlink and uplink. A DL TCI chain includes a Synchronization Signal Block (SSB) and one or more Channel State Information Reference Signals (CSI-RS) resources, and the TCI state of each reference signal includes another reference signal in the same TCI chain, where the SSB can be associated with the serving cell's Physical Cell Identifier (PCID) or with a PCID different from the serving cell's PCID.

[0025] There exists a pool of TCI states configured via Radio Resource Control (RRC) signaling, and a subset of these configured TCI states are activated via a Medium Access Control Element (MAC-CE) with up to eight TCI code points, each code point pointing to an individual or combined DL / UL TCI state.

[0026] The unified TCI framework also defines the concept of indicated TCI states, which can be a combined DL / UL TCI state or a separate DL and a separate UL TCI state. This means that one or more of the configured TCI states (e.g., in the case of multiple TRPs) constitute one indicated TCI state(s).

[0027] Rel-17 introduces a unified TCI framework for UEs for a single TRP (sTRP) scenario, where there is a single indication of a joint DL / UL TCI state, or a single indication of a DL and a single indication of a UL TCI state.

[0028] Then, Rel-18 extends the unified TCI framework for mTRP to the UE, where there is a joint TCI state with two indications at one time, or a separate DL with two indications and a separate UL TCI state with two indications at one time.

[0029] The features described in this article can typically involve timing advance (TA), such as the two TA enhancements in Rel-18. Rel-18 includes several enhancements, such as simultaneous multi-panel transmission (STxMP), two TAs, and power control, as highlighted in the Rel-18 MIMO EvoWID RP-213598 objective: "...studies, and if necessary, specify the following items to facilitate simultaneous multi-panel UL transmission for higher UL throughput / reliability, focusing on FR2 and multiple TRPs, assuming up to 2 TRPs and up to 2 panels, for CPE / FWA / vehicle / industrial equipment (if applicable)." The UL precoding instructions for PUSCH do not introduce a new codebook for simultaneous transmission of multiple panels. Considering multi-TRP operations based on single DCI and multiple DCI, the total number of layers on all panels can be up to four, and the total number of codewords on all panels can be up to two.

[0030] For UL beam indication of PUCCH / PUSCH, assuming the extension of the unified TCI framework in Objective 2, multi-TRP operation based on single DCI and multiple DCI is considered. For multi-TRP operations based on multiple DCI, only PUSCH+PUSCH or PUCCH+PUCCH are transmitted across two panels in the same CC.

[0031] The study shall, if proven, stipulate the following: For two TAs of UL multi-DCI used for multi-TRP operation Power control for UL single DCI used in multi-TRP operation, where it is assumed that the unified TCI framework in Objective 2 is extended.

[0032] For simultaneous UL transmissions from multiple panels, operation will be limited to scenario 6… TA stands for Offset, which the UE can use to advance its UL transmission relative to the time it receives (multiple) DL transmissions from the base station. In other words, it is the offset between the start of the received downlink subframe and the transmitted uplink subframe for the UE. The UE can obtain UL timing advance during the random access procedure (e.g., when it does not yet have a TA). As an example, in a contention-based random access (CBRA) or contention-free random access (CFRA) procedure, the UE can transmit a random access preamble (which may be pre-assigned in the case of CFRA), and in the random access response (RAR), the network can provide the UE with an absolute timing advance command (TAC). To maintain the adjusted timing advance, the network can periodically update the timing advance for the UE by sending additional TACs, which may in turn lead to the restart / starting of the time alignment timer.

[0033] Rel-18 introduces two TAs for multi-DCI two-TRP scenarios, allowing UL transmission from the UE to both TRPs. The link between these two TRPs can be characterized by a large difference in propagation delay relative to the cyclic prefix (CP) length. This scenario is considered highly relevant, especially in FR2. Furthermore, considering the potential for non-ideal synchronization between the two TRPs, Rel-18 focuses on multi-DCI. Several enablers are introduced in Rel-18, including configuring two timing advance groups (TAGs) and requiring the UE to monitor two DL reference timings.

[0034] Two TAGs or two timing advance (TA) loops can be configured for the serving cell, with each TAG or TA loop essentially corresponding to one TRP. This allows the UE to use two TA features: for both intra-cell multiple TRPs and inter-cell multiple TRPs, receiving a timing advance command (TAC) TA1 for TRP1 and a TAC TA2 for TRP2.

[0035] The UE may need to monitor two DL reference timings, each corresponding to a TAG / TA loop / TRP. Based on traditional single TA requirements, it depends on the UE to determine which reference signals (RS) (e.g., Synchronization Signal Block (SSB) or even Channel State Information Reference Signal (CSI-RS)) to use as the DL reference timing for each TAG.

[0036] To allow the UE to know which beam / TCI state is associated with which TAG, the TAG ID has been introduced as a field in the TCI state IE.

[0037] Regarding the Physical Random Access Channel (PRACH), cross-TRP PDCCH command PRACH has been introduced, whereby one TRP can trigger (e.g., via PDCCH) PRACH to another TRP (or even itself): however, only contention-free random access (CFRA) is supported in the two TA enhancements of Rel-18 (and not contention-based random access (CBRA)).

[0038] With the Rel-18 enhancement, the PRACH transmission timing offset can be controlled by the network with higher-level parameters n-TimingAdvanceOffset (and n-TimingAdvanceOffset2). More specifically, the network can configure two different PRACH transmission timings for the UE for two tags: - If n-TimingAdvanceOffset2 is not configured, the UE assumes that the PRACH transmission timing for TAG2 is the same as that for TAG1. - If n-TimingAdvanceOffset is not configured, the UE assumes a predefined value for the PRACH transmission timing for TAG1, such as Table 7.1.2-2 from 38.133.

[0039] This network control of PRACH transmission timing is rather coarse or crude because n-TimingAdvanceOffset can only take a limited number of values: .

[0040] Statement 7.1 of Clause 38.133 of TS: "...For a multi-DCI-based multi-TRP operation with two TAs, for each TAG, the uplink transmission timing occurs before the downlink reference point is received (N..." TA +N TAoffset )x Tx.

[0041] For multi-DCI-based multi-TRP operations with two TAs, the reference point for PUCCH / PUSCH / SRS is the same as that with the same TAG as the uplink signal. DLorJointTCIState The first detection path (in time) of one of the corresponding downlink reference signals of one of the reference cells associated with one of TS 38.331[2].

[0042] For a multi-TRP operation based on multiple DCIs within a cell with two TAs, the reference point for PRACH transmission triggered by a PDCCH command is the first detection path (in time) of one of the following downlink reference signals: when the PRACH association indicator is 0, the downlink reference signal(s) is in a DL or joint TCI state with the same coresetPoolIndex as the PDCCH carrying the PDCCH command; when the PRACH association indicator is 1, the downlink reference signal(s) is in a DL or joint TCI state corresponding to another coresetPoolIndex.

[0043] For multi-TRP operations based on inter-cell multiple DCI with two TAs, the reference point for PRACH transmission is triggered by the PDCCH command. - If the "PRACH association indicator" is 0, then the reference timing is the first detection path (in time) of one of the corresponding downlink reference signals of the (multiple) DL TCI states of the reference cell associated with the first TAG.

[0044] - If the "PRACH association indicator" is 1, then the reference timing is the first detection path (in time) of one of the corresponding downlink reference signals of the (multiple) DL TCI states of the reference cell associated with the second TAG.

[0045] Where N TA and N TAoffset The network commands TS 38.311[2] independently for each TAG. If configured, then... N for the first and second tags TAoffset For example, n-TimingAdvanceOffset and n-TimingAdvanceOffset2 If defined in the table, then it is N as defined in Table 7.1.2-2. TAoffset 。

[0046] As required in Clause 7.1.2, if the UE supports ncd-SSB-BWP-Wor-r18, then the SSB applies to both CD-SSB and NCD-SSB… N TAoffset The values ​​are shown in Table 1:

[0047] Clause 7.1 of TS 38.133 also defines the ServingCellConfigCommon information element, which includes n-TimingAdvanceOffset.

[0048] The features described in this article typically relate to Rel-19 asymmetric DL sTRP / UL mTRP. Rel-19 is currently working to extend multiple TRPs to cover UL-only TRPs, i.e., TRPs that do not transmit data or control information to the UE, which may potentially be deployed near the cell edge, with the primary aim of improving UL coverage.

[0049] When a UL-only TRP is introduced within the coverage area of ​​a cell, the required UL transmit power level may be lower than that of a conventional UL TRP, so the introduction may not cause additional UL interference. UL-only TRPs can be deployed to improve average and cell edge spectrum efficiency. UL-only TRPs may be more cost-effective than small cells (which can provide both UL and DL capabilities), as small cells typically have both UL and DL capabilities and are therefore more expensive than UL-only TRPs, and may also introduce additional interference in the DL.

[0050] It can be noted that a UL TRP may be able to receive data from the UE via the uplink channel, but may not be able to receive data from the network via the downlink channel. Since a UL TRP does not have the capability to transmit to the UE in the DL (i.e., without a DLTX RF chain), the (multiple) UEs do not have the means to estimate the channel and calculate the path loss between the UL TRP and the UE. A UL TRP may include hardware that can be used to perform DL transmissions, but this hardware may be deactivated; alternatively, a UL TRP may not include hardware that can be used to perform some DL transmissions, such as an SSB. Alternatively, a UL TRP may be able to transmit some RS. A UL TRP may be able to perform transmission and / or reception, and may be alternatively referred to as a transmission point, or a reception point, or a transmission-reception point. Additionally or alternatively, a UL TRP may not transmit UE-specific signals, such as data or control signals, to the UE, but may transmit reference signals common to all UEs, such as an SSB.

[0051] In this disclosure, the UL TRP may alternatively be referred to as a UL-only receiving point, receiving point, UL-only node, UL-only transmitter, UL-only transmission point, node configured to perform uplink transmission only, node not configured to perform downlink transmission, node limited to performing uplink transmission, and / or node with limited transmission capabilities.

[0052] Although no data or control is transmitted to the UE, a UL TRP-only may transmit some RSs, such as SSBs. More specifically, it has been proposed that if the UE is configured with a path loss (PL) offset for transmissions toward the UL TRP-only, then such a UL TRP-only will not transmit any RSs. However, if this PL offset is not configured, the UE may expect some SSBs to also originate from the UL TRP-only.

[0053] The updated version of Rel-19 MIMO Ph5 WID RP-242394 describes the following objectives: "...This specification addresses enhancements for asymmetric DL sTRP / UL mTRP deployment scenarios, assuming in-band DU non-co-located mTRP scenarios, without altering existing cell definitions or defining new cells (e.g., UL cells only), assuming the Rel-17 / 18 unified TCI framework and full reuse of traditional QCL / UL spatial relationship rules, targeting FR1 and FR2." Two closed-loop PC adjustment states for SRS are independent of PUSCH; and when the path loss RS comes from DL sTRP, a path loss offset configuration is used to calculate the path loss to (multiple) UL TRP.

[0054] Assuming traditional PRACH resources, two TAs reuse the Rel-18 specifications of the two TAs for multiple DCI-based multi-TRPs and remove the restriction of needing to configure coresetPoolIndex… In this “asymmetric DL sTRP / UL mTRP”, for example, Figure 4 As shown, the DL transmission (440) originates from only one TRP, described as a "TRP with DL / UL capability" (410), which is the sole TRP sending data (450) and control information (440) to the UE (420), and therefore also schedules UE DL and UL transmissions. The UE (420) is configured to perform UL transmissions (e.g., PUCCH or PUSCH) to one or both of TRP1 (410) and ULTRP2 (430) (460). The TRP with UL / DL capability (410) may also be referred to as the anchor TRP.

[0055] Since only TRP1 (i.e., TRP (410) with DL / UL capability) is allowed to send PDCCH (440) to UE (420), the asymmetric DL sTRP / UL mTRP scenario can be identified as a specific case of a single DCI multi-TRP scenario, where the same DCI can be used to schedule UL transmissions to multiple TRPs.

[0056] Much of RAN1’s work to date has been defining two closed-loop power control (CLPC) adjustments for the sounding reference signal (SRS), introducing a new parameter called “PL offset”, which allows the UE to set its transmission power when transmitting to “UL TRP only”.

[0057] To date, RAN1 has also decided to require the UE to: - When the UE is configured with a PL offset, monitoring will be performed on one DL reference timing for both TAGs (implicitly meaning from the TRP with DL / UL capability to the UE, since that TRP is ultimately the only TRP transmitting any DL data or control signaling to the UE); or when the UE is not configured with a PL offset, monitoring will be performed on two DL reference timings, implicitly meaning one DL reference timing for each TAG (since only the UL TRP transmits RS in this case); and - Apply TAC TA1 and TA2 to the appropriate DL reference timing to set the UL transmission timing for TAG1 and TAG2.

[0058] The following was proposed in RAN1#118bis(Hefei): "...Supports 2TA for asymmetric DL sTRP / UL mTRP deployment scenarios:" Removed the restriction that coresetPoolIndex needs to be configured for 2TA features.

[0059] Supports a downlink reference timing and applies it to two tags.

[0060] (FFS Note: UE-autonomous TA adjustment only applies to the first TAG) A single n-TimingAdvanceoffset is configured and applied to both tags.

[0061] Any TCI state can be associated with either of the two TAGs.

[0062] The RAR carrying the TA adjustments for these two tags was reused for Rel-19 2TA. The MAC CE-based TA adjustment for the two tags was reused in Rel-19 2TA.

[0063] Introducing optional UE capability of “overlapping UL transmission reduction” for Rel-19 2TA. If the UE does not report its capabilities, the UE does not expect two UL transmissions associated with different TAGs to overlap.

[0064] FFS: The UE does not expect two consecutive repetitions associated with different tags to overlap in a TDM PUSCH type B repetition transmission within a time slot… The following was proposed in RAN1#119 (Orlando): The answer to question 1 in LS R1-2409353 is: From the user experience (UE) perspective: If the UE has a PL offset configured in (multiple) joint / UL TCI states, the UE does not expect The UE may receive SSBs from (multiple) UL TRPs; otherwise, the UE may expect to receive SSBs from (multiple) UL TRPs. …” The following conclusions were drawn from RAN1#120 (Athens): "...In asymmetric DL sTRP / UL mTRP deployment scenarios, The PDCCH-order PRACH to UL TRP is CFRA …” The following was proposed in RAN1#120bis(Wuhan): "...the following are the answers to question RAN4:" RAN1 proposal in RAN1#118bis: "Support a downlink reference timing and apply it to two tags" This should not be applied when the UE is not configured with a PL offset in (multiple) joint / UL TCI states and the UE may expect to receive from (multiple) UL TRPs. Scenarios for receiving SSB …” The following was proposed in RAN1#120bis(Wuhan): "... For scenarios where the UE is configured with a PL offset in (multiple) joint / UL TCI states, when the UE is configured with rel-19 In dual TA mode, the UE maintains a single downlink reference timing. For UEs that are not configured with a PL offset in (multiple) joint / UL TCI states and the UE may expect to receive PL offsets from (multiple) UL states. In scenarios where the TRP receives the SSB, when the UE is configured with rel-19 dual TA... : The UE maintains two downlink reference timings; The baseline assumption for this feature is that the Rx timing difference between two DL reference timings is no greater than one CP length, while the Rx timing difference between two DL reference timings can be assumed to be greater than the CP length, which is subject to the optional UE capabilities.

[0065] The reference point used for PRACH transmission is indicated as follows: If the "PRACH association indicator" in DCI format 1_0 is 0, then the reference timing is the reference cell associated with the first TAG. (Multiple) DL TCI status (Multiple) The first detection path (in time) corresponds to one of the downlink reference signals.

[0066] If the "PRACH association indicator" in DCI format 1_0 is 1, then the reference timing is the reference cell associated with the second TAG. (Multiple) DL TCI status (Multiple) The first detection path (in time) corresponds to one of the downlink reference signals. The above applies to UE configurations with SSB-MTC-additionalPCI The situation… In asymmetric DL sTRP / UL mTRP scenarios, for UL-only TRPs that do not transmit RS (such as SSB), the UE uses a single DL reference timing for both the DL / UL-capable TRP (TAG1) and the UL-only TRP (TAG2). Therefore, the timing error transmitted to the UE for UL-only TRPs tends to be larger compared to scenarios where the UE needs to monitor the DL reference timing for each TAG (as in Rel-18). This timing error is then compensated for by the network via TAC. However, when the UE transmits the Random Access Channel (RACH) preamble, this transmission is not time-advanced to align with the uplink reception time at the gNB receiver because the network has not yet sent the TAC to the UE (i.e., the TAC is received in the RAR first after the RACH preamble transmission).

[0067] For example, during preamble transmission as part of the PRACH procedure, as specified in TS 38.133, the reference point for the UE's initial transmission timing control requirements is the downlink timing of the reference cell. Therefore, when PRACH is triggered toward a UL-only TRP (such as an SSB) that does not transmit RS, since the UE does not have a downlink reference timing from the UL-only TRP, the UE transmits the RACH preamble toward the UL-only TRP based on: the DL reference timing from a TRP with DL / UL capabilities; and a timing advance offset n-TimingAdvanceOffset / n-TimingAdvanceOffset2, optionally configured by the network.

[0068] In this “Asymmetric DL sTRP / UL mTRP scenario”, because the UE may not be able to obtain the DL reference timing based on the RS sent by UL TRP alone, the transmission timing error of the PRACH preamble may be too large, which may lead to a) interference and b) the network being unable to detect the RACH preamble.

[0069] Late arrival is unlikely to be a major problem due to the guard period (GP) at the end of the RACH preamble (in most preamble formats), as the GP following the preamble sequence ensures that the preamble will not interfere with other uplink transmissions when received by the gNB receiver. However, early arrival can be problematic.

[0070] Early arrival scenarios can be addressed using a default timing offset, depending on the timing alignment error (TAE), more specifically, 0.5 * TAE ≈ 1.5 μs (TAE is defined in 38.104: the maximum TAE should not exceed 3 μs). However, while such a solution addresses the TAE involved in imperfect time synchronization between the two TRPs, it does not address the difference in propagation delay from the two TRPs. Note that this 1.5 μs roughly means a gap that can handle a propagation delay difference of approximately 450 meters without any TAE, which might be sufficient for FR2 but possibly insufficient for FR1.

[0071] The technical effect of the exemplary embodiments of this disclosure can be to reduce uplink interference caused by misaligned RACH preamble transmissions toward UL TRP-only transmissions that do not transmit any RS.

[0072] In the example embodiment, the “force” field, which indicates the timing offset when the UE transmits a PRACH, can be implemented for asymmetric DL sTRP / UL mTRP deployments with two TAs. In other words, when transmitting a PRACH to a UL-only TRP, for example before receiving a TAC regarding the UL-only TRP, the UE can force the application of a timing offset.

[0073] In the example embodiment, the timing offset can be a timing offset relative to the downlink reference timing of a TRP with DL / UL capability (e.g., an anchor TRP). Additionally or alternatively, the timing offset can be exactly one of the higher-layer parameters n-TimingAdvanceOffset or n-TimingAdvanceOffset2 defined in the standard. Note that if n-TimingAdvanceOffset2 is not configured, the timing offset for TAG2 can be the value of n-TimingAdvanceOffset. Also note that if n-TimingAdvanceOffset is not configured either, the UE can use the default value.

[0074] In example embodiments, the timing offset may be mandatory only when the UE transmits PRACH to a UL-only TRP. Additionally or alternatively, when the UE is configured / required to monitor a DL reference timing together for both a DL / UL-capable TRP and a UL-only TRP, the timing offset may be mandatory only for the UL-only TRP. Additionally or alternatively, when such a UL-only TRP does not transmit any RS, the timing offset may be mandatory only for the UL-only TRP. For example, the timing offset may be mandatory only if the UL-only TRP does not transmit any RS within a first time window or period preceding the transmission / reception time of the RACH preamble or the transmission / reception time of the PDCCH command message (e.g., the time slot for sending / receiving such signaling). Additionally or alternatively, when the UE is configured with a PL offset associated with at least one TCI state for a UL-only TRP, the timing offset may be mandatory only for such UL-only TRPs.

[0075] In an example embodiment, PRACH can be triggered by a PDCCH command from a TRP with DL / UL capabilities.

[0076] In example embodiments, timing offsets can be configured / included in PDCCH command messages (e.g., commands to trigger PRACH) from the network. Alternatively or additionally, timing offsets can be configured in separate messages before or after the PDCCH command, for example, via DCI, RRC, or MAC CE. Alternatively or additionally, the network can send the timing offset along with a timing advance command for a TRP with DL / UL capability. Alternatively or additionally, timing offsets can be configured / included in SIB messages from the network. Alternatively or additionally, timing offsets can be obtained from the UE, the gNB with DL / UL capability, and a lookup table known only to the UL TRP. The lookup table can include several timing offset values ​​(e.g., positive and / or negative values). The TRP with DL / UL capability can indicate an index for the timing offset towards the RACH preamble for the UL-only TRP via DL control signaling (e.g., DCI, MAC CE, RRC, etc.). Alternatively or additionally, the timing offset can be obtained from the network-side AI / ML module, for example, at a TRP with DL / UL capability. The network-side model can be trained based on data from a DL / UL-capable TRP, such as: the location of the UL-only TRP, the UE's location, the timing offset(s) used in the UE, UE operating parameters, etc. The network-side model can acquire the UE and the location of the UL-only TRP and / or other UE operating parameters, and output the timing offset required to transmit the UE's RACH preamble to the UL-only TRP. The DL / UL-capable TRP can indicate this value to the UE. Alternatively or additionally, the timing offset can be indicated via the "PRACH indicator bit" in DCI 1_0, as introduced in Rel-19. Alternatively or additionally, the timing offset can be indicated in the PL offset configuration in the DCI or in the UL / joint TCI state.

[0077] In example embodiments, the RACH process may include CFRA only, CBRA only, or both CBRA and CFRA.

[0078] Now for reference Figure 5This illustrates an example of a UE configured with a timing offset for PRACH transmission, which is mandatory only for UL TRP only when no RS is transmitted by this UL TRP only. At 505, the UE can be configured with an asymmetric DL sTRP / UL mTRP configuration. At 510, it can be determined in the network that RS is not transmitted by UL TRP only. At 515, the DL / UL TRP can transmit a timing offset configuration for UL TRP only to the UE. In one example, the timing offset configuration may include a mandatory timing offset. At 520, the DL / UL TRP can transmit DL RS to the UE. At 525, the DL / UL TRP can transmit PDSCH and / or PDCCH to the UE. At 530, the UE can transmit PUSCH and / or PUCCH to both the DL / UL TRP and the UL TRP only. At 535, the NW can determine that PRACH is required towards the UL TRP only. At 540, the DL / UL TRP can transmit a PDCCH command to the UE to trigger a PRACH towards the UL-only TRP. At 545, the UE can determine the transmission timing of the RACH preamble to the UL-only TRP, at least based on a forced timing offset. At 550, the UE can transmit the PRACH preamble to the UL-only TRP, at least partially based on the determined transmission timing. The determined transmission timing may include applying a forced timing offset to the transmission timing determined based on, for example, a reference timing associated with the DL / UL TRP. The DL / UL TRP can know when the UE will transmit the PRACH to the UL-only TRP.

[0079] In an example embodiment, the UE may receive a message including: an indication of a mandatory timing offset for transmitting PRACH to a UL-only TRP transmitting RS, and an indication that such UL-only TRP stops transmitting RS, for example, after another second time window or period predefined in the standard or configured by the network. The offset may be considered mandatory immediately, or the offset may be considered mandatory only after the second time window has expired or ended.

[0080] Now for reference Figure 6Example of a timing offset configuration message further instructing the UL TRP only to stop any RS transmissions is shown. At 605, the UE can be configured with an asymmetric DL sTRP / UL mTRP configuration. At 610, the DL / UL TRP can transmit DL RS to the UE. At 615, the UL TRP only can transmit DL RS to the UE. At 620, the DL / UL TRP can transmit PDSCH and / or PDCCH to the UE. At 625, the UE can transmit PUSCH and / or PUCCH to both the DL / UL TRP and the UL TRP only. At 630, the NW can determine to stop RS transmissions from the UL TRP only. At 635, the DL / UL TRP can transmit a timing offset configuration for the UL TRP only to the UE, which may include a forced timing offset. At 640, the UL TRP only can stop RS transmissions. At 645, the NW can determine that a PRACH is needed towards the UL TRP only. It can be noted that before configuring the transmission timing offset, the NW can optionally determine the need for a PRACH toward the UL TRP only. At 650, the DL / UL TRP can transmit a PDCCH command to the UE to trigger the PRACH toward the UL TRP only. At 655, the UE can determine the transmission timing of the RACH preamble toward the UL TRP only based at least on the forced timing offset. At 660, the UE can transmit the PRACH preamble to the UL TRP only based at least partially on the determined transmission timing. The determined transmission timing may include applying the forced timing offset to a transmission timing determined based on, for example, a reference timing associated with the DL / UL TRP. The DL / UL TRP can know when the UE will transmit the PRACH to the UL TRP only.

[0081] The technical effect of the exemplary embodiments of this disclosure can be to enable the UE to better transmit the RACH preamble in an asymmetric DLsTRP / UL mTRP deployment with two TAs, for example, because the network always configures a timing offset under certain conditions.

[0082] In the example embodiment, when the UE transmits PRACH in an asymmetric DL sTRP / UL mTRP deployment with two TAs, a "Timing Offset DELTA field" can be implemented in addition to n-TimingAdvanceOffset / n-TimingAdvanceOffset2. In the example embodiment, a timing offset increment can be added to n-TimingAdvanceOffset / n-TimingAdvanceOffset2 to set the UL transmission timing of the PRACH. In the example embodiment, the timing offset increment can be a positive or negative value.

[0083] In this disclosure, the terms “timing offset increment”, “increment value”, “additional timing offset”, “another timing offset”, “high-resolution timing offset” and “high-granularity timing offset” are used interchangeably.

[0084] In the example embodiment, the timing offset increment can be used only when the UE transmits PRACH to the UL-only TRP. Alternatively, when the UE is configured / required to monitor a DL reference timing together for both a DL / UL-capable TRP and a UL-only TRP, the timing offset increment can be introduced only to the UL-only TRP. Alternatively, when such a UL-only TRP does not transmit any RS, the timing offset increment can be introduced only to the UL-only TRP. Additionally, or alternatively, the timing offset increment can be introduced only when the UL-only TRP does not transmit any RS within a first time window or period preceding the RACH preamble transmission / reception time or the PDCCH command message. Alternatively, when the UE is configured with a PL offset associated with at least one TCI state for the UL-only TRP (which can be transmitted to the UE, for example, by the anchor TRP), the timing offset increment can be introduced only toward such UL-only TRP.

[0085] In an example embodiment, PRACH can be triggered by a PDCCH command from a TRP with DL / UL capabilities.

[0086] In example embodiments, the timing offset increment can be configured / included in a PDCCH command message from the network. Additionally or alternatively, the timing offset increment can be configured in a separate message before or after the PDCCH command, for example, via DCI, RRC, or MAC CE. Additionally or alternatively, the timing offset increment can be sent by the network along with a timing advance command for a TRP with DL / UL capability. Additionally or alternatively, the timing offset increment can be configured / included in an SIB message from the network. Additionally or alternatively, the timing offset increment can be obtained from the UE, the gNB with DL / UL capability, and a lookup table known only to the UL TRP. The lookup table can include several timing offset DELTA values ​​(e.g., positive and / or negative values). The TRP with DL / UL capability can indicate an index for the timing offset DELTA towards the RACH preamble for a ULTRP only via, for example, DL control signaling (e.g., DCI, MAC CE, RRC, etc.). Alternatively or additionally, the timing offset increment can be obtained from the network-side AI / ML module, for example, at a TRP with DL / UL capability. The network-side model can be trained based on data from a TRP with DL / UL capability, such as the location of the UL-only TRP, the UE's location, the timing offset increment used in the UE, UE operating parameters, etc. The network-side model can acquire the UE's location, the location of the UL-only TRP, and / or other UE operating parameters, and output the timing offset increment required for the UE's RACH preamble to the UL-only TRP. The DL / UL-enabled TRP can indicate this value to the UE. Alternatively or additionally, the timing offset increment can be indicated via the "PRACH indicator bit" in DCI 1_0, for example, as introduced in Rel-19. Alternatively or additionally, the timing offset increment can be indicated in the PL offset configuration (e.g., in the DCI or in the UL / joint TCI state).

[0087] In an example embodiment, when the UE is configured with such a timing offset increment for transmitting RS-only UL TRP, such a message may also instruct such UL-only TRP to stop transmitting RS, for example, after another second time window or period predefined in the standard or configured by the network.

[0088] In example embodiments, the RACH process may include CFRA only, CBRA only, or both CBRA and CFRA.

[0089] The technical effect of the exemplary embodiments of this disclosure can be to enable the UE to perform better transmission timing of the RACH preamble in an asymmetric DLsTRP / UL mTRP deployment with two TAs, for example, due to timing offsets that can be configured with better granularity.

[0090] An example of an AI / ML module or model is a neural network. A neural network (NN) is a computational graph consisting of two or more layers of computation. Each layer may consist of one or more units, each of which performs basic computations. Units may be connected to one or more other units, and this connection may have weights associated with it. Weights can be used to scale signals through the associated connections. Weights can be learnable parameters, i.e., values ​​that can be learned from training data. Other learnable parameters may exist, such as the parameters of batch normalization layers. Neural networks and other machine learning tools may be able to learn properties from input data in a supervised or unsupervised manner. This learning can be the result of a training algorithm or a meta-level neural network that provides training signals.

[0091] Figure 7 Potential steps of example method 700 are illustrated. Example method 700 may include: determining a random access preamble to be transmitted to the uplink-only transmission and reception point 710; determining timing 720 for transmitting the random access preamble to the uplink-only transmission and reception point based at least in part on a forced timing offset; and transmitting the random access preamble to the uplink-only transmission and reception point 730 based at least in part on the determined timing. For example, example method 700 may be performed using a UE.

[0092] Figure 8 Potential steps of example method 800 are illustrated. Example method 800 may include: transmitting a forced timing offset 810 to a user equipment associated with transmitting a random access preamble to the uplink-only transmission and receiver point; and transmitting an indication 820 to the user equipment for transmitting the random access preamble to the uplink-only transmission and receiver point. Example method 800 may be performed, for example, by a network node, base station, TRP, DL / UL TRP, gNB, network entity, etc.

[0093] Figure 9 Potential steps of example method 900 are illustrated. Example method 900 may include: determining a random access preamble to be transmitted to the transmitting and receiving points 910; determining a timing offset for transmitting the random access preamble 920; determining an increment value associated with the timing offset 930; determining timing for transmitting the random access preamble to the transmitting and receiving points based at least in part on the timing offset and the increment value 940; and transmitting the random access preamble to the uplink-only transmitting and receiving points 950 based at least in part on the determined timing. For example, example method 900 may be performed using a UE.

[0094] Figure 10The potential steps of example method 1000 are illustrated. Example method 1000 may include: transmitting a timing offset 1010 to a user equipment for transmitting a random access preamble to the transmitting and receiving points; transmitting an increment value 1020 associated with the timing offset to the user equipment; and transmitting an indication 1030 to the user equipment for transmitting the random access preamble to the transmitting and receiving points. Example method 1000 may be performed, for example, by a network node, base station, TRP, DL / UL TRP, gNB, network entity, etc.

[0095] According to the first aspect, the following subject matter is provided: determining a random access preamble for transmission to an uplink-only transmission and reception point; determining the timing for transmitting the random access preamble to the uplink-only transmission and reception point based at least in part on a forced timing offset; and transmitting the random access preamble to the uplink-only transmission and reception point based at least in part on the determined timing. The first aspect may be implemented in algorithms, encoded in distributed media or computer program products, and implemented as methods executed by means of means of means. An apparatus may include components for causing the means to perform at least the methods. The components may include: at least one processor; and at least one memory storing the algorithms as instructions that, when executed by the at least one processor, cause the means to perform at least the methods.

[0096] The first aspect may include any single feature or any combination of features from the following: - The forced timing offset is determined based on at least one of the following: a timing offset configuration for uplink-only transmission and reception points, which may include at least a forced timing offset; a physical downlink control channel message, which may include at least a forced timing offset; downlink control information; radio resource control signaling; media access control signaling; a system information block message; a timing advance command for another transmission and reception point, which may include at least a forced timing offset; a table that may include multiple timing offset values; the output of a trained model; or a path loss offset configuration, which may include at least a forced timing offset.

[0097] - Receive timing offset configuration from another transmit and receive point.

[0098] Downlink control information may include at least a physical random access channel indicator bit that indicates a forced timing offset.

[0099] - Receive downlink control signaling, wherein the downlink control signaling may include at least the table index.

[0100] The trained model may include a network-side model trained using at least one of the following: location of uplink transmission and reception points only, device location, or timing offset associated with user equipment.

[0101] - Forced timing offset can include one of the following: a first timing advance offset associated with a first timing advance group, a second timing advance offset associated with a second timing advance group, or a default value.

[0102] - A mandatory timing offset may include the following timing offset: This timing offset is mandatory for random access preamble transmissions toward only uplink transmission and reception points.

[0103] - A mandatory timing offset may include the following timing offset: in response to the device / UE being configured to monitor a single downlink reference timing for both uplink-only transmission and reception points and another transmission and reception point, the timing offset may be mandatory for random access preamble transmissions toward the uplink-only transmission and reception point.

[0104] - A forced timing offset may include a timing offset that is mandatory for random access preamble transmissions toward an uplink-only transmission and reception point in response to the failure to receive a reference signal from the uplink-only transmission and reception point during a predetermined time period.

[0105] - The predetermined time period may include one of the following: a time period before the reception time of the indication used to transmit the random access preamble to the uplink-only transmission and the receiving point, or a time period before the determined timing.

[0106] Determining the timing for transmitting the random access preamble may include: receiving an indication of the time for uplink-only transmission and the time for the receiving point to stop transmitting one or more reference signals; and determining the timing for transmitting the random access preamble based at least in part on the time for uplink-only transmission and the time for the receiving point to stop transmitting one or more reference signals.

[0107] - The indication may be received via a timing offset configuration for uplink-only transmission and reception points, wherein the timing offset configuration may also include a forced timing offset.

[0108] - A mandatory timing offset may include a timing offset that is mandatory for random access preamble transmission toward an uplink-only transmission and reception point, in response to the device / UE being configured with a path loss offset associated with at least one transmission configuration indicator state configured for uplink-only transmission and reception point.

[0109] - The timing for transmitting the random access preamble can also be determined based on the downlink reference timing associated with another transmission and reception point.

[0110] - Determining to transmit the random access preamble to the uplink-only transmission and reception point may include receiving an indication via the physical downlink control channel to transmit the random access preamble to the uplink-only transmission and reception point.

[0111] - The random access preamble may include a random access preamble for one of the following: contention-free random access or contention-based random access.

[0112] - Uplink-only transmission and reception points may include at least one of the following: transmission and reception points that do not transmit data or control signals to the device / UE, transmission and reception points that do not transmit dedicated reference signals to the device / UE, or transmission and reception points that transmit reference signals common to multiple user equipments.

[0113] - The device / UE may include user equipment.

[0114] According to the second aspect, the following topics are provided: transmitting to a user equipment a forced timing offset associated with transmitting a random access preamble to an uplink-only transmission and a receive point; and transmitting to the user equipment an indication to transmit a random access preamble to an uplink-only transmission and a receive point. The second aspect can be implemented in algorithms, encoded in distributed media or computer program products, and implemented as methods executed by means of means of means. An apparatus may include components for causing the means to perform at least the methods. The components may include: at least one processor; and at least one memory storing the algorithms as instructions that, when executed by the at least one processor, cause the means to perform at least the methods.

[0115] The second aspect may include any single feature or any combination of features from the following: - Determine that only the uplink transmission and reception points may not transmit reference signals to the user equipment, wherein a forced timing offset may be transmitted to the user equipment based at least in part on the determination that only the uplink transmission and reception points do not transmit reference signals to the user equipment.

[0116] - Forced timing offsets can be transmitted via at least one of the following: timing offset configuration for uplink-only transmission and reception points; physical downlink control channel messages; downlink control information; radio resource control signaling; media access control signaling; system information block messages; timing advance commands associated with device / network nodes; an index of a table including multiple timing offset values; or path loss offset configuration.

[0117] Downlink control information may include at least a physical random access channel indicator bit that indicates a forced timing offset.

[0118] - A forced timing offset may include at least one of the following: a value output from a network-side model trained using at least one of the following: the location of the uplink transmission and reception point only, the location of the user equipment, or a timing offset associated with the user equipment; a first timing advance offset associated with a first timing advance group; a second timing advance offset associated with a second timing advance group; or a default value.

[0119] - A mandatory timing offset may include the following timing offset: This timing offset is mandatory for random access preamble transmissions toward only uplink transmission and reception points.

[0120] - A mandatory timing offset may include the following timing offset: in response to the user equipment being configured to monitor a single downlink reference timing for both uplink-only transmission and reception points and device / network nodes, the timing offset may be mandatory for random access preamble transmissions toward uplink-only transmission and reception points.

[0121] - A forced timing offset may include a timing offset that is mandatory for random access preamble transmission toward an uplink-only transmission and reception point in response to the failure to receive a reference signal from the uplink-only transmission and reception point during a predetermined time period.

[0122] - The predetermined time period may include one of the following: a time period prior to the transmission time for the indication of transmitting the random access preamble to the uplink-only transmission and receiving point, or a time period prior to the transmission time for transmitting the random access preamble to the uplink-only transmission and receiving point.

[0123] - Transmits to the user equipment an indication of the time when uplink transmission only and the receiving point stops transmitting one or more reference signals.

[0124] - An indication of when the uplink-only transmission and reception point should stop transmitting one or more reference signals can be transmitted via a timing offset configuration for the uplink-only transmission and reception point, wherein the timing offset configuration may also include a forced timing offset.

[0125] - A forced timing offset may include a timing offset that is mandatory for random access preamble transmission toward an uplink-only transmission and reception point, in response to a device / network node being configured with a path loss offset associated with at least one transmission configuration indicator state configured for uplink-only transmission and reception point transmission.

[0126] - Transmit to the user equipment the configuration of at least one transmission configuration indicator state for uplink transmission and receiving point configuration only.

[0127] - Indications for random access preambles can be transmitted to uplink-only transmission and receiving points via the physical downlink control channel.

[0128] - Random access preambles may include random access preambles for either contention-free random access or contention-based random access.

[0129] - Uplink-only transmission and reception points may include at least one of the following: transmission and reception points that do not transmit data or control signals to user equipment, transmission and reception points that do not transmit dedicated reference signals to user equipment, or transmission and reception points that transmit reference signals common to multiple user equipment.

[0130] Transmit and receive points configured to perform uplink and downlink communication with user equipment may include devices / network nodes.

[0131] As used herein, the terms “circuit” or “component” may refer to one or more or all of the following: (a) a hardware circuit implementation (such as an implementation in an analog, digital, and / or quantum circuit system); and (b) a combination of (multiple) hardware circuits and software, such as (if applicable): (i) a combination of (multiple) analog, digital, and / or quantum hardware circuits with software / firmware; and (ii) any or all portions of (multiple) hardware processors (including (multiple) digital and / or quantum processors with software), and (multiple) memories, which work together to enable a device such as a mobile device, computing device, or server to perform various functions; and (c) any or all portions of (multiple) hardware circuits, such as (multiple) microprocessors, (multiple) processors, and / or (multiple) quantum processors, which require software (e.g., firmware) to operate, but may be absent when the software is not required to operate. This definition of a circuit applies to all uses of the term herein (including in any claim). As another example, as used herein, the term "circuit" also encompasses implementations of hardware circuitry or processors (or processors) or a portion thereof and their accompanying software and / or firmware. The term "circuit" also encompasses, for example and if applicable to a particular claim element, baseband integrated circuits or processor integrated circuits for mobile devices or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0132] Processors, memory, and / or example algorithms (which may be encoded as instructions, programs, or code) may be provided as example components for providing or causing the execution of operations.

[0133] As used herein, the term “non-transient” refers to a limitation on the medium itself (i.e., tangible, not signaling), rather than a limitation on the persistence of data storage (e.g., RAM vs. ROM).

[0134] As used herein, the terms “at least one” and “one or more” mean “any one of at least one” and “any one of one or more”, respectively.

[0135] It should be understood that the foregoing description is illustrative only. Those skilled in the art can devise various alternatives and modifications. For example, the features recited in the various dependent claims can be combined with each other in any suitable combination. Furthermore, features from the different embodiments described above can be selectively combined to form new embodiments. Therefore, this specification is intended to cover all such alternatives, modifications, and variations that fall within the scope of the appended claims.

[0136] Furthermore, the various implementations of this disclosure can be described with reference to the following terms, and their features can be combined in any reasonable manner.

[0137] Clause 1. An apparatus for communication, comprising: at least one processor; and at least one memory storing instructions that, when executed using the at least one processor, cause the apparatus to at least: determine a random access preamble to be transmitted to an uplink-only transmission and reception point; determine timing for transmitting the random access preamble to the uplink-only transmission and reception point based at least in part on a forced timing offset; and transmit the random access preamble to the uplink-only transmission and reception point based at least in part on the determined timing.

[0138] Clause 2. The apparatus according to Clause 1, wherein when the instructions are executed using at least one processor, the apparatus causes to: determine a forced timing offset based on at least one of: a timing offset configuration for uplink-only transmission and reception points, the timing offset configuration including at least a forced timing offset; a physical downlink control channel message including at least a forced timing offset; downlink control information; radio resource control signaling; media access control signaling; a system information block message; a timing advance command for another transmission and reception point, including at least a forced timing offset; a table including multiple timing offset values; the output of a trained model; or a path loss offset configuration including at least a forced timing offset.

[0139] Clause 3. The apparatus according to Clause 2, wherein the instructions, when executed using at least one processor, cause the apparatus to: receive a timing offset configuration from another transmission and reception point.

[0140] Clause 4. The apparatus according to Clause 2, wherein the downlink control information includes at least a physical random access channel indication bit indicating a forced timing offset.

[0141] Clause 5. The apparatus according to Clause 2, wherein when the instructions are executed using at least one processor, the apparatus causes to: receive downlink control signaling, wherein the downlink control signaling includes at least an index of a table.

[0142] Clause 6. An apparatus pursuant to Clause 2, wherein the trained model includes a network-side model trained using at least one of the following: location of uplink transmission and reception points only, location of the apparatus, or timing offset associated with the user equipment.

[0143] Clause 7. The apparatus according to Clause 1, wherein the forced timing offset includes one of the following: a first timing advance offset associated with a first timing advance group, a second timing advance offset associated with a second timing advance group, or a default value.

[0144] Clause 8. The apparatus according to Clause 1, wherein the mandatory timing offset includes a mandatory timing offset for random access preamble transmission toward only uplink transmission and receiving point.

[0145] Clause 9. The apparatus of Clause 1, wherein the mandatory timing offset includes a timing offset such that, in response to the apparatus being configured to monitor a single downlink reference setting for both uplink-only transmission and reception points and another transmission and reception point, the timing offset is mandatory for random access preamble transmissions toward the uplink-only transmission and reception point.

[0146] Clause 10. The apparatus according to Clause 1, wherein the mandatory timing offset includes a timing offset that is mandatory for random access preamble transmission toward the uplink-only transmission and reception point in response to the failure to receive a reference signal from the uplink-only transmission and reception point during a predetermined time period.

[0147] Clause 11. The apparatus according to Clause 10, wherein the predetermined time period includes one of the following: a time period prior to the reception time for the indication of transmitting the random access preamble to the uplink-only transmission and the receiving point, or a time period prior to the determined timing.

[0148] Clause 12. The apparatus according to Clause 10, wherein determining the timing for transmitting the random access preamble comprises instructions, when executed using at least one processor, causing the apparatus to: receive an indication of the time for uplink-only transmission and the time for the receiving point to stop transmitting one or more reference signals; and determine the timing for transmitting the random access preamble based at least in part on the time for uplink-only transmission and the time for the receiving point to stop transmitting one or more reference signals.

[0149] Clause 13. The apparatus pursuant to Clause 12, wherein the indication is received via a timing offset configuration for uplink-only transmission and reception points, wherein the timing offset configuration further includes a forced timing offset.

[0150] Clause 14. The apparatus according to Clause 1, wherein the mandatory timing offset includes a timing offset that is mandatory for random access preamble transmission toward the uplink-only transmission and reception point in response to the apparatus being configured with a path loss offset associated with at least one transmission configuration indicator state configured for uplink-only transmission and reception point.

[0151] Clause 15. The apparatus according to Clause 1, wherein the timing for transmitting the random access preamble is also determined based on a downlink reference timing associated with another transmission and reception point.

[0152] Clause 16. The apparatus according to Clause 1, wherein determining to transmit a random access preamble to an uplink-only transmission and reception point includes instructions, when executed using at least one processor, causing the apparatus to: receive, via a physical downlink control channel, an indication for transmitting the random access preamble to an uplink-only transmission and reception point.

[0153] Clause 17. The apparatus according to Clause 1, wherein the random access preamble includes a random access preamble for one of: contention-free random access or contention-based random access.

[0154] Clause 18. The apparatus according to Clause 1, wherein the uplink transmission and reception point includes at least one of the following: a transmission and reception point that does not transmit data or control signals to the apparatus, a transmission and reception point that does not transmit dedicated reference signals to the apparatus, or a transmission and reception point that transmits reference signals common to multiple user equipments.

[0155] Clause 19. An apparatus pursuant to any one of Clauses 1 to 18, wherein the apparatus includes user equipment.

[0156] Clause 20. A method for communication, comprising: using a user equipment to determine a random access preamble to be transmitted to an uplink-only transmission and reception point; determining timing for transmitting the random access preamble to the uplink-only transmission and reception point based at least in part on a forced timing offset; and transmitting the random access preamble to the uplink-only transmission and reception point based at least in part on the determined timing.

[0157] Clause 21. An apparatus for communication, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: transmit to a user equipment a forced timing offset associated with transmitting a random access preamble to an uplink-only transmission and receiving point; and transmit to the user equipment an indication for transmitting the random access preamble to an uplink-only transmission and receiving point.

[0158] Clause 22. A method for communication, comprising: transmitting a forced timing offset associated with transmitting a random access preamble to an uplink-only transmission and a receiving point via a network node to a user equipment; and transmitting an indication to the user equipment for transmitting the random access preamble to an uplink-only transmission and a receiving point.

Claims

1. A device for communication, comprising: At least one processor; as well as At least one memory storing instructions that, when executed using the at least one processor, cause the device to at least: Determine to transmit random access preamble to only the uplink transmission and the receiving point; The timing for transmitting the random access preamble to the uplink-only transmission and reception point is determined at least in part based on a forced timing offset. as well as The random access preamble is transmitted to the uplink-only transmission and reception point at least in part based on the determined timing.

2. The apparatus of claim 1, wherein the instructions, when executed using the at least one processor, cause the apparatus to: The forced timing offset is determined based on at least one of the following: The timing offset configuration for the uplink-only transmission and reception point includes at least the forced timing offset. Physical downlink control channel messages, which include at least the forced timing offset; Downlink control information; Radio resource control signaling; Media access control signaling; System information block message; A timing advance command for another transmission and reception point, which includes at least the forced timing offset; A table containing multiple timing offset values; The output of the trained model; or It includes at least the path loss offset configuration for the forced timing offset.

3. The apparatus of claim 2, wherein the instructions, when executed using the at least one processor, cause the apparatus to: The timing offset configuration is received from the other transmission and reception point.

4. The apparatus of claim 2, wherein the downlink control information includes at least a physical random access channel indication bit indicating the forced timing offset.

5. The apparatus of claim 2, wherein the instructions, when executed using the at least one processor, cause the apparatus to: Receive downlink control signaling, wherein the downlink control signaling includes at least the index of the table.

6. The apparatus of claim 2, wherein the trained model comprises a network-side model trained using at least one of the following: the location of the uplink-only transmission and reception point, the location of the apparatus, or a timing offset associated with the user equipment.

7. The apparatus of claim 1, wherein the forced timing offset comprises one of the following: The first timing advance offset associated with the first timing advance group, The second timing advance offset associated with the second timing advance group, or default value.

8. The apparatus of claim 1, wherein the forced timing offset includes a forced timing offset for random access preamble transmission toward the uplink-only transmission and reception point.

9. The apparatus of claim 1, wherein the forced timing offset comprises a timing offset that is mandatory for random access preamble transmission toward the uplink-only transmission and reception point in response to the apparatus being configured to monitor a single downlink reference setting for both the uplink-only transmission and reception point and another transmission and reception point.

10. The apparatus of claim 1, wherein the forced timing offset comprises a timing offset that is mandatory for random access preamble transmission toward the uplink-only transmission and reception point in response to the failure to receive a reference signal from the uplink-only transmission and reception point during a predetermined time period.