METHOD AT A TERMINAL NODE, METHOD AT A NETWORK NODE, TERMINAL NODE, AND, NETWORK NODE

Description

/ 90 METHOD AT A TERMINAL NODE, METHOD AT A NETWORK NODE, TERMINAL NODE, AND, NETWORK NODE TECHNICAL FIELD

[001] The present description relates to the field of telecommunications and, in particular, to terminal nodes, network nodes and methods for Physical Random Access Channel (PRACH) Occasion (RO) indexing in multiple PRACH transmissions. FUNDAMENTALS OF THE INVENTION

[002] With the development of electronic and telecommunications technologies, mobile devices, such as a cell phone, a smartphone, a laptop, a tablet, a vehicle-mounted device, become an important part of our daily lives. To support a large number of mobile devices, a highly power-efficient Radio Access Network (RAN), such as a fifth-generation (5G) New Radio (NR) RAN, will be required. Search for NR cell and system information acquisition.

[003] In NR, the combination of synchronization signals (SS) and physical broadcast channel (PBCH) is referred to as an SS / PBCH block (SSB). Similar to LTE, an SS pair, primary synchronization signal (PSS) and secondary synchronization signal (SSS), is periodically transmitted downlink from each cell to allow a UE to initially access the network. By detecting the SS, a UE can obtain the physical cell identity, achieve downlink synchronization in both time and frequency, and acquire synchronization for the PBCH. The PBCH carries the Master Information Block (MIB), which contains the minimum system information required for a UE to acquire System Information Block 1 (SIB 1). SIB 1 carries the remaining Minimum System Information required for a UE to perform subsequent random access procedures.

[004] Up to 4, 8, or 64 SSBs, depending on the frequency band of Petition 870250088817, dated 09 / 30 / 2025, page 125 / 235 / 90 frequency band used, can be transmitted in an SSB period that can be 5 ms, 10 ms, 20 ms, 40 ms, 80 ms or 160 ms configured in SIB1, the standard SSB period is 20 ms considered for initial cell search, since SIB1 is not available. Random Access Procedure NR

[005] Random access is performed by a terminal device, for example, User Equipment (UE), in NR and Long Term Evolution (LTE) networks for access to a new cell. Once a random access procedure is completed, a terminal device can be connected to a network device, for example, an evolved NodeB (eNB) or gNB, and communicate with the network device using dedicated transmissions.

[006] Two types of random access procedures are supported: There are 4-step random access types with Msg1 and 2-step random access types with MSGA. Both Random Access (RA) procedure types support contention-based random access (CBRA) and contention-free random access (CFRA).

[007] Figure 1A shows a signaling sequence of a 4-step contention-based random access procedure, also referred to as Type 1 random access procedure in 3GPP TS 38.213. As shown in 101, a UE detects a Synchronization Signal (SS) from a gNB. In 102, the UE decodes Master Information Block (MIB) and System Information Block (SIB) (i.e., Minimum Remaining System Information (RMSI) and Other System Information (OSI), which may be distributed across multiple physical channels such as Physical Broadcast Channel (PBCH) and Physical Downlink Shared Channel (PDSCH)), to acquire random access transmission parameters. In 111, the UE transmits a Physical Random Access Channel (PRACH) preamble, or Msg1, to the gNB. The gNB detects the Petition 870250088817, dated 09 / 30 / 2025, pages 126 / 235 / 90 Msg1 responds with a Random Access Response (RAR), or Msg2, on 112. On 113, the UE transmits a Shared Channel on Physical Uplink (PUSCH), or Msg3, to the gNB according to configuration information for PUSCH transmission conducted on the RAR. On 114, the gNB transmits a Contention Resolution Message, or Msg4, to the UE.

[008] In the 4-step random access procedure, as shown in Figure 1A, the resource, including time and frequency resource allocation, for PUSCH (i.e., Msg3) is indicated in the RAR (i.e., Msg2). In particular, the RAR contains an uplink allocation including a 14-bit “PUSCH frequency resource allocation” field indicating the frequency domain resource for PUSCH and a 4-bit “PUSCH time resource allocation” field indicating the time domain resource for PUSCH.

[009] There may be cases where multiple UEs select the same random access preamble and transmit the preamble on the same PRACH time / frequency resource. This preamble collision is called contention. One of the main purposes of applying Step 113 and Step 114 is to resolve such potential contention.

[0010] In order to minimize the number of channel accesses, which is important, for example, for operations in unlicensed frequency bands where Listen Before Transmission (LBT) is required before transmission, a 2-step random access procedure has also been proposed for NR. Instead of using the four steps 111~114, the 4-step random access procedure completes random access in just two steps with two messages, which can be referred to as Msg A and Msg B. Figure 1B shows a signaling sequence of a 2-step contention-based random access procedure, also referred to as Type 2 random access procedure in TS 38.213. As shown, Petition 870250088817, dated 09 / 30 / 2025, page 127 / 235 / 90, steps 101-102 in Figure 1B are the same as steps 101-102 in Figure 1A. In 121, the UE transmits a PRACH preamble and a PUSCH in one message (i.e., Message A, msgA) to the gNB. The PUSCH may include upper-layer data, such as a Radio Resource Control (RRC) connection request, possibly with some small additional payload. In 122, the gNB transmits Message B (msgB) to the UE, including UE identifier assignment, synchronization advance information, and contention resolution message (CRM), etc.

[0011] Figure 2A illustrates a contention-free random access of the 4-step random access type, and Figure 2B illustrates a contention-free random access of the 2-step random access type. As shown in Figure 2A, network node 104 assigns a preamble for CFRA in 4-step RACH, and as shown in Figure 2B, network node 104 assigns a preamble and PUSCH for CFRA in 2-step RACH. Network node 104 does not configure CFRA resources for both 4-step and 2-step RA types simultaneously for a Bandwidth Share (BWP). CFRA with 2-step RA type is only supported for pass-through transfer.

[0012] A 4-step type RA Msg1 includes only a preamble in PRACH, while a 2-step type RA MSGA includes a preamble in PRACH and a payload in PUSCH. After the transmission of Msg1 or the transmission of MSGA, UE 102 monitors a response from network node 104 in a configured window. For CFRA, upon receiving the network response, UE 102 terminates the random access procedure. PRACH configuration

[0013] In NR, the time and frequency resource in which a RACH preamble is transmitted is defined as a PRACH Occasion, RO.

[0014] The timing resources and process format for a PRACH preamble are configured by a RACH configuration index. Petition 870250088817, dated 09 / 30 / 2025, pages 128 / 235 / 90 For details of the PRACH configuration index, reference may be made to 3GPP TS38.211, which is incorporated herein by reference in its entirety. The PRACH configuration index indicates a row in a PRACH configuration table specified in TS 38.21, Tables 6.3.3.2-2, 6.3.3.2-3, 6.3.3.2-4 for FR1 (e.g., 450 MHz - 6 GHz) paired spectrum, FR1 unpaired spectrum, and FR2 (e.g., 24.25 GHz - 52.6 GHz) unpaired spectrum, respectively; a row in a PRACH configuration table specifies the time-domain PRACH occasion pattern for a PRACH configuration period. A PRACH configuration period may be 10, 20, 40, 80, or 160 ms.

[0015] In the frequency domain, NR supports multiple frequency-multiplexed RACH occasions within the same time-domain RACH occasion. This is primarily driven by NR's support for analog beam sweeping, such that RACH occasions associated with an SSB are configured in the same time instance but at different frequency locations. PRACH preambles can only be transmitted on the frequency resources given by the msglFrequencyStart upper-layer parameter. The frequency resource for PRACH occasions UraG{0,1,...,M-1}, where M equals the msglFDM upper-layer parameter, is numbered in ascending order in the initial active uplink bandwidth portion during initial access, starting from the lowest frequency. In other circumstances, ura is numbered in ascending order in the active uplink bandwidth portion, starting from the lowest frequency.The number M of PRACH occasions that are frequency-domain multiplexed (FDMed) into a time-domain RACH occasion can be 1, 2, 4, or 8.

[0016] Figure 3 illustrates an example of the PRACH occasion configuration in NR. As shown in Figure 3, four PRACH occasions are frequency-division multiplexed into one time instance. Petition 870250088817, dated 09 / 30 / 2025, pages 129 / 235 / 90

[0017] In NR Rel-17, there are up to 64 sequences that can be used as RACH preambles on RACH occasion in each cell. The RRC parameter totalNumberOfRA-Preambles determines how many of these 64 sequences are used as RACH preambles on RACH occasion in each cell. The 64 sequences are configured by first including all available cyclic shifts of a Zadoff-Chu root sequence and, second, in ascending root sequence index order, until 64 preambles are generated for the RACH occasion. NR Rel-17 Association between SSB and PRACH occasion

[0018] NR Rel-17 supports one-to-one, one-to-many, and many-to-one association between SSB and RACH instances.

[0019] The RACH preambles associated with each SSB are configured by two RRC parameters in RACH-ConfigCommon: ssbperRACH-OccasionAndCB-PreamblesPerSSB and totalNumberOfRAPreambles.

[0020] Figure 4 illustrates an example of the mapping between SSBs and RACH preambles, where the number of SSBs is 8, M = 32 (i.e., 2 SSBs per PRACH instance), the number of PRACH instances that are frequency division multiplexed into a time instance is 2. The PRACH format is A3, i.e., 2 TD PRACH instances per interval. The PRACH setup period is 20 ms, and there are 2 PRACH intervals per setup period.

[0021] For each SSB, the preambles associated on occasion Λ rtotal PRACH, preamble / N, are further divided into two sets for Contention-Based Random Access (CBRA) and Contention-Free Random Access (CFRA). The number of CB preambles per SSB on a PRACH occasion, R, is signaled by the RRC parameter ssb-perRACH-OccasionAndCBPreamblesPerSSB. Preamble indices for CBRA and CFRA are mapped consecutively to an SSB on a PRACH occasion. Petition 870250088817, dated 09 / 30 / 2025, pages 130 / 235 / 90

[0022] In 3GPP Rel-18, multiple PRACH transmissions are supported, where a UE transmits multiple PRACHs on a set of ROs for a single PRACH attempt. The UE and gNB need to be aligned on the specific set of ROs in order for the gNB to match them for a single PRACH attempt, and for the UE and gNB to determine the start of the RAR window, Random Access - Radio Network Temporary Identity (RA-RNTI), etc.

[0023] However, on the one hand, in NR, up to Rel-18, RO indexing is only specified for CFRA, and there is no specification on RO indexing for CBRA. On the other hand, RO indexing for CFRA is specified for three scenarios and will cause some problems or restrictions if applied in determining the UE of a set of ROs for multiple PRACH transmissions.

[0024] Furthermore, there may be problems when there are ROs overlapping time domains between legacy ROs and separate ROs. SUMMARY

[0025] One objective of the present application is to provide some RO indexing solutions for multiple PRACH transmissions, and solutions to address the problems when there are ROs overlapping time domains between legacy ROs and separate ROs.

[0026] According to a first aspect of the present description, a method at a terminal node for performing multiple Physical Random Access Channel (PRACH) transmissions for a single PRACH attempt is provided. The method includes: determining a number of PRACH transmissions based on a parameter received from a network node; determining a configured number K of PRACH transmissions; determining a number R of PRACH Occasions (ROs) associated with a selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions in an association period; determining an association period. Petition 870250088817, dated 09 / 30 / 2025, p. 131 / 235 / 90 extended, the extended association period including a number X of association periods, wherein the number X of association periods is the minimum number of association periods, such that X^R > K; determine, within the extended association period, a set of ROs for indexing, wherein an RO in the set of ROs is associated with the selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions; index the determined ROs in the set of ROs; and perform one or more PRACH transmissions based on the determined number of PRACH transmissions in the indexed set of ROs, wherein the number of ROs in the set is equal to the determined number of PRACH transmissions.

[0027] According to a second aspect of the present description, a terminal node is provided. The terminal node is configured to: determine a number of PRACH transmissions based on a parameter received from a network node; determine a configured number K of PRACH transmissions; determine a number R of PRACH Occasions, ROs, associated with a selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions in an association period; determine an extended association period, the extended association period including a number X of association periods, wherein the number X of association periods is the minimum number of association periods, such that X^R > K; determine, in the extended association period, a set of ROs for indexing, wherein an RO in the set of ROs is associated with the selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions;index the determined ROs in the set of ROs; and perform one or more PRACH transmissions based on the determined number of PRACH transmissions in the indexed set of ROs, where the number of ROs in the set is equal to the determined number of PRACH transmissions. Petition 870250088817, dated 09 / 30 / 2025, pages 132 / 235 / 90

[0028] According to a third aspect of the present description, a method on a network node for receiving multiple PRACH transmissions for a PRACH attempt from a terminal node is provided. The method includes: determining a number of PRACH transmissions; determining a configured number K of PRACH transmissions; determining a number R of PRACH Occasions, ROs, associated with a selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions in an association period; determining an extended association period, the extended association period including a number X of association periods, wherein the number X of association periods is the minimum number of association periods such that X^R > K;Determine, during the extended association period, a set of ROs for indexing, where an RO in the set of ROs is associated with the selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions; index the determined ROs in the set of ROs; and receive and associate the number of PRACH transmissions in the indexed set of ROs with a PRACH attempt, where the number of ROs in the set is equal to the determined number of PRACH transmissions.

[0029] According to a fourth aspect of the present description, a network node is provided. The network node is configured to: determine a number of PRACH transmissions; determine a configured number K of PRACH transmissions; determine a number R of PRACH Occasions, ROs, associated with the selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions in an association period; determine an extended association period, the extended association period including a number X of association periods, wherein the number X of association periods is the minimum number of association periods such that X^R > K; determine, within the association period Petition 870250088817, dated 09 / 30 / 2025, p. 133 / 235 / 90 extended, a set of ROs for indexing, wherein an RO in the set of ROs is associated with the selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions; index the determined ROs in the set of ROs; and receive and associate the number of PRACH transmissions in the indexed set of ROs with a PRACH attempt, wherein the number of ROs in the set is equal to the determined number of PRACH transmissions.

[0030] This description proposes an RO indexing solution for multiple PRACH transmissions to help UE and gNB align on the set of ROs, so that gNB can combine them for a PRACH attempt. This description also proposes a solution for PRACH transmission in the case where there is overlapping RO in the time domain between two PRACH configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1A shows a signaling sequence of a 4-step contention-based random access procedure.

[0032] Figure 1B shows a signaling sequence of a 2-step contention-based random access procedure.

[0033] Figure 2A illustrates a contention-free random access of the 4-step random access type.

[0034] Figure 2B illustrates a contention-free random access of the 2-step random access type.

[0035] Figure 3 illustrates an example of the RACH occasion configuration in NR.

[0036] Figure 4 illustrates an example of the mapping between SSB and RACH preambles.

[0037] Figure 5 is a diagram illustrating an exemplary telecommunications network in which UEs and gNB can be operated according to an embodiment of the present description. Petition 870250088817, dated 09 / 30 / 2025, pages 134 / 235 / 90

[0038] Figure 6 illustrates an index of the PRACH configuration in FR2 TDD.

[0039] Figure 7 is a flowchart illustrating an exemplary method at a terminal node for performing multiple PRACH transmissions for a PRACH attempt according to an embodiment of the present description.

[0040] Figure 8 is a flowchart illustrating an exemplary method at a network node for receiving multiple PRACH transmissions for a PRACH attempt from a terminal node according to an embodiment of the present description.

[0041] Figure 9A illustrates the results of the distribution of PRACH transmissions through ROs according to an embodiment of the present description.

[0042] Figure 9B illustrates the results of the distribution of PRACH transmissions through ROs according to another embodiment of the present description.

[0043] Figure 10A illustrates a scenario in which there are time-domain ROs overlapping between two PRACH configurations, and Figure 1B the scenario in which missing ROs are crossed out.

[0044] Figure 11 is a flowchart illustrating an exemplary method at a terminal node for performing PRACH transmission for a PRACH attempt according to an embodiment of the present description.

[0045] Figure 12A illustrates the results of applying one embodiment of the present application.

[0046] Figure 12B illustrates the results of applying another embodiment of the present application.

[0047] Figure 13 schematically shows one embodiment of an arrangement that can be used in a terminal node or a network node according to an embodiment of the present description.

[0048] Figure 14 is a block diagram of a terminal node. Petition 870250088817, dated 09 / 30 / 2025, page 135 / 235 / 90 copy according to a modality of the present description.

[0049] Figure 15 is a block diagram of an exemplary network node according to an embodiment of the present description.

[0050] Figure 16 is a block diagram of an exemplary terminal node according to an embodiment of the present description.

[0051] Figure 17 shows an example of a 1700 communication system according to some modalities.

[0052] Figure 18 shows a UE according to some modalities.

[0053] Figure 19 shows a UE according to some modalities.

[0054] Figure 20 is a block diagram of a 2000 host, which may be an embodiment of the 1716 host of Figure 17, according to several aspects described herein.

[0055] Figure 21 is a block diagram illustrating a 2100 virtualization environment in which the functions implemented by some modes can be virtualized.

[0056] Figure 22 shows a communication diagram of a host 2202 communicating via a network node 2204 with a UE 2206 through a partially wireless connection according to some modes. DETAILED DESCRIPTION

[0057] Next, the principle and spirit of the present description will be described in relation to illustrative embodiments. Some of the embodiments contemplated herein will now be described more fully in relation to the accompanying drawings. Other embodiments, however, are contained within the scope of the matter described herein; the matter described should not be interpreted as limited only to the embodiments presented herein; rather, these embodiments are provided by way of example to guide the scope of Petition 870250088817, dated 09 / 30 / 2025, pp. 136 / 235 / 90, subject to those versed in the technique. Additional information can also be verified in the following references: 1) 3GPP TS 38.213 V17.5.0 (2023-03), 2) 3GPP TS 38.321 V17.4.0 (2023-03), 3) 3GPP TS 38.211 V17.4.0 (2022-12), and 4) 3GPP TS 38.331 V17.4.0 (2023-03).

[0058] References in this descriptive report to “an embodiment”, “some embodiment”, “an example embodiment”, etc. indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that each embodiment includes the particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Additionally, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is understood that it is known to those skilled in the art to affect such aspect, structure, or characteristic in connection with other embodiments, whether or not explicitly described.

[0059] Those skilled in the art will realize that the term “exemplary” is used here to mean “illustrative,” or “serving as an example,” and is not intended to imply that one particular modality is preferred over another, or that a particular feature is essential. Likewise, the terms “first,” “second,” “third,” “fourth,” and similar terms are used simply to distinguish one particular instance of an item or feature from another, and do not indicate a particular order or arrangement unless the context clearly indicates otherwise. Additionally, the term “step,” as used here, is intended to be synonymous with “operation” or “action.” Any description given here of a sequence of steps does not imply that these operations must be performed in a particular order, or even that these operations Petition 870250088817, dated 09 / 30 / 2025, page 137 / 235 / 90 are carried out in any order whatsoever, unless the context or details of the operation described clearly indicate otherwise.

[0060] Conditional language used herein, such as “can”, “could”, “might”, “for example” and the like, unless specifically stated otherwise, or otherwise understood in the context used, is generally intended to convey that certain modalities include, while other modalities do not include, certain features, elements and / or states. Thus, such conditional language is not intended to generally imply that features, elements and / or states are in any way required for one or more modalities or that one or more modalities necessarily include logic to decide, with or without input or stimulus to the author, whether these features, elements and / or states are included or must be realized in any particular modality.Also, the term “or” is used in its inclusive sense (and not in its exclusive sense), so that, when used, for example, to connect a list of elements, the term “or” means one, some, or all of the elements in the list. Additionally, the term “each,” as used here, besides having its ordinary meaning, can mean any subset of a set of elements to which the term “each” is applied.

[0061] The terminology used here is for the purpose of describing particular modalities only, and is not intended to be a limitation of the modalities exemplified. As used here, the singular forms “a”, “an”, “the” and “the” are intended to also include the plural forms, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises”, “comprising”, “has”, “having”, “includes” and / or “including”, when used here, specify the presence of stated features, elements and / or components, etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof. It will also be Petition 870250088817, dated 09 / 30 / 2025, page 138 / 235 / 90, it is understood that the terms “connect”, “connecting”, “connected”, etc., when used here, only mean that there is an electrical or communicative connection between two elements, and they can be connected either directly or indirectly, unless explicitly stated otherwise.

[0062] Certainly, the present description can be carried out in specific ways different from those presented here without departing from the scope and essential characteristics of the description. One or more of the specific processes discussed below can be performed in any electronic device comprising one or more appropriately configured processing circuits, which may, in some exemplary embodiments, be incorporated into one or more application-specific integrated circuits (ASICs). In some exemplary embodiments, these processing circuits may comprise one or more microprocessors, microcontrollers, and / or digital signal processors programmed with appropriate software and / or embedded software to perform one or more of the above-described operations, or variants thereof. In some exemplary embodiments, these processing circuits may comprise custom hardware to perform one or more of the above-described functions.The present options, therefore, should be considered, in all respects, as illustrative and not restrictive.

[0063] Although multiple embodiments of the present description are illustrated in the accompanying drawings and described in the following detailed description, it is understood that the description is not limited to the embodiments described, but instead is also capable of numerous rearrangements, modifications and substitutions without departing from the present description which will be presented and defined in the claims.

[0064] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein are Petition 870250088817, dated 09 / 30 / 2025, p. 139 / 235 / 90 has the same meaning commonly understood by those versed in the technique to which this description pertains.

[0065] The techniques described herein can be used for various wireless communication networks, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), Long Term Evolution (LTE), New Radio (NR), and other networks developed in the future. The terms "network" and "system" are sometimes used interchangeably. For illustration purposes only, certain aspects of the techniques are described below for 5th Generation wireless communication networks. However, it will be perceived by those skilled in the art that the techniques described herein can also be used for other wireless networks, such as LTE and corresponding radio technologies mentioned herein, as well as wireless networks and radio technologies proposed in the future.

[0066] A type of communication device is a wireless communication device, which can be any type of wireless device that has access to (i.e., is served by) a wireless network (e.g., a cellular network). Some examples of a wireless communication device include, but are not limited to: a User Equipment (UE) device on a 3GPP network, a Machine-Type Communication (MTC) device, and an Internet of Things (IoT) device.

[0067] As used herein, the term “UE” may be, by way of example and without limitation, a User Equipment (UE), a Subscriber Station (SS), a Portable Subscriber Station (PSS), a Mobile Station (MS), a Mobile Terminal (MT) or an Access Terminal (AT). The UE may include, but is not limited to, mobile phones, cell phones, smartphones, or personal digital assistants (PDAs). Petition 870250088817, dated 09 / 30 / 2025, page 140 / 235 / 90 portable computers, image capture terminal devices, such as digital cameras, gaming terminal devices, music storage and playback applications, wearable terminal devices, vehicle-mounted wireless terminal devices and the like. In the following description, the terms “EU”, “wireless communication device”, “terminal device”, “mobile terminal” and “user equipment” may be used interchangeably.

[0068] As used here, a “network node” is any node that is either part of the radio access network or the core network of a cellular communications network / system.

[0069] Figure 5 is a diagram illustrating an exemplary telecommunications network 10 in which UE No. 1 100-1, UE No. 2 100-2, and gNB 105 can be operated according to an embodiment of the present description. Although the telecommunications network 10 is a network defined in the context of 5G NR, the present description is not limited to it.

[0070] As shown in Figure 5, network 10 may comprise one or more UEs 100-1 and 100-2 (collectively, UE(s) 100) and a RAN 105 node, which may be a base station, a Node B, an evolved Node B (eNB), a gNB, or an AN node that provides UEs 100 with network access. Additionally, network 10 may comprise its core network portion which is not shown in Figure 5.

[0071] However, the present description is not limited to it. In some other embodiments, the network 10 may comprise additional nodes, fewer nodes, or some variants of the existing nodes shown in Figure 5. For example, in a network with a 4G architecture, the entities (e.g., an eNB) that perform these functions may be different from those (e.g., the gNB 105) shown in Figure 5. As another example, in a network with a mixed 4G / 5G architecture, some of the entities may be the same as those shown in Figure 5, and others may be different. Petition 870250088817, dated 09 / 30 / 2025, p. 141 / 235 / 90

[0072] Additionally, although two UEs 100 and one gNB 105 are shown in figure 5, the present description is not limited to them. In some other embodiments, any number of UEs and / or any number of gNBs may be included in the network 10.

[0073] As shown in Figure 5, the UEs 100 can be communicatively connected to the gNB 105 which, in turn, can be communicatively connected to a corresponding Central Network (CN) and then to the Internet, in such a way that the UEs 100 can finally communicate their user-plane data with other devices outside the network 10, for example, via the gNB 105.

[0074] In 3GPP Rel-18, multiple PRACH transmissions are provided, where a UE transmits multiple PRACHs in a set of ROs (PRACH occasions) for a PRACH attempt. The UE and gNB need to be aligned on the specific set of ROs in order for the gNB to match them for a PRACH attempt and for the UE and gNB to determine the start of the RAR, RA-RNTI, etc. window. A simple solution for the UE to determine a set of ROs is based on the RO index. As an example of K PRACH transmissions, the initial RO index can be determined as mod(initial RO index, K)=0. It can be observed that RO indexing is necessary to support the UE's determination of ROs for multiple PRACH transmissions. However, on the one hand, in NR up to Rel-18, RO indexing is only specified for CFRA, and there is no specification on RO indexing for CBRA.On the other hand, the indexing of ROs to CFRA is specified for the following three scenarios and will cause some problems or restrictions if applied in the EU's determination of a set of ROs for multiple PRACH transmissions. Reasons and related clauses are as follows.

[0075] - Scenario 1: RO indexing is limited in 1 / N instances Valid consecutive PRACH passes per SSB, provided that a UE is provided. Petition 870250088817, dated 09 / 30 / 2025, page 142 / 235 / 90 number N of SS / PBCH blocks associated with a PRACH occasion and N<1

[0076] - Scenario 2: RO indexing for SI request is within an association period.

[0077] - Scenario 3: If csirs-ResourceList is provided, indexing of RO is adjusted based on the standard membership period.

[0078] Some related part in 3GPP TS38.213 v17.4.0 is quoted here as follows. A membership period, starting from frame 0, for mapping SS / PBCH block indices to PRACH occasions is the smallest value in the set determined by the PRACH configuration period according to Table 8.1-1, such that SS / PBCH block indices are mapped at least once to PRACH occasions in the membership period, where a UE obtains this from the value of ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon. If, after an integral number of mapping cycles of SS / PBCH block indices to PRACH occasions in the membership period, there is a set of PRACH occasions or PRACH preambles that are not mapped to SS / PBCH block indices, no SS / PBCH block index is mapped to the set of PRACH occasions or PRACH preambles. A standard association period includes one or more association periods and is determined so that a pattern between the PRACH occasions and the SS / PBCH block indices repeats at most every 160 ms.PRACH occasions not associated with SS / PBCH block indices after a whole number of association periods, if any, are not used for PRACH transmissions. For a PRACH transmission by a UE triggered by a PDCCH order, the PRACH mask index field [5, TS 38.212], if the value of the random access preamble index field is not zero, indicates the Petition 870250088817, dated 09 / 30 / 2025, page 143 / 235 / 90 occasion PRACH for the transmission of PRACH where the PRACH occasions are associated with the SS / PBCH block index indicated by the SS / PBCH block index field of the PDCCH order. [omitted] For a PRACH transmission triggered by upper layers, if ssbResourceList is provided, the PRACH mask index is indicated by rassb-OccasionMaskIndex, which indicates the PRACH occasions for the PRACH transmission where the PRACH occasions are associated with the selected SS / PBCH block index. PRACH occasions are mapped consecutively by corresponding SS / PBCH block index. The PRACH occasion indexing indicated by the mask index value is readjusted by mapping cycle of consecutive PRACH occasions by SS / PBCH block index. The UE selects for a PRACH transmission the PRACH occasion indicated by the PRACH mask index value for the SS / PBCH block index indicated in the first available mapping cycle. For the indicated preamble index, the ordering of PRACH occasions is - first, in ascending order of frequency feature indices for frequency-multiplexed PRACH occasions - second, in ascending order of time resource indices for time-multiplexed PRACH occasions within a PRACH interval - third, in ascending order of indices for PRACH intervals For a PRACH transmission triggered by a request from higher layers, a value of ra-OccasionList [12, TS 38.331], if csirsResourceList is provided, indicates a list of PRACH occasions for the PRACH transmission where the PRACH occasions are associated with the selected CSI-RS index indicated by csi-RS. The indexing of the PRACH occasions indicated by ra-OccasionList is reset periodically. Petition 870250088817, dated 09 / 30 / 2025, page 144 / 235 / 90 standard association. Table 1: Table 8.1-1: Mapping between configuration period of PRACH and SS / PBCH block for the PRACH membership period. PRACH setup period (msec) Membership period (number of PRACH setup periods) 10 {1, 2, 4, 8, 16} 20 {1, 2, 4, 8} 40 {1, 2, 4} 80 {1, 2} 160 {1}

[0079] Some related part in 3GPP TS38.321 v17.2.0 is quoted here as follows. ra-ssb-OccasionMaskIndex: defines PRACH occasion(s) associated with an SSB in which the MAC entity can transmit a random access preamble (see clause 7.4); 1> Otherwise, if an SSB was previously selected: 2> determine the next available PRACH occasion from the PRACH occasions corresponding to the selected SSB allowed by the constraints given by ra-ssb-OccasionMaskIndex if configured, or ssbSharedRO-MaskIndex if configured, or indicated by PDCCH (the MAC entity must select a PRACH occasion randomly with equal probability among the consecutive PRACH occasions according to clause 8.1 of TS 38.213 [6], regardless of the FR2 UL gap, corresponding to the selected SSB; the MAC entity may take into account possible measurement occurrence gaps and MUSIM gaps during the determination of the next available PRACH occasion corresponding to the selected SSB). 1> Otherwise, if a CSI-RS was previously selected: 2> If there is no contention-free Random Access Resource associated with the selected CSI-RS: 3> Determine the next available PRACH occasion from the PRACH occasions allowed by the restrictions given by ra-ssb. Petition 870250088817, dated 09 / 30 / 2025, page 145 / 235 / 90 OccasionMaskIndex if configured, corresponding to the SSB in candidateBeamRSList that is quasi-colocalized with the selected CSI-RS, as specified in TS 38.214 [7] (the MAC entity must select a PRACH occasion randomly with equal probability among consecutive PRACH occasions according to clause 8.1 of TS 38.213 [6] regardless of the FR2 UL gap, corresponding to the SSB that is quasi-colocalized with the selected CSI-RS; the MAC entity may take into account possible measurement occurrence gaps and MUSIM gaps when determining the next available PRACH occasion corresponding to the SSB that is quasi-colocalized with the selected CSI-RS). Table 2: Table 7.4-1: PRACH mask index values PRACH Mask Index / msgA-SSB-SharedRO-MaskIndex PRACH Occasion(s) Allowed for SSB 0 All 1 PRACH Occasion Index 1 2 PRACH Occasion Index 2 3 PRACH Occasion Index 3 4 PRACH Occasion Index 4 5 PRACH Occasion Index 5 6 PRACH Occasion Index 6 7 PRACH Occasion Index 7 8 PRACH Occasion Index 8 9 All even PRACH occasions 10 All odd PRACH occasions 11 Reserved 12 Reserved 13 Reserved 14 Reserved 15 Reserved

[0080] Some related part in 3GPP TS38.331 v17.4.0 is cited here as follows. SI-RequestConfig information element - - ASN1START - - TAG-SI-REQUESTCONFIG-START SI-RequestConfig ::= SEQUENCE { rach-OccasionsSI SEQUENCE { rach-ConfigSI RACH-ConfigGeneric, Petição 870250088817, de 30 / 09 / 2025, pág. 146 / 235 / 90 ssb-perRACH-Occasion ENUMERATED {oneEighth, oneFourth, oneHalf, one, two, four, eight, sixteen}} OPTIONAL, -- Need R si-RequestPeriod ENUMERATED {one, two, four, six, eight, ten, twelve, sixteen} OPTIONAL, -- Need R si-RequestResources SEQUENCE (SIZE (1..maxSI-Message)) OF SIRequestResources} SI-RequestResources ::= SEQUENCE { ra-PreambleStartIndex INTEGER (0..63), ra-AssociationPeriodIndex INTEGER (0..15) OPTIONAL, -- Need R ra-ssb-OccasionMaskIndex INTEGER (0..15) OPTIONAL -- Need R} - - TAG-SI-REQUESTCONFIG-STOP - - ASN1STOP

[0081] According to the definition in 3GPP TS38.213, an association period is the smallest time interval among those supported for at least one SS / PBCH block index mapping cycle for PRACH occasions. For example, as shown in Figure 6 for the PRACH configuration index 127 in FR2 TDD, if SCS is 120 KHz, there are 8 ROs in a PRACH configuration period of 10 ms.

[0082] For multiple PRACH Rel-18 transmissions, it was agreed that “For multiple PRACH transmissions with the same beam, at least ROs located in different time instances may be used for the transmissions”. In other words, multiple time-domain multiplexed PRACH transmissions are supported. For simplicity, if there are multiple FDMed ROs associated with an SSB, only one of them is considered in a time instance.

[0083] Some considerations will be made, for example: Petition 870250088817, dated 09 / 30 / 2025, page 147 / 235 / 90 There are two SSBs, SSB1 and SSB2; - onehalf is provided by ssb-perRACH-OccasionAndCBPreamblesPerSSB, indicating that one SSB is associated with two ROs.

[0084] The SSB to RO mapping is shown in Table 1. There are four ROs associated with an SSB during the association period, and two of these ROs are consecutive. According to CFRA RO indexing scenario 1, the RO index is up to two. The four ROs associated with an SSB have corresponding indices of 0, 1, 0, 1, if the index starts from 0. Indeed, if the four ROs have indices of 0~3, they can be used for the first, second, third, and fourth PRACH transmissions of a RACH attempt. But, with indices of 0 and 1, it is unclear how to support a number of PRACH transmissions greater than 2.

[0085] Since the ROs in the PRACH setup period are sufficient for at least one SSB-RO mapping cycle, the association period is 10 ms. For a selected SSB, for example, SSB No. 1, an association period consists of two sets of ROs for two PRACH transmissions and one set of ROs for four PRACH transmissions, but the same cannot accommodate a set of ROs for eight transmissions, which, under other circumstances, can be supported by ROs in two association periods. In short, one observation is that it is beneficial for multiple PRACH transmissions from a single RACH attempt to encompass multiple association periods, which exceeds the range of CFRA RO indexing scenario 2. Table 1: Mapping of SS / PBCH block indices for PRACH occasions with two SSBs____________________________________________________ RO index in a PRACH configuration period 0 1 2 3 4 5 6 7 Associated SSB index 1 1 2 2 1 1 2 2

[0086] Finally, if a set of ROs for multiple PRACH transmissions from a RACH attempt spans X periods of Petition 870250088817, dated 09 / 30 / 2025, page 148 / 235 / 90 association, where the number of ROs associated with an SSB is sufficient for a number of PRACH transmissions, the value of X is determined based on the number of PRACH transmissions. In contrast, the number of association periods in a standard association period in scenario 3 is based on SSB periodicity. If the time interval of X association periods is greater than a standard association period, the CFRA RO indexing method in scenario 3 will cause the same problem mentioned above for scenario 1.

[0087] The RO group was discussed in RAN1 No. 112 with an agreement, the related part of which is quoted below. Work Consideration For multiple PRACH transmissions on the same Tx beam, to differentiate multiple PRACH transmissions from a single PRACH transmission, it is at least supported that multiple PRACHs are transmitted on separate ROs. • Note: Separate RO means that the RO is separate with single PRACH transmission. • FFS: if the Rel-17 structure of the feature combination (FeatureCombination-r17) and additional RACH configuration (AdditionalRACH-Config-r17) can be reused for multiple PRACH transmissions Rel-18 to perform the corresponding partitioning of the PRACH resource. Agreement For multiple PRACH transmissions with the same Tx beam, an “RO group” is considered to be multiple PRACH transmissions with separate preambles in shared ROs and / or multiple PRACH transmissions in separate ROs, and an RO group consists of valid RO(s) for a specific number of multiple PRACH transmissions. Note 1: All ROs in a RO group are associated with the Petition 870250088817, dated 09 / 30 / 2025, p. 149 / 235 / 90 same SSB(s). Note 2: Shared or separate RO / preamble means that the RO / preamble are shared or separate with single PRACH transmission. Note 3: Whether / how to define “RO group” in the descriptive report will be discussed separately. Note 4: Valid RO(s) refers to what is defined in the existing specification. FFS: If and how to address collisions between valid ROs for multiple PRACH transmissions and other existing ROs for legacy single PRACH transmissions or other resources, for example, 2-stage PRACH. FFS: The time interval of the RO group. FFS: If and how ROs can be shared between different RO groups for different numbers of multiple PRACH transmissions. FFS: other details

[0088] Since it is still open whether a group of ROs consists of ROs for multiple PRACH transmissions for a single RACH attempt or multiple RACH attempts, in this IvD, the term 'a set of ROs' is used to refer to the ROs associated with an SSB for the multiple PRACH transmissions of a RACH attempt.

[0089] It was also agreed RAN1 No. 112 that a gNB can configure more than {2, 4, 8} as the possible multiple PRACH transmission numbers. It is FFS how to differentiate PRACH resources between the different numbers. For example, a gNB can configure separate preamble partitions in a RO or separate ROs for different PRACH transmission numbers. Still other methods are not yet prevented, for example, different PRACH transmission numbers are configured in a preamble partition. Petition 870250088817, dated 09 / 30 / 2025, pages 150 / 235 / 90 Agreement Support {2, 4, 8} for the number of multiple PRACH transmissions with the same Tx beams. Agreement For multiple PRACH transmissions with the same Tx beam, gNB can configure one or multiple values ​​for the number of multiple PRACH transmissions. • If multiple values ​​are configured, differentiation of PRACH resources between multiple PRACH transmissions with a different number of multiple PRACH transmissions is supported. • FFS: details

[0090] Regardless of the gNB configuration, a common understanding is that an UE, which determines a specific number of PRACH transmissions, only transmits PRACH on ROs with a preamble partition applicable to its determined number. A general approach for counting and indexing ROs is that an UE only counts ROs with a preamble partition applicable to its determined number of PRACH transmissions. In other words, ROs without a preamble for the UE-determined number of PRACH transmissions are not counted for indexing.

[0091] If an association period does not have enough ROs associated with a particular number of PRACH transmissions, which is configured by gNB, a UE targeting this number of PRACH transmissions will search for ROs in at least several association periods for a RACH attempt. A minimum of X association periods provides ROs associated with the selected SSB, where the total number of such ROs is equal to or greater than the number of PRACH transmissions in a RACH attempt. X > 1. For example, according to Table 1, a UE determines two association periods for 8 PRACH transmissions, one Petition 870250088817, dated 09 / 30 / 2025, p. 151 / 235 / 90 association period for 4 PRACH transmissions and one of the two sets of ROs in an association period for 2 PRACH transmissions. Equal to an association period, the X association periods also start from radio frame 0.

[0092] Next, a rule for counting RO and indexing RO and a method for determining X and indexing RO are provided. Based on these, a UE can determine a set of ROs for a RACH attempt.

[0093] Figure 7 is a flowchart of an exemplary method 700 on a terminal node for performing multiple PRACH transmissions for a PRACH attempt according to an embodiment of the present description. The method 700 can be performed on a terminal node (e.g., UE 100). The method 700 may comprise steps S710 ~ S740. However, the present description is not limited to the same. In some other embodiments, the method 700 may comprise more steps, fewer steps, different steps, or any combination thereof. Additionally, the steps of the method 700 may be performed in a different order than that described herein. Furthermore, in some exemplary embodiments, a step in the method 700 may be divided into multiple substeps and performed by different entities, and / or multiple steps in the method 700 may be combined into a single step.

[0094] Method 700 can start at step S710, where it determines a number of PRACH transmissions based on a parameter received from a network node. The network node can configure one or more candidate numbers for the number of PRACH transmissions. For example, the network node can configure {2, 4, 8} as the number of PRACH transmissions. The terminal node can determine one of the configured numbers itself. For example, in the CBRA case, the terminal node can determine the number of PRACH transmissions by its SSB measurement. Petition 870250088817, dated 09 / 30 / 2025, page 152 / 235 / 90

[0095] In step S720, the terminal node determines a group of ROs for indexing, where an RO in the group of ROs is associated with a selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions.

[0096] Then, in step S730, the ROs in the group of ROs determined in step S720 are indexed.

[0097] Finally, in step S740, the terminal node performs one or more PRACH transmissions based on the determined number of PRACH transmissions in a set of indexed ROs, where the number of ROs in the set is equal to the determined number of PRACH transmissions. The terminal node first determines a group of ROs, i.e., candidate ROs to perform the PRACH transmissions, and then selects a set of ROs from the group to actually perform the PRACH transmissions.

[0098] In one embodiment, if the number of PRACH transmissions are time-domain multiplexed and, if there are multiple frequency multiplexing ROs associated with the selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions, one of the multiple ROs in a time instance is determined.

[0099] In one embodiment, if at least part of the number of PRACH transmissions are frequency-domain multiplexed, the S720 step of determining a group of ROs for indexing may comprise a step of determining a number of ROs that are frequency-domain multiplexed, with the number being equal to the number of simultaneous frequency-domain multiplexed PRACH transmissions.

[00100] In one embodiment, method 700 may additionally comprise: a step of determining a configured number K of PRACH transmissions; a step of determining a number R of ROs associated with the selected SSB and with a preamble partition. Petition 870250088817, dated 09 / 30 / 2025, p. 153 / 235 / 90 applicable to the determined number of PRACH transmissions in an association period; and, if the R number is less than the K number, a step to determine an extended association period that includes a minimum number X of association periods, wherein a number of ROs associated with the selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions in the X association periods is greater than or equal to the configured determined K number, and wherein the S720 determination step and the S730 indexing step of a group of ROs are performed in the extended association period.

[00101] In one embodiment, if the R number is greater than or equal to the K number, the X number is determined as 1, and the S720 determination step and the S730 indexing step of a group of ROs are performed in one association period.

[00102] In one embodiment, the number K is the determined number of PRACH transmissions, or a larger number of the multiple numbers of PRACH transmissions configured by the network node.

[00103] In one embodiment, method 700 may further comprise: a step of determining a first frame of a first association period of the extended association period as an initial radio frame of the extended association period, and a frame immediately after the end of the extended association period as an initial radio frame of an extended association period close to the extended association period.

[00104] In one embodiment, if the number of ROs in the RO group during the extended membership period is greater than the determined number of PRACH transmissions, the S740 step of performing one or more PRACH transmissions based on the determined number of PRACH transmissions in the indexed RO set may comprise a step of performing the one or more PRACH transmissions in a first number Petition 870250088817, dated 09 / 30 / 2025, page 154 / 235 / 90 of ROs in the indexed ROs, the first number being equal to the number of one or more PRACH transmissions, and a step of repeating a PRACH transmission from one or more PRACH transmissions in the remaining ROs in the indexed ROs.

[00105] In one embodiment, if the number of ROs in the RO group in the extended membership period is greater than the number of PRACH transmissions, the S740 step of performing one or more PRACH transmissions based on the determined number of PRACH transmissions in the indexed RO set may comprise a step of performing the one or more PRACH transmissions by distributing the one or more PRACH transmissions across the RO group, such that a pattern of used ROs spreading across each of the X membership periods is the same.

[00106] In one embodiment, the S740 step of performing one or more PRACH transmissions based on the determined number of PRACH transmissions in the indexed RO set may comprise a step of determining a transmission pattern for the one or more PRACH transmissions, and a step of performing the one or more PRACH transmissions by following the transmission pattern.

[00107] In one mode, the transmission pattern is identified by the frame number.

[00108] Figure 8 is a flowchart of an exemplary 800 method on a network node for receiving multiple PRACH transmissions for a PRACH attempt from a terminal node according to an embodiment of the present description. The 800 method can be implemented on a network node (e.g., gNB 105). The 800 method may comprise steps S810 ~ S840. However, the present description is not limited to the same. In some other embodiments, the 800 method may comprise more steps, fewer steps, different steps, or any combination thereof. Petition 870250088817, dated 09 / 30 / 2025, pp. 155 / 235 / 90 same. Additionally, the steps of method 800 may be performed in a different order than that described here. Additionally, in some exemplary embodiments, a step in method 800 may be divided into multiple substeps and performed by different entities, and / or multiple steps in method 800 may be combined into a single step.

[00109] Method 800 can start at step S810, where it determines a number of PRACH transmissions.

[00110] In step S820, the network node determines a group of ROs for indexing, where an RO in the group of ROs is associated with a selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions.

[00111] Then, in step S830, the ROs in the group of ROs determined in step S820 are indexed.

[00112] Finally, in step S840, the network node receives and associates the number of PRACH transmissions into a set of indexed ROs, where the number of ROs in the set is equal to the determined number of PRACH transmissions. The network node first determines a group of ROs, i.e., candidate ROs to receive the PRACH transmissions, and then selects a set of ROs from that group to actually receive the PRACH transmissions.

[00113] In one embodiment, if the number of PRACH transmissions are time-domain multiplexed and if there are multiple frequency multiplexing ROs associated with the selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions, one of the multiple ROs in a time instance is determined.

[00114] In one embodiment, if at least part of the number of PRACH transmissions are frequency-domain multiplexed, the S820 step of determining a group of ROs for indexing may comprise a step of determining a number of ROs that are Petition 870250088817, dated 09 / 30 / 2025, page 156 / 235 / 90 multiplexed in frequency domain, with the number being equal to the number of simultaneous multiplexed PRACH transmissions in frequency domain.

[00115] In one embodiment, method 800 may further comprise: a step of determining a configured number K of PRACH transmissions; a step of determining a number R of ROs associated with the selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions in an association period; and, if the number R is less than the number K, a step of determining an extended association period that includes a minimum number X of association periods, wherein the number of ROs associated with the selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions in the X association periods is greater than or equal to the determined configured number K, and wherein the S820 determination step and the S830 indexing step of a group of ROs are performed in the extended association period.

[00116] In one embodiment, if the R number is greater than or equal to the K number, the X number is determined as 1, and the S820 determination step and the S830 indexing step of a group of ROs are performed in one association period.

[00117] In one embodiment, the number K is the determined number of PRACH transmissions, or a larger number of the multiple numbers of PRACH transmissions configured by the network node.

[00118] In one embodiment, method 800 may further comprise: a step of determining a first frame of a first membership period of the extended membership period as an initial radio frame of the extended membership period, and a frame immediately after the end of the extended membership period as an initial radio frame of an extended membership period close to the period of Petition 870250088817, dated 09 / 30 / 2025, page 157 / 235 / 90 extended association.

[00119] In one embodiment, if the number of ROs in the RO group during the extended association period is greater than the determined number of PRACH transmissions, the S840 step of receiving and associating the number of PRACH transmissions in the indexed RO set may comprise a step of receiving the number of PRACH transmissions in a first number of ROs in the indexed ROs, the first number being equal to the number of PRACH transmissions, and a step of receiving a repetition of one of the number of PRACH transmissions in the remaining ROs in the indexed ROs.

[00120] In one embodiment, if the number of ROs in the RO group in the extended association period is greater than the number of PRACH transmissions, the S840 step of receiving and associating the number of PRACH transmissions in the indexed RO set may comprise a step of receiving the number of PRACH transmissions that are distributed across the RO group, wherein a pattern of ROs used spreading across each of the X association periods is the same.

[00121] In one embodiment, the S840 step of receiving the number of PRACH transmissions in the indexed RO set may comprise a step of determining a transmission pattern for the number of PRACH transmissions, and a step of receiving the number of PRACH transmissions by following the transmission pattern.

[00122] In one mode, the transmission pattern is identified by the frame number.

[00123] Below are some methods for indexing ROs, so that the EU can determine a set of ROs for a PRACH attempt. Obviously, the present application is not limited to these.

[00124] Modality 1, among the ROs associated with an SSB in the X association periods, if there are multiple FDMed ROs associated with a Petition 870250088817, dated 09 / 30 / 2025, pp. 158 / 235 / 90 In a given instance, one or more of the following may be used.

[00125] For PRACH transmissions that have passed through TDM, only one of the FDMed ROs in a given instance is counted for RO indexing and indexed.

[00126] For PRACH transmissions where some or all are frequency-domain multiplexed, the number of FDMed ROs counted for RO indexing and indexed is equal to the number of simultaneous frequency-domain multiplexed PRACH transmissions. For example, a UE with two Tx chains can transmit two PRACHs simultaneously on a total of two FDMed ROs. If more than two FDMed ROs are associated with the selected SSB, the UE counts two of them for RO indexing and then indexes them.

[00127] Mode 2, for a selected SSB and a number of PRACH K transmissions, a UE follows one or more of the following steps to determine X Ros of membership periods and indices.

[00128] 1> Determine R, the number of ROs associated with the selected SSB in an association period based on the counting rule in Mode 1

[00129] 2> if R>K, X=1.

[00130] 2> if R<K, determinar X (X> 1) the minimum number of association periods such that the number of ROs associated with the selected SSB in the X association periods is not less than K

[00131] 3> determine the initial radio frame of the X association periods such that mod(initial frame index, X*number of frames in an association period)=0. In other words, the first X association periods start from frame 0, and the next X association periods start immediately after the end of the previous ones, etc.

[00132] 1> Index the ROs associated with the selected SSB in the X period(s) of association based on the indexing rule of Modality 1 (Already Petition 870250088817, dated 09 / 30 / 2025, p. 159 / 235 / 90, which states that the X association periods span the time frame, with FDMed ROs associated with an SSB, the rule in Mode 1 is to ensure that only the counted ROs are indexed.

[00133] A sub-modality of Modality 2, provided that a gNB can configure multiple candidate numbers of multiple PRACH transmissions, one or more of the following can be used to determine K, the number of PRACH transmissions, which is used to determine X, the number of membership periods.

[00134] - Option 1, K is the same determined number of PRACH transmissions

[00135] - Option 2, K is the larger number of multiple transmissions of PRACH configured by gNB.

[00136] If a gNB configures {2, 4, 8} as the number of PRACH transmissions, also known as the PRACH repetition factor, a UE can determine one of the same for itself for CBRA or be configured with a repetition factor for CFRA. With Option 1, X is UE-specific and specific to a PRACH repetition factor. There can be three X values ​​corresponding to the three configured PRACH repetition factors. Conversely, Option 2 will result in a cell-specific X, the same for all UEs. The highest RO index with Option 2 may be higher than Option 1, but Option 2 may be simpler for standardization and implementation.

[00137] When the determined number of PRACH transmissions is greater than the number of RO groups associated with the selected SSB in an association period, the UE sends a subset of the transmissions in the first association period. Any remaining transmissions will be sent in the next association period(s) in the same set of ROs. In one mode, if the PRACH transmissions are less than the existing ROs in the RO group or association period with the Petition 870250088817, dated 09 / 30 / 2025, page 160 / 235 / 90, with the closest possible combination of transmissions (e.g., 4 transmissions distributed across 3+3 ROs), the number of PRACH transmissions can either be increased to encompass all ROs in the RO group, or transmit only the determined number, K. In one example, the determined transmissions are 4, but the RO group across two membership periods has 6 ROs. The UE in this example sends more transmissions than determined to use all ROs in the RO group.

[00138] The distribution of PRACH transmissions through ROs can be done in numerous ways, for example: - The same RO (Reference Order) should be used in the X association periods, as shown in Figure 9A; - each RO in the X association periods must be used, as shown in figure 9B.

[00139] In another mode, RO groups allow only a combination of two multiple transmission patterns, and the pattern is identified by the frame number. Both 8 and 4 transmissions will be allowed for transmission across two RO groups of 4 ROs, but only 4 transmissions will be allowed, for example, even frame numbers. This will enable gNB to know that transmissions in the RO group with odd frame numbers are associated with an equal number of transmissions in the previous or next association period. This will also increase the chance of detecting at least a subset of the multiple PRACH transmissions. As a sub-mode, the UE encompassing association periods selects even or odd preambles to indicate whether the transmission is made as a series of the first half or the last half, see Table 3 below: Table 3: Selection of preambles Odd number of frames. Even preamble. This is the first part of a series of transmissions. Odd preamble. This is the last part of a series of transmissions. Petition 870250088817, dated 09 / 30 / 2025, p. 161 / 235 / 90

[00140] This will help gNB detect multiple PRACH transmissions, as it will know which sets of PRACH transmissions to match. ROs overlapping time domain between two RACH configurations

[00141] Another problem that is being addressed is the overlapping time domain of ROs between legacy ROs and separate ROs. This is a legacy problem that starts with 2-stage RACH in Rel-16. For any feature that requires early UE indication by PRACH, its configured ROs may collide with legacy ROs for single PRACH transmission or with separate ROs configured for another feature. If the overlapping ROs are associated with different SSBs, gNB in ​​FR2 with analog beamforming is unable to receive PRACH transmissions with different SSB beams.

[00142] Take the example of legacy single PRACH transmission and multiple PRACH Rel-18 transmissions. A working consideration made in RAN1 No. 112 is that separate ROs can be configured by gNB for multiple PRACH transmissions. For example, separate ROs can be configured with the AdditionalRACH-Config-r17 IE. According to 38.331 v17.4.0, ssb-perRACH-OccasionAndCB-PreamblesPerSSB and msg1-FrequencyStart are independently configured for additional ROs. - ASN1START -- TAG-BWP-UPLINKCOMMON-START BWP-UplinkCommon ::= SEQUENCE { genericParameters BWP, rach-ConfigCommon SetupRelease { RACH-ConfigCommon} ... omitted... AdditionalRACH-ConfigList-r17 ::= SEQUENCE (SIZE(1..maxAdditionalRACH-r17)) OF AdditionalRACH-Config-r17 Petition 870250088817, dated 09 / 30 / 2025, pages 162 / 235 / 90 AdditionalRACH-Config-r17 ::= SEQUENCE { rach-ConfigCommon-r17 RACH-ConfigCommon OPTIONAL, -- Need R msgA-ConfigCommon-r17 MsgA-ConfigCommon-r16 OPTIONAL, -Need R ...} NumberOfMsg3-Repetitions-r17::= ENUMERATED {n1, n2, n3, n4, n7, n8, n12, n16} -- TAG-BWP-UPLINKCOMMON-STOP -- ASN1STOP RACH-ConfigCommon ::= SEQUENCE { rach-ConfigGeneric RACH-ConfigGeneric, totalNumberOfRA-Preambles INTEGER (1..63) OPTIONAL, -- Need S ssb-perRACH-OccasionAndCB-PreamblesPerSSB CHOICE { oneEighth ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64}, oneFourth ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64}, oneHalf ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64}, one ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64}, two ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32}, four INTEGER (1..16), eight INTEGER (1..8), sixteen INTEGER (1..4)} OPTIONAL, -- Need M RACH-ConfigGeneric ::= SEQUENCE { Petição 870250088817, de 30 / 09 / 2025, pág. 163 / 235 / 90 prach-ConfigurationIndex INTEGER (0..255), msgl-FDM ENUMERATED {one, two, four, eight}, msg1-FrequencyStart INTEGER (0..maxNrofPhysicalResourceBlocks-1), zeroCorrelationZoneConfig INTEGER(0..15), preambleReceivedTargetPower INTEGER (-202..-60), preambleTransMax ENUMERATED {n3, n4, n5, n6, n7, n8, n10, n20, n50, n100, n200}, powerRampingStep ENUMERATED {dB0, dB2, dB4, dB6}, ra-ResponseWindow ENUMERATED {sl1, sl2, sl4, sl8, sl10, sl20, sl40, sl80}, ...,} -- TAG-RACH-CONFIGGENERIC-STOP -- ASN1STOP

[00143] An example configuration is illustrated in Figure 10(a), where the ROs for single PRACH and multiple PRACH transmissions are completely overlapping in time, but configured with different frequency resources. Two SSBs are assumed. The number of N SSBs associated with an RO, provided by ssb-perRACH-OccasionAndCBPreamblesPerSSB, is one for single PRACH ROs and one-half for multiple PRACH transmission ROs (With such a configuration, the single PRACH transmission will not occupy many RACH resources, and for a selected SSB, the two PRACH transmissions of a RACH attempt can occur on consecutive ROs in the time domain with a small latency.). As can be seen, in time occasion 2 and time occasion 3, the two FDM ROs are associated with different SSBs. This is not a problem for a gNB capable of receiving in different directions simultaneously.However, gNB with analog beamforming can only receive on an operating system (OS) with the associated SSB beamforming at one time, and those transmitted. Petition 870250088817, dated 09 / 30 / 2025, page 164 / 235 / 90 in the FDM RO associated with another SSB are lost. It is likely that a gNB will choose to receive the RO configured for single PRACH transmission and forgo receiving RO for multiple PRACH transmissions, because losing one of multiple PRACH transmissions is more tolerable than losing one of a single PRACH. The lost ROs are cross-referenced in figure 10 (b).

[00144] Figure 11 is a flowchart of an exemplary method 1100 on a terminal node for performing PRACH transmission for a PRACH attempt according to an embodiment of the present description. The method 1100 can be performed on a terminal node (e.g., UE 100). The method 1100 may comprise steps S1110 ~ S1140. However, the present description is not limited to the same. In some other embodiments, the method 1100 may comprise more steps, fewer steps, different steps, or any combination thereof. Additionally, the steps of the method 1100 may be performed in a different order than that described herein. Furthermore, in some exemplary embodiments, a step in the method 1100 may be divided into multiple substeps and performed by different entities, and / or multiple steps in the method 1100 may be combined into a single step.

[00145] Method 1100 can start at step S1110, where an initial PRACH configuration is received from a network node. The initial PRACH configuration sets up an initial set of ROs and includes an initial SSB mapping indication that indicates the mapping of SSBs to ROs.

[00146] In step S1120, the terminal node receives a second PRACH configuration from the network node. The second PRACH configuration sets up a second set of ROs and includes a second SSB mapping indication that indicates the mapping of SSBs to ROs. Petition 870250088817, dated 09 / 30 / 2025, pages 165 / 235 / 90

[00147] So, in step S1130, the network node determines if there is at least one RO associated with an SSB according to the first PRACH configuration overlapping in the time domain with an RO associated with a different SSB according to the second PRACH configuration.

[00148] Finally, in step S1140, in response to the determination that there is at least one RO associated with an SSB according to the first PRACH configuration overlapping in the time domain with an RO associated with a different SSB according to the second PRACH configuration, the network node determines an RO for the PRACH transmission.

[00149] In one embodiment, the S1140 step of determining an RO for PRACH transmission may comprise a step of determining whether the network node is capable of receiving PRACH transmissions with different SSB beams simultaneously.

[00150] In one embodiment, if time-overlapping ROs are configured with different priorities, it is determined that the network node is not able to receive PRACH transmissions with different SSB beams simultaneously and, in this case, the network node only receives PRACH transmissions on high-priority ROs.

[00151] In one embodiment, if an RO of a RACH configuration in which the terminal node selects for PRACH transmission is of a lower priority, the S1140 step of determining an RO for PRACH transmission may comprise a step of determining the RO for PRACH transmission.

[00152] In one embodiment, the step of determining the RO for PRACH transmission may comprise a step of determining ROs mapped to SSBs based on the first and second received PRACH configurations, wherein time-overlapping ROs with a lower priority are not associated with an SSB, which is different from an SSB, with Petition 870250088817, dated 09 / 30 / 2025, page 166 / 235 / 90 which overlapping time ROs with a high priority are associated.

[00153] In one embodiment, the step of determining the RO for PRACH transmission may comprise a step of not counting overlapping time ROs of a lower priority in the RO determination.

[00154] The following are some embodiments for RO selection in the case where there are time-domain overlapping ROs between two RACH configurations, so that the UE can determine an RO for a PRACH attempt. It is obvious that the present request is not limited to the same.

[00155] Time-domain overlapping ROs between two RACH configurations can be configured with different frequency features or the same frequency feature.

[00156] Mode 1, a gNB can indicate whether it is capable of receiving different SSB beams simultaneously or not by configuration.

[00157] A submodality, a gNB can configure a priority for ROs in a RACH configuration. If time-overlapping ROs are associated with different SSBs and configured with different priorities, this implies that the gNB is unable to receive ROs simultaneously associated with different SSBs, and the RO with the lowest priority must be lost. The absence of priority configuration or the same priority configured for time-overlapping ROs indicates that the gNB has no problem receiving ROs simultaneously with different SSB beams.

[00158] A UE usually performs the following two steps before transmitting PRACH, based on which some options are provided: 1) Associate ROs with SSB indices (mapping SSB indices to ROs) according to ssb-perRACH-OccasionAndCBPreamblesPerSSB; Petition 870250088817, dated 09 / 30 / 2025, page 167 / 235 / 90 2) For the selected SSB, determine RO(s) for PRACH transmission(s).

[00159] Mode 2, if the time-domain ROs are associated with different SSBs, and a UE, which plans to transmit PRACH on a low-priority RO, knows that a gNB is unable to simultaneously receive the RO on which it will transmit, one or more of the following may be taken to prevent the gNB from missing an RO.

[00160] - Option 1, the EU can redo the index mapping of SSB for RO for low-priority ROs. The same will not associate a low-priority RO with a different SSB index than that of the overlapping high-priority RO in the time domain. In other words, some low-priority ROs are not associated with an SSB index unless the SSB index is the same as that for the overlapping high-priority ROs in the time domain.

[00161] - Option 2, the overlapping RO in a low-priority time domain is not counted for the determination of a set of ROs for multiple PRACH transmissions, namely, the UE can look for another RO to constitute the uncounted RO.

[00162] - Option 3, the UE does not transmit on the overlapping RO in a time domain with a low priority.

[00163] The result of applying the options is illustrated in Figure 12(a) and Figure 12(b). In particular, Figure 12(a) shows the result of applying Option 1, and Figure 12(b) shows the result of applying Option 2. Consider that ROs for multiple PRACH transmissions are of lower priority. With Option 1, after a UE performs the different SSB indexes on time occasion 2, it will redo the SSB-RO mapping for the low-priority ROs configured for multiple PRACH transmissions. With ssb-perRACH-OccasionAndCBPreamblesPerSSB configured as onehalf, each SSB is associated with two Petition 870250088817, dated 09 / 30 / 2025, pages 168 / 235 / 90 ROs. To map the ROs on frequency resource 2, the UE ignores the RO at time occasion 2 and associates the RO at time occasion 3 with SSB1, which is the same SSB index as the time-overlapping RO on frequency resource 1. After mapping an RO to SSB2 at time occasion 4, the next is at time occasion 6, and the one at time occasion 5 is not associated with an SSB. With Option 2, since the UE knows that the PRACH transmission with frequency resource 2 and at time occasions 2, 3, 6, and 7 should not be received by gNB, it selects the ROs that can be received by gNB for its transmission. For an example of two PRACH transmissions from a RACH attempt, two non-consecutive ROs associated with an SSB form a set of ROs for a RACH attempt.

[00164] Figure 13 schematically shows an embodiment of a 1300 arrangement that can be used in a terminal node (e.g., UE 100) or a network node (e.g., gNB 105) according to an embodiment of the present description.

[00165] The 1300 arrangement comprises either a control unit or a processing unit 1303, for example, a Digital Signal Processor (DSP) or a Central Processing Unit (CPU). The processing unit 1303 may be a single unit or a plurality of units to perform different procedural actions described herein by executing a computer program. The computer program may be stored in a memory 1305. The memory 1305 may be any combination of a RAM (Random Access Memory) and a ROM (Read-Only Memory). The memory may also comprise persistent storage, which, for example, may be any one or a combination of magnetic memory, optical memory, or solid-state memory, or even remotely mounted memory.

[00166] Array 1300 may also comprise an interface of Petition 870250088817, dated 09 / 30 / 2025, page 169 / 235 / 90 communication 1301 arranged for communication. The communication interface 1301 can be implemented as an input unit to receive signals from other entities, and an output unit to provide signal(s) to other entities. The communication interface 401 can also be implemented as an integrated entity or as separate entities.

[00167] The computer program, which comprises computer-readable code / instructions that, when executed by the processing unit 1303 in the arrangement 400, cause the arrangement 1300 and / or the terminal node / network node in which it is included to perform the actions, for example, of the procedure described above in conjunction with Figure 7, Figure 8 and Figure 11 or any other variant.

[00168] The computer program can be configured as a computer program code structured in computer program modules.Therefore, in one embodiment of the example, when the 1300 array is used in a terminal node, the code in the 1300 array computer program includes: a module configured to determine a number of PRACH transmissions based on a parameter received from a network node; a module configured to determine a group of ROs for indexing, wherein an RO in the group of ROs is associated with a selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions; a module configured to index the determined ROs in the group of ROs; and a module configured to perform one or more PRACH transmissions based on the determined number of PRACH transmissions in a set of indexed ROs, wherein a number of ROs in the set is equal to the determined number of PRACH transmissions.

[00169] Additionally or alternatively, in an exemplary embodiment, when the 1300 array is used in a network node, the code in the 1300 array computer program includes: a configured module Petition 870250088817, dated 09 / 30 / 2025, page 170 / 235 / 90 to determine a number of PRACH transmissions; a module configured to determine a group of ROs for indexing, wherein an RO in the group of ROs is associated with a selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions; a module configured to index the ROs determined in the group of ROs; and a module configured to receive and associate the number of PRACH transmissions in a set of indexed ROs, wherein a number of ROs in the set is equal to the determined number of PRACH transmissions.

[00170] Additionally or alternatively, in an exemplary embodiment, when the 1300 array is used on a terminal node, the code in the 1300 array computer program includes: a module configured to receive a first PRACH configuration from a network node, wherein the first PRACH configuration configures a first set of ROs and comprises a first SSB mapping indication that indicates the mapping of SSBs to ROs; a module configured to receive a second PRACH configuration from a network node, wherein the first PRACH configuration configures a second set of ROs and comprises a second SSB mapping indication that indicates the mapping of SSBs to ROs; a module configured to determine whether there is at least one RO associated with an SSB according to the first PRACH configuration overlapping in the time domain with an RO associated with a different SSB according to the second PRACH configuration;and a module configured to, in response to the determination that there is at least one RO associated with an SSB according to the first PRACH configuration overlapping in time domain with an RO associated with a different SSB according to the second PRACH configuration, determine an RO for PRACH transmission. Petition 870250088817, dated 09 / 30 / 2025, page 171 / 235 / 90

[00171] The computer program modules can essentially perform the flow actions illustrated in Figure 7, Figure 8, and Figure 11 to emulate the terminal node or the network node. In other words, when the different modules of the computer program are executed on processing unit 1103, they can correspond to different modules on the terminal node or the network node.

[00172] Although the code means in the embodiments described above together with Figure 13 are implemented as computer program modules that, when executed in the processing unit, cause the arrangement to perform the actions described above together with the aforementioned figures, at least one of the code means may, in alternative embodiments, be implemented at least partially as hardware circuits.

[00173] The present description also provides at least one computer program product in the form of non-volatile or volatile memory, for example, a non-transient computer-readable storage medium, an Electrically Erasable Programmable Read-Only Memory (EEPROM), a flash memory, and a hard disk. The computer program product includes a computer program.The computer program includes: computer-readable code / instructions that, when executed by the 1303 processor, cause the 1300 array to perform the actions, for example, of the procedure described earlier in conjunction with Figure 7; or computer-readable code / instructions that, when executed by the 1303 processor, cause the 1300 array to perform the actions, for example, of the procedure described earlier in conjunction with Figure 8; or computer-readable code / instructions that, when executed by the 1303 processor, cause the 1300 array to perform the actions, for example, of the procedure described earlier in conjunction with Figure 11. Petition 870250088817, dated 09 / 30 / 2025, pp. 172 / 235 / 90

[00174] The computer program product can be configured as a computer program code structured in computer program modules. The computer program modules can essentially perform the flow actions illustrated in Figure 7, Figure 8, or Figure 11.

[00175] The processor may be a single CPU (Central Processing Unit), but it may also comprise two or more processing units. For example, the processor may include general-purpose microprocessors; instruction set processors and / or related chip assemblies and / or special-purpose microprocessors, such as application-specific integrated circuits (ASICs). The processor may also comprise onboard memory for caching purposes. The computer program may be driven by a computer program product connected to the processor. The computer program product may comprise a computer-readable medium on which the computer program is stored.For example, the computer program product may be a flash memory, a random access memory (RAM), a read-only memory (ROM), or an EEPROM, and the above-described computer program modules may, in alternative embodiments, be distributed across different computer program products in the form of memories on the terminal node and / or the network node.

[00176] Corresponding to the above-described method 700, an exemplary terminal node is provided. Figure 14 is a block diagram of a terminal node 1400 according to an embodiment of the present description. The terminal node 1400 may be, for example, UE 100 in some embodiments.

[00177] Terminal node 1400 can be configured to perform method 700, as described above in connection with Figure 7. As shown in Figure 14, terminal node 1400 can comprise a receiving module 1410 configured to determine a number of transmissions of Petition 870250088817, dated 09 / 30 / 2025, page 173 / 235 / 90 PRACH based on a parameter received from a network node, and determine a group of ROs for indexing, wherein an RO in the group of ROs is associated with a selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions; an indexing module 1420 configured to index the ROs determined in the group of ROs; and a transmission module 1430 configured to perform one or more PRACH transmissions based on the determined number of PRACH transmissions in a set of indexed ROs, wherein the number of ROs in the set is equal to the determined number of PRACH transmissions.

[00178] The exposed modules 1410, 1420 and / or 1430 can be implemented as a pure hardware solution or as a combination of software and hardware, for example, by one or more of: a processor or microprocessor and suitable software and memory for software storage, a Programmable Logic Device (PLD) or other electronic component(s) or processing circuitry configured to perform the above-described actions, and illustrated, for example, in Figure 7. Additionally, the terminal node 1400 may comprise one or more additional modules, each of which may perform any of the steps of method 700 described in relation to Figure 7.

[00179] Corresponding to the above-described method 800, a network node is provided. Figure 15 is a block diagram of an exemplary network node 1500 according to an embodiment of the present description. The network node 1500 may be, for example, gNB 105 in some embodiments.

[00180] Network node 1500 can be configured to perform the above-described method 800 in connection with Figure 8. As shown in Figure 15, network node 1500 can comprise a determination module 1510 configured to determine a number of PRACH transmissions, and for Petition 870250088817, dated 09 / 30 / 2025, page 174 / 235 / 90 to determine a group of ROs for indexing, wherein an RO in the group of ROs is associated with a selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions; an indexing module 1520 configured to index the ROs determined in the group of ROs; and a receiving module 1530 configured to receive and associate the number of PRACH transmissions in a set of indexed ROs, wherein the number of ROs in the set is equal to the determined number of PRACH transmissions.

[00181] The exposed modules 1510, 1520 and / or 15300 can be implemented as a pure hardware solution or as a combination of software and hardware, for example, by one or more of: a processor or microprocessor and suitable software and memory for software storage, a PLD or other electronic component(s) or processing circuitry configured to perform the above-described actions, and illustrated, for example, in Figure 8. Additionally, the network node 1500 may comprise one or more additional modules, each of which may perform any of the steps of the method 900 described in relation to Figure 8.

[00182] Corresponding to the above-described 1100 method, an exemplary terminal node is provided. Figure 16 is a block diagram of a 1600 terminal node according to an embodiment of the present description. The 1600 terminal node may be, for example, UE 100 in some embodiments.

[00183] Terminal node 1600 can be configured to perform the above-described method 1100 in connection with Figure 11. As shown in Figure 16, terminal node 1600 can comprise a receiving module 1610 configured to receive an initial PRACH configuration from a network node, wherein the initial PRACH configuration configures an initial set of ROs and comprises an initial SSB mapping indication that indicates the mapping of SSBs to ROs, and to Petition 870250088817, dated 09 / 30 / 2025, page 175 / 235 / 90 to receive a second PRACH configuration from a network node, wherein the first PRACH configuration configures a second set of ROs and comprises a second SSB mapping indication that indicates the mapping of SSBs to ROs; a determination module 1620 configured to determine whether there is at least one RO associated with an SSB according to the first PRACH configuration overlapping in time domain with an RO associated with a different SSB according to the second PRACH configuration, and in response to the determination that there is at least one RO associated with an SSB according to the first PRACH configuration overlapping in time domain with an RO associated with a different SSB according to the second PRACH configuration, to determine an RO for the PRACH transmission.

[00184] The exposed modules 1610 and / or 1620 can be implemented as a pure hardware solution or as a combination of software and hardware, for example, by one or more of: a processor or microprocessor and suitable software and memory for software storage, a Programmable Logic Device (PLD) or other electronic component(s) or processing circuitry configured to perform the above-described actions, and illustrated, for example, in Figure 11. Additionally, the terminal node 1600 may comprise one or more additional modules, each of which may perform any of the steps of the method 1100 described in relation to Figure 11.

[00185] Figure 17 shows an example of a 1700 communication system according to some modalities.

[00186] In the example, the communication system 1700 includes a telecommunication network 1702 which includes an access network 1704, such as a radio access network (RAN), and a core network 1706, which includes one or more nodes of the core network 1708. The access network 1704 includes one or more nodes Petition 870250088817, dated 09 / 30 / 2025, page 176 / 235 / 90 of the access network, such as 1710a and 1710b network nodes (one or more of which may generally be referred to as 1710 network nodes), or any other similar access node of the 3rd Generation Partnership Project (3GPP) or non-3GPP access point. 1710 network nodes facilitate the direct or indirect connection of user equipment (UE), such as by connecting 1712a, 1712b, 1712c, and 1712d UEs (one or more of which may generally be referred to as 1712 UEs) to the 1706 core network via one or more wireless connections.

[00187] Wireless communications to and through a wireless connection includes transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conducting information without the use of wires, cables, or other conductive materials. Furthermore, in different embodiments, the 1700 communication system may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals, whether through wired or wireless connections. The 1700 communication system may include and / or interface with any type of communication network, telecommunication, data, cellular, radio, and / or other similar type of system.

[00188] UEs 1712 can be any of a wide variety of communication devices, including wireless devices arranged, configured and / or operable to communicate wirelessly with network nodes 1710 and other communication devices. Similarly, network nodes 1710 are arranged, capable, configured and / or operable to communicate directly or indirectly with UEs 1712 and / or with other network nodes or equipment in the telecommunications network 1702 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration, in the telecommunications network 1702. Petition 870250088817, dated 09 / 30 / 2025, p. 177 / 235 / 90

[00189] In the example shown, the core network 1706 connects the network nodes 1710 to one or more hosts, such as host 1716. These connections can be direct or indirect through one or more intermediate networks or devices. In other examples, the network nodes may be directly coupled to the hosts. The core network 1706 includes one or more core network nodes (e.g., core network node 1708) that are structured with hardware and software components. The characteristics of these components may be substantially similar to those described in relation to the UEs, network nodes, and / or hosts, such that their descriptions are generally applicable to the corresponding components of the core network node 1708.The nodes of the example core network include functions from one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier Unveiling Function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[00190] Host 1716 may be owned or controlled by a service provider other than an operator or provider of the access network 1704 and / or the telecommunications network 1702, and may be operated by or on behalf of the service provider. Host 1716 may host a variety of applications to provide one or more services. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieval and compilation of data under various environmental conditions detected by a plurality of UEs, analytics functionality, social media, functions to control or otherwise interact with remote devices, functions for a data center. Petition 870250088817, dated 09 / 30 / 2025, page 178 / 235 / 90 alarm and surveillance, or any other such function performed by a server.

[00191] As a whole, the 1700 communication system in Figure 18 enables connectivity between UEs, network nodes, and hosts. In this sense, the communication system can be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunication System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the 802 standards.11 (WiFi) from the Institute of Electrical and Electronics Engineers (IEEE); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMAX), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi and / or any low-power wide area network (LPWAN) standards, such as LoRa and Sigfox.

[00192] In some instances, the 1702 telecommunications network is a cellular network that implements features standardized by 3GPP. In this way, the 1702 telecommunications network can support network slicing to provide different logical networks to different devices that are connected to the 1702 telecommunications network. For example, the 1702 telecommunications network can provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while simultaneously providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive IoT services to still additional UEs.

[00193] In some examples, UEs 1712 are configured to transmit and / or receive information without direct human interaction. For example, a UE may be designed to transmit information to the network of Petition 870250088817, dated 09 / 30 / 2025, page 179 / 235 / 90 access 1704 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the 1704 access network. Additionally, a UE can be configured to operate in single or multi-RAT or multi-pattern RAT mode. For example, a UE can operate with any one or a combination of Wi-Fi, NR (New Radio) and LTE, i.e., being configured for dual multi-radio connectivity (MR-DC), such as E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[00194] In the example, concentrator 1714 communicates with access network 1704 to facilitate indirect communication between one or more UEs (e.g., UE 1712c and / or 1712d) and network nodes (e.g., network node 1710b). In some examples, concentrator 1714 may be a controller, a router, a content and analytics source, or any of the other communication devices described herein in relation to the UEs. For example, concentrator 1714 may be a broadband router that enables access to the central network 1706 for the UEs. As another example, concentrator 1714 may be a controller that sends commands or instructions to one or more actuators on the UEs. Commands or instructions may be received from the UEs, network nodes 1710, or by code, script, process, or other executable instructions on concentrator 1714.As another example, the 1714 concentrator can be a data collector that acts as temporary storage for UE data and, in some embodiments, can perform analysis or other data processing. As another example, the 1714 concentrator can be a content source. For example, for a UE that is a headset, display, speaker, or other VR media delivery device, the 1714 concentrator can retrieve assets, video, audio, or other VR media or sensory information-related data through a network node, which the 1714 concentrator then provides to the UE, or directly after the UE has been created. Petition 870250088817, dated 09 / 30 / 2025, pp. 180 / 235 / 90 local processing, and / or after the addition of local content. In yet another example, the 1714 concentrator acts as a proxy or orchestrator server for the UEs, in particular, if one or more of the UEs are low-energy IoT devices.

[00195] The 1714 concentrator can have a constant / persistent or intermittent connection to the 1710b network node. The 1714 concentrator can also allow a different communication scheme and / or schedule between the 1714 concentrator and the UEs (e.g., UEs 1712c and / or 1712d), and between the 1714 concentrator and the 1706 central network. In other examples, the 1714 concentrator is connected to the 1706 central network and / or one or more UEs via a wired connection. Furthermore, the 1714 concentrator can be configured to connect to an M2M service provider via the 1704 access network and / or to another UE via a direct connection. In some scenarios, UEs can establish a wireless connection with the 1710 network nodes while still being connected through the 1714 concentrator via a wired or wireless connection.In some embodiments, the 1714 concentrator may be a dedicated concentrator—that is, a concentrator whose primary function is to route communications to / from UEs originating from / to the 1710b network node. In other embodiments, the 1714 concentrator may be a non-dedicated concentrator—that is, a device that can operate to route communications between UEs and the 1710b network node, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[00196] Figure 18 shows an UE 1800 according to some embodiments. As used here, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smartphone, a mobile phone, a cellular phone, a voice over IP (VoIP) phone, a wireless local area network phone, a computer Petition 870250088817, dated 09 / 30 / 2025, page 181 / 235 / 90 table, a personal digital assistant (PDA), wireless cameras, a gaming console or device, a music storage device, a playback application, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop embedded equipment (LEE), a laptop mounted equipment (LME), a smart device, wireless consumer premises equipment (CPE), a vehicle-mounted or embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrowband internet of things (NB-IoT) UE, a machine-type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[00197] A UE can support device-to-device (D2D) communication, for example, by implementing a 3GPP standard for side-link communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user, but which may not, or may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user, but which may be associated with or operated for the benefit of a user (e.g., a smart energy meter).

[00198] The UE 1800 includes a set of processing circuits 1802 which is operatively coupled via a bus 1804 to an input / output interface 1806, a power supply 1808, a memory 1810, a communication interface 1812, and / or any other Petition 870250088817, dated 09 / 30 / 2025, p. 182 / 235 / 90 component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 18. The level of integration between components may vary from one UE to another UE. Additionally, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[00199] The 1802 processing circuitry is configured to process instructions and data and can be configured to implement any operational sequential state machine to execute instructions stored as machine-readable computer programs in memory 1810. The 1802 processing circuitry can be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.); programmable logic together with appropriate embedded software; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the 1802 processing circuitry may include multiple central processing units (CPUs).

[00200] In the example, the 1806 input / output interface can be configured to provide an interface or interfaces for an input device, an output device, or one or more input and / or output devices. Examples of an output device include a loudspeaker, a sound card, a video card, a display, a monitor, a printer, an actuator, a transmitter, a smart card, another output device, or any combination thereof. An input device can allow a user to capture information on the UE 1800. Examples of an input device include a touch-sensitive or presence-sensitive display, a Petition 870250088817, dated 09 / 30 / 2025, page 183 / 235 / 90 camera (for example, a digital camera, a digital video camera, an internet camera, etc.), a microphone, a sensor, a mouse, a ball mouse, a directional base, a trackpad, a scroll wheel, a smart card and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to perceive input from a user. A sensor may be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide both an input and an output device.

[00201] In some embodiments, the 1808 power supply is structured as a battery or battery pack. Other types of power supplies, such as an external power supply (e.g., an electrical outlet), a photovoltaic device, or a power cell, may be used. The 1808 power supply may additionally include a power circuit assembly for distributing power from the 1808 power supply itself, and / or an external power supply, to the various parts of the UE 1800 via the circuit assembly or an input interface, such as a power cable. The power distribution may be, for example, for charging the 1808 power supply.The power circuitry can perform any shaping, conversion, or other modification to the power coming from the 1808 power supply to make the power suitable for the respective UE 1800 components to which the power is supplied.

[00202] The 1810 memory can be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), Petition 870250088817, dated 09 / 30 / 2025, page 184 / 235 / 90 exclusively erasable programmable read-only memory (EPROM), exclusively erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 1810 includes one or more application programs 1814, such as an operating system, internet browser application, a widget, gadget engine, or yet another application, and corresponding data 1816. The memory 1810 may store, for use by the UE 1800, any one of a variety of different operating systems or combinations of operating systems.

[00203] The 1810 memory can be configured to include numerous physical units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, USB drive, pen drive, keychain, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smart card memory, such as a tamper-resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or an ISIM, other memory or any combination thereof.The UICC can be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly known as a 'SIM card'. The 1810 memory can allow the UE 1800 to access instructions, application programs, and the like, stored on transient or non-transient memory media, to download data, or to load data. A manufactured item, such as one that uses a communication system, can be tangibly incorporated as or in the 1810 memory, which may be or comprise a... Petition 870250088817, dated 09 / 30 / 2025, page 185 / 235 / 90 device-readable storage media.

[00204] The processing circuitry 1802 can be configured to communicate with an access network or another network using the communication interface 1812. The communication interface 1812 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1822. The communication interface 1812 may include one or more transceivers used for communication, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 1818 and / or a receiver 1820 suitable for providing network communications (e.g., optical, electrical, frequency allocations, and so forth).Furthermore, the 1818 transmitter and the 1820 receiver can be coupled to one or more antennas (e.g., antenna 1822) and can share circuit components, software, or embedded software, or alternatively be implemented separately.

[00205] In the illustrated embodiment, communication functions of the 1812 communication interface may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the Global Positioning System (GPS) to determine a location, another similar communication function, or any combination thereof. Communications may be implemented in accordance with one or more communication protocols and / or standards such as IEEE 802.11, Code Division Multiplexing (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Network (SONET), Petition 870250088817, dated 09 / 30 / 2025, pages 186 / 235 / 90 Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so on.

[00206] Regardless of the sensor type, a UE can provide an output of data captured by its sensors, through its 1812 communication interface, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated wirelessly to a network node via another UE. The output can be periodic (e.g., once every 15 minutes if it reports the perceived temperature), random (e.g., to balance the loads of reports from multiple sensors), in response to a trigger event (e.g., when humidity is detected, an alert is sent), in response to a request (e.g., a user-initiated request), or a continuous stream (e.g., a live video feed of a patient).

[00207] As another example, a UE comprises an actuator, a motor, or a switch connected to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input, the states of the actuator, motor, or switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or a robotic arm that performs a medical procedure according to the received input.

[00208] A UE, when in the form of an Internet of Things (IoT) device, can be a device for use in one or more application domains, these domains comprising, but not limited to, wearable technology in the city, extended industrial application and healthcare. Non-limiting examples of an IoT device such as this are a device that is or is embedded in: a connected refrigerator or freezer, a Petition 870250088817, dated 09 / 30 / 2025, pages 187 / 235 / 90 A TV, a connected lighting device, an electricity meter, a robotic vacuum cleaner, a voice-controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / humidity sensor, an electric door lock, a connected doorbell, an air conditioning system such as a heat pump, an autonomous vehicle, a surveillance system, a climate monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smartwatch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable item for tactile augmentation or sensory enhancement, a water sprinkler, an animal or item tracking device, a sensor for monitoring a plant or animal, an industrial robot,An Unmanned Aerial Vehicle (UAV), and any type of medical device, such as a heart rate monitor or a remotely controlled surgical robot. A UE in the form of an IoT device comprises a set of circuits and / or software depending on the intended application of the IoT device, in addition to the other components, as described in relation to the UE 1800 shown in Figure 18.

[00209] As yet another specific example, in an IoT scenario, a UE can represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE can, in this case, be an M2M device, which, in a 3GPP context, can be referred to as an MTC device. As a particular example, the UE can implement the NB-IoT 3GPP standard. In other scenarios, a UE can represent a vehicle, such as a car, a bus, a truck, a ship, and an aircraft, or other equipment that is capable of monitoring and / or reporting on its operational status or other... Petition 870250088817, dated 09 / 30 / 2025, pp. 188 / 235 / 90 functions associated with its operation.

[00210] In practice, any number of UEs can be used together in relation to a single use case. For example, a first UE might be integrated into a drone and provide the drone's speed information (obtained through a speed sensor) to a second UE, which is a remote control that operates the drone. When the user makes changes from the remote control, the first UE can adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone's speed. The first and / or second UEs can also include more than one of the above-described functionalities. For example, a UE might understand both the sensor and the actuator, and handle data communication for both the speed sensor and the actuators.

[00211] Figure 19 shows a 1900 network node according to some embodiments. As used herein, a network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment in a telecommunications network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, B nodes, evolved B nodes (eNBs) and NR NodeBs (gNBs)).

[00212] Base stations can be categorized based on the amount of coverage they provide (or, stated differently, their transmission power levels) and, therefore, depending on the amount of coverage provided, can be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station can be a relay node or a relay donor node that controls a relay. A network node can also include one or more (or all) parts of a base station. Petition 870250088817, dated 09 / 30 / 2025, page 189 / 235 / 90 distributed radio, such as centralized digital units and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna-integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[00213] Other examples of network nodes include 5G access nodes with multiple transmission points (multi-TRP), multi-standard radio equipment (MSR), such as MSR BSs, network controllers, such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multi-broadcast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Mobile Local Service Centers (E-SMLCs)), and / or Drive Test Minimization (MDTs).

[00214] Network node 1900 includes a set of processing circuits 1902, a memory 1904, a communication interface 1906, and a power supply 1908. Network node 1900 may be composed of multiple physically separate components (e.g., a NodeB component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have its own respective components. In certain scenarios where network node 1900 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair may, in some instances, be considered a single separate network node. In some embodiments, network node 1900 may be configured to Petition 870250088817, dated 09 / 30 / 2025, pp. 190 / 235 / 90 support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1904 for different RATs) and some components may be reused (e.g., the same antenna 1910 may be shared by different RATs). The network node 1900 may also include multiple sets of the various components illustrated for different wireless technologies integrated into the network node 1900, for example, GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-Wave, LoRaWAN, Radio Frequency Identification (RFID), or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components in the network node 1900.

[00215] The processing circuitry set 1902 may comprise a combination of one or more microprocessors, controllers, microcontrollers, central processing units, digital signal processors, application-specific integrated circuits, field-programmable gate arrays, or any other device, feature, or combination of operable computing hardware, software, and / or coded logic suitable for providing, either individually or in conjunction with other network node components 1900, such as memory 1904, for providing network node functionality 1900.

[00216] In some embodiments, the 1902 processing circuitry includes a system-on-a-chip (SOC). In some embodiments, the 1902 processing circuitry includes one or more of the 1912 radio frequency (RF) transceiver circuitry and the 1914 baseband processing circuitry. In some embodiments, the 1912 radio frequency (RF) transceiver circuitry and the 1914 baseband processing circuitry may reside on chips (or chip assemblies), boards, or separate units, such as radio units and digital units. In alternative embodiments, Petition 870250088817, dated 09 / 30 / 2025, p. 191 / 235 / 90 parts or the entirety of the RF transceiver circuit assembly 1912 and the baseband processing circuit assembly 1914 may be on the same chip or set of chips, boards or units.

[00217] Memory 1904 may comprise any form of volatile or non-volatile computer-readable memory including, but not limited to, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., a hard disk), removable storage media (e.g., a flash drive, a Compact Disc (CD), or a Digital Video Disc (DVD)), and / or any other volatile or non-volatile, non-transient, device-readable and / or computer-executable memory devices that store information, data, and / or instructions that can be used by the processing circuitry 1902.Memory 1904 can store any suitable instructions, data, or information, including a computer program, software, or application, including one or more logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 1902 and used by the network node 1900. Memory 1904 can be used to store any calculations performed by the processing circuitry 1902 and / or any data received through the communication interface 1906. In some embodiments, the processing circuitry 1902 and memory 1904 are integrated.

[00218] The 1906 communication interface is used for wired or wireless signaling and / or data communication between a network node, access network, and / or UE. As illustrated, the 1906 communication interface comprises 1916 port(s) / terminal(s) for sending and receiving data, for example, to and from a network via a wired connection. APetition 870250088817, dated 09 / 30 / 2025, pp. 192 / 235 / 90 communication interface 1906 also includes radio front-end circuit assembly 1918 which can be coupled to, or, in certain embodiments, to a part of, antenna 1910. Radio front-end circuit assembly 1918 comprises filters 1920 and amplifiers 1922. Radio front-end circuit assembly 1918 can be connected to an antenna 1910 and to processing circuit assembly 1902. Radio front-end circuit assembly can be configured to condition signals communicated between antenna 1910 and processing circuit assembly 1902. Radio front-end circuit assembly 1918 can receive digital data that must be sent to other network nodes or UEs via a wireless connection.The radio front-end circuitry 1918 can convert digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1920 and / or amplifiers 1922. The radio signal can then be transmitted via antenna 1910. Similarly, during data reception, antenna 1910 can collect radio signals which are then converted into digital data by the radio front-end circuitry 1918. The digital data can be passed to the processing circuitry 1902. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[00219] In certain alternative embodiments, the network node 1900 does not include a separate radio front-end terminal circuit assembly 1918; instead, the processing circuit assembly 1902 includes a radio front-end terminal circuit assembly and is connected to the antenna 1910. Similarly, in some embodiments, all or parts of the RF transceiver circuit assembly 1912 are part of the communication interface 1906. In still other embodiments, the communication interface 1906 includes one or more ports or terminals 1916, the terminal circuit assembly. Petition 870250088817, dated 09 / 30 / 2025, p. 193 / 235 / 90 front radio 1918 and RF transceiver circuit assembly 1912 as part of a radio unit (not shown), and communication interface 1906 communicates with baseband processing circuit assembly 1914, which is part of a digital unit (not shown).

[00220] The 1910 antenna may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The 1910 antenna may be coupled to the 1918 radio front terminal circuit assembly and may be any type of antenna capable of transmitting and receiving wireless data and / or signals. In certain embodiments, the 1910 antenna is separate from the 1900 network node and connectable to the 1900 network node via an interface or port.

[00221] Antenna 1910, communication interface 1906 and / or processing circuitry 1902 can be configured to perform any reception operations and / or certain acquisition operations described herein as being performed by the network node. Any information, data and / or signals can be received from a UE, another network node and / or any other networked equipment. Similarly, antenna 1910, communication interface 1906 and / or processing circuitry 1902 can be configured to perform any transmission operations described herein as being performed by the network node. Any information, data and / or signals can be transmitted to a UE, another network node and / or any other networked equipment.

[00222] The 1908 power supply provides power to the various components of the 1900 network node in a form suitable for the respective components (e.g., at a voltage and current level required for each respective component). The 1908 power supply may additionally comprise, or be coupled to, a set of power management circuits to supply power to the components of the 1900 network node to perform the functionality described herein. For example, the network node Petition 870250088817, dated 09 / 30 / 2025, pages 194 / 235 / 90 1900 can be connected to an external power source (e.g., the mains electricity, an electrical outlet) via a set of circuits or an input interface, such as an electrical cable, whereby the external power source supplies power to the power circuit assembly from the power source 1908. As a further example, the power source 1908 may comprise a power source in the form of a battery or battery pack that is connected to, or integrated into, the power circuit assembly. The battery may provide backup power should the external power source fail.

[00223] Network node 1900 configurations may include additional components beyond those shown in Figure 19 to provide certain aspects of network node functionality, including any of the functionalities described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1900 may include user interface equipment to allow input of information into the network node 1900 and to allow output of information from the network node 1900. This may allow a user to perform diagnostics, maintenance, repair, and other administrative functions for the network node 1900.

[00224] Figure 20 is a block diagram of a 2000 host, which may be an embodiment of the 1716 host of Figure 17, according to various aspects described herein. As used herein, the 2000 host may be or comprise various combinations of hardware and / or software, including a standalone server, a blade server, a cloud-deployed server, a distributed server, a virtual machine, a container, or processing resources in a server farm. The 2000 host may provide one or more services to one or more UEs.

[00225] Host 2000 includes processing circuitry 2002 which is operatively coupled via a bus 2004 to an input / output interface 2006, an interface of Petition 870250088817, dated 09 / 30 / 2025, p. 195 / 235 / 90 network 2008, a power supply 2010 and a memory 2012. Other components may be included in other embodiments. Characteristics of these components may be substantially similar to those described in relation to the devices in the preceding figures, such as figures 18 and 19, in such a way that the descriptions thereof are, in general, applicable to the corresponding components of the host 2000.

[00226] Memory 2012 may include one or more computer programs, including one or more host application programs 2014 and data 2016, which may include user data, for example, data generated by a UE for host 2000 or data generated by host 2000 for a UE. Host 2000 modes may utilize only a subset or all of the components shown. Host application programs 2014 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., telephone sets, desktop computers, wearable display systems, alert monitor systems). Host 2014 application programs can also provide user authentication and licensing checks, and can periodically report health, routes, and content availability to a central node, such as a device on, or at the edge of, a central network. In this way, host 2000 can select and / or indicate a different host for over-the-top services for a UE. Host 2014 application programs can support various protocols, such as the HTTP Live Streaming Protocol (HLS), Real-Time Messaging System Protocol (RTMP), and Streaming Protocol. Petition 870250088817, dated 09 / 30 / 2025, pages 196 / 235 / 90 Real-Time Streaming (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[00227] Figure 21 is a block diagram illustrating a 2100 virtualization environment in which the functions implemented by some modalities can be virtualized. In the present context, virtualization means the creation of virtual versions of appliances or devices, which may include the virtualization of hardware platforms, storage devices, and network resources. As used here, virtualization can be applied to any device described herein, or components thereof, and refers to an implementation in which at least part of the functionality is implemented as one or more virtual components.Some or all of the functions described herein may be implemented as virtual components running on one or more virtual machines (VMs) deployed in one or more virtual environments hosted by one or more hardware nodes, such as a hardware computing device operating as a network node, UE, core network node, or host. Additionally, in embodiments where the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be fully virtualized.

[00228] 2102 applications (which may alternatively be called software instances, virtual applications, network functions, virtual nodes, virtual network functions, etc.) run in the Q400 virtualization environment to implement some of the features, functions and / or benefits of some of the modalities described herein.

[00229] The 2104 hardware includes a set of processing circuits, memory that stores software and / or instructions executable by the hardware processing circuits, and / or other hardware devices, as described herein, such as a network interface, an input / output interface, and so forth. The software may be Petition 870250088817, dated 09 / 30 / 2025, pp. 197 / 235 / 90 executed by the set of processing circuits to instantiate one or more 2106 virtualization layers (also referred to as hypervisors or virtual machine monitors (VMMs)), provide 2108a and 2108b VMs (one or more of which may generally be referred to as 2108 VMs), and / or perform any of the functions, features, and / or benefits described in connection with some embodiments described herein. The 2106 virtualization layer may present a virtual operating platform that appears as networked hardware for the 2108 VMs.

[00230] VMs 2108 comprise virtual processing, virtual memory, virtual network or interface, and virtual storage, and may be run by a corresponding virtualization layer 2106. Different instance modes of a virtual application 2102 may be implemented on one or more of the VMs 2108, and the implementations may be done in different ways. Hardware virtualization is, in some contexts, referred to as network function virtualization (NFV). NFV can be used to consolidate many types of networked equipment over industry-standard high-volume server hardware, physical switches and physical storage, which may be located in data centers, and equipment on consumer premises.

[00231] In the context of NFV, a 2108 VM can be a software implementation of a physical machine that executes programs as if they were running on a non-virtualized physical machine. Each of the 2108 VMs, and that part of the 2104 hardware that runs this VM, whether it is the same hardware dedicated to this VM and / or hardware shared by this VM with other VMs, forms separate virtual network elements. Also in the context of NFV, a virtual network function is responsible for handling specific network functions that run on one or more 2108 VMs on top of the 2104 hardware and correspond to the 2102 application. Petition 870250088817, dated 09 / 30 / 2025, pages 198 / 235 / 90

[00232] 2104 hardware can be implemented on a standalone network node with generic or specific components. 2104 hardware can implement some functions through virtualization. Alternatively, 2104 hardware can be part of a larger hardware cluster (for example, such as in a data center or CPE), where many hardware nodes work together and are managed through 2110 management and orchestration, which, among other things, oversees the lifecycle management of 2102 applications. In some embodiments, 2104 hardware is coupled to one or more radio units, each of which includes one or more transmitters and one or more receivers that can be coupled to one or more antennas.Radio units can communicate directly with other hardware nodes via one or more appropriate network interfaces and can be used in combination with virtual components to provide virtual radio node capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided using a 2112 control system that can alternatively be used for communication between hardware nodes and radio units.

[00233] Figure 22 shows a communication diagram of a host 2202 communicating via a network node 2204 with a UE 2206 through a partially wireless connection according to some embodiments. Example implementations, according to various embodiments, of the UE (such as a UE 1712a of Figure 17 and / or a UE 1800 of Figure 18), of the network node (such as the network node 1710a of Figure 17 and / or the network node 1900 of Figure 19) and of the host (such as the host 1716 of Figure 17 and / or the host 2000 of Figure 20) discussed in the preceding paragraphs will now be described in relation to Figure 22.

[00234] Like host 2000, host 2202 modes include hardware, such as a communication interface, a set of Petition 870250088817, dated 09 / 30 / 2025, pp. 199 / 235 / 90 processing circuits and a memory. Host 2202 also includes software, which is stored on or accessible by host 2202 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as UE 2206, which connects via an over-the-top (OTT) connection 2250 that extends between UE 2206 and host 2202. In providing the service to the remote user, a host application may provide user data that is transmitted using the OTT connection 2250.

[00235] Network node 2204 includes hardware that enables it to communicate with host 2202 and UE 2206. Connection 2260 can be direct or pass through a core network (such as core network 1706 in Figure 17) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network can be a core network or the Internet.

[00236] The UE 2206 includes hardware and software, which is stored on or accessible by the UE 2206 and executable by the UE's processing circuitry. The software includes a client application, such as an internet browser or operator-specific "app," which may be operable to provide a service to a human or non-human user via the UE 2206 with the support of the host 2202. On the host 2202, a running host application may communicate with the running client application via the OTT 2250 connection terminating on the UE 2206 and the host 2202. In providing the service to the user, the UE client application may receive request data from the host application and provide user data in response to the request data. The OTT 2250 connection may transfer both request data and user data.The UE client application can interact with the user to generate the user data that the user provides. Petition 870250088817, dated 09 / 30 / 2025, pages 200 / 235 / 90 for the application of a host via the OTT 2250 connection.

[00237] The OTT 2250 connection can be extended via a 2260 connection between host 2202 and network node 2204 and via a 2270 wireless connection between network node 2204 and UE 2206 to provide the connection between host 2202 and UE 2206. The 2260 connection and the 2270 wireless connection, through which the OTT 2250 connection can be provided, were abstractly designed to illustrate communication between host 2202 and UE 2206 via network node 2204, without explicit reference to any intermediate device or to the precise routing of messages through these devices.

[00238] As an example of data transmission via the OTT 2250 connection, in step 2208, host 2202 provides user data, which can be accomplished by running a host application. In some embodiments, user data is associated with a particular human user interacting with UE 2206. In other embodiments, user data is associated with a UE 2206 that shares data with host 2202 without explicit human interaction. In step 2210, host 2202 initiates a transmission that carries user data toward UE 2206. Host 2202 may initiate the transmission in response to a request transmitted by UE 2206. The request may be caused by human interaction with UE 2206 or by the operation of a client application running on UE 2206. The transmission may pass through network node 2204, in accordance with the principles of the modalities described throughout this description.Thus, in step 2212, network node 2204 transmits to UE 2206 the user data that was carried in the transmission initiated by host 2202, according to the principles of the modalities described throughout this description. In step 2214, UE 2206 receives the user data carried in the transmission, which can be done by a client application running on the associated UE 2206. Petition 870250088817, dated 09 / 30 / 2025, pages 201 / 235 / 90 with the host application executed by host 2202.

[00239] In some instances, UE 2206 runs a client application that provides user data to host 2202. The user data may be provided in reaction to or in response to data received from host 2202. Thus, in step 2216, UE 2206 may provide user data, which may be accomplished by running the client application. In providing user data, the client application may additionally consider user input received from the user via an input / output interface of UE 2206. Regardless of the specific manner in which the user data was provided, UE 2206 initiates, in step 2218, the transmission of user data towards host 2202 via network node 2204.In step 2220, according to the principles of the modalities described throughout this description, network node 2204 receives user data from UE 2206 and initiates the transmission of the received user data towards host 2202. In step 2222, host 2202 receives the user data carried in the transmission initiated by UE 2206.

[00240] One or more of the various modalities improve the performance of OTT services provided to UE 2206 using the OTT 2250 connection, where the wireless 2270 connection forms the last segment. More precisely, the precepts of these modalities can improve the likelihood of successful random access and thus provide benefits such as reduced user waiting time.

[00241] In one example scenario, factory status information can be collected and analyzed by host 2202. As another example, host 2202 can process audio and video data that may have been retrieved from a UE for use in map creation. As yet another example, host 2202 can collect and analyze real-time data to assist in vehicle congestion control (e.g., Petition 870250088817, dated 09 / 30 / 2025, pp. 202 / 235 / 90 traffic light control). As another example, host 2202 can store surveillance video uploaded by a UE. As another example, host 2202 can store or control access to media content, such as video, audio, VR, or AR, which it can transmit via broadcast, multicast, or unicast to UEs. As other examples, host 2202 can be used for energy pricing, remote control of non-time-critical electrical load to balance energy generation needs, location services, presentation services (such as compiling diagrams, etc., from data collected from remote devices), or any other data collection, retrieval, storage, analysis, and / or transmission function.

[00242] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency, and other factors that one or more modes improve. There may additionally be an optional network functionality to reconfigure the OTT 2250 connection between host 2202 and UE 2206 in response to variations in measurement results. The measurement procedure and / or the network functionality to reconfigure the OTT connection may be implemented in software and hardware of host 2202 and / or UE 2206.In some embodiments, sensors (not shown) may be implemented in, or in association with, other devices through which the OTT 2250 connection passes; the sensors may participate in the measurement procedure by supplying values ​​of the monitored quantities exemplified previously, or by supplying values ​​of other physical quantities from which the software can compute or estimate the monitored quantities. Reconfiguration of the OTT 2250 connection may include message format, retransmission settings, preferred routing, etc.; reconfiguration does not need to directly alter the operation of the 2204 network node. Such procedures and functionalities may be known. Petition 870250088817, dated 09 / 30 / 2025, pp. 203 / 235 / 90 and practiced in the technology. In certain modalities, the measurements may involve proprietary UE signaling that facilitates measurements of transfer rate, propagation times, latency and the like by the 2202 host. The measurements may be implemented where the software causes messages to be transmitted, in particular, empty or 'simulated' messages, using the 2250 OTT connection while monitoring propagation times, errors, etc.

[00243] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It should be understood that these computing devices may comprise any suitable combination of hardware and / or software necessary to perform the tasks, features, functions, and methods described herein.The determination, calculation, acquisition, or similar operations described herein may be performed by the set of processing circuits, which may process information, for example, by converting the obtained information into other information, comparing the obtained or converted information with the information stored in the network node, and / or performing one or more operations based on the obtained or converted information, and, as a result of said processing, making a determination. Furthermore, although components are represented as individual boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that constitute a single illustrated component, and functionality may be partitioned among separate components.For example, a communication interface can be configured to include any of the components described here, and / or the functionality of the components can be partitioned among the set of... Petition 870250088817, dated 09 / 30 / 2025, pp. 204 / 235 / 90 processing circuits and the communication interface. In another example, the non-computationally intensive functions of any of these components can be implemented in software or embedded software, and the computationally intensive functions can be implemented in hardware.

[00244] In certain embodiments, parts or all of the functionality described herein may be provided by the processing circuitry that executes instructions stored in memory, which, in certain embodiments, may be a computer program product in the form of a nontransient, computer-readable storage medium. In alternative embodiments, parts or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a manner embedded in a hardware system. In either of these particular embodiments, whether executing instructions stored on a nontransient, computer-readable storage medium or not, the processing circuitry may be configured to perform the described functionality.The benefits provided by such functionality are not limited to the individual processing circuitry or other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network in general.

[00245] The present description is described above in relation to embodiments thereof. However, these embodiments are provided for illustrative purposes only, rather than limiting the present description. The scope of the description is defined by the appended claims, as well as by equivalents thereof. Those skilled in the art may make various alterations and modifications without departing from the scope of the description, all of which will fall within the scope of the present description. Petition 870250088817, dated 09 / 30 / 2025, pages 205 / 235 / 90 scope of the description. NUMBERED MODALITIES

[00246] 1. A method (700) at a terminal node for performing multiple transmissions on Physical Random Access Channel, PRACH, for a PRACH attempt, comprising: determine (S710) a number of PRACH transmissions based on a parameter received from a network node, determine (S720) a group of PRACH Occasions, ROs, for indexing, wherein an RO in the group of ROs is associated with a selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions, index (S730) the ROs determined in the group of ROs, and perform (S740) one or more PRACH transmissions based on the determined number of PRACH transmissions in a set of indexed ROs, wherein a number of ROs in the set is equal to the determined number of PRACH transmissions.

[00247] 2. The method of mode 1, wherein, if the number of PRACH transmissions are time-domain multiplexed and, if there are multiple frequency multiplexing ROs associated with the selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions, one of the multiple ROs in a time instance is determined.

[00248] 3. The method of mode 1 or 2, in which, if at least part of the number of PRACH transmissions are multiplexed in the frequency domain, the determination of a group of ROs for indexing comprises: Determine a number of ROs that are frequency-domain multiplexed, with the number being equal to the number of simultaneous frequency-domain multiplexed PRACH transmissions. Petition 870250088817, dated 09 / 30 / 2025, pages 206 / 235 / 90

[00249] 4. The method of any of the modalities 1 to 3, additionally comprising: Determine a configured number K of PRACH transmissions, determine a number R of ROs associated with the selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions in an association period, and if the number R is less than the number K, determine an extended association period that includes a minimum number X of association periods, where the number of ROs associated with the selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions in the X association periods is greater than or equal to the determined configured number K, and where the determination and indexing of a group of ROs are performed in the extended association period.

[00250] 5. The method of modality 4, in which, if the number R is greater than or equal to the number K, the number X is determined as 1, and the determination and indexing of a group of ROs are carried out in a period of association.

[00251] 6. The method of mode 4 or 5, where the number K is the determined number of PRACH transmissions, or a larger number of the multiple numbers of PRACH transmissions configured by the network node.

[00252] 7. The method of any of the modes 4 to 6, additionally comprising: To determine the first frame of an initial membership period of the extended membership period as an initial radio frame of the extended membership period, and a frame immediately after the end of the extended membership period as an initial radio frame of an extended membership period close to the membership period. Petition 870250088817, dated 09 / 30 / 2025, pp. 207 / 235 / 90 extended.

[00253] 8. The method of any of the modalities 4 to 7, wherein, if the number of ROs in the RO group during the extended association period is greater than the determined number of PRACH transmissions, the performance of one or more PRACH transmissions based on the determined number of PRACH transmissions in the indexed RO set comprises: Perform one or more RACH transmissions on an initial number of ROs in the indexed ROs, the first number being equal to the number of PRACH transmissions, and repeat one PRACH transmission from the one or more PRACH transmissions on the remaining ROs in the indexed ROs.

[00254] 9. The method of any of the modalities 4 to 7, wherein, if the number of ROs in the RO group during the extended association period is greater than the number of PRACH transmissions, the performance of one or more PRACH transmissions based on the determined number of PRACH transmissions in the indexed RO set comprises: To carry out one or more PRACH transmissions by distributing one or more PRACH transmissions across the group of ROs, so that a pattern of ROs used is disseminated in each of the X association periods.

[00255] 10. The method of any of the modalities 1 to 9, in which the realization of one or more PRACH transmissions based on the determined number of PRACH transmissions in the set of indexed ROs comprises: To determine a transmission pattern for one or more PRACH transmissions, and to carry out one or more PRACH transmissions by following the transmission pattern.

[00256] 11. The method of modality 10, in which the pattern of Petition 870250088817, dated 09 / 30 / 2025, page 208 / 235 / 90 transmission is identified by the frame number.

[00257] 12. Method (800) on a network node for receiving multiple Physical Random Access Channel, PRACH, transmissions for a PRACH attempt from a terminal node, comprising: determine (S810) a number of PRACH transmissions, determine (S820) a group of PRACH Occasions, ROs, for indexing, wherein an RO in the group of ROs is associated with a selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions, index (S830) the ROs determined in the group of ROs, and receive and associate (S840) the number of PRACH transmissions in a set of indexed ROs with a PRACH attempt, wherein a number of ROs in the set is equal to the determined number of PRACH transmissions.

[00258] 13. The method of modality 12, in which, if the number of PRACH transmissions are time-domain multiplexed and, if there are multiple frequency multiplexing ROs associated with the selected SSB and with a preamble partition applicable to the determined number of RRACH transmissions, one of the multiple ROs in a time instance is determined.

[00259] 14. The method of mode 12 or 13, in which, if at least part of the number of PRACH transmissions are multiplexed in the frequency domain, determining a group of ROs for indexing comprises: Determine a number of ROs that are frequency-domain multiplexed, with the number being equal to the number of simultaneous frequency-domain multiplexed PRACH transmissions.

[00260] 15. The method of any of the modalities 12 to 14, additionally comprising: Petition 870250088817, dated 09 / 30 / 2025, p. 209 / 235 / 90 to determine a configured number K of PRACH transmissions, to determine a number R of ROs associated with the selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions in an association period, and if the number R is less than the number K, to determine an extended association period that includes a minimum number X of association periods, wherein a number of ROs associated with the selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions in the X association periods is greater than or equal to the determined configured number K, and wherein the determination and indexing of a group of ROs are performed in the extended association period.

[00261] 16. The method of modality 15, in which, if the number R is greater than or equal to the number K, the number X is determined as 1, and the determination and indexing of a group of ROs are carried out in a period of association.

[00262] 17. The method of mode 15 or 16, where the number K is the determined number of PRACH transmissions, or a larger number of the multiple numbers of PRACH transmissions configured by the network node.

[00263] 18. The method of any of the modalities 15 to 17, additionally comprising: To determine the first frame of an initial association period of the extended association period as an initial radio frame of the extended association period, and a frame immediately after the end of the extended association period as an initial radio frame of an extended association period close to the extended association period.

[00264] 19. The method of any of the modalities 15 to 18, in Petition 870250088817, dated 09 / 30 / 2025, pp. 210 / 235 / 90, which states that if the number of ROs in the RO group during the extended association period is greater than the determined number of PRACH transmissions, receiving and associating the number of PRACH transmissions in the indexed RO set comprises: Receive the number of PRACH transmissions in an initial number of ROs in the indexed ROs, the first number being equal to the number of PRACH transmissions, and receive a repetition of one of the number of PRACH transmissions in the remaining ROs in the indexed ROs.

[00265] 20. The method of any of the modalities 15 to 18, in which, if the number of ROs in the RO group in the extended association period is greater than the number of PRACH transmissions, receiving and associating the number of PRACH transmissions in the indexed RO set comprises: receive the number of PRACH transmissions that are distributed across the group of ROs, where a pattern of ROs used spreading in each of the X association periods is the same.

[00266] 21. The method of any of the modalities 12 to 20, in which receiving the number of PRACH transmissions in the set of indexed ROs comprises: To determine a transmission pattern for the number of PRACH transmissions, and to receive the number of PRACH transmissions by following the transmission pattern.

[00267] 22. The method of mode 21, in which the transmission pattern is identified by the frame number.

[00268] 23. A method (1100) on a terminal node for performing PRACH transmission for a PRACH attempt, comprising: receive (S1110) a first configuration of the Channel of Petition 870250088817, dated 09 / 30 / 2025, pages 211 / 235 / 90 Physical Random Access (PRACH) from a network node, wherein the PRACH configuration configures a first set of ROs and comprises a first SSB mapping indication that indicates the mapping of Synchronization Signal / Physical Broadcast Channels, SSBs, to PRACH Occasions, ROs, receive (S1120) a second PRACH configuration from a network node, wherein the second PRACH configuration configures a second set of ROs and comprises a second SSB mapping indication that indicates the mapping of SSBs to ROs, determine (S1130) whether there is at least one RO associated with an SSB according to the first PRACH configuration overlapping in time domain with an RO associated with a different SSB according to the second PRACH configuration,and in response to the determination that there is at least one RO associated with an SSB according to the first PRACH configuration overlapping in time domain with an RO associated with a different SSB according to the second PRACH configuration, determine (S1130) an RO for the PRACH transmission.

[00269] 24. The method of modality 23, in which determining a RO for the transmission of PRACH comprises: To determine if the network node is capable of receiving PRACH transmissions with different SSB beams simultaneously.

[00270] 25. The method of modality 24, in which, if the time-overlapping ROs are configured with different priorities, it is determined that the network node is not able to receive PRACH transmissions with different SSB beams simultaneously and, in this case, the network node only receives PRACH transmissions on high-priority ROs.

[00271] 26. The method of modality 25, in which, if an RO of a RACH configuration in which the terminal node selects for transmission of Petition 870250088817, dated 09 / 30 / 2025, pages 212 / 235 / 90 For PRACH transmissions of lower priority, determining a RO for PRACH transmission includes: determine the RO for PRACH transmission.

[00272] 27. The method of modality 26, in which determining the RO for the transmission of PRACH comprises: Determine ROs mapped to SSBs based on the first and second PRACH configurations received, where time-overlapping ROs with a lower priority are not associated with an SSB, which is different from an SSB, with which time-overlapping ROs with a high priority are associated.

[00273] 28. The method of modality 26, in which determining the RO for the transmission of PRACH comprises: Do not count overlapping ROs in the time of a lower priority in determining the RO.

[00274] 29. A terminal node (1300), comprising: a communication interface (1301) arranged for communication, at least one processor (1303), and a memory (1305) comprising instructions which, when executed by at least one processor, cause the terminal node to perform the method as defined in any of the embodiments 1 to 11.

[00275] 30. A network node (1300), comprising: a communication interface (1301) arranged for communication, at least one processor (1303), and a memory (1305) comprising instructions which, when executed by at least one processor, cause the network node to perform the method as defined in any of the modes 12 to 22 and modes 23-28. Petition 870250088817, dated 09 / 30 / 2025, pp. 213 / 235 / 90

[00276] 31. A computer program comprising instructions that, when executed by at least one processor, cause that processor to perform the method as defined in any of the embodiments 1 to 11.

[00277] 32. A computer program comprising instructions that, when executed by at least one processor, cause that processor to perform the method as defined in any of embodiments 12 to 22 and embodiments 23-28.

[00278] 33. A carrier containing the computer program of embodiments 31 or 32, wherein the carrier is an electronic signal, an optical signal, a radio signal or a computer-readable storage medium. Petition 870250088817, dated 09 / 30 / 2025, pages 214 / 235

Claims

1 / 6 CLAIMS 1. Method (700) on a terminal node for performing multiple transmissions on Physical Random Access Channel, PRACH, for a PRACH attempt, characterized in that it comprises: determining (S710) a number of PRACH transmissions based on a parameter received from a network node, determining a configured number K of PRACH transmissions, determining a number R of PRACH Occasions, ROs, associated with a selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions in an association period, determining an extended association period, the extended association period including a number X of association periods, wherein the number X of association periods is the minimum number of association periods such that X^R > K, determining (S720), in the extended association period, a set of ROs for indexing,wherein an RO in the set of ROs is associated with the selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions, index (S730) the determined ROs in the set of ROs, and perform (S740) one or more PRACH transmissions based on the determined number of PRACH transmissions in the indexed set of ROs, wherein the number of ROs in the set is equal to the determined number of PRACH transmissions.

2. Method according to claim 1, characterized in that, if the number X is determined as 1, the determination and indexing of the set of ROs are performed in one association period.

3. Method according to claim 1 or 2, characterized in Petition 870250088817, dated 09 / 30 / 2025, page 215 / 235 2 / 6 by the fact that the number K is the largest of the multiple number of PRACH transmission candidates configured by the network node.

4. A method according to any one of claims 1 to 3, characterized in that it further comprises: determining a first frame of a first association period of the extended association period as an initial radio frame of the extended association period, and a frame immediately after the end of the extended association period as an initial radio frame of an extended association period close to the extended association period.

5. A method according to any one of claims 1 to 4, characterized in that, if the number of ROs in the set of ROs in the extended membership period is greater than the determined number of PRACH transmissions, performing one or more PRACH transmissions based on the determined number of PRACH transmissions in the set of indexed ROs comprises: performing the one or more PRACH transmissions on an initial number of ROs in the indexed ROs, the initial number being equal to the number of PRACH transmissions, and repeating one PRACH transmission from the one or more PRACH transmissions on the remaining ROs in the indexed ROs.

6. A method according to any one of claims 1 to 5, characterized in that performing one or more PRACH transmissions based on a determined number of PRACH transmissions in the set of indexed ROs comprises: determining a transmission pattern for the one or more PRACH transmissions, and performing the one or more PRACH transmissions by following the transmission pattern. Petition 870250088817, dated 09 / 30 / 2025, pp. 216 / 235 3 / 6 7. Method according to claim 6, characterized in that the transmission pattern is identified by the frame number.

8. Method (800) on a network node for receiving multiple transmissions on Physical Random Access Channel, PRACH, for a PRACH attempt from a terminal node, characterized in that it comprises: determining (S810) a number of PRACH transmissions, determining a configured number K of PRACH transmissions, determining a number R of PRACH Occasions, ROs, associated with a selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions in an association period, determining an extended association period, the extended association period including a number X of association periods, wherein the number X of association periods is the minimum number of association periods such that X^R > K, determining (S820), in the extended association period, a set of ROs for indexing,wherein an RO in the set of ROs is associated with the selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions, index (S830) the determined ROs in the set of ROs, and receive and associate (S840) the number of PRACH transmissions in the indexed set of ROs with a PRACH attempt, wherein the number of ROs in the set is equal to the determined number of PRACH transmissions.

9. Method according to claim 8, characterized in that, if number X is determined as 1, the determination and indexing of the set of ROs are performed in one association period. Petition 870250088817, dated 09 / 30 / 2025, p. 217 / 235 4 / 6 10. Method according to claim 8 or 9, characterized in that the number K is the largest of the multiple number of PRACH transmission candidates configured by the network node.

11. A method according to any one of claims 8 to 10, characterized in that it further comprises: determining a first frame of a first association period of the extended association period as an initial radio frame of the extended association period, and a frame immediately after the end of the extended association period as an initial radio frame of an extended association period close to the extended association period.

12. A method according to any one of claims 8 to 11, characterized in that, if the number of ROs in the RO set during the extended association period is greater than the determined number of PRACH transmissions, receiving and associating the number of PRACH transmissions in the indexed RO set comprises: receiving the number of PRACH transmissions in a first number of ROs in the indexed ROs, the first number being equal to the number of PRACH transmissions, and receiving a repetition of one of the number of PRACH transmissions in the remaining ROs in the indexed ROs.

13. A method according to any one of claims 8 to 12, characterized in that receiving the number of PRACH transmissions in the set of indexed ROs comprises: determining a transmission pattern for the number of PRACH transmissions, and receiving the number of PRACH transmissions by following the transmission pattern.

14. Method according to claim 13, characterized in Petition 870250088817, dated 09 / 30 / 2025, pp. 218 / 235 5 / 6 by the fact that the transmission pattern is identified by the frame number.

15. Terminal node (1300), for performing multiple transmissions on Physical Random Access Channel, PRACH, for a PRACH attempt, characterized in that the terminal node is configured to: determine (S710) a number of PRACH transmissions based on a parameter received from a network node, determine a configured number K of PRACH transmissions, determine a number R of PRACH Occasions, ROs, associated with a selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions in an association period, determine an extended association period, the extended association period including a number X of association periods, wherein the number X of association periods is the minimum number of association periods, such that X^R > K, determine (S720), in the extended association period, a set of ROs for indexing,wherein an RO in the set of ROs is associated with the selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions, index (S730) the determined ROs in the set of ROs, and perform (S740) one or more PRACH transmissions based on the determined number of PRACH transmissions in the indexed set of ROs, wherein the number of ROs in the set is equal to the determined number of PRACH transmissions.

16. Terminal node according to claim 15, characterized in that it is additionally configured to perform the method as defined in any one of claims 2 to 7. Petition 870250088817, dated 09 / 30 / 2025, p. 219 / 235 6 / 6 17. Network node (1300) for receiving multiple transmissions on Physical Random Access Channel, PRACH, for a PRACH attempt from a terminal node, characterized in that the network node is configured to: determine (S810) a number of PRACH transmissions, determine a configured number K of PRACH transmissions, determine a number R of PRACH Occasions, ROs, associated with a selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions in an association period, determine an extended association period, the extended association period including a number X of association periods, wherein the number X of association periods is the minimum number of association periods such that X^R > K, determine (S820), in the extended association period, a set of ROs for indexing,wherein an RO in the set of ROs is associated with the selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions, index (S830) the determined ROs in the set of ROs, and receive and associate (S840) the number of PRACH transmissions in the indexed set of ROs with a PRACH attempt, wherein the number of ROs in the set is equal to the determined number of PRACH transmissions.

18. Network node according to claim 17, characterized in that it is additionally configured to perform the method as defined in any one of claims 8 to 14.

19. Product, process, system, means, kit or use, characterized by the fact that it comprises one or more elements as described in the descriptive report and / or illustrated in the figures. Petition 870250088817, dated 09 / 30 / 2025, pp. 220 / 235

Images