Provider Object Distribution via Local Persistence Conditions

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems face challenges in coordinating provider objects across different regions, leading to inefficiencies in data exchange and management, particularly when provider objects are generated in one region and consumed in another.

Innovation Solution

A device and method for distributing and locally persisting provider objects, which involves a communication interface and a controller that manage provider object streams between devices in different regions. The controller provides and receives indications of provider objects, discards those that do not meet local persistence conditions, and locally persists those that do, ensuring that provider objects are associated with their respective regions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If provider objects are exchanged between devices in different regions using standardized formats, then data exchange compatibility is improved, but coordination complexity increases due to different persistence mechanisms and regional variations

Engineering Contradiction:
Improvedata exchange compatibilityVSAvoidcoordination complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a message stream as an intermediary mechanism that standardizes the exchange of provider object indications between devices in different regions. The message stream acts as a mediator that carries standardized messages containing provider object data, region identifiers, and persistence conditions, thereby enabling compatible data exchange while abstracting away the coordination complexity of regional differences and persistence mechanisms

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the provider object exchange process into distinct standardized message components: provider object indications, region identifiers, persistence conditions, and update notifications. This segmentation allows each component to be handled independently according to standardized rules, reducing the overall coordination complexity while maintaining adaptability across regions

Inventive Principle:
Principle #1Segmentation

2Reliability

If all provider objects are persisted locally at every device, then data availability is improved, but bandwidth usage and processing overhead increase

Engineering Contradiction:
Improvedata availabilityVSAvoidbandwidth usage and processing overhead
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent applies local quality by allowing each device to selectively persist provider objects based on its specific needs, region, and persistence conditions received in messages. Instead of uniformly persisting all provider objects at all devices, each device makes localized decisions about what to persist, ensuring data availability for relevant objects while minimizing unnecessary bandwidth usage and processing overhead

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent implements a mechanism where devices receive persistence conditions in messages that indicate which provider objects should be persisted locally and which should be discarded. Devices can discard provider objects that do not meet local persistence conditions and recover them later through update notifications in the message stream, thereby optimizing bandwidth usage and processing overhead while maintaining data availability when needed

Inventive Principle:
Principle #34Discarding and recovering

Data Source

PatentUS12307394B2Device, system and method for distributing and locally persisting provider objects
Publication Date: 2025.05.20 AMADEUS SAS
  • US12307394B2 patent drawing
  • US12307394B2 patent drawing
  • US12307394B2 patent drawing

AI summary

A device, system and method for distributing and locally persisting provider objects is provided. A first device provides, in a provider object stream, first indications of first provider objects, generated and locally persisted in association with a first region, to a second device associated with a second region. The first device receives, in the stream, from the second device, second indications of second provider objects generated locally persisted in association with the second region, the second indications including respective identifiers identifying the second region. The first device: discards given second provider objects, indicated by the second indications, which do not meet a local persistence condition; and locally persists other second provider objects, as indicated by the second indications, which meet the local persistence condition, the other second provider objects locally persisted in association with the first region.