Hierarchical Publish-Subscribe Software Distribution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing enterprise software distribution systems face challenges in efficiently managing network bandwidth and resources, particularly in large networks with over 1000 nodes, where point-to-point protocols are slow, broadcast distributions require operator support, and publish/subscribe models lead to unnecessary message flow and resource overload.

Innovation Solution

A modified publish and subscribe messaging system that optimizes message delivery by including recipient routes in message addresses and using existing network communications, allowing centralized sequencing of messages without requiring each node to subscribe to multiple channels, thereby minimizing resource usage and optimizing bandwidth.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If point-to-point message protocol is used for software distribution, then each node receives only the messages it needs, but the distribution time becomes excessively long for large networks with over 1000 nodes

Engineering Contradiction:
Improvemessage delivery accuracyVSAvoiddistribution time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the enterprise network into multiple hierarchical levels with distribution points at each level. Software distribution messages are segmented and routed through this hierarchy, allowing parallel distribution to multiple nodes simultaneously while maintaining targeted delivery. This resolves the contradiction by enabling fast distribution across large networks without sending unnecessary messages to all nodes.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces application layer routers as intermediary components that receive software distribution messages and intelligently forward them to appropriate subscribers. These routers act as mediators between the central distribution point and end nodes, enabling efficient routed distribution that combines the speed of broadcast with the precision of point-to-point delivery.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Use of energy by moving object

If broadcast protocol is used to distribute software to multiple endpoints, then network bandwidth requirements are reduced, but operator support and configuration are required at each workstation

Engineering Contradiction:
Improvenetwork bandwidth usageVSAvoidworkstation configuration
Core Design Contradiction:
Use of energy by moving objectVSEase of operation

Solution Approach 1:

The patent implements self-service mechanisms where endpoints automatically discover and subscribe to relevant software distribution channels based on their identity and requirements. The system performs automatic configuration at each workstation without requiring operator intervention, while still using efficient broadcast-based distribution that minimizes network bandwidth usage.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If publish and subscribe messaging is used to control software distribution based on location and function, then distribution control is improved, but unnecessary messages are sent to endpoints and network resources are overloaded

Engineering Contradiction:
Improvedistribution controlVSAvoidnetwork resource usage
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The patent segments the publish/subscribe model into a hierarchical structure with multiple levels of distribution points. Each level handles a subset of endpoints, segmenting the message flow so that messages are not propagated to all endpoints in the enterprise. This maintains adaptability and control while reducing unnecessary message transmission and network resource consumption.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts and removes unnecessary message routing from the traditional publish/subscribe model. By implementing intelligent routing at application layer routers that filter and forward only relevant messages to appropriate subscribers, the system eliminates the wasteful broadcast-to-all approach while preserving the adaptability benefits of publish/subscribe messaging.

Inventive Principle:
Principle #2Taking out (Extraction)

4Loss of time

If multiple distribution points are used to speed up software distribution in large networks, then distribution time is reduced, but configuration and coordination complexity increases

Engineering Contradiction:
Improvedistribution timeVSAvoiddistribution system configuration
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The patent implements a universal hierarchical distribution architecture where distribution points at different levels follow the same standardized protocols and messaging formats. This multi-functional framework allows multiple distribution points to operate simultaneously with reduced coordination complexity, as each point independently handles its local endpoints using the same universal rules.

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

Solution Approach 2:

The patent performs preliminary configuration and setup at the design phase, establishing the hierarchical distribution structure and routing rules before software distribution begins. Application layer routers are pre-configured with subscriber information and routing tables, enabling fast distribution without requiring real-time coordination between multiple distribution points.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8166185B2System and method for enterprise software distribution
Publication Date: 2012.04.24 HEWLETT PACKARD ENTERPRISE DEV LP
  • US8166185B2 patent drawing
  • US8166185B2 patent drawing
  • US8166185B2 patent drawing

AI summary

A method for distributing software is provided. The method includes distributing a message from an application server to one or more application layer routers, such as servers that are being used to route enterprise software distribution messages, using a modified publish and subscribe architecture that includes the route to all recipients in the message address and that uses existing network communications. The message can thus be distributed to one or more subscribers on a first channel. The message is then distributed to one or more subscribers using the modified publish and subscribe architecture on one or more second channels selected from a second channel layer if necessary. This process is repeated until the message reaches all subscribers listed as recipients in the message.