RO indexing multiple PRACH transmissions

Abstract

The present disclosure relates to an end node, a network node and a method of performing RO indexing to ensure alignment of ROs so that the network node can combine them for PRACH attempts. A method at a terminal node is provided, comprising: determining the number of PRACH transmissions; determining a PRACH transmission configuration number K; determining a number R of ROs associated with the selected SSB and associated with a preamble partition applicable to the determined number of PRACH transmissions within an association period; determining an extended association period including X association periods; determining a set of ROs for indexing within the extended association cycle; indexing the determined ROs in the set of ROs; and performing one or more PRACH transmissions within the set of indexed ROs based on the determined number of PRACH transmissions.

Description

Technical Field

[0001] This disclosure relates to the field of telecommunications, and more particularly to terminal nodes, network nodes, and methods for compiling PRACH timing (RO) indexes in multiple Physical Random Access Channel (PRACH) transmissions. Background Technology

[0002] With the development of electronic and telecommunications technologies, mobile devices such as mobile phones, smartphones, laptops, tablets, and in-vehicle devices have become an important part of our daily lives. To support a large number of mobile devices, efficient radio access networks (RANs) such as fifth-generation (5G) new radio (NR) RANs will be needed.

[0003] NR cell search and system information acquisition

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

[0005] Up to 4, 8, or 64 SSBs can be transmitted within an SSB period, depending on the frequency range of the frequency band used. An SSB period can be 5ms, 10ms, 20ms, 40ms, 80ms, or 160ms as configured in SIB1. Assuming it is used for initial cell search, the default SSB period is 20ms since SIB1 is unavailable.

[0006] NR random access procedure

[0007] In NR and LTE networks, a terminal device (e.g., a user equipment (UE)) performs random access to access a new cell. Once the random access process is complete, the terminal device can connect to network equipment (e.g., an evolved NodeB (eNB) or gNB) and communicate with the network equipment using dedicated transport.

[0008] Two types of random access procedures are supported: a 4-step random access type using Msg1 and a 2-step random access type using MSGA. Both types of random access (RA) procedures support contention-based random access (CBRA) and contention-free random access (CFRA).

[0009] Figure 1A The signaling sequence for a four-step contention-based random access procedure (also known as a Type 1 random access procedure in 3GPP TS 38.213) is shown. As illustrated, at 101, the UE detects the synchronization signal (SS) from the gNB. At 102, the UE decodes the Master Information Block (MIB) and System Information Block (SIB) (i.e., Residual Minimum System Information (RMSI) and other System Information (OSI)) to obtain random access transmission parameters, which may be distributed across multiple physical channels such as the Physical Broadcast Channel (PBCH) and the Physical Downlink Shared Channel (PDSCH). At 111, the UE sends the Physical Random Access Channel (PRACH) preamble or Msg1 to the gNB. At 112, the gNB detects Msg1 and responds with a Random Access Response (RAR) (Msg2). At 113, the UE sends either the PUSCH or Msg3 to the gNB based on the configuration information for Physical Uplink Shared Channel (PUSCH) transmission carried in the RAR. At position 114, the gNB sends a contention resolution message or Msg4 to the UE.

[0010] In such Figure 1A In the four-step random access process shown, the resources (including time and frequency resources) used for PUSCH (i.e., Msg3) are indicated in the RAR (i.e., Msg2). Specifically, the RAR contains an uplink grant, which includes a 14-bit "PUSCH Frequency Resource Allocation" field indicating the frequency domain resources used for PUSCH and a 4-bit "PUSCH Time Resource Allocation" field indicating the time domain resources used for PUSCH.

[0011] It is possible for multiple UEs to select the same random access preamble and transmit the preamble on the same PRACH time / frequency resources. This preamble conflict is called contention. One of the main purposes of applying steps 113 and 114 is to resolve this potential contention.

[0012] To minimize the number of channel accesses (which is important for operations in unlicensed bands where a Talk-Before-Transmission (LBT) is required), a two-step random access procedure is also proposed for NR. The four-step random access procedure does not use four steps 111 to 114, but instead completes random access in only two steps and two messages (which may be referred to as Msg A and Msg B). Figure 1BThe signaling sequence for a two-step contention-based random access procedure (also known as a Type 2 random access procedure in TS 38.213) is shown in the figure. Figure 1B Steps 101 to 102 in the middle Figure 1A Steps 101 to 102 are the same. At 121, the UE sends a PRACH preamble and PUSCH to the gNB in ​​a message (i.e., message A (msgA)). The PUSCH may include higher-layer data such as a Radio Resource Control (RRC) connection request, and possibly some small additional payloads. At 122, the gNB sends message B (msgB) to the UE, which includes UE identifier assignment, timing advance information, and contention resolution message (CRM), etc.

[0013] Figure 2A The diagram illustrates a four-step random access type with no contention for random access, and... Figure 2B This illustrates a two-step random access type, contention-free random access. For example... Figure 2A As shown, network node 104 assigns a preamble for CFRA in the 4-step RACH, and as... Figure 2B As shown, network node 104 assigns the preamble and PUSCH for CFRA in the 2-step RACH. For the bandwidth portion (BWP), network node 104 does not simultaneously configure CFRA resources for both the 4-step RA type and the 2-step RA type. CFRA for the 2-step RA type is only supported for switching.

[0014] The 4-step RA type Msg1 includes only the preamble on the PRACH, while the 2-step RA type MSGA includes both the preamble on the PRACH and the payload on the PUSCH. After either the Msg1 or MSGA transmission, UE 102 monitors for responses from network node 104 within a configured window. For CFRA, UE 102 terminates the random access procedure upon receiving a network response.

[0015] PRACH configuration

[0016] In NR, the time and frequency resources for transmitting the RACH preamble are defined as PRACH timing (RO).

[0017] The timing resources and format of the PRACH preamble are configured by the RACH configuration index. For details of the PRACH configuration index, refer to 3GPP TS 38.211, the entire contents of which are incorporated herein by reference. The PRACH configuration index indicates the rows in the PRACH configuration tables specified in TS 38.21, Tables 6.3.3.2-2, 6.3.3.2-3, and 6.3.3.2-4, for paired spectrum of FR1 (e.g., 450MHz to 6GHz), unpaired spectrum of FR1, and unpaired spectrum of FR2 (e.g., 24.25GHz to 52.6GHz), respectively. The rows in the RACH configuration tables specify the time-domain PRACH timing pattern for a RACH configuration period. A PRACH configuration period can be 10, 20, 40, 80, or 160 ms.

[0018] In the frequency domain, NR supports multiple frequency-reused RACH opportunities on the same time-domain RACH opportunity. The primary motivation is to support analog beam scanning in NR so that RACH opportunities associated with a single SSB can be configured at the same time but at different frequency locations. The PRACH preamble can only be transmitted in the frequency resources specified by the higher-layer parameter msg1-FrequencyStart. During initial access, the frequency resource n for the PRACH opportunity... RA ∈{0, 1…M-1} (where M equals the higher-layer parameter msg1-FDM) are numbered in ascending order starting from the lowest frequency within the initial active uplink bandwidth portion. Otherwise, n RA Within the active uplink bandwidth portion, numbers are assigned in ascending order, starting from the lowest frequency. The number M of PRACH opportunities that are frequency-domain multiplexed (FDMed) within a time-domain RACH opportunity can be 1, 2, 4, or 8.

[0019] Figure 3 An example of PRACH timing configuration in NR is shown. Figure 3 As shown, in one time instance, four PRACH timings are frequency-division multiplexed.

[0020] In NR Release 17, for each RACH timing in each cell, there are up to 64 sequences that can be used as RACH preambles. The RRC parameter totalNumberOfRA-Preambles determines how many of these 64 sequences are used as RACH preambles for each RACH timing in each cell. The 64 sequences are configured as follows: first, all available cyclic shifts of the Zadoff-Chu root sequence are included; second, they are ordered in ascending order of the root index until 64 preambles have been generated for the PRACH timing.

[0021] NR version 17 correlation between SSB and PRACH timing

[0022] NR version 17 supports one-to-one, one-to-many, and many-to-one associations between SSB and RACH timing.

[0023] The RACH preamble associated with each SSB is configured by two RRC parameters in RACH-ConfigCommon: ssb-perRACH-OccasionAndCB-PreamblesPerSSB and totalNumberOfRA-Preambles.

[0024] Figure 4 An example of the mapping between SSBs and RACH preambles is shown, where the number of SSBs is 8, M=32 (i.e., 2 SSBs per PRACH opportunity), and the number of frequency-division multiplexed PRACH opportunities in a time instance is 2. The PRACH format is A3, i.e., 2 TD PRACH opportunities per slot. The PRACH configuration period is 20ms, and there are 2 PRACH slots per configuration period.

[0025] For each SSB, the associated preamble for each PRACH timing / It is further divided into two groups: Contention-Based Random Access (CBRA) and Contention-Free Random Access (CFRA). The number R of CB preambles for each SSB in each PRACH timing is signaled by the RRC parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB. In a PRACH timing for one SSB, the preamble indices for CBRA and CFRA are mapped sequentially.

[0026] In 3GPP Release 18, multiple PRACH transmissions are supported, where the UE transmits multiple PRACHs within a set of ROs used for PRACH attempts. The UE and gNB need to align on a specific set of ROs so that the gNB can combine them for PRACH attempts and allow the UE and gNB to determine the start of the RAR window, the Random Access Radio Network Temporary Identifier (RA-RNTI), etc.

[0027] However, on the one hand, in NR versions prior to version 18, RO indexing was only specified for CFRA, not for CBRA. On the other hand, RO indexing for CFRA was specified for three scenarios, and applying it to a set of ROs that the UE determines for multiple PRACH transmissions will cause some problems or limitations.

[0028] Furthermore, problems may arise when there is temporal overlap between conventional RO and standalone RO. Summary of the Invention

[0029] The purpose of this application is to provide some solutions for indexing multiple PRACH transports using RO, and solutions for addressing problems that arise when there are time-domain overlapping ROs between traditional ROs and individual ROs.

[0030] According to a first aspect of this disclosure, a method is provided at an end node for performing multiple PRACH transmissions for a Physical Random Access Channel (PRACH) attempt. The method includes: determining the number of PRACH transmissions based on parameters received from a network node; determining a PRACH transmission configuration number K; determining a number R of PRACH opportunities (ROs) associated with a selected SSB and associated with a preamble partition applicable to the determined number of PRACH transmissions within an association period; and determining an extended association period comprising X association periods, wherein the X association periods are such that... The minimum number of association periods; determining a set of ROs for indexing within an extended association period, wherein the ROs in the set of ROs are associated with the selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions; indexing the determined ROs in the set of ROs; and performing 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.

[0031] According to a second aspect of this disclosure, a terminal node is provided. The terminal node is configured to: determine the number of PRACH transmissions based on parameters received from a network node; determine a PRACH transmission configuration number K; determine a number R of PRACH timings (ROs) associated with a selected SSB and associated with a preamble division applicable to the determined number of PRACH transmissions within an association period; and determine an extended association period comprising X association periods, wherein the X association periods are such that... The minimum number of association periods; determining a set of ROs for indexing within an extended association period, wherein the ROs in the set of ROs are associated with the selected SSB and with a preamble partition applicable to the determined number of PRACH transmissions; indexing the determined ROs in the set of ROs; and performing 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.

[0032] According to a third aspect of this disclosure, a method is provided at a network node for receiving multiple PRACH transmissions for a PRACH attempt from an end node. The method includes: determining the number of PRACH transmissions; determining a PRACH transmission configuration number K; determining a number R of PRACH opportunities (ROs) associated with a selected SSB and associated with a preamble partition applicable to the determined number of PRACH transmissions within an association period; and determining an extended association period comprising X association periods, wherein the X association periods are such that... The minimum number of association periods; within the extended association period, a set of ROs for indexing is determined, wherein the ROs in the set of ROs are associated with the selected SSB and with the preamble partition applicable to the determined number of PRACH transmissions; the determined ROs in the set of ROs are indexed; the number of PRACH transmissions is received within the set of indexed ROs and associated with the PRACH attempts, wherein the number of ROs in the set is equal to the number of determined PRACH transmissions.

[0033] According to a fourth aspect of this disclosure, a network node is provided. The network node is configured to: determine the number of PRACH transmissions; determine the number K of PRACH transmission configurations; determine the number R of PRACH timings (ROs) associated with a selected SSB and associated with a preamble partition applicable to the determined number of PRACH transmissions within an association period; and determine an extended association period comprising X association periods, wherein the X association periods are such that... The minimum number of association periods; within the extended association period, a set of ROs for indexing is determined, wherein the ROs in the set of ROs are associated with the selected SSB and with the preamble partition applicable to the determined number of PRACH transmissions; the determined ROs in the set of ROs are indexed; the number of PRACH transmissions is received within the set of indexed ROs and associated with the PRACH attempts, wherein the number of ROs in the set is equal to the number of determined PRACH transmissions.

[0034] This disclosure proposes a solution for indexing multiple PRACH transmissions using RO (Relationship to Root) parameters to help the UE and gNB align on this set of ROs, allowing the gNB to combine them for a PRACH attempt. This disclosure also proposes a solution for PRACH transmissions in cases where there are overlapping ROs in the time domain between two PRACH configurations. Attached Figure Description

[0035] Figure 1A The signaling sequence for a four-step competition-based random access procedure is shown.

[0036] Figure 1B The signaling sequence for a two-step competition-based random access procedure is shown.

[0037] Figure 2A This illustrates a four-step random access type, contention-free random access.

[0038] Figure 2B This illustrates a two-step random access type, contention-free random access.

[0039] Figure 3 An example of RACH timing configuration in NR is shown.

[0040] Figure 4 An example of the mapping between SSB and RACH preamble is shown.

[0041] Figure 5 A diagram of an exemplary telecommunications network in which a UE and gNB may operate according to embodiments of the present disclosure is shown.

[0042] Figure 6 The PRACH configuration index in FR2 TDD is shown.

[0043] Figure 7 A flowchart is shown of an exemplary method at an end node for performing multiple PRACH transmissions for a PRACH attempt, according to an embodiment of the present disclosure.

[0044] Figure 8 A flowchart is shown of an exemplary method at a network node for receiving multiple PRACH transmissions for a PRACH attempt from an end node, according to an embodiment of the present disclosure.

[0045] Figure 9 shows the result of distributing PRACH transmission on RO according to an embodiment of the present disclosure.

[0046] Figure 10 This illustrates a scenario where there is temporal overlap (RO) between two PRACH configurations.

[0047] Figure 11 This is a flowchart illustrating an exemplary method at an end node for performing a PRACH transmission for a PRACH attempt, according to an embodiment of the present disclosure.

[0048] Figure 12 The results of applying an embodiment of this application are shown.

[0049] Figure 13 An embodiment of an arrangement that can be used in a terminal node or network node according to an embodiment of the present disclosure is illustrated schematically.

[0050] Figure 14This is a block diagram illustrating an exemplary terminal node according to an embodiment of the present disclosure.

[0051] Figure 15 This is a block diagram of an exemplary network node according to embodiments of the present disclosure.

[0052] Figure 16 This is a block diagram of an exemplary terminal node according to an embodiment of the present disclosure.

[0053] Figure 17 An example of a communication system 1700 according to some embodiments is shown.

[0054] Figure 18 A UE according to some embodiments is shown.

[0055] Figure 19 A UE according to some embodiments is shown.

[0056] Figure 20 This is a block diagram of the host 2000 based on the various aspects described in this document. The host can be... Figure 17 An embodiment of host 1716.

[0057] Figure 21 This is a block diagram illustrating a virtualized environment 2100 in which functionality implemented by some embodiments can be virtualized.

[0058] Figure 22 A communication diagram is shown of a host 2202 communicating with a UE 2206 via a network node 2204 through a partial wireless connection, according to some embodiments. Detailed Implementation

[0059] In the following description, the principles and spirit of this disclosure will be described with reference to illustrative embodiments. Some embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. Additional information may also be found in the following references:

[0060] 1) 3GPP TS 38.213 V17.5.0 (2023-03),

[0061] 2) 3GPP TS 38.321 V17.4.0 (2023-03),

[0062] 3) 3GPP TS 38.211 V17.4.0 (2022-12), and

[0063] 4) 3GPP TS 38.331 V17.4.0 (2023-03).

[0064] References to "an embodiment," "embodiment," "example embodiment," etc., in this specification indicate that the described embodiment may include a specific feature, structure, or characteristic, but not every embodiment must include that specific feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. Moreover, when a specific feature, structure, or characteristic is described in connection with an embodiment, it should be assumed that implementing such a feature, structure, or characteristic in conjunction with other embodiments (whether explicitly described or not) is within the knowledge of those skilled in the art.

[0065] Those skilled in the art will understand that the term "exemplary" is used herein to mean "illustrative" or "serves as an example" and is not intended to imply that a particular embodiment is superior to another or that a particular feature is essential. Similarly, unless the context clearly indicates otherwise, the terms "first," "second," "third," and "fourth," and similar terms, are used only to distinguish one particular instance of an item or feature from another particular instance, and do not indicate a particular order or arrangement. Furthermore, as used herein, the term "step" is intended to be synonymous with "operation" or "action." Unless the context or details of the described operations clearly indicate otherwise, any description of a sequence of steps herein does not imply that these operations must be performed in a particular order, or even in any arbitrary order.

[0066] Unless explicitly defined herein or understood from the context, the conditional language used herein (e.g., “can,” “may,” “can,” “for example,” etc.) is generally intended to convey that some embodiments include certain features, elements, and / or steps while other embodiments do not include said features, elements, and / or states. Therefore, such conditional language is not generally intended to imply that a feature, element, and / or step is necessary for one or more embodiments in any case, or to imply that one or more embodiments must include logic circuitry to determine, with or without the author’s input or permission, whether to include those features, elements, and / or states in any particular embodiment, or to perform said features, elements, and / or states in any particular embodiment. Furthermore, the term “or” is used in an inclusive sense (and not an exclusionary sense) such that when used, for example, to connect a list of elements, the term “or” indicates one, some, or all of the elements in the list. In addition to having its ordinary meaning, the term “each” as used herein may also mean any subset of the set of elements to which the term “each” is applied.

[0067] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context explicitly indicates otherwise. It will also be understood that, when used herein, the words “comprising,” “having,” “including,” etc., indicate the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. It will also be understood that, unless explicitly stated to the contrary, when used herein, the terms “connected,” “connected to,” “connected to,” etc., mean only that there is an electrical or communication connection between two elements and that they may be directly or indirectly connected.

[0068] Of course, this disclosure may be implemented in other specific ways than those set forth herein without departing from the scope and essence of this disclosure. One or more specific processes discussed below can be performed in any electronic device including one or more appropriately configured processing circuits, which in some exemplary embodiments may be embodied in one or more application-specific integrated circuits (ASICs). In some exemplary embodiments, these processing circuits may include one or more microprocessors, microcontrollers, and / or digital signal processors programmed with appropriate software and / or firmware to implement one or more of the above-described operations and variations thereof. In some exemplary embodiments, these processing circuits may include custom hardware performing one or more of the above-described functions. The presented embodiments should therefore be considered illustrative rather than restrictive in all respects.

[0069] Although various embodiments of this disclosure will be shown in the accompanying drawings and described in the following detailed description, it should be understood that this disclosure is not limited to the disclosed embodiments, but is capable of various rearrangements, modifications and substitutions without departing from the disclosure as set forth and defined in the appended claims.

[0070] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0071] The techniques described herein can be used in 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 illustrative purposes only, certain aspects of these techniques are described below with reference to 5G wireless communication networks. However, those skilled in the art will understand that the techniques described herein can also be used in other wireless networks, such as LTE and the corresponding radio technologies mentioned herein, as well as wireless networks and radio technologies proposed in the future.

[0072] One type of communication device is a wireless communication device, which can be any type of wireless device capable of accessing a wireless network (e.g., a cellular network) (i.e., served by a wireless network). Some examples of wireless communication devices include, but are not limited to: user equipment (UE) in 3GPP networks, machine-type communication (MTC) devices, and Internet of Things (IoT) devices.

[0073] As used herein, by way of example and not limitation, the term "UE" can refer to a user equipment (UE), SS (subscriber station), portable subscriber station (PSS), mobile station (MS), mobile terminal (MT), or access terminal (AT). A UE can include, but is not limited to, mobile phones, cellular phones, smartphones or personal digital assistants (PDAs), portable computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback devices, wearable terminal devices, vehicle-mounted wireless terminal devices, etc. In the following description, the terms "UE," "wireless communication device," "terminal device," "mobile terminal," and "user equipment" are used interchangeably.

[0074] As used in this article, "network node" refers to any node that is part of the radio access network or core network of a cellular communication network / system.

[0075] Figure 5 This is a diagram illustrating an exemplary telecommunications network 10 capable of operating UE #1 100-1, UE #2 100-2, and gNB 105 according to embodiments of the present disclosure. Although telecommunications network 10 is a network defined in the context of 5G NR, the present disclosure is not limited thereto.

[0076] like Figure 5As shown, network 10 may include one or more UEs 100-1 and 100-2 (collectively referred to as UE 100) and RAN node 105, which may be a base station, Node B, evolved Node B (eNB), gNB, or AN node providing access to the network for UE 100. Furthermore, network 10 may also include... Figure 5 The core network portion is not shown in the diagram.

[0077] However, this disclosure is not limited thereto. In some other embodiments, network 10 may include additional nodes, fewer nodes, or Figure 5 Some variations of existing nodes are shown. For example, in a network with a 4G architecture, the entity performing these functions (e.g., eNB) can interact with... Figure 5 The entities shown (e.g., gNB 105) are different. For example, in networks with a hybrid 4G / 5G architecture, some of these entities may differ from... Figure 5 The entities shown are the same, while others may be different.

[0078] Furthermore, despite Figure 5 Two UEs 100 and one gNB 105 are shown, but this disclosure is not limited thereto. In some other embodiments, any number of UEs and / or any number of gNBs may be included in network 10.

[0079] like Figure 5 As shown, UE 100 can communicatively connect to gNB 105, which in turn can communicatively connect to the corresponding core network (CN) and then to the Internet, so that UE 100 can ultimately transmit its user plane data to other devices outside network 10, for example, via gNB 105.

[0080] In 3GPP Release 18, multiple PRACH transmissions are provided, where the UE sends multiple PRACH attempts within a set of ROs (PRACH opportunities). The UE and gNB need to align on a specific set of ROs so that the gNB can combine them for RACH attempts and allow the UE and gNB to determine the start of the RAR window, RA-RNTI, etc. A simple solution for the UE to determine a set of ROs is based on RO indexing. Taking K PRACH transmissions as an example, the index of the starting RO can be determined by mod(starting RO index, K) = 0. It can be observed that RO indexing is required to support the UE in determining the ROs used for multiple PRACH transmissions. However, on the one hand, in NR releases prior to Release 18, RO indexing was only specified for CFRA, not CBRA. On the other hand, RO indexing for CFRA is specified for the following three scenarios, and applying it to the UE in determining a set of ROs for multiple PRACH transmissions will cause some problems or limitations. The reasons and related clauses are as follows.

[0081] - Scenario 1: RO index compilation is limited to 1 / N consecutive valid PRACH opportunities per SSB, provided that the UE is provided with a number associated with a PRACH opportunity. SS / PBCH blocks and .

[0082] -Scenario 2: The RO index used for SI requests is compiled within the association period.

[0083] -Scenario 3: If csirs-ResourceList is provided, the RO index is reset in each association pattern cycle.

[0084] This quote references a relevant section from 3GPP TS 38.213 V17.4.0, as shown below.

[0085]

[0086]

[0087] This quote references a relevant section from 3GPP TS 38.321 V17.2.0, as shown below.

[0088]

[0089]

[0090] This quote references a relevant section from 3GPP TS 38.331 V17.4.0, as shown below.

[0091] SI-RequestConfig information element

[0092]

[0093] According to the definition in 3GPP TS 38.213, the association period is the smallest time span among the time spans that support at least one SS / PBCH block index to PRACH timing mapping period. For example, as Figure 6 As shown, for PRACH configuration index 127 in FR2 TDD, if SCS is 120KHz, there are 8 ROs within a 10ms PRACH configuration cycle.

[0094] For multiple PRACH transmissions in version 18, it has been agreed that "for multiple PRACH transmissions using the same beam, at least one RO located at a different time instance can be used for transmission." In other words, multiple PRACH transmissions multiplexed in the time domain are supported. For simplicity, if there are multiple frequency-division multiplexed ROs associated with a single SSB, only one of them is considered at the time instance.

[0095] For example, we make some assumptions:

[0096] - There are two SSBs, namely SSB1 and SSB2;

[0097] - One half is provided by ssb-perRACH-OccasionAndCB-PreamblesPerSSB, indicating that an SSB is associated with two ROs.

[0098] Table 1 shows the SSB to RO mapping. There are four ROs associated with the SSB within the association period, and two of these ROs are consecutive. Based on CFRA RO indexing scenario 1, there are up to two RO indices. If the indexes start from 0, the four ROs associated with the SSB have corresponding indices of 0, 1, 0, and 1. In practice, if the four ROs have indices from 0 to 3, they can be used for the first, second, third, and fourth PRACH transfers in the RACH attempt. However, it is unclear how to support a greater than two number of PRACH transfers with indices of 0 and 1.

[0099] Since the number of ROs in the PRACH configuration cycle is sufficient for at least one SSB-RO mapping cycle, the association cycle is 10ms. For the selected SSB, such as SSB#1, one association cycle consists of two sets of ROs for two PRACH transmissions and one set of ROs for four PRACH transmissions, but it cannot accommodate one set of ROs for eight transmissions, which would otherwise be supported by ROs within two association cycles. In summary, one observation is that, advantageously, multiple PRACH transmissions attempted by RACH can span multiple association cycles, which is beyond the scope of CFRA RO indexing scenario 2.

[0100] Table 1: SS / PBCH block index to PRACH timing mapping, which includes two SSBs.

[0101]

[0102] Finally, if a set of ROs used for multiple PRACH transmissions in a RACH attempt spans X association periods, where the number of ROs associated with one SSB is sufficient to support multiple PRACH transmissions, then the value of X is determined based on the number of PRACH transmissions. In contrast, the number of association periods within an association pattern period in Scenario 3 is based on the SSB period. If the time span of X association periods is greater than the association pattern period, the CFRA RO indexing method in Scenario 3 will lead to the same problem mentioned above for Scenario 1.

[0103] The RO group discussed and reached a consensus in RAN1#112, and the relevant parts are cited below.

[0104]

[0105] Since it remains undetermined whether a group of ROs consists of multiple PRACH transmissions for one RACH attempt or several RACH attempts, in this IvD we use the term "group of ROs" to refer to an RO associated with multiple PRACH transmissions for one RACH attempt.

[0106] RAN1#112 also agrees that the gNB can configure multiple values ​​from {2, 4, 8} as possible numbers for multiple PRACH transmissions. How to differentiate PRACH resources between different numbers of transmissions requires future research. For example, the gNB could configure separate preamble partitions in the RO, or configure separate ROs for different numbers of PRACH transmissions. Other methods are not currently ruled out, such as configuring different numbers of PRACH transmissions within a single preamble partition.

[0107]

[0108] Regardless of the gNB configuration, the consensus is that a UE determining a specific number of PRACH transmissions will only transmit PRACHs in ROs that have a preamble partition suitable for its determined number of PRACH transmissions. A general implementation of RO counting and indexing is that the UE only counts ROs that have a preamble partition suitable for its determined number of PRACH transmissions. In other words, for indexing, ROs without a preamble for the UE's determined number of PRACH transmissions are not counted.

[0109] If the association period does not have enough Returns of Interest (ROs) associated with a SSB for a specific number of PRACH transmissions (configured by the gNB), the UE intending to perform that number of PRACH transmissions will search for ROs for the RACH attempt over at least a number of association periods. A minimum number 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 for the RACH attempt. X ≥ 1. For example, according to Table 1, the UE determines two association periods for 8 PRACH transmissions, one association period for 4 PRACH transmissions, and determines one of these two sets of ROs for 2 PRACH transmissions within one association period. Similar to the association periods, the X association periods also begin with radio frame 0.

[0110] Below, we provide the rules for RO counting and RO indexing, as well as the methods for determining X and RO indexing. Based on this, the UE can determine a set of ROs for RACH attempts.

[0111] Figure 7 This is a flowchart of an example method 700 for performing multiple PRACH transmissions for a PRACH attempt at an end node according to embodiments of the present disclosure. Method 700 can be performed at an end node (e.g., UE 100). Method 700 may include steps S710 to S740. However, the present disclosure is not limited thereto. In some other embodiments, method 700 may include more steps, fewer steps, different steps, or any combination thereof. Furthermore, the steps of method 700 may be performed in an order different from that described herein. Additionally, in some exemplary embodiments, the steps in method 700 may be broken down into multiple sub-steps and performed by different entities, and / or multiple steps in method 700 may be combined into a single step.

[0112] Method 700 may begin at step S710, where the number of PRACH transmissions is determined based on parameters received from the 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 a number from the configured numbers. For example, in the case of CBRA, the terminal node can determine the number of PRACH transmissions through its SSB measurement.

[0113] At step S720, the terminal node determines a set of ROs for indexing, wherein the ROs in the set of ROs are associated with the selected SSB and with the preamble partition applicable to the determined number of PRACH transmissions.

[0114] Then, in step S730, an index is created for the ROs in the group of ROs determined in step S720.

[0115] Finally, in step S740, the terminal node performs one or more PRACH transmissions within a set of indexed ROs based on the determined number of PRACH transmissions, wherein the number of ROs in the set is equal to the determined number of PRACH transmissions. The terminal node first determines a set of ROs (i.e., candidate ROs for performing PRACH transmissions), and then selects a set of ROs from this set for actually performing the PRACH transmissions.

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

[0117] In one embodiment, if at least a portion of the number of PRACH transmissions is multiplexed in the frequency domain, the step S720 of determining a set of ROs for indexing may include determining the number of ROs multiplexed in the frequency domain, which is equal to the number of PRACH transmissions multiplexed simultaneously in the frequency domain.

[0118] In one embodiment, method 700 may further include the following steps: determining the number of PRACH transmission configurations K; determining the number R of ROs associated with the selected SSB and the preamble partition applicable to the determined number of PRACH transmissions within an association period; and if the number R is less than the number K, determining an extended association period including a minimum number X of association periods, wherein, within X association periods, the number of ROs associated with the selected SSB and the preamble partition applicable to the determined number of PRACH transmissions is greater than or equal to the determined configuration number K, and wherein, within the extended association period, step S720 of determining a set of ROs and step S730 of indexing the set of ROs are performed.

[0119] In one embodiment, if the quantity R is greater than or equal to the quantity K, the quantity X is determined to be 1, and the steps S720 of determining a set of ROs and S730 of indexing the set of ROs are performed within the association period.

[0120] In one embodiment, the quantity K is the determined number of PRACH transmissions, or the maximum of a plurality of PRACH transmissions configured by the network node.

[0121] In one embodiment, method 700 may further include the steps of: determining the first frame of the first association period of the extended association period as the starting radio frame of the extended association period, and determining the frame immediately following the end of the extended association period as the starting radio frame of the next extended association period after the extended association period.

[0122] In one embodiment, if the number of ROs in the group of ROs is greater than the determined number of PRACH transmissions within the extended association period, then step S740 of performing one or more PRACH transmissions based on the determined number of PRACH transmissions within the group of indexed ROs may include the following steps: performing the one or more PRACH transmissions within a first number of ROs in the indexed ROs, the first number being equal to the number of the one or more PRACH transmissions; and repeating the PRACH transmissions in the one or more PRACH transmissions within the remaining ROs in the indexed ROs.

[0123] In one embodiment, if the number of ROs in the group of ROs is greater than the number of PRACH transmissions within an extended association period, then step S740 of performing one or more PRACH transmissions based on the determined number of PRACH transmissions within the group of indexed ROs may include the step of performing the one or more PRACH transmissions by distributing the one or more PRACH transmissions within the group of ROs such that the extension mode of the ROs used in each of the X association periods is the same.

[0124] In one embodiment, step S740 of performing one or more PRACH transmissions based on the determined number of PRACH transmissions in the indexed ROs may include the steps of: determining the transmission mode of the one or more PRACH transmissions; and performing the one or more PRACH transmissions by following the transmission mode.

[0125] In one embodiment, the transmission mode is identified by the frame number.

[0126] Figure 8 This is a flowchart of an example method 800 for receiving multiple PRACH transmissions from an end node at a network node according to embodiments of the present disclosure. Method 800 can be performed at a network node (e.g., gNB 105). Method 800 may include steps S810 to S840. However, the present disclosure is not limited thereto. In some other embodiments, method 800 may include more steps, fewer steps, different steps, or any combination thereof. Furthermore, the steps of method 800 may be performed in an order different from that described herein. Additionally, in some exemplary embodiments, the steps in method 800 may be broken down into multiple sub-steps and performed by different entities, and / or multiple steps in method 800 may be combined into a single step.

[0127] Method 800 may begin step S810, in which the number of PRACH transmissions is determined.

[0128] At step S820, the network node determines a set of ROs for indexing, wherein the ROs in the set of ROs are associated with the selected SSB and with the preamble partition applicable to the determined number of PRACH transmissions.

[0129] Then, in step S830, an index is created for the ROs in the group of ROs determined in step S820.

[0130] Finally, in step S840, the network node receives and associates the number of PRACH transmissions within a set of indexed ROs, wherein the number of ROs in the set is equal to the number of PRACH transmissions determined. The network node first determines a set of ROs (i.e., candidate ROs for receiving PRACH transmissions), and then selects a set of ROs from that set for actually receiving the PRACH transmissions.

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

[0132] In one embodiment, if at least a portion of the number of PRACH transmissions is multiplexed in the frequency domain, the step S820 of determining a set of ROs for indexing may include determining the number of ROs multiplexed in the frequency domain, which is equal to the number of PRACH transmissions multiplexed simultaneously in the frequency domain.

[0133] In one embodiment, method 800 may further include the following steps: determining the number of PRACH transmission configurations K; determining the number R of ROs associated with the selected SSB and the preamble partition applicable to the determined number of PRACH transmissions within an association period; and if the number R is less than the number K, determining an extended association period including a minimum number X of association periods, wherein within X association periods, the number of ROs associated with the selected SSB and the preamble partition applicable to the determined number of PRACH transmissions is greater than or equal to the determined configuration number K, and wherein step S820 of determining a set of ROs and step S830 of indexing the set of ROs are performed within the extended association period.

[0134] In one embodiment, if the quantity R is greater than or equal to the quantity K, the quantity X is determined to be 1, and the steps S820 of determining a set of ROs and S830 of indexing the set of ROs are performed within the association period.

[0135] In one embodiment, the quantity K is the determined number of PRACH transmissions, or the maximum of a plurality of PRACH transmissions configured by the network node.

[0136] In one embodiment, method 800 may further include the steps of: determining the first frame of a first association period of an extended association period as the starting radio frame of the extended association period, and determining the frame immediately following the end of the extended association period as the starting radio frame of the next extended association period after the extended association period.

[0137] In one embodiment, if the number of ROs in the group of ROs is greater than the determined number of PRACH transmissions within the extended association period, then step S840 of receiving and associating the number of PRACH transmissions within the group of indexed ROs may include the following steps: receiving the number of PRACH transmissions within 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 within the remaining ROs in the indexed ROs.

[0138] In one embodiment, if the number of ROs in the group of ROs is greater than the number of PRACH transmissions within an extended association period, then step S840 of receiving and associating the number of PRACH transmissions within the group of indexed ROs may include the following steps: receiving the number of PRACH transmissions distributed within the group of ROs, wherein the extension mode of the ROs used in each of the X association periods is the same.

[0139] In one embodiment, step S840 of receiving the number of PRACH transmissions within the indexed RO group may include the following steps: determining the transmission pattern of the number of PRACH transmissions; and receiving the number of PRACH transmissions by following the transmission pattern.

[0140] In one embodiment, the transmission mode is identified by the frame number.

[0141] The following are some embodiments of RO indexing so that the UE can determine a set of ROs for the PRACH attempt. Obviously, this application is not limited thereto.

[0142] Example 1: If, within X associated periods, there are multiple frequency-division multiplexed ROs associated with an SSB at a certain time instance, one or more of the following methods can be used.

[0143] For time-division multiplexed PRACH transmissions, at a given time instance, only one frequency-division multiplexed RO is included in the RO index and indexed.

[0144] For some or all of the PRACH transmissions multiplexed in the frequency domain, the number of frequency-division multiplexed ROs included in the RO index and indexed is equal to the number of simultaneous PRACH transmissions multiplexed in the frequency domain. For example, a UE with two Tx chains can transmit two PRACHs simultaneously in a total of two frequency-division multiplexed ROs. If more than two frequency-division multiplexed ROs are associated with the selected SSB, the UE includes two of these ROs in the RO index and then indexes them.

[0145] Example 2: For the selected number K of SSB and PRACH transmissions, the UE follows one or more of the following steps to determine X associated periods and index the RO.

[0146] 1> The number of ROs R associated with the selected SSB within the associated period is determined based on the counting rules in Example 1.

[0147] 2> If R≥K, then X=1.

[0148] 2> If R < K, determine X (X > 1), i.e., the minimum number of associated periods, such that the number of ROs associated with the selected SSB within X associated periods is not less than K.

[0149] 3> Determine the starting radio frames of the X associated periods such that mod(starting frame index, number of frames within X * associated period) = 0. In other words, the first X associated periods start from frame 0, and the next X associated periods start immediately after the end of the previous associated period, and so on.

[0150] 1> Based on the indexing rule in Embodiment 1, index the ROs associated with the selected SSB within the X associated periods. (Since the X associated periods span time and the frequency - division - multiplexed ROs are associated with one SSB, the rule in Embodiment 1 ensures that only the ROs to be counted are indexed.)

[0151] For a sub - embodiment of Embodiment 2, assuming that the gNB can configure multiple candidate numbers for PRACH transmission, one or more of the following options can be used to determine the number K of PRACH transmissions, which is used to determine the number X of associated periods.

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

[0153] - Option 2, K is the maximum number of multiple PRACH transmissions configured by the gNB

[0154] If the gNB configures {2, 4, 8} as the number of PRACH transmissions (also known as the PRACH repetition factor), the UE can determine one of them for CBRA by itself, or be configured with the repetition factor for CFRA. For Option 1, X is UE - specific and specific to the PRACH repetition factor. There can be three X values corresponding to the three configured PRACH repetition factors. In contrast, Option 2 will result in a cell - specific X that is the same for all UEs. The maximum RO index of Option 2 can be greater than that of Option 1, but Option 2 can be easier to standardize and implement.

[0155] When the determined number of PRACH transmissions is greater than the number of RO groups associated with the selected SSB within the association period, the UE transmits a subset of the transmissions within the first association period. The remaining transmissions are then transmitted on the same RO groups in the next association period. In one embodiment, if the number of PRACH transmissions is less than the number of existing ROs with the closest capacity matching the transmissions in the RO group or the association period (e.g., 4 transmissions distributed across 3+3 ROs), the number of PRACH transmissions can be increased to cover all ROs in that RO group, or only the determined number K can be transmitted. In the example, the determined number of transmissions is 4, but the RO group has 6 ROs within two association periods. In this example, the UE transmits more transmissions than the determined number to utilize all ROs in that RO group.

[0156] Distributing PRACH transmissions on RO can be done in several ways, for example:

[0157] - The same RO must be used within X associated periods, such as Figure 9A As shown.

[0158] - Each RO within X associated periods must be used, such as Figure 9B As shown.

[0159] In another embodiment, the RO group only allows combinations of two multi-transmission modes, and the mode is identified by the frame number. Both 8 and 4 transmissions are allowed to be sent within two RO groups of 4 ROs, but 4 transmissions will only be allowed to be sent on, for example, even frame numbers. This will allow the gNB to know that a transmission on an odd-numbered RO group is associated with an equal number of transmissions in the previous or next association period. This will also increase the probability of detecting at least a subset of the multiple PRACH transmissions. As a sub-implementation, the UE across the association period selects an even or odd preamble to indicate whether the transmission is performed as a first or second half of a series, as follows:

[0160]

[0161] This will help the gNB detect the multiple PRACH transports, as it will know which PRACH transport groups to combine.

[0162] Temporal overlap RO between the two RACH configurations

[0163] Another issue we are trying to address is the temporal overlap of ROs between traditional ROs and individual ROs. This is a legacy issue that has existed since the 2-step RACH in Release 16. For any feature that requires advance UE indication of PRACH, its configured ROs may conflict with traditional ROs used for a single PRACH transmission or with individual ROs configured for another feature. If the overlapping ROs are associated with different SSBs, a gNB using analog beamforming in FR2 will not be able to receive PRACH transmissions using different SSB beams.

[0164] We use a traditional single PRACH transport and multiple PRACH transports in version 18 as examples. One working assumption made in RAN1#112 is that a gNB can configure separate ROs for multiple PRACH transports. For example, separate ROs can be configured using the IE of AdditionalRACH-Config-r17. According to 38.331 V17.4.0, ssb-perRACH-OccasionAndCB-PreamblesPerSSB and msg1-FrequencyStart are configured independently for additional ROs.

[0165]

[0166]

[0167]

[0168] Figure 10Example configuration is shown in (a) where the ROs for a single PRACH transmission and multiple PRACH transmissions are fully overlapped in time but configured with different frequency resources. We assume two SSBs. The number N of SSBs associated with one RO, provided by ssb-perRACH-OccasionAndCB-PreamblesPerSSB, is one for the RO of a single PRACH and half for the RO of multiple PRACH transmissions. (With this configuration, a single PRACH transmission will not consume excessive RACH resources, and for the selected SSB, the two PRACH transmissions attempted by the RACH can occur in consecutive time-domain ROs with short delays.) It can be seen that within timings 2 and 3, the two frequency-division multiplexed ROs are associated with different SSBs. This is not a problem for gNBs capable of receiving simultaneously in different directions. However, gNBs using analog beamforming can only receive within one RO at a time using the associated SSB beam, while PRACH transmissions sent in the FDM RO associated with the other SSB are lost. The gNB may choose to receive the RO configured for a single PRACH transmission, rather than accepting ROs used for multiple PRACH transmissions, because losing one of multiple PRACH transmissions is more acceptable than losing one of a single PRACH transmission. Lost ROs in Figure 10 (b) is crossed out.

[0169] Figure 11 This is a flowchart of an example method 1100 for performing a PRACH transmission for a PRACH attempt at an end node according to embodiments of the present disclosure. Method 1100 can be performed at an end node (e.g., UE 100). Method 1100 may include steps S1110 to S1140. However, the present disclosure is not limited thereto. In some other embodiments, method 1100 may include more steps, fewer steps, different steps, or any combination thereof. Furthermore, the steps of method 1100 may be performed in an order different from that described herein. Additionally, in some exemplary embodiments, the steps in method 1100 may be broken down into multiple sub-steps and performed by different entities, and / or multiple steps in method 1100 may be combined into a single step.

[0170] Method 1100 may begin at step S1110, wherein a first PRACH configuration is received from a network node. The first PRACH configuration configures a first group of ROs and includes a first SSB mapping indication indicating the mapping of SSBs to ROs.

[0171] At step S1120, the terminal node receives a second PRACH configuration from the network node. The second PRACH configuration configures a second group of ROs and includes a second SSB mapping indication indicating the mapping from SSBs to ROs.

[0172] Then, in step S1130, the network node determines whether at least one RO associated with an SSB according to the first PRACH configuration overlaps in the time domain with ROs associated with different SSBs according to the second PRACH configuration.

[0173] Finally, in step S1140, in response to determining that at least one RO associated with an SSB according to the first PRACH configuration overlaps in the time domain with ROs associated with different SSBs according to the second PRACH configuration, the network node determines the ROs for PRACH transmission.

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

[0175] In one embodiment, if time-overlapping ROs are configured with different priorities, it is determined that network nodes cannot simultaneously receive PRACH transmissions using different SSB beams, and in this case, the network node only receives PRACH transmissions from the RO with the higher priority.

[0176] In one embodiment, if the RO selected by the end node for the RACH configuration for PRACH transmission has a lower priority, the step S1140 of determining the RO for PRACH transmission may include the step of determining the RO for PRACH transmission.

[0177] In one embodiment, the step of determining the RO for PRACH transmission may include the following steps: determining the RO mapped to the SSB based on a received first PRACH configuration and a second PRACH configuration, wherein a time-overlapping RO with a lower priority is not associated with an SSB that is different from the SSB associated with a time-overlapping RO with a higher priority.

[0178] In one embodiment, the step of determining the RO for PRACH transmission may include the step of not counting lower-priority time-overlapping ROs when determining the RO.

[0179] The following are some embodiments of RO selection in the case of overlapping time-domain ROs between two RACH configurations, so that the UE can determine the RO for the PRACH attempt. Obviously, this application is not limited thereto.

[0180] The time-domain overlap RO between the two RACH configurations can be configured with different frequency resources or the same frequency resources.

[0181] In Example 1, the gNB can be configured to indicate whether it can simultaneously receive signals using different SSB beams.

[0182] One sub-example: The gNB can configure priorities for ROs in the RACH configuration. If time-overlapping ROs are associated with different SSBs and configured with different priorities, this means that the gNB cannot simultaneously receive ROs associated with different SSBs, and the RO with the lower priority will be lost. The lack of priority configuration for time-overlapping ROs or the configuration of the same priority for time-overlapping ROs indicates that the gNB can use different SSB beams to simultaneously receive the ROs.

[0183] The UE typically performs the following two steps before PRACH transmission, and based on these steps, we provide some options:

[0184] 1) Associate the RO with the SSB index based on ssb-perRACH-OccasionAndCB-PreamblesPerSSB (Mapping from SSB index to RO).

[0185] 2) For the selected SSB, determine the RO used for PRACH transmission.

[0186] Example 2: If time-domain overlapping ROs are associated with different SSBs, and a UE that plans to send PRACH in a low-priority RO knows that the gNB cannot simultaneously receive the RO in which it will send, one or more of the following options can be taken to prevent the gNB from losing the RO.

[0187] Option 1 allows the UE to re-execute the SSB index to RO mapping for low-priority ROs. It will not associate low-priority ROs with SSB indices that are different from those of high-priority time-overlapping ROs. In other words, some low-priority ROs will not be associated with that SSB index unless the SSB index is the same as the SSB index used for time-overlapping high-priority ROs.

[0188] - Option 2: For a set of ROs determined for multiple PRACH transmissions, time-domain overlapping ROs with low priority are not counted, meaning the UE can find another RO to compensate for the uncounted RO.

[0189] - Option 3: The UE does not transmit within time-domain overlapped ROs with low priority.

[0190] The results of applying these options are Figure 12 (a) and Figure 12 As shown in (b). Specifically, Figure 12 (a) shows the result of applying option 1, and Figure 12(b) illustrates the result of applying option 2. Assume that the ROs used for multiple PRACH transmissions have lower priority. Using option 1, after the UE identifies different SSB indices within timing 2, it re-executes SSB-RO mapping for the low-priority ROs configured for multiple PRACH transmissions. By configuring ssb-perRACH-OccasionAndCB-PreamblesPerSSB to half, each SSB is associated with two ROs. To map the ROs in frequency resource 2, the UE skips the ROs in timing 2 and associates the RO in timing 3 with SSB1, which is the same SSB index in frequency resource 1 used for time-overlapping ROs. After mapping an RO for SSB2 in timing 4, the next RO is in timing 6, and the RO in timing 5 is not associated with an SSB. Using option 2, since the UE knows that PRACH transmissions with frequency resource 2 and in timings 2, 3, 6, and 7 will not be received by the gNB, it selects the ROs that can be received by the gNB for its transmission. Taking two PRACH transmissions in a RACH attempt as an example, the two non-contiguous ROs associated with the SSB form a set of ROs for the RACH attempt.

[0191] Figure 13 An embodiment of arrangement 1300 according to embodiments of the present disclosure is illustrated schematically, which can be used in a terminal node (e.g., UE 100) or a network node (e.g., gNB 105).

[0192] Arrangement 1300 includes a control unit or processing unit 1303, for example, having a digital signal processor (DSP) or a central processing unit (CPU). Processing unit 1303 may be a single unit or multiple units for performing different actions of the processes described herein by executing a computer program. The computer program may be stored in memory 1305. Memory 1305 may be any combination of RAM (random access memory) and ROM (read-only memory). Memory may also include permanent memory, which may be, for example, any one or a combination of magnetic storage, optical storage, or solid-state storage, or even remotely mounted storage.

[0193] Arrangement 1300 may also include a communication interface 1301 arranged for communication. Communication interface 1301 may be implemented as an input unit for receiving signals from other entities and an output unit for providing signals to other entities. Communication interface 1301 may also be implemented as an integrated entity or a separate entity.

[0194] The computer program includes code / computer-readable instructions that, when executed by the processing unit 1303 in arrangement 400, cause arrangement 1300 or a terminal node / network node including arrangement 1300 to perform, for example, previously combined Figure 7 , Figure 8 and Figure 11 Or the action of the process described by any other variant.

[0195] A computer program can be configured as computer program code constructed from computer program modules. Therefore, in an exemplary embodiment, when arrangement 1300 is used in an end node, the code in the computer program of arrangement 1300 includes: a module configured to determine the number of PRACH transmissions based on parameters received from a network node; a module configured to determine a set of ROs for indexing, wherein the ROs in the set of ROs are 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 set of ROs; and a module configured to perform one or more PRACH transmissions within the set of indexed ROs based on the determined number of PRACH transmissions, wherein the number of ROs in the set is equal to the determined number of PRACH transmissions.

[0196] Additionally or alternatively, in an exemplary embodiment, when arrangement 1300 is used in a network node, the code in the computer program of arrangement 1300 includes: a module configured to determine the number of PRACH transmissions; a module configured to determine a set of ROs for indexing, wherein the ROs in the set of ROs are 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 set of ROs; and a module configured to receive and associate the determined number of PRACH transmissions within a set of indexed ROs, wherein the number of ROs in the set is equal to the determined number of PRACH transmissions.

[0197] Additionally or alternatively, in an exemplary embodiment, when arrangement 1300 is used in a terminal node, the code in the computer program of arrangement 1300 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 includes a first SSB mapping indication indicating a mapping from SSB to RO; 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 includes a second SSB mapping indication indicating a mapping from SSB to RO; a module configured to determine whether at least one RO associated with an SSB according to the first PRACH configuration overlaps in the time domain with an RO associated with a different SSB according to the second PRACH configuration; and a module configured to: determine an RO for PRACH transmission in response to determining that at least one RO associated with an SSB according to the first PRACH configuration overlaps in the time domain with an RO associated with a different SSB according to the second PRACH configuration.

[0198] Computer program modules are basically executable. Figure 7 , Figure 8 and Figure 11 The actions of the illustrated process are used to simulate terminal nodes or network nodes. In other words, when different computer program modules are executed in the processing unit 1103, these computer program modules can correspond to different modules in the terminal node or network node.

[0199] Despite the above combination Figure 13 In the disclosed embodiments, the code means are implemented as a computer program module (which, when executed in a processor, causes the arrangement to perform the actions described above in conjunction with the accompanying drawings), but in alternative embodiments, at least one code means may be implemented as hardware circuitry, at least in part.

[0200] This disclosure also provides at least one computer program product in the form of non-volatile or volatile memory, such as a non-transitory computer-readable storage medium, electrically erasable programmable read-only memory (EEPROM), flash memory, and hard disk drive. The computer program product includes a computer program. The computer program includes: code / computer-readable instructions that, when executed by processor 1303, cause arrangement 1300 to perform, for example, the aforementioned... Figure 7 The described process actions; or code / computer-readable instructions that, when executed by processor 1303, cause arrangement 1300 to perform, for example, in conjunction with the preceding... Figure 8 The described process involves actions; code / computer-readable instructions that, when executed by processor 1303, cause arrangement 1300 to perform actions, for example, in conjunction with the preceding... Figure 11 The actions described in the process.

[0201] Computer program products can be configured as computer program code constructed from computer program modules. Computer program modules are essentially executable. Figure 7 , Figure 8 or Figure 11 The actions of the process shown.

[0202] The processor may be a single CPU (Central Processing Unit), but may also include two or more processing units. For example, the processor may include a general-purpose microprocessor, an instruction set processor, and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)). The processor may also include onboard memory for caching purposes. The computer program may be carried by a computer program product associated with the processor. The computer program product may include a computer-readable medium on which the computer program is stored. For example, the computer program product may be flash memory, random access memory (RAM), read-only memory (ROM), or EEPROM, and in alternative embodiments, the aforementioned computer program modules may be distributed across different computer program products in the form of memory within terminal nodes and / or network nodes.

[0203] An exemplary terminal node is provided in correspondence with the method 700 described above. Figure 14 This is a block diagram of a terminal node 1400 according to an embodiment of the present disclosure. In some embodiments, the terminal node 1400 may be, for example, a UE 100.

[0204] Terminal node 1400 can be configured to perform the above combination Figure 7 The described method 700. (e.g.) Figure 14 As shown, the terminal node 1400 may include: a receiving module 1410 configured to determine the number of PRACH transmissions based on parameters received from the network node and to determine a set of ROs for indexing, wherein the ROs in the set of ROs are 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 determined ROs in the set of ROs; and a sending module 1430 configured to perform one or more PRACH transmissions within the set of indexed ROs based on the determined number of PRACH transmissions, wherein the number of ROs in the set is equal to the determined number of PRACH transmissions.

[0205] Modules 1410, 1420, and / or 1430 described above can be implemented as a purely hardware solution or as a combination of software and hardware, for example, by one or more of the following: configured to perform the above description and, for example, in Figure 7The processor or microprocessor and appropriate software shown herein, along with memory, programmable logic device (PLD), or other electronic components or processing circuitry for storing the software, are described. Furthermore, the terminal node 1400 may include one or more additional modules, each of which may execute the reference... Figure 7 Any step of the described method 700.

[0206] A network node is provided in accordance with the method 800 described above. Figure 15 This is a block diagram of an exemplary network node 1500 according to embodiments of the present disclosure. In some embodiments, network node 1500 may be, for example, a gNB 105.

[0207] Network node 1500 can be configured to perform the above combination Figure 8 The described method 800. (e.g.) Figure 15 As shown, network node 1500 may include a determining module 1510 configured to determine the number of PRACH transmissions and determine a set of ROs for indexing, wherein the ROs in the set of ROs are 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 determined ROs in the set of ROs; and a receiving module 1530 configured to receive and associate the number of PRACH transmissions within the set of indexed ROs, wherein the number of ROs in the set is equal to the determined number of PRACH transmissions.

[0208] The modules 1510, 1520, and / or 15300 described above can be implemented as a pure hardware solution or as a combination of software and hardware, for example, by one or more of the following: configured to perform the above description and, for example, in Figure 8 The processor or microprocessor and appropriate software shown herein, along with memory, PLD, or other electronic components or processing circuitry for storing the software, are described. Furthermore, network node 1500 may include one or more additional modules, each of which may execute the reference... Figure 8 Any step of the described method 900.

[0209] An exemplary terminal node is provided in correspondence with method 1100 as described above. Figure 16 This is a block diagram of a terminal node 1600 according to an embodiment of the present disclosure. In some embodiments, the terminal node 1600 may be, for example, a UE 100.

[0210] Terminal node 1600 can be configured to execute the above combination Figure 11 The described method 1100. (e.g.) Figure 16As shown, the terminal node 1600 may include: a receiving module 1610 configured to receive a first PRACH configuration from a network node, wherein the first PRACH configuration configures a first set of ROs and includes a first SSB mapping indication indicating the mapping from SSBs to ROs; and a second PRACH configuration from a network node, wherein the first PRACH configuration configures a second set of ROs and includes a second SSB mapping indication indicating the mapping from SSBs to ROs; and a determining module 1620 configured to: determine whether at least one RO associated with an SSB according to the first PRACH configuration overlaps in the time domain with ROs associated with different SSBs according to the second PRACH configuration; and in response to determining that at least one RO associated with an SSB according to the first PRACH configuration overlaps in the time domain with ROs associated with different SSBs according to the second PRACH configuration, determine ROs for PRACH transmission.

[0211] Modules 1610 and / or 1620 described above can be implemented as a pure hardware solution or as a combination of software and hardware, for example, by one or more of the following: configured to perform the above description and, for example, in Figure 11 The processor or microprocessor and appropriate software shown herein, along with memory, programmable logic device (PLD), or other electronic components or processing circuitry for storing the software, are described. Furthermore, the terminal node 1600 may include one or more additional modules, each of which may execute the reference... Figure 11 Any step of the described method 1100.

[0212] Figure 17 An example of a communication system 1700 according to some embodiments is shown.

[0213] In this example, the communication system 1700 includes: a telecommunications network 1702, including an access network 1704 such as a radio access network (RAN); and a core network 1706, including one or more core network nodes 1708. The access network 1704 includes one or more access network nodes, such as network nodes 1710a and 1710b (one or more of which may generally be referred to as network node 1710), or any other similar 3GPP access node or non-3GPP access point. Network node 1710 facilitates direct or indirect connections of user equipment (UEs), for example, connecting UEs 1712a, 1712b, 1712c, and 1712d (one or more of which may generally be referred to as UE 1712) to the core network 1706 via one or more wireless connections.

[0214] Examples of wireless communication via wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information without using wiring, cables, or other conductors. Furthermore, in various embodiments, communication system 1700 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that can facilitate or participate in the communication of data and / or signals (whether via wired or wireless connections). Communication system 1700 may include any type of communication, telecommunications, data, cellular, radio network, and / or other similar system, and / or interface with any type of communication, telecommunications, data, cellular, radio network, and / or other similar system.

[0215] UE 1712 can be any of a wide variety of communication devices, including wireless devices that are arranged, configured, and / or operable to communicate wirelessly with network node 1710 and other communication devices. Similarly, network node 1710 is arranged, capable, configured, and / or operable to communicate directly or indirectly with UE 1712 and / or with other network nodes or devices in telecommunication network 1702 to achieve and / or provide network access (e.g., wireless network access) and / or to perform other functions in telecommunication network 1702 (e.g., management).

[0216] In the depicted example, core network 1706 connects network node 1710 to one or more hosts (such as host 1716). These connections can be direct connections or indirect connections via one or more intermediate networks or devices. In other examples, network nodes may be directly coupled to hosts. Core network 1706 includes one or more core network nodes (e.g., core network node 1708) that are formed together with hardware and software components. The characteristics of these components may be substantially similar to those described with respect to UEs, network nodes, and / or hosts, such that the description is generally applicable to the corresponding components of core network node 1708. Example core network nodes include the functions of one or more of the following: 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 Unhiding Function (SIDF), Unified Data Management (UDM), Secure Edge Protection Agent (SEPP), Network Open Function (NEF), and / or User Plane Function (UPF).

[0217] Host 1716 may be owned or under the control of a service provider other than the operator or provider of access network 1704 and / or 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 real-time and pre-recorded audio / video content, data collection services (e.g., retrieving and compiling data about various environmental conditions detected by multiple UEs), analytics functions, social media, functions for controlling or otherwise interacting with remote devices, functions for alarm and monitoring centers, or any other such functions performed by a server.

[0218] As a whole, Figure 18 The communication system 1700 enables connectivity between the UE, 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, including but not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications 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 Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi); and / or any other suitable wireless communication standards, such as Global Microwave Access Interoperability (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.

[0219] In some examples, telecommunications network 1702 is a cellular network implementing 3GPP standardized features. Therefore, telecommunications network 1702 can support network slicing to provide different logical networks to different devices connected to it. For example, telecommunications network 1702 can provide ultra-reliable low-latency communication (URLLC) services to some UEs while providing enhanced mobile broadband (eMBB) services to other UEs, and / or massive machine-type communication (mMTC) / massive IoT services to yet another UE.

[0220] In some examples, UE 1712 is configured to send and / or receive information without direct human interaction. For example, the UE may be designed to send information to access network 1704 according to a predetermined schedule when triggered by internal or external events or in response to a request from access network 1704. Additionally, the UE may be configured to operate in single-RAT mode, multi-RAT mode, or multi-standard mode. For example, the UE may operate using any one or a combination of Wi-Fi, NR (New Radio), and LTE, i.e., configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) New Radio Dual Connectivity (EN-DC).

[0221] In this example, hub 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, hub 1714 may be a controller, router, content source and analyzer, or any other communication device described herein relating to the UE. For example, hub 1714 may be a broadband router that enables the UE to access core network 1706. As another example, hub 1714 may be a controller that sends commands or instructions to one or more actuators of the UE. Commands or instructions may be received from the UE, network node 1710, or via executable code, scripts, procedures, or other instructions in hub 1714. As another example, hub 1714 may be a data collector that acts as a temporary storage device for UE data, and in some embodiments, may perform data analysis or other processing. As another example, hub 1714 may be a content source. For example, for a UE acting as a VR headset, display, speaker, or other media delivery device, hub 1714 can retrieve VR assets, video, audio, or other media or data related to perceived information via a network node, and then provide them directly to the UE after performing local processing and / or adding additional local content. In yet another example, hub 1714 acts as a proxy server or orchestrator for the UE, particularly if one or more UEs are low-power IoT devices.

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

[0223] Figure 18 A UE 1800 according to some embodiments is illustrated. As used herein, a UE refers to a device capable of, configured, positioned, and / or operable to wirelessly communicate with network nodes and / or other UEs. Examples of UEs include, but are not limited to, smartphones, mobile phones, cellular phones, Voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptop computers, laptop embedded devices (LEEs), laptop-mounted devices (LMEs), smart devices, wireless client devices (CPEs), vehicle-mounted or vehicle-embedded / integrated wireless devices, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including Narrowband Internet of Things (NB-IoT) UEs, Machine Type Communication (MTC) UEs, and / or Enhanced MTC (eMTC) UEs.

[0224] The UE can support device-to-device (D2D) communication, for example, by implementing 3GPP standards for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, the UE may not necessarily be a user in the sense of a human user who owns and / or operates the associated device. Alternatively, the UE may represent a device intended to be sold to or operated by a human user but which may not or initially may not be associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, the UE may represent a device not intended to be sold to or operated by an end user but which may be associated with or operated for the benefit of the user (e.g., a smart power meter).

[0225] UE 1800 includes processing circuitry 1802, which is operatively coupled via bus 1804 to input / output interface 1806, power supply 1808, memory 1810, communication interface 1812, and / or any other component or any combination thereof. Some UEs may utilize... Figure 18 The components shown may be all or a subset. The level of integration between components can vary depending on the UE. Furthermore, some UEs may include multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0226] Processing circuitry 1802 is configured to process instructions and data and can be configured to implement any sequential state machine operable to execute instructions stored in memory 1810 as machine-readable computer processes. Processing circuitry 1802 can be implemented as: one or more hardware-implemented state machines (e.g., implemented with discrete logic, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer processes, general-purpose processors (e.g., microprocessors or digital signal processors (DSPs)) together with appropriate software; or any combination of the foregoing. For example, processing circuitry 1802 may include multiple central processing units (CPUs).

[0227] In the example, input / output interface 1806 can be configured to provide one or more interfaces to input devices, output devices, or one or more input and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, transmitters, smart cards, other output devices, or any combination thereof. Input devices can allow users to capture information into UE 1800. Examples of input devices include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital camcorders, webcams, etc.), microphones, sensors, mice, trackballs, directional keyboards, touchpads, scroll wheels, smart cards, etc. Presence-sensitive displays may include capacitive or resistive touch sensors to sense input from the user. Sensors may be, for example, accelerometers, gyroscopes, tilt sensors, force sensors, magnetometers, optical sensors, proximity sensors, biometric sensors, etc., or any combination thereof. Output devices can use the same type of interface port as input devices. For example, a Universal Serial Bus (USB) port can be used to provide both input and output devices.

[0228] In some embodiments, power supply 1808 is configured as a battery or battery pack. Other types of power sources can be used, such as external power sources (e.g., power outlets), photovoltaic devices, or batteries. Power supply 1808 may also include power supply circuitry for delivering power from power supply 1808 itself and / or an external power source to various parts of UE 1800 via input circuitry or an interface such as a power cable. The delivery of power can, for example, be used for charging power supply 1808. The power supply circuitry can perform any formatting, conversion, or other modifications on the power from power supply 1808 to suit the power for the corresponding components of UE 1800 to which it is supplied power.

[0229] Memory 1810 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), disk, optical disk, hard disk, removable magnetic tape, flash drive, etc. In one example, memory 1810 includes one or more application processes 1814, such as an operating system, web browser application, widget, utility engine, or other application, and corresponding data 1816. Memory 1810 may store any one or a combination of various operating systems used by UE 1800.

[0230] The memory 1810 can be configured to include multiple physical drive units, such as a redundant array of independent disks (RAID), flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital multifunction optical disc (HD-DVD) drive, an internal hard drive, a Blu-ray disc drive, a holographic digital data storage (HDDS) disc drive, an external mini dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro DIMM SDRAM, smart card memory (e.g., a tamper-proof module in the form of a universal integrated circuit card (UICC), including one or more subscriber identification modules (SIMs), such as USIM and / or 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 referred to as a "SIM card." The memory 1810 can allow the UE 1800 to access instructions, applications, etc., stored on transient or non-transient storage media to offload or upload data. Articles of manufacture, such as those utilizing a communication system, may be tangibly embodied in or contained in memory 1810, which may be or include a device-readable storage medium.

[0231] Processing circuitry 1802 can be configured to communicate with an access network or other network using communication interface 1812. Communication interface 1812 may include one or more communication subsystems and may include or be communicatively coupled to antenna 1822. Communication interface 1812 may include one or more transceivers for communication, such as communication with one or more remote transceivers capable of wireless communication (e.g., another UE or a network node in the access network). Each transceiver may include a transmitter 1818 and / or a receiver 1820 suitable for providing network communication (e.g., optical, electrical, frequency allocation, etc.). Furthermore, transmitter 1818 and receiver 1820 may be coupled to one or more antennas (e.g., antenna 1822) and may share circuitry, software, or firmware, or alternatively, be implemented separately.

[0232] In the illustrated embodiment, the communication functions of the communication interface 1812 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication (e.g., using a Global Positioning System (GPS) to determine location), another type of communication function, or any combination thereof. Communication may be implemented according to one or more communication protocols and / or standards (e.g., IEEE 802.11, Code Division Multiple Access (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), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), etc.).

[0233] Regardless of the sensor type, the UE can provide the output of data captured by its sensors via its communication interface 1812 through a wireless connection with a network node. Data captured by the UE's sensors can be transmitted via another UE through the same wireless connection. The output can be periodic (e.g., every 15 minutes if it reports the sensed temperature), random (e.g., to balance the load of reports from several sensors), responsive to a triggering event (e.g., sending an alarm when humidity is detected), responsive to a request (e.g., a user-initiated request), or a continuous stream (e.g., real-time video feed of a patient).

[0234] As another example, the UE includes actuators, motors, or switches associated with a communication interface configured to receive wireless input from a network node via a wireless connection. The state of the actuator, motor, or switch can change in response to the received wireless input. For example, the UE may include a motor that adjusts the control surfaces or rotors of a flying drone based on the received input, or adjusts a robotic arm performing a medical procedure based on the received input.

[0235] When the UE is in the form of an Internet of Things (IoT) device, the UE can be a device used in one or more application areas, including but not limited to urban wearable technology, extended industrial applications, and healthcare. Non-limiting examples of such IoT devices include or embedded in the following devices: connected refrigerators or freezers, televisions, connected lighting devices, electricity meters, robotic vacuum cleaners, voice-controlled smart speakers, home security cameras, motion detectors, thermostats, smoke detectors, door and window sensors, flood / humidity sensors, electronic door locks, connected doorbells, air conditioning systems (such as heat pumps), autonomous vehicles, surveillance systems, weather monitoring devices, vehicle parking monitoring devices, electric vehicle charging stations, smartwatches, fitness trackers, head-mounted displays for augmented reality (AR) or virtual reality (VR), wearable devices for haptic or sensory enhancement, sprinklers, animal or item tracking devices, sensors for monitoring plants or animals, industrial robots, unmanned aerial vehicles (UAVs), and any kind of medical device (such as heart rate monitors or remote-controlled surgical robots). In addition to the above... Figure 18 In addition to the other components described in the UE 1800 shown, a UE in the form of an IoT device also includes circuitry and / or software depending on the intended application of the IoT device.

[0236] As another specific example, in an IoT scenario, a UE can represent a machine or other device that performs monitoring and / or measurement and sends the results of such monitoring and / or measurement to another UE and / or network node. In this case, the UE can be an M2M device, which can be referred to as an MTC device in the 3GPP context. As a specific example, the UE can implement the 3GPP NB-IoT standard. In other scenarios, a UE can represent a vehicle (e.g., a car, bus, truck, ship, and aircraft) or other device capable of monitoring and / or reporting its operational status or other functions associated with its operation.

[0237] In practice, any number of UEs can be used together for a single use case. For example, the first UE can be a drone or integrated into a drone, and provides the drone's speed information (obtained via a speed sensor) to a second UE, which is a remote controller for operating the drone. When the user makes a change from the remote controller, the first UE can adjust the throttle on the drone (e.g., by controlling the actuators) to increase or decrease the drone's speed. The first UE and / or the second UE can also include more than one of the functions described above. For example, the UE can include sensors and actuators, and handle data communication between both the speed sensor and the actuators.

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

[0239] Base stations can be classified based on the coverage they provide (or, in other words, their transmission power levels); therefore, depending on the coverage provided, a base station can be called a femtobase, picobase, microbase, or macrobase. A base station can be a relay node or a relay donor node controlling a relay. Network nodes can also include one or more (or all) portions of a distributed radio base station, such as centralized digital units and / or remote radio units (RRUs), sometimes referred to as remote radio headends (RRHs). These remote radio units can be integrated with an antenna to form an antenna-integrated radio, or they can be independent of an antenna integration. A portion of a distributed radio base station can also be referred to as a node in a distributed antenna system (DAS).

[0240] Other examples of network nodes include multi-transmitter point (multi-TRP) 5G access nodes, multi-standard radio (MSR) devices (e.g., MSR BS), network controllers (e.g., radio network controllers (RNC) or base station controllers (BSC)), base transceiver stations (BTS), transmitter points, transmitter nodes, multi-cell / multicast coordination entities (MCE), operations and maintenance (O&M) nodes, operations support system (OSS) nodes, self-organizing network (SON) nodes, location nodes (e.g., evolved Serving Mobility Location Center (E-SMLC)) and / or minimized drive test (MDT).

[0241] Network node 1900 includes processing circuitry 1902, memory 1904, communication interface 1906, and power supply 1908. Network node 1900 may consist of multiple physically separate components (e.g., Node B components and RNC components, BTS components and BSC components, etc.), each with its own corresponding components. In some scenarios where network node 1900 includes multiple separate components (e.g., BTS and BSC components), one or more separate components may be shared among several network nodes. For example, a single RNC can control multiple NodeBs. In such scenarios, each unique “NodeB and RNC pair” can be considered a single, separate network node in some cases. In some embodiments, network node 1900 may be configured to support multiple Radio Access Technologies (RATs). In such embodiments, some components may be replicated (e.g., separate memory 1904 exists for different RATs), and some components may be reused (e.g., the same antenna 1910 may be shared by different RATs). Network node 1900 may also include multiple sets of various components shown for different wireless technologies (e.g., GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, RFID, or Bluetooth wireless technologies). These wireless technologies may be integrated into the same or different chips or chipsets and other components within network node 1900.

[0242] The processing circuitry 1902 may include one or more of the following: a microprocessor, a controller, a central processing unit, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or coding logic, operable to provide network node 1900 functionality, either alone or in combination with other network node 1900 components (e.g., memory 1904).

[0243] In some embodiments, the processing circuitry 1902 includes a system-on-a-chip (SOC). In some embodiments, the processing circuitry 1902 includes one or more of a radio frequency (RF) transceiver circuitry 1912 and a baseband processing circuitry 1914. In some embodiments, the RF transceiver circuitry 1912 and the baseband processing circuitry 1914 may be on separate chips (or chipsets), boards, or units (e.g., radio units and digital units). In alternative embodiments, some or all of the RF transceiver circuitry 1912 and the baseband processing circuitry 1914 may be on the same chip or chipset, board, or unit group.

[0244] Memory 1904 may include any form of volatile or non-volatile computer-readable memory, including but not limited to permanent storage devices, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drives, optical discs (CDs), or digital video discs (DVDs)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions that can be used by processing circuitry 1902. Memory 1904 may store any suitable instructions, data, or information, including computer processes, software, applications including logic, rules, codes, tables, and / or other instructions that can be executed by processing circuitry 1902 and used by network node 1900. Memory 1904 may be used to store any calculations performed by processing circuitry 1902 and / or any data received via communication interface 1906. In some embodiments, processing circuitry 1902 and memory 1904 are integrated together.

[0245] Communication interface 1906 is used for wired or wireless communication of signaling and / or data between network nodes, access networks, and / or UEs. As shown, communication interface 1906 includes a port / terminal 1916 for transmitting and receiving data to and from the network, for example, via a wired connection. Communication interface 1906 also includes radio front-end circuitry 1918, which may be coupled to antenna 1910, or in some embodiments, to a portion of antenna 1910. Radio front-end circuitry 1918 includes a filter 1920 and an amplifier 1922. Radio front-end circuitry 1918 may be connected to antenna 1910 and processing circuitry 1902. Radio front-end circuitry 1918 may be configured to modulate the signal transmitted between antenna 1910 and processing circuitry 1902. Radio front-end circuitry 1918 may receive digital data to be transmitted to other network nodes or UEs via a wireless connection. Radio front-end circuitry 1918 may use a combination of filter 1920 and / or amplifier 1922 to convert the digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal may then be transmitted via antenna 1910. Similarly, when data is received, antenna 1910 can collect radio signals, which are then converted into digital data by radio front-end circuitry 1918. The digital data can then be passed to processing circuitry 1902. In other embodiments, the communication interface may include different components and / or different combinations of components.

[0246] In some alternative embodiments, network node 1900 does not include a separate radio front-end circuitry 1918; instead, processing circuitry 1902 includes radio front-end circuitry and is connected to antenna 1910. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1912 is part of communication interface 1906. In yet another embodiment, communication interface 1906 includes one or more ports or terminals 1916, radio front-end circuitry 1918, and RF transceiver circuitry 1912 as part of a radio unit (not shown), and communication interface 1906 communicates with baseband processing circuitry 1914, which is part of a digital unit (not shown).

[0247] Antenna 1910 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna 1910 may be coupled to radio front-end circuitry 1918 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 1910 is decoupled from network node 1900 and may be connected to network node 1900 via an interface or port.

[0248] Antenna 1910, communication interface 1906, and / or processing circuitry 1902 can be configured to perform any receive operation and / or certain acquire operation described herein by a network node. Any information, data, and / or signals can be received from the UE, another network node, and / or any other network device. Similarly, antenna 1910, communication interface 1906, and / or processing circuitry 1902 can be configured to perform any transmit operation described herein by a network node. Any information, data, and / or signals can be transmitted to the UE, another network node, and / or any other network device.

[0249] Power supply 1908 provides power to the various components of network node 1900 in a form suitable for the various components (e.g., at the voltage and current levels required by each respective component). Power supply 1908 may also include or be coupled to power management circuitry to supply power to the components of network node 1900 for performing the functions described herein. For example, network node 1900 may be connected to an external power source (e.g., mains, power outlet) via input circuitry or an interface (e.g., cable), thereby supplying power to the power circuitry of power supply 1908. As another example, power supply 1908 may include a power source in the form of a battery or battery pack, which is connected to or integrated into the power circuitry. The battery can provide backup power if the external power source fails.

[0250] Implementations of network node 1900 may include more than Figure 19Additional components shown are provided to offer certain aspects of the functionality of the network node, including any of the functions described herein and / or any functionality required to support the topics described herein. For example, network node 1900 may include a user interface device to allow information to be input into and output from network node 1900. This allows users to perform diagnostic, maintenance, repair, and other management functions on network node 1900.

[0251] Figure 20 Based on the block diagram of the host 2000 described in this document, the host 2000 can be... Figure 17 The embodiment of host 1716. As used herein, host 2000 can be or include various combinations of hardware and / or software, including processing resources in a standalone server, blade server, cloud-implemented server, distributed server, virtual machine, container, or server cluster. Host 2000 can provide one or more services to one or more UEs.

[0252] The host 2000 includes processing circuitry 2002, which is operatively coupled via bus 2004 to input / output interface 2006, network interface 2008, power supply 2010, and memory 2012. Other components may be included in other embodiments. The characteristics of these components may be substantially similar to those with respect to the previous figures (e.g., Figure 18 and Figure 19 The characteristics described for the device make its description generally applicable to the corresponding components of the host 2000.

[0253] Memory 2012 may include one or more computer programs, including data 2016 and one or more host applications 2014. Data 2016 may include user data, such as data generated by the UE for the host 2000, or data generated by the host 2000 for the UE. Embodiments of the host 2000 may utilize only a subset or all of the illustrated components. Host applications 2014 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Universal 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 various categories, types, or implementations of UEs (e.g., mobile phones, desktop computers, wearable display systems, head-up display systems). Host applications 2014 may also provide user authentication and authorization checks and may periodically report health status, routing, and content availability to a central node (such as a device in the core network or a device at the edge of the core network). Therefore, host 2000 can select and / or indicate different hosts for over-the-top services for the UE. Host application 2014 can support various protocols, such as HTTP Live Streaming (HLS), Real-time Messaging Protocol (RTMP), Real-time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0254] Figure 21 This diagram illustrates a block diagram of a virtualization environment 2100 in which functionality implemented by some embodiments can be virtualized. In this context, virtualization means creating a virtual version of an apparatus or device that may include a virtualization hardware platform, storage devices, and network resources. As used herein, virtualization can be applied to any device or component thereof described herein, and involves at least a portion of its functionality being implemented as one or more virtual components. Some or all of the functionality described herein can be implemented as virtual components executed by one or more virtual machines (VMs) in one or more virtual environments 2100 hosted by one or more hardware nodes (e.g., hardware computing devices operating as network nodes, UEs, core network nodes, or hosts). Furthermore, in embodiments where virtual nodes do not require radio connectivity (e.g., core network nodes or hosts), the nodes can be fully virtualized.

[0255] Application 2102 (which may alternatively be referred to as a software instance, virtual device, network function, virtual node, virtual network function, etc.) operates in a virtualized environment Q400 to implement some of the features, functions, and / or benefits of some embodiments disclosed herein.

[0256] Hardware 2104 includes processing circuitry, memory storing software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices described herein (such as network interfaces, input / output interfaces, etc.). The software can be executed by the processing circuitry to instantiate one or more virtualization layers 2106 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 2108a and 2108b (one or more of which may generally be referred to as VM 2108), and / or perform any functions, features, and / or benefits described in relation to some embodiments described herein. Virtualization layer 2106 can present a virtual operating platform to VM 2108, which appears as network hardware.

[0257] VM 2108 includes virtual processing, virtual memory, virtual network or interface, and virtual storage, and can be operated by a corresponding virtualization layer 2106. Different embodiments of instances of virtual device 2102 can be implemented on one or more VMs 2108, and these implementations can be carried out in different ways. In some contexts, hardware virtualization is referred to as Network Functions Virtualization (NFV). NFV can be used to unify numerous network device types onto industry-standard high-capacity server hardware, physical switches, and physical storage that can reside in data centers and customer premises equipment (CPE).

[0258] In the context of NFV, VM 2108 can be a software implementation of a physical machine, whose operating procedures are executed as if on a physical, non-virtualized machine. Each VM 2108, along with the hardware portion of hardware 2104 that executes that VM (whether it is dedicated hardware for that VM and / or hardware shared by that VM with other VMs), forms a separate virtual network element. Still within the context of NFV, the virtual network function is responsible for handling the specific network functions operating on one or more VMs 2108 above hardware 2104 and corresponding to application 2102.

[0259] Hardware 2104 can be implemented in a standalone network node with general or specific components. Hardware 2104 may implement some functions via virtualization. Alternatively, hardware 2104 may be part of a larger hardware cluster (e.g., in a data center or CPE) where many hardware nodes work together and are managed through management and orchestration 2110, which in particular oversees the lifecycle management of application 2102. In some embodiments, hardware 2104 is coupled to one or more radio units, each radio unit including one or more transmitters and one or more receivers that can be coupled to one or more antennas. The radio units may communicate directly with other hardware nodes via one or more suitable network interfaces and may be used in conjunction with virtual components to provide radio capabilities to virtual nodes (e.g., radio access nodes or base stations). In some embodiments, some signaling may be provided using a control system 2112, which may alternatively be used for communication between hardware nodes and radio units.

[0260] Figure 22 A communication diagram is shown illustrating how host 2202 communicates with UE 2206 via network node 2204 through a partial wireless connection, according to some embodiments. Reference will now be made to... Figure 22 Describe the UE discussed in the preceding paragraphs (e.g., Figure 17 UE1712a and / or Figure 18 UE 1800), network nodes (e.g., Figure 17 Network node 1710a and / or Figure 19 Network node 1900) and host (e.g., Figure 17 Host 1716 and / or Figure 20 Example implementations of the host 2000 according to various embodiments.

[0261] Similar to host 2000, embodiments of host 2202 include hardware such as a communication interface, processing circuitry, and memory. Host 2202 also includes software stored in or accessible by host 2202 and executable by the processing circuitry. This software includes a host application operable to provide services to a remote user, such as UE 2206 connected via an over-the-top (OTT) connection 2250 extending between UE 2206 and host 2202. When providing services to a remote user, the host application can provide user data transmitted using OTT connection 2250.

[0262] Network node 2204 includes hardware that enables it to communicate with host 2202 and UE 2206. Connection 2260 can be a direct connection or via a core network (such as...). Figure 17The connection is to the core network (1706) and / or one or more other intermediate networks (e.g., one or more public, private, or hosted networks). For example, an intermediate network could be a backbone network or the Internet.

[0263] UE 2206 includes hardware and software, the software being stored in or accessible by UE 2206 and executable by the UE's processing circuitry. This software includes client applications (e.g., a web browser or operator-specific "application") operable to provide services to human or non-human users via UE 2206, supported by host 2202. In host 2202, the executing host application can communicate with the executing client application via OTT connection 2250, which terminates between UE 2206 and host 2202. When providing services to a user, the UE's client application can receive request data from the host application of the host and, in response to the request data, provide user data. OTT connection 2250 can send both request data and user data. The UE's client application can interact with the user to generate user data provided to the host application via OTT connection 2250.

[0264] OTT connection 2250 can be extended via connection 2260 between host 2202 and network node 2204 and via wireless connection 2270 between network node 2204 and UE 2206 to provide connectivity between host 2202 and UE 2206. Connection 2260 and wireless connection 2270, which provide OTT connection 2250, have been abstractly drawn to illustrate communication between host 2202 and UE 2206 via network node 2204, without explicitly involving any intermediate devices and the precise routing of messages via these devices.

[0265] As an example of sending data via OTT connection 2250, in step 2208, host 2202 provides user data, which can be performed by executing a host application. In some embodiments, the user data is associated with a specific human user interacting with UE 2206. In other embodiments, the user data is associated with UE 2206, which shares data with host 2202 without explicit human interaction. In step 2210, host 2202 initiates a transmission to UE 2206 carrying the user data. Host 2202 may initiate the transmission in response to a request sent by UE 2206. This request may be caused by human interaction with UE 2206 or by the operation of a client application executed on UE 2206. Based on the teachings of the embodiments described throughout this disclosure, this transmission may be carried out via network node 2204. Therefore, in step 2212, based on the teachings of the embodiments described throughout this disclosure, network node 2204 sends the user data carried in the transmission initiated by host 2202 to UE 2206. In step 2214, UE 2206 receives user data carried in the transmission, which can be performed by a client application running on UE 2206, which is associated with a host application running by host 2202.

[0266] In some examples, UE 2206 executes a client application that provides user data to host 2202. User data can be provided as a response to data received from host 2202. Therefore, in step 2216, UE 2206 can provide user data, which can be done by executing the client application. When providing user data, the client application may also consider user input received from a user via the input / output interface of UE 2206. Regardless of the specific manner in which user data is provided, in step 2218, UE 2206 initiates a transmission of user data to host 2202 via network node 2204. In step 2220, in accordance with the teachings of the embodiments described throughout this disclosure, network node 2204 receives user data from UE 2206 and initiates the transmission of the received user data to host 2202. In step 2222, host 2202 receives the user data carried in the transmission initiated by UE 2206.

[0267] One or more embodiments in various examples improve the performance of OTT services provided to UE 2206 using OTT connection 2250, in which wireless connection 2270 forms the final part. More specifically, the teachings of these embodiments can increase the probability of successful random access, thereby providing benefits such as reduced user wait time.

[0268] In the example scenario, host 2202 can collect and analyze plant status information. As another example, host 2202 can process audio and video data that may have been retrieved from the UE for creating mappings. As another example, host 2202 can collect and analyze real-time data to help control vehicle congestion (e.g., control service lights). As another example, host 2202 can store surveillance video uploaded by the UE. As another example, host 2202 can store or control access to media content such as video, audio, VR, or AR, which can be broadcast, multicast, or unicast to the UE. As other examples, host 2202 can be used for energy pricing, remote control of non-time-critical power loads to balance generation demand, location services, presentation services (e.g., compiling charts based on data collected from remote devices), or any other function that collects, retrieves, stores, analyzes, and / or transmits data.

[0269] In some examples, a measurement process may be provided for the purpose of monitoring improved data rates, latency, and other factors in one or more embodiments. Optional network functions may also be present for reconfiguring the OTT connection 2250 between host 2202 and UE 2206 in response to changes in measurement results. The measurement process and / or the network functions for reconfiguring the OTT connection may be implemented in the software and hardware of host 2202 and / or UE 2206. In some embodiments, sensors (not shown) may be deployed in or associated with other devices traversed by the OTT connection 2250; the sensors may participate in the measurement process by providing values ​​of the monitored quantities exemplified above or by providing values ​​of other physical quantities from which the software can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 2250 may include message formatting, retransmission settings, preferred routing, etc.; reconfiguration does not require a direct change in the operation of network node 2204. Such processes and functions may be known and practiced in the art. In some embodiments, the measurement may involve proprietary UE signaling that facilitates host 2202's measurement of throughput, propagation time, latency, etc. Measurements can be achieved by having the software use an OTT connection 2250 to send messages (especially empty or “virtual” messages) while monitoring propagation time, errors, etc.

[0270] While the computing devices described herein (e.g., UE, network node, host) may include combinations of the hardware components shown, other embodiments may include computing devices with different combinations of components. It should be understood that these computing devices may include any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. The determination, calculation, acquisition, or similar operations described herein may be performed by processing circuitry that processes information in ways such as: converting acquired information into other information, comparing the acquired or converted information with information stored in a network node, and / or performing one or more operations based on the acquired or converted information, and making a determination based on the result of said processing. Furthermore, although components are depicted as single boxes located within larger boxes or nested within multiple boxes, in practice, a computing device may include multiple different physical components constituting a single illustrated component, and functionality may be partitioned between individual components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of a component may be partitioned between processing circuitry and the communication interface. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

[0271] In some embodiments, some or all of the functions described herein may be provided by processing circuitry that executes instructions stored in memory, which in some embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functions may be provided by the processing circuitry, for example, in a hard-wired manner, without executing instructions stored on a separate or discrete device-readable storage medium. In any of these particular embodiments, the processing circuitry may be configured to perform the described functions regardless of whether instructions stored on a non-transitory computer-readable storage medium are executed. The benefits provided by such functions are not limited to the individual processing circuitry or other components of the computing device, but are enjoyed holistically by the computing device and / or generally by the end user and wireless network.

[0272] The present disclosure has been described above with reference to embodiments thereof. However, these embodiments are for illustrative purposes only and are not intended to limit the present disclosure. The scope of the present disclosure is defined by the appended claims and their equivalents. Various changes and modifications can be made by those skilled in the art without departing from the scope of the present disclosure, all of which fall within the scope of the present disclosure.

[0273] Numbered Examples

[0274] 1. A method (700) at an end node for performing multiple PRACH transmissions for a Physical Random Access Channel (PRACH) attempt, comprising:

[0275] The number of (S710) PRACH transmissions is determined based on parameters received from the network node;

[0276] Determine (S720) a set of PRACH opportunities (ROs) for indexing, wherein the ROs in the set of ROs are associated with the selected SSB and with the preamble partition applicable to the determined number of PRACH transmissions;

[0277] Index the identified ROs in this group of ROs (S730); and

[0278] In a set of indexed ROs, one or more PRACH transmissions are performed (S740) based on the determined number of PRACH transmissions, wherein the number of ROs in the set is equal to the determined number of PRACH transmissions.

[0279] 2. The method according to embodiment 1, wherein if the number of PRACH transmissions is multiplexed in the time domain, and if there are multiple frequency-multiplexed ROs associated with the selected SSB and associated with the preamble division applicable to the determined number of PRACH transmissions, then one of the multiple ROs at a certain time instance is determined.

[0280] 3. The method according to embodiment 1 or 2, wherein if at least a portion of the number of PRACH transmissions is multiplexed in the frequency domain, determining a set of ROs for indexing includes:

[0281] Determine the number of ROs multiplexed in the frequency domain, which is equal to the number of PRACH transmissions multiplexed simultaneously in the frequency domain.

[0282] 3. The method according to any one of embodiments 1 to 3 further includes:

[0283] Determine the number K of PRACH transport configurations;

[0284] Determine the number of ROs R associated with the selected SSB and the number of preamble divisions applicable to the determined number of PRACH transmissions within an association period;

[0285] If the number R is less than the number K, then an extended association period is determined, including the minimum number X association periods, wherein within X association periods, the number of ROs associated with the selected SSB and associated with the preamble partition applicable to the determined number of PRACH transmissions is greater than or equal to the determined configuration number K, and

[0286] Specifically, during the extended association cycle, a set of ROs is determined and indexed.

[0287] 5. According to the method described in Example 4, if the quantity R is greater than or equal to the quantity K, the quantity X is determined to be 1, and a set of ROs is determined and indexed within the association period.

[0288] 6. The method according to embodiment 4 or 5, wherein the quantity K is the determined number of PRACH transmissions, or the maximum of a plurality of PRACH transmissions configured by the network node.

[0289] 7. The method according to any one of embodiments 4 to 6 further includes:

[0290] The first frame of the first association period of the extended association period is determined as the starting radio frame of the extended association period, and the frame immediately following the end of the extended association period is determined as the starting radio frame of the next extended association period.

[0291] 8. The method according to any one of embodiments 4 to 7, wherein performing one or more PRACH transmissions within the group of indexed ROs based on the determined number of PRACH transmissions within the extended association period comprises:

[0292] Perform the one or more RACH transfers within a first number of indexed ROs, where the first number is equal to the number of PRACH transfers; and

[0293] Repeat the PRACH transmission in one or more PRACH transmissions within the remaining ROs in the indexed ROs.

[0294] 9. The method according to any one of embodiments 4 to 7, wherein performing one or more PRACH transmissions within the group of indexed ROs based on the determined number of PRACH transmissions within the extended association period comprises:

[0295] The one or more PRACH transmissions are performed by distributing the one or more PRACH transmissions within the RO group, such that the extended mode of the RO used in each of the X associated cycles is the same.

[0296] 10. The method according to any one of embodiments 1 to 9, wherein performing one or more PRACH transmissions within the indexed RO based on the determined number of PRACH transmissions comprises:

[0297] Determine the transmission mode of the one or more PRACH transmissions; and

[0298] The one or more PRACH transfers are performed by following this transfer mode.

[0299] 11. The method according to embodiment 10, wherein the transmission mode is identified by the frame number.

[0300] 12. A method (800) at a network node for receiving multiple PRACH transmissions from an end node for a Physical Random Access Channel (PRACH) attempt, comprising:

[0301] Determine the number of PRACH transmissions (S810);

[0302] Determine (S820) a set of PRACH occupancy periods (ROs) for indexing, wherein the ROs in the set of ROs are associated with the selected SSB and with the preamble partition applicable to the determined number of PRACH transmissions;

[0303] Index the identified ROs in this group of ROs (S830); and

[0304] The number of PRACH transmissions is received within the indexed ROs in the group and associated with the PRACH attempt (S840), wherein the number of ROs in the group is equal to the number of PRACH transmissions determined.

[0305] 13. The method according to embodiment 12, wherein if the number of PRACH transmissions is multiplexed in the time domain, and if there are multiple frequency-multiplexed ROs associated with the selected SSB and associated with the preamble division applicable to the determined number of PRACH transmissions, then one of the multiple ROs at a certain time instance is determined.

[0306] 14. The method according to embodiment 12 or 13, wherein if at least a portion of the number of PRACH transmissions is multiplexed in the frequency domain, determining a set of ROs for indexing includes:

[0307] Determine the number of ROs multiplexed in the frequency domain, which is equal to the number of PRACH transmissions multiplexed simultaneously in the frequency domain.

[0308] 15. The method according to any one of embodiments 12 to 14, further comprising:

[0309] Determine the number K of PRACH transport configurations;

[0310] Determine the number of ROs R associated with the selected SSB and the number of preamble divisions applicable to the determined number of PRACH transmissions within an association period;

[0311] If the number R is less than the number K, then an extended association period is determined, including the minimum number X association periods, wherein within X association periods, the number of ROs associated with the selected SSB and associated with the preamble partition applicable to the determined number of PRACH transmissions is greater than or equal to the determined configuration number K, and

[0312] Specifically, during the extended association cycle, a set of ROs is determined and indexed.

[0313] 16. The method according to embodiment 15, wherein if the quantity R is greater than or equal to the quantity K, the quantity X is determined to be 1, and a set of ROs is determined and indexed within the association period.

[0314] 17. The method according to embodiment 15 or 16, wherein the quantity K is the determined number of PRACH transmissions, or the maximum of a plurality of PRACH transmissions configured by the network node.

[0315] 18. The method according to any one of embodiments 15 to 17 further includes:

[0316] The first frame of the first association period of the extended association period is determined as the starting radio frame of the extended association period, and the frame immediately following the end of the extended association period is determined as the starting radio frame of the next extended association period.

[0317] 19. The method according to any one of embodiments 15 to 18, wherein if the number of ROs in the group of ROs is greater than the determined number of PRACH transmissions within the extended association period, the number of PRACH transmissions received and associated within the group of indexed ROs includes:

[0318] Receive the number of PRACH transmissions within a first number of indexed ROs, where the first number is equal to the number of PRACH transmissions; and

[0319] One of the number of PRACH transmissions is repeated in the remaining ROs of the indexed ROs.

[0320] 20. The method according to any one of embodiments 15 to 18, wherein if the number of ROs in the group of ROs is greater than the number of PRACH transmissions within the extended association period, the number of PRACH transmissions received and associated within the group of indexed ROs includes:

[0321] Receive the number of PRACH transmissions distributed within the group of ROs, wherein the extended mode of the ROs used in each of the X associated cycles is the same.

[0322] 21. The method according to any one of embodiments 12 to 20, wherein receiving the number of PRACH transmissions within the group of indexed ROs comprises:

[0323] Determine the transmission mode for this number of RACH transmissions; and

[0324] This number of PRACH transmissions is received by following this transmission pattern.

[0325] 22. The method according to embodiment 21, wherein the transmission mode is identified by the frame number.

[0326] 23. A method (1100) at an end node for performing a PRACH transmission for a PRACH attempt, comprising:

[0327] Receive (S1110) a first physical random access channel (PRACH) configuration from a network node, wherein the PRACH configuration configures a first set of ROs and includes a first SSB mapping indication indicating the mapping of synchronization signal / physical broadcast channel SSB to PRACH timing (RO);

[0328] Receive (S1120) a second PRACH configuration from the network node, wherein the second PRACH configuration configures a second group of ROs and includes a second SSB mapping indication indicating the mapping of SSBs to ROs;

[0329] Determine (S1130) whether at least one RO associated with an SSB according to the first PRACH configuration overlaps in the time domain with ROs associated with different SSBs according to the second PRACH configuration; and

[0330] In response to determining that at least one RO associated with an SSB according to the first PRACH configuration overlaps in the time domain with ROs associated with different SSBs according to the second PRACH configuration, the ROs for PRACH transmission are determined (S1130).

[0331] 24. The method according to embodiment 23, wherein determining the RO for PRACH transmission includes:

[0332] Determine whether network nodes can simultaneously receive PRACH transmissions using different SSB beams.

[0333] 25. The method according to embodiment 24, wherein if time-overlapping ROs are configured with different priorities, it is determined that network nodes cannot simultaneously receive PRACH transmissions using different SSB beams, and in this case, the network node only receives PRACH transmissions in the RO with the higher priority.

[0334] 26. The method according to embodiment 25, wherein determining the RO for PRACH transmission if the RO selected by the terminal node for the RACH configuration has a lower priority includes:

[0335] Determine the RO used for PRACH transmission.

[0336] 27. The method according to embodiment 26, wherein determining the RO for PRACH transmission includes:

[0337] The RO mapped to the SSB is determined based on the received first PRACH configuration and second PRACH configuration, wherein the time-overlapping RO with lower priority is not associated with the SSB, which is different from the SSB associated with the time-overlapping RO with higher priority.

[0338] 28. The method according to embodiment 26, wherein determining the RO for PRACH transmission includes:

[0339] When determining the RO, lower-priority time-overlapping ROs are not counted.

[0340] 29. A terminal node (1300), comprising:

[0341] The communication interface (1301) is arranged for communication;

[0342] At least one processor (1303); and

[0343] The memory (1305) includes instructions that, when executed by at least one processor, cause the terminal node to perform the method according to any one of embodiments 1 to 11.

[0344] 30. A network node (1300), comprising:

[0345] The communication interface (1301) is arranged for communication;

[0346] At least one processor (1303); and

[0347] The memory (1305) includes instructions that, when executed by at least one processor, cause the network node to perform the method described according to any one of embodiments 12 to 22 and embodiments 23 to 28.

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

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

[0350] 33. A carrier comprising a computer program according to embodiment 31 or 32, wherein the carrier is one of an electrical signal, an optical signal, a radio signal, or a computer-readable storage medium.

Claims

1. A method (700) at an end node for performing multiple PRACH transmissions for a Physical Random Access Channel (PRACH) attempt, comprising: The number of (S710) PRACH transmissions is determined based on parameters received from the network node; Determine the number K of PRACH transport configurations; Determine the number of PRACH timings R that are associated with the selected SSB and the number of preamble divisions applicable to the determined number of PRACH transmissions within an associated period; Determine the extended association period, which includes X association periods, wherein the X association periods are such that... The minimum number of associated cycles; Within the extended association period, a set of ROs for indexing is determined (S720), wherein the ROs in the set of ROs are associated with the selected SSB and with the preamble partition applicable to the determined number of PRACH transmissions; Index the identified ROs in the set of ROs (S730); and In a set of indexed ROs, one or more PRACH transmissions are performed (S740) based on the determined number of PRACH transmissions, wherein the number of ROs in the set is equal to the determined number of PRACH transmissions.

2. The method according to claim 1, wherein, If the quantity X is determined to be 1, then the set of ROs is determined and indexed within the associated period.

3. The method according to claim 1 or 2, wherein, The quantity K is the maximum number of PRACH transmission candidates among the multiple PRACH transmission candidates configured by the network node.

4. The method according to any one of claims 1 to 3, further comprising: The first frame of the first association period of the extended association period is determined as the starting radio frame of the extended association period, and the frame immediately following the end of the extended association period is determined as the starting radio frame of the next extended association period after the extended association period.

5. The method according to any one of claims 1 to 4, wherein, If the number of ROs in the set of ROs is greater than the determined number of PRACH transmissions within the extended association period, then performing one or more PRACH transmissions based on the determined number of PRACH transmissions within the set of indexed ROs includes: Perform the one or more RACH transmissions within a first number of ROs in the indexed ROs, the first number being equal to the number of RACH transmissions; and The PRACH transmissions in one or more PRACH transmissions are repeated in the remaining ROs of the indexed ROs.

6. The method according to any one of claims 1 to 5, wherein, Performing one or more PRACH transmissions within the indexed set of ROs based on the determined number of PRACH transmissions includes: Determine the transmission mode of the one or more PRACH transmissions; and The one or more PRACH transmissions are performed by following the transmission mode.

7. The method according to claim 6, wherein, The transmission mode is identified by the frame number.

8. A method (800) at a network node for receiving multiple PRACH transmissions from an end node for a Physical Random Access Channel (PRACH) attempt, comprising: Determine the number of PRACH transmissions (S810); Determine the number K of PRACH transport configurations; Determine the number of PRACH timings R that are associated with the selected SSB and the number of preamble divisions applicable to the determined number of PRACH transmissions within an associated period; Determine the extended association period, which includes X association periods, wherein the X association periods are such that... The minimum number of associated cycles; Within the extended association period, a set of ROs for indexing is determined (S820), wherein the ROs in the set of ROs are associated with the selected SSB and with the preamble partition applicable to the determined number of PRACH transmissions; Index the identified ROs in the set of ROs (S830); and Receive the number of PRACH transmissions within the set of indexed ROs and associate them with a PRACH attempt (S840), wherein the number of ROs in the set of indexed ROs is equal to the number of determined PRACH transmissions.

9. The method according to claim 8, wherein, If the quantity X is determined to be 1, then the set of ROs is determined and indexed within the associated period.

10. The method according to claim 8 or 9, wherein, The quantity K is the maximum number of PRACH transmission candidates among the multiple PRACH transmission candidates configured by the network node.

11. The method according to any one of claims 8 to 10, further comprising: The first frame of the first association period of the extended association period is determined as the starting radio frame of the extended association period, and the frame immediately following the end of the extended association period is determined as the starting radio frame of the next extended association period after the extended association period.

12. The method according to any one of claims 8 to 11, wherein, If the number of ROs in the set of ROs is greater than the determined number of PRACH transmissions within the extended association period, then receiving and associating the number of PRACH transmissions within the set of indexed ROs includes: Receive the number of PRACH transmissions within a first number of ROs in the indexed ROs, the first number being equal to the number of PRACH transmissions; and One of the number of PRACH transmissions is repeated in the remaining ROs of the indexed ROs.

13. The method according to any one of claims 8 to 12, wherein, Receiving the number of PRACH transmissions within the set of indexed ROs includes: The transmission mode for the number of RACH transmissions is determined; and The number of PRACH transmissions is received by following the transmission pattern.

14. The method according to claim 13, wherein, The transmission mode is identified by the frame number.

15. A terminal node (1300) for performing multiple PRACH transmissions for a Physical Random Access Channel (PRACH) attempt, said terminal node being configured to: The number of (S710) PRACH transmissions is determined based on parameters received from the network node; Determine the number K of PRACH transport configurations; Determine the number of PRACH timings R that are associated with the selected SSB and the number of preamble divisions applicable to the determined number of PRACH transmissions within an associated period; The extended association period is determined, and the extended association period includes X association periods, wherein, The X associated periods are such that The minimum number of associated cycles; Within the extended association period, a set of ROs for indexing is determined (S720), wherein the ROs in the set of ROs are associated with the selected SSB and with the preamble partition applicable to the determined number of PRACH transmissions; Index the identified ROs in the set of ROs (S730); and In a set of indexed ROs, one or more PRACH transmissions are performed (S740) based on the determined number of PRACH transmissions, wherein the number of ROs in the set is equal to the determined number of PRACH transmissions.

16. The terminal node of claim 15 is further configured to perform the method of any one of claims 2 to 7.

17. A network node (1300) for receiving from an end node a plurality of PRACH transmissions for a Physical Random Access Channel (PRACH) attempt, said network node being configured to: Determine the number of PRACH transmissions (S810); Determine the number K of PRACH transport configurations; Determine the number of PRACH timings R that are associated with the selected SSB and the number of preamble divisions applicable to the determined number of PRACH transmissions within an associated period; The extended association period is determined, and the extended association period includes X association periods, wherein, The X associated periods are such that The minimum number of associated cycles; Within the extended association period, a set of ROs for indexing is determined (S820), wherein the ROs in the set of ROs are associated with the selected SSB and with the preamble partition applicable to the determined number of PRACH transmissions; Index the identified ROs in the set of ROs (S830); and Receive the number of PRACH transmissions within the set of indexed ROs and associate them with a PRACH attempt (S840), wherein the number of ROs in the set of indexed ROs is equal to the number of determined PRACH transmissions.

18. The network node of claim 17 is further configured to perform the method of any one of claims 8 to 14.

Images