MME API for Direct Paging in Cloud Mobile Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current LTE systems face high signaling load, latency, and security vulnerabilities due to the need for rapid idle-active transitions and paging procedures, which burden core network elements and introduce latency, especially when handling push services like email notifications.
Innovation Solution
A software API-driven approach is introduced within a cloud-based MME service that controls network and bearer states, allowing for direct paging procedure triggering without involving the PGW and SGW, reducing core network involvement and enhancing security through an SSL-secured REST API.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the traditional paging procedure is used to send push notifications to idle UEs, then the network can deliver services, but the signaling load on core network elements becomes extremely high
Solution Approach 1:
The patent extracts the paging trigger function from the traditional core network flow (PGW/SGW) and relocates it to the MME. By having the MME directly trigger paging based on subscriber state and service requirements, the patent eliminates the need for PGW and SGW to handle complex paging signaling, thereby reducing core network complexity while maintaining push service delivery capability
Solution Approach 2:
The patent segments the network functions by introducing a software API layer that separates service triggering from traditional core network processing. The MME handles paging triggers independently from PGW and SGW, allowing each element to have a more focused, simpler function and reducing overall core network signaling burden
2Productivity
If the paging procedure is initiated through traditional core network elements, then push notifications can be sent, but latency is introduced in the system
Solution Approach 1:
The patent implements preliminary action by having the MME maintain subscriber state information and proactively trigger paging before data arrival. The MME pre-configures paging parameters and can immediately initiate paging procedures when push services are detected, eliminating the sequential processing delays inherent in traditional PGW-SGW-MME signaling chains
Solution Approach 2:
The patent introduces a software API-driven intermediary layer at the MME that mediates between service servers and the core network. This intermediary can directly translate service triggers into paging procedures without requiring multiple core network elements to process and forward signaling, thereby reducing latency while maintaining notification delivery
3Adaptability or versatility
If multiple core network elements handle paging signaling, then comprehensive service control is achieved, but additional latency and security vulnerabilities are introduced
Solution Approach 1:
The patent extracts the security-critical paging trigger function from the distributed core network elements (PGW/SGW) and consolidates it at the MME. By centralizing the paging initiation point at the MME, the patent reduces the attack surface and eliminates security vulnerabilities associated with multiple elements handling paging signaling, while maintaining comprehensive service control through MME's centralized subscriber state management
Solution Approach 2:
The patent changes the operational parameters of the paging procedure by shifting from a distributed triggering model (multiple core elements) to a centralized model (MME only). This parameter change in the paging initiation point consolidates security responsibilities at a single hardened function, improving reliability against denial-of-service attacks while preserving service control adaptability
Data Source
AI summary
A system and method for optimizing push services in mobile networks using a software API driven approach is provided. More particularly, an MME service is provided which includes a software API for controlling a subscriber's network and bearer states. The software API is called to trigger a paging procedure in the MME service without the interaction of the PGW and SGW, in order to move a subscriber's user equipment (UE) from an idle state to an active state. The MME service and/or the push service may be part of a cloud computing environment.