MBOA MAC Resource Allocation via Protocol-Aware Idle Time
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional resource allocation methods in home network environments, such as MBOA MAC, are ineffective in multiple-protocol settings as they prioritize resource competition based on data type, leading to difficulties in ensuring priority for applications using certain protocols like IEEE 1394 over others, such as USB, when they have higher priority but share the same data type.
Innovation Solution
A resource allocation method in the PCA period of MBOA MAC that allocates an AIFS value based on the data type of the requested resource, followed by a back-off timer period where an idle time value is determined by the application protocol, allowing devices to compete for resources based on protocol type, thereby ensuring higher priority protocols have an advantage in resource acquisition.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If resource competition is based on data type priority, then data transmission efficiency is improved, but protocol priority cannot be guaranteed in multiple-protocol environments
Solution Approach 1:
The patent segments the priority determination into two stages: first by data type (AC_VO, AC_VL, AC_BE, AC_BK) and then by protocol type within each data type category. This segmentation allows the system to maintain data type-based efficiency while adding protocol-level priority control, resolving the contradiction between productivity and reliability.
Solution Approach 2:
The patent applies local quality by assigning different idle time values based on specific protocol types (e.g., IEEE 1394 vs. USB) within the same data type category. This allows tailored priority treatment for different protocols, ensuring that high-priority protocols like IEEE 1394 receive preferential treatment while maintaining overall data type-based efficiency.
2Ease of operation
If AIFS value is allocated based on data type, then resource competition is simplified, but protocol-specific priority control is lost
Solution Approach 1:
The patent introduces dynamics by making the idle time value adjustable based on both data type and protocol type. The system dynamically selects idle time values from predefined ranges corresponding to different protocol types, enabling flexible adaptation to various protocol requirements while maintaining a structured competition framework.
Solution Approach 2:
The patent changes the parameter of idle time value based on protocol type identification. By mapping different protocol types to specific idle time ranges (e.g., IEEE 1394 to shorter idle times, USB to longer idle times), the system achieves protocol-specific priority control without fundamentally changing the resource competition mechanism.
3Productivity
If shorter idle time is assigned to higher priority data types, then resource acquisition probability increases, but lower priority protocols are disadvantaged
Solution Approach 1:
The patent applies local quality by differentiating idle time values specifically for lower priority protocols within their data type categories. For example, USB protocols receive longer idle times compared to IEEE 1394 protocols, creating localized priority adjustments that prevent harmful disadvantages while maintaining overall productivity.
Solution Approach 2:
The patent implements feedback by continuously monitoring resource allocation outcomes and adjusting idle time values based on protocol type performance. This feedback mechanism ensures that lower priority protocols receive appropriate compensation through extended idle times, preventing them from being unfairly disadvantaged while maintaining system efficiency.
Data Source
AI summary
A resource allocation method for performing resource competition between protocols based on a protocol in a home network environment using multiple protocols is provided. In the resource allocation method, a request of using a resource is received from an external device. An AIFS value is allocated according to a data type of the resource requested from the device. Then, the resource is not provided to the device for an AIFS period. After passing the period of the AIFS value, a back-off timer period is entered. In the back-off timer period, an application protocol of the external device requesting the resource is identified, and an idle time value is allocated according to a type of the identified protocol. Then, a corresponding resource is provided to the first device coming out of the allocated idle time.