Closed Loop Stage Composition for Multi-Vendor Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current closed loop automation in 5G and future wireless networks faces challenges in integrating closed loop management functions from different vendors without the need for a shared development kit or standardized APIs, particularly in multi-vendor network automation environments.
Innovation Solution
A standards-based multi-vendor approach leveraging the 3GPP SA5 API to enable the integration of closed loops from different closed loop stages by defining a CLStage information model, CLStageProfile, and implementing standardized interfaces for data exchange between stages, allowing for the composition of closed loops from multiple vendors.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If closed loop management functions are implemented in a single application combining all functionalities, then integration and deployment are simplified, but multi-vendor interactions are limited and vendors cannot independently deploy their modules
Solution Approach 1:
The patent segments the closed loop management function into distinct stages (data collection, analysis, decision, execution) that can be independently implemented by different vendors. Each stage is defined as a separate module with standardized interfaces, allowing multi-vendor integration while maintaining deployment simplicity through the standardized stage composition framework.
2Adaptability or versatility
If vendors use a shared development kit for multi-vendor integration, then integration capability is improved, but intellectual property concerns prevent vendors from opening their developments
Solution Approach 1:
The patent introduces a standardized closed loop stage profile as an intermediary that enables multi-vendor integration without requiring vendors to share their proprietary development kits. The profile acts as a common interface specification that allows different vendor implementations to interoperate through standardized data exchange formats and stage composition rules, protecting intellectual property while achieving integration.
3Adaptability or versatility
If closed loop stages from different vendors are integrated without standardized APIs, then vendor independence is maintained, but integration complexity increases and runtime composition becomes difficult
Solution Approach 1:
The patent creates a universal closed loop stage profile that can accommodate implementations from different vendors through standardized interfaces. The profile defines common data structures, stage types, and composition rules that enable runtime integration of heterogeneous vendor stages without requiring proprietary APIs, thus maintaining vendor independence while reducing integration complexity.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
There are provided measures for composition of closed loops from closed loop stages. Such measures exemplarily comprise, at of a network entity composing a closed loop from a plurality of closed loop stages, transmitting a request for a first closed loop stage profile, receiving said first closed loop stage profile indicative of capabilities and characteristics of a first closed loop stage, analyzing said first closed loop stage profile, and deciding on application of said first closed loop stage based on said first closed loop stage profile.