Method and device for reporting RSSI measurements in a wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. A method performed by a user device (UE) in a wireless communication system comprises: receiving setting information for reporting a received signal strength indicator (RSSI) measurement; setting adjacent frequency RSSI measurement result information—adjacent frequency RSSI measurement result information includes information on subcarrier spacing (SCS)—based on a linear average of available RSSI sample values ​​for adjacent frequencies; receiving a UE information request message; and transmitting a UE information response message containing adjacent frequency RSSI measurement result information.

Description

Technology Field

[0001] The embodiments disclosed in the present invention relate to wireless communication networks, and in particular to methods and systems for reporting RSSI measurements to perform self-optimization in wireless networks. Background Technology

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in frequency bands below 6 GHz ('Sub 6 GHz'), such as 3.5 gigahertz (3.5 GHz), but also in ultra-high frequency bands called millimeter waves (mmWave), such as 28 GHz and 39 GHz ('Above 6 GHz'). In addition, for 6G mobile communication technology, which is referred to as a system beyond 5G, implementation in the terahertz band (e.g., the 3 terahertz (3 THz) band at 95 GHz) is being considered to achieve transmission speeds 50 times faster and ultra-low latency reduced to one-tenth compared to 5G mobile communication technology.

[0003] In the early stages of 5G mobile communication technology, aiming to satisfy service support and performance requirements for enhanced Mobile BroadBand (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), technologies such as beamforming and Massive MIMO to mitigate path loss and increase transmission distance in ultra-high frequency bands, support for various numerologies (such as the operation of multiple subcarrier spacings) and dynamic operation of slot formats for the efficient utilization of ultra-high frequency resources, initial access techniques to support multi-beam transmission and broadband, definition and operation of Band-Width Parts (BWP), Low Density Parity Check (LDPC) codes for high-volume data transmission, new channel coding methods such as Polar Codes for the reliable transmission of control information, and L2 pre-processing (L2 Standardization has been carried out for pre-processing, network slicing which provides a dedicated network specialized for specific services, and other methods.

[0004] Currently, discussions are underway to improve and enhance the performance of the initial 5G mobile communication technology, taking into account the services that the 5G mobile communication technology was intended to support. Additionally, standardization of the physical layer is in progress for technologies such as V2X (Vehicle-to-Everything), which helps autonomous vehicles make driving decisions and enhance user convenience based on their own location and status information transmitted by the vehicle; NR-U (New Radio Unlicensed), which aims for system operation in unlicensed bands to comply with various regulatory requirements; NR terminal low power consumption technology (UE Power Saving); Non-Terrestrial Network (NTN), which is direct terminal-satellite communication for securing coverage in areas where communication with the terrestrial network is impossible; and positioning.

[0005] In addition, standardization is underway in the field of wireless interface architecture / protocols for technologies such as the Industrial Internet of Things (IIoT) for supporting new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) which provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement including Conditional Handover and Dual Active Protocol Stack (DAPS) Handover, and 2-step Random Access (2-step RACH for NR) which simplifies random access procedures. Standardization is also underway in the field of system architecture / services for 5G baseline architectures (e.g., Service based Architecture, Service based Interface) for incorporating Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC), which provides services based on the location of the terminal.

[0006] When such 5G mobile communication systems are commercialized, connected devices, which are increasing explosively, will be connected to communication networks. Accordingly, it is expected that there will be a need to enhance the functionality and performance of 5G mobile communication systems and to integrate the operation of connected devices. To this end, new research is planned to be conducted on 5G performance improvement and complexity reduction, support for AI services, support for metaverse services, and drone communication using eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] Furthermore, the advancement of these 5G mobile communication systems encompasses multi-antenna transmission technologies such as new waveforms, Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas to guarantee coverage in the terahertz band of 6G mobile communication technology; metamaterial-based lenses and antennas; high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM); and Reconfigurable Intelligent Surface (RIS) technology to improve terahertz band signal coverage; as well as full-duplex technology for enhancing frequency efficiency and system networks in 6G mobile communication technology; AI-based communication technologies that realize system optimization by utilizing satellites and Artificial Intelligence (AI) from the design stage and internalizing end-to-end AI support functions; and the realization of services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could serve as a foundation for the development of next-generation distributed computing technologies.

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

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

[0010] - Scenario A.1: No uplink established in SCell (Downlink (DL) only);

[0011] - Scenario A.2: Uplink is established on SCell(DL+Uplink(UpLink; UL));

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

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

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

[0015] - Scenario E: Duplex connection between the licensed spectrum NR (PCell) and the shared spectrum NR (PSCell).

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

[0017] Self-optimization in NR:

[0018] A 5G NR radio access network, also known as NG-RAN (Next Generation Radio Network), comprises multiple NR base stations (also referred to as gNBs in this specification). Base stations (gNBs) can be interconnected via Xn interfaces and will be connected to various core network elements (such as the Access and Mobility Management Function (AMF), User Plane Function (UPF), etc.). Additionally, base stations can be divided into two physical entities: a Centralized Unit (CU) and a Distributed Unit (DU). The CU provides support for the upper 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 the physical layer).

[0019] Each base station can have multiple cells serving many User Equipment (UEs). Numerous algorithms and configuration parameters are used in NG-RAN. Identifying the most optimal radio parameters and operators, which rely on manual techniques such as drive tests to determine optimal parameters, can be a very difficult task. However, this manual parameter tuning is a costly operation because it depends on many factors, such as the number of users, the number of neighbors, the maximum throughput within the cell, and the average throughput within the cell. Furthermore, many of these manual operations need to be repeated whenever a neighboring base station is installed or a new service is introduced.

[0020] To address these issues, 3GPP introduced Self-Organizing Network (SON) technologies to wireless technologies such as NR. SON was first introduced to LTE in 3GPP Release 9. SON solutions can be divided into three categories: Self-Configuration, Self-Optimization, and Self-Healing. SON architectures can be centralized, distributed, or hybrid solutions. Mobility Robustness Optimization (MRO) is an SON technology used to optimize various parameters related to mobility.

[0021] According to 3GPP specifications such as TS 38.300 V17.0.0, MRO aims to enable the detection and correction of the following problems, but is not limited to:

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

[0023] - Unnecessary HO between other systems (too early HO between other systems from NR to E-UTRAN without radio link failure); and

[0024] - HO ping-pong between different systems.

[0025] MRO provides a means to distinguish the aforementioned problems from NR coverage-related problems and other problems unrelated to mobility. For the analysis of connection failures, the UE makes wireless link failure (RLF) reports available to the network. The UE stores the most recent RLF reports, including LTE and NR RLF reports, until the RLF report is fetched by the network or is fetched for 48 hours after a connection failure is detected.

[0026] One of the MRO functions of NR R17 is to detect connection failures caused by handovers between different systems that are too early or too late. These issues are defined as follows:

[0027] - Inter-system / too-late handover, RLF occurs after the UE has stayed in a cell belonging to the NG-RAN node for a long time; the UE attempts to reconnect to a cell belonging to the E-UTRAN node.

[0028] - Inter-system / Premature Handover, RLF occurs immediately 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 reconnect to the source cell or another cell belonging to the E-UTRAN node.

[0029] One of the purposes of the MRO between different systems in NR R17 is to detect non-optimal use of network resources. In particular, in the case of operations between different systems and when NR is considered, cases known as unnecessary HO to other systems may occur, where a UE is handed over from NR to E-UTRAN even though the quality of NR coverage was sufficient for the service used by the UE, and thus the handover can be considered an unnecessary HO to another system (i.e., EPS) (an HO between different systems that is too fast without connection failure).

[0030] In a handover between different systems, if the serving cell threshold (NR cell) is set too high and a cell from another system (i.e., EPS) with good signal strength is available, the handover to the other system is unnecessarily triggered, which can lead to inefficient use of the networks. If the threshold is low, the UE can continue to be used in the source system (5GS).

[0031] One of the functions of MRO (Mobility Robustness Optimization) is to detect ping-pong events occurring in the environment between different systems, where 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 within a predefined limited time, the UE is handed over back to the cell in the source system, but the coverage of the source system was sufficient for the service used by the UE. This event may occur more than once.

[0032] UEs can log various events and information and report them to the network to support optimization. Some of the information that can be logged includes RLF-Reports and SHR (Successful Handover Reports).

[0033] The description of the RLF-Report fields is as follows:

[0034] bwp-Info: This field is used to indicate BWP information where the UE detected a persistent uplink LBT failure. This field is set only if the detected persistent uplink LBT failure did not trigger a random access procedure.

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

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

[0037] connectionFailureType: This field is used to indicate whether the connection failure was caused by a wireless link failure or a handover failure.

[0038] csi-rsRLMConfigBitmap, csi-rsRLMConfigBitmap-v1650: These fields are used by the UE to indicate the CSI-RS indices set in the RLM configurations for the active BWP when declaring an RLF or HOF. The UE first populates csi-rsRLMConfigBitmap-r16 to indicate the first 96 CSI-RS indices, and then populates csi-rsRLMConfigBitmap-v1650 to indicate the later 96 CSI-RS indices. The first / leftmost bit of csi-rsRLMConfigBitmap-r16 corresponds to CSI-RS index 0, and the second bit corresponds to CSI-RS index 1. The first / leftmost bit of csi-rsRLMConfigBitmap-v1650 corresponds to CSI-RS index 96, and the second bit corresponds to CSI-RS index 97. These fields are included only when the RadioLinkMonitoringConfig is set for each BWP.

[0039] c-RNTI: This field indicates the C-RNTI used by the PCell when detecting a wireless link failure or the C-RNTI used by the source PCell when a handover failure occurs.

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

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

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

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

[0044] lastHO-Type: This field is used to indicate the type of the last handover executed prior to the last detected connection failure. This field is set to cho if the last executed handover was initiated by a conditional reset execution. This 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 quick MCG recovery failure.

[0046] measResultListEUTRA: This field refers to the last measurement results taken from adjacent EUTRA cells when a wireless link failure or handover failure occurred.

[0047] measResultListNR: This field refers to the last measurement results taken from adjacent NR cells when a wireless link failure or handover failure occurred.

[0048] measResultLastServCell: This field refers to the log measurement results taken from the PCell when detecting a wireless link failure or from the source PCell when a handover failure occurs.

[0049] measResultLastServCell-RSSI: This field refers to the log RSSI measurement results (dBm) taken for the Pcell frequency when detecting a wireless link failure or handover failure (see TS 38.215).

[0050] measResultNeighFreqList-RSSI: This field is used to log RSSI measurement results (dBm) taken for adjacent frequencies (see TS 38.215) when the UE detects a radio link failure or handover failure while operating in unlicensed spectrum.

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

[0052] measResult-RLF-Report-EUTRA-v1690: Includes 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 (the source PCell when the last executed RRCReconfiguration message containing reconfigurationWithSync was received). For handovers between the same NR, nrPreviousCell is included, and for handovers from EUTRA to NR, eutraPreviousCell is included.

[0055] pSCellId: This field is used to indicate the PSCell where the UE failed to perform the quick MCG recovery procedure or the PSCell where the UE successfully performed the quick MCG recovery procedure.

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

[0057] reconnectCellId: This field is used to indicate the cell to which the UE reconnects after a connection failure and a re-establishment failure. If the UE returns to the RRC CONNECTED state from an NR cell, nrReconnectCellID is included, and if the UE returns to the RRC CONNECTED state from an LTE cell, eutraReconnectCellID is included.

[0058] reestablishmentCellId: If conditionalReconfiguration is not set for the UE during the reestablishment attempt, or if the cell selected for the reestablishment attempt is not a candidate target cell for conditional reconfiguration, this field is used to indicate the cell on which the reestablishment attempt was made after the connection failure.

[0059] rlf-Cause: This field is used to indicate the cause of the last detected wireless link failure. For handover failure information reporting (i.e., when connectionFailureType is set to 'hof'), the UE may set this field to any value, except when a wireless link failure is detected in the source PCell during a DAPS handover.

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

[0061] timeConnFailure: This field is used to indicate the time elapsed from the last HO execution until connection failure. The actual value is the field value * 100 milliseconds; for example, the maximum value of 1023 means 102.3 seconds or more.

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

[0063] timeSinceFailure: This field is used to indicate the time elapsed since a connection (wireless link or handover) failure, and its value is in seconds. For example, the maximum value of 172800 means 172800 seconds or more. For failure(s) associated with a DAPS handover (at the source or target, or both), this field indicates the time elapsed since the most recent connection (wireless link or handover) failure.

[0064] timeSinceCHO-Reconfig: In the case of a handover failure, this field is used to indicate the time elapsed between the start of the last handover execution to the target cell and the reception of the most recent conditional reset. In the case of a wireless link failure, this field is used to indicate the time elapsed between the wireless link failure and the reception of the most recent conditional reset while connected to the source PCell. The actual value is the field value * 100ms. For example, the maximum value of 1023 means 102.3 seconds or more.

[0065] timeUntilReconnection: This field is used to indicate the time elapsed between a connection (wireless link or handover) failure and the next time the UE becomes RRC CONNECTED in an NR or EUTRA cell; after the reconnection fails, its value is in seconds. For example, the maximum value of 172800 means 172800 seconds or more.

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

[0067] The SHR field description is as follows:

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

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

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

[0071] measResultListNR: This field refers to the last measurement results taken from adjacent NR cells when a successful handover is executed.

[0072] measResultServCell-RSSI: This field refers to the log RSSI measurement results (dBm) taken for the frequency of the source Pcell when a successful handover is performed (see TS 38.215).

[0073] measResultNeighFreqList-RSSI: This field is used to log the RSSI measurement results (dBm) taken for adjacent frequencies (see TS 38.215) when a successful handover is executed.

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

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

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

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

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

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

[0080] timeSinceCHO-Reconfig: This field is used to indicate the time elapsed between the start of the last conditional reset execution for a target cell and the receipt of the most recent conditional reset for that target cell. The actual value is the field value * 100ms. For example, the maximum value of 1023 means 102.3 seconds or more.

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

[0082] upInterruptionTimeAtHO: This field is used to indicate the elapsed time between the arrival time of the last PDCP PDU received from the source cell for all data radio bearers and the arrival time of the first non-overlapping PDCP PDU received from the target cell for all data radio bearers, which is measured from the arrival time of the first non-overlapping PDCP PDU received from the target cell for all data radio bearers. This field is set only for DAPS handovers, and its value is in milliseconds. For example, the maximum value of 1023 means 1023ms or more.

[0083] RSSI Report:

[0084] The NR carrier Received Signal Strength Indicator (NR carrier RSSI) comprises the linear average of the total received power (watts) observed only at specific OFDM symbols of the measurement time resource(s) within the measurement bandwidth across N resource blocks from all sources, including co-channel serving and non-serving cells, adjacent channel interference, thermal noise, etc. RSSI measurements are associated with a measurement identifier (measId) when the measRSSI-ReportConfig is configured within the corresponding reportConfig for this measId.

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

[0086] The UE can discard successful handover information, that is, release the UE variable VarSuccessHO-Report 48 hours after the last successful handover information is added to VarSuccessHO-Report. The problem to be solved

[0087] Typically, the UE does not report an SCS while transmitting measurement results for RSSI measurements, as in measurement reports. During measurement reports, the UE includes a measurement identifier along with the RSSI measurements. However, RLF reports and SHRs are stored for extended periods, even when the UE transitions to the RRC_IDLE state. Therefore, measurement identifiers are unsuitable when RSSI measurements are reported in RLF reports and SHRs, as this forces the network to indiscriminately store frequency settings for long periods. Consequently, without an SCS, the network's self-optimization module will be unable to process the received RSSI measurements for self-optimization.

[0088] Therefore, in this technology field, solutions capable of overcoming the aforementioned disadvantage(s) are particularly needed. means of solving the problem

[0089] In one embodiment, a method is provided to be performed by user equipment (UE) in a wireless communication system. The method comprises the steps of: receiving setting information for reporting a received signal strength indicator (RSSI) measurement; setting adjacent frequency RSSI measurement result information—adjacent frequency RSSI measurement result information includes information on subcarrier spacing (SCS)—based on a linear average of available RSSI sample values ​​for adjacent frequencies; receiving a UE information request message; and transmitting a UE information response message containing adjacent 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 comprises the steps of: transmitting configuration information for reporting RSSI measurements of a UE; transmitting a UE information request message; and receiving a UE information response message containing adjacent frequency RSSI measurement result information set as the linear average of available RSSI sample values ​​for adjacent frequencies of the UE. The adjacent frequency RSSI measurement result information includes information regarding the 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 at least one processor is configured to receive configuration information for reporting RSSI measurements through the transceiver, set adjacent frequency RSSI measurement result information—adjacent frequency RSSI measurement result information includes information about SCS—based on the linear average of available RSSI sample values ​​for adjacent frequencies, receive a UE information request message through the transceiver, and transmit a UE information response message containing adjacent frequency RSSI measurement result information through the transceiver.

[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 at least one processor is configured to transmit configuration information for reporting RSSI measurements of a UE through the transceiver, transmit a UE information request message through the transceiver, and receive a UE information response message through the transceiver that includes adjacent frequency RSSI measurement result information set as the linear average of available RSSI sample values ​​for adjacent frequencies of the UE. The adjacent frequency RSSI measurement result information includes information regarding the SCS.

[0093] Accordingly, embodiments of the present specification provide a method for a user device (UE) to report Received Signal Strength Indicator (RSSI) measurements in a wireless communication network, the method comprising the step of the UE including a subcarrier spacing (SCS) together with a New Radio - Absolute Radio Frequency Channel Number (NR-ARFCN); and the step of the UE reporting the SCS having RSSI measurements for adjacent frequencies to the network.

[0094] Accordingly, embodiments of the present specification provide a method for a user device (UE) in a wireless communication network to report Received Signal Strength Indicator (RSSI) measurements, the method comprising: a step in which the UE determines whether a reporting standard for RSRP measurements is set for a combination of frequency and subcarrier spacing (SCS) of a source Pcell; and a step in which, if the UE determines that a reporting standard for RSRP measurements is set for a combination of frequency and subcarrier spacing (SCS) of a source Pcell, the UE reports the RSSI of a serving cell in at least one of a wireless link failure (RLF) report and a successful handover report (SHR).

[0095] Accordingly, embodiments of the present specification provide a user device (UE) comprising a processing module, memory, and a transceiver. The processing module is combined with the memory and the transceiver and is configured to report the SCS, which includes a subcarrier spacing (SCS) along with an NR-ARFCN (New Radio - Absolute Radio Frequency Channel Number), to a network having RSSI measurements for adjacent frequencies.

[0096] Accordingly, embodiments of this specification provide a user device (UE) comprising a processing module, memory, and a transceiver. The processing module is combined with the memory and the transceiver to determine whether a reporting criterion for RSRP measurements is set for a combination of the frequency and subcarrier spacing (SCS) of the source Pcell, and if the UE determines that a reporting criterion for RSRP measurements is set for a combination of the frequency and subcarrier spacing (SCS) of the source Pcell, it is configured to report the RSSI of the serving cell in at least one of a radio link failure (RLF) report and a successful handover report (SHR).

[0097] Accordingly, embodiments of the present specification provide a method for performing self-optimization in a wireless communication network. The method comprises the steps of: a base station (Next Generation Node B (gNB)) in a wireless communication network receiving a subcarrier spacing (SCS) having Received Signal Strength Indicator (RSSI) measurements and an Absolute Radio Frequency Channel Number (ARFCN) for adjacent frequencies from a user device (UE); and the base station performing self-optimization using the received SCS.

[0098] Accordingly, embodiments of this specification provide a base station (Next Generation Node B (gNB)) comprising a processing module, memory, and a transceiver, wherein the processing module is coupled with the memory and the transceiver. The processing module receives a subcarrier spacing (SCS) having Received Signal Strength Indicator (RSSI) measurements and an Absolute Radio Frequency Channel Number (ARFCN) for adjacent frequencies from a user device (UE); and is configured to perform self-optimization using the received SCS.

[0099] These and other aspects of the embodiments of this specification will be better understood when considered together with the following description and the accompanying drawings. However, the following description, while indicating at least one embodiment and numerous specific details thereof, should be interpreted as being provided by example rather than as a limitation. Many changes and modifications may be made within the scope of the embodiments of this specification without departing from the spirit thereof, and the embodiments of this specification include all such modifications. Effects of the invention

[0100] According to various embodiments of the present disclosure, a UE may be configured to include SCS information in measurement reports, RLF reports, or successful handover reports. By providing explicit knowledge of the SCS to the network, received RSSI measurements can be processed more accurately and efficiently for self-optimization without imposing excessive requirements to store frequency setting parameters over excessively long periods. Consequently, Self-Organizing Network (SON) functions and Minimization of Drive Test (MDT) operations can be significantly improved by utilizing the included SCS data to perform more precise network optimization, reduce unnecessary signaling overhead, and maintain improved quality of service to the user. Brief explanation of the drawing

[0101] The embodiments of this specification are illustrated in the accompanying drawings, and throughout the drawings, the same reference numerals indicate corresponding parts in various drawings. The embodiments of this specification will be better understood from the following description by referring to the following exemplary drawings. The embodiments of this specification are illustrated by examples in the accompanying drawings. FIG. 1 illustrates a UE connected to a wireless communication network according to embodiments as disclosed in the present specification. FIG. 2 illustrates an RSSI measurement reporting process for SON / MDT according to embodiments as disclosed in this specification. FIG. 3 illustrates a process for logging RSSI measurements for SHR between different RATs according to embodiments as disclosed in this specification. FIG. 4 illustrates a process for logging RSSI measurements for SHR according to embodiments as disclosed in this specification. FIG. 5 illustrates a process for logging RSSI measurements to an RLF report according to embodiments as disclosed in this specification. FIG. 6 is a flowchart illustrating the process of a UE reporting RSSI measurements in a wireless communication network according to embodiments as disclosed in this specification. FIG. 7 is a flowchart illustrating the process of a UE reporting RSSI measurements in a wireless communication network according to embodiments as disclosed in this specification. FIG. 8 illustrates a UE according to embodiments as disclosed in the present specification. FIG. 9 is a flowchart illustrating a method for performing self-optimization in a wireless communication network according to embodiments as disclosed in this specification. FIG. 10 illustrates a base station according to embodiments as disclosed in the present specification. Specific details for implementing the invention

[0102] The embodiments of this specification and their various features and advantageous details are further described in detail with reference to non-limiting embodiments illustrated in the accompanying drawings and described in detail in the following description. Descriptions of well-known components and processing techniques are omitted to avoid unnecessarily obscuring the embodiments of this specification. The examples used in this specification are merely intended to facilitate understanding of the ways in which the embodiments of this specification may be practiced and to enable those skilled in the art to practice the embodiments of this specification. Accordingly, the examples should not be construed as limiting the scope of the embodiments of this specification.

[0103] To interpret this specification, definitions (as defined herein) shall apply, and whenever appropriate, terms used in the singular shall include the plural and vice versa. The terms used herein are intended to describe specific embodiments only and are not intended to be restrictive. The terms “comprising,” “having,” and “including” shall be interpreted as open-ended terms unless otherwise specified.

[0104] In this specification, the words / phrases “exemplary,” “example,” “illustration,” “in an instance,” “and the like,” “and so on,” “etc.,” “etcetera,” “eg,” and “ie” are used simply to mean “serving as an example, instance, or illustration.” Any embodiment or implementation of the subject matter described in this specification using the words / phrases “exemplary,” “example,” “illustration,” “in an instance,” “and the like,” “and so on,” “e.g.,” “eg,” and “ie” is not to be interpreted as being preferred or advantageous over other embodiments.

[0105] The embodiments of this specification may be described and illustrated in terms of the described functions or blocks that perform the functions. These blocks, which may be referred to herein as managers, units, modules, hardware components, etc., 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, etc., and may optionally be driven by firmware. For example, these circuits may be implemented on one or more semiconductor chips or on substrate supports such as printed circuit boards. The circuits constituting the blocks may be implemented by dedicated hardware, processors (e.g., one or more programmed microprocessors and associated circuits), or a combination of dedicated hardware that performs some functions of the blocks and processors that perform other functions of the blocks. Each block of the embodiments may be physically separated into two or more interacting separate blocks without departing from the scope of this disclosure. Likewise, the blocks of the embodiments may be combined into physically more complex blocks without departing from the scope of the present disclosure.

[0106] It should be noted that elements of the drawings are illustrated for the sake of such explanation and ease of understanding and may not necessarily be illustrated to actual size. For example, flowcharts / sequence diagrams illustrate methods through steps necessary to understand aspects of embodiments as disclosed herein. Additionally, regarding the configuration of the device, one or more components of the device may be indicated by conventional symbols in the drawings, and the drawings may illustrate only these specific details relevant to understanding the embodiments so as not to obscure the drawings with details readily apparent to a person skilled in the art having the benefit of the description in this specification. Additionally, regarding the system, one or more components / modules comprising the system may be indicated by conventional symbols in the drawings, and the drawings may illustrate only these specific details relevant to understanding the embodiments so as not to obscure the drawings with details readily apparent to a person skilled in the art having the benefit of the description in this specification.

[0107] The attached drawings are used to facilitate understanding of various technical features, and it should be understood that the embodiments presented herein are not limited by the attached drawings. As such, the present disclosure should be interpreted to extend to all modifications, equivalents, and substitutions, in addition to those specifically stated in the attached drawings and corresponding descriptions. The use of words such as "first," "second," "third," etc., to describe components / elements / steps is for illustrative purposes only and should not be interpreted as a sequential order / arrangement / occurrence unless otherwise specified.

[0108] The embodiments of this specification achieve methods and systems for reporting the subcarrier spacing (SCS) through RSSI measurements for at least one adjacent frequency and / or serving cell in wireless link failure (RLF) report(s) in wireless communication networks. Now, referring to the drawings, particularly FIGS. 1 through 10, similar reference numerals consistently indicate corresponding features throughout the drawings, and embodiments are illustrated.

[0109] FIG. 1 illustrates a UE connected to a wireless communication network. As illustrated, the UE (101) may be served by a source cell (102) (hereinafter referred to interchangeably as source cell, serving cell, target cell, etc.) and is located near one or more adjacent cells (103) (i.e., the UE (101) may detect signals from one or more adjacent cells (hereinafter referred to interchangeably as adjacent frequencies, neighbor frequencies, etc.).

[0110] In one embodiment of the present specification, the UE (101) may log and report the subcarrier spacing (SCS) (e.g., the SCS of the measured SSB (Synchronization Signal / Physical Broadcast Channel (PBCH) block)) along with RSSI measurements for adjacent frequencies in reports such as RLF-Report, SHR, etc. In one embodiment of the present specification, the SCS as referred to herein is the SCS corresponding to the SSB of the measurement object, and measurements are performed and measurement results are reported based thereon, that is, the SCS is the SCS set within the measurement object setting (ssbSubcarrierSpacing within MeasObjectNR) where RSSI measurements are reported.

[0111] FIG. 2 illustrates an RSSI measurement reporting process for SON / MDT. In step (201), the UE (101) receives a configuration that includes measRSSI-ReportConfig within the measurement configuration. In one embodiment of the present specification, the UE (101) may also receive an SHR configuration. In step (202), the UE (101) is triggered to log an RLF report or an SHR. In step (203), the UE (101) logs an RLF report or an SHR, wherein the logged RLF report or SHR includes RSSI measurements. In one embodiment of the present specification, the UE (101) calculates the RSSI measurements as the average of the measurements over a period of the report-config. In one embodiment of the present specification, the UE (101) indicates an SCS for one or more adjacent frequencies when an SSB is used for RSSI measurements. In step (204), the UE (101) receives a UE information request, wherein the UE information request asks the UE (101) to report an RLF or SHR. In step (205), the UE (101) transmits a UE information response, wherein the UE information response includes a logged RLF report or SHR, which further includes SSB SCS and RSSI measurements. Various operations in the method (200) may be performed in the order presented, in a different order, or simultaneously. Additionally, in some embodiments, some operations listed in FIG. 2 may be omitted.

[0112] In one embodiment of the present specification, in TS 38.331, adjacent RSSI measurements may include the Absolute Radio Frequency Channel Number of an SSB frequency or CSI-RS frequency and RSSI values, wherein the reported RSSI values ​​may be values ​​from 0 to 76. In one embodiment of the present specification, the UE (101) also includes the SCS of the SSB frequency in adjacent RSSI measurements.

[0113] In one embodiment of the present specification, the UE (101) may include an SCS if ssbFrequency (ssbFrequency-r18) is included in RSSI measurements of adjacent frequencies. In one embodiment of the present specification, the UE (101) may include an SCS only if there are multiple measurement objects with different SCSs set for the same SSB frequency. In one embodiment of the present specification, the base station (i.e., source base station) does not set multiple measurement objects with different SCSs set for the same SSB frequency when an RLF report or SHR is to be retrieved from the UE (101) (e.g., set in OtherConfig).

[0114] The measurement identifier to which measurements are performed and reported maps the reporting configuration that sets the corresponding measRSSI-ReportConfig to the measurement object on which the measurements are performed.

[0115] In one embodiment of the present specification, the UE (101) may log and report the measurement identifier in an RLF report or SHR along with the measurement results of adjacent frequencies (e.g., the given MeasResultNeighFreq-RSSI-r18 as described above). In an embodiment of the present specification, the UE (101) includes measurements corresponding to the measurement identifier along with the measurement identifier in adjacent cell RSSI measurements. In an embodiment of the present specification, the UE (101) may skip including the SSB frequency, SSB SCS, or CSI-RS reference frequency along with adjacent cell RSSI measurements in SON / MDT reports such as RLF reports, SHR, etc.

[0116] In one embodiment of the present specification, the UE (101) may include a measurement identifier along with measurement results of adjacent frequencies (e.g., MeasResultNeighFreq-RSSI-r18) such as RLF reports or SHRs, which can be further optimized from a signaling perspective. However, this implies that the base station must 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 would increase storage requirements and implementation complexity in the network. Therefore, reporting the frequency and SCS is more efficient from the perspective of memory and implementation complexity.

[0117] The base station of the cell where the RLF occurred, or the base station of the source cell or target cell where the handover failure or near handover failure occurred, receives the SSBFrequency and SCS from the UE (101) or another base station in the UE information response or in the SHR. Then, the base station maps the measurements to the SSB frequency and SCS and takes steps to reduce or prevent radio link failures (in the case of HOF and RLF), handover failures (in the case of HOF and RLF), or probable handover failure (in the case of SHR).

[0118] In one embodiment of the present specification, the UE (101) may report the serving cell RSSI in the RLF report when the measRSSI-ReportConfig is configured for the frequency and SCS combination of the source PCell (i.e., the measurement identifier associated with the source PCell). The UE (101) may report the measResultLastServCell-RSSI as the linear average of the available RSSI sample value(s) provided by the lower layers for the frequency and SCS combination of the source PCell (in the case of HO failure) or PCell (in the case of RLF) up to the point where the UE (101) detects a failure.

[0119] In one embodiment of the present specification, when the frequency and SCS combination of the UE is different from the frequency and SCS combination of the source PCell and measRSSI-ReportConfig is configured for the frequency and SCS combination of the source PCell, the UE (101) reports RSSI measurements for adjacent frequency and SCS combinations. The UE (101) sets measResultNeighFreq-RSSI in measResultNeighFreqList-RSSI to the linear average of the available RSSI sample value(s) provided by the lower layers for the frequency and SCS combination and reports this to the network.

[0120] In one embodiment of the present specification, the operation(s) for reporting an RLF report of the UE (101) may be represented by Table 1 as follows:

[0121] RLF report content determination The UE may determine the content in the VarRLF-Report as follows:1> clear the information included in VarRLF-Report , if any;1> 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);1> 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., registered SNPN);1> set the measResultLastServCell to 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;

[0122] In one embodiment of the present specification, the UE (101) may report the serving cell RSSI in the RLF report when the measRSSI-ReportConfig is set for a measurement identifier associated with the source PCell. The UE (101) may report measResultLastServCell-RSSI as the linear average of the available RSSI sample value(s) provided by the lower layers for the measurement identifier associated with the source PCell (in the case of HO failure) or PCell (in the case of RLF) up to the point where the UE (101) detects a failure.

[0123] In one embodiment of the present specification, the UE (101) may report RSSI measurements for adjacent frequency and SCS combinations when the associated measurement identifier is different from the associated measurement identifier of the source PCell and measRSSI-ReportConfig is set for the measurement identifier of adjacent frequencies. The UE (101) may report to the network by setting measResultNeighFreq-RSSI in measResultNeighFreqList-RSSI to the linear average of the available RSSI sample value(s) provided by the lower layers corresponding to the measurement identifier.

[0124] In one embodiment of the present specification, the operation(s) for reporting an RLF report of the UE (101) may be represented by Table 2 as follows:

[0125] RLF report content determination The UE may determine the content in the VarRLF-Report as follows:1> clear the information included in VarRLF-Report , if any;1> 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);1> 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., registered SNPN);1> set the measResultLastServCell to 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;

[0126] In one embodiment of the present specification, the UE (101) may report the serving cell RSSI to the SHR (or SHR between other RATs) when the measRSSI-ReportConfig is configured for the frequency and SCS combination of the source PCell (i.e., the measurement identifier associated with the source PCell). The UE (101) may report the measResultLastServCell-RSSI as the linear average of the available RSSI sample value(s) provided by the lower layers for the frequency and SCS combination of the source PCell up to the point where the UE (101) detects a failure.

[0127] In one embodiment of the present specification, the UE (101) may report RSSI measurements for adjacent frequency and SCS combinations when the frequency and SCS combination is different from the frequency and SCS combination of the source PCell and measRSSI-ReportConfig is set for the frequency and SCS combination of the source PCell. The UE (101) may set measResultNeighFreq-RSSI of measResultNeighFreqList-RSSI to the linear average of the available RSSI sample value(s) provided by the lower layer(s) for the frequency and SCS combinations and report this to the network.

[0128] In one embodiment of the present specification, the operation(s) for reporting a successful handover of the UE (101) may be represented by Table 3 as follows:

[0129] Actions for the successful handover report determination The 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 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.,

[0130] UE (101) can discard successful handover information, that is, UE (101) can release the UE variable VarSuccessHO-Report 48 hours after the last successful handover information is added to VarSuccessHO-Report.

[0131] In one embodiment of the present specification, the UE (101) may report the serving cell RSSI to the SHR or another RAT-to-SHR when the measRSSI-ReportConfig is set for the measurement identifier associated with the source PCell. The UE (101) may report the measResultLastServCell-RSSI as the linear average of the available RSSI sample value(s) provided by the lower layers for the measurement identifier associated with the source PCell up to the point where the UE (101) detects a failure.

[0132] FIG. 3 illustrates a process for logging RSSI measurements for SHR between different RATs. In step (301), the UE (101) includes the CSI-RS frequency or SSB frequency and the associated SSB SCS in MeasResultNeighFreq-RSSI. In step (302), the UE (101) sets measResultServCell-RSSI to the linear average of the available RSSI sample value(s) provided by the lower layers for the combination of the source PCell's frequency and SCS during the report-Interval in a report configuration that includes measRSSI-ReportConfig and is associated with a measurement ID corresponding to the Pcell's frequency up to the point of transmitting the EUTRA RRCConnectionReconfigurationComplete message. In step (303), the UE (101) sets measResultNeighFreq-RSSI of measResultNeighFreqList-RSSI as the linear average of available RSSI sample value(s) provided by lower levels for associated adjacent frequencies within a reporting interval in a reporting configuration that includes measRSSI-ReportConfig and is associated with a measurement ID corresponding to the frequency of the Pcell up to the point when the UE transmits the EUTRA RRCConnectionReconfigurationComplete message. The UE (101) also includes an SCS along with NR-ARFCN and measurements. Various operations in method (300) may be performed in the order presented, in a different order, or simultaneously. Additionally, in some embodiments, some operations listed in FIG. 3 may be omitted.

[0133] In one embodiment of the present specification, the UE (101) may report RSSI measurements of SHR or other RAT-to-SHR for adjacent frequency and SCS combinations when the associated measurement identifier is different from the associated measurement identifier of the source PCell and measRSSI-ReportConfig is set for the measurement identifier of adjacent frequency. The UE (101) may report to the network the measResultNeighFreq-RSSI within measResultNeighFreqList-RSSI as the linear average of the available RSSI sample value(s) provided by the sub-layers corresponding to the measurement identifier. The UE (101) may also include the SCS along with the NR-ARFCN and measurements.

[0134] In all embodiments, the UE (101) may consider the SCS for the SSB but not for the CSI-RS; that is, the combination of frequency and SCS is considered only for the SSB measurement, and only the frequency is considered for the CSI-RS measurement.

[0135] In one embodiment of the present specification, the operation(s) for reporting a successful handover of the UE (101) may be represented by Table 4 as follows:

[0136] Actions for the successful handover report determination The 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 tosuccessful 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> ifthe 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 thresholdPercentageT312included 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 Mobilityfrom 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 RRCReconfigurationCompletemessage 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 measurementscollected 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 trackingarea 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 ofthe 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 ifconfigured 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, configuredby 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 configuredmeasObjectNR 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 themeasResultListNR 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 theneighboring 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 EUTRARRCConnectionReconfigurationComplete 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 wasapplied:***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, inwhich 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.

[0137] UE (101) can discard successful handover information, that is, UE (101) can release the UE variable VarSuccessHO-Report 48 hours after the last successful handover information is added to VarSuccessHO-Report.

[0138] In one embodiment of the present specification, when a handover failure or SHR is logged but at least one adjacent cell is associated with the same frequency during a successful handover where the SCS is different, the UE (101) reports the RSSI measurements of the frequency in the RLF report and SHR, the combination of the SCS of the source PCell as the RSSI measurements of the serving cell, and the RSSI measurements of the frequency, the combination of the SCS of the adjacent cell as the RSSI measurements of the adjacent frequency.

[0139] FIG. 4 illustrates a process for logging RSSI measurements for SHR. In step (401), the UE (101) includes the CSI-RS frequency or SSB frequency and the associated SSB SCS in MeasResultNeighFreq-RSSI. In step (402), the UE (101) sets measResultServCell-RSSI to the linear average of the available RSSI sample value(s) provided by the lower layers for the frequency and SCS combination of the source PCell during the reporting interval in a reporting configuration that includes measRSSI-ReportConfig and is associated with a measurement ID corresponding to the frequency of the Pcell up to the point of transmitting the RRCReconfigurationComplete message. In step (403), the UE (101) sets measResultNeighFreq-RSSI of measResultNeighFreqList-RSSI as the linear average of available RSSI sample value(s) provided by lower levels for associated adjacent frequencies within a reporting interval in a reporting configuration that includes measRSSI-ReportConfig and is associated with a measurement ID corresponding to the frequency of the Pcell up to the point of transmitting the RRCReconfigurationComplete message. The UE (101) may also include an SCS along with NR-ARFCN and measurements. Various operations in the method (400) may be performed in the order presented, in a different order, or simultaneously. Additionally, in some embodiments, some operations listed in FIG. 4 may be omitted.

[0140] FIG. 5 illustrates a process for logging RSSI measurements to an RLF report. In step (501), the UE (101) includes the CSI-RS frequency or SSB frequency and the associated SSB SCS in MeasResultNeighFreq-RSSI. In step (502), the UE (101) sets measResultServCell-RSSI to the linear average of the available RSSI sample value(s) provided by the lower layers for the frequency of the source PCell during the reporting interval in a report configuration that includes measRSSI-ReportConfig and is associated with a measurement ID corresponding to the PCell frequency and SCS combination up to the point where RLF is detected. In step (503), the UE (101) sets measResultNeighFreq-RSSI of measResultNeighFreqList-RSSI as the linear average of available RSSI sample value(s) provided by lower levels for associated adjacent frequencies within a reporting interval in a reporting configuration that includes measRSSI-ReportConfig and is associated with a measurement ID corresponding to the frequency of the PCell up to the point where RLF is detected. The UE (101) also includes an SCS with NR-ARFCN and measurements. Various operations in the method (500) may be performed in the order presented, in a different order, or simultaneously. Additionally, in some embodiments, some operations listed in FIG. 5 may be omitted.

[0141] In one embodiment of the present specification, when the SHR is logged but the SCS is different, and the serving PCell and at least one adjacent cell are both associated with the same frequency during a wireless link failure, the UE (101) may report the RSSI measurements of the frequency and the combination of the serving PCell's SCS in the RLF report as the RSSI measurements of the serving cell and the combination of the RSSI measurements of the frequency and the adjacent cell's SCS as the RSSI measurements of the adjacent frequency.

[0142] In one embodiment of the present specification, the UE (101) may log the RLF report for the serving frequency or the RSSI measurements in the SHR as a linear average of the sample value(s) provided by the lower levels in the reportInterval for the serving frequency.

[0143] In one embodiment of the present specification, if the period during which the UE (101) performed RSSI measurements at the serving frequency before logging the RLF or SHR is less than the reportInterval, the UE (101) may log the RLF report for the serving frequency or the RSSI measurements at the SHR as a linear average of the sample value(s) provided by the lower levels over the period for the serving frequency.

[0144] In one embodiment of the present specification, the UE (101) may log the RLF reports for adjacent frequencies or RSSI measurements in SHR as a linear average of the sample value(s) provided by the lower levels in the reportInterval for adjacent frequencies.

[0145] In one embodiment of the present specification, if the period during which the UE (101) performed RSSI measurements at adjacent frequencies before logging the RLF or SHR is less than the reportInterval, the UE (101) may log the RLF report for adjacent frequencies or the RSSI measurements at SHR as a linear average of the sample value(s) provided by the lower levels over the period for adjacent frequencies.

[0146] In one embodiment of the present specification, RSSI measurements reported in an RLF report may be represented by the following Table 5.

[0147] RLF report content determination The UE may determine the content in the VarRLF-Report as follows:1> clear the information included in VarRLF-Report , if any;1> 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);1> 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., registered SNPN);1> set the measResultLastServCell to 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 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 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 configured measObjectNR if measRSSI-ReportConfig is configured for the configured frequency:*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 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;

[0148] In one embodiment of the present specification, RSSI measurements reported in a successful handover report (SHR) can be represented by Table 6 as follows.

[0149] Actions for the successful handover report determination The 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 thesource 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 istriggered 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 UEsends 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 thetarget 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 timerT310 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 PCellbefore 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 whichthe 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 theconfigured 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 inmeasResultNeighCells 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 setincluded 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 EUTRARRCConnectionReconfigurationComplete 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 wasapplied:***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 whichthe 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.

[0150] UE (101) can discard successful handover information, that is, UE (101) can release the UE variable VarSuccessHO-Report 48 hours after the last successful handover information is added to VarSuccessHO-Report.

[0151] The report-Interval mentioned in this specification is a reporting interval within the reporting setting (i.e., the corresponding reportConfig) for a measurement identifier (measId), and measurements are performed and reported based thereon.

[0152] FIG. 6 is a flowchart illustrating the process of a UE reporting RSSI measurements in a wireless communication network. In step (601), the UE (101) determines an SCS for adjacent frequencies, wherein the determined SCS corresponds to the synchronization signal / physical broadcast channel (PBCH) block (SSB) of the measurement object, and measurements are performed based thereon. The SCS is an SCS set within the measurement object configuration where RSSI measurements are reported. In step (602), the UE (101) includes an SCS with an NR-ARFCN (New Radio - Absolute Radio Frequency Channel Number) and reports the SCS with RSSI measurements for adjacent frequencies to the network. In one embodiment of the present specification, the UE (101) reports an SCS with RSSI measurements to MeasResultNeighFreq-RSSI. In one embodiment of the present specification, the UE (101) includes an SCS in at least one of a wireless link failure (RLF) report and a successful handover report (SHR). Various operations in the method (600) may be performed in the presented order, in a different order, or simultaneously. Additionally, in some embodiments, some operations listed in FIG. 6 may be omitted.

[0153] FIG. 7 is a flowchart illustrating the process of a UE reporting RSSI measurements in a wireless communication network. In step (701), the UE (101) determines whether the reporting criteria for RSRP measurements are set for the combination of the source Pcell's frequency and subcarrier spacing (SCS). If it is determined that the reporting criteria for RSRP measurements are set for the combination of the source Pcell's frequency and subcarrier spacing (SCS), in step (702), the UE (101) reports the RSSI of the serving cell in at least one of a wireless link failure (RLF) report and a successful handover report (SHR). If it is determined that the reporting criteria for RSRP measurements are not set for the combination of the source Pcell's frequency and subcarrier spacing (SCS), in step (703), the UE (101) includes the SCS in the frequency and measurement values ​​in the RSSI measurements for adjacent frequencies, and in step (704), the UE (101) reports the RSSI measurements for adjacent frequencies. In one embodiment of the present specification, measRSSI-ReportConfig is a reporting standard for RSRP measurements. In one embodiment of the present specification, the UE (101) sets measResultLastServCell-RSSI to the linear average of at least one available RSSI sample value provided by lower layers for a frequency and SCS combination of either the source PCell or one of the PCells up to the point of detecting a failure for RLF reporting. In one embodiment of the present specification, the UE (101) sets measResultLastServCell-RSSI to the linear average of at least one available RSSI sample value provided by lower layers for a frequency and SCS combination of either the source PCell or one of the PCells up to the point of transmitting the RRCReconfigurationComplete message during the successful completion of reconfiguration through synchronization.In one embodiment of the present specification, the UE (101) sets measResultLastServCell-RSSI to the linear average of at least one available RSSI sample value provided by lower layers for a frequency and SCS combination of one of the source PCell or PCell up to the point of transmitting the E-UTRA (Evolved Universal Terrestrial Radio Access) RRCConnectionReconfigurationComplete message due to the successful completion of mobility from NR (New Radio) to E-UTRA. Various operations in the method (700) may be performed in the order presented, in a different order, or simultaneously. Additionally, in some embodiments, some operations listed in FIG. 7 may be omitted.

[0154] FIG. 8 illustrates a UE. As illustrated, the UE (101) includes a processing module (801), at least one memory (801), and at least one transceiver (803).

[0155] The processing module (801) may be at least one of a single processor, multiple processors, multiple homogeneous or heterogeneous cores, multiple Central Processing Units (CPUs) of different types, microcontrollers, special media, and other accelerators. The processing module (801) may be an Application Processor (AP), a graphics-dedicated 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).

[0156] In one embodiment of the present specification, at least one transceiver (803) is configured to enable communication between the UE and at least one external entity (e.g., serving cells, adjacent cells, etc., but not limited thereto) through a network or cloud. The transceiver (803) communicating between the UE (101) and at least one external entity may include a 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 include, but is not limited to, a Global Positioning System (GPS), Global System for Mobile Communications (GSM), Local Area Network (LAN), Wireless Fidelity (Wi-Fi) compatible, Bluetooth Low Energy (BLE), Near-Fire Communication (NFC). Depending on the usage environment, wireless communication may further include one or more of short-range wireless communication such as Bluetooth, ZigBee (Zonal Intercommunication Global Standard), and UWB (Ultra-wideband), medium-range wireless communication such as Wi-Fi, or long-range wireless communication such as 3G (Third Generation), 4G (Fourth Generation), and WiMAX (Worldwide Interoperability for Microwave Access).

[0157] In the embodiments described herein, at least one memory (802) may include one or more volatile and non-volatile memory components capable of storing data and instructions to be executed. Examples of at least one memory (802) may be, but are not limited to, NAND, eMMC (embedded Multimedia Card), SD (Secure Digital) cards, USB (Universal Serial Bus), SATA (Serial Advanced Technology Attachment), SSD (solid-state drive), etc. 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 disks, optical disks, floppy disks, flash memories, or forms of EPROM (electrically programmable memory) or EEPROM (electrically erasable and programmable memory). Additionally, in some examples, at least one memory (802) may be considered as a non-transient storage medium. The term “non-transitory” may indicate that the storage medium is not implemented by a carrier or propagated signal. However, the term “non-transitory” should not be interpreted to mean that at least one memory (802) is immovable. In certain examples, the non-transitory storage medium may store data that may change over time (e.g., RAM (Random Access Memory) or cache).

[0158] The processing module (801) can determine an SCS for adjacent frequencies, wherein the determined SCS corresponds to the synchronization signal / physical broadcast channel (PBCH) block (SSB) of the measurement object, and measurements are performed based thereon. The SCS is an SCS set within the measurement object configuration where RSSI measurements are reported. The processing module (801) may include an SCS with an NR-ARFCN (New Radio - Absolute Radio Frequency Channel Number) and report the SCS with RSSI measurements for adjacent frequencies to the network. In one embodiment of the specification, the processing module (801) reports an SCS with RSSI measurements to MeasResultNeighFreq-RSSI. In one embodiment of the specification, the processing module (801) includes an SCS in at least one of a wireless link failure (RLF) report and a successful handover report (SHR).

[0159] The processing module (801) can determine whether the reporting criteria for RSRP measurements are set for the frequency and subcarrier spacing (SCS) combination of the source Pcell. If the reporting criteria for RSRP measurements are set for the frequency and subcarrier spacing (SCS) combination of the source Pcell, the processing module (801) can report the RSSI of the serving cell in at least one of the radio link failure (RLF) report and the successful handover report (SHR). If the reporting criteria for RSRP measurements are not set for the frequency and subcarrier spacing (SCS) combination of the source Pcell, the processing module (801) may include the SCS in the frequency and measurement values ​​in the RSSI measurements for adjacent frequencies. The processing module (801) can also report RSSI measurements for adjacent frequencies. In one embodiment of the present specification, the processing module (801) may set measResultLastServCell-RSSI as the linear average of at least one available RSSI sample value provided by lower layers for a frequency and SCS combination of either the source PCell or one of the PCells up to the point when the UE (101) detects a failure regarding the RLF report. In one embodiment of the present specification, the processing module (801) may set measResultLastServCell-RSSI as the linear average of at least one available RSSI sample value provided by lower layers for a frequency and SCS combination of either the source PCell or one of the PCells up to the point when the UE (101) transmits the RRCReconfigurationComplete message during the successful completion of the reconfiguration through synchronization.In one embodiment of the present specification, the processing module (801) may set measResultLastServCell-RSSI as the linear average of at least one available RSSI sample value provided by lower layers for a frequency and SCS combination of one of the source PCell or PCell until the time of transmitting the E-UTRA (Evolved Universal Terrestrial Radio Access) RRCConnectionReconfigurationComplete message due to the successful completion of mobility from NR (New Radio) to E-UTRA.

[0160] FIG. 9 is a flowchart illustrating a method for performing self-optimization in a wireless communication network. In step (901), a base station (1001) (as shown in FIG. 10) receives an SCS with RSSI measurements and an ARFCN (Absolute Radio Frequency channel number) for adjacent frequencies from a UE (101). In step (902), the base station (1001) performs self-optimization using the received SCS and other information. Various operations in the method (900) may be performed in the order presented, in a different order, or simultaneously. Additionally, in some embodiments, some operations listed in FIG. 9 may be omitted.

[0161] FIG. 10 illustrates a base station. As illustrated, the base station (1001) includes a processing module (1001A), at least one memory (1001B), and at least one transceiver (1001C).

[0162] The processing module (1001A) may be at least one of a single processor, multiple processors, multiple homogeneous or heterogeneous cores, multiple central processing units (CPUs) of different types, microcontrollers, special media, and other accelerators. The processing module (1001A) may be an application processor (AP), a graphics-dedicated processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU) and / or a neural processing unit (NPU), or an artificial intelligence (AI)-dedicated processor.

[0163] In one embodiment of the present specification, at least one transceiver (1001C) is configured to enable communication between a base station (1001) and at least one external entity (e.g., UE (101), but not limited thereto) through a network or cloud. The transceiver (1001C) through which the base station (1001) and at least one external entity communicate may include a 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 include, but is not limited to, a Global Positioning System (GPS), Global System for Mobile Communications (GSM), Local Area Network (LAN), Wireless Fidelity (Wi-Fi) compatible, Bluetooth Low Energy (BLE), Near-Fire Communication (NFC). Depending on the usage environment, wireless communication may further include one or more of short-range wireless communication such as Bluetooth, ZigBee (Zonal Intercommunication Global Standard), and UWB (Ultra-wideband), medium-range wireless communication such as Wi-Fi, or long-range wireless communication such as 3G (Third Generation), 4G (Fourth Generation), and WiMAX (Worldwide Interoperability for Microwave Access).

[0164] In the embodiments described herein, at least one memory (1001B) may include one or more volatile and non-volatile memory components capable of storing data and instructions to be executed. Examples of at least one memory (1001B) may be, but are not limited to, NAND, eMMC (embedded Multimedia Card), SD (Secure Digital) cards, USB (Universal Serial Bus), SATA (Serial Advanced Technology Attachment), SSD (solid-state drive), etc. 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 disks, optical disks, floppy disks, flash memories, or forms of EPROM (electrically programmable memory) or EEPROM (electrically erasable and programmable memory). Additionally, in some examples, at least one memory (1001B) may be considered a non-transient storage medium. The term “non-transient” may indicate that the storage medium is not implemented by a carrier or propagated signal. However, the term “non-transient” should not be interpreted to mean that at least one memory (1001B) is immovable. In certain examples, the non-transient storage medium may store data that may change over time (e.g., RAM (Random Access Memory) or cache).

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

[0166] The embodiments disclosed herein may be implemented through at least one software program that is executed on at least one hardware device and performs network management functions for controlling network elements. These elements may include blocks that may be at least one of a hardware device or a combination of a hardware device and a software module.

[0167] The embodiments disclosed herein describe methods and systems for reporting a subcarrier interval (SCS) via RSSI measurements for at least one adjacent frequency and / or serving cell in wireless communication networks for wireless link failure (RLF) report(s). Accordingly, the scope of protection extends to such programs, and in addition to computer-readable means having a message, such computer-readable storage means is understood to include means of program code for implementing one or more steps of the method when the program is executed on a server, a mobile device, or a suitable programmable device. The method is implemented in at least one embodiment through or together with a software program written, for example, in VHDL (Very high speed integrated circuit Hardware Description Language) or another programming language, or by one or more VHDL or multiple software modules executed on at least one hardware device. The hardware device may be any type of portable device capable of being programmed. The device may also include means which may be a hardware means such as, for example, an ASIC, or a combination of hardware and software means such as an ASIC and an FPGA, or at least one memory in which at least one microprocessor and software modules are embedded. The method embodiments described herein may be implemented partially in hardware and partially in software. Alternatively, the present invention may be implemented on different hardware devices, for example, using a plurality of CPUs.

[0168] As the foregoing description of specific embodiments sufficiently reveals the general characteristics of the embodiments of this specification, other modifications and / or applications of these specific embodiments can be easily made to various applications without departing from the general concept by applying current knowledge, and thus such applications and modifications should be understood as being included within the meaning and scope of equivalents of the disclosed embodiments. The terms used in this specification should be understood as descriptive, not limiting. Accordingly, although the embodiments of this specification have been described through examples and illustrations, those skilled in the art will understand that the embodiments and illustrations disclosed in this specification may be modified and practiced within the scope of the embodiments as described herein.

Claims

Claim 1 A method performed by a user device (UE) in a wireless communication system, comprising: receiving setting information for reporting a received signal strength indicator (RSSI) measurement; setting adjacent frequency RSSI measurement result information based on a linear average of available RSSI sample values ​​for adjacent frequencies, wherein the adjacent frequency RSSI measurement result information includes information on the subcarrier spacing (SCS); receiving a UE information request message; and transmitting a UE information response message including the adjacent frequency RSSI measurement result information. Claim 2 A method performed by a user device (UE), wherein, in the first aspect, when the setting information is set for a frequency and SCS associated with a primary cell (PCell), the method further comprises the step of setting last serving cell RSSI measurement result information based on the linear average of available RSSI sample values ​​for the frequency of the PCell, and the UE information response message further comprises the last serving cell RSSI measurement result information. Claim 3 A method performed by a user device (UE), wherein the adjacent frequency RSSI measurement result information is included in a wireless link failure report within the UE information response message. Claim 4 A method performed by a user device (UE), wherein the adjacent frequency RSSI measurement result information is included in a successful handover report within the UE information response message. Claim 5 A method performed by a base station in a wireless communication system comprises: transmitting setting information for reporting a received signal strength indicator (RSSI) measurement of a user device (UE); transmitting a UE information request message; and receiving a UE information response message including adjacent frequency RSSI measurement result information set as a linear average of available RSSI sample values ​​for adjacent frequencies of the UE, wherein the adjacent frequency RSSI measurement result information includes information regarding a subcarrier spacing (SCS). Claim 6 A method performed by a base station, wherein, in claim 5, the UE information response message further includes last serving cell RSSI measurement result information, and when the setting information is set for the frequency and SCS associated with the primary cell (PCell), the last serving cell RSSI measurement result information is set as the linear average of the RSSI sample values ​​available for the frequency of the PCell. Claim 7 In claim 5, the method performed by the base station, wherein the adjacent frequency RSSI measurement result information is included in the wireless link failure report within the UE information response message. Claim 8 In claim 5, the method performed by the base station, wherein the adjacent frequency RSSI measurement result information is included in the successful handover report within the UE information response message. Claim 9 A user device (UE) in a wireless communication system comprises: a transceiver; and at least one processor, wherein the processor receives setting information for reporting a received signal strength indicator (RSSI) measurement through the transceiver, sets adjacent frequency RSSI measurement result information—the adjacent frequency RSSI measurement result information includes information on the subcarrier spacing (SCS)—based on a linear average of available RSSI sample values ​​for adjacent frequencies, receives a UE information request message through the transceiver, and is configured to transmit a UE information response message containing the adjacent frequency RSSI measurement result information through the transceiver. Claim 10 In claim 9, the at least one processor is further configured to set last serving cell RSSI measurement result information based on the linear average of available RSSI sample values ​​for the frequency of the PCell when the setting information is set for the frequency and SCS associated with the primary cell (PCell), and the UE information response message further includes the last serving cell RSSI measurement result information, a user device (UE) in a wireless communication system. Claim 11 In claim 9, the user device (UE) in a wireless communication system, wherein the adjacent frequency RSSI measurement result information is included in the wireless link failure report within the UE information response message. Claim 12 In claim 9, the user device (UE) in a wireless communication system, wherein the adjacent frequency RSSI measurement result information is included in the successful handover report within the UE information response message. Claim 13 A base station in a wireless communication system comprises: a transceiver; and at least one processor, wherein the processor is configured to transmit configuration information for reporting a received signal strength indicator (RSSI) measurement of a user device (UE) through the transceiver, transmit a UE information request message through the transceiver, and receive a UE information response message through the transceiver that includes adjacent frequency RSSI measurement result information set as a linear average of available RSSI sample values ​​for adjacent frequencies of the UE, wherein the adjacent frequency RSSI measurement result information includes information on a subcarrier spacing (SCS). Claim 14 A base station in a wireless communication system, wherein, in claim 13, the UE information response message further includes last serving cell RSSI measurement result information, and where the setting information is set for the frequency and SCS associated with the primary cell (PCell), the last serving cell RSSI measurement result information is set as the linear average of the RSSI sample values ​​available for the frequency of the PCell. Claim 15 In claim 13, the adjacent frequency RSSI measurement result information is included in the wireless link failure report or successful handover report within the UE information response message, in a base station in a wireless communication system.

Images