Low Latency Subnet for High Priority Wireless Messages
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
High priority messages experience significant latency in multiple-access wireless networks like Link 16 due to heavy usage imbalances in subnets, leading to inefficient bandwidth utilization and potential delays in critical communications.
Innovation Solution
Designating a low latency subnet for high priority messages, allowing nodes to transmit on this subnet with minimal latency without affecting standard priority message traffic, using a contention-based approach and message acknowledgement protocols to ensure timely delivery and collision detection.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a contention protocol is used for timeslot access in subnets with light message traffic, then node operation simplicity is improved, but message transmission latency increases due to frequent collisions and retransmissions
Solution Approach 1:
The network is segmented into multiple subnets with different access protocols. Light-traffic subnets use contention protocols for simplicity, while heavy-traffic subnets use dedicated timeslot assignments to reduce latency. This segmentation allows each subnet to optimize for its specific traffic characteristics.
Solution Approach 2:
The system dynamically switches between contention and dedicated access modes based on traffic conditions. Nodes can transition from contention-based operation to dedicated timeslot operation when message traffic volume increases, optimizing performance adaptively.
2Reliability
If dedicated timeslots are assigned to member nodes in subnets with heavy message traffic, then collision avoidance is improved, but message transmission latency increases due to wide spacing between timeslots
Solution Approach 1:
The network is divided into subnets based on traffic intensity. Heavy-traffic subnets receive dedicated timeslot assignments to eliminate collisions, while light-traffic subnets use contention protocols. This segmentation optimizes both reliability and latency for different traffic conditions.
Solution Approach 2:
Different access control qualities are applied to different subnets. Dedicated timeslot assignment is applied locally to subnets with heavy traffic where collision avoidance is critical, while contention protocols are used in subnets where latency is less critical and simplicity is preferred.
3Productivity
If multiple subnets are created in a multi-access wireless network to enable efficient communications, then communication efficiency is improved, but bandwidth utilization efficiency deteriorates due to uneven usage across subnets
Solution Approach 1:
The system dynamically manages subnet usage by allowing nodes to switch between subnets based on traffic conditions. When a subnet becomes overloaded, nodes can migrate to less busy subnets, dynamically balancing the load and optimizing overall bandwidth utilization.
Solution Approach 2:
The system changes operational parameters such as timeslot assignment and access protocol based on traffic volume. When traffic conditions change, nodes adjust their behavior dynamically, switching between contention and dedicated access modes to optimize bandwidth usage.
Data Source
Figure 1
Figure 2A~2C
Figure 3
AI summary
A method is disclosed for minimizing latency for high priority messages without sacrificing subnet bandwidth in a wireless, multiple access network such as Link 16. Nodes are able to simultaneously receive messages on at least two subnets, one of which is designated as a low latency ("LL") subnet that transmits messages immediately on a contention access basis. A message acknowledgement protocol can be implemented and high priority messages that fail due to collisions or other reasons can be retransmitted. Jitter can be used to detect collisions. Embodiments include a plurality of "standard" and/or LL subnets designated for messages of varied urgency. High priority messages can reserve an acknowledgement timeslot for use only by the message recipient. Link 16 embodiments implement CMN-4, whereby the LL subnet is one of four subnets monitored by each node. Link 16 latencies in the LL network can be limited to less than 40 msec.