Zone-Based State Synchronization for Secure Operations

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems struggle to maintain state consistency and ensure secure, synchronized operations among multiple actors within computer-implemented environments, particularly in distributed systems, leading to potential inconsistencies and security vulnerabilities.

Innovation Solution

A method and system for secure communication and synchronization of actors within zones, using unique identifiers and shared secrets to determine presence and prevent overlapping actions, implemented through a domain and zone structure with cryptographic controls.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple users act independently in distributed systems, then system flexibility and autonomy are improved, but state consistency and data integrity deteriorate

Engineering Contradiction:
Improveuser autonomyVSAvoidstate consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system implements feedback mechanisms where users receive notifications about state changes in the shared data store, allowing them to adjust their independent actions accordingly. This feedback loop enables users to maintain autonomy while preserving state consistency through informed decision-making based on real-time system state information.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs preliminary actions by establishing a shared data store and notification mechanisms before users begin their independent operations. This preliminary setup ensures that all users start with a consistent state baseline and have the infrastructure in place to maintain consistency throughout their independent actions.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If a record system is implemented to track changes, then data integrity is improved, but system complexity increases

Engineering Contradiction:
Improvedata integrityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system creates a simplified copy of the data store state that is distributed to all users through notifications. Instead of implementing a complex centralized record-keeping system, the patent uses replicated state information that automatically reflects changes, reducing system complexity while maintaining data integrity through consistent state copying.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system extracts only the essential change information from the complete data store and transmits it to users through notifications. This extraction approach focuses the record-keeping function on what is actually needed for user awareness and action, rather than maintaining complex comprehensive records of all system operations.

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If users are notified of state changes, then state consistency is improved, but communication overhead increases

Engineering Contradiction:
Improvestate consistencyVSAvoidcommunication overhead
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system implements partial notification by sending only the essential state change information rather than complete data copies. This partial action approach provides sufficient state consistency information for users to understand and respond to changes without the excessive communication overhead of transmitting entire data sets.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS20250286896A1Methods & systems for synchronising and controlling state within computer-implemented environments
Publication Date: 2025.09.11 NCHAIN LICENSING AG
  • US20250286896A1 patent drawing
  • US20250286896A1 patent drawing
  • US20250286896A1 patent drawing

AI summary

A computer-implemented method of broadcasting a presence of first actor (O1) within or near said zone (Z), of a domain (D) comprising a plurality of zones (Z) that are at least one of: a physical entity represented by spatial or geospatial data; representable as a virtual zone in a virtual domain; and representable as an entry within a database or data table. A zone can comprise functionality and/or variables; and/or controlled by a program representing the zone. The domain (D) can be at least one of a distributed data structure and/or configured on a distributed ledger. The method broadcasts to at least another actor (O2) within the domain. At least one transmission contains data that enables the at least another actor (O2) to determine proximity of a first actor (O1) to the zone (Z). The domain can be a network, an environment or domain, such as a warehouse.