Role-Driven Notification System for Cloud Provisioning Automation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity of provisioning cloud services in a cloud environment is labor-intensive and often manual, requiring efficient automation to streamline processes such as resource allocation and notification management.

Innovation Solution

A role-driven notification system that combines notification templates based on user roles, collapsing redundant information and generating the least necessary notifications, with a hierarchy that maps roles to notification templates and sends consolidated messages to users based on their role hierarchy.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If multiple notification templates are sent to users with multiple roles, then all relevant information is provided, but notification redundancy and information overload increase

Engineering Contradiction:
Improvenotification completenessVSAvoidnotification management complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent combines multiple notification templates associated with different roles into a single consolidated notification. The system identifies users with multiple roles, retrieves all applicable notification templates, merges their content while removing duplicates, and delivers one unified notification instead of multiple separate ones. This resolves the contradiction by maintaining information completeness while reducing notification redundancy and management complexity.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates a universal notification template that serves multiple roles simultaneously. Instead of creating separate notifications for each role, the system generates a single multi-functional notification that incorporates information relevant to all applicable roles. This universal approach maintains comprehensive information delivery while simplifying the notification management process.

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

2Measurement precision

If notification templates are customized for each role, then notification precision is improved, but system complexity increases

Engineering Contradiction:
Improvenotification relevanceVSAvoidtemplate management complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent merges multiple role-specific notification templates into a single consolidated template. The system retrieves templates associated with each of a user's roles, combines their content, removes redundancies, and produces one unified notification template. This approach maintains the precision of role-specific information while reducing the complexity of managing multiple separate templates.

Inventive Principle:
Principle #5Merging (Combining)

3Device complexity

If manual processing of cloud service provisioning is used, then system complexity is reduced, but productivity decreases

Engineering Contradiction:
Improvesystem simplicityVSAvoidprovisioning efficiency
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent implements an automated notification system that self-services the cloud provisioning process. The system automatically identifies users with multiple roles, retrieves applicable notification templates, determines which information to consolidate, and generates unified notifications without manual intervention. This automation maintains system simplicity while dramatically improving provisioning productivity and efficiency.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10341171B2Role-driven notification system including support for collapsing combinations
Publication Date: 2019.07.02 ORACLE INT CORP
  • US10341171B2 patent drawing
  • US10341171B2 patent drawing
  • US10341171B2 patent drawing

AI summary

Embodiments of the invention relate techniques of implementing role-driven notification. The techniques can include determining a location of a role in a role hierarchy and a corresponding location of a first notification template in a notification template hierarchy. The techniques can also include identifying one or more child roles of the role corresponding to the user and one or more child notification templates of the notification template corresponding to the user. The techniques can include generating a second notification template, the second notification template including the one or more rules included in each of the one or more child notification templates and sending a notification for the user based on the second notification template.