Variable Bandwidth Request Header for Wireless Overhead Reduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional broadband wireless access systems incur unnecessary overhead due to the fixed format of bandwidth request headers, which do not efficiently manage varying uplink bandwidth requests.
Innovation Solution
A method is introduced to determine the bandwidth request type based on the requested uplink bandwidth size, generating a bandwidth request message with a variable format, including options for per-connection, per-QoS, and per-mobile-station requests, and utilizing random access codes mapped to header types for optimized transmission.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a fixed format bandwidth request header is used to ensure simple structure, then device complexity is reduced, but bandwidth request overhead increases due to unnecessary fields for small requests
Solution Approach 1:
The bandwidth request header is segmented into multiple format types (Format 1 for small requests ≤2KB, Format 2 for large requests >2KB). Each format contains only the necessary fields for its specific use case, eliminating unnecessary overhead while maintaining structural simplicity within each segment.
Solution Approach 2:
The header format dynamically adapts based on the bandwidth request size. The system selects Format 1 or Format 2 according to whether the requested bandwidth exceeds 2KB, making the header structure flexible rather than fixed, thereby optimizing overhead for different request scenarios.
2Adaptability or versatility
If a bandwidth request header includes all possible fields for maximum requested bandwidth (512KB or 2KB), then adaptability is improved, but bandwidth request overhead increases due to unnecessary fields for smaller requests
Solution Approach 1:
The header is divided into two segmented formats: Format 1 includes only essential fields (BR, CID, HCS) for small requests, while Format 2 includes additional fields (UL Tx power, HCS) for large requests. This segmentation ensures adaptability to different request sizes without including unnecessary fields in each case.
Solution Approach 2:
Different header formats provide different field compositions tailored to local requirements: Format 1 is optimized for small requests with minimal fields, while Format 2 is optimized for large requests with additional control fields. Each format has the appropriate quality and detail level for its specific bandwidth request scenario.
Data Source
AI summary
A method for requesting a bandwidth by a message having a variable format is disclosed. The method includes determining a bandwidth request type according to a size of an uplink bandwidth requested by a mobile station, generating a bandwidth request message having a header format according to the determined bandwidth request type, and transmitting the bandwidth request message to a base station. The determined bandwidth request type is one of a bandwidth request per connection, a bandwidth request per Quality of Service (QoS), and a bandwidth request per mobile station.


