| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Current Section4.5.6 Call Blocking (Open)Editor’s note: This section is proposed for deletion because it is viewed as already being included in section 4.4.1. [When the bandwidth required for a call cannot be reserved, the system will provide signaling to support call blocking.] [No sentence]
[When MAC/PHY resources cannot be allocated to support the QOS characteristics 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.] Proposed text When bandwidth required for a call requiring “high priority bandwidth reserved” like (VOIP) is not available, the system shall provide signaling to the upper layers to support call blocking. Rational While blocking is a higher layer function it can not be accomplished with out real-time signaling form the MAC/PHY. It has been argued that this should be deleted because it is covered in section 4.4.1. I do not believe it is covered in that section. The following text
“Service classes of service and QoS parameters of all services may be translated into a common set of parameters defined by 802.20. A QoS based IP network may employ the Resource Reservation Protocol (RSVP) to signal the allocation of resources along a routed IP path.”
This does not indicate that the system should pass resource availability information for reserved bandwidth but rather that it should provide information to reserve end to end bandwidth for a call already set up. This function needs to be provided to layer 3+ and belongs in this section.
My first
David S. McGinniss Sprint Broadband Wireless Group Principal Engineer II (630) 926-3184
|