Conditional CEF Report Lists for Duplicate Failure Filtering

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current communication systems face issues with duplicate Connection Establishment Failure (CEF) reports being sent to the network, leading to incorrect coverage analysis due to the lack of proper handling of CEF report lists, which can result in exaggerated coverage hole issues.

Innovation Solution

Implement methods at both the UE and network node levels to identify and discard or flag duplicate CEF reports, ensuring that only unique reports are sent to the network, either by comparing CEF report content with the CEF report list or by using a retainability timer to manage CEF reports for the same cell.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If the UE sends both CEF report and CEF report list to the network, then complete failure information is provided, but duplicate information is reported leading to incorrect coverage analysis

Engineering Contradiction:
ImproveCEF information completenessVSAvoidcoverage analysis accuracy
Core Design Contradiction:
Loss of informationVSMeasurement precision

Solution Approach 1:

The network node performs preliminary comparison between the CEF report and CEF report list before processing. By checking for duplicates in advance using cell identity and failure cause comparisons, the network node prevents duplicate information from being included in coverage analysis, thus resolving the contradiction between providing complete information and maintaining analysis accuracy

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism where the network node identifies duplicate CEF reports through comparison of cell identity and failure cause, then excludes these duplicates from coverage analysis. This feedback loop ensures that only unique CEF information contributes to coverage hole detection, maintaining measurement precision while still receiving comprehensive reporting from the UE

Inventive Principle:
Principle #23Feedback

2Loss of information

If the UE logs multiple CEF reports in VarConnEstFailReportList, then comprehensive failure data is stored, but duplicate reports increase signaling overhead

Engineering Contradiction:
ImproveCEF report data completenessVSAvoidsignaling overhead
Core Design Contradiction:
Loss of informationVSQuantity of substance

Solution Approach 1:

The network node performs preliminary filtering by comparing the standalone CEF report with entries in the CEF report list before processing. By identifying and flagging duplicates based on cell identity and failure cause matching, the system reduces the quantity of unique CEF reports that need further processing, thereby reducing signaling overhead while preserving complete failure data

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system discards duplicate CEF reports identified through comparison of cell identity and failure cause between the CEF report and CEF report list. By removing these redundant copies, the system recovers signaling resources while maintaining complete failure information through the retained unique reports, thus resolving the contradiction between data completeness and overhead reduction

Inventive Principle:
Principle #34Discarding and recovering

Data Source

PatentUS20250254547A1Conditional connection establishment failure (CEF) report list
Publication Date: 2025.08.07 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US20250254547A1 patent drawing
  • US20250254547A1 patent drawing
  • US20250254547A1 patent drawing

AI summary

A method performed in a user equipment, UE includes responsive to experiencing a first connection establishment failure, CEF, logging information related to the first CEF as part of a CEF report. The method includes experiencing a second CEF. The method includes responsive to the second CEF occurring in a different cell than a cell where the first CEF occurred: logging the CEF report as an entry of a CEF report list; and updating the CEF report with information associated with the second CEF.