Model-Based Data Acquisition for Cloud Monitoring Systems

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Traditional monitoring systems are inefficient and difficult to update, requiring recoding and redeployment for new acquisition objects, which affects service operations and is not well-suited for the rapid changes and complexities of 5G and cloud network environments.

Innovation Solution

A data acquisition method using model files to define data acquisition objects, parameters, and alarm descriptions, allowing for flexible deployment and customization without recoding, and enabling rapid development and connection of new devices, with a microservice architecture for efficient data processing and transmission.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional monitoring systems use hard-coded acquisition objects, then system stability is maintained, but adaptability to new requirements deteriorates

Engineering Contradiction:

Improveadaptability to new requirementsVSAvoidsystem update complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the monitoring system into independent microservices, including acquisition services, processing services, and notification services. Each microservice can be independently developed, deployed, and updated. The acquisition objects are separated from the core system logic and can be dynamically loaded through configuration files, allowing new acquisition objects to be added without modifying the system code, thus improving adaptability while maintaining system stability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent implements dynamic configuration capabilities where acquisition objects, parameters, and alarm thresholds can be modified through configuration files without requiring system restart or recoding. The system can dynamically load and unload acquisition objects based on configuration changes, enabling flexible adaptation to new requirements while maintaining operational stability.

Inventive Principle:

Principle #15Dynamics

2Productivity

If traditional monitoring systems deploy new acquisition objects through recoding, then measurement precision is ensured, but loss of time increases

Engineering Contradiction:

Improvedeployment speedVSAvoiddevelopment and debugging time

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The patent prepares acquisition objects in advance as configurable templates with predefined parameters and structures. These templates are stored in configuration files and can be quickly instantiated when needed. The preliminary preparation of acquisition object templates eliminates the need for time-consuming recoding and debugging during deployment, significantly improving deployment speed while maintaining measurement precision through the use of pre-validated templates.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent uses configuration files as copies of acquisition object definitions, which can be replicated and modified without affecting the original system code. New acquisition objects can be created by copying existing templates and modifying their configuration parameters, avoiding the need for recoding and extensive debugging, thus reducing deployment time while ensuring consistency and precision.

Inventive Principle:

Principle #26Copying

3Reliability

If traditional monitoring systems restart after deployment, then reliability of new functions is ensured, but service continuity deteriorates

Engineering Contradiction:

Improvefunction deployment reliabilityVSAvoidservice continuity

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The patent implements hot-swapping capabilities for acquisition objects, allowing new or modified acquisition objects to be loaded and activated without stopping the monitoring system. The microservice architecture enables seamless replacement of acquisition services, maintaining continuous data acquisition and processing operations. This ensures both the reliability of new functions through proper loading procedures and the continuity of service operations without restarts.

Inventive Principle:

Principle #20Continuity of useful action

4Adaptability or versatility

If traditional monitoring systems use fixed architecture, then manufacturing precision is maintained, but adaptability to different environments deteriorates

Engineering Contradiction:

Improvesupport for different deployment environmentsVSAvoidarchitecture flexibility

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent designs a universal microservice architecture that can function across different deployment environments (cloud, edge, on-premise) using the same core components. The acquisition services, processing services, and notification services are environment-agnostic and can be deployed in various configurations. Configuration files define environment-specific parameters, allowing the same system architecture to adapt to different deployment scenarios without requiring environment-specific code, thus improving versatility while maintaining architectural consistency.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentEP3975481B1Data acquisition method and apparatus, computer device, and computer-readable medium

Publication Date: 2024.06.26 ZTE CORP

Figure 1~3
Figure 4~5a
Figure 6a~6b

AI summary

A data acquisition method and apparatus, a computer device, and a computer-readable medium are disclosed. The method includes: receiving a model file configured to define a data acquisition object, an acquisition parameter, and alarm description information (S21); and sending the model file to an acquisition apparatus, such that the acquisition apparatus acquires data according to the model file (S22).