Dynamic Service Mesh Configuration for Discovered Peers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Service meshes face challenges in dynamically configuring networking resources for newly discovered external entities in dynamic environments, such as 5G networks, where peers are not previously known, leading to difficulties in establishing communication paths and managing service mesh configurations.

Innovation Solution

A system and method that utilize custom resource objects and a Kubernetes control plane to dynamically create and configure service mesh network resources, including service entries, virtual services, and route rules, based on custom resource definitions provided by newly discovered external entities, allowing for real-time management of communication paths and resource allocation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If service meshes use static configuration for networking resources, then configuration management is simplified, but adaptability to dynamically discovered external entities is reduced

Engineering Contradiction:
Improveadaptability to dynamically discovered external entitiesVSAvoidconfiguration management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements dynamic service mesh configuration by enabling the system to automatically create and update networking resources (ServiceEntries, VirtualServices, DestinationRules) based on runtime discovery of external entities. The configuration transitions from static pre-definition to dynamic generation through the Service Mesh Controller, which processes discovered entities and generates appropriate Istio configuration resources automatically.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The service mesh system performs self-configuration through automated controller logic that discovers external entities and generates the necessary networking resources without manual intervention. The controller automatically creates ServiceEntries for external entity registration, generates VirtualServices for traffic routing, and configures DestinationRules for load balancing and policy enforcement, enabling the system to adapt to new entities autonomously.

Inventive Principle:
Principle #25Self-service

2Adaptability or versatility

If service meshes dynamically create networking resources for newly discovered entities, then adaptability improves, but device complexity and configuration overhead increase

Engineering Contradiction:
Improveability to operate in dynamic environmentsVSAvoidservice mesh configuration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The Service Mesh Controller acts as an intermediary between discovered external entities and the service mesh networking resources. The controller receives information about external entities, processes this information through standardized logic, and generates the appropriate Istio configuration resources. This intermediary layer abstracts the complexity of dynamic configuration management, allowing the system to adapt to new entities while maintaining controlled and manageable configuration processes.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The service mesh configuration system implements universal handling for different types of external entities through a unified configuration approach. The same controller logic and resource generation process handles various entity types (databases, servers, peer network functions) consistently, creating appropriate ServiceEntries, VirtualServices, and DestinationRules based on entity characteristics. This universal mechanism reduces configuration complexity by applying the same patterns across diverse entity types.

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

3Ease of operation

If each application implements its own communication features, then communication functionality is achieved, but troubleshooting difficulty increases

Engineering Contradiction:
Improvecommunication functionalityVSAvoidtroubleshooting difficulty
Core Design Contradiction:
Ease of operationVSDifficulty of detecting and measuring

Solution Approach 1:

The patent extracts communication functionality from individual applications and centralizes it in the service mesh infrastructure. Features such as traffic encryption, decryption, and packet capture are implemented at the service mesh layer through standardized configurations rather than being embedded in each application. This extraction allows communication features to be managed uniformly and troubleshooted through a single point of control, eliminating the need to investigate each application's custom implementation.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The service mesh consolidates various communication features into a unified infrastructure layer that handles encryption, decryption, routing, and packet capture collectively. By merging these distributed communication functions into a centralized service mesh system with standardized configurations, the patent enables uniform troubleshooting procedures that can detect and measure communication issues across all applications through a single management interface.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS11936724B2Configuring service mesh networking resources for dynamically discovered peers or network functions
Publication Date: 2024.03.19 MICROSOFT TECHNOLOGY LICENSING LLC
  • US11936724B2 patent drawing
  • US11936724B2 patent drawing
  • US11936724B2 patent drawing

AI summary

The present disclosure relates to methods and systems for configuring service mesh networking resources for dynamically discovered external entities. The methods and systems create custom resource objects for services provided by the external entities and dynamically create service mesh network resources for the custom resource objects. The methods and systems enable communications with the external entities using the service mesh network resources.