Service-Aware Lawful Interception Mediator for RCS Correlation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current lawful interception (LI) standards are not suitable for intercepting traffic at higher levels, such as Rich Communication Suite (RCS) services, due to the lack of standardization specific for each service, causing issues in differentiating signaling and content, and correlating instant message disposition notifications with related messages.
Innovation Solution
Implementing a service-aware lawful interception method that extracts LI data from communications at the network level, determines associations with services provided to LI targets, and generates service-LI messages including service-specific information to be forwarded to law enforcement agencies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If LI data is intercepted at network level for services like RCS, then interception capability is achieved, but ability to differentiate signaling and content deteriorates
Solution Approach 1:
The patent segments LI data into distinct categories (signaling vs. content) by introducing service-specific information elements that mark and organize different types of data. The mediation function separates IRI and CC into service-specific containers, enabling clear differentiation between signaling messages and content messages even when intercepted at network level.
Solution Approach 2:
The patent introduces a service-specific mediation function as an intermediary between network-level interception and LEA delivery. This mediator processes raw LI data, identifies service-specific patterns, and reformats the data with appropriate service information, thereby preserving the ability to differentiate signaling and content despite network-level interception limitations.
2Device complexity
If generic LI standards are used without service-specific standardization, then implementation complexity is reduced, but ability to correlate service-specific data deteriorates
Solution Approach 1:
The patent changes the parameter structure of LI data by adding service-specific information fields and identifiers. Service-specific IRI and CC messages include unique service identifiers, message types, and correlation fields that enable precise tracking and correlation of service-related communications without requiring complete service-level standardization.
Solution Approach 2:
The patent creates a universal framework that handles multiple service types through a common mediation function. The service-specific information structure is designed to be adaptable to different services (RCS, messaging, etc.) while using a unified interception and delivery mechanism, achieving both universality and service-specific correlation capability.
3Measurement precision
If LI is performed at application level, then service-specific information accuracy is improved, but CSP ability to alter and control interception deteriorates
Solution Approach 1:
The patent creates a copy of application-level service information within the network-level interception framework. By extracting and replicating service-specific data elements (message types, disposition notifications, correlation identifiers) from application protocols into standardized service-specific LI containers, the system achieves accurate service representation without requiring direct application-level access.
Data Source
AI summary
Methods and devices provide service-specific information besides LI data extracted from communications of LI targets, which receive services via the network and interact with a core function of the network. LI data includes at least one of IRI and CC. This approach is particularly useful if LI at application/service level is unavailable.