First network node, second network node and methods for handling random access resources for l1 / l2 triggered mobility

Abstract

A method performed by a first network node (101) is provided. The method is for handling resources in a wireless communication network (100). The first network node (101) receives a first and a second message from a second network node (102), the first message comprising first data associated with one or more RA procedures for early UL synchronization to be used by one or more UEs, and the second message comprising a first identifier and second data associated with a first RA procedure for early UL synchronization performed by a first UE (121). The second data comprises a preamble index used by the first UE (121), a TA value associated with the first RA procedure performed by the first UE (121), and one or more of: • a PRACH occasion used by the first UE (121), • an SSB index, • an SSB burst position, • a PRACH mask Index, or • a carrier type indication. If a second identifier, derived from the first data comprised in the first message and the second data comprised in the second message, is determined to be equal to the first identifier, the first network node (101) identifies the first UE (121) having performed the first RA procedure.

Description

[0001] FIRST NETWORK NODE, SECOND NETWORK NODE AND METHODS PERFORMED THEREBY IN WIRELESS COMMUNICATION NETWORK

[0002] TECHNICAL FIELD

[0003] Embodiments herein relate to a first network node, a second network node, and methods performed therein regarding communication. Furthermore, a computer program product and a computer readable storage medium are also provided herein. In particular, embodiments herein relate to handling resources in a wireless communication network.

[0004] BACKGROUND

[0005] In a typical wireless communication network, wireless devices, also known as wireless communication devices, mobile stations, stations (STA) and / or User Equipment (UE), communicate via a Wide Area Network or a Local Area Network such as a Wi-Fi network or a cellular network comprising a Radio Access Network (RAN) part and a Core Network (CN) part. The RAN covers a geographical area which is divided into service areas or cell areas, which may also be referred to as a beam or a beam group, with each service area or cell area being served by a radio network node such as a radio access node e.g., a Wi-Fi access point, a Base Station (BS) or a radio base station (RBS), which in some networks may also be denoted, for example, a Base Station (BS), a NodeB, eNodeB (eNB), or gNodeB (gNB) as denoted in Fifth Generation (5G) telecommunications. A service area or cell area is a geographical area where radio coverage is provided by the radio network node. The radio network node communicates over an air interface operating on a radio frequency with the wireless devices within the range of the radio network node.

[0006] 3rd Generation Partnership Project (3GPP) is the standardization body for specifying the standards for the cellular system evolution, e.g., including 3G, 4G, 5G and the future evolutions. Specifications for Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet System (EPS) have been completed within the 3GPP. In 4G also called a Fourth Generation (4G) network, EPS is core network and E-UTRA is radio access network. In 5G, 5GC is core network, NR is radio access network. As a continued network evolution, the new release of 3GPP specifies a 5G network also referred to as 5G New Radio (NR) and 5G Core (5GC).

[0007] Frequency bands for 5G NR are being separated into two different frequency ranges, Frequency Range 1 (FR1) and Frequency Range 2 (FR2). FR1 comprises sub-6 GHz frequency bands. Some of these bands are bands traditionally used by legacy standards but have been extended to cover potential new spectrum offerings from 410 MHz to 7125 MHz.FR2 comprises frequency bands from 24.25 GHz to 52.6 GHz. Bands in this millimeter wave range have shorter range but higher available bandwidth than bands in the FR1.

[0008] Multi-antenna techniques may significantly increase the data rates and reliability of a wireless communication system. For a wireless connection between a single user, such as UE, and a BS, the performance is in particular improved if both the transmitter and the receiver are equipped with multiple antennas, which results in a Multiple-Input Multiple-Output (MIMO) communication channel. This may be referred to as Single-User (SU)-MIMO. In the scenario where MIMO techniques are used for the wireless connection between multiple users and the base station, MIMO enables the users to communicate with the base station simultaneously using the same time-frequency resources by spatially separating the users, which increases further the cell capacity. This may be referred to as Multi-User (MU)-MIMO. Note that MU-MIMO may benefit when each UE only has one antenna. The cell capacity can be increased linearly with respect to the number of antennas at the BS side. Due to that, more and more antennas are employed in BS. Such systems and / or related techniques are commonly referred to as massive MIMO.

[0009] L1 / L2 Triggered Mobility (LTM) LTM is introduced as a lower-layer mobility procedure in release (Rel)-18, enabling a network node to receive measurement reports from a UE via Layer 1 (L1) signaling. These L1 -measurement reports are used by the network for mobility-related decisions, such as executing an LTM cell switch to a target cell by sending an LTM Cell Switch Command medium access control (MAC) Control Element (CE) command. The LTM process, also shown in Fig. 1, is outlined as follows:

[0010] • The UE sends Layer 3 (L3) measurement report(s) to the gNB for one or more cells.

[0011] Based on these reports, the gNB identifies and configures one or more cells as LTM candidate cells, initiating the LTM preparation phase.

[0012] • The gNB sends a radio resource control (RRC) Reconfiguration message to the UE with the configuration details for the LTM candidate cells.

[0013] • The UE stores the received LTM candidate configurations and acknowledges with an RRC Reconfiguration Complete message.

[0014] • Downlink (DL) Pre-Synchronization, also known as “early DL synchronization”: The UE may perform early DL synchronization with LTM candidate cells upon receiving a "Candidate Cell transmission configuration indicator (TCI) States Activation / Deactivation MAC CE," reducing the mobility interruption by avoiding synchronization signal block (SSB)-based synchronization after the cell switch.

[0015] • Uplink (UL) Pre-Synchronization, also known as “early UL synchronization”: If the UE receives a physical downlink control channel (PDCCH) order for early timing advance (TA) acquisition, it may also perform UL pre-synchronization with thecandidate cells, further reducing the mobility delay. If configured by the network to do so, the UE may also, or instead, perform the UL pre-synchronization by autonomously determining a timing advance for a candidate cell by comparing the time of reception of reference signals in the candidate cell with the time of reception signals in the serving cell. The UE autonomous UL pre-synchronization mechanism requires that the candidate cell and the serving cell are synchronized.

[0016] • The UE performs L1 measurements on the configured LTM candidate cells and reports them to the source node.

[0017] • The source node decides the target cell, out of the configured and prepared LTM candidate cells, for the switch and sends an LTM Cell Switch Command MAC CE containing the configuration index of the selected LTM cell, i.e., the target cell. The UE switches to the target cell and applies the indicated configuration of the LTM candidate cell.

[0018] • If the UE lacks a valid TA value for the target cell, it performs a random access procedure. If a valid TA was acquired earlier during early UL synchronization, this procedure is skipped and the UE performs a so-called random access channel (RACH)-less LTM cell switch. Moreover, if the target cell TCI state indicated in the LTM cell switch MAC CE differs from the pre-synchronized TCI state, additional synchronization may be required.

[0019] • The UE completes the LTM cell switch by sending an RRC Reconfiguration Complete message to the target cell. For cases involving random access, successful completion of the random access procedure confirms the switch. For RACH-less LTM, the switch is deemed successful once the network acknowledges the UE’s first UL data transmission.

[0020] SUMMARY

[0021] As part of the development of embodiments herein, one or more challenges with the existing technology will first be identified and discussed.

[0022] In 3GPP Release 18 Intra Central Unit (Intra-CU) LTM, the concept of shared preamble resources has been introduced. Therefore, a Random Access (RA) - Radio Network Temporary Identifier (RNTI) is included in the F1AP TA Information Transfer signalings to identify the specific Physical Random Access Channel (PRACH) occasion where the UE transmitted the RA preamble. According to this, the source gNB Distributed Unit (gNB-DU) should be able to calculate the same RA-RNTI as the candidate gNB-DU, e.g., when a preamble is received by the UE, but at the moment there is no means for the source gNB-DU to calculate the RA-RNTI and associate this RNTI to a UE. Therefore, in case the source gNB-DU receives the TA value from a candidate gNB-DU, it would not be possible to associate such TA value with a UE and this means that RACH-less LTM would not be possible.

[0023] An object of embodiments herein is to handle resources, such as RA resources, in a wireless communication network in an efficient manner.

[0024] According to an aspect the object is achieved, according to some embodiments herein, by providing a method performed by a first network node for handling resources in a wireless communication network. The first network node receives a first message from a second network node, wherein the first message comprises first data associated with one or more RA procedures for early UL synchronization to be used by one or more UEs. The first network node receives a second message from the second network node, wherein the second message comprises a first identifier associated with a first RA procedure for early UL synchronization and second data associated with the first RA procedure, the first RA procedure being performed by a first UE. The second data comprises a preamble index used by the first UE, a TA value associated with the first RA procedure performed by the first UE, and any one or more out of:

[0025] • a PRACH occasion used by the first UE (121),

[0026] • a SSB index,

[0027] • an SSB position in a burst,

[0028] • a PRACH mask Index, or

[0029] • an indication of a type of carrier.

[0030] The first network node derives a second identifier based on the first data comprised in the first message and the second data comprised in the second message and determines whether the derived second identifier is equal to the first identifier. Responsive to when the second identifier is equal to the first identifier, the first network node identifies the first UE having performed the first RA procedure.

[0031] According to another aspect the object is achieved, according to some embodiments herein, by providing a method performed by a second network node for handling resources in a wireless communication network. The second network node transmits a first message to a first network node, wherein the first message comprises first data associated with one or more RA procedures for early UL synchronization to be used by one or more UEs. The second network node transmits a second message to the first network node, wherein the second message comprises a first identifier associated with a first RA procedure for early UL synchronization and second data associated with the first RA procedure, wherein the first RA procedure being performed by a first UE. The second data comprises a preamble index used by the first UE, a TA value associated with the first RA procedure performed by the first UE, and any one or more out of:

[0032] • a PRACH occasion used by the first UE (121),• a SSB index,

[0033] • an SSB position in a burst,

[0034] • a PRACH mask Index, or

[0035] • an indication of a type of carrier.

[0036] Furthermore, it is provided herein, a computer program comprising instructions, which when executed by a processor, causes the processor to perform actions according to any of the embodiments herein, as performed by the first network node and the second network node, respectively. It is also provided a carrier comprising the computer program, wherein the carrier is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0037] According to another aspect the object is achieved by providing a UE, and a radio network node configured to perform the methods herein, respectively.

[0038] Thus, according to an aspect the object is achieved, according to some embodiments herein, by providing a first network node for handling resources in a wireless communication network. The first network node is configured to receive a first message from a second network node, wherein the first message comprises first data associated with one or more RA procedures for early UL synchronization to be used by one or more UEs. The first network node is configured to receive a second message from the second network node, wherein the second message comprises a first identifier associated with a first RA procedure for early UL synchronization and second data associated with the first RA procedure, the first RA procedure being performed by a first UE. The second data comprises a preamble index used by the first UE, a TA value associated with the first RA procedure performed by the first UE, and any one or more out of:

[0039] • a PRACH occasion used by the first UE (121),

[0040] • a SSB index,

[0041] • an SSB position in a burst,

[0042] • a PRACH mask Index, or

[0043] • an indication of a type of carrier.

[0044] The first network node is configured to derive a second identifier based on the first data comprised in the first message and the second data comprised in the second message, and to determine whether the derived second identifier is equal to the first identifier. Responsive to when the second identifier is equal to the first identifier, the first network node is configured to identify the first UE having performed the first RA procedure.

[0045] According to another aspect the object is achieved, according to some embodiments herein, by providing a second network node for handling resources in a wirelesscommunication network. The second network node is configured to transmit a first message to a first network node, wherein the first message comprises first data associated with one or more RA procedures for early UL synchronization to be used by one or more UEs. The second network node is configured to transmit a second message to the first network node, wherein the second message comprises a first identifier associated with a first RA procedure for early UL synchronization and second data associated with the first RA procedure, wherein the first RA procedure being performed by a first UE. The second data comprises a preamble index used by the first UE, a TA value associated with the first RA procedure performed by the first UE, and any one or more out of:

[0046] • a PRACH occasion used by the first UE (121),

[0047] • a SSB index,

[0048] • an SSB position in a burst,

[0049] • a PRACH mask Index, or

[0050] • an indication of a type of carrier.

[0051] In order to address the above one or more challenges, examples of embodiments herein provide methods to allow the second network node such as a candidate network node to allocate RA resources, e.g., PRACH occasion, and / or preamble index, for each LTM candidate configuration or per UE in an alternative approach. The second network node may then transfer the specific RA resources utilized by the UE through F1AP / XnAP messages, being examples of the second message. This enables the first network node, such as the source network node, to compute the same RA-RNTI as returned by the second network node to the first network node, based on the RA resources, in particular the PRACH occasion, for early UL synchronization. This enables identifying the UE that performed the early UL synchronization.

[0052] Examples of embodiments herein may, e.g., bring the advantage of enabling the network to divide RA resources efficiently and improve the number of UEs for which an early UL synchronization procedure can be triggered. This improves the chances for the network and UE to perform a RACH-less LTM cell switch procedure which allows to reduce the latency of the mobility procedure, the connectivity interruption, and / or the signaling overhead.

[0053] BRIEF DESCRIPTION OF THE DRAWINGS

[0054] Embodiments will now be described in more detail in relation to the enclosed drawings, in which:

[0055] Fig. 1 shows an overview of an LTM procedure according to prior art;

[0056] Fig. 2 shows an overview depicting a wireless communication network according to embodiments herein;

[0057] Fig. 3 shows example embodiments of a method performed by a first network node according to embodiments herein;Fig. 4 shows example embodiments of a method performed by a second network node according to embodiments herein;

[0058] Fig. 5 shows a block diagram depicting a first network node according to embodiments herein;

[0059] Fig. 6 shows a block diagram depicting a second network node according to embodiments herein;

[0060] Fig. 7 shows an example of a communication system in accordance with some embodiments; Fig. 8 shows a communication system in accordance with some embodiments;

[0061] Fig. 9 shows a UE 15300 in accordance with some embodiments;

[0062] Fig. 10 is a block diagram of a network node in accordance with various aspects described herein; and

[0063] Fig. 11 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.

[0064] DETAILED DESCRIPTION

[0065] Embodiments herein relate to handling of resources, such as RA resources, in wireless communication network. Furthermore, embodiments herein relate to wireless communication networks in general. Fig. 2 is a schematic overview depicting a wireless communication network 100. The wireless communication network 100 comprises one or more RANs and one or more CNs. The wireless communication network 100 may be a 5G system, or a newer system supporting similar functionality, such as for example, a Sixth Generation (6G) system. In some examples, the wireless communication network may support, additionally or alternatively, a Long-Term Evolution (LTE) network and may support other technologies such as a for example, LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), LTE Half-Duplex Frequency Division Duplex (HD-FDD), and LTE operating in an unlicensed band. The telecommunications system may also support other technologies, such as Wideband Code Division Multiple Access (WCDMA), Universal Mobile Telecommunications System Terrestrial Radio Access (UTRA) TDD, Global System for Mobile communications (GSM) network, GSM / Enhanced Data Rate for GSM Evolution (EDGE) Radio Access Network (GERAN) network, Ultra-Mobile Broadband (UMB), EDGE network, network comprising any combination of Radio Access Technologies (RATs) such as e.g. Multi-Standard Radio (MSR) base stations, multi-RAT base stations etc., any 3rd Generation Partnership Project (3GPP) cellular network, Wireless Local Area Network / s (WLAN) or WiFi network / s, Worldwide Interoperability for Microwave Access (WiMax), IEEE 802.15.4-based low-power short-range networks such as IPv6 over Low-Power Wireless Personal Area Networks (6LowPAN), Zigbee, Z-Wave, Bluetooth Low Energy (BLE), or any cellular network or system. The telecommunications system may for example support a Low Power Wide Area Network(LPWAN). LPWAN technologies may comprise Long Range physical layer protocol (LoRa), Haystack, SigFox, LTE-M, and Narrow-Band loT (NB-loT).

[0066] A number of network nodes operate in the wireless communication network 100 such as e g. a first network node 101 and a second network node 102. These nodes provide radio coverage in a number of cells which may also be referred to as a beam or a beam group of beams.

[0067] The first network node 101 and second network node 102 may be any of a NG-RAN node, a transmission and reception point e.g. a base station, a radio access network node such as a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), an access controller, a base station, e.g. a radio base station such as a NodeB, an evolved Node B (eNB, eNode B), a gNB, a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a transmission arrangement of a radio base station, a stand-alone access point, a network controlled repeater or any other network unit capable of communicating with a wireless device within the service area served by the first network node 101 and / or second network node 102 depending e.g. on the first radio access technology and terminology used. The first network node 101 and / or second network node 102 may be referred to as a serving radio network node and / or target or candidate radio network node and communicates with a User Equipment (UE) 121 with Downlink (DL) transmissions to the UE 121 and Uplink (UL) transmissions from the UE 121.

[0068] In some examples, the wireless communication network 100 may comprise an access network, such as a radio access network (RAN), and a core network, which may include one or more core network nodes. The access network may include one or more access network nodes, such as the first network node 101 and / or the second network node 102, e.g., which may be generally referred to as network nodes, or any other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes may include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network may include one or more Open-RAN (ORAN) network nodes. An ORAN network node may be understood as a node in the telecommunication network that may support an ORAN specification, e.g., a specification published by the O-RAN Alliance, or any similar organization, and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network, including one or more network nodes and / or core network nodes.

[0069] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller, near-real time or non-real time, hosting software or software plug-ins, such as a near-real time control application, e.g., xApp, or a non-real time control application, e.g., rApp, or any combination thereof, the adjective “open” designating support of an ORAN specification. The radio network node 140 may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment, in which one or more network functions may be virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies. The first network node 101 may facilitate direct or indirect connection of UE, such as by connecting the UE 121 to the core network over one or more wireless connections.

[0070] In the wireless communication network 100, one or more wireless devices operate, such as e.g. the UE 121. The UE 121 may be also known as a, e.g., device, wireless device, mobile terminal, wireless terminal and / or mobile station, mobile telephone, cellular telephone, or laptop with wireless capability, an Internet of Things (loT) device, or a Customer Premises Equipment (CPE), smartwatch, vehicle, just to mention some further examples. The UE 121 in the present context may be, for example, portable, pocket-storable, hand-held, computer-comprised, or a vehicle-mounted mobile device, enabled to communicate voice and / or data, via a RAN, with another entity, such as a server, a laptop, a Personal Digital Assistant (PDA), or a tablet, a Machine-to-Machine (M2M) device, an Internet of Things (loT) device, e.g., a sensor or a camera, a device equipped with a wireless interface, such as a printer or a file storage device, modem, Laptop Embedded Equipped (LEE), Laptop Mounted Equipment (LME), USB dongles, CPE or any other radio network unit capable of communicating over a radio link in the wireless communication network 100. The UE 121 may be wireless, i.e., it may be enabled to communicate wirelessly in the wireless communication network 100 and, in some particular examples, may be able to support transmission using beamforming. The communication may be performed e.g., between two devices, between a device and a radio network node, and / or between a device and a server. The communication may be performed e.g., via a RAN and possibly one or more core networks, comprised, respectively, within the wireless communication network 100.

[0071] Methods herein may be performed by the first network node 101 and the second network node 102. As an alternative, a Distributed Node (DN) and functionality, e.g. comprised in a cloud 190 as shown in Fig. 2, may be used for performing or partly performing the methods herein.The above-described one or more challenges are addressed in a number of embodiments, some of which may be seen as alternatives, while some may be used in combination. Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only 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.

[0072] The above-described one or more challenges are addressed in a number of embodiments, some of which may be seen as alternatives, while some may be used in combination.

[0073] A method according to embodiments will now be described from the view of the first network node 101 together with Fig. 3. Fig. 3 shows example embodiments of a method performed by the first network node 101 for handling resources in the wireless communication network 100. The method comprises the following actions, which actions may be taken in any suitable order. Actions that are optional are presented in dashed boxes in Fig. 3.

[0074] Action 301. The first network node 101 receives a first message from the second network node 102. The first message comprises first data associated with one or more RA procedures for early UL synchronization to be used by one or more UEs.

[0075] In some embodiments, the first data comprises any one or more out of:

[0076] - one or more PRACH occasions,

[0077] - one or more preamble indexes,

[0078] - a preamble index which has available to been used by a UE,

[0079] - a PRACH occasion which has available to been used by a UE,

[0080] - a SSB index,

[0081] - an SSB position in a burst,

[0082] - a PRACH mask Index,

[0083] - an indication of a type of carrier,

[0084] - an Orthogonal Frequency Division Multiplexing (OFDM) symbol of the PRACH occasion available to be used by a UE 121,

[0085] - an index of a slot of the PRACH occasion available to be used by a UE,

[0086] - a subcarrier spacing, e.g., associated to the index of the slot of the PRACH occasion that can be used by a UE,

[0087] - an index of the PRACH occasion in the frequency domain,

[0088] - an indication of an RA type, e.g., a 4-step RA type, or procedure, or a 2-step RA type, or procedure.In some embodiments, the first message may be exchanged between the first network node 101 and the second network node 102 using an F1AP procedure or an XnAP procedure. In other words, the first network node 101 may receive the first message using an F1AP procedure or an XnAP procedure. The F1AP procedure may, e.g., comprise an existing F1AP procedure such as e.g., F1AP CU-Dll TA Information transfer. Alternatively, the F1AP procedure may, e.g., comprise a new F1AP procedure such as, e.g., F1AP RA Resource Information Transfer. The XnAP procedure may, e.g., comprise an existing XnAP procedure such as, e.g., XnAP TA Information Transfer. Alternatively, the XnAP procedure may, e.g., comprise a new XnAP procedure such as, e.g., XnAP RA Resource Information Transfer e.g., supplementary uplink carrier or normal uplink carrier.

[0089] Action 302. In some embodiments, the first network node 101 may transmit an RA triggering message to the first UE 121. The RA triggering message comprises the first data. The RA triggering message may trigger the first UE 121 to perform the first RA procedure. In other words, the first network node 101 may trigger the first UE 121 to perform the first RA procedure by transmitting the RA triggering message to the first UE 121. The RA triggering message may comprise the first data, that is, the first data that was received from the second network node 102 in the first message. The first RA procedure may, e.g., comprise an LTM cell switch, a conditional LTM (CLTM) cell switch and / or early UL synchronization. The RA triggering message may, e.g., comprise a Physical Downlink Control Channel (PDCCH) order.

[0090] Action 303. The first network node 101 receives a second message from the second network node 102. The second message comprises a first identifier associated with a first RA procedure for early UL synchronization and second data associated with the first RA procedure, the first RA procedure being performed by the first UE 121. The second data comprises a preamble index used by the first UE 121, a TA value associated with the first RA procedure performed by the first UE 121, and any one or more out of:

[0091] • a PRACH occasion used by the first UE 121,

[0092] • an SSB index,

[0093] • an SSB position in a burst,

[0094] • a PRACH mask Index, or

[0095] • an indication of a type of carrier.

[0096] In some embodiments, the first identifier may comprise a first RA-RNTI and / or a Message B RNTI (MSGB-RNTI). The first RA-RNTI may be associated with a 4-step RA procedure and the MSGB-RNTI may be associated with a 2-step RA procedure.

[0097] Thus, for example, the SSB index and / or the PRACH occasion may correspond to the first identifier.

[0098] In some embodiments, the second message may be exchanged between the first network node 101 and the second network node 102 using an F1AP procedure or an XnAPprocedure. In other words, the first network node 101 may receive the second message using an F1AP procedure or an XnAP procedure. The F1AP procedure may, e.g., comprise an existing F1AP procedure such as e.g., F1AP CU-Dll TA Information transfer. Alternatively, the F1AP procedure may, e.g., comprise a new F1AP procedure such as, e.g., F1AP RA Resource Information Transfer. The XnAP procedure may, e.g., comprise an existing XnAP procedure such as, e.g., XnAP TA Information Transfer. Alternatively, the XnAP procedure may e.g., comprise a new XnAP procedure such as e.g., XnAP RA Resource Information T ransfer.

[0099] In some embodiments, the second data may further comprise any one or more out of: - one or more PRACH occasions,

[0100] - an OFDM symbol of the PRACH occasion used by the first UE 121

[0101] - an index of a slot of the PRACH occasion used by the first UE 121 ,

[0102] - a subcarrier spacing, e.g., associated to the index of the slot of the PRACH occasion used by the first UE 121,

[0103] - an index of the PRACH occasion in the frequency domain,

[0104] - an indication of an RA type e.g., a 4-step RA type, or procedure, or a 2-step RA type, or procedure.

[0105] Action 304. The first network node 101 obtains or derives a second identifier based on the first data comprised in the first message and the second data comprised in the second message. In other words, the first network node 101 may use the first data comprised in the first message and the second data comprised in the second message to obtain the second identifier. In some examples, the first network node 101 may obtain the second identifier based on e.g., a preamble index and the second data such as a PRACH occasion indicated in the second data comprised in the second message.

[0106] In some embodiments, the second identifier comprises a second RA-RNTI and / or a second MSGB-RNTI. The second RA-RNTI may be associated with a 4-step RA procedure and the MSGB-RNTI may be associated with a 2-step RA procedure.

[0107] In some embodiments, the second identifier is used to obtain, such as identify, derive and / or determine, the first UE 121 associated with the TA value.

[0108] In some embodiments, the TA value is comprised in the second message or the first message.

[0109] Action 305. The first network node 101 determines whether the derived second identifier is equal to the first identifier.

[0110] Action 306. Responsive to when the second identifier is equal to the first identifier, the first network node 101 obtains or identifies the first UE 121 having performed the first RA procedure. Responsive to when the second identifier is equal to the first identifier, the firstnetwork node 101 obtains or identifies that the UE associated with the TA value is the first UE 121.

[0111] Thus, in some embodiments, obtaining the first UE 121 may comprise comparing the second identifier with the first identifier, e.g., to check whether the first identifier and the second identifier are equal.

[0112] In some embodiments, responsive to when the second identifier is equal to the first identifier, the first network node 101 may associate the TA value, such as the TA value comprised in the second message, or the second data, with the first UE 121, such as obtaining, determining, identifying or deriving, the first UE 121 associated with the TA value. In other words, obtaining the first UE 121 may comprise associating the first UE 121 with the TA value.

[0113] Thus, the first network node 101 may determine, such as identify or derive, that the first UE 121 associated with the TA value is the first UE 121 for which the second identifier equals the first identifier.

[0114] Action 307. In some embodiments, the first network node 101 may transmit a third message to the second network node 102. The third message acknowledges the reception of the first message and / or the second message. The third message may e.g., be transmitted using the same procedure as for the first message and / or second message.

[0115] Action 308. The first network node 101 may transmit to the identified UE the TA value in the second data. Thus, responsive to when the second identifier is equal to the first identifier, and upon triggering of a cell switch procedure to a cell associated with the data comprised in the second message, the first network node 101 may transmit the TA value comprised in the second message to the UE 121.

[0116] A method according to embodiments will now be described from the view of the second network node 102 together with Fig. 4. Fig. 4 shows example embodiments of a method performed by the second network node 102 for handling resources in the wireless communication network 100. The method comprises the following actions, which actions may be taken in any suitable order. Actions that are optional are presented in dashed boxes in Fig.

[0117] 4.

[0118] Action 401. The second network node 102 transmits the first message to the first network node 101. The first message comprises the first data associated with one or more RA procedures for early UL synchronization to be used by one or more UEs.

[0119] In some embodiments, the first data further comprises any one or more out of:

[0120] - one or more PRACH occasions,

[0121] - one or more preamble indexes,

[0122] - a preamble index which has available to been used by a UE,- a PRACH occasion which has available to been used by a UE,

[0123] - an SSB index,

[0124] - an SSB position in a burst,

[0125] - a PRACH mask Index,

[0126] - an indication of a type of carrier,

[0127] - an OFDM symbol of the PRACH occasion available to be used by a UE,

[0128] - an index of a slot of the PRACH occasion available to be used by a UE,

[0129] - a subcarrier spacing, e.g., associated to the index of the slot of the PRACH occasion that can be used by a UE,

[0130] - an index of the PRACH occasion in the frequency domain,

[0131] - an indication of an RA type e.g., a 4-step RA type, or procedure, or a 2-step RA type, or procedure.

[0132] In some embodiments, the first message may be exchanged between the first network node 101 and the second network node 102 using an F1AP procedure or an XnAP procedure. In other words, the second network node 102 may transmit the first message using an F1AP procedure or an XnAP procedure. The F1AP procedure may, e.g., comprise an existing F1AP procedure such as e.g., F1AP CU-DU TA Information transfer. Alternatively, the F1AP procedure may, e.g., comprise a new F1AP procedure such as e.g., F1AP RA Resource Information Transfer. The XnAP procedure may, e.g., comprise an existing XnAP procedure such as, e.g., XnAP TA Information Transfer. Alternatively, the XnAP procedure may, e.g., comprise a new XnAP procedure such as, e.g., XnAP RA Resource Information Transfer e.g., supplementary uplink carrier or normal uplink carrier.

[0133] Action 402. In some embodiments, the second network node 102 may obtain the second data comprised in the second message. The second data comprises data associated with the first RA procedure performed by the first UE 121. The RA procedure may, e.g., comprise a mobility procedure, such as early UL synchronization and / or a cell switch procedure. E.g., an RA-RNTI and / or MSGB-RNTI may be obtained. The RA-RNTI and / or MSGB-RNTI may be obtained based on standardized procedures, e.g., as standardized by 3GPP. The second network node 102 may further obtain a TA value for the first UE 121 by calculating the TA value. The TA value is for the first UE 121 that performed the first RA procedure. The RA-RNTI may be associated with a 4-step RA procedure and the MSGB-RNTI may be associated with a 2-step RA procedure.

[0134] In some embodiments, the second data may comprise any one or more out of:

[0135] - one or more preamble indexes,

[0136] - a preamble index used by the first UE 121,

[0137] - a PRACH occasion used by the first UE 121,

[0138] - an SSB index,- an SSB position in a burst,

[0139] - a PRACH mask Index,

[0140] - an indication of a type of carrier,

[0141] The second data may further comprise one or more of the following:

[0142] - an OFDM symbol of the PRACH occasion used by the first UE 121

[0143] - an index of a slot of the PRACH occasion used by the first UE 121 ,

[0144] - a subcarrier spacing, e.g., associated to the index of the slot of the PRACH occasion used by the first UE 121,

[0145] - an index of the PRACH occasion in the frequency domain,

[0146] - an indication of an RA type e.g., a 4-step RA type, or procedure, or a 2-step RA type, or procedure.

[0147] Action 403. The second network node 102 transmits the second message to the first network node 101. The second message comprises the first identifier associated with the first RA procedure for early UL synchronization and the second data associated with the first RA procedure, the first RA procedure being performed by a first UE 121. The second data comprises the preamble index used by the first UE 121, the TA value associated with the first RA procedure performed by the first UE 121 , and any one or more out of:

[0148] • the PRACH occasion used by the first UE 121,

[0149] • the SSB index,

[0150] • the SSB position in a burst,

[0151] • the PRACH mask Index, or

[0152] • the indication of a type of carrier.

[0153] In some embodiments, the first identifier comprises the first RA-RNTI and / or the first MSGB-RNTI. The first RA-RNTI may be associated with a 4-step RA procedure and the first MSGB-RNTI may be associated with a 2-step RA procedure.

[0154] In some embodiments, the second message may be exchanged between the first network node 101 and the second network node 102 using an F1AP procedure or an XnAP procedure. In other words, the second network node 102 may transmit the second message using an F1AP procedure or an XnAP procedure. The F1AP procedure may, e.g., comprise an existing F1AP procedure such as e.g., F1AP CU-DU TA Information transfer. Alternatively, the F1AP procedure may, e.g., comprise a new F1AP procedure such as e.g., F1AP RA Resource Information Transfer. The XnAP procedure may, e.g., comprise an existing XnAP procedure such as, e.g., XnAP TA Information Transfer. Alternatively, the XnAP procedure may e.g., comprise a new XnAP procedure such as e.g., XnAP RA Resource Information Transfer.

[0155] Action 404. In some embodiments, the second network node 102 may receive the third message from the first network node 101. The third message acknowledges the reception ofthe first message and / or the second message. The third message may e.g., be transmitted using the same procedure as for the first message and / or second message.

[0156] Embodiments herein such as the embodiments mentioned above will now be further described and exemplified. The text below is applicable to embodiments herein and may be combined with any suitable embodiment described above.

[0157] The first network node 101 refers to the network node controlling the serving cell of an LTM or CLTM mobility procedure. The first network node 101 may be the current serving network node, the current serving gNB, the current source gNB, the current serving gNB-Cll, the source gNB-Cll, the serving CU, the source CU, the current serving gNB-Dll, the source gNB-Dll, the current serving DU, or the source DU.

[0158] The second network node 102 refers to the network node controlling at least one of the candidate cell(s) of an LTM or CLTM mobility procedure. The second network node 102 may be a candidate network node, a candidate gNB, a candidate gNB-CU, a candidate CU, a candidate gNB-DU, ora candidate DU.

[0159] The term “source node” refers to a node from which a UE 121 is moved in a mobility procedure, in particular an LTM cell switch procedure in the context of this disclosure, to another node, which is referred to as a “target node”. Herein, the term “source node” is also used to refer to a node serving a UE 121 for which an LTM cell switch procedure is being prepared or has been prepared, although no LTM cell switch procedure has been triggered or executed (yet), or an LTM cell switch procedure was triggered or executed, and the source node is now the network node serving the UE 121, and the UE 121 keeps the mobility configuration, e.g., as in subsequent LTM. In this disclosure, such a node may thus be referred to either as a “source node” or a “serving node”. In addition, when a CLTM cell switch has been executed the source node may sometimes be referred to as the “serving node”, although this node in principle does not serve the UE anymore. These principles may be generalized to the terms “source gNB”, “source CU”, “source DU” and “source cell” too. The above applies also when the “node” is referred to as a “network node” or a “RAN node”.

[0160] The term “candidate node” refers to a node that is being prepared to possibly be the target node of a mobility procedure, in the context of this disclosure in particular an LTM cell switch procedure. If a candidate node is selected to be the target node of the mobility procedure and the execution of the mobility procedure towards that node is triggered and / or ongoing, this candidate becomes the “target node”. Herein, the terms “candidate node” and “target node” are sometimes mixed in a way that make them interchangeably. However, in some particular contexts, the distinction between “candidate node” and “target node” becomessignificant. This can be generalized to the terms “candidate gNB7”target gNB”, “candidate CUVtarget CU”, “candidate DUTtarget DU” and “candidate cellTtarget cell”.

[0161] The random access resources indicated in embodiments herein may refer to random access resources used by the first network node for Early Uplink Synchronization of one UE 121 or may refer to random access resources used by the first network node for Early Uplink Synchronization of multiple UEs.

[0162] According to some examples of embodiments herein, the first network node 101, e.g., a source CU, a source DU, or a source gNB, receives from a second network node, e.g., a candidate gNB-DU, candidate gNB-CU, or candidate gNB, such as the second network node 102, a first message comprising information, such as first data, related to RA resources used by a UE for early UL synchronization. The first message, such as the information in the first message and / or the first data, may e.g., comprise one or more of the following:

[0163] - The first identifier associated with an RA procedure, such as e.g., the first RA-RNTI. - One or more PRACH occasions.

[0164] - One or more Preamble indexes.

[0165] - A Preamble index which has been used by a UE.

[0166] - A PRACH occasion which has been used by a UE.

[0167] - An SSB Index.

[0168] - An SSB position in a burst.

[0169] - A PRACH Mask Index.

[0170] - An indication of a type of carrier, e.g., a supplementary uplink carrier or a normal uplink.

[0171] The first network node 101 may receive, from the second network node 102, a second message comprising information, such as second data, related to one or more random access procedures, e.g., a TA value, a preamble index, a PRACH occasion, a RA-RNTI, for the UE 121 or a group of UEs.

[0172] The first network node 101 may derive, such as determine, calculate or compute, a second identifier associated to an RA procedure, such as e.g., an RA-RNTI, by using information such as the RA resources, e.g., preamble index, PRACH occasion. The RA resources may comprise resources received in the second message.

[0173] The first network node 101 may determine whether the determined, derived, calculated or computed, second identifier is equal to the first identifier received by the second network node.

[0174] The first network node 101 may transmit, to the second network node 102, a message, such as the third message, to acknowledge the successful reception of the above information, such as the information received in the first and / or second message.The first network node 101 may transmit to the UE 121 identified by the calculated second identifier the information received by the second network node, e.g., the TA value.

[0175] In some examples of embodiments herein, the first network node 101 may derive the second identifier associated with an RA procedure for determining which UE 121 is associated with a certain TA value that the first network node 101 receives (or received) from the second network node 102, e.g., in the second message.

[0176] In some examples of embodiments herein, the first network node 101 may determine that the UE 121 associated with a certain TA value that the first network node 101 receives (or received) from the second network node 102 is the UE 121 for which the second identifier derived by the first network node 101 is the same as the received first identifier.

[0177] In some examples of embodiments herein, the first network node 101 may associate a UE 121 with one or more information received by the second network node 102 in the first message.

[0178] In some examples of embodiments herein, the procedure between the first network node 101 and second network node 102 is using existing F1AP orXnAP procedures, e.g., F1AP CU-DU TA Information Transfer or an XnAP TA Information Transfer message.

[0179] In some examples of embodiments herein, the procedure between the first network node 101 and second network node 102 may be using a new F1AP orXnAP procedures, e.g., a Random Access Resources Information Transfer or an XnAP Random Access Resources Information Transfer message.

[0180] In some examples of embodiments herein, the first network node 101 may further receive from the second network 102 in the first message a mapping between one or more random access information. For instance, the following may be received:

[0181] - For a PRACH index, one or more PRACH occasions.

[0182] - For a PRACH occasions, one or more PRACH index.

[0183] - A couple which includes only a PRACH index and only a PRACH occasion.

[0184] - Whether the mapping is only for one LTM candidate cell.

[0185] - Whether the mapping is for a subset of LTM candidate cells.

[0186] - Whether the mapping is for all the LTM candidate cells.

[0187] According to some examples of embodiments herein, a second network node, e.g., a candidate gNB-DU, candidate gNB-CU, or candidate gNB, such as the second network node 102, derives the random access resources for the UE 121 and may send the related information, such as the first data, e.g., RA-RNTI, of a candidate cell.

[0188] The second network node 102 transmits to the first network node 101 the first message comprising the information, such as the first data, related to random access resources used bythe UE 121 for early UL synchronization. The first message, such as the information in the first message and / or the first data, may e.g., comprise one or more of the following:

[0189] - The first identifier associated with an RA procedure, such as e.g., a first RA-RNTI. - One or more PRACH occasions.

[0190] - One or more Preamble indexes.

[0191] - A Preamble index which has been used by a UE.

[0192] - A PRACH occasion which has been used by a UE.

[0193] - An SSB Index.

[0194] - An SSB position in a burst.

[0195] - A PRACH Mask Index.

[0196] - An indication of a type of carrier, e.g., supplementary uplink carrier or normal uplink carrier.

[0197] The second network node 102 may derive or obtain the RA resources, e.g., RACH occasion, preamble index, according to a RA procedure performed by the UE 121 for a mobility procedure, e.g., an early UL synchronization procedure.

[0198] The second network node 102 may transmit to the first network node 101 the second message comprising the information, such as second data, related to RA resources used by the UE 121 for early UL synchronization. The second message, such as the information in the second message and / or the second data, may e.g., comprise one or more of the following:

[0199] - A PRACH occasion.

[0200] - A Preamble index.

[0201] - An SSB Index.

[0202] - An SSB position in a burst.

[0203] - A calculated RA-RNTI.

[0204] - An indication of the carrier, e.g., supplementary uplink carrier or normal uplink carrier. - A TA value.

[0205] The second network node 102 may receive from the first network node 101 a message to acknowledge the successful reception of the above information, such as the information received in the first and / or second message.

[0206] In some examples of embodiments herein, the procedure between the first network node 101 and second network node 102 is using existing F1AP orXnAP procedures, e.g., F1AP DU-CU TA Information Transfer or an XnAP TA Information Transfer message.

[0207] In some examples of embodiments herein, the procedure between the first network node 101 and second network node 102 is using a new F1AP orXnAP procedures, e.g., a Random Access Resources Information Transfer or an XnAP Random Access Resources Information Transfer message.In some examples of embodiments herein, the second network node 102 may further include to the first network node 101 in the first message a mapping between one or more random access information. For instance, one or more of the following may be received:

[0208] - For a PRACH index, one or more PRACH occasions.

[0209] - For a PRACH occasions, one or more PRACH index.

[0210] - A couple which includes only a PRACH index and only a PRACH occasion.

[0211] - Whether the mapping is only for one LTM candidate cell.

[0212] - Whether the mapping is for a subset of LTM candidate cells.

[0213] - Whether the mapping is for all the LTM candidate cells.

[0214] In some examples of embodiments herein, which may be combined with the other embodiments herein, the RA resource(s) is(are) associated with one of the following:

[0215] - The UE 121.

[0216] - A plurality of UEs.

[0217] - A second network node, controlling at least one LTM candidate cell.

[0218] - A second network node, controlling at least one Conditional LTM candidate cell.

[0219] - One or more candidate gNB-DUs.

[0220] - A candidate gNB.

[0221] - One or more LTM candidate cells.

[0222] - One or more CLTM candidate cells.

[0223] In some examples of embodiments herein, which can be combined with the other embodiments herein, the RA resource(s) comprise one or more of the following:

[0224] - One or more random access preamble ID, or preamble index, e.g. the preamble ID or index of a contention-free RA preamble.

[0225] - An RA configuration ID.

[0226] - An RA partitioning ID.

[0227] - A frequency value for each RA preamble ID.

[0228] - A time value (e.g., slot, subframe, frame value) for each RA preamble ID.

[0229] In some examples of embodiments herein, which can be combined with the other embodiments herein, the first network node 101 may be a source DU, or a source CU, or a source gNB.

[0230] In some examples of embodiments herein, which can be combined with the other embodiments herein, the second network node 102 may be a candidate DU, a candidate CU, or a candidate gNB, a source CU.

[0231] In an inter-DU LTM case with a gNB-DU1 and a gNB-DU2 being controlled by a same gNB-CU, the following may occur

[0232] 1. Source gNB-DU1 sends a PDCCH order to the first UE 121 to trigger the first RA

[0233] procedure.2. The target gNB-DU2 receives a RA request from the first UE 121 and calculates the TA.

[0234] 3. The target gNB-DU2 sends to the source gNB-DU1 , e.g., via the gNB-Cll, the calculated TA value and to support the source gNB-DU1 to identify which UE the TA value corresponds to, it sends the Preamble Index, an RA-RNTI, and one or more of the PRACH occasion, SSB Index, SSB position in Burst, PRACH Mask Index, and / or type of carrier.

[0235] Only knowing the “Preamble Index” and the “RA-RNTI” is not enough for the source gNB-DU1 to exactly pinpoint the UE to which the TA value is associated with. According to embodiments herein, on top of “Preamble Index” and “RA-RNTI”, the target gNB-DU2 also sends other information such as PRACH occasion, SSB Index, SSB position in Burst, PRACH Mask Index, and / or type of carrier.

[0236] In this section, examples of implementations are provided. New parts are highlighted in bold and underlined.

[0237] In one implementation, the DU-CU TA INFORMATION TRANSFER F1AP message and the CU-DU TA INFORMATION TRANSFER message is extended to include e.g., the PRACH occasion and the SSB index of the SSB used by the UE for which the calculated TA value is provided in the signaling message.

[0238] 9.2.1.24 DU-CU TA INFORMATION TRANSFER

[0239] This message is sent by the gNB-Dll to inform the gNB-Cll about TA information.

[0240] Direction: gNB-Dll gNB-Cll

[0241] > <

[0242]

[0243] >

[0244]

[0245]

[0246]

[0247] 9.2.1.25 CU-DU TA INFORMATION TRANSFER

[0248] This message is sent by the gNB-Cll to inform the gNB-Dll about TA information.

[0249] Direction: gNB-Cll

[0250]

[0251] gNB-Dll

[0252] > <

[0253]

[0254] >

[0255]

[0256]

[0257]

[0258] Figure 5 depicts an example of the arrangement that the first network node 101 may comprise to perform the method described in Figure 3. The first network node 101 may be understood to be for handling resources, e.g., RA resources. The first network node 101 is configured to operate in the wireless communication network 100.

[0259] Several embodiments are comprised herein. It should be noted that the examples herein are not mutually exclusive. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description.

[0260] Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. The detailed description of some of the following corresponds to the same references provided above, in relation to the actions described for the first network node 101 and will thus not be repeated here to simplify the description.

[0261] The first network node 101 may comprise an input and output interface 10 configured to communicate with each other. The input and output interface 10 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown).

[0262] The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 11 of a processing circuitry in the first network node 101 depicted in Figure 5, together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the first network node 101. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the first network node 101.The first network node 101 and / or the processor 11 is e.g., configured handle resources in the wireless communication network 100.

[0263] The first network node 101 and / or the processor 11 is configured to receive the first message from the second network node 102. The first message is adapted to comprise the first data associated with one or more RA procedures for early UL synchronization to be used by one or more UEs.

[0264] The first network node 101 and / or the processor 11 is configured to receive the second message from the second network node 102. The second message is adapted to comprise the first identifier associated with the first RA procedure for early UL synchronization and the second data associated with the first RA procedure. The first RA procedure is performed by the first UE 121. The second data comprises the preamble index used by the first UE 121, the TA value associated with the first RA procedure performed by the first UE 121 , and any one or more out of:

[0265] • a Physical Random Access Channel, PRACH, occasion used by the first UE (121),

[0266] • a Synchronization Signal Block, SSB, index,

[0267] • an SSB position in a burst,

[0268] • a PRACH mask Index, or

[0269] • an indication of a type of carrier.

[0270] The first network node 101 and / or the processor 11 is configured to obtain the second identifier based on the first data comprised in the first message and the second data comprised in the second message.

[0271] The first network node 101 and / or the processor 11 is configured to determine whether the derived second identifier is equal to the first identifier.

[0272] Responsive the second identifier is equal to the first identifier, the first network node 101 and / or processor 11 is configured to identify or obtain the first UE 121 having performed the first RA procedure.

[0273] The first network node 101 and / or the processor 11 may be configured to transmit to the identified UE 121 the TA value in the second data.

[0274] In some embodiments, the first identifier is adapted to comprise the first RA-RNTI and the second identifier is adapted to comprise the second RA-RNTI.

[0275] In some embodiments, the first data is adapted to comprise any one or more out of: - one or more PRACH occasions,

[0276] - one or more preamble indexes,

[0277] - a preamble index available to be used by a UE,

[0278] - a PRACH occasion available to be used by a UE,

[0279] - an SSB index,- an SSB position in a burst,

[0280] - a PRACH mask Index,

[0281] - an indication of a type of carrier,

[0282] - an OFDM symbol of the PRACH occasion available to be used by a UE,

[0283] - an index of a slot of the PRACH occasion available to be used by a UE,

[0284] - a subcarrier spacing, e.g., associated to the index of the slot of the PRACH occasion that can be used by a UE,

[0285] - an index of the PRACH occasion in the frequency domain,

[0286] - an indication of an RA type.

[0287] In some embodiments, the second data is adapted to further comprise any one or more out of:

[0288] - one or more PRACH occasions,

[0289] - an OFDM symbol of the PRACH occasion used by the first UE 121

[0290] - an index of a slot of the PRACH occasion used by the first UE 121 ,

[0291] - a subcarrier spacing, e.g., associated to the index of the slot of the PRACH occasion used by the first UE 121,

[0292] - an index of the PRACH occasion in the frequency domain,

[0293] - an indication of an RA type.

[0294] In some embodiments, the second identifier is adapted to be used to obtain the first UE 121 associated with the TA value.

[0295] In some embodiments, responsive to the first identifier being equal to the second identifier, the first network node 101 and / or processor 11 may be configured to associate the TA value with the first UE 121.

[0296] In some embodiments, the first network node 101 and / or the processor 11 may be configured to obtain the first UE 121 by associating the first UE 121 with the TA value.

[0297] In some embodiments, the TA value is adapted to be comprised in the second message and / or in the second data in the second message.

[0298] The first network node 101 and / or the processor 11 may be configured to exchange any of the first message and the second message between the first network node 101 and the second network node 102 using an F1AP procedure or an XnAP procedure.

[0299] The first network node 101 and / or the processor 11 may be configured to transmit the third message to the second network node 102. The third message may acknowledge the reception of the first message and / or the second message.

[0300] In some embodiments, the first network node 101 and / or the processor 11 may further be configured to transmit, to the first UE 121, the RA triggering message adapted to comprise the first data. The RA triggering message is adapted to trigger the first UE 121 to perform the first RA procedure for early UL synchronization.The first network node 101 may further comprise a memory 12 comprising one or more memory units. The memory 12 comprises instructions executable by the processor 11 in the first network node 101.

[0301] The memory 12 is arranged to be used to store instructions, data, configurations, packets, resources, indications, timers, rules, allocations, identifiers, TA values, and applications to perform the methods herein when being executed in the first network node 101.

[0302] In some embodiments, a computer program 13 comprises instructions, which when executed by the at least one processor 11 , cause the at least one processor 11 of the first network node 101 to perform the actions above.

[0303] In some embodiments, a respective carrier 14 comprises the respective computer program 13, wherein the carrier 14 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0304] Thus, embodiments herein may disclose the first network node 101 configured to handle resources in the wireless communication network 100. The first network node 101 is configured to operate in the wireless communication network 100. The first network node 101 comprises the processor 11 and the memory 12, said memory 12 comprising instructions executable by said processor 11 whereby said first network node 101 is operative to perform any of the methods herein.

[0305] As will be readily understood by those familiar with communications design, that functions means or modules may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single applicationspecific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a radio network node, for example.

[0306] Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and / or program or application data, and non-volatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications receivers will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

[0307] Figure 6 depicts an example of the arrangement that the second network node 102 may comprise to perform the method described in Figure 4. The second network node 102 may be understood to be for handling resources, e.g., RA resources. The second network node 102 is configured to operate in the wireless communication network 100.

[0308] Several embodiments are comprised herein. It should be noted that the examples herein are not mutually exclusive. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description.

[0309] Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. The detailed description of some of the following corresponds to the same references provided above, in relation to the actions described for the second network node 102 and will thus not be repeated here to simplify the description.

[0310] The second network node 102 may comprise an input and output interface 20 configured to communicate with each other. The input and output interface 20 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown).

[0311] The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 21 of a processing circuitry in the second network node 102 depicted in Figure 6, together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loadedinto the second network node 102. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the second network node 102.

[0312] The second network node 102 and / or processor 21 is e.g., configured to handle resources in the wireless communication network 100.

[0313] The second network node 102 and / or the processor 21 is configured to transmit the first message to the first network node 101. The first message comprises the first data associated with one or more RA procedures for early UL synchronization to be used by one or more UEs.

[0314] The second network node 102 and / or processor 21 is configured to transmit the second message to the first network node 101. The second message comprises the first identifier associated with the first RA procedure for early UL synchronization and the second data associated with the first RA procedure. The first RA procedure is performed by the first UE 121. The second data comprises the preamble index used by the first UE 121 , the TA value associated with the first RA procedure performed by the first UE 121 , and any one or more out of:

[0315] • a PRACH occasion used by the first UE 121,

[0316] • an SSB index,

[0317] • an SSB position in a burst,

[0318] • a PRACH mask Index, or

[0319] • an indication of a type of carrier.

[0320] 1. The second network node (102) according to any of the claims 23-27, wherein the second network node (102) is configured to:

[0321] obtain the second data comprised in the second message.

[0322] In some embodiments, the first identifier may comprise the first RA-RNTI.

[0323] In some embodiments, the first data is adapted to comprise any one or more out of: - one or more PRACH occasions,

[0324] - one or more preamble indexes,

[0325] - a preamble index available to be used by a UE,

[0326] - a PRACH occasion available to be used by a UE,

[0327] - a SSB index,

[0328] - an SSB position in a burst,

[0329] - a PRACH mask Index,

[0330] - an indication of a type of carrier,

[0331] - an OFDM symbol of the PRACH occasion available to be used by a UE,- an index of a slot of the PRACH occasion available to be used by a UE, - a subcarrier spacing, e.g., associated to the index of the slot of the PRACH occasion that can be used by a UE,

[0332] - an index of the PRACH occasion in the frequency domain,

[0333] - an indication of an RA type.

[0334] In some embodiments, the second data is adapted to comprise any one or more out of: - one or more PRACH occasions,

[0335] - one or more preamble indexes,

[0336] - a preamble index used by the first UE 121,

[0337] - a PRACH occasion used by the first UE 121,

[0338] - a SSB index,

[0339] - an SSB position in a burst,

[0340] - a PRACH mask Index,

[0341] - an indication of a type of carrier,

[0342] - an OFDM symbol of the PRACH occasion used by the first UE 121

[0343] - an index of a slot of the PRACH occasion used by the first UE 121 ,

[0344] - a subcarrier spacing, e.g., associated to the index of the slot of the PRACH occasion used by the first UE 121,

[0345] - an index of the PRACH occasion in the frequency domain,

[0346] - an indication of an RA type.

[0347] The second network node 102 and / or processor 21 may be configured to configured to exchange any of the first message and the second message between the first network node 101 and the second network node 102 using an F1AP procedure or an XnAP procedure.

[0348] In some embodiments, the second network node 102 and / or processor 21 may further by configured to receive the third message from the first network node 101. The third message may acknowledge the reception of the first message and / or the second message.

[0349] In some embodiments, the second network node 102 and / or processor 21 may further by configured to obtain the second data and / or the first identifier comprised in the second message.

[0350] The second network node 102 may further comprise respective a memory 22 comprising one or more memory units. The memory 22 comprises instructions executable by the processor 21 in the second network node 102.

[0351] The memory 22 is arranged to be used to store instructions, data, configurations, packets, resources, indications, timers, rules, allocations, identifiers, TA values, and applications to perform the methods herein when being executed in the second network node 102.In some embodiments, a computer program 23 comprises instructions, which when executed by the at least one processor 21 , cause the at least one processor 21 of the second network node 102 to perform the actions above.

[0352] In some embodiments, a respective carrier 24 comprises the respective computer program 23, wherein the carrier 24 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0353] Thus, embodiments herein may disclose the second network node 102 configured to handle resources in the wireless communication network 100. The second network node 102 is configured to operate in the wireless communication network 100. The second network node 102 comprises the processor 21 and the memory 22, said memory 22 comprising instructions executable by said processor 21 whereby said second network node 102 is operative to perform any of the methods herein.

[0354] As will be readily understood by those familiar with communications design, that functions means or modules may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single applicationspecific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a radio network node, for example.

[0355] Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and / or program or application data, and non-volatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications receivers will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

[0356] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processingcircuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

[0357] Embodiments

[0358] Below, some example Embodiments 1-40 are shortly described..

[0359] Embodiment 1. A method performed by a first network node 101 e.g., for handling resources in a wireless communication network 100, the method comprising any one or more out of:

[0360] receiving 301 a first message from a second network node 102, the first message comprising first data associated with one or more Random Access, RA, procedure for early Uplink, UL, synchronization of one or more User Equipments, UE,

[0361] receiving 303 a second message from the second network node 102, the second message comprising a first identifier associated with a first RA procedure for early UL synchronization and second data associated with the first RA procedure, the first RA procedure being performed by a first UE 121,

[0362] obtaining 304 a second identifier, the second identifier being based on the first data comprised in the first message and the second data comprised in the second message, responsive the second identifier being equal to the first identifier, obtaining 305 the first UE 121 having performed the first RA procedure.

[0363] Embodiment 2. The method according to embodiment 1, wherein any one or more out of:

[0364] - the first identifier comprises a first RA Radio Network Temporary Identifier, RA-RNTI, and

[0365] - the second identifier comprises a second RA-RNTI.

[0366] Embodiment 3. The method according to any of embodiments 1-2, wherein the first data comprises any one or more out of:

[0367] - one or more Physical Random Access Channel, PRACH, occasions,

[0368] - one or more preamble indexes,- a preamble index available to be used by a UE,

[0369] - a PRACH occasion available to be used by a UE,

[0370] - a Synchronization Signal Block, SSB, index,

[0371] - an SSB position in a burst,

[0372] - a PRACH mask Index,

[0373] - an indication of a type of carrier,

[0374] - an OFDM symbol of the PRACH occasion available to be used by a UE,

[0375] - an index of a slot of the PRACH occasion available to be used by a UE,

[0376] - a subcarrier spacing, e.g., associated to the index of the slot of the PRACH occasion that can be used by a UE,

[0377] - an index of the PRACH occasion in the frequency domain,

[0378] - an indication of an RA type.

[0379] Embodiment 4. The method according to any of embodiments 1-3, wherein the second data comprises any one or more out of:

[0380] - one or more PRACH occasions,

[0381] - one or more preamble indexes,

[0382] - a preamble index used by the first UE 121,

[0383] - a PRACH occasion used by the first UE 121,

[0384] - an SSB index,

[0385] - an SSB position in a burst,

[0386] - a PRACH mask Index,

[0387] - an indication of a type of carrier,

[0388] - an OFDM symbol of the PRACH occasion used by the first UE 121

[0389] - an index of a slot of the PRACH occasion used by the first UE 121 ,

[0390] - a subcarrier spacing, e.g., associated to the index of the slot of the PRACH occasion used by the first UE 121,

[0391] - an index of the PRACH occasion in the frequency domain,

[0392] - an indication of an RA type.

[0393] Embodiment 5. The method according to any of embodiments 1-4, wherein the second identifier is used to obtain the first UE 121 associated with a Timing Advance, TA value.

[0394] Embodiment 6. The method according to any of embodiments 1-5, wherein responsive to the first identifier being equal to the second identifier, associating the TA value with the first UE 121.Embodiment 7. The method according to any of embodiments 1-6, wherein obtaining the first UE 121 comprises associating the first UE 121 with the TA value.

[0395] Embodiment 8. The method according to any of embodiments 5-7, wherein the TA value is comprised in the second message and / or in the second data in the second message.

[0396] Embodiment 9. The method according to any of embodiments 1-7, wherein any of the first message and the second message is exchanged between the first network node 101 and the second network node 102 using an F1AP procedure or an XnAP procedure.

[0397] Embodiment 10. The method according to any of embodiments 1-8, wherein the method further comprises:

[0398] transmitting 305 a third message to the second network node 102, the third message acknowledging the reception of the first message and / or the second message.

[0399] Embodiment 11. The method according to any of embodiments 1-9, wherein the method further comprises:

[0400] transmitting 302 to the first UE 121 an RA triggering message comprising the first data, the RA triggering message triggering the first UE 121 to perform the first RA procedure.

[0401] Embodiment 12. A computer program 13 comprising instructions, which when executed by a processor 11 , causes the processor 11 to perform actions according to any of the embodiments 1-11.

[0402] Embodiment 13. A carrier 14 comprising the computer program 13 of embodiment 12, wherein the carrier 14 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0403] Embodiment 14. A method performed by a second network node 102 e.g., for handling resources in a wireless communication network 100, the method comprising any one or more out of:

[0404] transmitting 401 a first message to a first network node 101, the first message comprising first data associated with one or more Random Access, RA, procedure for early Uplink, UL, synchronization of one or more User Equipments, UE,

[0405] transmitting 403 a second message to the first network node 101, the second message comprising a first identifier associated with a first RA procedure for early UL synchronizationand second data associated with the first RA procedure, the first RA procedure being performed by a first UE 121.

[0406] Embodiment 15. The method according to embodiment 14, wherein the first identifier comprises a first RA Radio Network Temporary Identifier, RA-RNTI.

[0407] Embodiment 16. The method according to any of embodiments 14-15, wherein the first data comprises any one or more out of:

[0408] - one or more Physical Random Access Channel, PRACH, occasions,

[0409] - one or more preamble indexes,

[0410] - a preamble index available to be used by a UE,

[0411] - a PRACH occasion available to be used by a UE,

[0412] - an Synchronization Signal Block, SSB index,

[0413] - an SSB position in a burst,

[0414] - a PRACH mask Index,

[0415] - an indication of a type of carrier,

[0416] - an OFDM symbol of the PRACH occasion available to be used by a UE,

[0417] - an index of a slot of the PRACH occasion available to be used by a UE,

[0418] - a subcarrier spacing, e.g., associated to the index of the slot of the PRACH occasion that can be used by a UE,

[0419] - an index of the PRACH occasion in the frequency domain,

[0420] - an indication of an RA type.

[0421] Embodiment 17. The method according to any of embodiments 14-16, wherein the second data comprises any one or more out of:

[0422] - one or more PRACH occasions,

[0423] - one or more preamble indexes,

[0424] - a preamble index used by the first UE 121,

[0425] - a PRACH occasion used by the first UE 121,

[0426] - an SSB index,

[0427] - an SSB position in a burst,

[0428] - a PRACH mask Index,

[0429] - an indication of a type of carrier,

[0430] - an OFDM symbol of the PRACH occasion used by the first UE 121

[0431] - an index of a slot of the PRACH occasion used by the first UE 121 ,

[0432] - a subcarrier spacing, e.g., associated to the index of the slot of the PRACH occasion used by the first UE 121,- an index of the PRACH occasion in the frequency domain,

[0433] - an indication of an RA type.

[0434] Embodiment 18. The method according to any of embodiments 14-17, wherein any of the first message and the second message is exchanged between the first network node 101 and the second network node 102 using an F1AP procedure or an XnAP procedure.

[0435] Embodiment 19. The method according to any of embodiments 14-18, wherein the method further comprises:

[0436] receiving 404 a third message from the first network node 101 , the third message acknowledging the reception of the first message and / or the second message.

[0437] Embodiment 20. The method according to any of embodiments 14-19, wherein the method further comprises:

[0438] obtaining 402 the data comprised in the second message.

[0439] Embodiment 21. A computer program 23 comprising instructions, which when executed by a processor 21 , causes the processor 21 to perform actions according to any of the embodiments 14-20.

[0440] Embodiment 22. A carrier 24 comprising the computer program 23 of embodiment 21, wherein the carrier 24 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0441] Embodiment 23. A first network node 101 e.g., configured to handle resources in a wireless communication network 100, the first network node 101 further being configured to any one or more out of:

[0442] receive a first message from a second network node 102, the first message adapted to comprise first data associated with one or more Random Access, RA, procedures for early Uplink, UL, synchronization of one or more User Equipments, UEs,

[0443] receive a second message from the second network node 102, the second message adapted to comprise a first identifier associated with a first RA procedure for early UL synchronization and second data associated with the first RA procedure, the first RA procedure being performed by a first UE 121,

[0444] obtain a second identifier, the second identifier adapted to be based on the first data comprised in the first message and the second data comprised in the second message,responsive the second identifier being equal to the first identifier, obtain the first UE 121 having performed the first RA procedure.

[0445] Embodiment 24. The first network node 101 according to embodiment 23, wherein any one or more out of:

[0446] - the first identifier is adapted to comprise a first RA Radio Network Temporary Identifier, RA-RNTI, and

[0447] - the second identifier is adapted to comprise a second RA-RNTI.

[0448] Embodiment 25. The first network node 101 according to any of embodiments 23-24, wherein the first data is adapted to comprise any one or more out of:

[0449] - one or more Physical Random Access Channel, PRACH, occasions,

[0450] - one or more preamble indexes,

[0451] - a preamble index available to be used by a UE,

[0452] - a PRACH occasion available to be used by a UE,

[0453] - a Synchronization Signal Block, SSB, index,

[0454] - an SSB position in a burst,

[0455] - a PRACH mask Index,

[0456] - an indication of a type of carrier,

[0457] - an OFDM symbol of the PRACH occasion available to be used by a UE,

[0458] - an index of a slot of the PRACH occasion available to be used by a UE,

[0459] - a subcarrier spacing, e.g., associated to the index of the slot of the PRACH occasion that can be used by a UE,

[0460] - an index of the PRACH occasion in the frequency domain,

[0461] - an indication of an RA type.

[0462] Embodiment 26. The first network node 101 according to any of embodiments 23-25, wherein the second data is adapted to comprise any one or more out of:

[0463] - one or more PRACH occasions,

[0464] - one or more preamble indexes,

[0465] - a preamble index used by the first UE 121,

[0466] - a PRACH occasion used by the first UE 121,

[0467] - an SSB index,

[0468] - an SSB position in a burst,

[0469] - a PRACH mask Index,

[0470] - an indication of a type of carrier,

[0471] - an OFDM symbol of the PRACH occasion used by the first UE 121- an index of a slot of the PRACH occasion used by the first UE 121 ,

[0472] - a subcarrier spacing, e.g., associated to the index of the slot of the PRACH occasion used by the first UE 121,

[0473] - an index of the PRACH occasion in the frequency domain,

[0474] - an indication of an RA type.

[0475] Embodiment 27. The first network node 101 according to any of embodiments 23-26, wherein the second identifier is adapted to be used to obtain the first UE 121 associated with a Timing Advance, TA, value.

[0476] Embodiment 28. The first network node 101 according to any of embodiments 23-27, wherein responsive to the first identifier being equal to the second identifier, associate the TA value with the first UE 121.

[0477] Embodiment 29. The first network node 101 according to any of embodiments 23-28, wherein the first network node 101 is configured to obtain the first UE 121 by associating the first UE 121 with the TA value.

[0478] Embodiment 30. The first network node 101 according to any of embodiments 27-29, wherein the TA value is adapted to be comprised in the second message and / or in the second data in the second message.

[0479] Embodiment 31. The first network node 101 according to any of embodiments 23-30, wherein any of the first message and the second message is adapted to be exchanged between the first network node 101 and the second network node 102 using an F1AP procedure or an XnAP procedure.

[0480] Embodiment 32. The first network node 101 according to any of embodiments 23-31, wherein the first network node 101 is further configured to:

[0481] transmit a third message to the second network node 102, the third message adapted to acknowledge the reception of the first message and / or the second message.

[0482] Embodiment 33. The first network node 101 according to any of embodiments 23-32, wherein the first network node 101 is further configured to:

[0483] transmit to the first UE 121 an RA triggering message adapted to comprise the first data, the RA triggering message adapted to trigger the first UE 121 to perform the first RA procedure.Embodiment 34. A second network node 102 e.g., configured to handle resources in a wireless communication network 100, the second network node 102 further being configured to any one or more out of:

[0484] transmit a first message to a first network node 101 , the first message adapted to comprise first data associated with one or more Random Access, RA, procedure for early Uplink, UL, synchronization of one or more User Equipments, UE,

[0485] transmit a second message to the first network node 101 , the second message adapted to comprise a first identifier associated with a first RA procedure for early UL synchronization and second data associated with the first RA procedure, the first RA procedure being performed by a first UE 121.

[0486] Embodiment 35. The second network node 102 according to embodiment 34, wherein the first identifier is adapted to comprise a first RA Radio Network Temporary Identifier, RA-RNTI.

[0487] Embodiment 36. The second network node 102 according to any of embodiments 34- 35, wherein the first data is adapted to comprise any one or more out of:

[0488] - one or more Physical Random Access Channel, PRACH, occasions,

[0489] - one or more preamble indexes,

[0490] - a preamble index available to be used by a UE,

[0491] - a PRACH occasion available to be used by a UE,

[0492] - a Synchronization Signal Block, SSB, index,

[0493] - an SSB position in a burst,

[0494] - a PRACH mask Index,

[0495] - an indication of a type of carrier,

[0496] - an OFDM symbol of the PRACH occasion available to be used by a UE,

[0497] - an index of a slot of the PRACH occasion available to be used by a UE,

[0498] - a subcarrier spacing, e.g., associated to the index of the slot of the PRACH occasion that can be used by a UE,

[0499] - an index of the PRACH occasion in the frequency domain,

[0500] - an indication of an RA type.

[0501] Embodiment 37. The second network node 102 according to any of embodiments 34- 36, wherein the second data is adapted to comprise any one or more out of:

[0502] - one or more PRACH occasions,

[0503] - one or more preamble indexes,- a preamble index used by the first UE 121,

[0504] - a PRACH occasion used by the first UE 121,

[0505] - an SSB, index,

[0506] - an SSB position in a burst,

[0507] - a PRACH mask Index,

[0508] - an indication of a type of carrier,

[0509] - an OFDM symbol of the PRACH occasion used by the first UE 121

[0510] - an index of a slot of the PRACH occasion used by the first UE 121 ,

[0511] - a subcarrier spacing, e.g., associated to the index of the slot of the PRACH occasion used by the first UE 121,

[0512] - an index of the PRACH occasion in the frequency domain,

[0513] - an indication of an RA type.

[0514] Embodiment 38. The second network node 102 according to any of embodiments 34- 37, wherein any of the first message and the second message is adapted to be exchanged between the first network node 101 and the second network node 102 using an F1AP procedure or an XnAP procedure.

[0515] Embodiment 39. The second network node 102 according to any of embodiments 34- 38, wherein the second network node 102 is further configured to:

[0516] receive a third message from the first network node 101 , the third message adapted to acknowledge the reception of the first message and / or the second message.

[0517] Embodiment 40. The second network node 102 according to any of embodiments 34- 39, wherein the second network node 102 is further configured to:

[0518] obtain the data comprised in the second message.

[0519] ADDITIONAL EXPLANATION

[0520] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0521] Figure 7 shows an example of a communication system 15100 in accordance with some embodiments.

[0522] In the example, the communication system 15100 includes a telecommunications network 15102 that includes an access network 15104, such as a radio access network (RAN), and a core network 15106, which includes one or more core network nodes 15108.The access network 15104 includes one or more access network nodes or base stations of various types, access network nodes 15110A and 1511 OB are depicted (which may be collectively referred to as network nodes 15110), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 15104 may include more than one access network technology. The network nodes 15110, being examples of the first network node 101 and the second network node 102, of access network 15104 facilitate direct or indirect connection of wireless devices, also referred to as (UEs, such as by connecting UEs 15112A, 15112B, 15112C, and 15112D (one or more of which may be generally referred to as UEs 15112 or UE 121) to the core network 15106 over one or more wireless connections.

[0523] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 15102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 15102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node in the telecommunications network 15102, including one or more access network nodes 15110 and / or core network nodes 15108.

[0524] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies.

[0525] The network nodes 15110 facilitate direct or indirect connection of one or more UEs 15112 to the core network 15106 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wirelesssignals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 15100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 15100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0526] The UEs 15112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 15110 and other communication devices. Similarly, the network nodes 15108, 15110 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 15102) with the UEs 15112 and / or with other network nodes or equipment in the telecommunications network 15102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 15102. More specifically, UEs 15112 may send messages, data, and / or other signals to network nodes 15108, 15110 or other elements of the telecommunications network 15102 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 15108, 15110 may send messages, data, and other signals to UEs 151122, other network nodes 15108, 15110, and other devices in telecommunications network 15102 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 15112 by transmitting the message to an access network node 15110 that will then transmit the message to the intended UE 15112. Similarly, a core network node 108 may receive a particular message from a UE 15112 by receiving the message from an access network node 15110 that itself received the message from the UE 15112.

[0527] In the depicted example, the core network 15106 connects elements of the access network 15104 (e.g., one or more of the network nodes 15110) to one or more host computing systems, such as host 15116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 15106 includes one or more core network nodes (e.g., core network node 15108) of various types, one or more of which may be generally referred to as network nodes 15108. Network nodes 15108 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptionsthereof are generally applicable to the corresponding components of the core network node 15108. Example core network nodes provide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (ALISF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0528] The host 15116 may be under the ownership or control of a service provider other than an operator or provider of the access network 15104 and / or the telecommunications network 15102. The host 15116 may be operated by the service provider or on behalf of the service provider. The host 15116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0529] As a whole, the communication system 15100 of Figure 7 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 15100 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM);

[0530] 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 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 15100 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 15100 supporting different standards, protocols, or rule sets.

[0531] As one example, in certain embodiments, access network 15104 may contain some access network nodes 15110 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 15110 support (or the same access network nodes 15110 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 15102 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as aresult, may include an access network 104 and / or a core network 106 that supports multiple different standard generations or may include multiple access networks 104 and / or multiple core networks 106 with individual networks 104, 106 supporting different standard generations.

[0532] Telecommunications network 15102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 15102. For example, the telecommunications network 15102 may 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 loT services to yet further UEs.

[0533] In some examples, one or more of the UEs 15112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 15104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 15104. Additionally, a UE may be configured for operating in single- or multi-RAT or multistandard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0534] In the example, the hub 15114 communicates with the access network 15104 to facilitate indirect communication between one or more UEs (e.g., UE 15112C and / or 15112D) and network nodes (e.g., network node 15110B). In some examples, the hub 15114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 15114 may be a broadband router enabling access to the core network 15106 for the UEs. As another example, the hub 15114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 15110, or by executable code, script, process, or other instructions in the hub 15114.

[0535] As another example, the hub 15114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 15114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 15114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 15114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 15114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.The hub 15114 may have a constant / persistent or intermittent connection to the network node 15110B. The hub 15114 may also allow for a different communication scheme and / or schedule between the hub 15114 and UEs (e.g., UE 15112C and / or 15112D), and between the hub 15114 and the core network 15106. In other examples, the hub 15114 is connected to the core network 15106 and / or one or more UEs via a wired connection. Moreover, the hub 15114 may be configured to connect to an M2M service provider over the access network 15104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 15110 while still connected via the hub 15114 via a wired or wireless connection. In some embodiments, the hub 15114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 15110B. In other embodiments, the hub 15114 may be a non-dedicated hub-that is, a device which is capable of operating to route communications between the UEs and network node 15110B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0536] Figure 8 is another example of a communication system 15200 according to some embodiments. As used herein, the communication system 15200 includes multiple access points (APs) 15210 (with four exemplary APs 15210A, 15210B, 15210C, and 15210D being depicted) and multiple wireless devices, referred to in the context of communication system 15200 as stations (STAs) 15212 (referred to individually as STA 15212A, STA 15212B, STA 15212C, STA 15212D, and STA 15212E). STA 15212A is served byAP 15210A in a first basic service set (BSS) 15220A. STA 15210B and STA 15210C are served by AP 15210B in a second BSS, BSS 15220B. STA 15212D is served by AP 15210C in a third BSS, BSS 15220C. STA 15212E is served by AP 15210D in a fourth BSS, BSS 15220D. Stations 15212 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 15212 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0537] Each of STAs 15212 may connect through a radio link to one of APs 15210. For example, depending on location or channel conditions experienced by a given STA 15212, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more OFDM carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.Each AP 15210 may provide data connectivity to STAs 15212 connected to a particular AP 15210. As illustrated, APs 15210 may be connected to a data network 15230. In this way, APs 15210 may also provide data connectivity between STAs 15212 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA 15212 and its serving AP 15210 may be used for providing various kinds of services to STA 15212, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 15212 and / or on a device linked to STA 15212. Byway of example, Figure 8 illustrates an application service platform 15232 provided in data network 15230. The application(s) executed on STA 15212 and / or on one or more other devices linked to STA 15212 may use the radio link for data communication with one or more other STA 15212 and / or the application service platform 15232, thereby enabling utilization of the corresponding service(s) at STA 15212.

[0538] Figure 9 shows a wireless device 15300 being an example of the first UE 121, which may be configured to operate in communication system 15100 of Figure 7 or in communication system 15200 of Figure 8. The wireless device 15300 may be alternatively referred to as a UE 15300, like a UE 15112 within the context of communication system 15100, or as a station (STA) 15300 or as a non-access-point station (non-AP STA) 15300, like a STA 15212 within the context of the communication system 15200, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices.

[0539] Examples of a wireless device include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, and wireless terminal. Other examples include any type of UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

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

[0541] In particular embodiments, wireless device 15300 includes processing circuitry 15302 that is operatively coupled via a bus 15304 to an input / output interface 15306, a power source 15308, a memory 15310, a communication interface 15312, and / or any other component, or any combination thereof. Certain embodiments of wireless device 15300 may include all or a subset of the components shown in Figure 9. The level of integration between the components may vary from one embodiment of wireless device 15300 to another. In general, in a particular embodiment of wireless device 15300, processing circuitry 15302, input / output interface 15306, power source 15308, memory 15310, and communication interface 15312 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 15300. Further, certain embodiments of wireless devices 15300 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

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

[0543] In the example, the input / output interface 15306 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into wireless device 15300. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximitysensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0544] In some embodiments, the power source 15308 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used to supply power to circuitry or to charge an associated battery. The power source 15308 may further include power circuitry for delivering power from the power source 15308 itself, and / or an external power source, to the various parts of wireless device 15300 via input circuitry or an interface such as an electrical power cable. Power source 15308 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 15300 to which power is supplied.

[0545] The memory 15310 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), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 15310 includes one or more programs 15314, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 15316. The memory 15310 may store, for use by wireless device 15300, any of a variety of various operating systems or combinations of operating systems.

[0546] The memory 15310 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 15310 may allow wireless device 15300 to access instructions, programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 15310, which may be or comprise a device-readable storage medium.The processing circuitry 15302 may be configured to communicate with an access network or other network via or using the communication interface 15312. The communication interface 15312 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 15322. The communication interface 15312 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another wireless device or a network node in an access network). Each transceiver may include a transmitter 15318 and / or a receiver 15320 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 15318 and receiver 15320 may be coupled to one or more antennas (e.g., antenna 15322) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0547] In the illustrated embodiment, communication functions of the communication interface 15312 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing 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 networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0548] In particular embodiments, wireless device 15300 may provide an output of data captured via a sensor, through its communication interface 15312, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 15300 can be communicated through a wireless connection to a network node via another wireless device 15300. In particular embodiments, such output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

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

[0550] Wireless device 15300, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smartwatch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. In particular embodiments, wireless device 15300 represents an loT device that comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the example embodiment of wireless device 15300 shown in Figure 9.

[0551] As yet another specific example, in an loT scenario, wireless device 15300 may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another wireless device and / or a network node. Wireless device 15300 may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, wireless device 15300 may implement the 3GPP NB-loT standard. In other scenarios, wireless device 15300 may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0552] In practice, any number of wireless devices 15300 may be used together with respect to a single use case. For example, a first wireless device 15300 might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second wireless device 15300 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 15300 may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second wireless device 15300 can also include more than one of the functionalities described above. For example, wireless device 15300 might comprise thesensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0553] Figure 10 shows a network node 15400, being an example of the first network node 101 and / or the second network node 102, in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunications network. In accordance with respective embodiments, network node 15400 may be configured to operate in communication system 15100 of Figure 7, like network nodes 15108 or 15110, or in communication system 15200 of Figure 8, like an AP 15210 or a station 15212. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0554] Network nodes 15400 may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Network node 15400 may be a relay node or a relay donor node controlling a relay. Network nodes 15400 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

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

[0556] In particular embodiments, network node 15400 includes a processing circuitry 15402, a memory 15404, a communication interface 15406, and a power source 15408. In general, in a particular embodiment of network node 15400, processing circuitry 15402, memory 15404, communication interface 15406, and power source 15408 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 15400.The network node 15400 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 15400 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 15400 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 15404 or portions of memory 15404 for different RATs) and some components may be reused (e.g., a same antenna 15410 may be shared by different RATs). The network node 15400 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 15400, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 15400.

[0557] The processing circuitry 15402 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other components, such as the memory 15404, to provide network node 15400 functionality.

[0558] In some embodiments, the processing circuitry 15402 includes a system on a chip (SOC). In some embodiments, the processing circuitry 15402 includes one or more of radio frequency (RF) transceiver circuitry 15412 and baseband processing circuitry 15414. In some embodiments, the RF transceiver circuitry 15412 and the baseband processing circuitry 15414 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 15412 and baseband processing circuitry 15414 may be on the same chip or set of chips, boards, or units.

[0559] The memory 15404 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processingcircuitry 15402. The memory 15404 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 15402 and utilized by the network node 15400. The memory 15404 may be used to store any calculations made by the processing circuitry 15402 and / or any data received via the communication interface 15406. In some embodiments, the processing circuitry 15402 and memory 15404 is integrated.

[0560] The communication interface 15406 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 15406 comprises port(s) / terminal(s) 15416 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 15300 may be capable of wireless communication and communication interface 15406 may also include radio front-end circuitry 15418 that may be coupled to, or in certain embodiments a part of, an antenna 15410. Particular embodiments of radio front-end circuitry 15418 include filter(s) 15420 and amplifier(s) 15422. The radio frontend circuitry 15418 may be connected to an antenna 15410 and processing circuitry 15402. The radio front-end circuitry may be configured to condition signals communicated between antenna 15410 and processing circuitry 15402. The radio front-end circuitry 15418 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 15418 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 15420 and / or amplifiers 15422. The radio signal(s) may then be transmitted via the antenna 15410. Similarly, when receiving data, the antenna 15410 may collect radio signals which are then converted into digital data by the radio front-end circuitry 15418. The digital data may be passed to the processing circuitry 15402. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0561] In certain alternative embodiments, network node 15400 may be capable of wireless communication but does not include separate radio front-end circuitry 15418, instead, the processing circuitry 15402 includes radio front-end circuitry and is connected to the antenna 15410. Similarly, in some embodiments, all or some of the RF transceiver circuitry 15412 is part of the communication interface 15406. In still other embodiments, the communication interface 15406 includes one or more ports or terminals 15416, the radio front-end circuitry 15418, and the RF transceiver circuitry 15412, as part of a radio unit (not shown), and the communication interface 15406 communicates with the baseband processing circuitry 15414, which is part of a digital unit (not shown).The antenna 15410 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 15410 may be coupled to the radio frontend circuitry 15418 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 15410 is separate from the network node 15400 and connectable to the network node 15400 through one or more interfaces or ports.

[0562] The antenna 15410, communication interface 15406, and / or the processing circuitry 15402 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node 15400. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 15410, the communication interface 15406, and / or the processing circuitry 15402 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 15400. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0563] The power source 15408 provides power to the various components of network node 15400 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 15408 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 15400 with power for performing the functionality described herein. For example, the network node 15400 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 15408. As a further example, the power source 15408 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0564] Embodiments of the network node 15400 may include additional components beyond those shown in Figure 10 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 15400 may include user interface equipment to allow input of information into the network node 15400 and to allow output of information from the network node 15400. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 15400.

[0565] Figure 11 is a block diagram illustrating a virtualization environment 15500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may includevirtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 15500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 15500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

[0566] Applications 15502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 15400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0567] Hardware 15504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 15506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 15508A and VM 15508B (which may be collectively referred to as VMs 15508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 15506 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 15508.

[0568] The VMs 15508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 15506. Different embodiments of the instance of a virtual appliance 15502 may be implemented on one or more of VMs 15508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0569] In the context of NFV, each of the VMs 15508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 15508, and that part of hardware 15504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs,forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more of the VMs 15508 on top of the hardware 15504 and corresponds to an application 15502.

[0570] Hardware 15504 may be implemented in a standalone network node with generic or specific components. Hardware 15504 may implement some functions via virtualization.

[0571] Alternatively, hardware 15504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 15510, which, among others, oversees lifecycle management of applications 15502. In some embodiments, hardware 15504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 15512 which may alternatively be used for communication between hardware nodes and radio units.

[0572] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0573] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certainembodiments 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 functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0574] The embodiments herein are not limited to the above-described preferred embodiments. Various alternatives, modifications and equivalents may be used.

[0575] It will be appreciated that the foregoing description and the accompanying drawings represent non-limiting examples of the methods and apparatus taught herein. As such, the apparatus and techniques taught herein are not limited by the foregoing description and accompanying drawings. Instead, the embodiments herein are limited only by the following claims and their legal equivalents.

Claims

CLAIMS1. A method performed by a first network node (101) for handling resources in a wireless communication network (100), the method comprising:receiving (301) a first message from a second network node (102), wherein the first message comprises first data associated with one or more Random Access, RA, procedures for early Uplink, UL, synchronization to be used by one or more User Equipments, UE;receiving (303) a second message from the second network node (102), wherein the second message comprises a first identifier associated with a first RA procedure for early UL synchronization and second data associated with the first RA procedure, the first RA procedure being performed by a first UE (121), wherein the second data comprises a preamble index used by the first UE (121), a timing advance, TA, value associated with the first RA procedure performed by the first UE (121), and any one or more out of:• a Physical Random Access Channel, PRACH, occasion used by the first UE (121),• a Synchronization Signal Block, SSB, index,• an SSB position in a burst,• a PRACH mask Index, or• an indication of a type of carrier;deriving (304) a second identifier based on the first data comprised in the first message and the second data comprised in the second message;determining (305) whether the derived second identifier is equal to the first identifier; andresponsive the second identifier being equal to the first identifier, identifying (306) the first UE (121) having performed the first RA procedure.

2. The method according to claim 1, further comprisingtransmitting (308) to the identified UE (121) the TA value in the second data.

3. The method according to any of the claims 1-2, wherein the first identifier comprises a first RA Radio Network Temporary Identifier, RA-RNTI, and the second identifier comprises a second RA-RNTI.

4. The method according to any of the claims 1-3, wherein the first data comprises any one or more out of:- one or more PRACH occasions,- one or more preamble indexes,- a preamble index available to be used by a UE,- a PRACH occasion available to be used by a UE,- an SSB index,- an SSB position in a burst,- a PRACH mask Index,- an indication of a type of carrier,- an Orthogonal Frequency Division Multiplexing, OFDM, symbol of the PRACH occasion available to be used by a UE,- an index of a slot of the PRACH occasion available to be used by a UE,- a subcarrier spacing, e.g., associated to the index of the slot of the PRACH occasion that can be used by a UE,- an index of the PRACH occasion in the frequency domain, and- an indication of an RA type.

5. The method according to any of the claims 1-4, wherein any of the first message and the second message is exchanged between the first network node (101) and the second network node (102) using an F1AP procedure or an XnAP procedure.

6. The method according to any of the claims 1-5, wherein the method further comprises:transmitting (305) a third message to the second network node (102), the third message acknowledging the reception of the first message and / or the second message.

7. The method according to any of the claims 1-6, further comprising:transmitting (302) to the first UE (121) an RA triggering message comprising the first data, the RA triggering message triggering the first UE (121) to perform the first RA procedure for early UL synchronization.

8. A method performed by a second network node (102) for handling resources in a wireless communication network (100), the method comprising:transmitting (401) a first message to a first network node (101), the first message comprising first data associated with one or more Random Access, RA, procedures for early Uplink, UL, synchronization to be used by one or more User Equipments, UE; andtransmitting (403) a second message to the first network node (101), wherein the second message comprises a first identifier associated with a first RA procedure for early UL synchronization and second data associated with the first RA procedure, the first RA procedure being performed by a first UE (121), wherein the second data comprises a preamble index used by the first UE (121), a timing advance, TA, value associated with the first RA procedure performed by the first UE (121), and any one or more out of:• a Physical Random Access Channel, PRACH, occasion used by the first UE (121),• a Synchronization Signal Block, SSB, index,• an SSB position in a burst,• a PRACH mask Index, or• an indication of a type of carrier.

9. The method according to claim 8, wherein the first identifier comprises a first RA Radio Network Temporary Identifier, RA-RNTI.

10. The method according to any of the claims 8-9, wherein the first data comprises any one or more out of:- one or more PRACH occasions,- one or more preamble indexes,- a preamble index available to be used by a UE,- a PRACH occasion available to be used by a UE,- an SSB index,- an SSB position in a burst,- a PRACH mask Index,- an indication of a type of carrier,- an Orthogonal Frequency Division Multiplexing, OFDM, symbol of the PRACH occasion available to be used by a UE,- an index of a slot of the PRACH occasion available to be used by a UE,- a subcarrier spacing, e.g., associated to the index of the slot of the PRACH occasion that can be used by a UE,- an index of the PRACH occasion in the frequency domain, and- an indication of an RA type.

11. The method according to any of the claims 8-10, wherein any of the first message and the second message is exchanged between the first network node (101) and the second network node (102) using an F1AP procedure or an XnAP procedure.

12. The method according to any of the claims 8-11, wherein the method further comprises:receiving (404) a third message from the first network node (101), the third message acknowledging the reception of the first message and / or the second message.

13. The method according to any of the claims 8-11, wherein the method further comprises:obtaining (402) the second data comprised in the second message.

14. A computer program comprising instructions, which when executed by a processor, causes the processor to perform actions according to any of the claims 1-13, as performed by the first network node and the second network node, respectively.

15. A carrier comprising the computer program of claim 14, wherein the carrier is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

16. A first network node (101) for handling resources in a wireless communication network (100), wherein the first network node is configured to:receive a first message from a second network node (102), wherein the first message comprises first data associated with one or more Random Access, RA, procedures for early Uplink, UL, synchronization to be used by one or more User Equipments, UE;receive a second message from the second network node (102), wherein the second message comprises a first identifier associated with a first RA procedure for early UL synchronization and second data associated with the first RA procedure, the first RA procedure being performed by a first UE (121), wherein the second data comprises a preamble index used by the first UE (121), a timing advance, TA, value associated with the first RA procedure performed by the first UE (121), and any one or more out of:• a Physical Random Access Channel, PRACH, occasion used by the first UE (121),• a Synchronization Signal Block, SSB, index,• an SSB position in a burst,• a PRACH mask Index, or• an indication of a type of carrier;derive a second identifier based on the first data comprised in the first message and the second data comprised in the second message;determine whether the derived second identifier is equal to the first identifier; andresponsive the second identifier being equal to the first identifier, identify the first UE (121) having performed the first RA procedure.

17. The first network node (101) according to claim 16, wherein the first network node is configured to transmit to the identified UE (121) the TA value in the second data.

18. The first network node (101) according to any of the claims 16-17, wherein the first identifier comprises a first RA Radio Network Temporary Identifier, RA-RNTI, and the second identifier comprises a second RA-RNTI.

19. The first network node (101) according to any of the claims 16-18, wherein the first data comprises any one or more out of:- one or more PRACH occasions,- one or more preamble indexes,- a preamble index available to be used by a UE,- a PRACH occasion available to be used by a UE,- an SSB index,- an SSB position in a burst,- a PRACH mask Index,- an indication of a type of carrier,- an Orthogonal Frequency Division Multiplexing, OFDM, symbol of the PRACH occasion available to be used by a UE,- an index of a slot of the PRACH occasion available to be used by a UE,- a subcarrier spacing, e.g., associated to the index of the slot of the PRACH occasion that can be used by a UE,- an index of the PRACH occasion in the frequency domain, and- an indication of an RA type.

20. The first network node (101) according to any of the claims 16-19, configured to exchange any of the first message and the second message between the first network node (101) and the second network node (102) using an F1AP procedure or an XnAP procedure.

21. The first network node (101) according to any of the claims 16-20, wherein the first network node (101) is configured to:transmit a third message to the second network node (102), the third message acknowledging the reception of the first message and / or the second message.

22. The first network node (101) according to any of the claims 16-21, wherein the first network node (101) is configured to:transmit to the first UE (121) an RA triggering message comprising the first data, the RA triggering message triggering the first UE (121) to perform the first RA procedure for early UL synchronization.

23. A second network node (102) for handling resources in a wireless communication network (100), wherein the second network node (102) is configured to:transmit a first message to a first network node (101), the first message comprising first data associated with one or more Random Access, RA, procedures for early Uplink, UL, synchronization to be used by one or more User Equipments, UE; andtransmit a second message to the first network node (101), wherein the second message comprises a first identifier associated with a first RA procedure for early UL synchronization and second data associated with the first RA procedure, the first RA procedure being performed by a first UE (121), wherein the second data comprises a preamble index used by the first UE (121), a timing advance, TA, value associated with the first RA procedure performed by the first UE (121), and any one or more out of:• a Physical Random Access Channel, PRACH, occasion used by the first UE (121),• a Synchronization Signal Block, SSB, index,• an SSB position in a burst,• a PRACH mask Index, or• an indication of a type of carrier.

24. The second network node (102) according to claim 23, wherein the first identifier comprises a first RA Radio Network Temporary Identifier, RA-RNTI.

25. The second network node (102) according to any of the claims 23-24, wherein the first data comprises any one or more out of:- one or more PRACH occasions,- one or more preamble indexes,- a preamble index available to be used by a UE,- a PRACH occasion available to be used by a UE,- an SSB index,- an SSB position in a burst,- a PRACH mask Index,- an indication of a type of carrier,- an Orthogonal Frequency Division Multiplexing, OFDM, symbol of the PRACH occasion available to be used by a UE,- an index of a slot of the PRACH occasion available to be used by a UE,- a subcarrier spacing, e.g., associated to the index of the slot of the PRACH occasion that can be used by a UE,- an index of the PRACH occasion in the frequency domain, and- an indication of an RA type.

26. The second network node (102) according to any of the claims 23-25, configured to exchange any of the first message and the second message between the first network node (101) and the second network node (102) using an F1AP procedure or an XnAP procedure.

27. The second network node (102) according to any of the claims 23-26, wherein the second network node (102) is configured to:receive a third message from the first network node (101), the third message acknowledging the reception of the first message and / or the second message.

28. The second network node (102) according to any of the claims 23-27, wherein the second network node (102) is configured to:obtain the second data comprised in the second message.

Images