RFID Edge Server Dynamic Configuration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

RFID edge servers face challenges in dynamically configuring multiple RFID readers without interrupting software application operations and managing large volumes of RFID data effectively, particularly in supporting different vendor-specific configurations and filtering requirements.

Innovation Solution

An RFID edge server system that uses metadata-based descriptions to configure RFID readers dynamically, allowing for updates without restarting the readers or the software application, and provides EPC code provisioning using business rules to support various client sites, enabling efficient data filtering and management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If RFID readers are configured dynamically without restarting, then system availability and operational continuity are improved, but configuration complexity and management difficulty increase

Engineering Contradiction:
Improvesystem availabilityVSAvoidconfiguration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements dynamic configuration capability where RFID readers can be reconfigured without restarting. The edge server maintains connection to readers and applies configuration changes in real-time, allowing the system to adapt to changing requirements while maintaining continuous operation. This resolves the contradiction by enabling flexible configuration (improving availability) while managing complexity through automated configuration mechanisms.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The edge server acts as an intermediary between configuration management systems and RFID readers. It receives configuration requests, validates them against business rules, and applies changes to readers without requiring reader restarts. This intermediary layer abstracts the complexity from the reader side while maintaining reliability through continuous operation.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If multiple vendor-specific RFID readers are supported with different configurations, then system versatility and adaptability are improved, but device complexity and management overhead increase

Engineering Contradiction:
Improvemulti-vendor supportVSAvoidmanagement overhead
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The edge server implements a universal configuration management framework that can handle multiple vendor-specific RFID readers through a single interface. It maintains a registry of supported reader types and applies appropriate vendor-specific configurations automatically, allowing one system to manage diverse hardware from different vendors without increasing operational complexity.

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

Solution Approach 2:

The system manages vendor-specific differences through parameter transformations. The edge server receives high-level configuration parameters and automatically translates them into vendor-specific settings for each reader type. This parameter abstraction layer enables multi-vendor support while keeping management simple, as administrators work with unified parameters rather than vendor-specific details.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If large volumes of RFID data are processed and filtered in real-time, then data processing capability and system responsiveness are improved, but computational resources and processing complexity increase

Engineering Contradiction:
Improvedata processing capabilityVSAvoidprocessing complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments data processing into multiple stages: raw data collection at readers, initial filtering at the edge server, and business-rule-based processing at the application layer. By dividing the processing workload and filtering data early at the edge server, the system handles large volumes of data without overwhelming computational resources, as only relevant data is processed further.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The edge server performs preliminary filtering and preprocessing of RFID data before it reaches application systems. It applies basic filters and transformations in advance, reducing the volume of data that requires complex business-rule processing. This preliminary action maintains system responsiveness while managing processing complexity through staged data handling.

Inventive Principle:
Principle #10Preliminary action

4Adaptability or versatility

If EPC code provisioning is managed dynamically across multiple client sites, then system flexibility and adaptability are improved, but configuration management complexity increases

Engineering Contradiction:
Improveprovisioning flexibilityVSAvoidconfiguration management
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The EPC provisioning system implements feedback mechanisms where client sites report their EPC code requirements and usage patterns back to the central management system. This feedback enables dynamic adjustment of provisioning policies and code allocation strategies, allowing the system to adapt to changing needs while simplifying management through automated feedback-driven decisions rather than manual configuration.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8890662B2EPC provisioning system
Publication Date: 2014.11.18 ORACLE INT CORP
  • US8890662B2 patent drawing
  • US8890662B2 patent drawing
  • US8890662B2 patent drawing

AI summary

An EPC provisioning system comprising an EPC server can dynamically provide EPC code blocks for one product to multiple client sites. The EPC server can use business rules to determine the EPC codes for the multiple client sites.