Managing Node Function Placement to Reduce Remote Call Latency

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Remote communications between functions in a dis-aggregated architecture are slow and prone to failures, especially when traversing container, cluster, or domain boundaries, due to serialization, inter-process communication, context switching, and resource-intensive mechanisms.

Innovation Solution

A mechanism that involves a managing node obtaining and analyzing measured parameters of communications between functions to dynamically update the deployment packaging, co-locating functions in shared memory spaces to reduce remote calls and optimize resource usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If functions are deployed in a dis-aggregated architecture across container, cluster, or domain boundaries, then service flexibility and modularity are improved, but communication speed and reliability deteriorate due to serialization, inter-process communication overhead, and context switching

Engineering Contradiction:

Improveservice flexibilityVSAvoidcommunication speed

Core Design Contradiction:

Adaptability or versatilityVSSpeed

Solution Approach 1:

The patent segments functions into deployable units that can be dynamically placed and managed. The system divides the service architecture into independent function units that can be deployed across different containers, clusters, or domains, enabling flexible service composition while maintaining manageable deployment units.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces a managing node as an intermediary that coordinates communication and deployment between distributed functions. This mediator optimizes function placement and manages inter-function communication, reducing the overhead of direct remote communications across distributed boundaries.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If functions are deployed in a dis-aggregated architecture, then service modularity is improved, but communication reliability deteriorates due to remote call failures and traversal issues

Engineering Contradiction:

Improveservice modularityVSAvoidcommunication reliability

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements dynamic function placement and deployment strategies where the managing node can relocate functions based on communication patterns, load conditions, and reliability requirements. This dynamic adjustment optimizes both modularity benefits and communication reliability by adapting the deployment architecture to actual runtime conditions.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system incorporates feedback mechanisms where communication performance and reliability metrics are monitored and fed back to the managing node. This feedback enables the managing node to make informed decisions about function placement, deployment packaging updates, and resource allocation to improve communication reliability while maintaining modularity.

Inventive Principle:

Principle #23Feedback

3Productivity

If functions are co-located in shared memory spaces, then communication latency is reduced and throughput increases, but deployment complexity and resource management difficulty increase

Engineering Contradiction:

ImprovethroughputVSAvoiddeployment complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The patent implements self-service mechanisms where functions can autonomously discover and communicate with co-located functions in shared memory spaces. The system provides self-describing function interfaces and automatic registration mechanisms that reduce deployment complexity by eliminating manual configuration requirements for co-located functions.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The patent creates a universal deployment packaging format and interface standard that works across different deployment scenarios whether functions are co-located in shared memory or distributed across remote boundaries. This universal approach simplifies deployment complexity by providing a single deployment model that adapts to different runtime configurations.

Inventive Principle:

Principle #6Universality (Multi-functionality)

4Productivity

If dynamic updates of deployment packaging are implemented, then service performance is optimized, but system complexity and management overhead increase

Engineering Contradiction:

Improveservice performanceVSAvoidsystem complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The patent implements preliminary action by pre-defining deployment packaging templates and function deployment descriptors that capture deployment metadata, resource requirements, and communication interfaces. This preliminary preparation enables automated deployment updates without complex runtime decision-making, reducing system complexity while maintaining performance optimization capabilities.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS20250254537A1Managing node, network node, and methods performed therein for handling a service comprising functions deployed in a communications network

Publication Date: 2025.08.07 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)

AI summary

Embodiments herein relate, in some examples, to a method performed by a managing node for handling a service comprising functions deployed in a communication network. The managing node obtains an indication of a measured parameter related to communications between the functions; and triggers an updating of a deployment packaging of the functions based on the obtained indication.