Message Broker Replay Agent for Charging Event Recovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Charging event messages are lost when a charging server in a 3GPP network becomes temporarily unavailable, leading to potential revenue loss for network operators.
Innovation Solution
A system utilizing a message broker and a replay agent to store charging event messages in persistent storage and deliver them to the charging server when it becomes available, supporting multiple protocols and scalability to handle different types of charging events.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If charging event messages are sent directly to the charging server without persistent storage, then the system operates with simple architecture and fast processing, but charging event messages are lost when the charging server becomes temporarily unavailable
Solution Approach 1:
The message broker performs preliminary action by storing charging event messages in persistent storage before the charging server is available to receive them. This ensures messages are preserved and not lost during server unavailability, resolving the contradiction between reliability and simplicity by adding a buffer layer that automatically handles message persistence.
Solution Approach 2:
The message broker acts as an intermediary component between the network element and the charging server. It receives charging event messages, stores them persistently, and forwards them when the server is available, thereby improving reliability without requiring complex changes to the core charging server architecture.
2Reliability
If a replay agent with persistent storage is added to preserve charging event messages, then message delivery reliability improves, but the system requires additional components and operational complexity
Solution Approach 1:
The replay agent implements self-service by automatically monitoring the persistent storage for charging event messages, retrieving them when the charging server becomes available, and forwarding them without requiring manual intervention. This automation maintains reliability while minimizing operational complexity.
Solution Approach 2:
The system implements feedback mechanisms where the replay agent continuously monitors server availability and adjusts its message forwarding behavior accordingly. When the server is unavailable, messages remain in persistent storage; when available, messages are automatically forwarded, creating a self-regulating operation that simplifies system management.
3Adaptability or versatility
If multiple protocols are supported for different charging servers, then system versatility improves, but the complexity of protocol handling and message routing increases
Solution Approach 1:
The message broker is designed with multi-functionality to support multiple communication protocols (e.g., HTTP, MQTT, AMQP) simultaneously. It can adapt to different charging server requirements without requiring separate specialized components for each protocol, thereby achieving versatility while managing complexity through a unified platform.
Solution Approach 2:
The system uses parameter changes to handle different protocols by configuring message broker instances with protocol-specific parameters. This allows the same core architecture to adapt to various protocols by changing configuration parameters rather than requiring fundamentally different system designs, maintaining versatility while controlling complexity.
Data Source
Figure 1
Figure 2A
Figure 2B
AI summary
A system for preserving charging event messages in a mobile telecommunications network when a charging server is unavailable includes a message broker comprising persistent storage. The system also includes a network element that generates a charging event message, attempts to send the charging event message to a charging server, and writes the charging event message to the message broker in response to determining that the attempt to send the charging event message to the charging server has failed. The system also includes a replay agent that subscribes to the message broker for notifications associated with the charging server, receives a notification from the message broker about the charging event message, reads the charging event message from the message broker, and causes the charging event message to be sent to the charging server when the charging server is available.