MME with MSC Functionality for SMS and M2M Signaling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current wireless communication systems inadequately support Short Messaging Service (SMS) and Machine-to-Machine (M2M) communications, particularly due to duplication of Mobility Management signaling and requirement for CS subscription and MSC Server function, which are undesirable for MSISDN-less and PS-only communication.
Innovation Solution
A Mobility Management Entity (MME) is defined to perform combined Packet Switched (PS) and Circuit Switched (CS) location updates over a single interface, merging MSC Server functionality into the MME and using a Diameter interface for SMS forwarding, eliminating the need for Service Gateways and reducing MM signaling duplication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If separate PS and CS location update procedures are used, then compatibility with existing networks is maintained, but signaling duplication and network complexity increase
Solution Approach 1:
The patent combines separate PS (Packet Switched) and CS (Circuit Switched) location update procedures into a single unified location update message. This merging eliminates redundant signaling between the MME and HSS/HLR, reducing network complexity while maintaining compatibility with existing networks that support both PS and CS domains.
Solution Approach 2:
The unified location update procedure serves multiple functions simultaneously: it performs both PS location registration and CS location registration in a single message exchange. This multi-functional approach allows the system to maintain compatibility with legacy networks while optimizing signaling efficiency for modern PS-only operations.
2Adaptability or versatility
If MSC Server function and Service Gateway are used for SMS support, then SMS functionality is provided, but network complexity and subscription requirements increase
Solution Approach 1:
The patent merges MSC Server functionality directly into the MME (Mobility Management Entity), creating a combined entity that handles both mobility management and SMS routing functions. This integration eliminates the need for separate Service Gateways and reduces network architecture complexity while maintaining full SMS support capabilities.
Solution Approach 2:
The patent extracts the essential SMS support functionality from the complex MSC Server and Service Gateway infrastructure and integrates it directly into the MME. This extraction allows SMS functionality to be provided with a simplified architecture, eliminating unnecessary network elements for PS-only subscriptions.
3Reliability
If CS subscription is required for SMS, then SMS delivery is ensured, but flexibility for PS-only communication is reduced
Solution Approach 1:
The unified MME with integrated MSC functionality provides universal support for both CS-based SMS and PS-based SMS delivery mechanisms. This allows the system to maintain reliable SMS delivery while offering flexible subscription options, enabling users to choose PS-only subscriptions without sacrificing SMS capability.
Data Source
Figure 1~2
Figure 3~4
Figure 5
AI summary
A Mobility Management Entity (MME) comprises at least one entity or layer having Mobile Switching Center (MSC) functionality to support a Short Messaging Service (SMS) between a network and a mobile station by employing Machine-to-Machine (M2M) or Machine Type Communication (MTC) protocols. A first state machine entity or layer that supports relay functions to perform forwarding of SMS messages to the mobile station. A second state machine entity or layer that supports connection functions with at least an HSS/HLR (Home Subscriber Server / Home Location Register), and with an SMS-SC (Short Messaging Service -Service Center) or GMSC/IWMSC (Gateway MSC / Interworking MSC).