Dynamic Software Architecture for Real-Time Device Personalization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current manufacturing processes for personalizing communication devices face challenges due to divergences and discrepancies among different devices, leading to increased development time, validation requirements, and the risk of introducing new bugs or errors during software updates, as existing software applications struggle to accommodate diverse protocols, security mechanisms, and hardware configurations.

Innovation Solution

A dynamic and real-time configurable software architecture that utilizes a message controller and message flow control engine to compose and process personalized messages for communication devices, allowing for simultaneous real-time personalization across different product and factory configurations, and enabling the software to operate as either a server or client, thereby reducing development and testing time.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If additional software applications are developed to address divergences and discrepancies among different devices, then the ability to handle diverse device configurations improves, but development time increases significantly

Engineering Contradiction:
Improveability to handle diverse device configurationsVSAvoiddevelopment time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements a universal personalization software application that can handle multiple device configurations, protocols, and security mechanisms through a single unified codebase. The system uses configurable parameters and runtime adaptation to serve multiple device types without requiring separate software applications for each device variant, thereby achieving versatility without proportional increases in development time.

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

Solution Approach 2:

The system employs dynamic configuration capabilities that allow the software to adapt its behavior at runtime based on the specific device being personalized. Configuration parameters can be modified without code changes, and the system can dynamically load different protocol handlers and security mechanisms based on device identification, enabling flexibility while maintaining a stable core codebase.

Inventive Principle:
Principle #15Dynamics

2Reliability

If validation and test code is added for software application verification, then software reliability improves, but development and testing time increases

Engineering Contradiction:
Improvesoftware reliabilityVSAvoidtesting time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent utilizes virtual device models and simulation environments that create simplified copies of actual devices for testing purposes. These virtual representations allow comprehensive validation of personalization software without requiring physical devices, enabling thorough testing while reducing the time and resources needed for hardware-based verification.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system implements automated regression testing and validation procedures that are executed continuously during the development process rather than as separate phases. Test cases are automatically generated and run against code changes, identifying issues early before they propagate through the development cycle, thereby improving reliability without adding significant time overhead.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If code changes are made to accommodate manufacturing parameter changes, then adaptability to new requirements improves, but the risk of introducing bugs and errors increases

Engineering Contradiction:
Improveadaptability to manufacturing parameter changesVSAvoidrisk of introducing bugs
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent structures the personalization software into modular components with clearly defined interfaces. Configuration parameters are separated from core logic, allowing manufacturing parameter changes to be made in isolated configuration sections without affecting the stability of the underlying code. This segmentation enables adaptability while containing the risk of bugs to specific modules.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system introduces a configuration layer that acts as an intermediary between manufacturing parameters and the core personalization logic. This intermediate configuration interface allows parameter changes to be made without direct code modifications, and includes validation mechanisms that prevent invalid configurations from reaching the execution layer, thereby reducing the risk of introducing bugs.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Adaptability or versatility

If separate software updates and deployments are performed for manufacturing changes, then customization capability improves, but productivity decreases due to additional deployment time and resources

Engineering Contradiction:
Improvecustomization capabilityVSAvoiddeployment efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent combines multiple personalization functions and device-specific configurations into a single unified software deployment. Rather than requiring separate updates for different device types or manufacturing changes, the system consolidates these into one comprehensive update package that can be deployed simultaneously across all target devices, improving productivity while maintaining customization capability through unified configuration management.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS8387011B2Method and apparatus for a dynamic and real-time configurable software architecture for manufacturing personalization
Publication Date: 2013.02.26 ARRIS ENTERPRISES LLC
  • US8387011B2 patent drawing
  • US8387011B2 patent drawing
  • US8387011B2 patent drawing

AI summary

A process receives a personalization request to personalize a communication device. Further, the process provides the personalization request to a message controller that composes a message having personalization information with a message composer engine according to a set of rules and configures one or more communication parameters for the message with a message flow control engine according to the set of rules. The set of rules indicates a distributed environment set of files that the message composer engine and the message flow control engine utilize in a distributed environment, and a centralized environment set of files that the message composer engine and the message flow control engine utilize in a centralized environment.