Cloud Service Event Reporting Framework

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cloud service technologies face challenges in efficiently providing real-time status information and managing workflows for media processing tasks, as they require complex processing capabilities and often necessitate cross-referencing multiple sources for understanding variables and events, leading to inefficiencies in reporting, monitoring, and notification processes.

Innovation Solution

A self-contained framework for cloud services that generates and sends messages containing updated variable and event information, using descriptors to provide complete and self-explanatory reports, notifications, and monitoring updates, ensuring recipients have all necessary information within the message without needing external cross-referencing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If cloud services use complex processing capabilities and multiple sources for status information, then measurement precision and reliability improve, but device complexity and ease of operation worsen

Engineering Contradiction:
Improvestatus information accuracyVSAvoidreporting system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system segments status information into distinct event types (variable events, system events, workflow events) and organizes them into structured event objects. Each event type is handled independently with specific descriptors, allowing the complex reporting system to be divided into manageable, modular components that can be processed separately while maintaining overall system accuracy.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary event reporting framework that acts as a mediator between the cloud service processing system and the monitoring/recording systems. This framework standardizes the representation of all status changes through unified event objects and descriptors, simplifying the interface between complex internal processing and external monitoring without losing measurement precision.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If cloud services provide comprehensive status information with complete variable descriptions, then information completeness improves, but loss of time and productivity worsen due to increased data processing

Engineering Contradiction:
Improvestatus information completenessVSAvoidreporting processing time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The system performs preliminary action by pre-defining variable descriptors with complete metadata (data types, units, formats, universal identifiers) before actual status monitoring begins. This allows the system to provide comprehensive information about all possible variables in advance, so that when events occur, only the specific event data needs to be transmitted rather than complete variable definitions repeatedly, reducing processing time while maintaining information completeness.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by creating standardized event object templates and descriptor structures that can be replicated and reused. Instead of transmitting complete variable definitions with every status update, the system copies and fills in only the necessary event-specific data within pre-established templates, significantly reducing data transmission and processing time while preserving complete information through the structured format.

Inventive Principle:
Principle #26Copying

3Reliability

If cloud services implement detailed monitoring and reporting frameworks, then reliability and measurement precision improve, but ease of operation and device complexity worsen

Engineering Contradiction:
Improveworkflow monitoring reliabilityVSAvoidreporting system usability
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent implements universality by designing a multi-functional event reporting framework that can handle multiple types of events (variable changes, system events, workflow events) through a single unified structure. The event objects and descriptors are designed to be universally applicable across different event types, allowing the system to provide detailed monitoring for all events while maintaining ease of operation through consistent, standardized handling procedures rather than requiring separate mechanisms for each event type.

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

Data Source

PatentUS11861411B2Variable and event reporting in a cloud service system
Publication Date: 2024.01.02 TENCENT AMERICA LLC
  • US11861411B2 patent drawing
  • US11861411B2 patent drawing
  • US11861411B2 patent drawing

AI summary

A method for cloud service includes receiving, by processing circuitry that operates for a cloud service, a request including a first reporting descriptor object including (i) a first variables descriptor object associated with variables, (ii) a first events descriptor object associated with events, and (iii) a reporting interval. The method also includes generating, by the processing circuitry, at a time within the reporting interval, a message including a second reporting descriptor object with (i) a second variables descriptor object having updated values for the variables and (ii) a second events descriptor object associated with a subset of the events. The method also includes sending, by the processing circuitry, the message to a recipient.