Enterprise Notification Service Subscription Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current notification systems lack flexibility and efficiency in managing subscriptions and delivering notifications across diverse applications, with limited support for dynamic subscription types, secure authentication, and reliable messaging.

Innovation Solution

A notification service that allows for flexible subscription management, secure authentication, and reliable messaging by providing a unified subscription model, supporting multiple notification types, and enabling secure redaction and authentication mechanisms, with the ability to handle various formats like RSS and email, and ensuring message delivery even if the service restarts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a unified subscription model is implemented to manage diverse applications, then adaptability and versatility improve, but device complexity increases

Engineering Contradiction:
Improvesubscription management flexibilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The notification service implements a universal subscription model that can handle multiple notification types (RSS, email, instant messaging) and serve diverse applications through a single standardized interface. The subscription object contains generic fields (subscriber ID, notification types, delivery preferences) that can accommodate different application requirements without requiring application-specific subscription structures, thus achieving versatility while maintaining manageable complexity through standardization.

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

2Reliability

If secure authentication and redaction mechanisms are added, then reliability improves, but device complexity increases

Engineering Contradiction:
Improvesecure notification deliveryVSAvoidauthentication mechanism complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The notification service acts as an intermediary between the publishing application and the subscriber, centralizing authentication and security checks. The service validates subscriber credentials, manages authentication tokens, and performs content redaction based on subscriber permissions before delivering notifications. This mediator approach ensures reliable secure delivery without requiring each application to implement its own complex authentication mechanisms, thus improving reliability while containing complexity within the notification service boundary.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary authentication and authorization checks before notification delivery. Subscriber credentials are verified in advance, authentication tokens are issued and stored, and content redaction rules are pre-configured based on subscriber permissions. This preliminary action ensures that only authenticated subscribers receive appropriate content, improving security and reliability while allowing the actual notification delivery process to proceed efficiently without repeated authentication overhead.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If multiple notification types and formats are supported, then adaptability improves, but device complexity increases

Engineering Contradiction:
Improvenotification format supportVSAvoidnotification handling complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The notification service segments the handling of different notification types into distinct, independent modules. Each notification type (RSS, email, instant messaging) has its own processing logic and delivery mechanism, but they all share a common subscription management framework. This segmentation allows the system to support multiple formats adaptably while keeping each individual notification type's complexity manageable and isolated, so adding or modifying one notification type does not affect others.

Inventive Principle:
Principle #1Segmentation

4Reliability

If message delivery reliability is ensured through persistent storage, then reliability improves, but loss of time increases

Engineering Contradiction:
Improvemessage delivery guaranteeVSAvoidnotification delivery delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The notification service performs preliminary actions by pre-processing and validating notification content before queuing for delivery. Authentication tokens are issued in advance, content redaction is performed beforehand, and notification templates are pre-configured. This preliminary action reduces the processing time required at delivery moment, allowing the system to maintain reliable persistent storage and queuing mechanisms while minimizing the actual delivery delay experienced by subscribers.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9734487B2Useful data and content feeds in the enterprise
Publication Date: 2017.08.15 ORACLE INT CORP
  • US9734487B2 patent drawing
  • US9734487B2 patent drawing
  • US9734487B2 patent drawing

AI summary

In a new Notification Service, applications can publish data and allow users to subscribe to that data how they wish, with methods for secure redaction and secure authentication.