Network Packet Transmission Reliability via QoS-Based Power Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network data transmission methods do not effectively enhance reliability, particularly in wireless networks, where interference leads to unreliable transmission quality, and existing quality of service (QoS) fields only prioritize packets but do not address transmission reliability.
Innovation Solution
The method involves identifying data types based on QoS fields to adapt transmission characteristics such as data rate, transmission power, and packet size, allowing high-priority packets to be transmitted with higher power and reduced retry attempts, while low-priority packets may not be retried, thereby optimizing transmission reliability without compromising throughput.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If transmission power is increased to improve reliability, then packet error rate decreases, but average transmission power exceeds regulatory limits
Solution Approach 1:
The patent applies local quality by differentiating transmission power allocation based on packet priority. High-priority packets receive elevated transmission power to ensure reliable delivery, while low-priority packets use reduced power. This selective power allocation improves overall transmission reliability for critical data without causing the average transmission power to exceed regulatory limits.
Solution Approach 2:
The patent changes the transmission power parameter dynamically based on packet priority classification. The system adjusts power levels adaptively - increasing power for high-priority packets and decreasing power for low-priority packets - thereby resolving the contradiction between maintaining high reliability and staying within average power constraints.
2Reliability
If retry attempts are increased for low-priority packets, then transmission reliability improves, but throughput decreases
Solution Approach 1:
The patent segments the data traffic into high-priority and low-priority packets based on QoS fields. Different transmission strategies are applied to each segment: high-priority packets receive enhanced reliability measures including retry attempts, while low-priority packets use best-effort transmission without retries. This segmentation resolves the contradiction by ensuring reliability for critical packets while maintaining throughput for non-critical packets.
Solution Approach 2:
The patent applies partial action by providing enhanced reliability measures (retry attempts) only to the extent necessary for high-priority packets, rather than applying them universally. This selective approach ensures that throughput is not unnecessarily reduced for low-priority traffic while still achieving reliable delivery for high-priority data.
3Productivity
If QoS fields are used for packet prioritization, then network handling efficiency improves, but transmission reliability does not improve
Solution Approach 1:
The patent transforms the static QoS prioritization mechanism into a dynamic system that adapts transmission parameters based on packet priority. The system dynamically adjusts transmission power, data rate, and retry behavior according to the QoS field values, thereby extending the functionality of QoS fields from mere prioritization to active reliability management.
Solution Approach 2:
The patent extends the functionality of QoS fields to serve multiple purposes: packet prioritization, transmission power control, data rate adaptation, and retry management. This multi-functionality allows the existing QoS infrastructure to simultaneously improve both network handling efficiency and transmission reliability without requiring separate mechanisms.
Data Source
AI summary
In one example embodiment, a method is provided and includes identifying a first data type of a first payload of a first data packet to be transmitted as part of a flow, where the first data type is identified by evaluating a quality of service (QoS) field, and setting an acknowledgement flag based on the first data type; the acknowledgement flag to indicate that an acknowledgement is not required from a receiving device such that a network device avoids retransmitting a first outgoing frame when the acknowledgement is not received for the first outgoing frame. In more particular instances, the method can include where the acknowledgement flag is in the first outgoing frame.