| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
This section was moved to layer 3 + Support based on the discussion at the Plenary in July.4.5.6 Call BlockingCurrent text “When the bandwidth required for a call cannot be reserved, the system will provide signaling to support call blocking.” Proposed Change When MAC/PHY resources cannot be allocated to support the QOS characterstics defined as “high priority bandwidth reserved” are not available the MAC/PHY API will provide messaging to the higher layer to support blocking. Example VOIP allowing the higher layer application to provide a busy signal blocking the call and providing feedback. The QOS must allow the assignment of specific resources to the QOS class so that the MAC/PHY may make this determination. Reasoning Certain types of traffic like VOIP, Streaming Video, etc. require committed resources to function correctly. It is important that the MAC/PHY have the ability to support them at a higher layer. The QOS section needs to be able to provide bandwidth
4.5.6 Call BlockingWhen the bandwidth required for a call cannot be reserved, the system will provide signaling to support call blocking. Comment Rationale: The sentence related to call blocking should be removed because call blocking is an application layer specific issue. The Requirements document should specify the classes of supported QoS, but application-specific exception handling should not be included in the document.
Call blocking or other exception handling techniques should be handled at a higher layer for any application that requires special QOS treatment. If there is an application (such as Void) that requires special QoS treatment, the application shall request it of the air interface via an API. If the air interface cannot provide the desired QoS, it shall inform the application of that fact via the API. It is up to the application to take the appropriate action, e.g., "blocking" the call. <John Fan 7/23/03>
David S. McGinniss Sprint Broadband Wireless Group Principal Engineer II (630) 926-3184
|