Edge Computing Network Deployment for 5G Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current edge computing network deployments in 5G systems face challenges in efficiently managing deployment requirements, including service area, quality of service, and software image information for edge application servers, edge enabling servers, and edge configuration servers, which are crucial for effective virtual network function instantiation.

Innovation Solution

The implementation of specific information models and operations, such as EASRequirements, EESFunction, and ECSFunction, within the edge computing service provider management system to capture and process deployment requirements like geographical and topological locations, software image details, and quality of service parameters, enabling precise instantiation of virtual network functions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If comprehensive deployment requirements information models are implemented to capture service area, QoS, and software image information, then deployment accuracy and service quality are improved, but system complexity and implementation difficulty increase

Engineering Contradiction:
Improvedeployment accuracyVSAvoidsystem complexity
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The deployment requirements information model is segmented into distinct components: service area requirements (geographical coordinates, civic locations, topological service areas), QoS requirements (bandwidth, latency, jitter), and software image information (storage, memory, processing requirements). This segmentation allows each aspect to be managed independently while maintaining overall deployment accuracy without overwhelming system complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The ECSP management system acts as an intermediary that receives deployment requests from ASPs, processes them through standardized information models, and translates them into actionable deployment configurations. This intermediary layer simplifies the interface between service providers and the deployment infrastructure, reducing implementation difficulty while maintaining precision.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Area of stationary object

If specific information models like EASRequirements, EESFunction, and ECSFunction are implemented to capture detailed deployment parameters, then service area coverage and QoS are improved, but information management complexity increases

Engineering Contradiction:
Improveservice area coverageVSAvoidinformation management complexity
Core Design Contradiction:
Area of stationary objectVSLoss of information

Solution Approach 1:

The information models are designed with universal structures that can accommodate multiple types of service area definitions (geographical, civic, topological) and various QoS parameters within a unified framework. The EASRequirements, EESFunction, and ECSFunction models share common attributes and relationships, allowing them to be managed consistently across different deployment scenarios without increasing information management complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The information models utilize parameterized structures where deployment requirements are defined as configurable parameters rather than fixed values. This allows the same model structure to adapt to different service areas and QoS requirements by simply changing parameter values, rather than creating separate complex models for each scenario.

Inventive Principle:
Principle #35Parameter changes

3Measurement precision

If comprehensive software image information including minimum disk, RAM, and role attributes is captured, then VNF instantiation accuracy is improved, but data collection and processing overhead increase

Engineering Contradiction:
ImproveVNF instantiation accuracyVSAvoiddata collection time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

Software image information requirements are determined and specified in advance during the service deployment planning phase. The minimum disk, RAM, and role attributes are pre-defined based on the VNF type and service requirements, eliminating the need for time-consuming on-site assessments or iterative adjustments during actual instantiation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Software image requirements are captured as standardized data templates that can be replicated and reused across multiple deployments. Once the minimum disk, RAM, and role attributes are defined for a particular VNF type, this information can be copied and applied to multiple instances, significantly reducing data collection time while maintaining high instantiation accuracy.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS20240259277A1Edge computing network deployment for fifth-generation (5G) systems
Publication Date: 2024.08.01 INTEL CORP
  • US20240259277A1 patent drawing
  • US20240259277A1 patent drawing
  • US20240259277A1 patent drawing

AI summary

Various embodiments herein may relate to edge computing network deployments, and in particular, some embodiments may be directed to instantiating edge application server (EAS) virtual network functions (VNFs). An edge computing service provider (ECSP) management system is to: receive a request for instantiation of a virtual network function (VNF) that includes deployment requirements comprising software image information associated with the instantiation of the VNF; and instantiate the VNF based on the deployment requirements.