Notification Manager Dynamic Feed Generation for IT Asset Monitoring

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

IT service management systems face challenges in accessing server-side information due to security restrictions and the complexity of dealing with lower-level protocols, particularly for web client applications, which often require pulling data asynchronously, potentially compromising network security and increasing client-side burden.

Innovation Solution

A client-side method where a notification manager dynamically generates new information objects or feeds, such as Atom feeds or XMLHttpRequest objects, to provide customized information about specific managed entities, allowing clients to request and receive tailored data without relying on proprietary protocols or APIs, using a publish-subscribe communication protocol to manage resource access securely.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If web clients use pull technology to access server-side entities, then clients can retrieve information asynchronously, but network security is compromised due to firewall holes

Engineering Contradiction:
Improveinformation retrieval efficiencyVSAvoidnetwork security risk
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The patent inverts the traditional pull model by implementing a push model where the server proactively sends information to clients. The server-side resource manager pushes notification feeds to web clients without requiring clients to initiate requests, thereby maintaining firewall security while enabling asynchronous information delivery. This is achieved through server-generated feeds that are pushed to clients via standard web protocols.

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

The patent introduces a notification manager as an intermediary component between the server-side resource manager and web clients. This intermediary receives push notifications from the resource manager, processes them into standardized feed formats, and delivers them to clients through web-compatible interfaces. The intermediary layer enables secure information push while maintaining protocol compatibility and security boundaries.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If clients deal with lower-level messaging protocols like JMS, then direct access to IT assets is achieved, but client program complexity increases substantially

Engineering Contradiction:
Improvedirect asset access capabilityVSAvoidclient programming complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts the complex messaging protocol handling from the client side and relocates it to the server side. The server-side notification manager handles all JMS protocol interactions, message routing, and asset access complexity internally. Clients only need to interact with simplified web-compatible feed interfaces, thereby extracting the complexity burden from clients while maintaining full access capability to IT assets.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent creates simplified copies of asset information in the form of standardized notification feeds. Instead of requiring clients to directly query complex IT assets through proprietary protocols, the server generates simplified feed representations that mirror the essential information. These feed copies provide clients with accessible information without requiring them to handle the underlying protocol complexity.

Inventive Principle:
Principle #26Copying

3Object-affected harmful factors

If servers provide information using push model, then network security is maintained, but clients cannot easily access customized information about specific entities

Engineering Contradiction:
Improvenetwork securityVSAvoidcustomized information access
Core Design Contradiction:
Object-affected harmful factorsVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic feed generation where the server-side notification manager creates customized notification feeds on-demand based on client subscriptions. When clients express interest in specific entities or information types, the system dynamically generates tailored feed streams without requiring pre-configured static feeds. This dynamic adaptation enables customized information access while maintaining the secure push model architecture.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent enables clients to customize information by changing subscription parameters such as entity identifiers, information types, and filtering criteria. The notification manager processes these parameter changes by generating feeds with customized content based on client-specific requirements. This parameter-based customization allows clients to receive tailored information while the server maintains security through controlled feed generation and delivery.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10637910B1Method for dynamically generating information objects based on a restful subscription request
Publication Date: 2020.04.28 EMC IP HLDG CO LLC
  • US10637910B1 patent drawing
  • US10637910B1 patent drawing
  • US10637910B1 patent drawing

AI summary

Techniques disclosed herein describe a client and/or server process for managing Information Technology (IT) assets, such as servers and storage devices. The process dynamically generates customized information objects based on subscription requests. A client generates a request for information. The request specifies information associated with a specific managed entity or IT resource. A server that monitors the specific managed entity does not maintain such information in an existing information object. Information associated with the specific managed entity can be performance information, health information, usage information, and the like. A notification manager receives the request and identifies that existing subscription resources don not contain the requested information. The notification manager generates a new information object that contains the requested information, and notifies the client.