Managing wireless resources
View Patent ↗Various embodiments provide for the management of wireless resources, which can reduce call blocking by allowing high priority services, under suitable conditions, to use resources allocated to low priority services. Thus high priority services can pre-empt the usage of wireless resources by low priority services. This has the advantage of reducing call blocking for high priority calls, while permitting low priority calls to have more access to radio resources than conventional systems with the same call blocking rate. Thus a base station can implement a preemption mechanism that would reclaim Walsh Code and Forward Power resources from an active Supplemental Channel (SCH) burst in order to accommodate incoming Fundamental Channel (FCH) requests.
1. A system, comprising:
at least one processor; and
at least one processor-readable storage medium storing instructions for execution by the at least one processor, the instructions executable to:
receive a request for a data session;
determine, responsive to the request, whether sufficient Walsh code resources and sufficient power resources are available to serve the data session; and
allocate available Walsh code resources and power resources to the data session responsive to determining that sufficient resources are available;
allocate pre-empted Walsh code resources and power resources to the data session responsive to determining that insufficient resources are available, the pre-empted Walsh code resources and power resources made available by pre-emption of a lower priority data session that does not have a real-time requirement, the lower priority data session selected for pre-emption from a plurality of lower priority data sessions based at least in part on a quality of service priority indicator of the lower priority data session; and
refuse the request for the data session upon determining that pre-empting the lower priority data session would not make sufficient resources available for the data session.
2. The system of claim 1 , wherein the allocated pre-empted Walsh code resources and power resources comprise at least a portion of resources made available by pre-emption of the lower priority data session and the lower priority data session having a lower priority than the data session.
3. The system of claim 1 , wherein the pre-emption of the lower priority data session comprise instructions executable to decrease resources allocated to the lower priority data session by sufficient resources to serve the data session.
4. The system of claim 1 , wherein the data session is more delay-sensitive than the lower priority data session.
5. The system of claim 1 , wherein the data session includes a real-time requirement.
6. The system of claim 1 , wherein the pre-emption is based at least in part on determining that pre-empting the lower priority data session would make sufficient resources available for the data session.
7. The system of claim 1 , wherein:
the instructions further comprise instructions executable by the at least one processor to support the plurality of lower priority data sessions on a supplementary channel (SCH).
8. The system of claim 7 , the instructions further executable to:
evaluate fundamental channel (FCH) usage; and
block use of the SCH only when the FCH usage has not exceeded an upper limit.
9. A method comprising:
receiving a request for a data session;
determining, responsive to the request, whether sufficient Walsh code resources and sufficient power resources are available to serve the data session; and
allocating available Walsh code resources and power resources to the data session responsive to determining that sufficient resources are available;
allocating pre-empted Walsh code resources and power resources to the data session responsive to determining that insufficient resources are available, the pre-empted Walsh code resources and power resources made available by pre-emption of a lower priority data session that does not have a real-time requirement, the lower priority data session selected for pre-emption from a plurality of lower priority data sessions based at least in part on a quality of service priority indicator of the lower priority data session; and
refusing the request for the data session upon determining that pre-empting the lower priority data session would not make sufficient resources available for the data session.
10. The method of claim 9 , wherein the allocated pre-empted Walsh code resources and power resources comprise at least a portion of resources made available by pre-emption of the lower priority data session and the lower priority data session having a lower priority than the data session.
11. The method of claim 9 , wherein the pre-emption of the lower priority data session comprises decreasing resources allocated to the lower priority data session by sufficient resources to serve the data session.
12. The method of claim 9 , wherein the data session is more delay-sensitive than the lower priority data session.
13. The method of claim 9 , wherein the data session includes a real-time requirement.
14. The method of claim 9 , wherein the pre-emption is based at least in part on determining that pre-empting the lower priority data session would make sufficient resources available for the data session.
15. A system, comprising:
at least one processor; and
at least one processor-readable storage medium storing instructions for execution by the at least one processor, the instructions executable to:
receive a request for a new data session;
determine, responsive to the request, whether sufficient Walsh code resources and sufficient power resources are available to serve the new data session; and
allocate available Walsh code resources and power resources to the new data session responsive to determining that sufficient resources are available; or
allocate pre-empted Walsh code resources and power resources to the new data session responsive to determining that insufficient resources are available, the pre-empted Walsh code resources and power resources made available by pre-emption of a lower priority data session that does not have a real-time requirement, the lower priority data session selected for pre-emption from a plurality of lower priority data sessions based at least in part on:
a quality of service priority indicator of each respective lower priority data session indicating that the respective lower priority data session includes a lower priority than the new data session;
a determination that pre-empting the respective lower priority data session would make sufficient resources available to serve the new data session; and
a determination that the lower priority data session passes a minimum active time check.
16. The one system of claim 15 , wherein the allocated pre-empted Walsh code resources and power resources comprise at least a portion of resources made available by pre-emption of the lower priority data session and the lower priority data session having a lower priority than the new data session.
17. The system of claim 15 , the instructions further executable to refuse the request for the new data session upon determining that pre-empting the lower priority data session would not make sufficient resources available for the new data session.
18. The system of claim 15 , wherein the new data session is more delay-sensitive than the lower priority data session.
19. The system of claim 15 , wherein the new data session has a real-time requirement.
20. The system of claim 15 , wherein the pre-emption of the lower priority data session comprises instructions executable to decrease resources allocated to the lower priority data session by sufficient resources to serve the data session.