Dynamic negotiation of resources for user equipment in wireless communications system

BACKGROUND

1. Field of the Invention

The present invention pertains to wireless telecommunications, and particularly to processes of obtaining resources of a wireless telecommunication system in connection with admitting and/or sustaining a call with a mobile user equipment unit (UE).

2. Related Art and Other Considerations

Cellular telecommunications systems employ a wireless link (e.g., air interface) between a (mobile) user equipment unit and a base station (BS) node. The base station node has transmitters and receivers for radio connections with numerous user equipment units. One or more base station nodes are connected (e.g., by landlines or microwave) and managed by a radio network controller node (also known in some networks as a base station controller [BSC]). The radio network controller node is, in turn, connected through control nodes to a core communications network. Control nodes can take various forms, depending on the types of services or networks to which the control nodes are connected. For connection to connection-oriented, switched circuit networks such as PSTN and/or ISDN, the control node can be a mobile switching center (MSC). For connecting to packet switching data services such as the Internet (for example), the control node can be a gateway data support node through which connection is made to the wired data networks, and perhaps one or more serving nodes.

A telecommunications connection between a mobile user equipment unit and another party (e.g., in the core communications network or another mobile user equipment unit) thus involves an uplink from the mobile unit through a base station and a radio network controller (RNC), and a downlink in the reverse direction. In some types of telecommunications systems, control and user information is transmitted in frames both on the uplink and downlink.

Typically the radio network controller (RNC) has complex processes for allocating resources for a call involving a user equipment unit (UE), including processes for allocating such resources as power, bitrate, etc. Generally, as the telecommunication system undergoes evolution from one generation to a more sophisticated generation, these processes must be overhauled for compatibility with the enhanced sophistication. Overhauling of the processes usually requires extensive revision of software and the like involved in these processes.

What is needed, therefore, and an object of the present invention, is capability for adding enhanced functionality to a telecommunication system without requiring fundamental revision of pre-existent processes.

BRIEF SUMMARY OF THE INVENTION

A telecommunications system has a user equipment unit agent for each wireless user equipment unit with which a connection is to be established. The user equipment agent negotiates resources with a capacity management system for the prospective connection to be established with its corresponding user equipment unit. In the negotiation, the user equipment agent determines a number of purchase units expendable by the user equipment unit for the negotiation, and issues a resource request to begin the negotiation. Each resource has a resource unit price at which a unit of the resource is sold. In response to the resource request issued by the user equipment agent, connection resources are allocated to the user equipment unit in accordance with what the number of purchase units expendable by the user equipment unit can afford.

The resource unit prices for the resources are posted on a resource price list. The resource unit price for the resources is dynamically adjusted, e.g., in accordance with load on the telecommunication system. The resources can include such capabilities as transmission power, spreading code, bit rate, and a number of handover legs (for diversity purposes).

As one aspect of the invention, the total number of purchase units for a connection is utilized collectively by the user equipment agent to obtain resources for a connection. In another aspect, the number of purchase units expendable by the user equipment unit is classified into a number of purchase units expendable for each of the plural connection resources, and the resource request is processed on a per connection resource basis with respect to-the classification.

In one embodiment, after the resources are initially allocated, the user equipment unit agent re-negotiates for the respective resource. The user equipment agent can commence the re-negotiation either on its own initiative, or in accordance with a change in status in the telecommunication system. As a variation of this embodiment, a load manager can apprise the user equipment unit agent of a status change in the telecommunication system, so that the user equipment unit agent re-negotiates in response to the status change.

As a further aspect of the invention, the resource unit prices for the resources can be dynamically adjusted by an adaptive control system. The adaptive control system can be utilized to determine the load on the telecommunication system, with a change in load being used dynamically to adjust the-resource unit price for one or more of the plural connection resources. The adaptive control system can determine a predicted load on the telecommunication system by using a long term prediction profile and a short term prediction profile.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other objects, features, and advantages of the invention will be apparent from the following more particular description of preferred embodiments as illustrated in the accompanying drawings in which reference characters refer to the same parts throughout the various views. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating the principles of the invention.

FIG. 1 is a schematic view of a telecommunication system according to an embodiment of the present invention.

FIG. 1A is a schematic view of a telecommunication system according to another embodiment of the present invention.

FIG. 2 is a diagrammatic view of one embodiment of a capacity management system for a node of the telecommunication system of FIG. <b>1</b>.

FIG. 2A is a diagrammatic view of an embodiment of a capacity management system for a node of the telecommunication system of FIG. IA.

FIG. 3 is a diagrammatic view showing basic operations performed in connection with certain aspects of resource negotiation in the capacity management system of FIG. 2 in the embodiment of FIG. <b>1</b>.

FIG. 3A is a diagrammatic view showing basic operations performed in connection with certain aspects of resource negotiation in the capacity management system of FIG. 2A in the embodiment of FIG. <b>1</b>.

FIG. 3B is a diagrammatic view showing basic operations performed in connection with a resource negotiation according to the embodiment of FIG. 2 in the embodiment of FIG. <b>1</b>A.

FIG. 4 is a diagrammatic view of basic functions performed by a user equipment unit agent of the telecommunication system of FIG. <b>1</b>.

FIG. 4A is a diagrammatic view of basic functions performed by a user equipment unit agent of the telecommunication system of FIG. <b>1</b>A.

FIG. 5 is a diagrammatic view of an adaptive control system for a node of the telecommunication system of the present invention.

FIG. 6 is a schematic view of a base station prediction process according to an embodiment of the present invention.

FIG. 7 is a diagrammatic view depicting development of a current long term prediction profile in accordance with the present invention.

FIG. 7A is a diagrammatic view showing an entry in the current long term prediction profile of FIG. <b>7</b>.

DETAILED DESCRIPTION

In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the present invention. However, it will be apparent to those skilled in the art that the present invention may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well known devices, circuits, and methods are omitted so as not to obscure the description of the present invention with unnecessary detail.

FIG. 1 shows a telecommunications network <b>18</b> in which a user equipment unit <b>20</b> communicates with one or more base stations <b>22</b> over air interface (e.g., radio interface) <b>23</b>. Base stations <b>22</b> are connected by terrestrial lines (or microwave) to radio network controller (RNC) <b>24</b> [also known as a base station controller (BSC) in some networks]. The radio network controller (RNC) <b>24</b> is, in turn, connected through a control node known as the mobile switching center <b>26</b> to circuit-switched telephone networks (PSTN/ISDN) represented by cloud <b>28</b>. In addition, radio network controller (RNC) <b>24</b> is connected to Serving GPRS Support Node (SGSN) <b>25</b> and through backbone network <b>27</b> to a Gateway GRPS support node (GGSN) <b>30</b>, through which connection is made with packet-switched networks (e.g., the Internet, X.25 external networks) represented by cloud <b>32</b>.

As understood by those skilled in the art, when user equipment unit <b>20</b> participates in a mobile telephonic connection, signaling information and user information from user equipment unit <b>20</b> are transmitted over air interface <b>23</b> on designated radio channels to one or more of the base stations <b>22</b>. The base stations have radio transceivers which transmit and receive radio signals involved in the connection or session. For information on the uplink from the user equipment unit <b>20</b> toward the other party involved in the connection, the base stations convert the radio-acquired information to digital signals which are forwarded to radio network controller (RNC) <b>24</b>. The radio network controller (RNC) <b>24</b> orchestrates participation of the plural base stations <b>22</b> which may be involved in the connection or session, since user equipment unit <b>20</b> may be geographically moving and handover may be occurring relative to the base stations <b>22</b>. On the uplink, radio network controller (RNC) <b>24</b> picks frames of user information from one or more base stations <b>22</b> to yield a connection between user equipment unit <b>20</b> and the other party, whether that party be in PSTN/IDSN <b>28</b> or on the packet-switched networks (e.g., the Internet) <b>32</b>.

The example embodiments illustrated herein happen to employ code division multiple access (CDMA), wherein the information transmitted between a base station and a particular mobile station is modulated by a mathematical code (such as spreading code) to distinguish it from information for other mobile stations which are utilizing the same radio frequency. Thus, in CDMA, the individual radio links are discriminated on the basis of codes. Various aspects of CDMA are set forth in Garg, Vijay K. et al., <i>Applications of CDMA in Wireless/Personal Communications</i>, Prentice Hall (1997). In view of the diversity aspects of CDMA, the user equipment unit <b>20</b> in FIG. 1 is depicted as being in contact with multiple base stations <b>22</b> (e.g., base station <b>22</b>₁and base station <b>22</b>₂).

An important aspect of the telecommunication system <b>18</b> of FIG. 1 is capacity management system <b>100</b> and an agent residence section <b>104</b>. Both capacity management system <b>100</b> and an agent residence section <b>104</b> are preferably located at the radio network controller (RNC) node <b>24</b> of telecommunication system <b>18</b>. The functions of capacity management system <b>100</b> and an agent residence section <b>104</b> are, at least in one embodiment, performed by coded instructions which are executed by one or more (e.g., distributed) processors of radio network controller (RNC) node <b>24</b>. Details of an example capacity management system <b>100</b> are illustrated in FIG. 2 in which all elements (except user equipment unit <b>20</b> and an agent residence section <b>104</b>) are included in capacity management system <b>100</b>.

The example capacity management system <b>100</b> includes admission control unit <b>106</b>; load manager <b>108</b>, and plural resource managers such as code manager <b>110</b> and power manager <b>112</b>. The load manager <b>108</b> includes a price list <b>120</b> and a price list manager <b>122</b>. The code manager <b>110</b> receives status communications from uplink code tree usage monitor <b>130</b> and downlink code tree usage monitor <b>132</b>. In similar fashion, power manager <b>112</b> receives status communications from MCPA downlink power monitor <b>140</b> and uplink (received) power monitor <b>142</b>. In one example version, capacity management system <b>100</b> is responsible for, and therefore associated with, a single cell. In such example version, there are separate instances of capacity management system <b>100</b> for each cell controlled by the radio network controller (RNC) node <b>24</b>.

Whenever a connection is requested between user equipment unit <b>20</b> and telecommunication system <b>18</b> (as represented by action <b>2</b>-<b>1</b> in FIG. <b>2</b>), a user equipment agent is allocated in agent residence section <b>104</b> for the potential connection. In this regard, the user equipment agent is a programming block which includes data and executable code allocated for the user equipment unit <b>20</b>. Therefore, for each connection with a user equipment unit (UE) controlled by the radio network controller (RNC) node <b>24</b> having capacity management system <b>100</b>, an user equipment agent is allocated in agent residence section <b>104</b>. For the particular user equipment unit <b>20</b> shown in FIG. 2, user equipment agent <b>150</b> is illustrated. For simplicity the user equipment agents for other user equipment units (UE) having connections with the telecommunication system <b>18</b> through radio network controller (RNC) node <b>24</b> are not shown in agent residence section <b>104</b> of FIG. <b>2</b>.

Whereas an agent residence section <b>104</b> has been described above as being separate and distinct from capacity management system <b>100</b>, in other embodiments the an agent residence section <b>104</b> can be included as part of capacity management system <b>100</b>. In either case, example details of basic aspects of user equipment agent <b>150</b> can be as shown in FIG. <b>4</b>. The user equipment agent <b>150</b> includes connection request handler <b>152</b>; admission request preparer <b>154</b>; subscription access function <b>156</b>; and, resource purchase unit calculator <b>158</b>. Operations of these example constituent functional aspects of user equipment agent <b>150</b> are understood in connection with the ensuing description of events depicted in FIG. <b>2</b> and FIG. <b>3</b>.

When a request for a connection with/by user equipment unit <b>20</b> occurs (such as that depicted by action <b>2</b>-<b>1</b> in FIG. <b>2</b>), the request is processed by connection request handler <b>152</b> of user equipment agent <b>150</b> (see FIG. <b>4</b>). As indicated by action <b>3</b>-<b>1</b> of FIG. 3, the connection request handler <b>152</b> invokes the subscription access function <b>156</b> to obtain subscription information characterizing the capabilities and privileges of user equipment unit <b>20</b>. In this respect, such subscription information for a user equipment unit (UE) is typically stored at a home location register (HRL) for the user equipment unit (UE). Therefore, the subscription access function <b>156</b> may participate in various messages and/or signaling (well known to the person skilled in the art) in order to obtain certain subscription information for user equipment unit <b>20</b>.

The subscription information obtained by subscription access function <b>156</b> relative to user equipment unit <b>20</b> is either obtained as, or converted to, a number of purchase units for each connection resource which needs to be utilized by user equipment unit <b>20</b>. In this regard, in order to establish a connection with telecommunication system <b>18</b> the user equipment unit <b>20</b> will require certain resources, such as transmission power, a spreading code (for a CDMA system), a permissible number of handover legs (for a CDMA system), etc. Moreover, the subscription information for the user equipment unit <b>20</b> (based, e.g., on a subscription agreement with the owner of user equipment unit <b>20</b>), indicates what types of services, priorities, and privileges to which the user equipment unit <b>20</b> is entitled, the degree of such likely being dependent upon the monetary subscription price specified in the subscription agreement. The subscription access function <b>156</b> quantifies the subscription information, e.g., by according either (1) a total number of “purchase units” expendable by user equipment <b>20</b>, or (2) a number of “purchase units” as being expendable by user equipment unit <b>20</b> for each of the plural respective resources. As explained in more detail herein, the purchase units are to be used as, e.g., money or currency for the user equipment agent <b>150</b> to negotiate resources with admission control unit <b>106</b>. As shown in FIG. 4, subscription access function <b>156</b> has purchase units for each of N number of connection resources, ranging from purchase units [indicated by box <b>170</b>(<b>1</b>)] for a first resource [resource #<b>1</b>]) to purchase units [indicated by box <b>170</b>(N)] for resource #N.

In one aspect of the invention, as depicted by action <b>3</b>-<b>2</b> of FIG. 4, the purchase units quantified or otherwise obtained by subscription access function <b>156</b> are applied to resource purchase unit calculator <b>158</b>. The resource purchase unit calculator <b>158</b> determines the total purchasing power of user equipment unit <b>20</b> based upon the purchase units stored at subscription access function <b>156</b>. In this mode of the invention, the total purchasing power of user equipment unit <b>20</b> (in purchase units) is supplied to admission request preparer <b>154</b> (see action <b>3</b>-<b>3</b>). The admission request preparer <b>154</b> also receives from connection request handler <b>152</b> (as indicated by action <b>3</b>-<b>4</b>) a listing of the particular resources desired for the requested connection.

The admission request issued by user equipment agent <b>150</b> on behalf of user equipment unit <b>20</b> is illustrated as action <b>2</b>-<b>2</b> in FIG. <b>2</b>. As obtained from connection request handler <b>152</b>, the admission request of action <b>2</b>-<b>2</b> lists the particular resources desired for the requested connection (e.g., transmit power, spreading codes, frequency <b>5</b> requirements, etc.), as well as the spending capability (e.g., number of resource purchase units) of user equipment unit <b>20</b>. The admission request <b>2</b>-<b>2</b> is handled by admission control unit <b>106</b>. In coordinated fashion, admission control unit <b>106</b> apprises various resource managers of the request for resources for the connection with user equipment unit <b>20</b>. Although only two example resource managers are illustrated in FIG. 2, it should be understood that managers for other resources behave in like manner as those illustrated. In this regard, as action <b>2</b>-<b>3</b> and action <b>2</b>-<b>4</b> the admission control unit <b>106</b> sends a code request and a power request to code manager <b>110</b> and power manager <b>112</b>, respectively.

Basic actions performed by typical resource managers are exemplified in FIG. 3 with reference to example resource managers <b>180</b>(<b>1</b>) and <b>180</b>(N). Each resource manager <b>180</b> includes a resource allocation procedure <b>182</b> and a resource cost calculator <b>184</b>. The resource allocation procedure <b>182</b> quantifies the request for the resource by assigning a number of allocation units to the request, the number assignment being based on the extent to which the resource is requested or required for the prospective no connection with user equipment unit <b>20</b>. The number of allocation units for the resource is sent to resource cost calculator <b>184</b>, which (as shown in FIG. 3) determines a resource cost or price tag (<b>188</b>) for the resource by multiplying the number of allocation units for the resource (<b>186</b>) by the current allocation unit price for the resource (<b>187</b>).

The actions described with reference to resource allocation procedure <b>182</b> and resource cost calculator <b>184</b> of FIG. 3 are applicable to each of the resource managers which are requested to provide resources for a prospective connection with user equipment unit <b>20</b>. For example, such actions are performed by code manager <b>110</b> and power manager <b>112</b> of FIG. <b>2</b>.

In one aspect of the invention, the resource cost or price tag (<b>188</b>) for each requested resource from each participating resource manager is sent to admission control unit <b>106</b>, which determines a total price tag at operation <b>190</b> thereof (see FIG. <b>3</b>). In FIG. 2 the resource cost or price tags <b>188</b> is are shown as being sent to admission control unit <b>106</b> from code manager <b>110</b> and power manager <b>112</b> by actions <b>2</b>-<b>5</b> and <b>2</b>-<b>6</b>, respectively. At step <b>192</b>, admission control unit <b>106</b> determines whether the user equipment agent <b>150</b> for user equipment unit <b>20</b> has enough resource purchase units to afford the total price tag of all allocated resources. If the user equipment agent <b>150</b> has <b>5</b> enough resource purchase units, at step <b>194</b> the admission control unit <b>106</b> prepares an advisory to user equipment agent <b>150</b> that the connection will be granted with the allocated connection resources. The advisory of successful negotiation and purchase of connection resources for admission is illustrated as action <b>2</b>-<b>7</b> in FIG. <b>2</b>.

If user equipment agent <b>150</b> is unable to afford the allocated connection resources, at step <b>196</b> the admission control unit <b>106</b> engages in resource adjustment logic. The resource adjustment logic of step <b>196</b> advises the resource allocation procedures <b>182</b> of one or more of the resource managers <b>180</b> of the over-budget calculation, and affords the resource allocation procedure(s) <b>182</b> an opportunity to allocate a less expensive extent of resources to user equipment unit <b>20</b>.

In accordance with the present invention, the resource unit price for each of the plural connection resources is dynamically adjusted in accordance with load on the telecommunication system. In this regard, as shown in FIG. <b>2</b> and FIG. 3, the resource unit price <b>187</b> for each resource is periodically or otherwise updated as indicated by action <b>200</b>. In FIG. 2, action <b>200</b>(<b>1</b>) reflects an update of the unit price <b>187</b>(<b>1</b>) for resource #<b>1</b>; action <b>200</b>(N) reflects an update of the unit price <b>187</b>(N) for resource #N.

FIG. 3 shows price list <b>120</b> as having a unit price [<b>202</b>(<b>1</b>)] for resource #<b>1</b> and a unit price for a variety of other resources including resource #N [<b>202</b>(N)] . The updated unit prices are obtained from price list <b>120</b>, which in turn is updated by price list manager <b>122</b>. The price list manager <b>122</b> can adjust or change the prices <b>202</b> in price list <b>120</b> in accordance with any specified criteria or impetus, an example of which pertaining to an adaptive control system is subsequently described herein.

Thus, as understood from the foregoing, admission control unit <b>106</b> responds to the admission request from user equipment agent <b>150</b> by allocating connection resources to the user equipment unit in accordance with what the number of purchase <b>30</b> units expendable by the user equipment unit can afford.

FIG. 2A shows another embodiment of the capacity management system <b>100</b> present invention in which the user equipment agent <b>150</b> not only makes an admission request of capacity management system <b>100</b>, but also re-negotiates for connection resources after an initial allocation of resources have been made. The user equipment agent <b>150</b> can periodically initiate such re-negotiations on its own behalf, or can do so as a result of a changed status in telecommunication system <b>18</b>. The embodiment of capacity management system <b>100</b> shown in FIG. 2A differs from that shown in FIG. 2 primarily in that load manager <b>108</b> sends change status notifications (such as that depicted by action <b>2</b>A-<b>1</b>) to user equipment agent <b>150</b>, and in that user equipment agent <b>150</b> re-negotiates connection resources with capacity management system <b>100</b>.

A change status notification <b>2</b>A-<b>1</b> can be triggered by any predetermined change in the network, such as a predetermined degree of change in load conditions in telecommunication system <b>18</b>. The change status notification <b>2</b>A-<b>1</b> can carry with it an indication of the nature of the change, and (optionally) an indication of the degree of the change.

The user equipment agent <b>150</b> for the embodiment of FIG. 2A is shown in FIG. 4A as including resource change logic <b>160</b>; status change handler <b>162</b>; and resource change request preparer <b>164</b>, in addition to the functions previously described in FIG. <b>4</b>. It is status change handler <b>162</b> that receives and processes the change status notification <b>2</b>A-<b>1</b>. As indicated by action <b>3</b>A-<b>1</b>, the status change handler <b>162</b> communicates the status change to resource change logic <b>160</b>. The resource change logic <b>160</b> estimates whether it would be worthwhile for user equipment agent <b>150</b> to attempt to re-negotiate for connection resources. For example, resource change logic <b>160</b> may estimate that a potential greater allocation of connection resources could now be obtained. Alternatively, the resource change logic <b>160</b> may realize that user equipment unit <b>20</b> is over extended in view of present network load conditions, and attempt to scale back resource utilization on its own before potentially more drastic measures are taken by telecommunication system <b>18</b>. In either case, when a re-negotiation appears feasible, as depicted by action <b>3</b>A-<b>2</b> resource change logic <b>160</b> authorizes resource change request preparer <b>164</b> to prepare a re-negotiation bid to submit to one or more resource managers.

The determination of resource change logic <b>160</b> is facilitated by availability of the number of purchase units computed by resource purchase unit calculator <b>158</b> and the number of purchase units for user equipment agent <b>150</b> as acquired by subscription access function <b>156</b>. The number of purchase units held by user equipment agent <b>150</b> is communicated to admission control unit <b>106</b> in the bid submitted by resource change request preparer <b>164</b>. FIG. 2A shows user equipment agent <b>150</b> submitting a re-negotiation bid to admission control unit <b>106</b> (action <b>2</b>A-<b>2</b>). Admission control unit <b>106</b> submits the re-negotiation bid to each of code manager <b>110</b> and power manager <b>112</b>, as indicated by respective actions <b>2</b>-<b>3</b>A and <b>2</b>-<b>4</b>A shown in FIG. <b>2</b>A.

FIG. 3A shows that the resources managers <b>180</b> process the re-negotiation bid in much the same manner as above discussed in connection with FIG. <b>3</b>. However, the processing by admission control <b>106</b> differs for a re-negotiation bid. In this regard, at step <b>302</b> the admission control unit <b>106</b> ascertains that resources have already been allocated for the connection (e.g., this is not an admission request). Then, at step <b>304</b>, the admission control unit <b>106</b> determines whether the user equipment agent <b>150</b> has sufficient purchase units to buy the requested new level of resource(s). If the price tag for the requested new level of resources cannot be afforded, a failure notification is prepared at step <b>308</b> and sent to user equipment agent <b>150</b>. If the price tag for the requested new level of resources is affordable by user equipment agent <b>150</b>, a success notification is prepared at step <b>306</b> and sent to user equipment agent <b>150</b>.

Thus, in the particular example illustrated in FIG. 2A in which additional resources are requested by user equipment agent <b>150</b> via admission control unit <b>106</b> from both code manager <b>110</b> and power manager <b>112</b>, action <b>2</b>A-<b>4</b> and <b>2</b>A-<b>5</b> are messages from code manager <b>110</b> and power manager <b>112</b> advising admission control unit <b>106</b> of the cost of the respective resources. Further, action <b>2</b>-<b>7</b>A shows admission control unit <b>106</b> providing the user equipment agent <b>150</b> with either a success (acceptance) or a failure (rejection) notification.

As an example scenario, suppose that the subscription information for equipment unit <b>20</b> indicates a very low priority (e.g., a low budget subscription) and that user equipment unit <b>20</b> is located near a boarder of a cell. Being at the boarder of the cell, the user equipment unit <b>20</b> must request considerable power. Further, the fact that user equipment unit <b>20</b> is near the cell boundary indicates that user equipment unit <b>20</b> will likely need to be connected to plural cells (for diversity purposes). The user equipment agent <b>150</b> for user equipment unit <b>20</b> determines how much “power” money, how much “bitrate” money, and whatever other resources user equipment unit <b>20</b> will require (e.g., how many power purchase units, how many bitrate purchase units the user equipment unit <b>20</b> will require). This assignment of money (i.e., resource purchase units) is independent of system requirements, and reflects how the different parameters and priorities associated with the user equipment unit <b>20</b> are converted into something that can be compared with what the system can offer, and what other users have. In this scenario, assume further that the system has significant load. The price list manager <b>122</b> therefore sets high values for resource unit prices <b>202</b> (e.g., for the power unit price, the bitrate unit price, etc.), making it very difficult to purchase resources. So in this scenario, when user equipment unit <b>20</b> as represented by its user equipment agent <b>150</b> negotiates with admission control unit <b>106</b> to obtain a channel with some power and bitrate, user equipment agent <b>150</b> will likely obtain the lowest quality possible, because the prices are so high and the priority of user equipment unit <b>20</b> is so low (as reflected by the low amount of purchase units). When the connection with user equipment unit <b>20</b> is added, the resource manager(s) note the depletion of resources caused by the addition of user equipment unit <b>20</b>, and so notify price list manager <b>122</b>. Accordingly, price list manager <b>122</b> raises the prices on price list <b>120</b> due to this new allocation.

In the foregoing scenario, it can happen at some later time that user equipment unit <b>20</b> tries to re-negotiate to obtain more resources (e.g., higher bitrate). If in the meantime some channels had been deallocated, such deallocation would be reflected by decreased prices on price list <b>120</b>. If user equipment agent <b>150</b> attempts to re-negotiate at this time, the additional resources may be obtained in view of their decline in price.

As indicated above, the resource unit prices stored on price list <b>120</b> are updated by price list manager <b>122</b>. The update of the resource unit prices stored on price list <b>120</b> can occur in any of a variety of manners, and for diverse reasons. One example of why and how the resource unit prices stored on price list <b>120</b> can be updated is provided in context of a further aspect of the invention, particularly an adaptive control system. In this regard, FIG. IA and FIG. 3B show another embodiment of telecommunication system <b>18</b> in which radio network controller (RNC) node <b>24</b> is additionally provided with adaptive control system <b>500</b> which works in conjunction with capacity management system <b>100</b>. FIG. 3B differs from FIG. 3 by showing adaptive control system <b>500</b> being utilized to provide information to price list manager <b>122</b>, so that the prices on price list <b>120</b> can be updated in accordance with the present invention.

As shown in more detail in FIG. 5, one example adaptive control system <b>500</b> includes various adaptive procedures, such as restart procedure <b>510</b>, resource control procedure <b>520</b>, and channel capacity allocation procedure <b>530</b>. In addition, adaptive control system <b>500</b> includes a traffic prediction module <b>540</b>. The traffic prediction module <b>540</b>. The traffic prediction module <b>540</b> includes processes for one or more of the base stations controlled by the radio network controller (RNC) node <b>24</b> whereat adaptive control system <b>500</b> is executed. FIG. 5 shows traffic prediction processes <b>542</b>₁through <b>542</b>_kfor each of base stations <b>22</b>₁through <b>22</b>_k, respectively.

An example traffic prediction processes <b>542</b> for adaptive control system <b>500</b> is illustrated in FIG. <b>6</b>. The example traffic prediction processes <b>542</b> includes a long term prediction (LTP) profile memory <b>550</b> in which plural long term prediction (LTP) profile records are stored. The profile records in long term prediction (LTP) profile memory <b>550</b> are used to develop a current long term prediction (LTP) profile <b>552</b>. Current traffic measurements/statistics for the cell associated with the base station are obtained and input (as indicated by arrow <b>6</b>-<b>1</b>) to a short term prediction (STP) logic unit <b>554</b>. The current traffic measurements/statistics for the cell input at arrow <b>6</b>-<b>1</b> include both the total load for the cell and an indication of the current mix of circuit switched connections (CSC) and packet switched connections (PSC) for the cell [e.g., 80% CSC and 20% PSC]. An entry for the current time from the current long term prediction (LTP) profile <b>552</b> and the output of the short term prediction (STP) logic unit <b>554</b> are both applied to summer <b>556</b> to obtain an STP_deviation. The STP_deviation represents the deviation of the actual current conditions from the predicted conditions as ascertained by current long term prediction (LTP) profile <b>552</b>. A weighting factor is multiplied for the STP_deviation by weighting factor multiplier <b>558</b>, which outputs a weighted STP_deviation. The weighted STP_deviation is summed by summer <b>560</b> with the actual current conditions [from the predicted conditions ascertained from current long term prediction (LTP) profile <b>552</b>] to obtain a current prediction value (CPV). The current prediction value (CPV) is used to develop a new long term prediction (LTP) profile <b>562</b>. At an appropriate time, the new long term prediction (LTP) profile <b>562</b> (which is accumulated over a specified time period) is then loaded into long term prediction (LTP) profile memory <b>550</b> for future use in determining a new current long term prediction (LTP) profile <b>552</b>.

FIG. 7 shows that long term prediction (LTP) profile memory <b>550</b> comprises plural LTP profiles, profiles <b>550</b><i>k </i>through <b>550</b><i>k-m </i>being illustrated. The current long term prediction (LTP) profile <b>552</b>, illustrated in more detail in FIG. 7, is obtained from long term prediction (LTP) profile memory <b>550</b>. The current long term prediction (LTP) profile <b>552</b> has an entry for each time period (e.g., hour) for each of a range (e.g., week) of days. Each entry in current long term prediction (LTP) profile <b>552</b>, corresponding to a specified hour of a specified day of the week in the illustrated example, is shown as a row/column intersection block in FIG. <b>7</b>. FIG. 7A shows in magnified fashion various example sub-entries for each entry in current long term prediction (LTP) profile <b>552</b>. For example, each entry in current long term prediction (LTP) profile <b>552</b> includes a total load entry <b>570</b>, a percent load of circuit switch connection entry <b>572</b>; and a percent load of packet switch connection entry <b>574</b>.

In one example embodiment, the current long term prediction (LTP) profile <b>552</b> is developed using a linear combination of values from the plural profiles in long term prediction (LTP) profile memory <b>550</b>. In the linear combination, the various constituent profiles in long term prediction (LTP) profile memory <b>550</b> can be weighted, with the most recent profile <b>550</b>k have a greatest weight, a next most recent profile <b>550</b><i>k-I </i>having a next greatest weight, and so forth. Other weighting schemes are, of course, also possible.

The load information ascertained by adaptive control system <b>500</b> is in one illustrated embodiment utilized by price list manager <b>122</b> to dynamically adjust the resource unit prices <b>202</b> in price list <b>120</b>. For example, when the weighted STP_deviation value (see FIG. 6) exceeds a predetermined percentage, the price list manager <b>122</b> can correspondingly change the resource unit price <b>202</b> for one or more resources in price list <b>120</b>. If the weighted STP_deviation value increases, the resource unit prices <b>202</b> can be increased correspondingly. On the other hand, if the weighted STP_deviation value decreases, the resource unit prices <b>202</b> can be decreased correspondingly.

As one feature of the embodiment of FIG. 2A, the restart procedure <b>510</b> of adaptive control system <b>500</b> can use the information in traffic prediction module <b>540</b> to define the start order for various resources. Resources in areas with suspected high traffic load, as evidenced by the traffic prediction processes <b>542</b> for the various base stations, can be started before resources are utilized in other areas (e.g., other base stations). Thus, restart procedure <b>510</b> is adapted to the actual traffic profile. For example, if a system restart occurs during normal office hours (e.g., during an hour of the work day), the resources employed to cover a business region can be started before resources in other areas with less traffic load (e.g., a residential area). Thus, if the traffic load peak moves around in the telecommunication system as a function of the time of the day, the restart order for the various resources is adapted to the movement of the traffic load peak.

In addition, the information in the traffic prediction processes <b>542</b> can also be used to decide what type of services are most frequently requested, and thereby used by resource control procedure <b>520</b> to pre-allocate and pre-configure (e.g., pre-start) resources for those services. For instance, in a geographical area in which voice calls dominate at a certain time of the day, the system can pre-allocate and configure resources for voice calls and store the “voice channels” in a pool of pre-configured resources. When a call is established, the call establishment procedure can pick a “voice channel” from the pool. The number of pre-allocated and configured resources (for a specific purpose) is kept in relation to the traffic profile for the specific call type.

In a wideband CDMA system, switching between channel types with different capacity is a difficult problem for which an adaptive scheme such as that provided by adaptive control system <b>500</b> is particularly useful. When telecommunication system <b>18</b> is to make decisions about what capacity a user is to be allocated, it is advantageous to be able to make good estimates regarding the traffic profile. In this regard, channel capacity allocation procedure <b>530</b> of the adaptive control system <b>500</b> of the present invention uses the long term prediction (LTP) profile and short term prediction (STP) profiles described above to make good estimates regarding the kind of expected users, and how large the load will be at any point in time. For example, suppose the profile for a base station in traffic prediction module <b>540</b> indicates that there is hardly any activity in the associated cell early on Sunday mornings. In such case, if a user is to be allocated a dedicated data channel, the channel capacity allocation procedure <b>530</b> can allocate to the user a large capacity, as hardly anyone else uses mobile communications at that time. Conversely, a mobile system can be very restrictive in distributing large capacities during an afternoon rush hour, as likely many people will be leaving their work places and placing voice calls in route home.

Thus, the adaptive control system <b>500</b> of the present invention affords various advantages. By using restart procedure <b>510</b>, resources employed in high traffic load areas are started earlier than resources in low traffic load areas, which means that the system is capable of providing services in high traffic load areas where the capacity is needed before providing services in other areas with a lower capacity need. By using the resource control procedure <b>520</b>, the resources can be pre-allocated and configured to map the need, which means that call setup time is minimized for the most frequently used service. Further, by using the channel capacity allocation procedure <b>530</b>, the system is more efficient in distributing its capacity. In this latter regard, in the ideal case, when the traffic looks about the same every week, the system has the best possible chance to make good decisions about channel switching. Such is particularly applicable at certain “scheduled” spots, such as bus stops, airports, schools and the like, where the behavior from week to week is very similar and thus the adaptivity can provide significant advantages.

Advantageously, the present invention permits accommodation of new functionality without having to change significantly existing processes.[need to develop this in greater detail]. For example, system modifications can be reflected by changing the prices on price list <b>120</b>, with the result that the executable code of the system processes may not need to be changed

While the invention has been described in connection with what is presently considered to be the most practical and preferred embodiment, it is to be understood that the invention is not to be limited to the disclosed embodiment, but on the contrary, is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.