Endpoint Release Deployment via Property-Based Filtering
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Managing software updates for complex systems like modern motor vehicles and IoT devices is challenging due to the unknown properties and capabilities of the endpoints, leading to difficulties in deploying upgrades effectively.
Innovation Solution
A data model and management system that uses propertyKey-propertyValue pairs to represent endpoint properties, groups endpoints based on criteria, and deploys releases to targeted groups using a Query Grammar for filtering and prioritization, ensuring efficient and accurate software updates across diverse systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a data model with propertyKey-propertyValue pairs is used to represent endpoint properties, then the system can handle arbitrary properties and previously unknown endpoints, but the device complexity increases due to the need for filtering and prioritization mechanisms
Solution Approach 1:
The system segments the endpoint properties into structured propertyKey-propertyValue pairs, allowing independent handling and filtering of each property. This segmentation enables the complex data model to be managed through modular filtering operations rather than monolithic processing.
Solution Approach 2:
The patent introduces an intermediary filtering mechanism that sits between the raw property data and the release deployment decision. This intermediary layer processes propertyKey-propertyValue pairs through Query Grammar rules, simplifying the overall system complexity by isolating the filtering logic.
2Measurement precision
If grouping mechanisms are implemented to target specific endpoint groups for releases, then the precision of release targeting improves, but the difficulty of detecting and measuring endpoint properties increases
Solution Approach 1:
The system performs preliminary grouping of endpoints based on their properties before release deployment. By pre-organizing endpoints into groups using property-based criteria, the system simplifies the measurement and detection process during actual release targeting, as the grouping logic is established in advance.
Solution Approach 2:
The patent changes the parameter representation from raw, unstructured endpoint properties to structured propertyKey-propertyValue pairs with associated filters. This parameter transformation makes endpoint properties more detectable and measurable by providing a standardized format for querying and filtering.
3Productivity
If Query Grammar filtering is applied to prioritize releases for different endpoint groups, then the efficiency of release deployment improves, but the device complexity increases due to multiple filtering levels
Solution Approach 1:
The patent adds a dimensional layer to the filtering process by introducing Query Grammar rules that operate on propertyKey-propertyValue pairs. This additional dimension allows efficient prioritization across multiple filtering levels without linearly increasing complexity, as the grammar provides a systematic framework for multi-level filtering.
Solution Approach 2:
The Query Grammar mechanism serves multiple functions simultaneously: it filters endpoints, prioritizes releases, and manages property-based grouping. This multi-functionality reduces overall system complexity by consolidating what would otherwise require separate mechanisms into a single universal filtering framework.
Data Source
AI summary
Transport information is to be used by an endpoint to obtain one or more packages comprised in a deployed release. The transport information is sent in a single message that identifies the deployed release and the one or more packages. The transport information may include allowed bearer settings and transport settings. Release parameters to be used by the endpoint in connection with the deployed release are determined and included in the single message. The message may include one of the packages as streamed inline content. The message may identify one of the packages via a network address of a file of that package. The message may identify one of the packages via an indication of where in local removable storage to find a file of that package, the local removable storage being local to the endpoint.


