Network Resource Orchestrator for Edge Server Connectivity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing telecommunications network infrastructure struggles to ensure satisfactory connectivity between servers allocated for virtualized network functions, particularly in edge computing environments where resources are limited, and previous orchestrators cannot guarantee the quality of network service between servers.

Innovation Solution

A resource allocation process that includes a resource orchestrator receiving a request for virtualized function instantiation, determining suitable servers and network resources for connectivity, emitting configuration requests for network infrastructure resources, and issuing requests for IT resource allocation on determined servers to ensure connectivity meets the instantiation requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If network functions are distributed to edge data centers to meet latency constraints, then service quality for end users is improved, but network connectivity between allocated servers cannot be guaranteed

Engineering Contradiction:
ImprovelatencyVSAvoidnetwork connectivity
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The orchestrator performs preliminary determination of network infrastructure resources that enable connectivity between servers before allocating servers for virtualized function instantiation. This advance planning ensures that connectivity requirements are satisfied before deployment, resolving the contradiction by proactively addressing network connectivity in edge distributed scenarios

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The orchestrator acts as an intermediary between server allocation and network connectivity assurance. It receives instantiation requests, determines both servers and network resources, transmits configuration requests to ensure connectivity, and then allocates computing resources. This intermediary role guarantees that distributed edge servers maintain satisfactory network connectivity

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If orchestrators allocate servers based on computing power and storage capacity, then resource utilization is optimized, but connectivity quality between servers cannot be verified or guaranteed

Engineering Contradiction:
Improveresource utilizationVSAvoidconnectivity quality
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The orchestrator determines network infrastructure resources enabling connectivity between servers before finalizing server allocation. This preliminary action ensures connectivity quality is guaranteed while maintaining optimized resource utilization based on computing power and storage capacity requirements

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The orchestrator transmits configuration requests to determined network resources to ensure connectivity between allocated servers. This feedback mechanism verifies and guarantees connectivity quality, resolving the contradiction by adding connectivity verification to the existing resource optimization process

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP3991356B1Method for allocating resources of a network infrastructure
Publication Date: 2025.04.16 ORANGE SA
  • EP3991356B1 patent drawingFigure 1~2
  • EP3991356B1 patent drawingFigure 3
  • EP3991356B1 patent drawingFigure 4

AI summary

The invention relates to a method for allocating resources of a network infrastructure for the provision of a telecommunication service. The method comprises: - receiving (107, 207), by a resource orchestrator (102, 202), a request to instantiate virtualised functions on servers; - determining (108, 208) servers to be allocated (104, 204) and network infrastructure resources allowing the connectivity between said servers in accordance with the instantiation request (107, 207); - sending, to the determined resources, a configuration request (113, 211) allowing the connectivity between the determined servers (104, 204); - sending, to the determined servers, a request for allocation of computing means on the determined servers (111, 210).