MEC Control Plane Segmentation for Low Latency IoT
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current IoT data transmission systems, especially those using Multi-access Edge Computing (MEC) platforms, face challenges in achieving low latency for short data segments due to control plane signaling that routes packets away from network edges to core devices, limiting the benefits of edge computing.
Innovation Solution
Implementing a localized control plane function at the MEC edge for short data transmissions, allowing non-IP communications and dedicated traffic-type identifiers like PLMN-ID, with a mobility management entity function instantiated at the edge to support a short data, low latency service, enabling control plane communications to reside entirely on the local MEC platform after initial authentication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If control plane signaling is used to transmit short IoT data segments, then device compatibility and network management are maintained, but latency increases due to routing packets away from network edges to core devices
Solution Approach 1:
The patent segments the control plane function into two parts: authentication/registration functions remain in the core network, while data transmission functions are localized at the MEC edge. This allows short data segments to be transmitted locally without routing to core devices, reducing latency while maintaining core network management capabilities.
Solution Approach 2:
The patent introduces a localized control plane function at the MEC edge that acts as an intermediary between IoT devices and the core network. This intermediary handles short data transmissions locally, eliminating the need to route packets to core devices while maintaining compatibility with existing core network protocols and authentication mechanisms.
2Device complexity
If data transmissions are routed through core network devices, then network management and authentication are simplified, but the benefits of edge computing are limited due to increased latency
Solution Approach 1:
The patent applies local quality by implementing control plane functions specifically at the MEC edge location where IoT devices connect. This localized implementation provides low-latency data transmission for edge devices while the core network continues to handle authentication and overall network management, optimizing both local performance and centralized control.
Solution Approach 2:
The patent adds a new dimensional layer to the network architecture by instantiating control plane functions at the MEC edge in addition to core network functions. This creates a multi-layered control plane where edge-level functions handle local transmissions and core-level functions handle authentication and management, enabling simultaneous optimization of latency and network control.
3Speed
If MEC platforms are used for IoT data transmission, then low latency is achieved for data processing, but control plane signaling routes packets away from network edges, limiting edge computing benefits
Solution Approach 1:
The patent merges the control plane and user plane functions at the MEC edge for short data transmissions. By combining authentication, registration, and data transmission functions in a single localized control plane function, the system eliminates the need to route control packets to core network devices, thereby maintaining the low latency benefits of MEC while enabling efficient short data transmission.
Data Source
AI summary
Systems and methods provide a short data, low latency service using a Multi-access Edge Computing (MEC) network. A network device receives, in a core network, an attach request from an end device and detect whether a packet size range for data transmissions from the end device is within a configured size threshold. The network device directs, when the packet size is within the configured size threshold, routing of the data transmissions via a control plane function of an edge network to a local instance of an application server in the edge network. The network device directs, when the packet size is over the configured size threshold, routing of the data transmissions via a user plane function of the edge network to a local instance of an application server in the edge network.