IMS-SCP Trigger Management for Roaming Call Normalization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Modern cellular communication networks face challenges in managing roaming calls between different communication providers, particularly in normalizing and charging for international calls, where existing systems often result in errors due to missing country codes and inadequate real-time charging mechanisms.
Innovation Solution
The implementation of an IMS-SCP module that performs trigger management between VAS and charging platforms, utilizing native interfaces like REST, CAMEL, and Diameter, to normalize called numbers, manage sessions, and facilitate correct charging, while allowing customizable invocation sequences and error handling.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional roaming call management systems are used, then basic call connectivity is maintained, but errors occur due to missing country codes and inadequate real-time charging mechanisms
Solution Approach 1:
The system performs preliminary normalization of the called number by detecting the roaming location and adding the appropriate country code before the call is routed. This preliminary action ensures that the complete and accurate number is available for subsequent charging and routing operations, preventing errors caused by missing country code information.
2Reliability
If sequential processing of normalization and charging platforms is used, then correct charging is achieved, but call setup time increases
Solution Approach 1:
The system dynamically adjusts the processing sequence based on the specific call scenario and service requirements. The trigger management functionality can invoke the normalization platform first for certain call types, or the charging platform first for others, optimizing the balance between charging accuracy and call setup time according to real-time conditions.
Solution Approach 2:
The call processing is segmented into independent normalization and charging operations, each triggered separately by the IMS-SCP. This segmentation allows the system to manage the complexity of sequential processing while maintaining the ability to optimize the sequence dynamically, preventing the operations from becoming a monolithic bottleneck.
3Device complexity
If feature platforms are invoked in fixed sequences, then system control is simplified, but adaptability to different service requirements is reduced
Solution Approach 1:
The trigger management system is designed to be dynamic rather than static. The IMS-SCP can adapt the invocation sequence of feature platforms based on service-specific requirements, caller profiles, and real-time network conditions. This dynamic capability allows the system to maintain simplified control logic while achieving high adaptability to different service scenarios.
Data Source
AI summary
An IP Multimedia Subsystem Service Control Point (IMS-SCP) module of a carrier network may provide trigger management for a request for a circuit switched (CS) call. For example, an IMS-SCP module may receive an request for a CS call associated with a user equipment. The IMS-SCP module may determine handling of the request for the CS call includes one or more first operations by a first feature platform and one or more second operations by a second feature platform. In response to the determining, the IMS-SCP module may perform trigger management associated with the request for the CS call. The trigger management may include invoking, by the IMS-SCP module, the one or more first operations of the first feature platform and, subsequent to the invoking the one or more first operations, invoking the one or more second operations of the second feature platform.