Group Manager Capability Data for Node Interoperability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

When adding a new device (node) to a group of computers, ensuring interoperability and compatibility among members with different software layers and versions is challenging due to varying protocols and data formats, leading to complexity in initial handshake communications and potential incompatibility issues.

Innovation Solution

Employing group capability data to standardize communication requirements, ensuring that new members support identified capabilities before joining, and dynamically updating these requirements to maintain software version consistency within the group, thereby simplifying inter-member communication and facilitating software migration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If each layer of software on newly added devices communicates with corresponding layers on existing members using different protocols and data formats, then interoperability between members is ensured, but communication complexity and incompatibility issues increase

Engineering Contradiction:
ImproveinteroperabilityVSAvoidcommunication complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a group manager as an intermediary component that maintains capability data for each software layer in the group. When a new device joins, the group manager provides the necessary capability information to enable communication without requiring the new device to handle all possible protocol variations directly. This mediator approach resolves the contradiction by centralizing compatibility management.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements preliminary action by having the group manager maintain capability data in advance before new devices join the group. The capability data describes what each layer can do, allowing new devices to be pre-configured with appropriate communication parameters. This eliminates the need for complex runtime negotiation and reduces communication complexity while ensuring interoperability.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If each layer of software handles a wide variety of incompatibility issues to ensure compatibility with other members, then interoperability is maintained, but the complexity of initial handshake communication increases

Engineering Contradiction:
ImprovecompatibilityVSAvoidhandshake communication complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the complexity of handling incompatibility issues from individual software layers and consolidates it in the group manager. The group manager maintains capability data that encapsulates all compatibility information, allowing individual layers to communicate using simplified protocols while the group manager ensures overall compatibility. This extraction reduces handshake communication complexity while maintaining reliability.

Inventive Principle:
Principle #2Taking out (Extraction)

3Productivity

If group capability data is dynamically updated to maintain software version consistency, then software migration is facilitated, but the need for persistent storage of capability data arises

Engineering Contradiction:
Improvesoftware migration efficiencyVSAvoidstorage requirements
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements self-service by having the group manager automatically update capability data when software versions change in the group. The system monitors software versions and dynamically updates capability information without requiring external intervention or persistent storage of historical capability data. This self-updating mechanism facilitates smooth software migration while avoiding the complexity of managing persistent capability data storage.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS7805503B2Capability requirements for group membership
Publication Date: 2010.09.28 ORACLE INT CORP
  • US7805503B2 patent drawing
  • US7805503B2 patent drawing
  • US7805503B2 patent drawing

AI summary

A method and apparatus for adding a node to a group of nodes is provided. Group capability data is stored in volatile memory of a group manager for a group. The group capability data identifies capability requirements for members of the group. The group manager provides notification services for members of the group. A request to add a particular node to a group is received. In response to receiving the request, a determination is made as to whether the particular node satisfies the capability requirements identified by the group capability data. Upon determining that the particular node does satisfy the capability requirements identified by the group capability data, the particular node is added to the group. The capability requirements for members of a group may initially be based on the capabilities of the first node that is added to a group.