Forwarder Device Network Coupling Scheduling

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Efficient data transfer management between infrastructure-based and ad-hoc networks is challenging due to the lack of a centralized hub in ad-hoc networks, leading to difficulties in coupling different networks and ensuring Quality of Service (QoS) requirements.

Innovation Solution

A forwarder device with a data transmission scheduling management function that operates on different frequency channels, acting as an interface between infrastructure-based and ad-hoc networks, manages data packet transfer by distinguishing between multi-hop and single-hop traffic, and uses a scheduling mechanism to balance processor loads and prevent bandwidth issues.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a forwarder device is implemented to interface between infrastructure-based and ad-hoc networks, then network coupling capability is improved, but data transmission management complexity increases

Engineering Contradiction:

Improvenetwork coupling capabilityVSAvoiddata transmission management complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The forwarder device segments data transmission management into distinct functional components: a scheduling management function that handles queue management and traffic classification, and a physical layer function that handles frequency switching. This segmentation allows each component to specialize in specific tasks, reducing overall system complexity while maintaining network coupling capability between infrastructure-based and ad-hoc networks.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The forwarder device acts as an intermediary between infrastructure-based networks (with central hubs) and ad-hoc networks (without central hubs). It mediates data transmission by implementing scheduling management functions that coordinate traffic from multiple sources to a common output, enabling seamless interaction between the two network types without requiring them to directly manage each other's complexity.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If multi-hop routing is used in ad-hoc networks, then network flexibility is improved, but data packet management difficulty increases

Engineering Contradiction:

Improvenetwork flexibilityVSAvoiddata packet management difficulty

Core Design Contradiction:

Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The scheduling management function implements feedback mechanisms to monitor and adjust data packet transmission in real-time. It tracks packet status, transmission success rates, and queue conditions to dynamically modify routing decisions and packet forwarding priorities, making the management of multi-hop routing packets more controllable and measurable.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system performs preliminary actions by pre-establishing routing paths and packet queues before actual data transmission occurs. The scheduling management function prepares packet handling protocols and allocates transmission resources in advance, reducing the complexity of real-time packet management in flexible ad-hoc networks.

Inventive Principle:

Principle #10Preliminary action

3Reliability

If data transmission scheduling management function is implemented, then QoS is improved, but processor load increases

Engineering Contradiction:

ImproveQoSVSAvoidprocessor load

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

The scheduling management function uses periodic action by implementing cyclic scheduling intervals where it periodically checks and manages data queues, adjusts transmission priorities, and coordinates packet forwarding. This periodic management approach maintains QoS requirements while distributing the processor load over time rather than requiring continuous high-intensity processing.

Inventive Principle:

Principle #19Periodic action

Solution Approach 2:

The system applies partial action by managing only the essential scheduling tasks required for QoS maintenance, such as priority queue management and traffic classification, rather than implementing comprehensive real-time optimization. This selective approach achieves acceptable QoS while significantly reducing processor load requirements.

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentUS9119227B2Network array, forwarder device and method of operating a forwarder device

Publication Date: 2015.08.25 KONINKLIJKE PHILIPS NV

AI summary

A network array (100) comprises a first network (101) having a plurality of first nodes (103, 104, 109), comprises a second network (102) having a plurality of second nodes (106, 109), and comprises a forwarder node (109). The forwarder node (109) constitutes one of the first nodes (103, 104, 109) and constitutes one of the second nodes (106, 109) to form a communication interface between the first network (101) and the second network (102). The forwarder node (109) has an implemented data transmission scheduling management function capable of distinguishing between data to be transmitted between the first network (101) and the second network (102) and data to be transmitted within the first network (101) or within the second network (102). The forwarder node (109) is adapted to communicate with the first network (101) using a first operation frequency and is adapted to communicate with the second network (102) using a second operation frequency which is different from the first operation frequency.