Network node, user equipment, and methods implemented in the network node and user equipment

Abstract

Embodiments herein provide a method, implemented by a UE (10), for handling communications in a communications network, in which the UE (10) provides to a network node (150) an RA report of an RA procedure on a first RAT for the UE (10) and assistance information instructing how the RA report should be routed between a second radio network node (13) of a second RAT that collects the RA report and a first radio network node (12) of the first RAT that controls a cell in which the RA procedure logged in the RA report was performed.

Description

[Technical Field]

[0001]

[0001] The present disclosure relates to a network node, a user equipment (UE), and a method implemented in the network node and the UE, relating to communications.

[0002] Further, a computer program and a computer-readable storage medium are also provided herein.

[0003] In particular, the present disclosure relates to handling reports in a communications network. [Background technology]

[0002] In a typical communication network, UEs, also known as wireless communication devices, mobile stations, stations (STAs) and / or wireless devices, communicate with one or more core networks (CNs) through a radio access network (RAN). The RAN covers a geographic area that is divided into service areas or cells, and each service area or cell is served by a radio network node, such as an access node, e.g., a Wi-Fi access point or a radio base station (RBS), which in some networks may be referred to as a Node B, gNode B, or eNode B. A service area or cell is a geographic area where radio coverage is provided by a radio network node. The radio network node operates on radio frequencies to communicate over the air interface with UEs within range of the radio network node. The radio network node communicates to the UE via a downlink (DL), and the UE communicates to the radio network node via an uplink (UL).

[0003] The Universal Mobile Telecommunications System (UMTS) is a third-generation (3G) communications network that evolved from the second-generation (2G) Global System for Mobile Communications (GSM). The UMTS Terrestrial Radio Access Network (UTRAN) is essentially a RAN that uses Wideband Code Division Multiple Access (WCDMA) and / or High-Speed ​​Packet Access (HSPA) for communications with user equipment. In a forum known as the Third Generation Partnership Project (3GPP), communications suppliers propose and agree on standards for current and future generations of networks, exploring, for example, enhanced data rates and radio capacity. In some RANs, as in UMTS, several radio network nodes may be connected, for example, by landlines or microwaves, to a controller node, such as a radio network controller (RNC) or base station controller (BSC), which monitors and coordinates the various activities of multiple radio network nodes connected to the controller node. The RNC is typically connected to one or more core networks.

[0004] Specifications for the Evolved Packet System (EPS) are being finalized within 3GPP and will be addressed in the next 3GPP Release (Rel), such as New Radio (NR). The EPS comprises an Enhanced Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long-Term Evolution (LTE) radio access network, and an Evolved Packet Core (EPC), also known as the System Architecture Evolution (SAE) core network. E-UTRAN / LTE is a 3GPP radio access technology in which radio network nodes are directly connected to the EPC core network. Thus, the RAN in the EPS has an essentially "flat" architecture, with radio network nodes directly connected to one or more core networks.

[0005] In emerging 5G technologies, such as NR, using a large number of transmit and receive antenna elements can be important because it allows for the use of beamforming, such as transmit and receive beamforming. Transmit beamforming means that the transmitter can amplify the transmit signal in one or more selected directions and suppress the transmit signal in other directions. Similarly, on the receive side, the receiver can amplify signals from one or more selected directions and suppress unwanted signals from other directions.

[0006] In most cases, uplink transmissions in cellular networks are controlled by the network, i.e., UEs only transmit uplink data in dedicated slots assigned by the network, and the risk of collisions between uplink transmissions from different UEs is minimal. However, upon initial access from an idle / inactive state, there is no connection to the network and the UE has no dedicated resources. Furthermore, the network has no means to estimate the UE's transmission time based on previous transmissions. Therefore, it is common to have collisions between uplink transmissions from different UEs.

[0007] A random access (RA) procedure is designed to solve this problem. In the random access procedure, the UE sends an initial preamble, such as a random access channel (RACH) preamble, to the network, and exchanges messages aimed at resolving potential contention issues, exchanging timing information, uplink grants, etc.

[0008] Further use cases for the random access procedure include: 1) Handover when synchronization is required in the new cell. 2) Re-establishing uplink synchronization to the current cell, which can occur due to long periods of inactivity on the uplink. 3) Requesting an uplink scheduling grant if one has not been provided to the UE. 4) Requesting transmission of non-broadcast system information blocks (SIBs).

[0009] There are two types of random access procedures: contention-free random access (CFRA), in which the UE is provided with a dedicated preamble, and contention-based random access (CBRA), in which the UE makes random access based on some common preamble.

[0010] Furthermore, based on the message / signaling exchange between the network and the UE, both CBRA and CFRA can be further divided into two procedures.

[0011] 4-step RA. The following exchanges between the UE and the network take place in the four-step RA shown in FIG.

[0012] Step 1: The device transmits a preamble, also known as a physical random access channel (PRACH), which is designed for low-complexity reception despite the lack of timing control.

[0013] Step 2: The network sends along a Random Access Response (RAR) indicating receipt of the preamble and providing a time alignment command based on the timing of the received preamble.

[0014] Steps 3 and 4: The UE and the network exchange messages 3 and 4 with the aim of resolving potential collisions.

[0015] 2-step RA. In the 2-step RA, the procedure is simplified, i.e., the PRACH and message 3 of the 4-step RA are combined into one message, i.e., message A, and the RAR and message 4 are combined into another message, i.e., message B. The aim of this procedure is to allow faster access, see Figure 2.

[0016] Multi-Radio Dual Connectivity (MR-DC) is a generalization of E-UTRA dual connectivity in which a multiple Tx / Rx capable UE can be configured to utilize resources provided by two different nodes connected via a non-ideal backhaul: one providing NR access and the other providing either E-UTRA or NR access. One node acts as the master node (MN) and the other node or nodes act as secondary nodes (SNs). Further details can be found in 3GPP 37.340; Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Stage2-V17.3.0.

[0017] E-UTRAN supports MR-DC via E-UTRA-NR Dual Connectivity (EN-DC), where a UE is connected to one eNB acting as MN and one en-gNB acting as SN. The eNB is connected to the EPC via the S1 interface and to the en-gNB via the X2 interface.

[0018] Figure 3 shows the control plane connectivity for the EN-DC.

[0019] From a radio protocol perspective, the control plane for the EN-DC is shown in FIG.

[0020] Figure 4 shows the control plane architecture for the EN-DC.

[0021] Therefore, all UE control plane signaling is transmitted via the E-UTRAN eNB. There is no control plane connection between the gNB and the EPC. The overall architecture for the EN-DC shows that the en-gNB is connected to one eNB via X2, and therefore the en-gNB does not have multiple X2 connections to different eNBs as shown in Figure 5. Figure 5 shows the EN-DC overall architecture.

[0022] RA report in NR. A basic form of RACH reporting from the UE was introduced in LTE. However, in NR Rel-16, extensive reports are collected and analyzed at the network node for optimization purposes. An excerpt from 38.331;NR;Radio Resource Control (RRC);Protocol specification;V-17.3.0, 3GPP is also provided below. A list of RA reports is collected by the UE and provided to the network upon network request. Details of the collection mechanism can be found in 38.331;NR;Radio Resource Control (RRC);Protocol specification;V-17.3.0, 3GPP. (Formula 1) Summary of the Invention

[0023] As part of developing the embodiments herein, one or more problems were identified. In MR-DC, the RACH report collection mechanism is defined only for the MN. Therefore, the UE may collect RACH reports for both the MN and the SN, but only the MN can fetch the reports. Furthermore, the RACH report list may contain RACHs implemented by the UE in different cells. It is up to the collection node to distribute the reports to the appropriate nodes.

[0024] The Rel-18 Self-Organizing Network (SON) Work Item (WI) includes ongoing work on RACH optimization. One such discussion concerns improving NR RACH reporting in the EN-DC. Under this discussion, it was agreed that an MN, such as an EUTRAN eNB, will be able to collect RACH reports of an SN, such as an NR gNB, from a UE. Furthermore, R2-2211164, Reply LS on SN RACH report status in R17, 3GPP TSG RAN WG#120, proposed that the UE should report NR Primary Secondary Cell (PSCell) identity information outside of the RACH report to aid in forwarding the report.

[0025] In EN-DC, the UE may perform a random access procedure in the SN, i.e., an NR node, and store an RA report. Such RA reports stored by the UE are coded in NR format and contain only NR cell information. After spending time in the RRC_INACTIVE or RRC_IDLE state, the UE may connect to a different EUTRAN cell upon handover(s) or cell reselection. If the new cell collects the RACH report from the UE, the new cell will not be able to read the NR cell information and forward the NR RA report initially stored by the UE to the appropriate NR node.

[0026] That is, the new eNB serving the UE needs to know the cell identity of the cell where the access generated the RA report in order to forward the RA report to the NR node serving that cell. This allows the NR node to analyze the report and infer from it information that may be useful for optimizing the RACH configuration. The proposal in R2-2211164, Reply LS on SN RACH report status in R17, 3GPP TSG RAN WG#120, to include PSCell information outside the NR RA report is not sufficient because if the NR RA report is later collected at a different EUTRAN node, the collecting node may not have an X2 connection with the NR RAN node controlling the cell where the random access procedure logged in the RA report was performed, and therefore the collecting node would not be able to forward the RA report. Furthermore, the E-UTRAN node collecting the NR RA report from the UE may be connected to a different mobility management entity (MME) compared to the eNB serving as the MN node due to the EN-DC connection where the NR node associated with the NR RA report served as the SN node. In such cases, the Xn connection between the new serving RAN node and the previous NR SN and / or previous E-UTRA MN may not be available. Therefore, the RA report cannot be forwarded to the NR node when a RACH access occurs.

[0027] R2-2211164, Reply LS on SN RACH report status in R17, a proposal in 3GPP TSG RAN WG#120, is also insufficient because it does not require the UE to read the NR Cell Global Identity (CGI) of the PSCell. Therefore, reporting PSCell information outside of the RA report may not be possible or it may be limited to partial PSCell information.

[0028] Another problem occurs when a UE initially in NR single connectivity with a first gNB performs an RA to an NR cell and logs a respective NR RA report. The UE then reselects a E-UTRAN cell served by an eNB that does not have Xn connectivity to the first gNB associated with the NR RA report. If the first gNB did not fetch the NR RA report before the UE reselected the E-UTRAN cell, the eNB cannot forward the NR RA report to the first gNB.

[0029] The goal of this specification is to provide a mechanism for handling communications in a communications network in an efficient manner.

[0030] According to one aspect, the objective is achieved by providing a method, implemented by a UE, for handling communications in a communication network according to an embodiment of the present specification. The UE may obtain RA parameters of an RA procedure and may receive a request to provide an RA report from a second radio network node, such as an LTE eNB, of a second RAT, such as LTE. The UE provides, e.g., transmits to the network node, an RA report of an RA procedure on a first RAT for the UE and assistance information instructing how the RA report should be routed between a second radio network node of the second RAT that collects the RA report and a first radio network node of the first RAT that controls a cell for which the RA procedure logged in the RA report was performed.

[0031] According to another aspect, the objective is achieved by providing a method for handling communications in a communications network according to an embodiment of the present specification, the method being implemented by a network node, such as a second radio network node or a first / second network node. The network node obtains an RA report of an RA procedure of a first RAT for a UE and assistance information instructing how the RA report should be routed between a second radio network node of a second RAT that collects the RA report and a first radio network node that controls a cell in which the RA procedure logged in the RA report was performed. The second radio network node forwards the RA report based on the assistance information.

[0032] According to one aspect, the objective is achieved in accordance with embodiments herein by providing a network node and a UE, each configured to perform the methods herein.

[0033] Thus, according to one aspect, the objective is achieved by providing a UE for handling communications in a communications network according to embodiments herein, wherein the UE is configured to provide, e.g., transmit, to a network node, an RA report of an RA procedure on a first RAT for the UE, and also to provide assistance information instructing how the RA report should be routed between a second radio network node of a second RAT that collects the RA report and a first radio network node of a first RAT that controls a cell for which the RA procedure logged in the RA report was performed.

[0034] According to another aspect, the objective is achieved by providing a network node, such as a second radio network node or a first / second network node, for handling communications in a communications network according to an embodiment of the present specification. The network node is configured to obtain, for a UE, an RA report of an RA procedure of a first RAT and assistance information instructing how the RA report should be routed between a second radio network node of a second RAT that collects the RA report and a first radio network node that controls a cell in which the RA procedure logged in the RA report was performed. The network node is further configured to forward the RA report based on the assistance information.

[0035] Further provided herein is a computer program product comprising instructions that, when executed on at least one processor, cause the at least one processor to perform any of the methods herein performed by the network node and the UE, respectively. Further provided herein is a computer-readable storage medium having stored thereon a computer program product comprising instructions that, when executed on at least one processor, cause the at least one processor to perform any of the methods herein performed by the network node and the UE, respectively.

[0036] Embodiments herein disclose procedures, such as methods, to be implemented by a UE operating in dual connectivity to include one or more identifiers that may lead to the identification of a first network node, such as a MN, of an access network type, such as NR or LTE, and that enable forwarding of information to a first or another first network node (SN) connected to a third network node.

[0037] In one embodiment, such assistance information may be included in an information element (IE) for transporting an NR RA report, hereinafter referred to as an "NR RA report container," where the NR RA report container includes a list of first reports, e.g., RA-ReportList, where the first report, e.g., NR RA report, includes a report of a random access procedure performed in a first access network type, e.g., NR. The method involves the UE performing one or more of the following: Logging random access procedure related information in a first report, such as an RA report, if the random access is performed in a cell belonging to a first network node, e.g., that supports NR. The UE may log a list of the first reports, e.g., an RA-ReportList, which may comprise n such first reports. o Including cell information of a second network node, e.g., MN, belonging to a second access network type, e.g., LTE, as part of the first report, e.g., RA report. A first indication may be sent to the network regarding the capability to include the first report in the UEInformationResponse message. A second indication may be sent to the network regarding the ability to include additional or assisting information as items in a list in the UEInformationResponse message. A request to provide the first report may be received from a second network node of a second access network type, e.g., LTE, e.g., an LTE eNB. o The UE may receive an explicit request to provide a first report. The UE may not receive an explicit request to provide the first report. The UE may receive a request to provide random access related information belonging to the second access network type. A list of first reports, e.g., RA-ReportList, may be included in the NR RA report container, and for each first report, e.g., RA report, in that list, assistance information needed to route the RA report to a first network node belonging to the first / second RAT may be included as an item in the list in the UEInformationResponse message. Thus, for each first report in the list of first reports, the RA report container may have an item with such assistance information in its list. In one embodiment, the assistance information used to identify the MN, a third radio network node, may consist of a CGI of the primary cell (PCell) served by the MN. The PCell CGI includes the MN's global node ID, which may be used to identify the MN. Using this information, a RAN node, such as a second radio network node, receiving the RA report (from the UE) may be able to forward the RA report to the CN. The CN may be able to forward the RA report to the SN where one or more reports were generated, the MN connected to the first radio network node. The MN may then forward such report to one or more SN nodes connected to the MN where the report was generated. o In another embodiment, the assistance information used to identify the MN may consist of the CGI and Tracking Area Identifier (TAI) of the PCell served by the MN and serving the UE when one or more RA reports are logged. The PCell CGI includes the MN's global node ID, which may be used to identify the MN, and the PCell's TAI may be used to route the message containing the RA report to the MN via one or more nodes in the core network. Using this information, the RAN node receiving the RA report may be able to forward the RA report to the CN. The CN may be able to forward the RA report to the MN connected to the SN where the one or more reports were generated. Such forwarding may potentially occur via other CN nodes connected to the MN. The MN may then forward such reports to one or more SN nodes connected to the MN where the reports were generated. In another embodiment, the assistance information used to identify the MN may consist of a CGI of the PSCell served by the SN where the RACH access occurred, generating one or more RA reports logged by the UE. The PSCell CGI includes the global node ID of the SN, also referred to as spCell-ID or PScell-ID. This information may be signaled to the CN along with the RA report. The CN may identify the MN to which the RA report needs to be forwarded, since the CN is aware that the SN identified by the global node ID in the PSCell CGI is connected to the target MN. Using this information, the RAN node receiving the RA report may be able to forward the RA report to the CN. The CN may be able to forward the RA report to the MN connected to the SN where the one or more reports were generated, since the CN can derive the SN global node ID from the PSCell CGI, and the CN knows that the SN to which the RA report needs to be forwarded is connected to a specific node, i.e., the MN, and therefore can derive the identity of the MN to which the RA report needs to be forwarded. Thus, the CN may forward RA reports to the MN, which may then forward such reports to one or more SN nodes connected to the MN where the reports were generated. In another embodiment, the assistance information used to identify the MN may consist of the CGI and TAI of the PCell served by the MN. Furthermore, the information includes the Physical Cell Identity (PCI) and / or CGI of the PSCell served by the SN where the RACH access occurred generating one or more RA reports logged by the UE. Using this information, the RAN node receiving the RA report may be able to forward the RA report to the CN. The CN may be able to forward the RA report to the MN connected to the SN where the one or more reports were generated. Such forwarding may potentially occur via other CN nodes connected to the MN. The MN may then forward such report to one or more SN nodes connected to the MN where the report was generated. o The above is because the TAI of the PCell can be used by the CN to route a message containing an RA report to a CN node connected to the MN. The PCell CGI contains the MN's global node ID, which can be used by a CN node receiving information to identify the MN. On the other hand, the PSCell PCI and / or CGI can be used by the MN to forward the received RA report to the appropriate SN. Using this information, the MN can identify the cells served by the SN to which the corresponding RA report needs to be forwarded, as it knows the PCI / CGI of those cells. Assuming that the PCI of the PSCell is not reused in the vicinity of the PCell, the MN can identify the SN serving the cell identified by the PSCell PCI and forward the RA report to that SN. Alternatively or additionally, the PSCell CGI can be used for such purpose.

[0038] Embodiments herein may propose, for example, a method to be implemented by a network node in a network (ie, a network node, such as an eNB, MME, or the like). A first indication may be received from the UE regarding the capability to include a first report list in the UEInformationResponse message. A second indication may be received from the UE regarding the capability to include the assistance information as an item in the list in the UEInformationResponse message. The UE may be requested to send an RA report or a list of first reports to provide. In one example, the network node may send an explicit request to provide a list of first reports. In another example, the network node may not send an explicit request to provide the first list of reports, but the network sends a request to provide a third report containing random access related information belonging to the second access network type. o In another example, the network node may send a request to the UE to provide a list of first reports if the list is available (i.e., an opportunistic request). The NR RA report container may be received from the UE as part of the UEInformationResponse message. The node(s) for the first report(s) may be identified and forwarded based on the assistance information in the NR RA report container. o Forwarding may involve other network nodes belonging to core networks of different technologies. The NR RA report container can be sent to the identified network node.

[0039] As an example, when a UE is connected in EN-DC mode, if the UE is logging an RA report of a random access procedure performed in an NR PSCell controlled by an NR SN, such as a first radio network node, and may be requested by another LTE eNB, such as a second radio network node, to send an RA report, the UE sends assistance information outside the NR SN RA report to enable propagation / routing of the RA report between the LTE eNB that collects the RA report and the NR gNB that controls the cell where the random access procedure logged in the RA report was performed, and the eNB (that requested the RA report) receives the assistance information. The solution further proposes an optional capability indicator sent from the UE to the eNB to enable the eNB to make an informed decision regarding the availability of an NR RA report and whether to request an NR RA report.

[0040] Therefore, a solution for handling communications in an efficient manner in a communications network is disclosed herein.

[0041] Embodiments will now be described in more detail with reference to the enclosed drawings. [Brief explanation of the drawings]

[0042] [Figure 1] FIG. 1 is an overview of the prior art. [Figure 2] FIG. 1 is an overview of the prior art. [Figure 3] FIG. 1 is an overview of the prior art. [Figure 4] FIG. 1 is an overview of the prior art. [Figure 5] FIG. 1 is an overview of the prior art. [Figure 6] 1 is a diagram illustrating an overview of a communication network according to embodiments herein; [Figure 7] 1 is a combined signaling scheme and flow chart illustrating an embodiment herein; [Figure 8] 1 is a flowchart illustrating a method performed by a UE according to an embodiment herein. [Figure 9] 1 is a flowchart illustrating a method performed by a network node according to embodiments herein. [Figure 10] FIG. 2 illustrates a schematic signaling flow according to some embodiments herein. [Figure 11] FIG. 2 illustrates a schematic signaling flow according to some embodiments herein. [Figure 12] FIG. 2 illustrates a schematic signaling flow according to some embodiments herein. [Figure 13] FIG. 2 illustrates a schematic signaling flow according to some embodiments herein. [Figure 14] FIG. 2 illustrates a schematic signaling flow according to some embodiments herein. [Figure 15] FIG. 2 is a block diagram illustrating an embodiment of a UE, in accordance with embodiments herein. [Figure 16] FIG. 2 is a block diagram illustrating an embodiment of a network node, according to embodiments herein. [Figure 17] FIG. 1 shows a schematic diagram of a communication network connected to a host computer via an intermediate network. [Figure 18] FIG. 1 is a generalized block diagram of a host computer communicating with user equipment via a base station over a partially wireless connection. [Figure 19] 1 is a flowchart illustrating a method implemented in a communication system including a host computer, a base station, and user equipment. [Figure 20] 1 is a flowchart illustrating a method implemented in a communication system including a host computer, a base station, and user equipment. [Figure 21] 1 is a flowchart illustrating a method implemented in a communication system including a host computer, a base station, and user equipment. [Figure 22]1 is a flowchart illustrating a method implemented in a communication system including a host computer, a base station, and user equipment. DETAILED DESCRIPTION OF THE INVENTION

[0043] Embodiments herein generally relate to communication networks. Figure 6 is an overview illustrating a communication network 1. The communication network 1 comprises one or more RANs and one or more CNs. The communication network 1 may use one or several different technologies. Although the embodiments herein relate to recent technology trends of particular interest in the NR context, the embodiments are also applicable in further evolutions of existing wireless communication systems, such as Wi-Fi, LTE, LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications (GSM) / Enhanced Data Rates for GSM Evolution (GSM / EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), to name just a few possible implementations.

[0044] The communication network 1 includes UEs 10, exemplified herein as wireless devices such as mobile stations, non-access point (non-AP) stations (STAs), STAs and / or wireless terminals, that communicate via one or more access networks (ANs), e.g., RANs, to one or more CNs. It should be understood by those skilled in the art that "UE" is a non-limiting term meaning any terminal, wireless communication terminal, user equipment, narrowband Internet of Things (NB-IoT) device, machine-type communication (MTC) device, device-to-device (D2D) terminal, or node, e.g., a smartphone, laptop computer, mobile phone, sensor, relay, mobile tablet, or even a small base station, that is capable of communicating using wireless communication with a radio network node within an area served by the radio network node.

[0045] The communication network 1 comprises a first radio network node 12, or simply radio network node, providing radio coverage over a geographical area, a first service area 11, or a first cell of a first RAT, such as NR, LTE, or the like. The first radio network node 12 may be a PScell ​​node, an access node, an access controller, a base station, e.g., a radio base station such as a gNodeB (gNB), an evolved NodeB (eNB, eNodeB), a NodeB, a base transceiver station, a wireless remote unit, an access point base station, a base station router, a wireless local area network (WLAN) access point or access point station (AP The first radio network node 12 may be a transmitting and receiving point such as a serving radio network node (STA), a transmission arrangement of a radio base station, a standalone access point, an en-gNB, an ng-eNB, a gNB-CU, a gNB-CU-CP, a gNB-CU-UP, an eNB-CU, an eNB-CU-CP, an eNB-CU-UP, an IAB node, an IAB donor DU, an IAB donor CU, an IAB-DU, an IAB-MT, an O-CU, an O-CU-CP, an O-CU-UP, an O-DU, an O-RU, an O-eNB, a cloud-based network function, a cloud-based centralized training node, or any other network unit or node capable of communicating with wireless devices in an area served by the radio network node depending, for example, on the first radio access technology and terminology used. The first radio network node 12 may be referred to as a serving radio network node, the service area may be referred to as a serving cell, and the serving network node communicates with the UE 10 in the form of DL transmissions to and UL transmissions from the UE 10. It should be noted that a service area may be referred to as a cell, beam, beam group, or the like to define an area of ​​wireless coverage.

[0046] The communication network 1 comprises a second radio network node 13 or another radio network node providing radio coverage over a geographical area, a second service area 14 or a second cell of a second RAT, such as NR, LTE or similar. The second radio network node 13 may be a transmitting and receiving point such as an access node, an access controller, a base station, e.g., a radio base station such as a gNB, eNB, eNodeB, Node B, base transceiver station, wireless remote unit, access point base station, base station router, WLAN access point or AP STA, a radio base station transmission arrangement, a standalone access point, en-gNB, ng-eNB, gNB-CU, gNB-CU-CP, gNB-CU-UP, eNB-CU, eNB-CU-CP, eNB-CU-UP, IAB node, IAB donor DU, IAB donor CU, IAB-DU, IAB-MT, O-CU, O-CU-CP, O-CU-UP, O-DU, O-RU, O-eNB, cloud based network function, cloud based centralized training node, or any other network unit or node capable of communicating with wireless devices in the area served by the radio network node, e.g., depending on the first radio access technology and terminology used. The second radio network node 13 may be referred to as a radio network node of the second RAT, the service area may be referred to as a serving cell, and the second radio network node communicates with the UE 10 in the form of DL transmissions to the UE 10 and UL transmissions from the UE 10. It should be noted that the service area may be denoted as a cell, beam, beam group, or the like to define an area of ​​radio coverage. The first RAT is different from the second RAT.

[0047] The communication network may comprise one or more network nodes, such as a first network node 15 and a second network node 16 of the same or different networks. The first and / or second network node may be a core network node, such as an MME or an Access and Mobility Management Function (AMF). The second radio network node 13, the first network node 15 and the second network node 16 are examples of network nodes 150 according to embodiments herein.

[0048] The network node 150 may be a RAN node, an Operations, Administration, and Maintenance (OAM), a core network node, a Service Management and Orchestration (SMO), a Network Management System (NMS), a non-real-time RAN intelligent controller (non-RT RIC), a real-time RAN intelligent controller (RT-RIC), a gNB, an eNB, an en-gNB, an ng-eNB, a gNB-CU, a gNB-CU-CP, a gNB-CU-UP, an eNB-CU, an eNB-CU-CP, an eNB-CU-UP, an IAB node, an IAB donor DU, an IAB donor CU, an IAB-DU, an IAB-MT, an O-CU, an O-CU-CP, an O-CU-UP, an O-DU, an O-RU, an O-eNB, a cloud-based network function, or a cloud-based centralized training node.

[0049] The first radio network node 12 may be a first RAT node in an EN-DC scenario, for example NR, where the third radio network node 17 may be a second RAT node, for example LTE.

[0050] The UE 10 may collect RA parameters during an RA procedure with the first radio network node 12. The UE 10 may then send an RA report to the second radio network node 13 and may send assistance information instructing how the RA report should be routed between the second radio network node 13 of the second RAT that collects the RA report and the first radio network node 12 of the first RAT that controls the cell for which the RA procedure logged in the RA report was performed, where forwarding of the RA report is based on the assistance information.

[0051] This allows the second RAT network node 150 fetching the first RAT RA report to correctly identify, for example, the network node that served as the UE's MN when the RA report was created, including information about a random access procedure performed in an NR cell controlled by an NR node serving as the UE's SN, e.g., a gNB or en-gNB. The second RAT network node 150 fetching the RA report can then forward the RA report to, for example, the identified second RAT network node that served as the UE's MN when the RA report was created, which can identify the NR node that served as the UE's SN and forward the report to that NR node for analysis. LTE and EUTRAN are used interchangeably. The second access network type refers to LTE. The first access network type refers to NR. The second network node and the third network node may be the same node. The term RA report is frequently used in the solution description. In this context, "RA report" refers to a report containing information about the random access procedure performed in an NR cell and adapted for transmission in an NR cell, i.e., to a gNB or en-gNB. In ASN.1, the RA report is the RA-Report-r16 IE. The corresponding report containing information about the random access procedure performed in an LTE cell, adapted for transmission in an LTE cell, is called a RACH report. In ASN.1, the RACH report is the RACH-Report-r16 IE.

[0052] FIG. 7 is a combined signaling scheme and flow chart illustrating an embodiment of the present disclosure.

[0053] Action 701. The UE 10 may perform an RA, thereby obtaining RA parameters during the RA procedure and including assistance information for the RA report. The UE 10 may store one or more RA reports with the RA parameters in a list of RA reports, along with their respective assistance information.

[0054] Action 702. The UE 10 sends an RA report and assistance information, for example, in an RA report container.

[0055] Action 703. A network node 150, such as the second radio network node 13, receives the RA report and the assistance information and may use the assistance information to determine how to process and forward the RA report to network nodes.

[0056] Action 704. The network node 150 forwards the RA report based on the assistance information. For example, the network node 150 may forward the RA report to the first radio network node 12 or a third network node associated with the first radio network node 12 based on the assistance information.

[0057] Action 705. The first radio network node 12 may use the RA report when handling the communication, for example to update or modify the RACH related settings.

[0058] In this disclosure, the term node is used, which may be a network node (radio network node) or a user equipment (UE).

[0059] Examples of network nodes or radio network nodes are Node B, base station (BS), MSR radio node such as Multi-Standard Radio (MSR) BS, eNodeB, gNodeB, Master eNodeB (MeNB), Secondary eNodeB (SeNB), Location Measurement Unit (LMU), Integrated Access Backhaul (IAB) node, network controller, Radio Network Controller (RNC), Base Station Controller (BSC), relay, donor node control relay, satellite node, Non-Terrestrial Network (NTN) node, High Altitude Platform (HAP) node. nodes, base transceiver station (BTS), central unit (e.g. in gNB), distributed unit (e.g. in gNB), baseband unit, centralized baseband, C-RAN, access point (AP), transmission point, transmitting node, transmit receiving point (TRP), RRU, RRH, node in distributed antenna system (DAS), core network node such as mobility management entity (MME), mobile switching center (MME), operation and maintenance (O&M), OSS, SON, positioning server (e.g. LMF, E-SMLC), etc.

[0060] The non-limiting term UE refers to any type of wireless device that communicates with network nodes and / or other UEs in a cellular or mobile communication system. Examples of UEs are target devices, device to device (D2D) UEs, vehicle to vehicle (V2V) UEs, machine-type UEs, MTC UEs or UEs capable of machine-to-machine (M2M) communications, Internet of Things (IoT) enabled devices, tablets, mobile terminals, smartphones, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, etc.

[0061] The term radio access technology or RAT may refer to any RAT, for example, UTRA, E-UTRA, Narrowband Internet of Things (NB-IoT), WiFi, Bluetooth, Next Generation RAT, New Radio (NR), 4G, 5G, etc. Any of the equipment denoted by the term node, network node, or radio network node may be capable of supporting a single RAT or multiple RATs.

[0062] The term signal or radio signal as used herein may refer to any physical signal or physical channel. Examples of DL physical signals are reference signals (RSs), such as primary synchronization signals (PSSs), secondary synchronization signals (SSSs), CSI-RSs, DMRS signals in SS / PBCH blocks (SSBs), discovery reference signals (DRSs), CRSs, and PRSs. RSs may be periodic; for example, an RS occasion carrying one or more RSs may occur with a certain periodicity, such as 20 ms, 40 ms, etc. RSs may also be aperiodic. Each SSB carries the NR-PSS, NR-SSS, and NR Physical Broadcast Channel (PBCH) in four consecutive symbols. One or more SSBs are transmitted in one SSB burst that repeats with a certain periodicity, such as 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, and 160 ms. A UE is configured with information about SSBs on a cell of a certain carrier frequency by one or more SS / PBCH block measurement timing configuration (SMTC) configurations. The SMTC configuration includes parameters such as SMTC periodicity, SMTC occasion length in time or duration, and reference time, e.g., SMTC time offset relative to the SFN of the serving cell. Thus, SMTC occasions can also occur with a certain periodicity, e.g., 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, and 160 ms. Examples of UL physical signals are reference signals, such as SRS and DMRS. The term physical channel refers to any channel that carries higher layer information, e.g., data, control, etc. Examples of physical channels are PBCH, NPBCH, PDCCH, PDSCH, sPUCCH, sPDSCH, sPUCCH, sPUSCH, MPDCCH, NPDCCH, NPDSCH, E-PDCCH, PUSCH, PUCCH, NPUSCH, etc.

[0063] Method actions performed by a UE 10 for handling communications in a communications network 1 according to an embodiment will now be described with reference to the flowchart shown in Figure 8. The actions do not have to be taken in the order set out below, but may be taken in any suitable order. Dashed boxes indicate optional features.

[0064] Action 801. The UE 10 may store one or more obtained RA reports associated with one or more pieces of assistance information. Thus, the UE 10 may obtain RA parameters of the RA procedure and store the RA reports associated with the assistance information. The UE 10 may obtain one or more RA reports in a list of RA reports. The assistance information may include a CGI of the SPCell-ID for each element of the list of RA reports, i.e., identification information of the first radio network node that is a PSCell network node. Thus, the assistance information may include identification information of the first radio network node 12 for (linked to) a received RA report.

[0065] Action 802. The UE 10 may indicate to the second radio network node 13 one or more capabilities including the capability to report an RA report and / or the capability to report assistance information.

[0066] Action 803. The UE 10 may receive a request to report one or more RA reports from a second radio network node 13. The UE 10 may receive a request to provide an RA report from a second radio network node 13, such as an LTE eNB, of a second RAT, such as LTE.

[0067] Action 804. The UE 10 provides to the network node an RA report of an RA procedure on the first RAT for the UE 10 and assistance information instructing how the RA report should be routed between the second radio network node 13 of the second RAT that collects the RA report and the first radio network node 12 of the first RAT that controls the cell in which the RA procedure logged in the RA report was performed. The assistance information instructing how the RA report should be routed may be specified by including a CGI and / or TAI of the SPCell identity for each element of the list of RA reports. Thus, the assistance information may include a CGI of the SPCell-ID for each element of the list of RA reports.

[0068] Thus, some embodiments may involve UE capability signaling and transmission of NR RA reports in LTE.

[0069] In one embodiment, the UE 10 may include a first indication to a network, such as the second network node 13, regarding the ability to include the list of first reports in the UEInformationResponse message.

[0070] In another embodiment, the UE 10 may include a second indication to the network, such as the second network node 13, regarding the ability to include additional information as items in the list in the UEInformationResponse message.

[0071] In another embodiment, the first instruction and the second instruction may be combined into a single instruction. These embodiments all relate to action 802 above.

[0072] Support information: In one embodiment, the UE 10 may include a list of primary reports (RA-ReportList) in the NR RA report container, and for each primary report (RA report) in the list, include in the UEInformationResponse message as an item in the list the assistance information required to route the RA report to the first network node 12 belonging to the first access network type. Thus, for each primary report (RA report) in the list of primary reports (RA-ReportList), the RA report container has an item with such assistance information in its list. The assistance information indicating how the RA report should be routed may be specified by including a CGI of the SPCell identity for each element of the list of RA reports. The assistance information may be exemplified in the following embodiments: o In one embodiment, the assistance information used to identify the MN may consist of the CGI of the PCell served by the MN. The PCell CGI includes the MN's global node ID, which may be used to identify the MN. Using this assistance information, a RAN node, such as the second radio network node 13, receiving the RA report (from the UE) may be able to forward the RA report to the CN. The CN may be able to forward the RA report to the MN connected to the SN where the report or reports were generated. The MN may then forward such report to one or more SN nodes connected to the MN where the report or reports were generated. o In another embodiment, the assistance information used to identify the MN may consist of the CGI and TAI of the PCell served by the MN and serving the UE when one or more RA reports are logged. The PCell CGI includes the MN's global node ID, which may be used to identify the MN, and the PCell's TAI may be used to route the message containing the RA report to the MN via one or more nodes in the core network. Using this assistance information, the RAN node receiving the RA report may be able to forward the RA report to the CN. The CN may be able to forward the RA report to the MN connected to the SN where the one or more reports were generated. Such forwarding may potentially occur via other CN nodes connected to the MN. The MN may then forward such reports to one or more SN nodes connected to the MN where the reports were generated. In another embodiment, the assistance information used to identify the MN may consist of a CGI of the PSCell served by the SN where the RACH access occurred generating one or more RA reports logged by the UE. The PSCell CGI includes the global node ID of the SN. This assistance information may be signaled to the CN together with the RA report. The CN may identify the MN to which the RA report needs to be forwarded since the CN is aware that the SN identified by the global node ID in the PSCell CGI is connected to the target MN. Using this assistance information, the RAN node receiving the RA report, such as the second network node 13, may be able to forward the RA report to the CN. The CN may be able to forward the RA report to the MN connected to the SN where the one or more reports were generated since the CN can derive the SN global node ID from the PSCell CGI and the CN knows that the SN to which the RA report needs to be forwarded is connected to a specific node, i.e., the MN, and therefore the CN can derive the identity of the MN to which the RA report needs to be forwarded. Thus, the CN may forward RA reports to the MN, which may then forward such reports to one or more SN nodes connected to the MN where the reports were generated. o In another embodiment, the assistance information used to identify the MN may consist of the CGI and TAI of the PCell served by the MN. Furthermore, the assistance information includes the PCI and / or CGI of the PSCell served by the SN where the RACH access occurred generating one or more RA reports logged by the UE. Using this assistance information, a RAN node, such as the second network node 13, receiving the RA reports may be able to forward the RA reports to the CN. The CN may be able to forward the RA reports to the MN connected to the SN where the one or more reports were generated. Such forwarding may potentially occur via other CN nodes connected to the MN. The MN may then forward such reports to one or more SN nodes connected to the MN where the reports were generated.

[0073] The above-mentioned assistance information may indicate how to route the RA report, since the TAI of the PCell may be used by the CN to route a message containing the RA report to a CN node connected to the MN. The PCell CGI contains the MN's global node ID, which may be used by a CN node receiving the information to identify the MN. Meanwhile, the PSCell PCI and / or CGI may be used by the MN to forward the received RA report to the appropriate SN. Using this information, the MN can identify the cells served by the SN to which the corresponding RA report needs to be forwarded, as the MN knows the PCI / CGI of those cells. Assuming that the PCI of the PSCell is not reused in the vicinity of the PCell, the MN can identify the SN serving the cell identified by the PSCell PCI and forward the RA report to that SN. Alternatively or additionally, the PSCell CGI may be used for such purpose.

[0074] In one embodiment, the UE 10 may send the NR RA report container upon receiving an explicit instruction from the network.

[0075] In a separate embodiment, the UE 10 may transmit an NR RA report container upon receiving a request to transmit an RA report related to a second access network type (LTE). In such a scenario, the UE transmits both the LTE RACH information and an NR RA report container that includes the NR RA report and assistance information described herein.

[0076] Method actions performed by a network node 150, such as a second radio network node 13 or a second network node 16 associated with a second RAT, for handling communications in the communications network 1 according to an embodiment will now be described with reference to the flowchart shown in Figure 9. The actions do not have to be taken in the order set out below, but may be taken in any suitable order. Dashed boxes indicate optional features.

[0077] Action 901. The network node 150 may receive one or more indications from the UE 10 indicating one or more capabilities including the ability to report an RA report and / or the ability to report assistance information.

[0078] Action 902. The network node 150 may send a request to report one or more RA reports to the UE 10. For example, a second radio network node 13 of a second RAT may request the UE 10 to provide RA reports of one or more RATs.

[0079] Action 903. The network node 150 obtains, for the UE, an RA report of an RA procedure of the first RAT and assistance information instructing how the RA report should be routed between the second radio network node 13 of the second RAT that collects the RA report and the first radio network node 12 of the first RAT that controls the cell in which the RA procedure logged in the RA report was performed. The network node 150 may receive the assistance information from the UE 10 or another network node.

[0080] Action 904. The network node 150 may identify one or more network nodes based on the aiding information, such as the CGI and / or the TAI.

[0081] Action 905. The network node 150 forwards the RA report based on the assistance information. The assistance information, which indicates how the RA report should be routed, may be defined by including the CGI and / or TAI of the SPCell-ID for each element of the list of RA reports, i.e., the identification information of the first radio network node. Thus, the assistance information may include, or at least indicate, the identification information of the first radio network node 12 for the received RA report.

[0082] Network implementation. In one embodiment, a network node 150, such as an eNB, may receive a first indication from the UE 10 regarding the capability to include a list of first reports (RA reports) in a UEInformationResponse message.

[0083] In another embodiment, the network node 150 may receive a second indication from the UE 10 regarding the capability to include, as an item in a list in the NR RA report container, assistance information used to forward the RA report to the SN where the RACH access occurred.

[0084] In another embodiment, the received first and second instructions may be combined into a single instruction.

[0085] In another embodiment, a third network node, e.g., an example of a network node 150, e.g., an eNB, that fetches or considers fetching a list of first reports (RA reports) from the UE 10 may provide an explicit indication requesting the UE 10 to transmit the list of first reports, which may optionally be an implicit request. Optionally, when determining whether to send such an explicit, and optionally implicit, request, the third network node takes into account one or more previously received capability indications received from the UE regarding the UE's ability to include the list of first reports in an NR RA report container and / or the UE's ability to include assistance information. To this end, if the third network node does not receive such a capability indication, the third network node may decide not to send an explicit request requesting the UE to transmit the list of first reports.

[0086] In one embodiment, upon receiving the second report from the UE 10, the network identifies nodes belonging to the second access network type from the included assistance information and forwards the first report to the respective nodes. The receiving node forwards the list of first reports to network nodes belonging to the first access network type, as detailed in the next section. The receiving node may send the report to all nodes of the first access network type with which the receiving node has an available communication link. A node belonging to the first access network type may need to forward the first report to the correct node of the first access network type. Alternatively, a node may drop the first report if it is not relevant to itself.

[0087] Embodiments Involving Routing RA Reports in a Network The proposed solution involves the routing of RA reports through the network as well as capability signaling aspects related to mechanisms for sending RA reports from the UE. The routing aspect relates to the routing of the RA report from another node, eNB in ​​the primary target scenario, that receives the RA report from the UE 10 that previously logged the RA information in the RA report to the intended node, en-gNB in ​​the primary target scenario. The capability signaling aspect relates to signaling an indication from the UE 10 to the eNB, i.e., a radio base station using LTE radio access technology, indicating its capability to deliver an RA report containing information collected at a radio base station using NR radio access technology, en-gNB in ​​the primary target scenario, in a manner that can be appropriately handled by the receiving eNB despite differences in radio access technology.

[0088] The main target scenarios are shown in Figure 10.

[0089] As shown in Figure 10, the scenario is that a UE configured in EN-DC mode performs a random access procedure toward an en-gNB, i.e., an SN, logs information related to the RA procedure in an RA report, and then moves and connects to another eNB in ​​the same EPC, i.e., an eNB other than the eNB that served as the UE's MN when the RA report was logged, and sends the RA report to this eNB upon request from the eNB. The eNB that requests and receives the RA report does not have an X2 connection toward the en-gNB and the eNB that served as the UE's SN and MN, respectively, when the RA report was logged. Note that the EN-DC mode refers to a mode in which the UE 10 is configured with dual connectivity toward an eNB serving as an MN and an en-gNB serving as an SN, and the en-gNB is operating in a non-standalone mode. In this scenario, UE10 must send the RA report in a manner that enables the network to route the RA report through the network to the en-gNB where UE10 performed the RA procedure when the RA information in the RA report was collected and logged, and provide assistance information to enable it to do so.

[0090] Routing of RA reports. In this section, the routing of RA reports is described with respect to a single RA report. However, this does not preclude the UE 10 from sending multiple RA reports, for example, a list of RA reports, such as in the RA-ReportList-r16 IE in 3GPP TS38.331 version 17.3.0. In such cases, RA reports with different destination nodes may be handled separately by the eNB receiving the RA report.

[0091] The assistance information that allows for the routing of RA reports is also referred to herein as routing-enabling information.

[0092] Figures 10 and 11 may be used as reference in the following description of the support information that enables routing of RA reports ("routing enabling information") if it is unclear or confusing which nodes are being referred to.

[0093] To enable routing of the RA report through the network, the UE 10 provides assistance information that enables each network node in the path to identify the next network node to which the RA report should be forwarded. Furthermore, since the RA report contains information that conforms to the standard for the NR radio access technology, it must also be taken into account that the eNB receiving the RA report may not be able to interpret the content of the RA report. This also applies not only to the eNB receiving the RA report, but also to all intermediate nodes in the RA report routing, i.e., all involved nodes, except the en-gNB, which is the final receiver of the RA report. Therefore, all routable information must be sent from the UE in a separate, but the same, UEInformationResponse RRC message as the RA report.

[0094] There is no single set of information items that can enable RA report routing, and therefore the proposed solutions include different variants of assistance information.

[0095] In further describing the assistance information, it should be noted that the information always relates to the network node involved when the UE performed the RA procedure and logged the relevant information, rather than the network node involved when the UE sent the RA report to the network.

[0096] The PSCell NR Cell Global Identifier (NCGI) or en-gNB ID may be used to allow the eNB receiving the report, referred to herein as the "receiving eNB," to know that it is not itself the intended final receiver of the RA report and that it does not have an X2 connection towards the final receiver of the RA report. If the neighboring eNBs of the receiving eNB provided information about the NR neighbor cells of the receiving eNB, for example, using the "NR Neighbor Info" IE in the X2 Setup Request message or the ENB Configuration Update message in the X2AP protocol, the PSCell NCGI also allows the receiving eNB to determine that it does not have an X2 connection towards the eNB that served as the MN for the UE when the RA report was logged. In some cases, additional information is required, or the receiving eNB simply assumes that it must send the received RA report to the MME to which it is connected. Thus, the PSCell will enable the receiving eNB to send the received RA report to the MME to which the receiving eNB is connected, referred to herein as the "receiving MME", because only via CN-based forwarding can the RA report retrieved by that eNB be forwarded to the en-gNB from which the RA report originated.

[0097] An alternative to the PSCell NCGI or en-gNB ID may be the PCell NCGI or eNB ID of the eNB that served as the MN for the UE when the RA report was logged, referred to herein as the "MN eNB," with respect to allowing the receiving eNB to know that it should forward the RA report to the receiving MME. The MN eNB ID will be useful in later routing steps, and it may be derived from the Evolved Cell Global Identifier (ECGI) of any of the cells served by the MN eNB, including the cell that was the PCell for the UE when the RA report was logged. As will be explained later, neither the UE 10 nor a core network node such as an MME is expected to be able to derive the eNB ID from the ECGI, although a RAN node such as an eNB is expected to be able to do so. Therefore, it is more reasonable for the UE to report the PCell NCGI rather than the MN eNB ID, and for the receiving eNB to then derive the MN eNB ID from the PCell NCGI and then forward the RA report together with the MN eNB ID and other routing enabling information to the receiving MME.

[0098] The next step in routing is enabled by the Tracking Area Code (TAC) or TAI associated with the Secondary Cell Group (SCG) cell for which the RA information was logged. This allows the MME of the receiving eNB to determine the correct MME to send the RA report to, referred to herein as the "destination MME", which in a simpler scenario may be the same MME. Note that the network can change the TAC to a TAI by prepending a Public Land Mobile Network (PLMN) ID, which is inherently known in the network, and the TAI is what is typically used for inter-MME routing in the EPC. Optionally, the TAC (or TAI) associated with the PSCell or the TAC (or TAI) associated with the PCell can be used instead of the TAC (or TAI) associated with the SCG cell for which the RA information was logged. In general, the TAC / TAI should be the same for all these cases, and in both cases, when used for inter-MME routing, the TAC / TAI will result in the same MME (or MME pool).

[0099] In the next step in the routing of the RA report, ie from the destination MME to the MN eNB, there are several options for the RA report routing enabling information, also indicated above as assistance information. - eNB ID of the MN eNB. Note that the eNB ID of an eNB can be derived from the ECGI of any cell controlled by the eNB, e.g., the PCell of a UE controlled by the MN eNB, but it is not expected that the UE will be able to do so. Furthermore, this may be similar for the MME, since the MME is a core network node that is not typically involved in cell IDs, i.e., it is not necessarily expected that the MME will be able to derive the eNB ID from the ECGI. However, it is expected that the RAN node will know how to derive the eNB ID from the ECGI. Therefore, to handle this situation, the UE 10 can log and report the PCell ECGI, and the receiving eNB can derive the MN eNB ID from the PCell ECGI and then send the MN eNB ID along with the RA report and other routing enablement information to the receiving MME. The receiving MME can then forward the MN eNB ID and RA report to the destination MME. o There may still be an option for the UE 10 to log and report the MN eNB ID, either as a UE implementation option or as a result of a newly specified requirement for the UE. o If the destination MME can be expected to actually derive the MN eNB ID from the PCell ECGI, sending the PCell ECGI to that MME as routing enabling information may also be an option. - en-gNB ID, which is a gNB ID. The rationale for this is that the MME is informed of the en-gNB ID of the eNB's (potential) connected en-gNB in ​​the S1 SETUP REQUEST (S1AP) message when the S1 interface is established, and therefore the MME can determine the eNB to which to route the RA report based on the en-gNB ID. As with the eNB ID, the gNB ID, which is similar to the en-gNB ID, can be derived from the cell ID of any of the cells belonging to the gNB / en-gNB, i.e., from the NCGI, but neither the UE nor the MME is expected to be able to do so. Thus, the UE 10 can report the PSCell NCGI if the PSCell is a cell controlled by the en-gNB, and the receiving eNB can derive the en-gNB ID from the reported PSCell NCGI and then send the en-gNB ID together with the RA report and other routing enablement information to the receiving MME. The receiving MME will then forward the en-gNB ID and RA report to the destination MME.

[0100] In the last step of RA report routing, ie from MN eNB to en-gNB, there are also several alternatives. - The NCGI of one of the SCG (PSCell) cells, i.e., the SCG cell NCGI. The MN eNB knows the NCGI of all cells of its connected en-gNB(s), thus enabling the routing of the RA report, the last step, to the en-gNB. The same is achieved if the MN eNB derives the en-gNB ID from the SCG cell NCGI. - The PCI of one of the SCG cells (i.e., the SCG cell PCI). There are 1008 available PCIs in the NR, and therefore, with proper PCI planning, the same PCI should appear only once in all cells of all en-gNB(s) that may be connected to the MN eNB. Therefore, the SCG cell PCI should unambiguously identify the correct SCG cell, which allows the MN eNB to forward the RA report to the correct en-gNB, since the MN eNB knows the PCIs of all cells of its connected en-gNB(s). - The PCI and Absolute Radio Frequency Channel Number (ARFCN) of one of the SCG cells. The PCI is locally unique per carrier frequency (and a carrier frequency is identified by its ARFCN), therefore combining the ARFCN of a Closed Subscriber Group (CSG) cell with the PCI of the CSG cell further reduces the risk of PCI collisions between the MN eNB and cells belonging to its connected en-gNB(s). - en-gNB ID. As explained before, the UE 10 cannot be expected to be able to derive this from the NCGI. Therefore, a more realistic alternative would be for the UE to report the SCG cell NCGI, and for the receiving eNB to derive the en-gNB ID from the SCG cell NCGI and then forward the en-gNB ID to the receiving MME as part of the assistance information together with the RA report. Another alternative is to provide no assistance information for the last routing step at all. In that case, the MN eNB would just know that it received an RA report intended for a node that uses, for example, the NR radio access technology in its cell, rather than a node that is the intended receiver of the RA report. Based on this incomplete information, the MN eNB could send the RA report to all its connected en-gNB(s), and each en-gNB would then check the cellId-r16 field in the RA report to find out if it is the intended receiver of the RA report.

[0101] All of the above shows how the RA report can be routed all the way to the en-gNB, thanks to the assistance information provided by the UE 10 along with the RA report. There is then one more step, which is not part of the actual RA report routing, but can be added to provide the en-gNB to take full advantage of the RA report. When the en-gNB receives the RA report, it should be able to identify the cell for which the RA procedure to which the RA report relates was performed. This information is easily included in the RA report itself in the form of the cellId-r16 field.

[0102] Both ECGI and NCGI have the PLMN ID, i.e., Mobile Country Code (MCC) + Mobile Network Code (MNC), in their most significant bits. This information is redundant when the procedure is restricted to a single PLMN. Therefore, in all the above options where ECGI or NCGI is used, the PLMN ID part can be pruned from the ECGI or NCGI. This makes the information slightly more compact while retaining functionality.

[0103] After each (non-final) step in the RA report routing, the network node 150 receiving the RA report and assistance information may prune portions of the assistance information that are not required for the subsequent routing step(s) before forwarding the remaining routing information along with the RA report to the next node in the routing chain.

[0104] Complete routing procedure. The above description of the assistance information explains how information can be provided (originating from the UE 10) to enable the network to route the RA report all the way to the en-gNB that is the intended receiver of the RA report (and to enable the en-gNB to identify the relevant cell). A complete step-by-step procedure is disclosed herein, in which various messages that can be utilized to forward the RA report and the assistance information are described. As explained above, there are several different options for how to assemble the complete assistance information, i.e., the complete assistance information that enables the RA report to be routed all the way to the en-gNB and that enables the en-gNB to identify the SCG cell for which the RA procedure was performed. In this example step-by-step procedure, it is assumed that the UE 10 provides the following assistance information to the receiving eNB, which is an example of a network node 150: - TAC of PCell - Pcell ECGI - PCI of the SCG cell where the RA report was logged - ARFCN of the SCG cell where the RA report was logged

[0105] Figure 11 can be used as a reference for the step-by-step example below.

[0106] FIG. 11 is a reference diagram for an exemplary step-by-step procedure, according to one example.

[0107] An exemplary step-by-step complete RA report routing procedure: Step 1 The UE 10 sends the RA report and assistance information to the receiving eNB in ​​a UEInformationResponse RRC message. The routing enablement information is included separately from the RA report, and the RA report, which is NR-specific (i.e., non-LTE information), should preferably be sent as a "transparent container," i.e., a chunk of data (e.g., an octet string or bit string) that the receiving eNB does not attempt to interpret. In the ASN.1 specification for the LTE RRC UEInformationResponse message (using 3GPP TS38.17.3.0 as a baseline), the nonCriticalExtension option can be used to extend the message with the UEInformationResponse-v1800-IEs IE, which contains, for example, the following ASN.1 code (the contents of the RoutingInformation IE containing the routing enablement information should be considered as an example): (Formula 2)

[0108] Step 2 The eNB that receives the UEInformationResponse RRC message from the UE 10, i.e., the "receiving eNB," extracts, but does not interpret, the en-gNB-SON-InfoContainer field containing the RA report from the UEInformationResponse RRC message, and extracts and interprets the parameters in the routingInformation field. The receiving eNB then derives the MN eNB ID from the PCell ECGI in the routing enablement information. Together, the PCell ECGI and the MN eNB ID tell the receiving eNB that the RA report must be routed through the core network to reach the intended receiver of the RA report.

[0109] The receiving eNB then prepares an S1AP message to send the RA report and the RA report's associated routing enablement information to the receiving MME.

[0110] A preferred choice of S1AP message is an eNB Configuration Transfer message, in which, as one possible embodiment, the receiving eNB can utilize the SON Configuration Transfer IE. In the SON Configuration Transfer IE, the receiving eNB populates the Target eNB-ID IE with the MN eNB ID (in the Global eNB ID field) and with the PCell TAC prepended with the PLMN ID (in the Selected TAI field). Similarly, the receiving eNB populates the Source eNB-ID IE with its own eNB ID (in the Global eNB ID field) and with the preferred TAI, e.g., the TAI of the cell from which the UEInformationResponse RRC message was received (in the Selected TAI field).

[0111] To include the RA report in the eNB Configuration Forward message, the receiving eNB uses the SON Information Report IE in the SON Information IE in the SON Configuration Forward IE. To enable this, the SON Information Report IE should be extended with another selection alternative in the CHOICE structure. The new selection alternative can be a new IE, for example, indicated as "En-gNB SON Info". The "En-gNB SON Info" IE may contain the IEs "En-gNB SON Information Container" (which will be a bit string), "Target PCI", and "Target ARFCN". The receiving eNB includes the RA report in the En-gNB SON Information Container IE and includes the PCI and ARFCN of the SCG cell where the RA report was logged in the Target PCI and ARFCN IEs.

[0112] Finally, the receiving eNB sends an eNB Configuration Transfer S1AP message to the receiving MME.

[0113] Step 3 The receiving MME uses the TAI in the Selected TAI IE in the Target eNB-ID IE in the received eNB Configuration Forward S1AP message to identify the MME to which the selected information should be forwarded, i.e., the destination MME, and transparently forwards the SON Configuration Forward IE using legacy mechanisms.

[0114] Step 4 The destination MME uses the MN eNB ID (contained in the Global eNB ID IE in the Target eNB-ID IE in the SON Configuration Forwarding IE, and possibly also included otherwise in the MME-to-MME message) to identify the eNB to which the information should be forwarded, and forwards the SON Configuration Forwarding IE in an MME Configuration Forwarding S1AP message to the MN eNB.

[0115] Step 5 The MN eNB extracts the RA report and the PCI and ARFCN of the SCG cell in which the RA report is logged from the En-gNB SON Information IE (contained in a SON Information Report IE contained in a SON Configuration Transfer IE).

[0116] The MN eNB uses the PCI and (if necessary) ARFCN of the SCG cell where the RA report was logged to identify the en-gNB that is the intended receiver of the RA report. The MN eNB then forwards the RA report to the identified en-gNB. To do this, the MN eNB may, as one alternative, use an EN-DC Configuration Transfer X2AP message. In this X2AP message, the RA report may, as one alternative, be included in a new IE, or, as another alternative, in the EN-DC SON Configuration Transfer IE. As another alternative, the MN eNB may send the RA report to the en-gNB using a newly designated X2AP message, for example, indicated as "SON Information Transfer". As a further option, the MN eNB may forward the entire received SON Configuration Transfer IE (or at least its contents) to the en-gNB, either in a new IE in the EN-DC Configuration Transfer X2AP message or in a new IE in a new X2AP message (e.g., shown above, i.e., as "SON Information Transfer").

[0117] Step 6 This step is not part of the actual routing of the RA report. In this step, the en-gNB reads the information in the received RA report, identifies the cell for which the RA report was logged based on the cellId-r16 field in the RA report (i.e. in the RA report-r16 IE), and optionally adds the RA report information to information forming the basis for a potential optimization of the settings in the concerned cell, e.g., a change of the RACH-related settings.

[0118] A brief alternative RA reporting routing example: In another routing example, if the UE includes in its routing enablement information (e.g., in the routingInformation IE) the NCGI (rather than the PCI and ARFCN) of the SCG cell where the RA report was logged, the receiving eNB uses this NCGI to derive the en-gNB ID. Together with other received routing enablement information and information the receiving eNB inherently knows (e.g., from its own configuration parameters), this allows the receiving eNB to use the EN-DC SON Configuration Forwarding IE (which also includes the SON Information IE) to convey the RA report to the receiving MME. The EN-DC SON Configuration Forwarding IE can then be forwarded all the way to the en-gNB. To enable this, the EN-DC SON Configuration Forwarding IE may possibly have to be extended with an additional forwarding type selection alternative (in addition to its selection alternatives, request and reply), which is neither a request nor a reply, but an unsolicited report, e.g., indicated as a report.

[0119] Other RA Reporting Routing Scenarios The main target scenario for which the solution has been described above is the most extensive. This is valid for the purpose of describing the solution because it allows for comprehensive coverage of the various aspects and steps of the solution. However, simpler scenarios for RA report routing may occur more frequently and are therefore equally important. Figures 12, 13, and 14 show several such RA report routing scenarios.

[0120] Figure 12 shows an RA reporting routing scenario involving a single MME, i.e., non-MME-to-MME routing.

[0121] FIG. 13 illustrates an RA report routing scenario involving an X2 connection between the receiving eNB and the MN eNB.

[0122] FIG. 14 illustrates an RA report routing scenario involving an X2 connection between the receiving eNB and the SN eNB.

[0123] The above simpler RA report routing scenarios involve fewer routing hops than the more comprehensive primary target scenario. Therefore, not all of the assistance information described for the primary target scenario is required in these scenarios. In each of these simpler RA report routing scenarios, only a subset of the assistance information parameters is required. Optionally, the UE 10 may omit unnecessary parameters in the routing enablement information (e.g., in the RoutingInformation IE), provided that the UE 10 can infer the structure / topology of the RA report routing path, e.g., the number of routing hops and the types of nodes involved. As another option, the receiving eNB may discard the assistance information received from the UE 10, i.e., unnecessary parameters in the routing enablement information, and omit the corresponding parameters in the assistance information sent to the next-hop node.

[0124] Impact on TS36.331 An example implementation in TS36.331 is provided in which the UE receives an explicit instruction from the network to send a list of first reports.

[0125] 5.6.5.3 Receiving a UEInformationRequest message Upon receiving the UEInformationRequest message, the UE shall do the following only after successful security activation: 1> If rach-ReportReq is set to true, set the content of rach-Report in the UEInformationResponse message as follows: 2> Set numberOfPreamblesSent to indicate the number of preambles sent by the MAC for the last successfully completed random access procedure, 2> If contention resolution was not successful as specified in TS 36.321 [6] for at least one of the transmitted preambles for the last successfully completed random access procedure, 3> set contentionDetected to true, 2> In other cases, 3> set contentionDetected to false, 2> If the UE is a BL UE or a UE in CE, 3> set initialCEL to indicate the initial CE level used for the last successfully completed random access procedure, 2> If the UE is an NB-IoT UE, 3> setting initialNRSRP-Level to indicate the NRSRP level of the NPRACH resource selected for the first preamble transmission for the last successfully completed random access procedure; 2> If the UE is a BL UE, a UE in CE, or an NB-IoT UE, 3> If the last successfully completed random access procedure was initiated on an EDT PRACH resource and was successful after receiving an EDT fallback indication from lower layers, 4> set edt-Fallback to true, 3> In other cases, 4> set edt-Fallback to false, 1> nr-rach-ReportReq is set to true and the UE has random access related information in the VarRA-Report specified in TS38.331 3> Set the value of ra-ReportList in VarRA-Report to RA-ReportList in the UEInformationResponse message. 3> Set the CGI of spCellID from each element of ra-ReportList to each element of CellIdList. 3> If the delivery of the UEInformationResponse message is successful and confirmed by the lower layer, discard the ra-ReportList from VarRA-Report; 1> if rlf-ReportReq is set to true and the UE has radio link failure information or handover failure information available in VarRLF-Report (VarRLF-Report-NB for NB-IoT) and the RPLMN is included in the plmn-IdentityList stored in VarRLF-Report; 2> For NB-IoT, if the global cell identity of the selected cell is the same as the reestablishmentCellId in VarRLF-Report-NB, 3> Remove reestablishmentCellId from VarRLF-Report-NB, 2> Set timeSinceFailure in VarRLF-Report (VarRLF-Report-NB in ​​case of NB-IoT) to the time elapsed since the last radio link or handover failure in E-UTRA; 2> Set rlf-Report in the UEInformationResponse message to the value of rlf-Report in VarRLF-Report (VarRLF-Report-NB in ​​the case of NB-IoT), 2> If the delivery of the UEInformationResponse message is successful, as confirmed by the lower layers, discard the rlf-Report from VarRLF-Report (VarRLF-Report-NB in ​​the case of NB-IoT), 1> Except for NB-IoT, if connEstFailReportReq is set to true and the UE has connection establishment failure information in VarConnEstFailReport, and if RPLMN is equal to the plmn-Identity stored in VarConnEstFailReport; 2> Set timeSinceFailure in VarConnEstFailReport to the time elapsed since the last connection establishment failure in E-UTRA; 2> Set connEstFailReport in the UEInformationResponse message to the value of connEstFailReport in VarConnEstFailReport; 2> If the delivery of the UEInformationResponse message is successful as confirmed by the lower layer, discard the connEstFailReport from VarConnEstFailReport; 1> Except for NB-IoT, if logMeasReportReq is present and if the RPLMN is included in the plmn-IdentityList stored in VarLogMeasReport, 2> If VarLogMeasReport contains one or more logged measurement entries, set the content of logMeasReport in the UEInformationResponse message as follows: 3> Include absoluteTimeStamp and set absoluteTimeStamp to the value of absoluteTimeInfo in VarLogMeasReport, 3> Include traceReference and set traceReference to the value of traceReference in VarLogMeasReport, 3> Include traceRecordingSessionRef and set traceRecordingSessionRef to the value of traceRecordingSessionRef in VarLogMeasReport, 3> Include tce-Id and set tce-Id to the value of tce-Id in VarLogMeasReport, 3> Include logMeasInfoList and set logMeasInfoList to include one or more entries from VarLogMeasReport starting from the first logged entry and, for each entry in the included logMeasInfoList, to include all the information stored in the corresponding logMeasInfoList entry in VarLogMeasReport, 3> If the VarLogMeasReport contains one or more additional logged measurement entries that are not included in the logMeasInfoList in the UEInformationResponse message, 4> Include logMeasAvailable, 4> If logMeasResultListBT is included in one or more of the additional logged measurement entries in VarLogMeasReport that are not included in the logMeasInfoList in the UEInformationResponse message, 5> include logMeasAvailableBT, 4> if logMeasResultListWLAN is included in one or more of the additional logged measurement entries in VarLogMeasReport that are not included in the logMeasInfoList in the UEInformationResponse message, 5> include logMeasAvailableWLAN, 1> Except for NB-IoT, if mobilityHistoryReportReq is set to true, 2> Include mobilityHistoryReport and set mobilityHistoryReport to include entries from VarMobilityHistoryReport, 2> Optionally, after removing the oldest entry if necessary, include an entry for the current cell in the mobilityHistoryReport and set its fields as follows: 3> Set visitedCellId to the global or physical cell identity and carrier frequency of the current cell; 3> Set the field timeSpent to the time spent in the current cell, 1> Except for NB-IoT, if idleModeMeasurementReq is included in UEInformationRequest and the UE stores VarMeasIdleReport containing measurement information related to a cell other than the PCell, 2> Set measResultListIdle-r15 in the UEInformationResponse message to the value of measReportIdle-r15 in VarMeasIdleReport; 2> Set measResultListExtIdle in the UEInformationResponse message to the value of measReportIdle-r16 in VarMeasIdleReport, if available; 2> Set measResultListIdleNR in the UEInformationResponse message to the value of measReportIdleNR in VarMeasIdleReport, if available; 2> If the delivery of the UEInformationResponse message is successful, as confirmed by the lower layer, discard the VarMeasIdleReport. 1> Except for NB-IoT, if the flightPathInfoReq field is present and the UE has flight path information available, 2> Include flightPathInfoReport and set flightPathInfoReport to include a list of waypoints along the flight path, 2> If includeTimeStamp is set to true, 3> Set the field timeStamp to the time the UE intends to reach each waypoint, if this information is available in the UE; 1> For NB-IoT, if anr-ReportReq is set to true and the UE has measResultList available in VarANR-MeasReport-NB, 2> Set anr-MeasReport in the UEInformationResponse message as follows: 3> If the global cell identity of the PCell is different from the servCellIdentity in VarANR-MeasReport-NB, 4> Include servCellIdentity and set servCellIdentity to the value of servCellIdentity in VarANR-MeasReport-NB, 3> Set measResultServCell to the value of measResultServCell in VarANR-MeasReport-NB, 3> Set relativeTimeStamp to the value of relativeTimeStamp in VarANR-MeasReport-NB, 3> Set measResultList to the value of measResultList in VarANR-MeasReport-NB, 2> If the delivery of the UEInformationResponse message is successful, as confirmed by the lower layers, discard the VarANR-MeasReport-NB; 1> Except for NB-IoT, if coarseLocationReq is set to true, 2> Include coarseLocationInfo if available, 1> If logMeasReport is included in UEInformationResponse, 2> Submit a UEInformationResponse message to lower layers for transmission via SRB2; 2> Upon successful delivery of the UEInformationResponse message confirmed by the lower layer, discard the logged measurement entries contained in the logMeasInfoList from VarLogMeasReport, 1> In other cases, 2> Submit a UEInformationResponse message to lower layers for transmission via SRB1;

[0126] An exemplary implementation in TS36.331 is provided in which the UE does not receive an explicit instruction from the network to send the first list of reports. 1 5.6.5.3 Receiving a UEInformationRequest message Upon receiving the UEInformationRequest message, the UE shall do the following only after successful security activation: 1> If rach-ReportReq is set to true, set the content of rach-Report in the UEInformationResponse message as follows: 2> Set numberOfPreamblesSent to indicate the number of preambles sent by the MAC for the last successfully completed random access procedure, 2> If contention resolution was not successful as specified in TS 36.321 [6] for at least one of the transmitted preambles for the last successfully completed random access procedure, 3> set contentionDetected to true, 2> In other cases, 3> set contentionDetected to false, 2> If the UE is a BL UE or a UE in CE, 3> set initialCEL to indicate the initial CE level used for the last successfully completed random access procedure, 2> If the UE is an NB-IoT UE, 3> setting initialNRSRP-Level to indicate the NRSRP level of the NPRACH resource selected for the first preamble transmission for the last successfully completed random access procedure; 2> If the UE is a BL UE, a UE in CE, or an NB-IoT UE, 3> If the last successfully completed random access procedure was initiated on an EDT PRACH resource and was successful after receiving an EDT fallback indication from lower layers, 4> set edt-Fallback to true, 3> In other cases, 4> set edt-Fallback to false, 2> If the UE supports NR RACH reporting and has random access related information in the VarRA-Report as specified in TS38.331, 3> Set the value of ra-ReportList in VarRA-Report to RA-ReportList in the UEInformationResponse message. 3> Set the CGI of spCellID from each element of ra-ReportList to each element of CellIdList. 3> If the delivery of the UEInformationResponse message is successful and confirmed by the lower layer, discard the ra-ReportList from VarRA-Report; 1> if rlf-ReportReq is set to true and the UE has radio link failure information or handover failure information available in VarRLF-Report (VarRLF-Report-NB for NB-IoT) and the RPLMN is included in the plmn-IdentityList stored in VarRLF-Report; 2> For NB-IoT, if the global cell identity of the selected cell is the same as the reestablishmentCellId in VarRLF-Report-NB, 3> Remove reestablishmentCellId from VarRLF-Report-NB, 2> Set timeSinceFailure in VarRLF-Report (VarRLF-Report-NB in ​​case of NB-IoT) to the time elapsed since the last radio link or handover failure in E-UTRA; 2> Set rlf-Report in the UEInformationResponse message to the value of rlf-Report in VarRLF-Report (VarRLF-Report-NB in ​​the case of NB-IoT), 2> If the delivery of the UEInformationResponse message is successful, as confirmed by the lower layers, discard the rlf-Report from VarRLF-Report (VarRLF-Report-NB in ​​the case of NB-IoT), 1> Except for NB-IoT, if connEstFailReportReq is set to true and the UE has connection establishment failure information in VarConnEstFailReport, and if RPLMN is equal to the plmn-Identity stored in VarConnEstFailReport; 2> Set timeSinceFailure in VarConnEstFailReport to the time elapsed since the last connection establishment failure in E-UTRA; 2> Set connEstFailReport in the UEInformationResponse message to the value of connEstFailReport in VarConnEstFailReport; 2> If the delivery of the UEInformationResponse message is successful as confirmed by the lower layer, discard the connEstFailReport from VarConnEstFailReport; 1> Except for NB-IoT, if logMeasReportReq is present and if the RPLMN is included in the plmn-IdentityList stored in VarLogMeasReport, 2> If VarLogMeasReport contains one or more logged measurement entries, set the content of logMeasReport in the UEInformationResponse message as follows: 3> Include absoluteTimeStamp and set absoluteTimeStamp to the value of absoluteTimeInfo in VarLogMeasReport, 3> Include traceReference and set traceReference to the value of traceReference in VarLogMeasReport, 3> Include traceRecordingSessionRef and set traceRecordingSessionRef to the value of traceRecordingSessionRef in VarLogMeasReport, 3> Include tce-Id and set tce-Id to the value of tce-Id in VarLogMeasReport, 3> Include logMeasInfoList and set logMeasInfoList to include one or more entries from VarLogMeasReport starting from the first logged entry and, for each entry in the included logMeasInfoList, to include all the information stored in the corresponding logMeasInfoList entry in VarLogMeasReport, 3> If the VarLogMeasReport contains one or more additional logged measurement entries that are not included in the logMeasInfoList in the UEInformationResponse message, 4> Include logMeasAvailable, 4> If logMeasResultListBT is included in one or more of the additional logged measurement entries in VarLogMeasReport that are not included in the logMeasInfoList in the UEInformationResponse message, 5> include logMeasAvailableBT, 4> if logMeasResultListWLAN is included in one or more of the additional logged measurement entries in VarLogMeasReport that are not included in the logMeasInfoList in the UEInformationResponse message, 5> include logMeasAvailableWLAN, 1> Except for NB-IoT, if mobilityHistoryReportReq is set to true, 2> Include mobilityHistoryReport and set mobilityHistoryReport to include entries from VarMobilityHistoryReport, 2> Optionally, after removing the oldest entry if necessary, include an entry for the current cell in the mobilityHistoryReport and set its fields as follows: 3> Set visitedCellId to the global or physical cell identity and carrier frequency of the current cell; 3> Set the field timeSpent to the time spent in the current cell, 1> Except for NB-IoT, if idleModeMeasurementReq is included in UEInformationRequest and the UE stores VarMeasIdleReport containing measurement information related to a cell other than the PCell, 2> Set measResultListIdle-r15 in the UEInformationResponse message to the value of measReportIdle-r15 in VarMeasIdleReport; 2> Set measResultListExtIdle in the UEInformationResponse message to the value of measReportIdle-r16 in VarMeasIdleReport, if available; 2> Set measResultListIdleNR in the UEInformationResponse message to the value of measReportIdleNR in VarMeasIdleReport, if available; 2> If the delivery of the UEInformationResponse message is successful, as confirmed by the lower layer, discard the VarMeasIdleReport. 1> Except for NB-IoT, if the flightPathInfoReq field is present and the UE has flight path information available, 2> Include flightPathInfoReport and set flightPathInfoReport to include a list of waypoints along the flight path, 2> If includeTimeStamp is set to true, 3> Set the field timeStamp to the time the UE intends to reach each waypoint, if this information is available in the UE; 1> For NB-IoT, if anr-ReportReq is set to true and the UE has measResultList available in VarANR-MeasReport-NB, 2> Set anr-MeasReport in the UEInformationResponse message as follows: 3> If the global cell identity of the PCell is different from the servCellIdentity in VarANR-MeasReport-NB, 4> Include servCellIdentity and set servCellIdentity to the value of servCellIdentity in VarANR-MeasReport-NB, 3> Set measResultServCell to the value of measResultServCell in VarANR-MeasReport-NB, 3> Set relativeTimeStamp to the value of relativeTimeStamp in VarANR-MeasReport-NB, 3> Set measResultList to the value of measResultList in VarANR-MeasReport-NB, 2> If the delivery of the UEInformationResponse message is successful, as confirmed by the lower layers, discard the VarANR-MeasReport-NB; 1> Except for NB-IoT, if coarseLocationReq is set to true, 2> Include coarseLocationInfo if available, 1> If logMeasReport is included in UEInformationResponse, 2> Submit a UEInformationResponse message to lower layers for transmission via SRB2; 2> Upon successful delivery of the UEInformationResponse message confirmed by the lower layer, discard the logged measurement entries contained in the logMeasInfoList from VarLogMeasReport, 1> In other cases, 2> Submit a UEInformationResponse message to lower layers for transmission via SRB1;

[0127] UEInformationResponse Message (Formula 3)

[0128] FIG. 15 shows a block diagram illustrating a UE 10 for handling communications in a communications network 1 according to an embodiment herein.

[0129] The UE 10 may comprise processing circuitry 1501, eg, one or more processors, configured to perform the methods herein.

[0130] The UE 10 and / or the processing circuit 1501 may be configured to obtain RA parameters of the RA procedure and may store an RA report associated with the assistance information.

[0131] The UE 10 and / or the processing circuitry 1501 may be configured to indicate to the second radio network node 13 one or more capabilities including the capability to report an RA report and / or the capability to report assistance information.

[0132] The UE 10 and / or the processing circuitry 1501 may be configured to receive a request to report one or more RA reports from the second radio network node 13. The UE 10 may receive a request to provide an RA report from a second radio network node (LTE eNB) of the second RAT (LTE).

[0133] The UE 10 and / or the processing circuitry 1501 are configured to provide to the network node 150 an RA report of an RA procedure on the first RAT for the UE 10 and assistance information instructing how the RA report should be routed between a second radio network node 13 of the second RAT that collects the RA report and a first radio network node 12 of the first RAT that controls a cell for which the RA procedure logged in the RA report was performed. The assistance information instructing how the RA report should be routed may be specified by including a CGI and / or TAI of the SPCell-ID for each element of the list of RA reports.

[0134] The UE 10 may comprise a memory 1505. The memory 1505 comprises one or more units to be used for storing data, such as data packets, RA reports, lists, assistance information, instructions, thresholds, signal strength / quality, measurements, RA procedures, events, and the like, and applications for performing the methods disclosed herein when executed. Additionally, the UE 10 may comprise a communication interface 1506, such as comprising a transmitter, a receiver, a transceiver, and / or one or more antennas.

[0135] Methods according to embodiments described herein for a UE 10 are implemented, for example, by a computer program product 1507 or computer program comprising instructions, i.e., software code portions, that, when executed on at least one processor, cause the at least one processor to perform actions described herein to be performed by the UE 10. The computer program product 1507 may be stored on a computer-readable storage medium 1508, such as a disk, a Universal Serial Bus (USB) stick, or the like. The computer-readable storage medium 1508 having the computer program product stored thereon may comprise instructions that, when executed on at least one processor, cause the at least one processor to perform actions described herein to be performed by the UE 10. In some embodiments, the computer-readable storage medium may be a transient or non-transitory computer-readable storage medium. Thus, embodiments herein may disclose a UE 10 for handling communications in a communications network, the UE 10 comprising a processing circuit and a memory, the memory comprising instructions executable by the processing circuit, such that the UE 10 is operable to perform any of the methods herein.

[0136] FIG. 16 shows a block diagram illustrating a network node 150, such as a second radio network node 13 or a second network node 16 associated with a second RAT, for handling communications in a communications network 1 according to an embodiment of the present specification.

[0137] The network node 150 may comprise processing circuitry 1601, eg, one or more processors, configured to perform the methods herein.

[0138] The network node 150 and / or the processing circuit 1601 are configured to obtain, i.e., receive, for the UE 10, an RA report of an RA procedure of a first RAT and assistance information instructing how the RA report should be routed between a second radio network node 13 of a second RAT that collects the RA report and a first radio network node 12 of the first RAT that controls a cell in which an RA procedure logged in the RA report was performed.

[0139] The network node 150 and / or the processing circuit 1601 are configured to forward the RA report based on the assistance information.

[0140] The network node 150 and / or the processing circuit 1601 may be configured to receive one or more indications from the UE 10 indicating one or more capabilities, such as the ability to report an RA report and / or the ability to report assistance information.

[0141] The network node 150 and / or processing circuitry may be configured to send a request to the UE 10 to report one or more RA reports.

[0142] The network node 150 and / or processing circuitry may be configured to identify one or more network nodes based on the assistance information.

[0143] The assistance information indicating how the RA report should be routed may be defined by including the CGI and / or TAI of the SPCell-ID, i.e., the identification of the first radio network node, for each element of the list of RA reports. Thus, the assistance information may include the identification of the first radio network node 12 for the received RA report.

[0144] The network node 150 may comprise a memory 1605. The memory 1605 comprises one or more units to be used for storing data, such as data packets, instructions, network node identities, route information, RA configurations, allocated resources, thresholds, events, and the like, and applications for performing the methods disclosed herein when executed. Additionally, the network node 150 may comprise a communication interface 1606, such as comprising a transmitter, a receiver, a transceiver, and / or one or more antennas.

[0145] Methods according to embodiments described herein for network node 150 are implemented by, for example, a computer program product 1607 or computer program comprising instructions, i.e., software code portions, that, when executed on at least one processor, cause the at least one processor to perform actions described herein to be performed by the network node. The computer program product 1607 may be stored on a computer-readable storage medium 1608, such as a disk, USB stick, or the like. The computer-readable storage medium 1608 having the computer program product stored thereon may comprise instructions that, when executed on at least one processor, cause the at least one processor to perform actions described herein to be performed by the network node. In some embodiments, the computer-readable storage medium may be a transient or non-transitory computer-readable storage medium. Thus, embodiments herein may disclose a network node for handling communications in a communications network, the network node comprising a processing circuit and a memory, the memory comprising instructions executable by the processing circuit, whereby the network node is operable to perform any of the methods herein.

[0146] In some embodiments, the more general term “network node” is used, and the term “network node” can correspond to any type of wireless network node or any network node that communicates with wireless devices and / or other network nodes. Examples of network nodes are Node Bs, MeNBs, SeNBs, network nodes belonging to a Master Cell Group (MCG) or a Secondary Cell Group (SCG), base stations (BSs), MSR radio nodes such as Multi-Standard Radio (MSR) BSs, eNodeBs, gNodeBs, network controllers, Radio Network Controllers (RNCs), Base Station Controllers (BSCs), relays, donor node controlled relays, base transceiver stations (BTSs), access points (APs), transmission points, transmitting nodes, remote radio units (RRUs), remote radio heads (RRHs), nodes in a distributed antenna system (DAS), etc.

[0147] In some embodiments, the non-limiting term wireless device or UE is used, which refers to any type of wireless device that communicates with network nodes and / or other wireless devices in a cellular or mobile communication system. Examples of UEs are target devices, device to device (D2D) UEs, proximity-enabled UEs (also known as ProSe UEs), machine-type UEs or UEs capable of machine-to-machine (M2M) communications, tablets, mobile terminals, IoT-enabled devices, smartphones, laptop embedded equipment (LEEs), laptop mounted equipment (LMEs), USB dongles, etc.

[0148] The embodiments are applicable to any RAT or multi-RAT system in which a UE receives and / or transmits signals (e.g., data), such as New Radio (NR), Wi-Fi, Long Term Evolution (LTE), LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications (GSM) / Enhanced Data Rates for GSM Evolution (GSM / EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), to name just a few possible implementations.

[0149] As will be readily understood by those familiar with communications design, the functional means or circuits may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, some or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces therebetween. Some of the functions may be implemented, for example, on a processor shared with other functional components of a wireless device or network node.

[0150] Alternatively, some of the functional elements of the described processing means may be provided by using dedicated hardware, while other functional elements are provided with hardware for executing software, in association with appropriate software or firmware. Thus, the terms "processor" or "controller" as used herein do not refer solely to hardware capable of executing software, but may implicitly include, without limitation, digital signal processor (DSP) hardware and / or program or application data. Other hardware, conventional and / or custom, may also be included. Designers of communications devices will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

[0151] Any suitable step, method, feature, function, or benefit disclosed herein may be implemented through one or more functional units or modules of one or more virtual devices. Each virtual device may comprise several 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), dedicated 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, and the like. The program code stored in memory includes program instructions for implementing one or more communication and / or data communication protocols, as well as instructions for performing one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause each functional unit to perform a corresponding function according to one or more embodiments of the present disclosure.

[0152] 17 , according to one embodiment, a communication system includes a communication network 3210, such as a 3GPP-type cellular network, comprising an access network 3211, such as a radio access network, and a core network 3214. The access network 3211 includes a plurality of base stations 3212 a, 3212 b, 3212 c, such as NBs, eNBs, gNBs, or other types of wireless access points, which are examples of radio network nodes 12 herein, each defining a corresponding coverage area 3213 a, 3213 b, 3213 c. Each base station 3212 a, 3212 b, 3212 c can be connected to the core network 3214 over a wired or wireless connection 3215. A first user equipment (UE) 3291, an example of a UE 10, located in the coverage area 3213 c is configured to wirelessly connect to or be paged by the corresponding base station 3212 c. A second UE 3292 in the coverage area 3213a can wirelessly connect to the corresponding base station 3212a. Although multiple UEs 3291, 3292 are shown in this example, the disclosed embodiments are equally applicable to situations where only one UE is in the coverage area or connects to the corresponding base station 3212.

[0153] The communications network 3210 is itself connected to a host computer 3230, which may be embodied in hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer 3230 may be owned or controlled by a service provider, or may be operated by or on behalf of the service provider. The connection 3221, 3222 between the communications network 3210 and the host computer 3230 may extend directly from the core network 3214 to the host computer 3230 or may proceed via an optional intermediate network 3220. The intermediate network 3220 may be one of a public network, a private network, or a hosted network, or a combination of two or more of them; the intermediate network 3220 may be a backbone network or the Internet, if any; in particular, the intermediate network 3220 may comprise two or more subnetworks (not shown).

[0154] The communication system of FIG. 17 as a whole enables connectivity between one of the connected UEs 3291, 3292 and a host computer 3230. The connectivity may be described as an over-the-top (OTT) connection 3250. The host computer 3230 and the connected UEs 3291, 3292 are configured to communicate data and / or signaling via the OTT connection 3250 using the access network 3211, the core network 3214, any intermediate networks 3220, and possible further infrastructure (not shown) as intermediaries. The OTT connection 3250 may be transparent in the sense that the participating communication devices through which the OTT connection 3250 passes are unaware of the routing of uplink and downlink communications. For example, the base station 3212 may not, or need not, be informed regarding the past routing of an incoming downlink communication involving data originating from the host computer 3230 that is to be forwarded (e.g., handed over) to the connected UE 3291. Similarly, base station 3212 does not need to be aware of the future routing of outgoing uplink communications originating from UE 3291 and destined for host computer 3230.

[0155] An exemplary implementation of the UE, base station, and host computer described in the previous paragraph, according to one embodiment, will now be described with reference to FIG. 18 . In the communication system 3300, the host computer 3310 comprises hardware 3315, including a communication interface 3316 configured to set up and maintain wired or wireless connections with interfaces of different communication devices of the communication system 3300. The host computer 3310 further comprises processing circuitry 3318, which may have storage and / or processing capabilities. In particular, the processing circuitry 3318 may comprise one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown), adapted to execute instructions. The host computer 3310 further comprises software 3311, which is stored on or accessible by the host computer 3310 and executable by the processing circuitry 3318. The software 3311 includes a host application 3312. The host application 3312 may be operable to provide services to a remote user, such as a UE 3330 connecting via an OTT connection 3350 that terminates at the UE 3330 and the host computer 3310. In providing services to the remote user, the host application 3312 may provide user data that is transmitted using the OTT connection 3350.

[0156] The communications system 3300 further includes a base station 3320 provided in the communications system, the base station 3320 comprising hardware 3325 that enables the base station 3320 to communicate with the host computer 3310 and the UE 3330. The hardware 3325 may include a communications interface 3326 for setting up and maintaining wired or wireless connections with interfaces of different communications devices of the communications system 3300, as well as a wireless interface 3327 for setting up and maintaining at least a wireless connection 3370 with a UE 3330 located in a coverage area (not shown in FIG. 18 ) served by the base station 3320. The communications interface 3326 may be configured to facilitate a connection 3360 to the host computer 3310. The connection 3360 may be direct, or alternatively, the connection 3360 may pass through a core network of the communications system (not shown in FIG. 18 ) and / or one or more intermediate networks external to the communications system. In the illustrated embodiment, the hardware 3325 of the base station 3320 further includes processing circuitry 3328, which may comprise one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The base station 3320 further has software 3321 that is stored internally or accessible via an external connection.

[0157] The communication system 3300 further includes the already-mentioned UE 3330. The hardware 3335 of the UE 3330 may include a wireless interface 3337 configured to set up and maintain a wireless connection 3370 with a base station serving a coverage area in which the UE 3330 is currently located. The hardware 3335 of the UE 3330 further includes a processing circuit 3338, which may comprise one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The UE 3330 further includes software 3331 stored on or accessible by the UE 3330 and executable by the processing circuit 3338. The software 3331 includes a client application 3332. The client application 3332, with the support of the host computer 3310, may be operable to provide services to a human or non-human user via the UE 3330. On the host computer 3310, a running host application 3312 may communicate with a running client application 3332 via an OTT connection 3350 that terminates at the UE 3330 and the host computer 3310. In providing a service to a user, the client application 3332 may receive request data from the host application 3312 and provide user data in response to the request data. The OTT connection 3350 may transfer both the request data and the user data. The client application 3332 may interact with the user to generate the user data that the client application 3332 provides.

[0158] It should be noted that the host computer 3310, base station 3320, and UE 3330 shown in Figure 18 may be equivalent to the host computer 3230, one of the base stations 3212a, 3212b, and 3212c, and one of the UEs 3291 and 3292, respectively, of Figure 17. That is, the inner workings of these entities may be as shown in Figure 18, and separately, the surrounding network topology may be that of Figure 17.

[0159] 18 , the OTT connection 3350 is depicted abstractly to show communication between the host computer 3310 and the user equipment 3330 via the base station 3320, without explicit reference to intermediary devices and the exact routing of messages through those devices. The network infrastructure may determine the routing, and the network infrastructure may be configured to hide the routing from the UE 3330 or from the service provider operating the host computer 3310, or both. While the OTT connection 3350 is active, the network infrastructure may also make decisions to dynamically change the routing, for example, based on load balancing considerations or reconfiguration of the network.

[0160] The wireless connection 3370 between the UE 3330 and the base station 3320 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT service provided to the UE 3330 using the OTT connection 3350 of which the wireless connection 3370 forms the last segment. More precisely, the teachings of these embodiments may improve performance because the RA reports reach the correct network node in an efficient manner, thereby providing benefits such as reduced user latency and better responsiveness.

[0161] Measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors that one or more embodiments improve upon. There may further be optional network functionality for reconfiguring the OTT connection 3350 between the host computer 3310 and the UE 3330 in response to fluctuations in the measurement results. The measurement procedures and / or the network functionality for reconfiguring the OTT connection 3350 may be implemented in the software 3311 of the host computer 3310 or in the software 3331 of the UE 3330, or both. In embodiments, sensors (not shown) may be deployed in or associated with communication devices through which the OTT connection 3350 passes, and the sensors may participate in the measurement procedures by providing values ​​of the monitored quantities exemplified above, or other physical quantities from which the software 3311, 3331 may calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 3350 may include message formats, retransmission settings, preferred routing, etc., and the reconfiguration need not affect the base station 3320, and the reconfiguration may be unknown or imperceptible to the base station 3320. Such procedures and functions may be known and practiced in the art. In some embodiments, the measurements may involve proprietary UE signaling that facilitates the host computer 3310 measurements of throughput, propagation time, latency, etc. The measurements may be implemented in software 3311, 3331 causing messages, particularly empty or “dummy” messages, to be sent using the OTT connection 3350 while the software 3311, 3331 monitors propagation times, errors, etc.

[0162] Figure 19 is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to Figures 17 and 18. For simplicity of this disclosure, only a drawing reference to Figure 19 is included in this section. In a first step 3410 of the method, the host computer provides user data. In an optional sub-step 3411 of the first step 3410, the host computer provides the user data by executing a host application. In a second step 3420, the host computer initiates a transmission carrying the user data to the UE. In an optional third step 3430, the base station transmits the user data carried in the host computer initiated transmission to the UE, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional fourth step 3440, the UE executes a client application associated with the host application executed by the host computer.

[0163] FIG. 20 is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIGS. 17 and 18. For simplicity of this disclosure, only a drawing reference to FIG. 20 is included in this section. In a first step 3510 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In a second step 3520, the host computer initiates a transmission carrying the user data to the UE. The transmission may proceed via the base station in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third step 3530, the UE receives the user data carried in the transmission.

[0164] FIG. 21 is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIGS. 17 and 18. For simplicity of this disclosure, only a drawing reference to FIG. 21 is included in this section. In an optional first step 3610 of the method, the UE receives input data provided by the host computer. Additionally or alternatively, in an optional second step 3620, the UE provides user data. In optional sub-step 3621 of the second step 3620, the UE provides the user data by executing a client application. In a further optional sub-step 3611 of the first step 3610, the UE executes the client application, which provides the user data in response to the received input data provided by the host computer. In providing the user data, the executed client application may further take into account user input received from the user. Regardless of the particular manner in which the user data is provided, the UE initiates transmission of the user data to the host computer in optional third sub-step 3630. In a fourth step 3640 of the method, the host computer receives user data transmitted from the UE according to the teachings of the embodiments described throughout this disclosure.

[0165] Figure 22 is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to Figures 17 and 18. For simplicity of this disclosure, only a drawing reference to Figure 22 is included in this section. In an optional first step 3710 of the method, the base station receives user data from the UE in accordance with the teachings of embodiments described throughout this disclosure. In an optional second step 3720, the base station initiates transmission of the received user data to the host computer. In a third step 3730, the host computer receives the user data carried in a transmission initiated by the base station.

[0166] Modifications of the disclosed embodiments and other embodiments will come to mind to one skilled in the art having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the embodiment(s) are not to be limited to the specific embodiment(s) disclosed and that modifications and other embodiments are intended to be included within the scope of the present disclosure. Although specific terms may be employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

[0167] Embodiments: Embodiment A1. 1. A method, implemented by a UE, for handling communications in a communications network, the method comprising: - providing a network node with assistance information instructing how to route an RA report of an RA procedure on a first RAT for the UE and the RA report between a second radio network node of a second RAT that collects the RA report and a first radio network node of a first RAT that controls a cell in which the RA procedure logged in the RA report was performed; A method comprising:

[0168] Embodiment A2. - instructing the second radio network node of one or more capabilities, such as the ability to report an RA report and / or report assistance information; The method of embodiment A1, further comprising:

[0169] Embodiment A3. - storing the obtained one or more RA reports associated with the one or more pieces of assistance information; The method of embodiment A1 or A2, further comprising:

[0170] Embodiment A4. The method of any one of embodiments A1 to A3, wherein the assistance information includes a CGI of the SPCell-ID, i.e., identification information of the first radio network node, for each element of the list in the RA report.

[0171] Embodiment B1. A method implemented by a network node, such as a second radio network node 13 or a second network node 16 associated with a second RAT, for handling communications in a communications network, the method comprising: - obtaining, for the UE, an RA report of an RA procedure of a first RAT and assistance information instructing how the RA report should be routed between a second radio network node of a second RAT that collects the RA report and a first radio network node that controls a cell in which the RA procedure logged in the RA report was performed; - Forwarding RA reports based on supporting information and A method comprising:

[0172] Embodiment B2. - receiving one or more indications from the UE indicating one or more capabilities, such as an ability to report an RA report and / or an ability to report assistance information; The method of embodiment B1, further comprising:

[0173] Embodiment B3. - sending a request to the UE to report one or more RA reports; The method of embodiment B1 or B2, further comprising:

[0174] Embodiment B4. - identifying one or more network nodes based on the aiding information; The method of any one of embodiments B1 to B3, further comprising:

[0175] Embodiment B5. The method of any one of embodiments B1 to B4, wherein the assistance information includes a CGI of the SPCell-ID, i.e., identification information of the first radio network node, for each element of the list in the RA report.

[0176] Embodiment C1. A UE for handling communications in a communications network, the UE comprising: Providing a network node with assistance information instructing how to route an RA report of an RA procedure on a first RAT for a UE and the RA report between a second radio network node of a second RAT that collects the RA report and a first radio network node of a first RAT that controls a cell in which the RA procedure logged in the RA report was performed. The UE is configured to:

[0177] Embodiment D1. a network node, such as a second radio network node 13 or a second network node 16 associated with a second RAT, for handling communications in a communications network, the network node comprising: obtaining, for the UE, an RA report of an RA procedure of a first RAT and assistance information instructing how the RA report should be routed between a second radio network node of a second RAT that collects the RA report and a first radio network node that controls a cell in which the RA procedure logged in the RA report was performed; Forwarding RA reports based on supporting information and A network node configured to

[0178] Abbreviation Description RA Random Access MN Master Node SN Secondary Node DC Dual Connectivity MME Mobility Management Entity AMF Access and Mobility Management Functions CGI Cell Global Identification Information PCell Primary Cell PSCell Primary Secondary Cell CN Core Network RAN Radio Access Network NCGI NR Cell Global Identifier ECGI Evolved Cell Global Identifier

[0179] References: [1] 37.340;Evolved Universal Terrestrial Radio Access(E-UTRA)and NR;Multi-connectivity;Stage2-V17.3.0, 3GPP [2] 38.331;NR;Radio Resource Control(RRC);Protocol specification;V-17.3.0, 3GPP [3] R2-2211164, Reply LS on SN RACH report status in R17, 3GPP TSG RAN WG#120

Claims

1. A method implemented by a user equipment (UE) (10) for handling communications in a communications network (1), said method comprising: providing (804) to a network node (150) a random access (RA) report of a RA procedure on a first radio access technology (RAT) for said UE (10) and assistance information instructing how said RA report should be routed between a second radio network node (13) of a second RAT that collects said RA report and a first radio network node (12) of said first RAT that controls a cell in which said RA procedure was performed that is logged in said RA report; A method comprising:

2. indicating (802) to said second radio network node (13) one or more capabilities including the capability to report an RA report and / or the capability to report said assistance information; The method of claim 1 further comprising:

3. - storing (801) one or more obtained RA reports associated with one or more pieces of assistance information; 3. The method of claim 1 or 2, further comprising:

4. 4. The method of claim 1, wherein the assistance information indicating how the RA report should be routed is defined by including a Cell Global Identity (CGI) and / or a Tracking Area Identifier (TAI) of Special Cell (SPCell) identity information for each element of the list of RA reports.

5. A method implemented by a network node (150) for handling communications in a communications network (1), said method comprising: - obtaining (903) a random access (RA) report of a first radio access technology (RAT) procedure for a user equipment (UE) (10) and assistance information indicating how the RA report should be routed between a second radio network node (13) of a second RAT that collects the RA report and a first radio network node (12) of the first RAT that controls a cell in which the RA procedure was performed and logged in the RA report; - forwarding (905) said RA report based on said assistance information; A method comprising:

6. receiving (901) one or more indications from the UE indicating one or more capabilities including a capability to report an RA report and / or a capability to report the assistance information; The method of claim 5 further comprising:

7. sending a request to the UE to report one or more RA reports (902); The method of claim 5 or 6, further comprising:

8. - identifying one or more network nodes based on said aiding information (904); The method of any one of claims 5 to 7, further comprising:

9. 9. The method of claim 5, wherein the assistance information indicating how the RA report should be routed is defined by including a Cell Global Identity (CGI) and / or a Tracking Area Identifier (TAI) of Special Cell (SPCell) identity information for each element of the list of RA reports.

10. A user equipment (UE) (10) for handling communications in a communications network (1), said UE (10) comprising: and providing a network node (150) with a random access (RA) report of a RA procedure on a first radio access technology (RAT) for the UE and assistance information instructing how the RA report should be routed between a second radio network node (13) of a second RAT that collects the RA report and a first radio network node (12) of the first RAT that controls a cell in which the RA procedure was performed and logged in the RA report. A user equipment (UE) (10) configured to:

11. The UE (10), Indicating to the second radio network node (13) one or more capabilities including the capability to report an RA report and / or the capability to report the assistance information. The UE (10) of claim 10, configured to:

12. The UE (10), Storing the obtained one or more RA reports associated with the one or more pieces of assistance information.

12. The UE (10) according to claim 10 or 11, configured to:

13. 13. The UE (10) of claim 10, wherein the assistance information instructing how the RA report should be routed is defined by including a Cell Global Identity (CGI) and / or a Tracking Area Identifier (TAI) of Special Cell (SPCell) identity information for each element of a list of RA reports.

14. A network node (150) associated with a second radio access technology (RAT) for handling communications in a communications network (1), said network node (150) comprising: obtaining a random access (RA) report of a first RAT procedure for a user equipment (UE) and assistance information indicating how the RA report should be routed between a second radio network node (13) of the second RAT that collects the RA report and a first radio network node (12) of the first RAT that controls a cell in which the RA procedure was performed and logged in the RA report; forwarding the RA report based on the assistance information; A network node (150) configured to:

15. The network node (150) receiving one or more indications from the UE (10) indicating one or more capabilities including an ability to report an RA report and / or an ability to report the assistance information; 15. The network node (150) of claim 14, configured to:

16. The network node (150) sending a request to the UE (10) to report one or more RA reports; 16. A network node (150) according to claim 14 or 15, configured to:

17. The network node (150) identifying one or more network nodes based on the assistance information; 17. A network node (150) according to any one of claims 14 to 16, configured to:

18. 18. A network node (150) according to any one of claims 14 to 17, wherein the assistance information instructing how the RA report should be routed is defined by including a Cell Global Identity (CGI) and / or a Tracking Area Identifier (TAI) of Special Cell (SPCell) identity information for each element of a list of RA reports.

19. 10. A computer program product comprising instructions that, when executed on at least one processor, cause the at least one processor to perform any of the methods of any one of claims 1 to 9, implemented by a network node (150) and a UE (10), respectively.

20. 10. A computer-readable storage medium having stored thereon a computer program product comprising instructions that, when executed on at least one processor, cause the at least one processor to perform any of the methods of any one of claims 1 to 9, implemented by a network node (150) and a UE (10), respectively.

21. 1. A user equipment (UE) for handling communications in a communications network, the UE comprising processing circuitry and memory, the memory comprising instructions executable by the processing circuitry, whereby the UE: and providing a network node (150) with a random access (RA) report of a RA procedure on a first radio access technology (RAT) for the UE and assistance information instructing how the RA report should be routed between a second radio network node (13) of a second RAT that collects the RA report and a first radio network node of the first RAT that controls a cell in which the RA procedure was performed that is logged in the RA report. a user equipment (UE) operable to:

22. 1. A network node for handling communications in a communications network, said network node comprising processing circuitry and memory, said memory comprising instructions executable by said processing circuitry, whereby said network node: obtaining a random access (RA) report of a first radio access technology (RAT) procedure for a user equipment (UE) and assistance information indicating how the RA report should be routed between a second radio network node (13) of a second RAT that collects the RA report and a first radio network node (12) of the first RAT that controls a cell in which the RA procedure was performed and logged in the RA report; forwarding the RA report based on the assistance information; a network node operable to:

Images