Edge Service Deployment via Network Slice Invocation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current edge computing systems face challenges in efficiently deploying and managing edge services across networks, particularly in 5G environments, leading to increased latency and bandwidth costs due to the need for centralized data processing and storage, which can be exacerbated by the growing number of IoT devices.
Innovation Solution
A computer program product and method that facilitates edge service deployment by obtaining service-related parameters for network slice invocation, requesting a network slice through a collaboration platform, and activating an edge service instance using network slice invocation codes, allowing for efficient cloning and scaling of edge services to match bandwidth provisions in the 5G network.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If data processing and storage are centralized in cloud servers, then service management is simplified, but latency increases and bandwidth costs increase
Solution Approach 1:
The patent segments the centralized cloud service into distributed edge service instances deployed across multiple edge locations. Each edge instance independently processes data locally, eliminating the need for all data to travel to central cloud servers. This segmentation reduces latency while maintaining simplified management through automated deployment mechanisms.
Solution Approach 2:
The patent introduces a new dimensional approach by deploying services across the edge network infrastructure rather than relying solely on vertical scaling of central cloud resources. This spatial distribution across multiple edge locations creates a new dimension for service delivery that simultaneously reduces latency and maintains management simplicity through standardized deployment procedures.
2Loss of time
If edge service instances are deployed across multiple locations, then latency is reduced, but deployment complexity and resource management difficulty increase
Solution Approach 1:
The patent creates a universal deployment mechanism that handles multiple edge locations through a single standardized process. The service deployment system can instantiate identical service configurations across numerous edge locations simultaneously, making the deployment process location-agnostic and reducing complexity despite the distributed nature of the infrastructure.
Solution Approach 2:
The patent employs copying mechanisms to replicate service configurations and instances across edge locations. Rather than manually configuring each edge instance, the system creates copies of standardized service templates and deploys them automatically to multiple locations, significantly reducing deployment complexity while maintaining consistency across the distributed infrastructure.
3Productivity
If more edge service instances are deployed to handle increased IoT device connections, then network capacity increases, but bandwidth costs and resource consumption increase
Solution Approach 1:
The patent implements self-service mechanisms where edge service instances autonomously manage their own resource allocation and optimization. Each edge instance can independently adjust its resource consumption based on local demand conditions, eliminating the need for over-provisioning and reducing overall bandwidth costs while maintaining adequate network capacity to handle IoT device connections.
Data Source
AI summary
Edge service deployment with network slice invocation is provided, which includes obtaining one or more service-related parameters for network slice invocation to support an edge service instance, and requesting a network slice from a network based on the obtained one or more service-related parameters. The requesting from the network is via a collaboration platform. Further, the edge service deployment and network slice invocation includes receiving from the network, based on requesting of the network slice, network slice invocation codes, and initiating activating of the edge service instance over the network slice of the network using the network slice invocation codes.