SCEF-ID Routing via MME Session State
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The increasing number of IoT devices in wireless communication networks burdens routing operations, particularly in scenarios where multiple Service Capability Exposure Function (SCEF) instances are deployed, leading to complexity, latency, and the need for extensive provisioning and session management.
Innovation Solution
A method utilizing a pseudo ID as a SCEF Identifier (SCEF-ID) during connection establishment, which is provisioned once by the Home Subscriber Server (HSS) and updated based on responses from SCEF instances, simplifies routing and reduces the need for multiple SCEF-IDs, thereby minimizing HSS provisioning operations and avoiding the use of session-aware routing agents.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple SCEF-IDs are provisioned for different SCEF instances, then routing can be performed, but HSS provisioning operations become extensive and complex
Solution Approach 1:
A single SCEF-ID is provisioned in the HSS that can be used for routing to multiple different SCEF instances. The MME uses this universal SCEF-ID for all connection establishment requests, and the network infrastructure routes these requests to appropriate SCEF instances based on session state, eliminating the need for multiple SCEF-IDs in HSS provisioning.
Solution Approach 2:
The MME acts as an intermediary that maintains session state information mapping the single SCEF-ID to specific SCEF instances. When routing is needed, the MME uses its stored session information to determine which SCEF instance to contact, rather than relying on multiple SCEF-IDs stored in the HSS.
2Reliability
If session-aware routing agents are used to manage multiple SCEF instances, then routing accuracy improves, but device complexity and cost increase
Solution Approach 1:
The session-aware routing functionality is extracted from a separate routing agent and integrated directly into the MME. The MME maintains the necessary session state information locally and performs routing decisions based on this information, eliminating the need for external session-aware routing agents while preserving routing accuracy.
Solution Approach 2:
The MME performs its own routing decisions using its internal session state information, rather than relying on external routing agents. The MME autonomously determines which SCEF instance to contact based on the session information it maintains, making the system self-sufficient and reducing overall infrastructure complexity.
3Reliability
If external databases are used to store session information, then session management is centralized, but cost and complexity increase
Solution Approach 1:
The session information storage functionality is merged with the MME itself rather than being separated into an external database. The MME maintains session state information in its own memory, combining the routing decision-making and session information storage functions into a single component, thereby eliminating external database requirements.
Solution Approach 2:
The MME performs multiple functions including session management, routing decisions, and information storage locally. By making the MME a multi-functional component that handles both routing and session state maintenance, the system eliminates the need for separate external database infrastructure.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A carrier network may provide connection establishment and routing optimization for Service Capability Exposure Function (SCEF). For example, a Mobility Management Entity (MME) component may transmit, to a SCEF, a connection request to establish a session, the request using a first SCEF identifier (ID). The MME may receive, from a particular SCEF instance of the SCEF, an answer for the session, the answer including an identifier that is different from the first SCEF-ID, the identifier associated with the particular SCEF instance. The MME may transmit, to the particular SCEF instance, a subsequent message for the session, wherein a second SCEF-ID of the subsequent message is associated with the identifier and is different from the first SCEF-ID.