Push Notification Delivery for Quota Exhaustion Alerts
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing solutions for quota exhaustion notifications in mobile networks, such as HTTP redirection and SMS messages, are ineffective due to encryption issues and user indifference, leading to unnoticed or ignored notifications.
Innovation Solution
A method for handling user notifications in communications networks using push notifications, where a Network Exposure Function (NEF) or Mobile Network Operator Application Function (MNO AF) transmits quota exhaustion alerts to user equipment, including a URL and notification text, ensuring users are informed of quota status and can refill as needed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If HTTP redirection is used for quota exhaustion notifications, then users can be redirected to refill services, but the solution fails when traffic is encrypted because HTTP headers are not visible
Solution Approach 1:
The patent introduces a push server as an intermediary component that receives notifications from the charging function and delivers them to user equipment through push notification technology. This mediator bypasses the encryption limitation by using a different communication channel (push notifications) that works with encrypted traffic, while the charging function and user equipment remain unchanged.
Solution Approach 2:
The patent replaces the HTTP redirection mechanism (application-level request manipulation) with push notification technology (system-level notification delivery). This substitution moves from manipulating HTTP headers in encrypted traffic to using a separate notification channel that is independent of the encrypted data flow.
2Reliability
If SMS messages are used for quota exhaustion notifications, then users can be made aware of quota status, but users may ignore or confuse these messages with spam
Solution Approach 1:
The push server acts as an intermediary that delivers notifications through the operator's application interface, creating a trusted channel between the network and the user. This intermediary ensures that notifications appear within the context of applications the user actively uses, rather than as separate SMS messages that can be easily ignored or mistaken for spam.
Solution Approach 2:
The patent changes the 'color' or form of the notification from SMS text messages to push notifications displayed within application interfaces. This visual and contextual transformation makes the notifications more recognizable as legitimate operator communications rather than spam, improving user response effectiveness.
3Ease of operation
If push notifications are used for quota exhaustion alerts, then users receive timely notifications through their devices, but requires integration with operator's application infrastructure
Solution Approach 1:
The push server provides a universal notification service that can handle multiple types of notifications (quota exhaustion, service alerts, etc.) through a single infrastructure. This multi-functional approach simplifies the overall system architecture by consolidating notification delivery across different scenarios into one standardized mechanism.
Solution Approach 2:
The system enables self-service by allowing the push server to automatically select appropriate notification types based on the notification content and user preferences. The charging function simply sends notifications to the push server, which then autonomously determines the best delivery method without requiring complex configuration or manual intervention.
Data Source
AI summary
A method for handling user notifications in a communications network. The method comprises receiving an indication that a second entity supports a user notification type; determining that a user notification of the user notification type shall be transmitted to the second entity, the user notification comprising a user identity and a notification content; selecting the second entity for delivering the user notification of the user notification type to the user; and transmitting to the second entity the user notification including the user identity and the notification content. The method may be performed by a Network Exposure Function (NEF), a Service Capability Exposure Function (SCEF), a Policy Control Function (PCF), a Policy and Charging Rules Function (PCRF), a Charging Function (CHF), or an Online Charging System (OCS). The second entity may be an application server, particularly a push notification server or a Service Capability Server (SCS), or a or a Mobile Network Operator Application Function, MNO AF.


