RAN Link Generation Using Cell Fragments for CDR Correlation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing RAN parsers are limited by vendor and technology-specific architectures, requiring centralized deployment and lacking flexibility in processing and distributing network data, which hinders efficient call detail record generation and real-time geolocation insights.

Innovation Solution

A Cloud Native Parser architecture that enables vendor/technology-agnostic link generation service, allowing deployment at the edge or central locations, and uses unique session identifiers to link messages from different interfaces into cell fragments, enhancing flexibility and efficiency in generating call data records.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If vendor and technology-specific architectures are used, then network data processing is achieved, but deployment flexibility and adaptability are reduced

Engineering Contradiction:
Improvedeployment flexibilityVSAvoidarchitecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal link generation service that can process messages from multiple vendors and technologies (2G, 3G, 4G, 5G) through a single standardized interface. The service uses common fields like fragment_id_1 and fragment_id_2 across different message types, allowing one system to handle diverse network data without requiring vendor-specific processing logic, thereby achieving deployment flexibility while reducing architectural complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Productivity

If centralized deployment is required, then system control is maintained, but processing efficiency and real-time capabilities are reduced

Engineering Contradiction:
Improvecall data record generation efficiencyVSAvoiddeployment flexibility
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent segments the RAN parser into distributed microservices that can be deployed at edge locations and central locations independently. The link generation service operates as a standalone microservice that can be instantiated anywhere in the network, processing messages locally at edge devices while maintaining the ability to centralize control when needed. This segmentation enables parallel processing and real-time operations without requiring centralized deployment.

Inventive Principle:
Principle #1Segmentation

3Manufacturing precision

If messages from different interfaces are not linked, then processing simplicity is maintained, but call detail record generation accuracy is reduced

Engineering Contradiction:
Improvecall detail record generation accuracyVSAvoidmessage linking complexity
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The patent introduces fragment_id_1 and fragment_id_2 as intermediary fields that serve as universal keys to link messages from different interfaces and network elements. These fields act as mediators that correlate messages across RRC, X2AP, and S1AP interfaces, enabling accurate call detail record generation without requiring complex correlation algorithms. The intermediary fields simplify the linking process by providing direct correlation keys that work across all message types and interfaces.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP4336783B1Link generation for ran parser
Publication Date: 2026.04.08 TC FRANCE SAS
  • EP4336783B1 patent drawingFigure 1
  • EP4336783B1 patent drawingFigure 2~3
  • EP4336783B1 patent drawingFigure 4~5

AI summary

A method (100) accessing (102) messages stored in a publishing system, wherein the messages are derived from Call Trace messages and are stored in a vendor and technology agnostic manner; starting (104) a cell fragment based on a starting type message for a call; linking (106) associated messages for the call to the cell fragment; ending (108) the cell fragment based on an ending type message for the call; and utilizing (110) the cell fragment for creating a Call Data Record (CDR) of the call.