Event Grid Service Schema Mapping for Cloud Interoperability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional event notification systems in cloud computing are rigid and inflexible, making it laborious to interconnect multiple applications and services, and often configured primarily for human subscribers, lacking scalability and flexibility for notifying various types of subscribers.

Innovation Solution

The event grid service intelligently derives and applies mappings to translate non-conforming event data from publishing services into conforming formats, enabling seamless interconnection and notification of subscribers without requiring changes to native formatting techniques, using registration information and schema analysis to establish relationships between services and subscribers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional event notification systems use fixed formatting and communication protocols for each service, then each service can maintain its native format, but interconnecting multiple applications and services becomes time-intensive and laborious

Engineering Contradiction:
Improveformat flexibilityVSAvoidinterconnection complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an event grid service as an intermediary between publishing services and subscribers. This mediator receives events from publishing services in various native formats, automatically derives mappings between the event schema and topic schema, and translates events into conforming formats for delivery to subscribers. This intermediary approach enables format flexibility without requiring direct integration between each service pair, thereby reducing interconnection complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system dynamically changes the formatting parameters of events based on the target subscriber's requirements. The event grid service analyzes the publishing service's event schema, compares it with the topic's default schema, and automatically derives mapping parameters that transform the event data into the appropriate format. This parameter transformation enables services to maintain their native formats while ensuring conforming output for subscribers.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If conventional notification systems are configured for human subscribers, then human users can receive notifications, but the systems lack scalability for notifying various types of subscribers

Engineering Contradiction:
Improvesubscriber type flexibilityVSAvoidnotification reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The event grid service implements a universal subscription mechanism that can handle multiple types of subscribers (human users, applications, services, or devices) through a single standardized interface. The system uses schema-based validation and automatic mapping that works regardless of subscriber type, enabling the same notification infrastructure to serve diverse subscribers reliably without requiring type-specific configuration.

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

3Adaptability or versatility

If services use their own native formatting techniques, then each service maintains its data structure, but manual schema mapping becomes required which increases labor and time requirements

Engineering Contradiction:
Improveformat diversityVSAvoidintegration speed
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The event grid service implements self-service automatic schema mapping that eliminates the need for manual configuration. When a publishing service registers with the event grid, the system automatically analyzes the service's event schema, compares it with the topic's default schema, and derives the appropriate mappings without human intervention. This self-deriving capability maintains support for diverse native formats while dramatically increasing integration speed and productivity.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10681164B2Input and output schema mappings
Publication Date: 2020.06.09 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10681164B2 patent drawing
  • US10681164B2 patent drawing
  • US10681164B2 patent drawing

AI summary

Optimizations are provided for interconnecting event sources with event subscribers in a seamless manner so that the native formatting/schema methodologies used by event sources and subscribers will not need to be natively modified. An event grid service is provided as a routing and mapping service. This event grid service receives event data that may be organized in any kind of format. By analyzing the format, the event grid service determines whether the format correlates with a format used by a consumer of that event data. If the formats conform, then the event grid service extracts relevant data from the event data and pushes it to the subscriber. If the formats do not conform, the event grid service intelligently generates a mapping to map the two formats together.