Endpoint Data Structure Management for Software Upgrade Compatibility

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing software updates across complex systems like modern vehicles and IoT devices is challenging due to the unknown properties and capabilities of the endpoints, leading to difficulties in ensuring compatibility and efficiency in software distribution.

Innovation Solution

A data model and management system that stores endpoint data structures, representing components with arbitrary properties, and uses conflict resolution methods to aggregate and prioritize updates, allowing for flexible grouping and targeted deployment of packages and releases through a Query Grammar-based filtering system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If software updates are distributed across complex systems with unknown endpoint properties, then system adaptability is improved, but management complexity increases

Engineering Contradiction:
Improvesystem adaptabilityVSAvoidmanagement complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments endpoint information into standardized data structures with specific fields (identifier, domain, component profiles, properties, packages). This segmentation allows the system to handle diverse endpoints with unknown properties by breaking down their characteristics into manageable, standardized components, reducing management complexity while maintaining adaptability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system uses configurable data structure templates that can be dynamically adjusted to accommodate different endpoint types and properties. By changing the parameter definitions in the templates rather than modifying the core system architecture, the system adapts to new endpoint types without increasing fundamental management complexity.

Inventive Principle:
Principle #35Parameter changes

2Quantity of substance

If arbitrary properties are aggregated from multiple sources, then data completeness is improved, but conflict resolution difficulty increases

Engineering Contradiction:
Improvedata completenessVSAvoidconflict resolution difficulty
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The system performs preliminary conflict resolution by establishing precedence rules before data aggregation occurs. Sources are pre-ranked and weighted, so when multiple sources provide conflicting property values, the system already knows which source takes precedence. This preliminary arrangement simplifies the actual aggregation process and reduces real-time conflict resolution difficulty.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system introduces a conflict resolution mechanism as an intermediary layer between data sources and the endpoint representation. This intermediary processes and mediates conflicts between multiple sources by applying predefined resolution strategies, allowing complete data aggregation from multiple sources without directly exposing the complexity of conflict resolution to the rest of the system.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Measurement precision

If comprehensive endpoint data structures are maintained, then update accuracy is improved, but data storage requirements increase

Engineering Contradiction:
Improveupdate accuracyVSAvoiddata storage requirements
Core Design Contradiction:
Measurement precisionVSQuantity of substance

Solution Approach 1:

The system applies partial action by maintaining only the necessary properties and packages for each endpoint type in its data structure. Rather than storing all possible properties universally, it stores only the relevant properties defined in the endpoint's template, reducing storage requirements while maintaining sufficient accuracy for updates.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system uses universal data structure templates that can represent multiple endpoint types through configuration rather than separate data structures for each type. This multi-functionality allows the same template framework to handle diverse endpoints, reducing overall storage requirements compared to maintaining separate comprehensive structures for each endpoint type.

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

Data Source

PatentEP3335164B1Management of upgradeable endpoints
Publication Date: 2020.09.16 BLACKBERRY LTD
  • EP3335164B1 patent drawingFigure 1
  • EP3335164B1 patent drawingFigure 2
  • EP3335164B1 patent drawingFigure 3

AI summary

Data structures are stored in an endpoint data store. Each data structure represents an endpoint having one or more components, each component having one or more arbitrary properties. Any packages installed on the components are represented in the data structures. Representations of the arbitrary properties within the data structure are aggregated from multiple sources, and conflict resolution methods are described.