Wireless Packet Scheduler for QoS Compliance in MANETs

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In mobile ad hoc networks (MANETs), ensuring Quality-of-Service (QoS) requirements for packet transmission is challenging due to dynamic topology, lack of infrastructure, and limited resources, which affects the reliability and timeliness of data delivery.

Innovation Solution

A node in a wireless communication network equipped with a scheduler and media access controller that calculates and updates the transmission order of packets based on remaining delay, expected delay, and slack variables, ensuring compliance with service level agreements by adjusting holding times and prioritizing packets according to their QoS metrics.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If packets are transmitted immediately upon arrival at each node, then the transmission speed and responsiveness are improved, but the Quality-of-Service requirements (delay constraints) cannot be guaranteed

Engineering Contradiction:
Improvepacket transmission speedVSAvoidQoS requirement compliance
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The patent applies preliminary action by calculating and setting the holding time for each packet before it is actually transmitted. The scheduler computes the holding time based on QoS parameters (maximum allowable end-to-end delay, number of remaining hops, reserved rate) and packet characteristics (length) in advance, then holds the packet for this calculated duration before transmission. This ensures that packets are transmitted at the optimal moment to meet delay constraints while maintaining efficient throughput.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If packets are held for extended periods to meet delay constraints, then QoS reliability is improved, but the overall network throughput and productivity deteriorate

Engineering Contradiction:
ImproveQoS requirement complianceVSAvoidnetwork throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies parameter changes by dynamically adjusting the holding time parameter for each packet based on multiple variables including the maximum allowable end-to-end delay, number of remaining hops, reserved rate of the flow, and packet length. Rather than using a fixed holding time or simple FIFO queuing, the system changes the holding time parameter adaptively for each packet to optimize both delay compliance and network throughput.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If the network maintains unused routes to all destinations at all times, then routing reliability is improved, but the network overhead and resource consumption increase significantly

Engineering Contradiction:
Improverouting reliabilityVSAvoidrouting overhead
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent applies dynamics by implementing reactive (on-demand) routing where routing information is collected only when necessary and only to destinations for which routes are needed. The network dynamically discovers and maintains routes as packets are transmitted, rather than maintaining static routes to all possible destinations. This adaptive routing approach reduces routing overhead and energy consumption while maintaining reliability for actual communication needs.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS7852763B2System and method for determining a transmission order for packets at a node in a wireless communication network
Publication Date: 2010.12.14 BAE SYSTEMS INFORMATION ANDELECTRONIC SYSTEMS INTEGRATION INC
  • US7852763B2 patent drawing
  • US7852763B2 patent drawing
  • US7852763B2 patent drawing

AI summary

A wireless communications network comprising a plurality of nodes and effective to provide quality of service requirements for packets being transmitted. An ingress node calculates variables based on quality of service requirements and places those variables in a header of a packet to be transmitted. The packet is then transmitted to a core node. The core node reads the variables in the packet and calculates a holding time for the packet based on the variables and the quality of service requirements.