IoT Service Activation via Edge-Deployed Software Containers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for providing resources to IoT devices rely on central cloud NFV, which leads to management overhead and inefficiencies, especially in scenarios requiring services at the network edge and during roaming.
Innovation Solution
Implementing a geographically optimal mechanism using Mobile Edge Computing (MEC) that allows IoT devices to dynamically request and activate services via software containers, such as Docker, which are deployed at the network edge, reducing reliance on central cloud resources and enabling low-latency service delivery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If resource delivery is masterminded by a central entity (NFV enabled operator), then resource provisioning can be standardized, but management overhead increases and service latency increases
Solution Approach 1:
The patent segments the centralized resource delivery function into distributed edge components. Instead of a single central NFV entity, multiple edge computing platforms are deployed at network edges, each capable of independent resource provisioning. This segmentation reduces latency by placing resources closer to IoT devices while maintaining standardized provisioning through containerization technologies.
Solution Approach 2:
The patent introduces a new architectural dimension by deploying edge computing platforms at multiple geographic locations throughout the network. This transforms the traditional single-point centralized provisioning model into a multi-dimensional distributed architecture, where resources can be delivered from the nearest edge platform, reducing latency while maintaining operational simplicity through standardized container interfaces.
2Device complexity
If services are pushed/provisioned from central cloud to IoT devices, then resource management is simplified, but unnecessary management overhead is created
Solution Approach 1:
The patent implements self-service mechanisms where edge computing platforms automatically discover IoT devices and push appropriate services without requiring complex centralized orchestration. The edge platforms autonomously manage service lifecycle, including deployment, monitoring, and updates, significantly reducing management overhead while maintaining simplicity through standardized container interfaces.
Solution Approach 2:
The patent pre-configures service containers at edge computing platforms before they are needed. When IoT devices connect to the network, services are already prepared and can be immediately pushed or activated, eliminating the need for complex real-time provisioning decisions from central cloud and reducing management overhead.
3Device complexity
If centralized NFV is used for resource delivery, then resource orchestration is simplified, but it does not work well in roaming scenarios
Solution Approach 1:
The patent segments the resource orchestration function across multiple edge computing platforms distributed throughout the network. Each edge platform independently manages local IoT devices, enabling seamless roaming support. When devices move between network areas, they can continue accessing services from the nearest edge platform without requiring complex centralized re-orchestration.
Solution Approach 2:
The patent changes the operational parameters of resource delivery by transitioning from centralized control to distributed edge-based control. This parameter change enables the system to adapt dynamically to roaming scenarios, where devices may move between different network operators or geographic regions, while maintaining simplified orchestration through standardized container interfaces at each edge location.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The embodiments herein relate to methods and apparatuses for activating or running services or resources requested by an loT device (400). The loT device (400) requests attachment to a mobile network by sending a request to core network which confirms said attachment. The loT device (400) then transmit a software/data container to the core network, the container comprises features/functions needed for running the requested resource/service. A network edge device then sets up the resource/service enabling the loT device (400) to run the service/resource provided the core network validates the software/data container. There is also provided a network edge device (600) and a core network.