Radiotag Multi-Platform Service Stacks for Seamless Beaconing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing radiotags are typically configured to operate with a single communication platform, limiting their compatibility with multiple competing platforms, and face challenges in efficiently managing multiple service stacks and user input for platform selection.

Innovation Solution

A radiotag with a pruned service stack and common interface architecture allows simultaneous support for multiple communication platforms by reducing redundant service stack sizes and using a common interface, along with automated platform selection and efficient resource management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a radiotag is configured to support multiple communication platforms with full service stacks, then platform compatibility is improved, but device complexity and resource consumption increase

Engineering Contradiction:

Improveplatform compatibilityVSAvoidservice stack complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The service stack is segmented into multiple independent pruned service stacks, each dedicated to a specific communication platform. This segmentation allows the radiotag to maintain separate, optimized service stacks for different platforms rather than one monolithic complex stack, reducing overall complexity while preserving multi-platform compatibility.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Redundant and platform-specific portions are extracted from complete service stacks to create pruned versions. Each pruned service stack contains only the essential components needed for its specific platform, removing unnecessary code and resources that would increase device complexity if included in all stacks.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 3:

The radiotag device is designed with universal multi-functionality by incorporating multiple pruned service stacks that can be selectively activated. The device can function with different communication platforms by loading the appropriate pruned service stack, achieving versatility without requiring all service stacks to run simultaneously.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If a radiotag includes complete service stacks for multiple platforms, then platform compatibility is improved, but memory usage and processing resources increase

Engineering Contradiction:

Improvemulti-platform supportVSAvoidfirmware size

Core Design Contradiction:

Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

Unnecessary portions are extracted from complete service stacks to create compact pruned versions. Each pruned service stack contains only the minimal required components for its specific platform, significantly reducing the total firmware size stored in the radiotag's memory while maintaining the ability to support multiple platforms.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

Instead of including complete service stacks for all platforms (excessive action), the radiotag uses partial service stacks that contain only the essential functionality needed for each platform. This partial inclusion approach reduces memory usage while providing sufficient multi-platform support.

Inventive Principle:

Principle #16Partial or excessive action

3Measurement precision

If the radiotag checks all service stacks for bonding information, then platform selection accuracy is improved, but startup time increases

Engineering Contradiction:

Improveplatform detection accuracyVSAvoidstartup time

Core Design Contradiction:

Measurement precisionVSLoss of time

Solution Approach 1:

Bonding information is pre-stored in the service configuration data storage for each supported communication platform. During startup, the radiotag performs a quick check of this pre-organized bonding information rather than extensively analyzing all service stacks, reducing startup time while maintaining accurate platform detection.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The platform detection process is segmented by checking bonding information for each pruned service stack separately in a structured manner. This segmentation allows efficient organization and retrieval of platform-specific bonding information, improving detection accuracy while minimizing the time required through systematic checking.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS20260043885A1Radiotag devices with seamless multi-platform support

Publication Date: 2026.02.12 PB INC

AI summary

In some embodiments, a computer-implemented method of operating a radiotag with a communication platform of two or more supported communication platforms is provided. An application service of the radiotag instantiates a plurality of service stack threads. Each service stack thread determines whether bonding information for a communication platform associated with the service stack thread is stored in a service configuration data storage of the radiotag.For each service stack thread, in response to determining that the bonding information for the communication platform associated with the service stack thread is not stored in the service configuration data storage, the service stack thread enters a waiting state; and in response to determining that the bonding information for the communication platform associated with the service stack thread is stored in the service configuration data storage, the service stack thread generates one or more beacons in a format for the associated communication platform.