Agreement Manager for Multi-Party Distributed System Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Large distributed systems face inefficiencies in managing and enforcing changes across numerous resources and users due to the inability of manual and informal approval mechanisms to scale effectively, making it difficult to coordinate, track, and approve updates in a scalable, traceable, and automated manner.

Innovation Solution

Implementing a multi-party update system that includes a proposer, agreement manager, and approvers, where proposed updates are submitted with an authorization scheme defining satisfaction criteria and approver identities, allowing for scalable, traceable, and automated coordination and approval of changes across distributed systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual and informal approval mechanisms are used for system updates, then ease of operation is maintained, but scalability and automation capability deteriorate

Engineering Contradiction:
Improveease of operationVSAvoidscalability
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent introduces an agreement manager as an intermediary component that coordinates multi-party updates. The agreement manager receives update proposals, manages authorization schemes, coordinates approvals from multiple parties, and executes updates when authorization criteria are met. This intermediary automates the approval workflow while maintaining the collaborative decision-making process, thereby improving scalability without sacrificing ease of operation.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If resource management systems are used to manage access privileges, then ease of operation improves, but the ability to cope with growing numbers of system components deteriorates

Engineering Contradiction:
Improveease of operationVSAvoiddevice complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent segments the authorization process into distinct components: update proposals, authorization schemes, approval criteria, and execution decisions. By dividing the complex resource management task into manageable segments with clear responsibilities, the system can handle growing numbers of system components and users more effectively while maintaining ease of operation through structured workflows.

Inventive Principle:
Principle #1Segmentation

3Productivity

If automated multi-party update systems are implemented, then scalability and productivity improve, but system complexity and difficulty of coordination increase

Engineering Contradiction:
ImproveproductivityVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The agreement manager serves multiple functions within a single component: receiving update proposals, managing authorization schemes, coordinating approvals from multiple parties, tracking authorization criteria, and executing updates. This multi-functional design consolidates complexity into a centralized coordinator rather than distributing it across multiple specialized components, thereby improving scalability while managing system complexity through functional integration.

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

Data Source

PatentUS10454786B2Multi-party updates to distributed systems
Publication Date: 2019.10.22 AMAZON TECH INC
  • US10454786B2 patent drawing
  • US10454786B2 patent drawing
  • US10454786B2 patent drawing

AI summary

Multi-party updates may be performed for distributed systems. An agreement request may be received that proposes updates to a distributed system. An authorization scheme for the agreement request may be determined and approvers for the proposed updates identified according to the authorization scheme. Notifications may be provided to the approvers indicating the proposed updates to the distributed system. Responses from the approvers may be evaluated to determine whether the authorization scheme is satisfied for the proposed updates. If the authorizations scheme is satisfied, then the proposed updates may be performed to the distributed system.