Cloud Event Schema Validation and Maturity Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud service providers face challenges in standardizing and automating the generation and management of cloud service provider events, leading to difficulties in data model and data contract management, which hinders the ability of consumers to effectively utilize and automate services.

Innovation Solution

Implementing a cloud provider events generation module that defines and validates event maturity levels, publishes event schemas, and calculates validation scores, allowing for automated event management and consumption, enabling consumers to understand event semantics and data contracts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If cloud service providers manually manage and publish events without standardization, then service providers can rapidly add new features and evolve services, but consumers face difficulty understanding event semantics, data contracts, and reliability, leading to manual operations and wasted human resources

Engineering Contradiction:
Improveservice evolution capabilityVSAvoidevent consumption difficulty
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent segments event information into structured components including event schemas, data contracts, maturity levels, and validation rules. This segmentation allows consumers to systematically understand and process event data without being overwhelmed by unstructured information, resolving the contradiction between service evolution and ease of operation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an event schema and data contract as intermediary layers between service providers and consumers. These intermediaries standardize event formats and semantics, enabling consumers to reliably process events from rapidly evolving services without manual intervention, thus resolving the contradiction.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If cloud service providers publish events without validation and standardization, then event generation is fast and flexible, but event reliability and consistency are compromised, making automation difficult

Engineering Contradiction:
Improveevent generation speedVSAvoidevent data consistency
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements preliminary validation through event schemas and data contracts before events are published. This preliminary action ensures that events meet consistency and reliability requirements upfront, allowing fast event generation without compromising data quality, thus resolving the contradiction between productivity and reliability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent incorporates feedback mechanisms where event schemas define validation rules that provide immediate feedback on event consistency. This feedback loop ensures that only reliable events are published, maintaining high productivity while ensuring event data consistency through automated validation.

Inventive Principle:
Principle #23Feedback

3Reliability

If cloud service providers implement comprehensive event validation and standardization, then event reliability and consumer automation capability improve, but the complexity of event management systems increases

Engineering Contradiction:
Improveevent trustworthinessVSAvoidevent management system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates universal event schemas and data contracts that serve multiple functions: validation, documentation, and automation guidance. This multi-functionality reduces the need for separate management systems, achieving high event reliability without proportionally increasing system complexity.

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

Solution Approach 2:

The patent introduces maturity levels as a parameter that evolves events from basic to advanced states. This parameterized approach allows gradual implementation of validation and standardization, enabling providers to balance reliability requirements with system complexity based on their specific needs.

Inventive Principle:
Principle #35Parameter changes

4Ease of manufacture

If cloud service providers use ad hoc event publication methods, then implementation is simple and quick, but consumers cannot reliably build automated features and operations remain manual

Engineering Contradiction:
Improveevent publication simplicityVSAvoidconsumer operation automation
Core Design Contradiction:
Ease of manufactureVSExtent of automation

Solution Approach 1:

The patent enables self-service automation through machine-consumable event schemas and data contracts. Consumers can automatically validate and process events without manual intervention, achieving reliable automation while maintaining simple event publication processes through standardized formats that self-describe their structure and semantics.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11675636B2Method and apparatus for cloud service provider events generation and management
Publication Date: 2023.06.13 JPMORGAN CHASE BANK NA
  • US11675636B2 patent drawing
  • US11675636B2 patent drawing
  • US11675636B2 patent drawing

AI summary

Various methods, apparatuses/systems, and media for automatic generation and management of cloud service provider events are provided. A service provider computing device defines a maturity level of an event; publishes an event schema associated with the maturity level of the event; and transmits the event to an event platform that is configured to provide infrastructure for event production and consumption. The event platform validates the event based on the event schema; calculates a validation score for the event upon validation of the event; and publishes the validation score on a website. A consumer computing device consumes the published event from the event platform.