Method and apparatus for reporting RSSI measurements in wireless communication system

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method performed by a user equipment (UE) in a wireless communication system includes receiving configuration information for received signal strength indicator (RSSI) measurement reporting; setting neighbour frequency RSSI measurement result information based on a linear average of available RSSI sample value for neighbour frequencies, wherein the neighbour frequency RSSI measurement result information includes information on a subcarrier spacing (SCS); receiving a UE information request message; and transmitting a UE information response message including the neighbour frequency RSSI measurement result information.

Description

METHOD AND APPARATUS FOR REPORTING RSSI MEASUREMENTS IN WIRELESS COMMUNICATION SYSTEM

[0001] Embodiments disclosed herein relate to wireless communication networks, and more particularly to methods and systems for reporting RSSI measurements for performing self-optimization in wireless networks.

[0002] 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in "Sub 6GHz" bands such as 3.5GHz, but also in "Above 6GHz" bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.

[0003] At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.

[0004] Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.

[0005] Moreover, there has been ongoing standardization in air interface architecture / protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture / service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.

[0006] As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.

[0007] Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.

[0008] According to TS 38.300, Radio Access operating with shared spectrum channel access can support the following deployment scenarios:

[0009] - Scenario A: Carrier aggregation between New Radio (NR) in licensed spectrum (SpCell) and NR in shared spectrum (SCell);

[0010] - Scenario A.1: SCell is not configured with uplink (DownLink (DL) only);

[0011] - Scenario A.2: SCell is configured with uplink (DL+UpLink (UL)).

[0012] - Scenario B: Dual connectivity between Long Term Evolution (LTE) in licensed spectrum and NR in shared spectrum (PSCell);

[0013] - Scenario C: NR in shared spectrum (PCell);

[0014] - Scenario D: NR cell in shared spectrum and uplink in licensed spectrum;

[0015] - Scenario E: Dual connectivity between NR in licensed spectrum (PCell) and NR in shared spectrum (PSCell).

[0016] Carrier aggregation of cells in the shared spectrum is applicable to all deployment scenarios.

[0017] Self Optimisation in NR:

[0018] A 5G NR radio access network also known as NG-RAN (Next Generation Radio Network) comprises a number of NR base stations (also referred to herein as gNB). The gNBs can be connected to each other through the Xn interface, and will be connected to various core network elements (like AMF (Access and Mobility Management Function), UPF (User Plane Function) etc.). Further, the gNBs can be divided into two physical entities; i.e., a CU (Centralized Unit) and a DU (Distributed Unit). The CU provides support for the higher layers of the protocol stack (such as SDAP (Session Data Application Protocol), PDCP (Packet Data Convergence Protocol) and RRC (Radio Resource Control)), while the DU provides support for the lower layers of the protocol stack (such as RLC (Radio Link Control), MAC (Medium Access Control) and Physical layer).

[0019] Each gNB can have multiple cells serving many UEs (User Equipment). There are a large number of algorithms and configuration parameters used in NG-RAN. It can be a very difficult task to identify the most optimal radio parameters and operators used to resort to manual techniques like drive tests to identify the optimal parameters. However, such manual parameter tuning is a costly operation since it depends on a lot of factors like the number of users, number of neighbors, maximum throughput in the cell, average throughput in the cell etc. Further, whenever a neighboring gNB is installed or a new service is introduced, many of these manual operations need to be repeated.

[0020] To resolve this problem, 3gpp has introduced Self-Organizing Networks (SON) techniques in the wireless technologies like NR. SON was first introduced in 3gpp release 9, in LTE. SON solutions can be divided into three categories: Self-Configuration, Self-Optimization and Self-Healing. The SON architecture can be a centralized solution, a distributed solution, or a hybrid solution. Mobility Robustness Optimization (MRO) is a SON technique which is used to optimize various parameters related to mobility.

[0021] According to 3gpp specifications like TS 38.300 V17.0.0, Mobility Robustness Optimization aims at detecting and enabling correction of problems such as, but not limited to:

[0022] - Connection failure due to intra-system or inter-system mobility;

[0023] - Inter-system Unnecessary HO (too early inter-system HO from NR to E-UTRAN with no radio link failure); and

[0024] - Inter-system HO ping-pong.

[0025] The MRO provides means to distinguish the above problems from NR coverage related problems and other problems, not related to mobility. For analysis of connection failures, the UE makes the Radio Link Failure (RLF) Report available to the network. The UE stores the latest RLF Report, including both LTE and NR RLF reports, until the RLF report is fetched by the network or for 48 hours after the connection failure is detected.

[0026] One of the functions of MRO in NR R17 is to detect connection failures that occurred due to Too Early or Too Late inter-system handovers. These problems are defined as follows:

[0027] - Inter-system / Too Late Handover, wherein an RLF occurs after the UE has stayed in a cell belonging to an NG-RAN node for a long period of time; and the UE attempts to re-connect to a cell belonging to an E-UTRAN node.

[0028] - Inter-system / Too Early Handover, wherein an RLF occurs shortly after a successful handover from a cell belonging to an E-UTRAN node to a target cell belonging to an NG-RAN node; and the UE attempts to re-connect to the source cell or to another cell belonging to an E-UTRAN node.

[0029] One of the purposes of inter-system MRO in NR R17 is the detection of a non-optimal use of network resources. In particular, in case of inter-system operations and when NR is considered, the case known as Unnecessary HO to another system can occur, wherein the UE is handed over from NR to E-UTRAN even though the quality of the NR coverage was sufficient for the service used by the UE, and the handover may therefore be considered as unnecessary HO to another system (i.e., EPS) (too early inter-system HO without connection failure).

[0030] In inter-system HO, if the serving cell threshold (NR cell) is set too high, and a cell in another system (i.e., EPS) with good signal strength is available, a handover to another system may be triggered unnecessarily, resulting in an inefficient use of the networks. With a lower threshold, the UE could have continued in the source system (5GS).

[0031] One of the functions of Mobility Robustness Optimization is to detect ping-pongs that occur in inter-system environment, wherein a UE is handed over from a cell in a source system (e.g. 5GS) to a cell in a target system different from the source system (e.g. EPS), and then within a predefined limited time, the UE is handed over back to a cell in the source system, while the coverage of the source system was sufficient for the service used by the UE. The event may occur more than once.

[0032] The UE may log various events and information and report to the network for supporting optimizations. Some of the information that may be logged are RLF-Report and SHR (Successful handover report).

[0033] The RLF-Report field descriptions are as follows:

[0034] bwp-Info: This field is used to indicate the BWP information in which the UE detected consistent uplink LBT failure. This field is set only when the detected consistent uplink LBT failure did not trigger the random access procedure.

[0035] choCandidateCellList: This field is used to indicate the list of candidate target cells for conditional handover included in condRRCReconfig at the time of connection failure. The field does not include the candidate target cells included in measResultNeighCells.

[0036] choCellId: This field is used to indicate the candidate target cell for conditional handover included in condRRCReconfig that the UE selected for CHO based recovery while T311 is running.

[0037] connectionFailureType: This field is used to indicate whether the connection failure is due to radio link failure or handover failure.

[0038] csi-rsRLMConfigBitmap,csi-rsRLMConfigBitmap-v1650: These fields are used to indicate the CSI-RS indexes configured in the RLM configurations for the active BWP when the UE declares RLF or HOF. The UE first fills in the csi-rsRLMConfigBitmap-r16 to indicate the first 96 CSI-RS indexes and then csi-rsRLMConfigBitmap-v1650 to indicate the latter 96 CSI-RS indexes. The first / leftmost bit in csi-rsRLMConfigBitmap-r16 corresponds to CSI-RS index 0, the second bit corresponds to CSI-RS index 1. The first / leftmost bit in csi-rsRLMConfigBitmap-v1650 corresponds to CSI-RS index 96, the second bit corresponds to CSI-RS index 97. These fields are included only if the RadioLinkMonitoringConfig for the respective BWP is configured.

[0039] c-RNTI: This field indicates the C-RNTI used in the PCell upon detecting radio link failure or the C-RNTI used in the source PCell upon handover failure.

[0040] elapsedTimeSCGFailure: This field is used to indicate the time elapsed between the SCG failure and the MCG failure. The maximum value 1023 means 1023ms or longer.

[0041] elapsedTimeT316: This field is used to indicate the time elapsed between the initiation of the MCGFailureInformation and the reception of the RRCReconfiguration or RRCRelease or MobilityFromNRCommand messages.

[0042] failedPCellId: This field is used to indicate the PCell in which RLF is detected or the target PCell of the failed handover. For intra-NR handover nrFailedPCellId is included and for the handover from NR to EUTRA eutraFailedPCellId is included. The UE sets the ARFCN according to the frequency band used for transmission / reception when the failure occurred.

[0043] failedPCellId-EUTRA: This field is used to indicate the PCell in which RLF is detected or the source PCell of the failed handover in an E-UTRA RLF report.

[0044] lastHO-Type: This field is used to indicate the type of the last executed handover before the last detected connection failure. The field is set to cho if the last executed handover was initiated by a conditional reconfiguration execution. The field is set to daps if the last executed handover was a DAPS handover.

[0045] mcgRecoveryFailureCause: This field is used to indicate the cause of the fast MCG recovery failure.

[0046] measResultListEUTRA: This field refers to the last measurement results taken in the neighboring EUTRA Cells, when the radio link failure or handover failure happened.

[0047] measResultListNR: This field refers to the last measurement results taken in the neighboring NR Cells, when the radio link failure or handover failure happened.

[0048] measResultLastServCell: This field refers to the log measurement results taken in the PCell upon detecting radio link failure or the source PCell upon handover failure.

[0049] measResultLastServCell-RSSI: This field refers to the log RSSI measurement results in dBm (see TS 38.215) taken for the frequency of the PCell upon detecting radio link failure or handover failure.

[0050] measResultNeighFreqList-RSSI: This field is used to log the RSSI measurement results in dBm (see TS 38.215) taken for the neighbouring frequencies upon detecting radio link failure or handover failure, when UE operates in unlicensed spectrum.

[0051] measResult-RLF-Report-EUTRA: Includes the E-UTRA RLF-Report-r9 IE as specified in TS 36.331.

[0052] measResult-RLF-Report-EUTRA-v1690: Includes the E-UTRA RLF-Report-v9e0 IE as specified in TS 36.331.

[0053] noSuitableCellFound: This field is set by the UE when the T311 expires.

[0054] previousPCellId: This field is used to indicate the source PCell of the last handover (source PCell when the last executed RRCReconfiguration message including reconfigurationWithSync was received). For intra-NR handover nrPreviousCell is included and for the handover from EUTRA to NR eutraPreviousCell is included.

[0055] pSCellId: This field is used to indicate the PSCell in which the UE failed to perform fast MCG recovery procedure, or the UE successfully performed fast MCG recovery procedure.

[0056] ra-InformationCommon: This field is optionally included when connectionFailureType is set to 'hof' or when connectionFailureType is set to 'rlf' and the rlf-Cause equals to 'randomAccessProblem' or 'beamRecoveryFailure'; otherwise, this field is absent.

[0057] reconnectCellId: This field is used to indicate the cell in which the UE comes back to connected after connection failure and after failing to perform reestablishment. If the UE comes back to RRC CONNECTED in an NR cell then nrReconnectCellID is included and if the UE comes back to RRC CONNECTED in an LTE cell then eutraReconnectCellID is included

[0058] reestablishmentCellId: If the UE was not configured with conditionalReconfiguration at the time of re-establishment attempt, or if the cell selected for the re-establishment attempt is not a candidate target cell for conditional reconfiguration, this field is used to indicate the cell in which the re-establishment attempt was made after connection failure.

[0059] rlf-Cause: This field is used to indicate the cause of the last radio link failure that was detected. In case of handover failure information reporting (i.e., the connectionFailureType is set to 'hof'), the UE is allowed to set this field to any value, except for the case in which a radio link failure was detected in the source PCell while performing a DAPS handover.

[0060] ssbRLMConfigBitmap: This field is used to indicate the SS / PBCH block indexes configured in the RLM configurations for the active BWP when the UE declares RLF or HOF. The first / leftmost bit corresponds to SSB index 0, the second bit corresponds to SSB index 1. This field is included only if the RadioLinkMonitoringConfig for the respective BWP is configured.

[0061] timeConnFailure: This field is used to indicate the time elapsed since the last HO execution until connection failure. Actual value = field value * 100 milliseconds; for example, the maximum value 1023 means 102.3 seconds or longer.

[0062] timeConnSourceDAPS-Failure: This field is used to indicate the time that elapsed between the last DAPS handover execution and the radio link failure detected in the source cell while T304 is running, whose value is in milliseconds. For example, the maximum value 1023 means 1023ms or longer.

[0063] timeSinceFailure: This field is used to indicate the time that elapsed since the connection (radio link or handover) failure, whose value is in seconds. For example, the maximum value 172800 means 172800s or longer. In the case of failure(s) (either at source or at target or at both) associated to DAPS handover, this field indicates the time elapsed since the latest connection (radio link or handover) failure.

[0064] timeSinceCHO-Reconfig: In case of handover failure, this field is used to indicate the time elapsed between the initiation of the last handover execution towards the target cell and the reception of the latest conditional reconfiguration. In case of radio link failure, this field is used to indicate the time elapsed between the radio link failure and the reception of the latest conditional reconfiguration while connected to the source PCell. Actual value = field value * 100ms. For example, the maximum value 1023 means 102.3s or longer.

[0065] timeUntilReconnection: This field is used to indicate the time that elapsed between the connection (radio link or handover) failure and the next time the UE comes to RRC CONNECTED in an NR or EUTRA cell; after failing to perform reestablishment, whose value is in seconds. For example, the maximum value 172800 means 172800s or longer.

[0066] voiceFallbackHO: This field is set if for the failed mobility from NR, the voiceFallbackIndication was included in the MobilityFromNRCommand message.

[0067] The SHR Field descriptions are as follows:

[0068] c-RNTI: This field indicates the C-RNTI assigned by the target PCell of the handover for which the successful HO report was generated.

[0069] eutraTargetCellInfo: This field is used to indicate the target EUTRA PCell and the last measurement results of the target PCell of a handover in which the successful handover triggers the SuccessHO-Report.

[0070] eutra-C-RNTI: This field indicates the C-RNTI assigned by the E-UTRA target PCell of the mobility from NR command for which the successful HO report was generated.

[0071] measResultListNR: This field refers to the last measurement results taken in the neighboring NR Cells when a successful handover is executed.

[0072] measResultServCell-RSSI: This field refers to the log RSSI measurement results in dBm (see TS 38.215) taken for the frequency of the source PCell upon successful handover execution.

[0073] measResultNeighFreqList-RSSI: This field is used to log the RSSI measurement results in dBm (see TS 38.215) taken for the neighbouring frequencies upon successful handover execution.

[0074] rlf-InSourceDAPS: This field indicates whether a radio link failure occurred at the source cell while T304 was running.

[0075] shr-Cause: This field is used to indicate the cause of the successful HO report.

[0076] sourceCellMeas: This field refers to the last measurement results taken in the source PCell of a handover in which the successful handover triggers the SuccessHO-Report.

[0077] sourcePCellId: This field is used to indicate the source PCell of a handover in which the successful handover triggers the SuccessHO-Report.

[0078] targetPCellId: This field is used to indicate the target PCell of a handover in which the successful handover triggers the SuccessHO-Report.

[0079] targetCellMeas: This field refers to the last measurement results taken in the target PCell of a handover in which the successful handover triggers the SuccessHO-Report.

[0080] timeSinceCHO-Reconfig: This field is used to indicate the time elapsed between the initiation of the last conditional reconfiguration execution towards the target cell and the reception of the latest conditional reconfiguration for this target cell. Actual value = field value * 100ms. For example, the maximum value 1023 means 102.3s or longer.

[0081] timeSinceSHR: This field is used to indicate the time elapsed since the execution of the last MobilityFromNRCommand towards the target EUTRA cell, whose value is in seconds. For example, the maximum value 172800 means 172800s or longer.

[0082] upInterruptionTimeAtHO: This field is used to indicate the time elapsed between the time of arrival of the last PDCP PDU received from the source cell for any data radio bearer and the time of arrival of the first non-duplicate PDCP PDU received from the target cell for any data radio bearer, and it is measured at the time of arrival of the first non-duplicate PDCP PDU received from the target cell for any data radio bearer. The field is set only in case of DAPS handover, whose value is in milliseconds. For example, the maximum value 1023 means 1023ms or longer.

[0083] RSSI reporting:

[0084] NR carrier Received Signal Strength Indicator (NR carrier RSSI), comprises the linear average of the total received power (in Watts) observed only in certain OFDM symbols of measurement time resource(s), in the measurement bandwidth, over N number of resource blocks from all sources, including co-channel serving and non-serving cells, adjacent channel interference, thermal noise etc. An RSSI measurements is associated to a measurement identifier (measId) if the measRSSI-ReportConfig is configured within the corresponding reportConfig for this measId.

[0085] The UE may report the RSSI measurement results of the serving and neighbouring frequencies in the RLF-Report (for the handover failure or radio link failure) or the SHR. The UE reports RSSI information in an RLF-Report, according to 3gpp TS 38.331.

[0086] The UE may discard the successful handover information, i.e., release the UE variable VarSuccessHO-Report, 48 hours after the last successful handover information is added to the VarSuccessHO-Report.

[0087] Traditionally, the UE never reports the SCS while sending the measurements results for RSSI measurements, such as in measurement reports. During measurement reporting, the UE includes the measurement identifier along with RSSI measurements. However, the RLF report and SHR stored for a longer period, even when the UE has been transitioned to RRC_IDLE state. Thus, the measurement identifier is not suitable when the RSSI measurements are reported in RLF report and SHR, as it will force the network to store the frequency configuration for indiscriminately long periods. Thus, without SCS, the self optimization module in the network will not be able to process the received RSSI measurements for the self optimization.

[0088] Hence, there is a need in the art for solutions which will overcome the above mentioned drawback(s), among others.

[0089] In one embodiment, a method performed by a user equipment (UE) in a wireless communication system is provided. The method includes receiving configuration information for received signal strength indicator (RSSI) measurement reporting; setting neighbour frequency RSSI measurement result information based on a linear average of available RSSI sample value for neighbour frequencies, wherein the neighbour frequency RSSI measurement result information includes information on a subcarrier spacing (SCS); receiving a UE information request message; and transmitting a UE information response message including the neighbour frequency RSSI measurement result information.

[0090] In one embodiment, a method performed by a base station in a wireless communication system is provided. The method includes transmitting configuration information for RSSI measurement reporting of a UE; transmitting a UE information request message; and receiving a UE information response message including neighbour frequency RSSI measurement result information set to a linear average of available RSSI sample value for neighbour frequencies of the UE. The neighbour frequency RSSI measurement result information includes information on an SCS.

[0091] In one embodiment, a UE in a wireless communication system is provided, The UE includes a transceiver and at least one processor. The least one processor is configured to receive, via the transceiver, configuration information for RSSI measurement reporting, set neighbour frequency RSSI measurement result information based on a linear average of available RSSI sample value for neighbour frequencies, wherein the neighbour frequency RSSI measurement result information includes information on an SCS, receive, via the transceiver, a UE information request message, and transmit, via the transceiver, a UE information response message including the neighbour frequency RSSI measurement result information.

[0092] In one embodiment, a base station in a wireless communication system is provided. the base station includes a transceiver and at least one processor. The least one processor is configured to transmit, via the transceiver, configuration information for RSSI measurement reporting of a UE, transmit, via the transceiver, a UE information request message, and receive, via the transceiver, a UE information response message including neighbour frequency RSSI measurement result information set to a linear average of available RSSI sample value for neighbour frequencies of the UE. The neighbour frequency RSSI measurement result information includes information on an SCS.

[0093] Accordingly, the embodiments herein provide a method for reporting Received Signal Strength Indicator (RSSI) measurements by a User Equipment (UE) in a wireless communication network, wherein the method comprises including, by the UE, subcarrier spacing (SCS) along with New Radio - Absolute Radio Frequency Channel Number (NR-ARFCN); and reporting, by the UE, the SCS with the RSSI measurements for neighbour frequencies to the network.

[0094] Accordingly, the embodiments herein provide a method for reporting Received Signal Strength Indicator (RSSI) measurements by a User Equipment (UE) in a wireless communication network. The method comprising determining, by the UE, if the reporting criteria for RSRP measurements is configured for frequency, and subcarrier spacing (SCS) combination of a source Pcell; and reporting, by the UE, RSSI of the serving cell in at least one of a Radio Link Failure (RLF) Report, and a Successful Handover Report (SHR), if it is determined, by the UE, that the reporting criteria for RSRP measurements is configured for frequency, and subcarrier spacing (SCS) combination of the source Pcell.

[0095] Accordingly, the embodiments herein provide a User Equipment (UE) comprising a processing module; a memory; and a transceiver. The processing module is coupled with the memory, and the transceiver, and configured to include subcarrier spacing (SCS) along with New Radio - Absolute Radio Frequency Channel Number (NR-ARFCN); and report the SCS with the RSSI measurements for neighbour frequencies to the network.

[0096] Accordingly, the embodiments herein provide a User Equipment (UE) comprising a processing module; a memory; and a transceiver. The processing module is coupled with the memory, and the transceiver, and configured to determine if the reporting criteria for RSRP measurements is configured for frequency, and subcarrier spacing (SCS) combination of a source Pcell; and report RSSI of the serving cell in at least one of a Radio Link Failure (RLF) Report, and a Successful Handover Report (SHR), if it is determined, by the UE, that the reporting criteria for RSRP measurements is configured for frequency, and subcarrier spacing (SCS) combination of the source Pcell.

[0097] Accordingly, the embodiments herein provide a method for performing self optimization in a wireless communication network. The method comprising receiving, by a Next Generation Node B (gNB) in the wireless communication network, a subcarrier spacing (SCS) with Received Signal Strength Indicator (RSSI) measurements and Absolute Radio Frequency channel number (ARFCN) for neighbour frequencies from a User Equipment (UE); and performing, by the gNB, self optimization using the received SCS.

[0098] Accordingly, the embodiments herein provide a Next Generation Node B (gNB) comprising a processing module; a memory; and a transceiver, wherein the processing module is coupled with the memory, and the transceiver. The processing module is and configured to receive a subcarrier spacing (SCS) with Received Signal Strength Indicator (RSSI) measurements and Absolute Radio Frequency channel number (ARFCN) for neighbour frequencies from a User Equipment (UE); and perform self optimization using the received SCS.

[0099] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating at least one embodiment and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit thereof, and the embodiments herein include all such modifications.

[0100] According to various embodiments in the present disclosure, the UE can be configured to include SCS information in the measurement reports, RLF reports, or successful handover reports. By providing the network with explicit knowledge of the SCS, it becomes feasible to process the received RSSI measurements more accurately and efficiently for self-optimization, without imposing an undue requirement to store frequency configuration parameters over excessively long periods. Consequently, the Self-Organizing Network (SON) functionalities and Minimization of Drive Tests (MDT) operations can be substantially enhanced, as they can leverage the included SCS data to perform more precise network optimization, reduce unnecessary signaling overhead, and maintain an improved quality of service for users.

[0101] Embodiments herein are illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the following illustratory drawings. Embodiments herein are illustrated by way of examples in the accompanying drawings, and in which:

[0102] FIG. 1 depicts a UE connected to a wireless communication network, according to embodiments as disclosed herein;

[0103] FIG. 2 depicts a process for RSSI measurement reporting for SON / MDT, according to embodiments as disclosed herein;

[0104] FIG. 3 depicts the process of logging RSSI measurements for Inter-RAT SHR, according to embodiments as disclosed herein;

[0105] FIG. 4 depicts the process of logging RSSI measurements for SHR, according to embodiments as disclosed herein;

[0106] FIG. 5 depicts the process of logging RSSI measurements in RLF report, according to embodiments as disclosed herein;

[0107] FIG. 6 is a flowchart depicting the process of reporting RSSI measurements by a UE in a wireless communication network, according to embodiments as disclosed herein;

[0108] FIG. 7 is a flowchart depicting the process of reporting RSSI measurements by a UE in a wireless communication network, according to embodiments as disclosed herein;

[0109] FIG. 8 depicts the UE, according to embodiments as disclosed herein;

[0110] FIG. 9 is a flowchart depicting a method for performing self optimization in a wireless communication network, according to embodiments as disclosed herein; and

[0111] FIG. 10 depicts the gNB, according to embodiments as disclosed herein.

[0112] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.

[0113] For the purposes of interpreting this specification, the definitions (as defined herein) will apply and whenever appropriate the terms used in singular will also include the plural and vice versa. It is to be understood that the terminology used herein is for the purposes of describing particular embodiments only and is not intended to be limiting. The terms "comprising", "having" and "including" are to be construed as open-ended terms unless otherwise noted.

[0114] The words / phrases "exemplary", “example”, “illustration”, “in an instance”, “and the like”, “and so on”, “etc.”, “etcetera”, “e.g.,” , “i.e.,” are merely used herein to mean "serving as an example, instance, or illustration." Any embodiment or implementation of the present subject matter described herein using the words / phrases "exemplary", “example”, “illustration”, “in an instance”, “and the like”, “and so on”, “etc.”, “etcetera”, “e.g.,” , “i.e.,” is not necessarily to be construed as preferred or advantageous over other embodiments.

[0115] Embodiments herein may be described and illustrated in terms of blocks which carry out a described function or functions.　These blocks, which may be referred to herein as managers, units, modules, hardware components or the like, are physically implemented by analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by a firmware. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like.　The circuits constituting a block may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block.　Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the disclosure.　Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the disclosure.

[0116] It should be noted that elements in the drawings are illustrated for the purposes of this description and ease of understanding and may not have necessarily been drawn to scale. For example, the flowcharts / sequence diagrams illustrate the method in terms of the steps required for understanding of aspects of the embodiments as disclosed herein. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Furthermore, in terms of the system, one or more components / modules which comprise the system may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

[0117] The accompanying drawings are used to help easily understand various technical features and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the present disclosure should be construed to extend to any modifications, equivalents, and substitutes in addition to those which are particularly set out in the accompanying drawings and the corresponding description. Usage of words such as first, second, third etc., to describe components / elements / steps is for the purposes of this description and should not be construed as sequential ordering / placement / occurrence unless specified otherwise.

[0118] The embodiments herein achieve methods and systems for reporting subcarrier spacing (SCS) with the RSSI measurements for at least one neighbouring frequency, and / or a serving cell in wireless communication networks in Radio Link Failure (RLF) report(s). Referring now to the drawings, and more particularly to FIGS. 1 through 10, where similar reference characters denote corresponding features consistently throughout the figures, there are shown embodiments.

[0119] FIG. 1 depicts a UE connected to a wireless communication network. The UE 101, as depicted, can be served by a source cell 102 (hereinafter referred to as source cell, serving cell, target cell, and so on, interchangeably), and is in the vicinity of one or more neighbouring cells 103 (i.e., the UE 101 can detect signals from the one or more neighbouring cells (hereinafter referred to as neighbouring frequencies, neighbor frequencies, and so on, interchangeably)).

[0120] In an embodiment herein, the UE 101 may log and report the subcarrier spacing (SCS) (such as SCS of the Synchronization Signal / Physical Broadcast Channel (PBCH) block (SSB) measured) along with the RSSI measurements for neighbor frequencies in the reports such as RLF-Report, SHR, and so on. In an embodiment herein, the SCS as referred to herein, is the SCS corresponding to the SSB of the measurement object based on which the measurements are performed, and the measurement results are reported; i.e., SCS is the SCS configured within the measurement object configuration (ssbSubcarrierSpacing within MeasObjectNR) for which the RSSI measurements are reported.

[0121] FIG. 2 depicts a process for RSSI measurement reporting for SON / MDT. In step 201, the UE 101 receives a configuration, wherein the configuration includes measRSSI-ReportConfig within a measurement configuration. In an embodiment herein, the UE 101 can also receive the SHR configuration. In step 202, the UE 101 is triggered to log the RLF report or SHR. In step 203, the UE 101 logs the RLF report or SHR, wherein the logged RLF report or SHR includes RSSI measurements. In an embodiment herein, the UE 101 calculates the RSSI measurements as the average of the measurements for the duration of the report-config. In an embodiment herein, the UE 101 indicates SCS for one or more neighboring frequencies, when SSB is used for RSSI measurements. In step 204, the UE 101 receives a UE Information Request, wherein the UE Information Request requests the UE 101 to report RLF or SHR. In step 205, the UE 101 transmits the UE information response, wherein the UE information response includes the logged RLF report or SHR, which further contains SSB SCS, and RSSI measurements. The various actions in method 200 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 2 may be omitted.

[0122] In an embodiment herein, in TS 38.331, neighbor RSSI measurements can include the Absolute Radio Frequency Channel Number of the SSB frequency or CSI-RS frequency and RSSI values, wherein the reported RSSI values can be from 0 to 76. In an embodiment herein, the UE 101 also includes the SCS of SSB frequency in the neighbor RSSI measurements.

[0123] In an embodiment herein, the UE 101 may include the SCS, if ssbFrequency (ssbFrequency-r18) is included in the RSSI measurements of neighboring frequencies. In an embodiment herein, the UE 101 may include the SCS (only) if there are multiple measurement objects with different SCS configured for the same SSB frequency. In an embodiment herein, the gNB (i.e., the source gNB) does not configure multiple measurement objects with different SCSs configured for the same SSB frequency, if the RLF report or SHR is to be retrieved from the UE 101 (e.g., configured in OtherConfig).

[0124] The Measurement identifier for which the measurements are performed / reported maps the report configuration which configures corresponding measRSSI-ReportConfig and the measurement object for which the measurements are performed.

[0125] In an embodiment herein, the UE 101 may log and report the measurement identifier in the RLF report or SHR along with measurement results of neighboring frequencies (such as in MeasResultNeighFreq-RSSI-r18 given above). In this embodiment herein, the UE 101 includes the measurements corresponding to the measurement identifier along with the measurement identifier in the neighbor cell RSSI measurements. In this embodiment herein, the UE 101 may skip including SSB frequency, SSB SCS or CSI-RS reference frequency along with neighbor cell RSSI measurements in the SON / MDT reports such as RLF report, SHR, and so on.

[0126] In an embodiment herein, the UE 101 may include the measurement identifier along with the measurement results of neighboring frequencies (such as in MeasResultNeighFreq-RSSI-r18) in RLF report or SHR, and so on, which can be more optimal from a signaling perspective. However, this means that the gNB will have to either always map the same frequency and SCS to the same measurement identifier or store the measurement identifier along with the frequency and SCS for each UE 101, which will increase the storage requirement and implementation complexity at the network. Thus, reporting frequency and SCS is more efficient from a memory and implementation complexity perspective.

[0127] The gNB of the cell where RLF occurred or of the source cell or target cell where handover failure or near handover failure occurred receives SSBFrequency and SCS in RLF report or SHR within the UE information response from the UE 101 or from another gNB. The gNB then maps the measurements to the SSB frequency and SCS and takes steps to reduce / avoid the radio link failures (in case of HOF and RLF), handover failures (in case of HOF and RLF) or probable handover failures (in case of SHR).

[0128] In an embodiment herein, the UE 101 can report the serving cell RSSI in the RLF report if the measRSSI-ReportConfig is configured for the frequency, SCS combination of the source PCell (i.e., for the measurement identifier associated with source PCell). The UE 101 can report measResultLastServCell-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency, SCS combination of the source PCell (in case HO failure) or PCell (in case of RLF) up to the moment that the UE 101 detected the failure.

[0129] In an embodiment herein, the UE 101 reports RSSI measurements for the neighbor frequency, SCS combination if the UE's frequency, and SCS combination is different from the frequency, and SCS combination of the source PCell and if the measRSSI-ReportConfig is configured for the frequency, and SCS combination of the source PCell. The UE 101 sets the measResultNeighFreq-RSSI in the measResultNeighFreqList-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency, and SCS combinations and reports the same to the network.

[0130] In an embodiment herein, the operation(s) for reporting RLF report of the UE 101 can be represented by Table 1 as follows:

[0131] RLF report content determinationThe UE may determine the content in theVarRLF-Reportas follows:1> clear the information included inVarRLF-Report, if any;1> if the UE is not in SNPN access mode, set theplmn-IdentityListto include the list of EPLMNs stored by the UE (i.e. includes the RPLMN);1> else if the UE is in SNPN access mode, set thesnpn-IdentityListto include the list of equivalent SNPNs stored by the UE (i.e., registered SNPN);1> set themeasResultLastServCellto include the cell level RSRP, RSRQ and the available SINR, of the source PCell (in case HO failure) or PCell (in case RLF) based on the available SSB and CSI-RS measurements collected up to the moment the UE detected failure;1> if measRSSI-ReportConfig is configured for the frequency, SCS combination of the source PCell (in case HO failure) or PCell (in case of RLF), set the measResultLastServCell-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency,SCS combination of the source PCell (in case HO failure) or PCell (in case of RLF) up to the moment the UE detected the failure;1> for each of the configured measObjectNR if measRSSI-ReportConfig is configured for the configured frequency, SCS combination:*2>set the measResultNeighFreq-RSSI in the measResultNeighFreqList-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency, SCS combinations other than the frequency, SCS combination of the source PCell (in case HO failure) or of the PCell (in case RLF), up to the moment the UE detected failure;

[0132] In an embodiment herein, the UE 101 can report the serving cell RSSI in the RLF report if the measRSSI-ReportConfig is configured for measurement identifier associated with source PCell. The UE 101 can report measResultLastServCell-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the measurement identifier associated with the source PCell (in case HO failure) or PCell (in case of RLF) up to the moment that the UE 101 detected the failure.

[0133] In an embodiment herein, the UE 101 can report RSSI measurements for the neighbor frequency, and SCS combination if its associated measurement identifier is different from the associated measurement identifier of the source PCell and if the measRSSI-ReportConfig is configured for the measurement identifier of the neighbor frequency. The UE 101 can set the measResultNeighFreq-RSSI in the measResultNeighFreqList-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers corresponding to the measurement identifier and reports to the network.

[0134] In an embodiment herein, the operation(s) for reporting RLF report of the UE 101 can be represented by Table 2 as follows:

[0135] RLF report content determinationThe UE may determine the content in theVarRLF-Reportas follows:1> clear the information included inVarRLF-Report, if any;1> if the UE is not in SNPN access mode, set theplmn-IdentityListto include the list of EPLMNs stored by the UE (i.e. includes the RPLMN);1> else if the UE is in SNPN access mode, set thesnpn-IdentityListto include the list of equivalent SNPNs stored by the UE (i.e., registered SNPN);1> set themeasResultLastServCellto include the cell level RSRP, RSRQ and the available SINR, of the source PCell (in case HO failure) or PCell (in case RLF) based on the available SSB and CSI-RS measurements collected up to the moment the UE detected failure;1> if measRSSI-ReportConfig is configured for the measurement identifier associated to the source PCell (in case HO failure) or PCell (in case of RLF),*2> set the measResultLastServCell-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the measurement identifier associated to the source PCell (in case HO failure) or PCell (in case of RLF) up to the moment the UE detected the failure;1> for each of the configured measObjectNR if measRSSI-ReportConfig is configured in an associated measurement identifier:*2> set the measResultNeighFreq-RSSI in the measResultNeighFreqList-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the for the measurement identifier having frequency, SCS combination other than the frequency, SCS combination of the source PCell (in case HO failure) or of the PCell (in case RLF), up to the moment the UE detected failure;

[0136] In an embodiment herein, the UE 101 can report the serving cell RSSI in the SHR (or Inter-RAT SHR) if the measRSSI-ReportConfig is configured for the frequency, and SCS combination of the source PCell (i.e., for the measurement identifier associated with source PCell). The UE 101 can report the measResultLastServCell-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency, and SCS combination of the source PCell up to the moment that the UE 101 detected the failure.

[0137] In an embodiment herein, the UE 101 can report RSSI measurements for the neighbor frequency, and SCS combination if its frequency, and SCS combination is different from the frequency, and SCS combination of the source PCell and if the measRSSI-ReportConfig is configured for the frequency, and SCS combination of the source PCell. The UE 101 can set the measResultNeighFreq-RSSI in the measResultNeighFreqList-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency, and SCS combinations and reports the same to the network.

[0138] In an embodiment herein, the operation(s) for reporting successful handover report of the UE 101 can be represented by Table 3 as follows:

[0139] Actions for the successful handover report determinationThe UE may for the PCell:1> if the procedure is triggered due to successful completion of reconfiguration with sync, and if the ratio between the value of the elapsed time of the timer T304 and the configured value of the timer T304, included in the last appliedRRCReconfigurationmessage including thereconfigurationWithSync, is greater thanthresholdPercentageT304if included in thesuccessHO-Configreceived before executing the last reconfiguration with sync; or1> if the procedure is triggered due to successful completion of reconfiguration with sync, and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync, is greater thanthresholdPercentageT310included in thesuccessHO-Configif configured by the source PCell before executing the last reconfiguration with sync; or1> if the procedure is triggered due to successful completion of reconfiguration with sync, and if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the reconfiguration with sync procedure and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync, is greater thanthresholdPercentageT312included in thesuccessHO-Configif configured by the source PCell before executing the last reconfiguration with sync; or1> if the procedure is triggered due to successful completion of reconfiguration with sync, and ifsourceDAPS-FailureReportingis included in thesuccessHO-Configbefore executing the last reconfiguration with sync and is set totrueand if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running; or1> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PCell before executing the last Mobility from NR to E-UTRA, is greater thanthresholdPercentageT310included in thesuccessHO-Configif configured by the source PCell before executing the last Mobility from NR to E-UTRA; or1> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, and if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the Mobility from NR to E-UTRA and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PCell before executing the last Mobility from NR to E-UTRA, is greater thanthresholdPercentageT312included in thesuccessHO-Configif configured by the source PCell before executing the last Mobility from NR to E-UTRA:*2> store the successful handover information in VarSuccessHO-Report and determine the content in VarSuccessHO-Report as follows:**3> clear the information included in VarSuccessHO-Report, if any;**3> if the UE is not in SNPN access mode, set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e., includes the RPLMN);**3> else if the UE is in SNPN access mode, set the snpn-IdentityList to include the list of equivalent SNPNs stored by the UE (i.e., includes the registered SNPN), if available;**3> set the c-RNTI to the C-RNTI assigned by the target PCell of the handover;**3> if the procedure is triggered due to successful completion of reconfiguration with sync, for the source PCell in which the last RRCReconfiguration message including reconfigurationWithSync was applied; or**3> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, for the source PCell in which the last MobilityFromNRCommand concerning an inter-RAT handover from NR to E-UTRA was applied:***4> set the sourceCellID in sourceCellInfo to the global cell identity and tracking area code, if available, of the source PCell;***4> set the sourceCellMeas in sourceCellInfo to include the cell level RSRP, RSRQ and the available SINR, of the source PCell based on the available SSB and CSI-RS measurements collected up to the moment the UE sends RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA;***4> set the rsIndexResults in sourceCellMeas to include all the available SSB and CSI-RS measurement quantities of the source PCell collected up to the moment the UE sends RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA;***4> if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running:****5> set the rlf-InSourceDAPS in sourceCellInfo to true;**3> if the procedure is triggered due to successful completion of reconfiguration with sync, for the target PCell indicated in the last applied RRCReconfiguration message including reconfigurationWithSync:***4> set the targetCellID in targetCellInfo to the global cell identity and tracking area code, if available, of the target PCell;***4> set the targetCellMeas in targetCellInfo to include the cell level RSRP, RSRQ and the available SINR, of the target PCell based on the available SSB and CSI-RS measurements collected up to the moment the UE sends RRCReconfigurationComplete message;***4> set the rsIndexResults in targetCellMeas to include all the available SSB and CSI-RS measurement quantities of the target PCell collected up to the moment the UE sends RRCReconfigurationComplete message;***4> if the last applied RRCReconfiguration message including reconfigurationWithSync was included in the stored condRRCReconfig:****5> set the timeSinceCHO-Reconfig to the time elapsed between the initiation of the execution of conditional reconfiguration for the target PCell and the reception of the last conditionalReconfiguration including the condRRCReconfig of the target PCell in the source PCell;**3> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, for the target PCell indicated in the last applied MobilityFromNRCommand concerning an inter-RAT handover from NR to E-UTRA:***4> set the targetPCellId in eutraTargetCellInfo to the global cell identity and tracking area code, if available, of the target PCell;***4> set the targetCellMeas in eutraTargetCellInfo to include the cell level RSRP, RSRQ and the available SINR, of the target PCell based on the available measurements collected up to the moment the UE sends RRCConnectionReconfigurationComplete message;**3> if the procedure is triggered due to successful completion of reconfiguration with sync and if the ratio between the value of the elapsed time of the timer T304 and the configured value of the T304 timer, included in the last applied RRCReconfiguration message including the reconfigurationWithSync, is greater than thresholdPercentageT304 if included in the successHO-Config received before executing the last reconfiguration with sync:***4> set t304-cause in shr-Cause to true;***4> set the ra-InformationCommon to include the random-access related information associated to the random access procedure in the target PCell, as specified in clause 5.7.10.5;**3> if the ratio between the value of the elapsed time of the timer T310 and the configured value of the T310 timer, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync or the last Mobility from NR to E-UTRA, is greater than thresholdPercentageT310 included in the successHO-Config if configured by the source PCell before executing the last reconfiguration with sync or Mobility from NR to E-UTRA:***4> set t310-cause in shr-Cause to true;**3> if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the reconfiguration with sync procedure or Mobility from NR to E-UTRA, and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the T312 timer, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync or Mobility from NR to E-UTRA, is greater than thresholdPercentageT312 included in the successHO-Config if configured by the source PCell before executing the last reconfiguration with sync, or Mobility from NR to E-UTRA:***4> set t312-cause in shr-Cause to true;**3> if the procedure is triggered due to successful completion of reconfiguration with sync and if sourceDAPS-FailureReporting included in the successHO-Config if configured by the source PCell before executing the last reconfiguration with sync is set to true, and if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running:***4> set sourceDAPS-Failure in shr-Cause to true;**3> if the procedure is triggered due to successful completion of reconfiguration with sync, for each of the measObjectNR, configured by the source PCell, in which the last RRCReconfiguration message including reconfigurationWithSync was applied; or**3> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, for each of the measObjectNR, configured by the source PCell, in which the last MobilityFromNRCommand concerning an inter-RAT handover from NR to E-UTRA was applied:***4> if measRSSI-ReportConfig is configured for the frequency, SCS combination of the source PCell:****5> if the procedure is triggered due to successful completion of reconfiguration with sync:*****6> set the measResultServCell-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency, SCS combination of the source PCell up to the moment the UE sends the RRCReconfigurationComplete message****5> else if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA:*****6> set the measResultServCell-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency, SCS combination of the source PCell up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message;***4> for each of the configured measObjectNR if measRSSI-ReportConfig is configured for the configured frequency, SCS combination:****5> if the procedure is triggered due to successful completion of reconfiguration with sync:*****6> set the measResultNeighFreq-RSSI in the measResultNeighFreqList-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the associated neighbouring frequency, SCS combination up to the moment the UE sends the RRCReconfigurationComplete message;****5> else if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA:*****6> set the measResultNeighFreq-RSSI in the measResultNeighFreqList-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the associated neighbouring frequency, SCS combination up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message;***4> if measurements are available for the measObjectNR:****5> if the SS / PBCH block-based measurement quantities are available:*****6> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell or target PCell, ordered such that the cell with highest SS / PBCH block RSRP is listed first if SS / PBCH block RSRP measurement results are available, otherwise the cell with highest SS / PBCH block RSRQ is listed first if SS / PBCH block RSRQ measurement results are available, otherwise the cell with highest SS / PBCH block SINR is listed first, based on the available SS / PBCH block based measurements collected up to the moment the UE sends the RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA;*****6> for each neighbour cell included, include the optional fields that are available;NOTE 1: For the neighboring cells set included in measResultListNR in measResultNeighCells ordered based on the SS / PBCH block measurement quantities, the UE includes also the CSI-RS based measurement quantities, if available.****5> if the CSI-RS measurement quantities are available:*****6> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell and target PCell, ordered such that the cell with highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the cell with highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the cell with highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE sends the RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA;*****6> for each neighbour cell included, include the optional fields that are available;NOTE 2: For the neighboring cells set ordered based on the CSI-RS measurement quantities, the UE includes measurements only for the cells not yet included in measResultListNR in measResultNeighCells to avoid overriding SS / PBCH block-based ordered measurements.**3> if the procedure is triggered due to successful completion of reconfiguration with sync, for each of the measObjectEUTRA, configured by the source PCell in which the last RRCReconfiguration message including reconfigurationWithSync was applied; or**3> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, for each of the measObjectEUTRA, configured by the source PCell in which the last MobilityFromNRCommand concerning an inter-RAT handover from NR to E-UTRA was applied:***4> if measurements are available for the measObjectEUTRA:****5>set the measResultListEUTRA in measResultNeighCells to include the best measured cells ordered such that the cell with highest RSRP is listed first if RSRP measurement results are available, otherwise the cell with highest RSRQ is listed first, based on measurements collected up to the moment the UE sends the RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA;****5>for each neighbour cell included, include the optional fields that are available;**3>for each of the neighbour cells included in measResultNeighCells:***4>if the cell was a candidate target cell included in the condRRCReconfig within the conditionalReconfiguration configured by the source PCell, in which the last RRCReconfiguration message including reconfigurationWithSync was applied:****5>set the choCandidate to true in measResultNR;**3>if available, set the locationInfo as in 5.3.3.7;1>release successHO-Config configured by the source PCell and thresholdPercentageT304 if configured by the target PCell.

[0140] The UE 101 may discard the successful handover information, i.e., the UE 101 may release the UE variableVarSuccessHO-Report, 48 hours after the last successful handover information is added to theVarSuccessHO-Report.

[0141] In an embodiment herein, the UE 101 may report the serving cell RSSI in the SHR or Inter-RAT SHR if the measRSSI-ReportConfig is configured for measurement identifier associated with source PCell. The UE 101 may report measResultLastServCell-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the measurement identifier associated with the source PCell, up to the moment that the UE 101 detected the failure.

[0142] FIG. 3 depicts the process of logging RSSI measurements for Inter-RAT SHR. In step 301, the UE 101 includes CSI-RS frequency or SSB frequency and associated SSB SCS in the MeasResultNeighFreq-RSSI. In step 302, the UE 101 sets the measResultServCell-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency and SCS combination of the source PCell during the report-Interval in the report configuration associated to the measurement id corresponding to Pcell's frequency and including measRSSI-ReportConfig, up to the moment that the UE 101 sends the EUTRA RRCConnectionReconfigurationComplete message. In step 303, the UE 101 sets the measResultNeighFreq-RSSI in the measResultNeighFreqList-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the associated neighbouring frequency in the report-Interval in the report configuration associated to the measurement id corresponding to Pcell's frequency and including measRSSI-ReportConfig, up to the moment that the UE sends the EUTRA RRCConnectionReconfigurationComplete message. The UE 101 also includes the SCS along with NR-ARFCN and the measurements. The various actions in method 300 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 3 may be omitted.

[0143] In an embodiment herein, the UE 101 may report RSSI measurements in SHR or inter-RAT SHR for the neighbor frequency, and SCS combination if its associated measurement identifier is different from the associated measurement identifier of source PCell and if the measRSSI-ReportConfig is configured for the measurement identifier of the neighbor frequency. The UE 101 may set the measResultNeighFreq-RSSI in the measResultNeighFreqList-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers corresponding to the measurement identifier and reports the same to the network. The UE 101 also may include the SCS along with NR-ARFCN and the measurements.

[0144] In all the embodiments, the UE 101 may consider the SCS for SSB and not for CSI-RS; i.e., the frequency and SCS combination is considered only for SSB measurements, and just frequency is considered for CSI-RS measurements.

[0145] In an embodiment herein, the operation(s) for reporting successful handover report of the UE 101 can be represented by Table 4 as follows:

[0146] Actions for the successful handover report determinationThe UE may for the PCell:1> if the procedure is triggered due to successful completion of reconfiguration with sync, and if the ratio between the value of the elapsed time of the timer T304 and the configured value of the timer T304, included in the last applied RRCReconfiguration message including the reconfigurationWithSync, is greater than thresholdPercentageT304 if included in the successHO-Config received before executing the last reconfiguration with sync; or1> if the procedure is triggered due to successful completion of reconfiguration with sync, and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT310 included in the successHO-Config if configured by the source PCell before executing the last reconfiguration with sync; or1> if the procedure is triggered due to successful completion of reconfiguration with sync, and if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the reconfiguration with sync procedure and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312 included in the successHO-Config if configured by the source PCell before executing the last reconfiguration with sync; or1> if the procedure is triggered due to successful completion of reconfiguration with sync, and if sourceDAPS-FailureReporting is included in the successHO-Config before executing the last reconfiguration with sync and is set to true and if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running; or1> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PCell before executing the last Mobility from NR to E-UTRA, is greater than thresholdPercentageT310 included in the successHO-Config if configured by the source PCell before executing the last Mobility from NR to E-UTRA; or1> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, and if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the Mobility from NR to E-UTRA and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PCell before executing the last Mobility from NR to E-UTRA, is greater than thresholdPercentageT312 included in the successHO-Config if configured by the source PCell before executing the last Mobility from NR to E-UTRA:*2> store the successful handover information in VarSuccessHO-Report and determine the content in VarSuccessHO-Report as follows:**3> clear the information included in VarSuccessHO-Report, if any;**3> if the UE is not in SNPN access mode, set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e., includes the RPLMN);**3> else if the UE is in SNPN access mode, set the snpn-IdentityList to include the list of equivalent SNPNs stored by the UE (i.e., includes the registered SNPN), if available;**3> set the c-RNTI to the C-RNTI assigned by the target PCell of the handover;**3> if the procedure is triggered due to successful completion of reconfiguration with sync, for the source PCell in which the last RRCReconfiguration message including reconfigurationWithSync was applied; or**3> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, for the source PCell in which the last MobilityFromNRCommand concerning an inter-RAT handover from NR to E-UTRA was applied:***4> set the sourceCellID in sourceCellInfo to the global cell identity and tracking area code, if available, of the source PCell;***4> set the sourceCellMeas in sourceCellInfo to include the cell level RSRP, RSRQ and the available SINR, of the source PCell based on the available SSB and CSI-RS measurements collected up to the moment the UE sends RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA;***4> set the rsIndexResults in sourceCellMeas to include all the available SSB and CSI-RS measurement quantities of the source PCell collected up to the moment the UE sends RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA;***4> if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running:****5> set the rlf-InSourceDAPS in sourceCellInfo to true;**3> if the procedure is triggered due to successful completion of reconfiguration with sync, for the target PCell indicated in the last applied RRCReconfiguration message including reconfigurationWithSync:***4> set the targetCellID in targetCellInfo to the global cell identity and tracking area code, if available, of the target PCell;***4> set the targetCellMeas in targetCellInfo to include the cell level RSRP, RSRQ and the available SINR, of the target PCell based on the available SSB and CSI-RS measurements collected up to the moment the UE sends RRCReconfigurationComplete message;***4> set the rsIndexResults in targetCellMeas to include all the available SSB and CSI-RS measurement quantities of the target PCell collected up to the moment the UE sends RRCReconfigurationComplete message;***4> if the last applied RRCReconfiguration message including reconfigurationWithSync was included in the stored condRRCReconfig:****5> set the timeSinceCHO-Reconfig to the time elapsed between the initiation of the execution of conditional reconfiguration for the target PCell and the reception of the last conditionalReconfiguration including the condRRCReconfig of the target PCell in the source PCell;**3> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, for the target PCell indicated in the last applied MobilityFromNRCommand concerning an inter-RAT handover from NR to E-UTRA:***4> set the targetPCellId in eutraTargetCellInfo to the global cell identity and tracking area code, if available, of the target PCell;***4> set the targetCellMeas in eutraTargetCellInfo to include the cell level RSRP, RSRQ and the available SINR, of the target PCell based on the available measurements collected up to the moment the UE sends RRCConnectionReconfigurationComplete message;**3> if the procedure is triggered due to successful completion of reconfiguration with sync and if the ratio between the value of the elapsed time of the timer T304 and the configured value of the T304 timer, included in the last applied RRCReconfiguration message including the reconfigurationWithSync, is greater than thresholdPercentageT304 if included in the successHO-Config received before executing the last reconfiguration with sync:***4> set t304-cause in shr-Cause to true;***4> set the ra-InformationCommon to include the random-access related information associated to the random access procedure in the target PCell, as specified in clause 5.7.10.5;**3> if the ratio between the value of the elapsed time of the timer T310 and the configured value of the T310 timer, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync or the last Mobility from NR to E-UTRA, is greater than thresholdPercentageT310 included in the successHO-Config if configured by the source PCell before executing the last reconfiguration with sync or Mobility from NR to E-UTRA:***4> set t310-cause in shr-Cause to true;**3> if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the reconfiguration with sync procedure or Mobility from NR to E-UTRA, and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the T312 timer, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync or Mobility from NR to E-UTRA, is greater than thresholdPercentageT312 included in the successHO-Config if configured by the source PCell before executing the last reconfiguration with sync, or Mobility from NR to E-UTRA:***4> set t312-cause in shr-Cause to true;**3> if the procedure is triggered due to successful completion of reconfiguration with sync and if sourceDAPS-FailureReporting included in the successHO-Config if configured by the source PCell before executing the last reconfiguration with sync is set to true, and if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running:***4> set sourceDAPS-Failure in shr-Cause to true;**3> if the procedure is triggered due to successful completion of reconfiguration with sync, for each of the measObjectNR, configured by the source PCell, in which the last RRCReconfiguration message including reconfigurationWithSync was applied; or**3> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, for each of the measObjectNR, configured by the source PCell, in which the last MobilityFromNRCommand concerning an inter-RAT handover from NR to E-UTRA was applied:***4> if measRSSI-ReportConfig is configured for the measurement identifier associated to the source PCell:****5> if the procedure is triggered due to successful completion of reconfiguration with sync:*****6> set the measResultServCell-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the measurement identifier associated to the source PCell up to the moment the UE sends the RRCReconfigurationComplete message****5> else if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA:*****6> set the measResultServCell-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the measurement identifier associated to the source PCell up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message;***4> for each of the configured measObjectNR if measRSSI-ReportConfig is configured for the associated measurement identifier:****5> if the procedure is triggered due to successful completion of reconfiguration with sync:*****6> set the measResultNeighFreq-RSSI in the measResultNeighFreqList-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the associated measurement identifier up to the moment the UE sends the RRCReconfigurationComplete message;****5> else if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA:*****6> set the measResultNeighFreq-RSSI in the measResultNeighFreqList-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the associated measurement identifier up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message;***4> if measurements are available for the measObjectNR:****5> if the SS / PBCH block-based measurement quantities are available:*****6> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell or target PCell, ordered such that the cell with highest SS / PBCH block RSRP is listed first if SS / PBCH block RSRP measurement results are available, otherwise the cell with highest SS / PBCH block RSRQ is listed first if SS / PBCH block RSRQ measurement results are available, otherwise the cell with highest SS / PBCH block SINR is listed first, based on the available SS / PBCH block based measurements collected up to the moment the UE sends the RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA;*****6> for each neighbour cell included, include the optional fields that are available;NOTE 1: For the neighboring cells set included in measResultListNR in measResultNeighCells ordered based on the SS / PBCH block measurement quantities, the UE includes also the CSI-RS based measurement quantities, if available.****5> if the CSI-RS measurement quantities are available:*****6>set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell and target PCell, ordered such that the cell with highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the cell with highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the cell with highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE sends the RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA;*****6> for each neighbour cell included, include the optional fields that are available;NOTE 2: For the neighboring cells set ordered based on the CSI-RS measurement quantities, the UE includes measurements only for the cells not yet included in measResultListNR in measResultNeighCells to avoid overriding SS / PBCH block-based ordered measurements.**3> if the procedure is triggered due to successful completion of reconfiguration with sync, for each of the measObjectEUTRA, configured by the source PCell in which the last RRCReconfiguration message including reconfigurationWithSync was applied; or**3> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, for each of the measObjectEUTRA, configured by the source PCell in which the last MobilityFromNRCommand concerning an inter-RAT handover from NR to E-UTRA was applied:***4> if measurements are available for the measObjectEUTRA:****5> set the measResultListEUTRA in measResultNeighCells to include the best measured cells ordered such that the cell with highest RSRP is listed first if RSRP measurement results are available, otherwise the cell with highest RSRQ is listed first, based on measurements collected up to the moment the UE sends the RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA;****5> for each neighbour cell included, include the optional fields that are available;**3> for each of the neighbour cells included in measResultNeighCells:***4> if the cell was a candidate target cell included in the condRRCReconfig within the conditionalReconfiguration configured by the source PCell, in which the last RRCReconfiguration message including reconfigurationWithSync was applied:****5> set the choCandidate to true in measResultNR;**3> if available, set the locationInfo as in 5.3.3.7;1> release successHO-Config configured by the source PCell and thresholdPercentageT304 if configured by the target PCell.

[0147] The UE 101 may discard the successful handover information; i.e., the UE 101 may release the UE variable VarSuccessHO-Report, 48 hours after the last successful handover information is added to the VarSuccessHO-Report.

[0148] In an embodiment herein, if both the source PCell and at least one neighboring cell is associated to the same frequency during a handover failure or a successful handover where SHR is logged, but the SCS is different, the UE 101 reports the RSSI measurements of the frequency, SCS combination of source PCell as the serving cell RSSI measurements and the RSSI measurements of the frequency, SCS combination of the neighboring cell as neighbor frequency RSSI measurements in the RLF report and SHR.

[0149] FIG. 4 depicts the process of logging RSSI measurements for SHR. In step 401, the UE 101 includes the CSI-RS frequency or SSB frequency and associated SSB SCS in MeasResultNeighFreq-RSSI. In step 402, the UE 101 sets the measResultServCell-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency and SCS combination of the source PCell during the report-Interval in the report configuration associated to the measurement id corresponding to Pcell's frequency and including measRSSI-ReportConfig, up to the moment that the UE 101 sends the RRCReconfigurationComplete message. In step 403, the UE 101 sets the measResultNeighFreq-RSSI in the measResultNeighFreqList-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the associated neighbouring frequency in the report-Interval in the report configuration associated to the measurement id corresponding to Pcell's frequency and including measRSSI-ReportConfig, up to the moment that the UE 101 sends the RRCReconfigurationComplete message. The UE 101 may also include the SCS along with NR-ARFCN and the measurements. The various actions in method 400 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 4 may be omitted.

[0150] FIG. 5 depicts the process of logging RSSI measurements in RLF report. In step 501, the UE 101 includes CSI-RS frequency or SSB frequency and associated SSB SCS in MeasResultNeighFreq-RSSI. In step 502, the UE 101 sets the measResultServCell-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency of the source PCell during the report-Interval in the report configuration associated to the measurement id corresponding to Pcell's frequency and SCS combination and including measRSSI-ReportConfig, up to the moment that the RLF is detected. In step 503, the UE 101 sets the measResultNeighFreq-RSSI in the measResultNeighFreqList-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the associated neighbouring frequency in the report-Interval in the report configuration associated to the measurement id corresponding to Pcell's frequency and including measRSSI-ReportConfig, up to the moment that the RLF is detected. The UE 101 also includes the SCS along with NR-ARFCN and the measurements. The various actions in method 500 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 5 may be omitted.

[0151] In an embodiment herein, if both the serving PCell and at least one neighboring cell are associated to the same frequency during a radio link failure where the SHR is logged, but the SCS is different, the UE 101 may report the RSSI measurements of the frequency, and SCS combination of serving PCell as the serving cell RSSI measurements and the RSSI measurements of the frequency, and SCS combination of the neighboring cell as neighbor frequency RSSI measurements in the RLF report.

[0152] In an embodiment herein, the UE 101 may log the RSSI measurements in the RLF report or SHR for serving frequency as the linear average of sample value(s) provided by lower layers in the reportInterval for the serving frequency.

[0153] In an embodiment herein, if the duration in which the UE 101 has performed RSSI measurements in serving frequency by the UE 101 before logging RLF or SHR is less than reportInterval, the UE 101 may log the RSSI measurements in the RLF report or SHR for serving frequency as the linear average of sample value(s) provided by lower layers in that duration for the serving frequency.

[0154] In an embodiment herein, the UE 101 may log the RSSI measurements in the RLF report or SHR for neighbor frequency as the linear average of sample value(s) provided by lower layers in the reportInterval for the neighbor frequency.

[0155] In an embodiment herein, if the duration in which the UE 101 has performed RSSI measurements in neighboring frequency by the UE 101 before logging RLF or SHR is less than reportInterval, the UE 101 may log the RSSI measurements in the RLF report or SHR for neighboring frequency as the linear average of sample value(s) provided by lower layers in that duration for the neighboring frequency.

[0156] In an embodiment herein, the RSSI measurement reporting in RLF report may be represented by Table 5 as follows.

[0157] RLF report content determinationThe UE may determine the content in theVarRLF-Reportas follows:1> clear the information included inVarRLF-Report, if any;1> if the UE is not in SNPN access mode, set theplmn-IdentityListto include the list of EPLMNs stored by the UE (i.e., includes the RPLMN);1> else if the UE is in SNPN access mode, set thesnpn-IdentityListto include the list of equivalent SNPNs stored by the UE (i.e., registered SNPN);1> set themeasResultLastServCellto include the cell level RSRP, RSRQ and the available SINR, of the source PCell (in case HO failure) or PCell (in case RLF) based on the available SSB and CSI-RS measurements collected up to the moment the UE detected failure;1> ifmeasRSSI-ReportConfigis configured for the frequency of the source PCell (in case HO failure) or PCell (in case of RLF), set themeasResultLastServCell-RSSIto the linear average of the available RSSI sample value(s) provided by lower layers for the frequency of the source PCell (in case HO failure) or PCell (in case of RLF) in the report-Interval up to the moment the UE detected the failure;1> for each of the configuredmeasObjectNRifmeasRSSI-ReportConfigis configured for the configured frequency:*2> set themeasResultNeighFreq-RSSIin themeasResultNeighFreqList-RSSIto the linear average of the available RSSI sample value(s) provided by lower layers for the frequencies other than the frequency of the source PCell (in case HO failure) or of the PCell (in case RLF), in the report-Interval up to the moment the UE detected failure;

[0158] In an embodiment herein, the RSSI measurement reporting in successful handover report (SHR) may be represented by Table 6 as follows.

[0159] Actions for the successful handover report determinationThe UE may for the PCell:1> if the procedure is triggered due to successful completion of reconfiguration with sync, and if the ratio between the value of the elapsed time of the timer T304 and the configured value of the timer T304, included in the last appliedRRCReconfigurationmessage including thereconfigurationWithSync, is greater than thresholdPercentageT304 if included in thesuccessHO-Configreceived before executing the last reconfiguration with sync; or1> if the procedure is triggered due to successful completion of reconfiguration with sync, and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync, is greater thanthresholdPercentageT310included in thesuccessHO-Configif configured by the source PCell before executing the last reconfiguration with sync; or1> if the procedure is triggered due to successful completion of reconfiguration with sync, and if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the reconfiguration with sync procedure and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync, is greater thanthresholdPercentageT312included in thesuccessHO-Configif configured by the source PCell before executing the last reconfiguration with sync; or1> if the procedure is triggered due to successful completion of reconfiguration with sync, and ifsourceDAPS-FailureReportingis included in thesuccessHO-Configbefore executing the last reconfiguration with sync and is set to true and if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running; or1> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PCell before executing the last Mobility from NR to E-UTRA, is greater thanthresholdPercentageT310included in thesuccessHO-Configif configured by the source PCell before executing the last Mobility from NR to E-UTRA; or1> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, and if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the Mobility from NR to E-UTRA and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PCell before executing the last Mobility from NR to E-UTRA, is greater thanthresholdPercentageT312included in thesuccessHO-Configif configured by the source PCell before executing the last Mobility from NR to E-UTRA:*2> store the successful handover information in VarSuccessHO-Report and determine the content in VarSuccessHO-Report as follows:**3> clear the information included in VarSuccessHO-Report, if any;**3> if the UE is not in SNPN access mode, set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e., includes the RPLMN);**3> else if the UE is in SNPN access mode, set the snpn-IdentityList to include the list of equivalent SNPNs stored by the UE (i.e., includes the registered SNPN), if available;**3> set the c-RNTI to the C-RNTI assigned by the target PCell of the handover;**3> if the procedure is triggered due to successful completion of reconfiguration with sync, for the source PCell in which the last RRCReconfiguration message including reconfigurationWithSync was applied; or**3> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, for the source PCell in which the last MobilityFromNRCommand concerning an inter-RAT handover from NR to E-UTRA was applied:***4> set the sourceCellID in sourceCellInfo to the global cell identity and tracking area code, if available, of the source PCell;***4> set the sourceCellMeas in sourceCellInfo to include the cell level RSRP, RSRQ and the available SINR, of the source PCell based on the available SSB and CSI-RS measurements collected up to the moment the UE sends RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA;***4> set the rsIndexResults in sourceCellMeas to include all the available SSB and CSI-RS measurement quantities of the source PCell collected up to the moment the UE sends RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA;***4> if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running:****5> set the rlf-InSourceDAPS in sourceCellInfo to true;**3> if the procedure is triggered due to successful completion of reconfiguration with sync, for the target PCell indicated in the last applied RRCReconfiguration message including reconfigurationWithSync:***4> set the targetCellID in targetCellInfo to the global cell identity and tracking area code, if available, of the target PCell;***4> set the targetCellMeas in targetCellInfo to include the cell level RSRP, RSRQ and the available SINR, of the target PCell based on the available SSB and CSI-RS measurements collected up to the moment the UE sends RRCReconfigurationComplete message;***4> set the rsIndexResults in targetCellMeas to include all the available SSB and CSI-RS measurement quantities of the target PCell collected up to the moment the UE sends RRCReconfigurationComplete message;***4> if the last applied RRCReconfiguration message including reconfigurationWithSync was included in the stored condRRCReconfig:****5> set the timeSinceCHO-Reconfig to the time elapsed between the initiation of the execution of conditional reconfiguration for the target PCell and the reception of the last conditionalReconfiguration including the condRRCReconfig of the target PCell in the source PCell;**3> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, for the target PCell indicated in the last applied MobilityFromNRCommand concerning an inter-RAT handover from NR to E-UTRA:***4> set the targetPCellId in eutraTargetCellInfo to the global cell identity and tracking area code, if available, of the target PCell;***4> set the targetCellMeas in eutraTargetCellInfo to include the cell level RSRP, RSRQ and the available SINR, of the target PCell based on the available measurements collected up to the moment the UE sends RRCConnectionReconfigurationComplete message;**3> if the procedure is triggered due to successful completion of reconfiguration with sync and if the ratio between the value of the elapsed time of the timer T304 and the configured value of the T304 timer, included in the last applied RRCReconfiguration message including the reconfigurationWithSync, is greater than thresholdPercentageT304 if included in the successHO-Config received before executing the last reconfiguration with sync:***4> set t304-cause in shr-Cause to true;***4> set the ra-InformationCommon to include the random-access related information associated to the random access procedure in the target PCell, as specified in clause 5.7.10.5;**3> if the ratio between the value of the elapsed time of the timer T310 and the configured value of the T310 timer, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync or the last Mobility from NR to E-UTRA, is greater than thresholdPercentageT310 included in the successHO-Config if configured by the source PCell before executing the last reconfiguration with sync or Mobility from NR to E-UTRA:***4> set t310-cause in shr-Cause to true;**3> if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the reconfiguration with sync procedure or Mobility from NR to E-UTRA, and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the T312 timer, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync or Mobility from NR to E-UTRA, is greater than thresholdPercentageT312 included in the successHO-Config if configured by the source PCell before executing the last reconfiguration with sync, or Mobility from NR to E-UTRA:***4> set t312-cause in shr-Cause to true;**3> if the procedure is triggered due to successful completion of reconfiguration with sync and if sourceDAPS-FailureReporting included in the successHO-Config if configured by the source PCell before executing the last reconfiguration with sync is set to true, and if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running:***4> set sourceDAPS-Failure in shr-Cause to true;**3> if the procedure is triggered due to successful completion of reconfiguration with sync, for each of the measObjectNR, configured by the source PCell, in which the last RRCReconfiguration message including reconfigurationWithSync was applied; or**3> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, for each of the measObjectNR, configured by the source PCell, in which the last MobilityFromNRCommand concerning an inter-RAT handover from NR to E-UTRA was applied:***4> if measRSSI-ReportConfig is configured for the frequency of the source PCell:****5> if the procedure is triggered due to successful completion of reconfiguration with sync:*****6> set the measResultServCell-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency of the source PCell in the report-Interval up to the moment the UE sends the RRCReconfigurationComplete message****5> else if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA:*****6> set the measResultServCell-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the frequency of the source PCell in the report-Interval up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message;***4> for each of the configured measObjectNR if measRSSI-ReportConfig is configured for the configured frequency:****5> if the procedure is triggered due to successful completion of reconfiguration with sync:*****6> set the measResultNeighFreq-RSSI in the measResultNeighFreqList-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the associated neighbouring frequency in the report-Interval up to the moment the UE sends the RRCReconfigurationComplete message;****5> else if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA:*****6> set the measResultNeighFreq-RSSI in the measResultNeighFreqList-RSSI to the linear average of the available RSSI sample value(s) provided by lower layers for the associated neighbouring frequency in the report-Interval up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message;***4> if measurements are available for the measObjectNR:****5>if the SS / PBCH block-based measurement quantities are available:*****6> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell or target PCell, ordered such that the cell with highest SS / PBCH block RSRP is listed first if SS / PBCH block RSRP measurement results are available, otherwise the cell with highest SS / PBCH block RSRQ is listed first if SS / PBCH block RSRQ measurement results are available, otherwise the cell with highest SS / PBCH block SINR is listed first, based on the available SS / PBCH block based measurements collected up to the moment the UE sends the RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA;*****6> for each neighbour cell included, include the optional fields that are available;NOTE 1: For the neighboring cells set included in measResultListNR in measResultNeighCells ordered based on the SS / PBCH block measurement quantities, the UE includes also the CSI-RS based measurement quantities, if available.****5> if the CSI-RS measurement quantities are available:*****6> set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell and target PCell, ordered such that the cell with highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the cell with highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the cell with highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE sends the RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA;*****6> for each neighbour cell included, include the optional fields that are available;NOTE 2: For the neighboring cells set ordered based on the CSI-RS measurement quantities, the UE includes measurements only for the cells not yet included in measResultListNR in measResultNeighCells to avoid overriding SS / PBCH block-based ordered measurements.**3> if the procedure is triggered due to successful completion of reconfiguration with sync, for each of the measObjectEUTRA, configured by the source PCell in which the last RRCReconfiguration message including reconfigurationWithSync was applied; or**3> if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA, for each of the measObjectEUTRA, configured by the source PCell in which the last MobilityFromNRCommand concerning an inter-RAT handover from NR to E-UTRA was applied:***4> if measurements are available for the measObjectEUTRA:****5>set the measResultListEUTRA in measResultNeighCells to include the best measured cells ordered such that the cell with highest RSRP is listed first if RSRP measurement results are available, otherwise the cell with highest RSRQ is listed first, based on measurements collected up to the moment the UE sends the RRCReconfigurationComplete message if the procedure is triggered due to successful completion of reconfiguration with sync, or up to the moment the UE sends the EUTRA RRCConnectionReconfigurationComplete message if the procedure is triggered due to successful completion of Mobility from NR to E-UTRA;****5> for each neighbour cell included, include the optional fields that are available;**3> for each of the neighbour cells included in measResultNeighCells:***4> if the cell was a candidate target cell included in the condRRCReconfig within the conditionalReconfiguration configured by the source PCell, in which the last RRCReconfiguration message including reconfigurationWithSync was applied:****5> set the choCandidate to true in measResultNR;**3> if available, set the locationInfo as in 5.3.3.7;1> release successHO-Config configured by the source PCell and thresholdPercentageT304 if configured by the target PCell.

[0160] The UE 101 may discard the successful handover information, i.e., the UE 101 may release the UE variable VarSuccessHO-Report, 48 hours after the last successful handover information is added to the VarSuccessHO-Report.

[0161] The report-Interval as referred to herein is the report-interval in the report configuration (i.e., within the corresponding reportConfig) for the measurement identifier (measId) based on which measurements are performed / reported.

[0162] FIG. 6 is a flowchart depicting the process of reporting RSSI measurements by a UE in a wireless communication network. In step 601, the UE 101 determines the SCS for neighbour frequencies, wherein the determined SCS corresponds to the Synchronization Signal / Physical Broadcast Channel (PBCH) block (SSB) of the measurement object based on which the measurements are performed. The SCS is the SCS configured within a measurement object configuration for which the RSSI measurements are reported. In step 602, the UE 101 includes the SCS along with New Radio - Absolute Radio Frequency Channel Number (NR-ARFCN) and reports the SCS with the RSSI measurements for neighbour frequencies to the network. In an embodiment herein, the UE 101 reports the SCS with the RSSI measurements in MeasResultNeighFreq-RSSI. In an embodiment herein, the UE 101 includes the SCS in at least one of a Radio Link Failure (RLF) Report, and a Successful Handover Report (SHR). The various actions in method 600 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 6 may be omitted.

[0163] FIG. 7 is a flowchart depicting the process of reporting RSSI measurements by a UE in a wireless communication network. In step 701, the UE 101 determines if the reporting criteria for RSRP measurements is configured for frequency, and subcarrier spacing (SCS) combination of a source Pcell. If it is determined that the reporting criteria for RSRP measurements is configured for frequency, and subcarrier spacing (SCS) combination of the source Pcell, in step 702, the UE 101 reports RSSI of the serving cell in at least one of a Radio Link Failure (RLF) Report, and a Successful Handover Report (SHR). If it is determined that the reporting criteria for RSRP measurements is not configured for frequency, and subcarrier spacing (SCS) combination of the source Pcell, in step 703, the UE 101 includes the SCS in frequency and measurement values in RSSI measurements for neighbour frequencies, and in step 704, the UE 101 reports the RSSI measurements for neighbour frequencies. In an embodiment herein, measRSSI-ReportConfig is the reporting criteria for RSRP measurements. In an embodiment herein, the UE 101 sets the measResultLastServCell-RSSI to a linear average of at least one available RSSI sample value provided by lower layers for the frequency, and SCS combination of one of a source PCell, or a PCell, up to a moment that the UE 101 detected the failure for RLF report. In an embodiment herein, the UE 101 sets the measResultLastServCell-RSSI to a linear average of at least one available RSSI sample value provided by lower layers for the frequency, and SCS combination of one of a source PCell, or a PCell, up to a moment that the UE 101 sends a RRCReconfigurationComplete message during successful completion of reconfiguration with sync. In an embodiment herein, the UE 101 sets the measResultLastServCell-RSSI to a linear average of at least one available RSSI sample value provided by lower layers for the frequency, and SCS combination of one of a source PCell, or a PCell, up to a moment that the UE 101 sends an Evolved Universal Terrestrial Radio Access (E-UTRA) RRCConnectionReconfigurationComplete message due to successful completion of Mobility from New Radio (NR) to E-UTRA. The various actions in method 700 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 7 may be omitted.

[0164] FIG. 8 depicts the UE. The UE 101, as depicted, comprises a processing module 801, at least one memory 801, and at least one transceiver 803.

[0165] The processing module 801 can be at least one of a single processor, a plurality of processors, multiple homogeneous or heterogeneous cores, multiple Central Processing Units (CPUs) of different kinds, microcontrollers, special media, and other accelerators. The processing module 801 may be an Application Processor (AP), a graphics-only processing unit such as a Graphics Processing Unit (GPU), a Visual Processing Unit (VPU), and / or an Artificial Intelligence (AI)-dedicated processor such as a Neural Processing Unit (NPU).

[0166] In an embodiment herein, the at least one transceiver 803 is configured to enable communication between the UE, and at least one external entity (such as, but not limited to, the serving cell, the neighbouring cells, and so on) through a network or cloud. The transceiver 803 through which the UE 101 and the at least one external entity communicate may include wired and / or wireless communication medium compatible with one or more different communication protocols. The transceiver 803 may be configured for communication through a network. The network may comprise, but are not limited to, Global Positioning System (GPS), Global System for Mobile Communications (GSM), Local Area Network (LAN), Wireless Fidelity (Wi-Fi) compatibility, Bluetooth Low Energy (BLE), Near-field Communication (NFC), and so on. The wireless communication may further comprise one or more of Bluetooth, Zonal Intercommunication Global Standard (ZigBee), short-range wireless communication such as Ultra-wideband (UWB), medium-range wireless communication such as Wi-Fi, or long-range wireless communication such as Third Generation (3G), Fourth Generation (4G), or Worldwide Interoperability for Microwave Access (WiMAX), according to the usage environment.

[0167] In the embodiment shown herein, the at least one memory 802 may comprise one or more volatile and non-volatile memory components that are capable of storing data and instructions to be executed. Examples of the at least one memory 802 can be, but are not limited to, NAND, embedded Multimedia Card (eMMC), Secure Digital (SD) cards, Universal Serial Bus (USB), Serial Advanced Technology Attachment (SATA), solid-state drive (SSD), and so on. The at least one memory 802 may also include one or more computer-readable storage media. Examples of non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the at least one memory 802 may, in some examples, be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted to mean that the at least one memory 802 is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).

[0168] The processing module 801 can determine the SCS for neighbour frequencies, wherein the determined SCS corresponds to the Synchronization Signal / Physical Broadcast Channel (PBCH) block (SSB) of the measurement object based on which the measurements are performed. The SCS is the SCS configured within a measurement object configuration for which the RSSI measurements are reported. The processing module 801 can include SCS along with New Radio - Absolute Radio Frequency Channel Number (NR-ARFCN); and report the SCS with the RSSI measurements for neighbour frequencies to the network. In an embodiment herein, the processing module 801 can report the SCS with the RSSI measurements in MeasResultNeighFreq-RSSI. In an embodiment herein, the processing module 801 can include the SCS in at least one of a Radio Link Failure (RLF) Report, and a Successful Handover Report (SHR).

[0169] The processing module 801 can determine if the reporting criteria for RSRP measurements is configured for frequency, and subcarrier spacing (SCS) combination of a source Pcell. If the reporting criteria for RSRP measurements is configured for frequency, and subcarrier spacing (SCS) combination of a source Pcell, the processing module 801 can report RSSI of the serving cell in at least one of a Radio Link Failure (RLF) Report, and a Successful Handover Report (SHR). If the reporting criteria for RSRP measurements has not been configured for frequency, and subcarrier spacing (SCS) combination of a source Pcell, the processing module 801 can include the SCS in frequency and measurement values in RSSI measurements for neighbour frequencies. The processing module 801 can further report the RSSI measurements for neighbour frequencies. In an embodiment herein, the processing module 801 can set the measResultLastServCell-RSSI to a linear average of at least one available RSSI sample value provided by lower layers for the frequency, and SCS combination of one of a source PCell, or a PCell, up to a moment that the UE 101 detected the failure for RLF report. In an embodiment herein, the processing module 801 can set the measResultLastServCell-RSSI to a linear average of at least one available RSSI sample value provided by lower layers for the frequency, and SCS combination of one of a source PCell, or a PCell, up to a moment that the UE 101 sends a RRCReconfigurationComplete message during successful completion of reconfiguration with sync. In an embodiment herein, the processing module 801 can set the measResultLastServCell-RSSI to a linear average of at least one available RSSI sample value provided by lower layers for the frequency, and SCS combination of one of a source PCell, or a PCell, up to a moment that the UE 101 sends an Evolved Universal Terrestrial Radio Access (E-UTRA) RRCConnectionReconfigurationComplete message due to successful completion of Mobility from New Radio (NR) to E-UTRA.

[0170] FIG. 9 is a flowchart depicting a method for performing self optimization in a wireless communication network. In step 901, the gNB 1001 (as depicted in FIG. 10) receives the SCS with RSSI measurements and Absolute Radio Frequency channel number (ARFCN) for neighbour frequencies from the UE (101). In step 902, the gNB 1001 performs self optimization using the received SCS, and other information. The various actions in method 900 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 9 may be omitted.

[0171] FIG. 10 depicts the gNB. The gNB 1001, as depicted, comprises a processing module 1001A, at least one memory 1001B, and at least one transceiver 1001C.

[0172] The processing module 1001A can be at least one of a single processor, a plurality of processors, multiple homogeneous or heterogeneous cores, multiple Central Processing Units (CPUs) of different kinds, microcontrollers, special media, and other accelerators. The processing module 1001A may be an Application Processor (AP), a graphics-only processing unit such as a Graphics Processing Unit (GPU), a Visual Processing Unit (VPU), and / or an Artificial Intelligence (AI)-dedicated processor such as a Neural Processing Unit (NPU).

[0173] In an embodiment herein, the at least one transceiver 1001C is configured to enable communication between the gNB 1001, and at least one external entity (such as, but not limited to, the UE 101, and so on) through a network or cloud. The transceiver 1001C through which the gNB 1001 and the at least one external entity communicate may include wired and / or wireless communication medium compatible with one or more different communication protocols. The transceiver 1001C may be configured for communication through a network. The network may comprise, but are not limited to, Global Positioning System (GPS), Global System for Mobile Communications (GSM), Local Area Network (LAN), Wireless Fidelity (Wi-Fi) compatibility, Bluetooth Low Energy (BLE), Near-field Communication (NFC), and so on. The wireless communication may further comprise one or more of Bluetooth, Zonal Intercommunication Global Standard (ZigBee), short-range wireless communication such as Ultra-wideband (UWB), medium-range wireless communication such as Wi-Fi, or long-range wireless communication such as Third Generation (3G), Fourth Generation (4G), or Worldwide Interoperability for Microwave Access (WiMAX), according to the usage environment.

[0174] In the embodiment shown herein, the at least one memory 1001B may comprise one or more volatile and non-volatile memory components that are capable of storing data and instructions to be executed. Examples of the at least one memory 1001B can be, but are not limited to, NAND, embedded Multimedia Card (eMMC), Secure Digital (SD) cards, Universal Serial Bus (USB), Serial Advanced Technology Attachment (SATA), solid-state drive (SSD), and so on. The at least one memory 1001B may also include one or more computer-readable storage media. Examples of non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the at least one memory 1001B may, in some examples, be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted to mean that the at least one memory 1001B is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).

[0175] The processing module 1001A can receive the SCS with RSSI measurements and Absolute Radio Frequency channel number (ARFCN) for neighbour frequencies from the UE 101. The processing module 1001A can further perform self optimization using the received SCS and other information.

[0176] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the network elements. The elements include blocks which can be at least one of a hardware device, or a combination of hardware device and software module.

[0177] The embodiments disclosed herein describe methods and systems for reporting subcarrier spacing (SCS) with the RSSI measurements for at least one neighbouring frequency, and / or a serving cell in wireless communication networks in Radio Link Failure (RLF) report(s). Therefore, it is understood that the scope of the protection is extended to such a program and in addition to a computer readable means having a message therein, such computer readable storage means contain program code means for implementation of one or more steps of the method, when the program runs on a server or mobile device or any suitable programmable device. The method is implemented in at least one embodiment through or together with a software program written in e.g., Very high speed integrated circuit Hardware Description Language (VHDL) another programming language, or implemented by one or more VHDL or several software modules being executed on at least one hardware device. The hardware device can be any kind of portable device that can be programmed. The device may also include means which could be e.g., hardware means like e.g., an ASIC, or a combination of hardware and software means, e.g., an ASIC and an FPGA, or at least one microprocessor and at least one memory with software modules located therein. The method embodiments described herein could be implemented partly in hardware and partly in software. Alternatively, the invention may be implemented on different hardware devices, e.g., using a plurality of CPUs.

[0178] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and / or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of embodiments and examples, those skilled in the art will recognize that the embodiments and examples disclosed herein can be practised with modification within the scope of the embodiments as described herein.

Claims

1.A method performed by a user equipment (UE) in a wireless communication system, the method comprising:receiving configuration information for received signal strength indicator (RSSI) measurement reporting;setting neighbour frequency RSSI measurement result information based on a linear average of available RSSI sample value for neighbour frequencies, wherein the neighbour frequency RSSI measurement result information includes information on a subcarrier spacing (SCS);receiving a UE information request message; andtransmitting a UE information response message including the neighbour frequency RSSI measurement result information.2.The method of claim 1, further comprising:in case that the configuration information is configured for a frequency and an SCS associated with a primary cell (PCell), setting last serving cell RSSI measurement result information based on a linear average of available RSSI sample value for the frequency of the PCell,wherein the UE information response message further includes the last serving cell RSSI measurement result information.3.The method of claim 1, wherein the neighbour frequency RSSI measurement result information is included in a radio link failure report within the UE information response message.4.The method of claim 1, wherein the neighbour frequency RSSI measurement result information is included in a successful handover report within the UE information response message.5.A method performed by a base station in a wireless communication system, the method comprising:transmitting configuration information for received signal strength indicator (RSSI) measurement reporting of a user equipment (UE);transmitting a UE information request message; andreceiving a UE information response message including neighbour frequency RSSI measurement result information set to a linear average of available RSSI sample value for neighbour frequencies of the UE,wherein the neighbour frequency RSSI measurement result information includes information on a subcarrier spacing (SCS).6.The method of claim 5, wherein:the UE information response message further includes last serving cell RSSI measurement result information, andin case that the configuration information is configured for a frequency and an SCS associated with a primary cell (PCell), the last serving cell RSSI measurement result information is set to a linear average of available RSSI sample values for the frequency of the PCell.7.The method of claim 5, wherein the neighbour frequency RSSI measurement result information is included in a radio link failure report within the UE information response message.8.The method of claim 5, wherein the neighbour frequency RSSI measurement result information is included in a successful handover report within the UE information response message.9.A user equipment (UE) in a wireless communication system, the UE comprising:a transceiver; andat least one processor configured to:receive, via the transceiver, configuration information for received signal strength indicator (RSSI) measurement reporting,set neighbour frequency RSSI measurement result information based on a linear average of available RSSI sample value for neighbour frequencies, wherein the neighbour frequency RSSI measurement result information includes information on a subcarrier spacing (SCS),receive, via the transceiver, a UE information request message, andtransmit, via the transceiver, a UE information response message including the neighbour frequency RSSI measurement result information.10.The UE of claim 9, wherein the at least one processor is further configured to:in case that the configuration information is configured for a frequency and an SCS associated with a primary cell (PCell), set last serving cell RSSI measurement result information based on a linear average of available RSSI sample values for the frequency of the PCell, andwherein the UE information response message further includes the last serving cell RSSI measurement result information.11.The UE of claim 9, wherein the neighbour frequency RSSI measurement result information is included in a radio link failure report within the UE information response message.12.The UE of claim 9, wherein the neighbour frequency RSSI measurement result information is included in a successful handover report within the UE information response message.13.A base station in a wireless communication system, the base station comprising:a transceiver; andat least one processor configured to:transmit, via the transceiver, configuration information for received signal strength indicator (RSSI) measurement reporting of a user equipment (UE),transmit, via the transceiver, a UE information request message, andreceive, via the transceiver, a UE information response message including neighbour frequency RSSI measurement result information set to a linear average of available RSSI sample value for neighbour frequencies of the UE,wherein the neighbour frequency RSSI measurement result information includes information on a subcarrier spacing (SCS).14.The base station of claim 13, wherein:the UE information response message further includes last serving cell RSSI measurement result information, andin case that the configuration information is configured for a frequency and an SCS associated with a primary cell (PCell), the last serving cell RSSI measurement result information is set to a linear average of available RSSI sample values for the frequency of the PCell.15.The base station of claim 13, wherein the neighbour frequency RSSI measurement result information is included in a radio link failure report or a successful handover report within the UE information response message.

Images