SDN Controller for IoT IP Service Provisioning in Cellular Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current cellular network architectures face significant challenges in provisioning Internet Protocol (IP) services for a large number of devices, particularly IoT devices, due to high signaling overhead and resource consumption, which is wasteful for devices that do not require constant connectivity.
Innovation Solution
The proposed solution involves a Software Defined Networking (SDN) architecture that separates control plane and user plane entities, allowing for tunnel-less transmission of IP services, preconfiguration of IP address pools, and dynamic allocation of IP addresses and routing policies to reduce messaging overhead and resource usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional GTP-based IP service provisioning is used for multiple UEs, then IP services can be delivered to user equipment, but signaling overhead and resource consumption in the EPC become significant
Solution Approach 1:
The patent segments the IP service provisioning process by introducing a network controller that handles control plane functions separately from the user plane. This segmentation allows multiple UEs to share common IP address pools and routing policies, reducing redundant signaling in the EPC while maintaining reliable IP service delivery to each UE.
Solution Approach 2:
The patent implements preconfiguration of IP address pools and routing policies in the network controller before UEs need services. This preliminary action enables rapid service provisioning without extensive real-time signaling overhead, as the controller can allocate pre-prepared IP addresses and policies to UEs on demand.
2Adaptability or versatility
If traditional session setup procedure is used for each UE, then IP services can be provisioned individually, but messaging overhead increases significantly for large numbers of devices
Solution Approach 1:
The patent merges the provisioning of common parameters (IP address pools, routing policies) across multiple UEs through the network controller. Instead of establishing separate complete session contexts in the EPC for each UE, the controller manages shared resources that serve multiple UEs simultaneously, reducing the quantity of messaging overhead while maintaining individual service adaptability.
Solution Approach 2:
The network controller is designed as a universal entity that handles IP service provisioning for multiple different UEs with diverse requirements. It maintains multiple IP address pools and routing policies that can be dynamically allocated to different UEs, providing individualized service provisioning through a single multi-functional controller rather than dedicated EPC sessions for each UE.
3Reliability
If always-on connection is maintained for IoT devices, then IP services are continuously available, but compute and energy resources are wasted for devices that transmit infrequently
Solution Approach 1:
The patent implements periodic or on-demand connection establishment for IoT devices through the network controller. Instead of maintaining always-on connections, the controller enables UEs to establish connections periodically or when data transmission is needed, using preconfigured IP address pools for rapid reconnection. This reduces energy consumption at both device and network levels while maintaining service availability when needed.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Methods and apparatus are described by which a network controller receives an attach request from a first user equipment (UE). The attach request including a requested IP service. A group of IP addresses for the IP service is allocated. A routing policy is configured for the group of IP addresses. The routing policy is sent to a RAN node and a data gateway. The routing policy indicates a route for data packets, from UEs using the requested IP service, received at the RAN node to the data gateway. A mapping between the service identifier and the group of IP addresses is stored.