Resource capacity reporting to control node of radio access network

BACKGROUND

1. FIELD OF THE INVENTION

0001The present invention pertains to wireless telecommunications, and particularly to acquisition of status information by a control node of a radio access network.

2. RELATED ART AND OTHER CONSIDERATIONS

0002In a typical cellular radio system, mobile user equipment units (UEs) communicate via a radio access network (RAN) to one or more core networks. The user equipment units (UEs) can be mobile stations such as mobile telephones ("cellular" telephones) and laptops with mobile termination, and thus can be, for example, portable, pocket, hand-held, computer-included, or car-mounted mobile devices which communicate voice and/or data with radio access network.

0003The radio access network (RAN) covers a geographical area which is divided into cell areas, with each cell area being served by a base station. A cell is a geographical area where radio coverage is provided by the radio base station equipment at a base station site. Each cell is identified by a unique identity, which is broadcast in the cell. The base stations communicate over the air interface (e.g., radio frequencies) with the user equipment units (UE) within range of the base stations. In the radio access network, several base stations are typically connected (e.g., by landlines or microwave) to a radio network controller (RNC). The radio network controller, also sometimes termed a base station controller (BSC), supervises and coordinates various activities of the plural base stations connected thereto. The radio network controllers are typically connected to one or more core networks.

0004One example of a radio access network is the Universal Mobile Telecommunications (UMTS) Terrestrial Radio Access Network (UTRAN). The UTRAN is a third generation system which in some respects builds upon the radio access technology known as <u>G</u>lobal <u>S</u>ystem for <u>M</u>obile communications (GSM) developed in Europe. UTRAN is essentially a wideband code division multiple access (W-CDMA) system.

0005As those skilled in the art appreciate, in W-CDMA technology a common frequency band allows simultaneous communication between a user equipment unit (UE) and plural base stations. Signals occupying the common frequency band are discriminated at the receiving station through spread spectrum CDMA waveform properties based on the use of a high speed, pseudo-noise (PN) code. These high speed PN codes are used to modulate signals transmitted from the base stations and the user equipment units (UEs). Transmitter stations using different PN codes (or a PN code offset in time) produce signals that can be separately demodulated at a receiving station. The high speed PN modulation also allows the receiving station to advantageously generate a received signal from a single transmitting station by combining several distinct propagation paths of the transmitted signal. In CDMA, therefore, a user equipment unit (UE) need not switch frequency when handoff of a connection is made from one cell to another. As a result, a destination cell can support a connection to a user equipment unit (UE) at the same time the origination cell continues to service the connection. Since the user equipment unit (UE) is always communicating through at least one cell during handover, there is no disruption to the call. Hence, the term "soft handover." In contrast to hard handover, soft handover is a "make-before-break" switching operation.

0006The Universal Mobile Telecommunications (UMTS) Terrestrial Radio Access Network (UTRAN) accommodates both circuit switched and packet switched connections. In this regard, in UTRAN the circuit switched connections involve a radio network controller (RNC) communicating with a mobile switching center (MSC), which in turn is connected to a connection-oriented, external core network, which may be (for example) the Public Switched Telephone Network (PSTN) and/or the Integrated Services Digital Network (ISDN). On the other hand, in UTRAN the packet switched connections involve the radio network controller communicating with a Serving GPRS Support Node (SGSN) which in turn is connected through a backbone network and a Gateway GPRS support node (GGSN) to packet-switched networks (e.g., the Internet, X.25 external networks).

0007There are several interfaces of interest in the UTRAN. The interface between the radio network controllers (RNCs) and the core network(s) is termed the "Iu" interface. The interface between a radio network controller (RNC) and its base stations (BSs) is termed the "Iub" interface. The interface between the user equipment unit (UE) and the base stations is known as the "air interface" or the "radio interface" or "Uu interface". An interface between radio network controllers (e.g., between a Serving RNC [SRNC] and a Drift RNC [DRNC]) is termed the "Iur" interface.

0008The radio network controller (RNC) controls the UTRAN. In fulfilling its control role, the RNC manages resources of the UTRAN. Such resources managed by the RNC include (among others) the downlink (DL) power transmitted by the base stations; the uplink (UL) interference perceived by the base stations; and the hardware situated at the base stations. Some of the hardware at the base stations can take the form of devices which are mounted on "boards" such as circuit boards.

0009Ideally an RNC attempts to manage UTRAN resources as efficiently as possible, thereby providing the greatest possible capacity (e.g., the largest number of possible connections between users) while maintaining an expected/desired quality for each connection. But in order to manage efficiently, the RNC must have fairly accurate and complete information about the services being carried by the UTRAN and the load in the portions of the network controlled by the RNC. This means that information about the load of a base station controlled by the RNC must be communicated to the RNC.

0010It would be impractical to communicate continuously the exact load situation in a given base station to its controlling RNC. To communicate the exact load situation, all status information for all hardware elements, e.g., boards, comprising the base station would have to be transmitted or transferred over the Iub interface to the RNC which manages the base station. Communication of such extensive load information would undersireably congest the Iub interface.

0011In recognition of the need to balance reporting of base station resource loading with efficient use of the Iub interface, a "Resource Status Indication" message has been proposed in Third Generation Partnership Project (3GPP) Specification 25.433 "UTRAN Iub Interface NBAP Signalling". The Third Generation Partnership Project (3GPP) has undertaken to evolve further the UTRAN and GSM-based radio access network technologies. The "Resource Status Indication" message, described, e.g., in the Third Generation Partnership Project (3GPP) Specification 25.433 §8.2.15 and §9.1.31, is sent from a base station node (e.g., "Node B") to its controlling RNC upon occurrence of specific events, and contains some approximating information regarding usage of hardware resources. The information reported by the base station in the "Resource Status Indication" message is generally expressed in terms of so-called "Consumption Laws". These laws indicate the amount of resources utilized for a connection given the spreading factor (SF) of the connection. The RNC then estimates the amount of resources being utilized at the base station by adding up the resource usage of each individual connection, taking this consumption law into account.

0012The proposed 3GPP "Resource Status Indication" message has deficiencies. Some of these deficiencies are rooted in the fact that the load on the base station node cannot always be expressed as a sum of the resource usage of each individual connection. As a first example deficiency, fragmentation problems at the base station node may render the sum misleading. Fragmentation can occur, for example, in a multi-board base station node in which spare capacity is scattered in an unusable fashion over several boards. In other words, while the sum contemplated by the 3GPP "Resource Status Indication" message may imply a certain spare capacity, not all the spare capacity is usable in view of the fragmentation.

0013<patcit id="pcit0001" dnum="WO9741698A"><text>WO 97/41698</text></patcit> (D1) relates to an inter system soft handoff method, of a subscriber unit between two base stations. Interaction between the two base stations is performed to determine if sufficient network resources are available to conduct the handoff. D1 does, however, not discuss the problem of fragmentation of the base station resources.

0014To illustrate the problem of fragmentation, suppose that there are a number of the same boards in a base station and three classes of connections exist, particularly connection classes A, B, and C. Further suppose that each of the three boards can handle either of the following: (1) three class A connections; (2) two class B connections; (3) one class C connection or a class A connection and a class B connection. Thus, in terms of Consumption laws, A=1; B=1.5, and C=3. A correct load value for the base station can be found when all connections are the same class, but when the connections are of mixed classes, the sum does not hold. When several boards have mixed class allocations like this, more resources seem to be free than actually is the case.

0015A second example deficiency is that the sum reported by the 3GPP "Resource Status Indication" message may not be accurate when more than one resource type is used for a connection. Suppose, for sake of illustration, that there are two kinds of boards involved in a connection. A first kind of board (board type P) uses one circuit per connection regardless of the spreading factor (e.g., board type P can carry ten connections). The use of resources on a second type of board (board type Q), however, depends on the spreading factor of the connections on the board. Suppose that board type Q has twenty circuits. Suppose further that connection class A uses one circuit each, and connection class B uses four circuits each. Table 1 shows maximum combinations under either of two consumption laws (the first consumption law being A=2, B=2; the second consumption law being A=1, B=4). From Table 1 it can be seen that using the first consumption law will work when many of the class A connections are in the system, while the second consumption law will work when many class B connections are in the system. <tables id="tabl0001" num="0001"><table frame="all"><title><u>TABLE 1</u></title><tgroup cols="3"><colspec colnum="1" colname="col1" colwidth="39mm" /><colspec colnum="2" colname="col2" colwidth="63mm" /><colspec colnum="3" colname="col3" colwidth="65mm" /><thead><row><entry valign="top">Maximum Combinations</entry><entry valign="top">First Consumption Law A=2, B=2, limit=20</entry><entry valign="top">Second Consumption Law A=1, B=4, limit=20</entry></row></thead><tbody><row><entry>10xA + 0Xb</entry><entry>20</entry><entry>10</entry></row><row><entry>9xA + 1Xb</entry><entry>20</entry><entry>13</entry></row><row><entry>8xA + 2Xb</entry><entry>20</entry><entry>16</entry></row><row><entry>7xA + 3Xb</entry><entry>20</entry><entry>19</entry></row><row><entry>4xA + 4Xb</entry><entry>16</entry><entry>20</entry></row></tbody></tgroup></table></tables>

0016What is needed, therefore, and an object of the present invention, is a technique for providing more accurate information regarding the load on a base station node in a radio access network.

BRIEF SUMMARY OF THE INVENTION

0017The invention is set out in claim 1, 17 and 18. A base station node of a radio access network determines a number of connections that can be added for each of plural spreading factors to the base station node, and sends to a radio network controller (RNC) node a capacity indication based on the determined number of connections. In a first message mode of the invention, the capacity indication is included in a conventional 3GPP "Resource Status Indication" message, while in a second message mode the capacity indication is included in a separate supplemental message known as the capacity message. Preferably the capacity indication supplements information from the base station node to the radio network controller (RNC) node which merely reports, in terms of consumption laws, the usage of hardware resources at the base station node.

0018To prepare the capacity indication, the base station tracks actual usage of base station resources for determining the number of connections that can be added to the base station node, and assesses the capability of the base station node to add new connections. The new connection assessment takes into consideration any fragmentation issues or combinations of connection types occurring at the base station node, and therefore provides an accurate indication of the potential additional capacity of the base station node.

0019In either message mode, the capacity indication provides one or more capacity values to the radio network controller node. Whether the capacity indication is included in an RSI message or its own capacity message, the indication can be differently comprised according to various reporting cases or reporting modes of the present invention. In accordance with a first reporting mode of the invention, the capacity indication is actually a vacancy capacity value, indicating the number of connections that can be added for each spreading factor. In this first reporting mode of the invention, the capacity indication includes a series of values which indicate how many allocations/connections of each possible spreading factor can be added before reaching the capacity limit. In accordance with a second reporting mode of the invention, the capacity indication is a total capacity value which reflects both the existing load and vacancy capacity over all spreading factors.

0020The base station node preferably has a processor which executes a base station resource measurement and reporting program in order to prepare and generate the capacity indication. The base station resource measurement and reporting program includes a device model object for various base station devices utilized in facilitating connections. By monitoring the device model objects, the base station resource measurement and reporting program ascertains an accurate calculation of the number of allocations/connections (A_sf) of each possible spreading factor (sf) can be added before reaching the capacity limit.

BRIEF DESCRIPTION OF THE DRAWINGS

0021The 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. <ul id="ul0001" list-style="none"><li><figref idref="f0001">Fig. 1</figref> is diagrammatic view of example mobile communications system in which the present invention may be advantageously employed.</li><li><figref idref="f0002">Fig. 2</figref> is a simplified function block diagram of a portion of a UMTS Terrestrial Radio Access Network wherein a capacity indication is sent from a base station node to a radio network controller node.</li><li><figref idref="f0003">Fig. 2A</figref> is a simplified function block diagram of a portion of a UMTS Terrestrial Radio Access Network wherein a capacity indication is sent from a base station node to a radio network controller node in an augmented RSI message.</li><li><figref idref="f0004">Fig. 2B</figref> is a simplified function block diagram of a portion of a UMTS Terrestrial Radio Access Network wherein a capacity indication is sent from a base station node to a radio network controller node in a separate capacity message.</li><li><figref idref="f0005">Fig. 3</figref> is a schematic view showing certain aspects of a base station resource measurement and reporting process in context of a representative base station node and radio network controller, wherein a capacity indication is sent from a base station node to a radio network controller node.</li><li><figref idref="f0006">Fig. 3A</figref> is a schematic view showing certain aspects of a base station resource measurement and reporting process in context of a representative base station node and radio network controller, wherein a capacity indication is sent from a base station node to a radio network controller node in an augmented RSI message.</li><li><figref idref="f0007">Fig. 3B</figref> is a schematic view showing certain aspects of a base station resource measurement and reporting process in context of a representative base station node and radio network controller, wherein a capacity indication is sent from a base station node to a radio network controller node in a separate capacity message.</li><li><figref idref="f0008">Fig. 4</figref> is a diagrammatic view showing various example devices located at a base station node.</li><li><figref idref="f0009">Fig. 5A</figref> is a diagrammatic view showing various processes included in a base station resource measurement and reporting program according to a mode of the invention wherein a capacity indication is sent from a base station node to a radio network controller node in an augmented RSI message.</li><li><figref idref="f0010">Fig. 5B</figref> is a diagrammatic view showing various processes included in a base station resource measurement and reporting program according to a mode of the invention wherein a capacity indication is sent from a base station node to a radio network controller node in a separate capacity message.</li><li><figref idref="f0011">Fig. 6</figref> is a flowchart showing certain events performed in connection with a node capacity assessment process.</li><li><figref idref="f0012">Fig. 7</figref> is a schematic view of an example RNC node in accordance with one embodiment of the invention.</li><li><figref idref="f0013">Fig. 8</figref> is a schematic view of an example base station node in accordance with one embodiment of the invention.</li></ul>

<u>DETAILED DESCRIPTION</u>

0022In 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.

0023The present invention is described in the non-limiting, example context of a universal mobile telecommunications (UMTS) 10 shown in <figref idref="f0001">Fig. 1</figref>. A representative, connection-oriented, external core network, shown as a cloud 12 may be for example the Public Switched Telephone Network (PSTN) and/or the Integrated Services Digital Network (ISDN). A representative, connectionless-oriented external core network shown as a cloud 14, may be for example the Internet. Both core networks are coupled to their corresponding service nodes 16. The PSTN/ISDN connection-oriented network 12 is connected to a connection-oriented service node shown as a Mobile Switching Center (MSC) node 18 that provides circuit-switched services. The Internet connectionless-oriented network 14 is connected to a General Packet Radio Service (GPRS) node 20 tailored to provide packet-switched type services which is sometimes referred to as the serving GPRS service node (SGSN).

0024Each of the core network service nodes 18 and 20 connects to a UMTS Terrestrial Radio Access Network (UTRAN) 24 over a radio access network (RAN) interface referred to as the Iu interface. UTRAN 24 includes one or more radio network controllers (RNCs) 26. For sake of simplicity, the UTRAN 24 of <figref idref="f0001">Fig. 1</figref> is shown with only two RNC nodes, particularly RNC 26₁ and RNC 26₂. Each RNC 26 is connected to a plurality of base stations (BS) 28. For example, and again for sake of simplicity, two base station nodes are shown connected to each RNC 26. In this regard, RNC 26₁ serves base station 28_1-1 and base station 28_1-2, while RNC 26₂ serves base station 28_2-1 and base station 28_2-2. It will be appreciated that a different number of base stations can be served by each RNC, and that RNCs need not serve the same number of base stations. Moreover, <figref idref="f0001">Fig. 1</figref> shows that an RNC can be connected over an Iur interface to one or more other RNCs in the URAN 24.

0025A user equipment unit (UE), such as user equipment unit (UE) 30 shown in <figref idref="f0001">Fig. 1</figref>, communicates with one or more base stations (BS) 28 over a radio or air interface 32. Each of the radio interface 32, the Iu interface, the Iub interface, and the Iur interface are shown by dash-dotted lines in <figref idref="f0001">Fig. 1</figref>.

0026Preferably, radio access is based upon wideband, Code Division Multiple Access (WCDMA) with individual radio channels allocated using CDMA spreading codes. Of course, other access methods may be employed. WCDMA provides wide bandwidth for multimedia services and other high transmission rate demands as well as robust features like diversity handoff and RAKE receivers to ensure high quality. Each user mobile station or equipment unit (UE) 30 is assigned its own scrambling code in order for a base station 28 to identify transmissions from that particular user equipment unit (UE) as well as for the user equipment unit (UE) to identify transmissions from the base station intended for that user equipment unit (UE) from all of the other transmissions and noise present in the same area.

0027Different types of control channels may exist between one of the base stations 28 and user equipment units (UEs) 30. For example, in the forward or downlink direction, there are several types of broadcast channels including a general broadcast channel (BCH), a paging channel (PCH), a common pilot channel (CPICH), and a forward access channel (FACH) for providing various other types of control messages to user equipment units (UEs). In the reverse or uplink direction, a random access channel (RACH) is employed by user equipment units (UEs) whenever access is desired to perform location registration, call origination, page response, and other types of access operations. The random access channel (RACH) is also used for carrying certain user data, e.g., best effort packet data for, e.g., web browser applications.

0028As set up by the control channels, traffic channels (TCH) are allocated to carry substantive call communications with a user equipment unit (UE). Some of the traffic channels can be common traffic channels, while others of the traffic channels can be dedicated traffic channels (DCHs).

0029<figref idref="f0002">Fig. 2</figref> shows selected general aspects of user equipment unit (UE) 30 and illustrative nodes such as radio network controller 26 and base station 28. The user equipment unit (UE) 30 shown in <figref idref="f0002">Fig. 2</figref> includes a data processing and control unit 31 for controlling various operations required by the user equipment unit (UE). The UE's data processing and control unit 31 provides control signals as well as data to a radio transceiver 33 connected to an antenna 35.

0030The example radio network controller 26 and base station 28 as shown in <figref idref="f0002">Fig. 2</figref> are radio network nodes that each include a corresponding data processing and control unit 36 and 37, respectively, for performing numerous radio and data processing operations required to conduct communications between the RNC 26 and the user equipment units (UEs) 30. Part of the equipment controlled by the base station data processing and control unit 37 includes plural radio transceivers 38 connected to one or more antennas 39.

0031In accordance with the present invention, the base station data processing and control unit 37 performs a base station resource measurement and reporting program 100. As generically shown in <figref idref="f0002">Fig. 2</figref> and <figref idref="f0005">Fig. 3</figref>, the base station resource measurement and reporting program 100 sends, to a UTRAN management program 104 (executing at radio network controller (RNC) node 26), a node capacity indication 110 which is based on a number of connections that can be added for each of plural spreading factors. In a first message mode of the invention, the capacity indication 110 may be included in (e.g., appended to) a conventional 3GPP "Resource Status Indication" message (RSI message 102), while in a second message mode the capacity indication 110 is included in a separate supplemental message (herein illustrated as capacity message 112).

0032<figref idref="f0005">Fig. 3</figref> shows a simplified representative structure of a generic base station (BS) 28 for the sake of illustrating operation of base station resource measurement and reporting program 100. In view of its representative nature, base station (BS) 28 has various base station devices 50, depicted as devices 50A - 50N in <figref idref="f0005">Fig. 3</figref>. Each device 50 needs to be allocated to radio links and/or radio link sets. The devices 50 are controlled by a device handler 52.

0033The types of devices 50 included at a base station can be several. Some of the devices 50 are of a type which are shared among plural users, and consequentially are not of particular interest to the present invention. Such shared devices include power amplifiers and low noise amplifiers, for example. Other devices 50 are of a type which are dedicated to one connection and are service dependent. These types of devices can generally be characterized as pertaining to coding and decoding, and include CRC handling, forward error correction, rate matching, interleaving, and radio frame segmentation. For these types of devices, the amount of resources required per connection is influenced by the service(s) carried by the connection, which has a strong relation to spreading factor. Yet other devices 50 are dedicated to one connection but are service independent. Examples of these devices are rate matching and mapping to physical channels, modulation/demodulation, and spreading/despreading. Unlike the service dependent devices, whether the connection is in softer handover or not is an issue for service independent devices, e.g., the number of spreaders relates directly to the number of cells occupied by a connection.

0034<figref idref="f0008">Fig. 4</figref> provides some examples of the types of devices 50 which are handled by device handler 52 of base station (BS) node 28. Device 50A is a Downlink Cell Oriented Processing (DCOP) device which includes power amplification and scrambling. Device 50B is an Uplink Cell Oriented Processing (UCOP) device which includes low noise amplification and descrambling. Device 50C is a Downlink Service Oriented Processing (DSOP) device which includes CRC generation, FEC coding, rate matching, interleaving, and radio frame segmentation. Device 50D is an Uplink Service Oriented Processing (USOP) device which includes CRC generation, FEC decoding, rate matching, deinterleaving, and radio frame desegmentation. Device 50E is a Downlink Link Oriented Processing (DLOP) device which includes rate matching, mapping to physical channels, modulation, and spreading. Device 50F is an Uplink Link Oriented Processing (ULOP) device which includes rate matching, demodulation, and despreading. Although not illustrated as such in <figref idref="f0008">Fig. 4</figref>, it should be understood that a base station node may have one or more of each type of device 50.

0035For each device 50, base station resource measurement and reporting program 100 has a corresponding device model 52. In the illustrated embodiment, each 52 is a software object. In addition, base station resource measurement and reporting program 100 has a software object 56 which is a collection of data which serves to model base station (BS) 28, and which is therefore denominated as model BS node 56.

0036The two message modes of the present invention are described as non-limiting examples of how a base station (BS) node 28 can send its capacity indication to a controlling node, such as to radio controller (RNC) node 26. In this regard, <figref idref="f0003">Fig. 2A</figref>, <figref idref="f0006">Fig. 3A</figref>, and <figref idref="f0009">Fig. 5A</figref> concern a first message mode of the invention in which the capacity indication is included in (e.g., appended to) a conventional 3GPP "Resource Status Indication" message (RSI message 102). <figref idref="f0004">Fig. 2B</figref>, <figref idref="f0007">Fig. 3B</figref>, and <figref idref="f0010">Fig. 5B</figref> concern another message mode of the invention in which the capacity indication is included in a capacity message 112 which is separate and distinct from the conventional 3GPP "Resource Status Indication" message (RSI message 102).

0037<figref idref="f0009">Fig. 5A</figref> and <figref idref="f0010">Fig. 5B</figref> show certain processes which are involved in the base station resource measurement and reporting program 100 in accordance with the two respective message modes. Since most of the operations/processes of the two message modes are similar, a description of the <figref idref="f0009">Fig. 5A</figref> embodiment is described as representative of the invention generally, with subsequent comment being provided for distinguishing the message modes of <figref idref="f0009">Fig. 5A</figref> and <figref idref="f0010">Fig. 5B</figref>.

0038<figref idref="f0009">Fig. 5A</figref> (and to some extent <figref idref="f0006">Fig. 3A</figref>) shows basic example operations involved with the base station resource measurement and reporting program 100 which executes on data processing and control unit 37 of base station (BS) node 28 in accordance with the first message mode of the invention. The basic operations comprising the example embodiment of base station resource measurement and reporting program 100 include node status process 5-1; RSI message generation process 5-2A; RSI message reporting requirement process 5-3; node resource tracking process 5-4; capacity assessment process 5-5; and, capacity indication reporting requirement process 5-7.

0039The node status process 5-1 serves to notify RSI message generation process 5-2 that a RSI message 102 should be generated. The events which prompt node status process 5-1 to serve its notification are listed in Third Generation Partnership Project (3GPP) Specification 25.433, section 8.2.15.2. Such events include, for example, a change in the capacity of base station (BS) node 28; start-up of a cell; or when a hardware failure occurs at the base station (BS) node 28.

0040When prompted by node status process 5-1, the RSI message generation process 5-2 generates the RSI message 102. The node status process 5-1 uses the model BS node 56 to prepare the RSI message 102. The model BS node 56 is a model which includes the total capacity of base station (BS) 28 in terms of "credits" and "Consumption Laws", stating the credit consumption for each spreading factor per radio link set separately for uplink (UP) and downlink (DL). Thus, a first purpose of the RSI message 102 of the present invention is s essentially to transfer the model BS node 56 to the UTRAN management process in RNC 26, as depicted by the software object model BS node 56' in <figref idref="f0005">Fig. 3</figref>. Thus, in accordance with this first purpose, at least a portion of the format of the RSI message 102 is understood with reference to Third Generation Partnership Project (3GPP) Specification 25.433, section 9.1.31.

0041As mentioned above, the RSI message 102 is prepared in accordance with "Consumption Laws". A simplified illustrative example of utilization of the Consumption Laws for generating the RSI message 102 follows. For sake of simplified illustration, assume that base station (BS) node 28 has a certain capacity rating of 300 for its downlink transmissions (e.g., DL Capacity Credit = 300) and a capacity rating of 500 for its uplink transmissions (e.g., UL Capacity Credit = 500). Assume further that the spreading factor (SF) values available at base station (BS) node 28 are as follows: 4, 8, 16, 32, 64, 128, and 256; which is expressed as in the manner of Expression 1. <maths id="math0001" num="Expression 1"><math display="block"><mi>SF</mi><mo>=</mo><mfenced open="{" close="}"><mn>4</mn><mn>8</mn><mn>16</mn><mn>32</mn><mn>64</mn><mn>128</mn><mn>256</mn></mfenced></math><img file="EP1323325B1_D0001.tif" /></maths>

0042As is generally termed, the spreading factor SF is the processing gain, i.e., the ratio of transmission bandwidth and information bandwidth. The spreading factor or processing gain essentially determines the number of users that can be allowed in a system, the amount of multi-path effect reduction, the difficulty to jam or detect a signal etc. For spread spectrum systems it is advantageous to have a processing gain as high as possible.

0043Further assume, for the simplified illustration, that the downlink consumption law for base station (BS) node 28 (for both common channels and dedicated channels) is expressed by Expression 2, while the uplink consumption law for base station (BS) node 28 is expressed by Expression 3: <maths id="math0002" num="Expression 2"><math display="block"><mi>DL Cost</mi><mo>=</mo><mfenced open="{" close="}"><mn>30</mn><mn>20</mn><mn>12</mn><mn>8</mn><mn>4</mn><mn>2</mn><mn>1</mn></mfenced></math><img file="EP1323325B1_D0002.tif" /></maths><maths id="math0003" num="Expression 3"><math display="block"><mi>UL Cost</mi><mo>=</mo><mfenced open="{" close="}"><mn>16</mn><mn>14</mn><mn>12</mn><mn>10</mn><mn>8</mn><mn>6</mn><mn>4</mn></mfenced></math><img file="EP1323325B1_D0003.tif" /></maths>

0044The information equivalent to that of Expression 2 and Expression 3 is included in the RSI message 102 sent from base station resource measurement and reporting program 100 of base station (BS) node 28 to radio network controller (RNC) node 26. Then, given the foregoing assumptions and upon receipt of the RSI message 102, the UTRAN management process 104 at radio network controller (RNC) node 26 and the base station resource measurement and reporting process 100 of base station 28 can independently calculate how much of base station (BS) node 28 is occupied. The base station (BS) 28 and the radio network controller (RNC) node 26 can independently calculate the occupancy of base station (BS) 28 by applying Expression 4. <maths id="math0004" num="Expression 4"><math display="block"><mi>L</mi><mo>=</mo><mstyle displaystyle="true"><munderover><mo>∑</mo><mi mathvariant="italic">sf</mi><mi mathvariant="italic">all SF</mi></munderover></mstyle><msub><mi>N</mi><mi mathvariant="italic">sf</mi></msub><mo>•</mo><msub><mi>C</mi><mi mathvariant="italic">sf</mi></msub></math><img file="EP1323325B1_D0004.tif" /></maths>

0045In Expression 4: <dl id="dl0001" compact="compact"><dt>L</dt><dd>= load/occupancy;</dd><dt>N_sf</dt><dd>= number of allocations with spreading factor sf; and</dd><dt>C_sf</dt><dd>= consumption for spreading factor sf according to reported consumption law.</dd></dl>

0046The determination of load/occupancy (e.g., using Expression 4) is applied separately both on UL and DL. A comparison between the load L and the earlier reported 'credits' indicates the occupancy of the base station (BS) 28.

0047Thus, the calculation is performed by multiplying the actual allocated channels of each spreading factor (SF) by the cost defined for that spreading factor. Suppose, for example, that number of channels active for each of the possible spreading factors (listed in the "SF" row of Table 2) is as shown in the "channels" row of Table 2. The radio network controller (RNC) node 26, which controls channel allocation, knows the number of channels active for each spreading factor. Using the information supplied in RSI message 102, e.g., the "DL cost" row and "UL cost" row of Table 2, the UTRAN management process 104 can determine the total cost relative to each spreading factor for each link direction (shown in the "DL total cost" row of Table 2 and the "UL total cost" row of Table 2). Adding the total costs for all spreading factors for the downlink, UTRAN management process 104 obtains a value of 282, and in view of the capacity rating of 300 for its downlink transmissions for base station (BS) node 28, determines that the downlink hardware of base station (BS) node 28 is 94% occupied. Similarly, adding the total costs for all spreading factors for the uplink, UTRAN management process 104 obtains a value of 444, and in view of the capacity rating of 500 for the uplink transmissions, determines that the uplink hardware of base station (BS) node 28 is 89% occupied. <tables id="tabl0002" num="0002"><table frame="all"><title><u>TABLE 2</u></title><tgroup cols="8"><colspec colnum="1" colname="col1" colwidth="22mm" /><colspec colnum="2" colname="col2" colwidth="10mm" /><colspec colnum="3" colname="col3" colwidth="10mm" /><colspec colnum="4" colname="col4" colwidth="10mm" /><colspec colnum="5" colname="col5" colwidth="10mm" /><colspec colnum="6" colname="col6" colwidth="10mm" /><colspec colnum="7" colname="col7" colwidth="11mm" /><colspec colnum="8" colname="col8" colwidth="11mm" /><tbody><row><entry>SF</entry><entry align="center">4</entry><entry align="center">8</entry><entry align="center">16</entry><entry align="center">32</entry><entry align="center">64</entry><entry align="center">128</entry><entry align="center">256</entry></row><row><entry>Channels</entry><entry align="center">1</entry><entry align="center">2</entry><entry align="center">4</entry><entry align="center">8</entry><entry align="center">12</entry><entry align="center">16</entry><entry align="center">20</entry></row><row><entry>DL cost</entry><entry align="center">30</entry><entry align="center">20</entry><entry align="center">12</entry><entry align="center">8</entry><entry align="center">4</entry><entry align="center">2</entry><entry align="center">1</entry></row><row><entry>DL total cost</entry><entry align="center">30</entry><entry align="center">40</entry><entry align="center">48</entry><entry align="center">64</entry><entry align="center">48</entry><entry align="center">32</entry><entry align="center">20</entry></row><row><entry>UL cost</entry><entry align="center">16</entry><entry align="center">14</entry><entry align="center">12</entry><entry align="center">10</entry><entry align="center">8</entry><entry align="center">6</entry><entry align="center">4</entry></row><row><entry>UL total Cost</entry><entry align="center">16</entry><entry align="center">28</entry><entry align="center">48</entry><entry align="center">80</entry><entry align="center">96</entry><entry align="center">96</entry><entry align="center">80</entry></row></tbody></tgroup></table></tables>

0048The RSI message reporting requirement process 5-3 specifies how the RSI message 102 is to be reported and/or formatted. For example, the RSI message reporting requirement process 5-3 apprises RSI message generation process 5-2 whether the RSI message 102 is to report UL and DL values separately or in combination.

0049It will be recalled that, in the first message mode of the invention, the RSI message 102 additionally contains the capacity indication of the present invention. In this regard, using the resource tracking process 5-4, the base station resource measurement and reporting program 100 keeps track of the usage of each type of resource/device. As part of resource tracking process 5-4, the number (N_sf) of allocations in radio base station (RBS) 28 with spreading factor sf and the total number (N) of allocations in the radio base station (RBS) 28 are determined.

0050The capacity assessment process 5-5 ultimately determines the capacity of the radio base station (RBS) 28, and prepares the capacity indication 110. In this first message mode of the invention, the capacity indication calculated by the capacity assessment process 5-5 is included in the modified RSI message 102 as shown in <figref idref="f0003">Fig. 2A</figref>, <figref idref="f0006">Fig. 3A</figref>, and <figref idref="f0009">Fig. 5A</figref>. As described below, the capacity message report requirement process 5-7 specifies to some degree how the capacity indication 110 is to be formatted.

0051The capacity indication 110 can be provided to network controller (RNC) node 26 in diverse formats, as required by capacity indication report requirement process 5-7. In a first reporting mode of the invention, the capacity indication is actually a vacancy capacity value, indicating the number of connections that can be added for each spreading factor. In this first reporting mode of the invention, the capacity indication 110 includes a series of values A_sf, the values A_sf indicating how many allocations/connections of each possible spreading factor (sf) can be added before reaching the capacity limit. In accordance with a second reporting mode of the invention, the capacity value transmitted by capacity indication 110 is a total capacity value which reflects both the existing load and vacancy capacity over all spreading factors. The first reporting mode and the second reporting mode can be applicable to both the first message mode and the second message mode.

0052In the first reporting mode of the invention, user or other input to the capacity indication report requirement process 5-7 can specify that the capacity indication 110 is to report how many connections can be added for one or more spreading factors (sf), considering the various types of resources/devices. In other words, the capacity indication report requirement process 5-7 determines for one or more spreading factors (sf) the amount of connections (i.e., number of allocations) that can be added. As further described with reference to <figref idref="f0011">Fig. 6</figref>, the capacity assessment process 5-5 uses the device models 54 to calculate how many allocations/connections (A_sf) of each possible spreading factor (sf) can be added before reaching the capacity limit. The capacity indication 110 includes a series of values A_sf, the values A_sf indicating how many allocations/connections of each possible spreading factor (sf) can be added before reaching the capacity limit. Thus, in this first reporting mode the capacity indication 110 includes a vacancy capacity value for each spreading factor. The capacity indication 110 of this mode can be generated separately for uplink (UL) and downlink (DL), if the capacity indication report requirement process 5-7 so indicates.

0053In the second reporting mode of the invention, user or other input to the capacity indication report requirement process 5-7 can specify that the capacity indication 110 is to report a single value indicative of totally capacity of radio base station (RBS) 28. In this second reporting mode, capacity assessment process 5-5 determines the total capacity value (e.g., a capacity value for the uplink [UL] and a capacity value for the downlink [DL]), with one technique of doing so being described below.

0054In the second reporting mode, as in the first reporting mode, the capacity assessment process 5-5 uses the device models 54 to calculate how many allocations (A_sf) of each possible spreading factor (sf) can be added before reaching the capacity limit. Example logic for determining the allocations (A_sf) of each possible spreading factor (sf) that can be added is illustrated in <figref idref="f0011">Fig. 6</figref> and described below. The different devices 50 may result in different amounts. The number that can be added is then the minimum of the numbers of the various devices. The capacity assessment process 5-5 thus initially provides an indication of how many connections of a spreading factor can be added if all added connections are of the same spreading factor.

0055Next, for the second reporting mode, the capacity assessment process 5-5 calculates the amount of free resources, expressed in terms of credits. One way of calculating the amount of free resources is provided by Expression 5: <maths id="math0005" num="Expression 5"><math display="block"><mi>F</mi><mo>=</mo><mstyle displaystyle="true"><munderover><mo>∑</mo><mi mathvariant="italic">sf</mi><mi mathvariant="italic">all SF</mi></munderover></mstyle><msub><mi>W</mi><mi mathvariant="italic">sf</mi></msub><mo>•</mo><msub><mi>A</mi><mi mathvariant="italic">sf</mi></msub><mo>•</mo><msub><mi>C</mi><mi mathvariant="italic">sf</mi></msub></math><img file="EP1323325B1_D0005.tif" /></maths>

0056In Expression 5: <dl id="dl0002" compact="compact"><dt>F</dt><dd>= free resources;</dd><dt>W_sf</dt><dd>= a weighting factor for spreading factor sf;</dd><dt>A_sf</dt><dd>= number of connections that can be added with spreading factor sf;</dd><dt>C_sf</dt><dd>= consumption for spreading factor sf according to reported consumption law.</dd></dl>

0057In one example embodiment, the weighting factor W_sf for the spreading factors sf is equal the number of connections with that spreading factor as a fraction of all connections, i.e., Nsf/N, where N_sf is the number of allocations in base station with spreading factor sf and N is the total number of allocations in the base station, so that for this weighting scheme Expression 5 can be rewritten as Expression 6: <maths id="math0006" num="Expression 6"><math display="block"><mi>F</mi><mo>=</mo><mstyle displaystyle="true"><munderover><mo>∑</mo><mi mathvariant="italic">sf</mi><mi mathvariant="italic">all SF</mi></munderover></mstyle><mfrac><msub><mi>N</mi><mi mathvariant="italic">sf</mi></msub><mi>N</mi></mfrac><mo>•</mo><msub><mi>A</mi><mi mathvariant="italic">sf</mi></msub><mo>•</mo><msub><mi>C</mi><mi mathvariant="italic">sf</mi></msub></math><img file="EP1323325B1_D0006.tif" /></maths>

0058A new capacity is than calculated by adding the load L and the free amount F, as shown in Expression 7: <maths id="math0007" num="Expression 7"><math display="block"><msub><mi mathvariant="italic">Cap</mi><mi mathvariant="italic">new</mi></msub><mo>=</mo><mi>L</mi><mo>+</mo><mi>F</mi></math><img file="EP1323325B1_D0007.tif" /></maths>

0059Since the evaluation of Expression 5 or Expression 7 depends upon the factors A_sf, the value ultimately transmitted by the capacity indication 110 in this second mode is said to be based on the determination of how many allocations/connections (A_sf) of each possible spreading factor (sf) can be added before reaching the capacity limit.

0060In one variation of the first message mode, the capacity indication report requirement process 5-7 can also authorize RSI message generator 5-2A to generate a RSI message 102 with the capacity indication 110 in accordance with various criteria, of which the following are examples: (1) the absolute difference between the newly calculated capacity and the most recently reported capacity is larger than a predetermined threshold; (2) the current load L is larger than a predetermined load threshold; (3) the time since the last update is larger than a predetermined time lapse threshold.

0061In the second message mode of the invention, illustrated with reference to <figref idref="f0004">Fig. 2B</figref>, <figref idref="f0007">Fig. 3B</figref>, and <figref idref="f0010">Fig. 5B</figref>, the capacity indication is the subject of a separate message which is sent from the base station (BS) node 28 to the radio controller (RNC) node 26, e.g., in a capacity message 112 which is separate and distinct from the RSI message 102. For this second message mode, the basic operations comprising the example embodiment of base station resource measurement and reporting program 100 include node status process 5-1; RSI message generation process 5-2B; RSI message reporting requirement process 5-3; node resource tracking process 5-4; capacity assessment process 5-5; capacity message generation process 5-6, and, capacity indication reporting requirement process 5-7.

0062As in the first message mode, the node status process 5-1 of the second message mode serves to notify RSI message generation process 5-2 that a RSI message 102 should be generated. When prompted by node status process 5-1, the RSI message generation process 5-2 generates the RSI message 102. The RSI message 102 of the second message mode is a conventional RSI message which does not additionally carry the capacity indication of the present invention. The node status process 5-1 uses the model BS node 56 to prepare the RSI message 102. Thus, the RSI message 102 essentially transfers the model BS node 56 to the UTRAN management process in RNC 26, as depicted by the software object model BS node 56' in <figref idref="f0007">Fig. 3B</figref>. The RSI message 102 is understood with reference to Third Generation Partnership Project (3GPP) Specification 25.433, section 9.1.31. The RSI message reporting requirement process 5-3 specifies how the RSI message 102 is to be reported and/or formatted. For example, the RSI message reporting requirement process 5-3 apprises RSI message generation process 5-2B whether the RSI message 102 is to report UL and DL values separately or in combination.

0063Also as in the first message mode, the resource tracking process 5-4 for the second message mode of the base station resource measurement and reporting program 100 keeps track of the usage of each type of resource/device. As part of resource tracking process 5-4, the number (N_sf) of allocations in radio base station (RBS) 28 with spreading factor sf and the total number (N) of allocations in the radio base station (RBS) 28 are determined.

0064The capacity assessment process 5-5 of the second message mode ultimately determines the capacity of the radio base station (RBS) 28, and prepares the capacity indication 110. Whether operating in the either the first reporting mode or the second reporting mode, the capacity assessment process 5-5 uses the device models 54 to calculate how many allocations (A_sf) of each possible spreading factor (sf) can be added before reaching the capacity limit, in the manner subsequently described with respect to <figref idref="f0011">Fig. 6</figref>. When operating in the second reporting mode, the capacity assessment process 5-5 proceeds to perform calculations to obtain a new capacity for the node, using calculations such as those in Expression 5, Expression 6 and Expression 7 discussed above.

0065Thus, in the second message mode of the invention, the capacity indication calculated by the capacity assessment process 5-5 is included in a separate capacity message, e.g., capacity message 112 illustrated in <figref idref="f0004">Fig. 2B</figref>, <figref idref="f0007">Fig. 3B</figref>, and <figref idref="f0010">Fig. 5B</figref>. The capacity message 112 is actually prepared by capacity message generator 5-6. The capacity message generator 5-6 generates the capacity message 110 when requested to do so by capacity message report requirement process 5-7. The capacity indication report requirement process 5-7 may authorize capacity message generator 5-6 to generate a capacity message 112 with the capacity indication 110 in accordance with various criteria, of which the following are examples: (1) the absolute difference between the newly calculated capacity and the most recently reported capacity is larger than a predetermined threshold; (2) the current load L is larger than a predetermined load threshold; (3) the time since the last update is larger than a predetermined time lapse threshold.

0066Thus, from the foregoing it will be appreciated that the separate capacity message 112 of the first message mode of the invention can be prepared in accordance with either the first reporting mode of the invention or the second reporting mode. In the first reporting mode, the capacity indication 110 of the capacity message 112 includes a series of values A_sf, the values A_sf indicating how many allocations/connections of each possible spreading factor (sf) can be added before reaching the capacity limit. In accordance with the second reporting mode of the invention, the capacity value transmitted by capacity message 110 is a total capacity value which reflects both the existing load and vacancy capacity over all spreading factors.

0067<figref idref="f0011">Fig. 6</figref> shows example logic which can be utilized for making an accurate calculation of the number of allocations/connections (A_sf) of each possible spreading factor (sf) can be added before reaching the capacity limit. The logic of <figref idref="f0011">Fig. 6</figref> can be implemented by the capacity assessment function 5-5 of either the first message mode (<figref idref="f0009">Fig. 5A</figref>) or the second message mode (<figref idref="f0010">Fig. 5B</figref>). Further, the logic for the determination of the number of allocations/connections (A_sf) is utilized in both reporting modes, including as a preliminary determination in the second reporting mode prior to evaluating expressions such as Expression 5, Expression 6, and Expression 7 as above described.

0068Block 6-1 of <figref idref="f0011">Fig. 6</figref> depicts beginning of the calculation, for a certain spreading factor, of the number of allocations/connections (A_sf) that can be added for that spreading factor before reaching the capacity limit. In actuality, block 6-1 is the first step of a spreading factor loop (comprising all but the last step 6-11 of <figref idref="f0011">Fig. 6</figref>) which is performed for each spreading factor applicable to the base station (BS) node 28.

0069The logic of <figref idref="f0011">Fig. 6</figref> has two loops nested within the spreading factor loop. The first loop is a device type loop, which is initialized at step 6-2 and extends through step 6-8. For each spreading factor, the device type loop is executed for each device type of the base station (BS) node 28. Examples of certain device types are illustrated and previously discussed with reference to <figref idref="f0008">Fig. 4</figref>. The initialization of step 6-2 includes a zeroing of the sum A_{Sf-DEVICE_TYPE}.

0070The second loop nested within the spreading factor loop is the device number loop. The device number loop is initialized at step 6-3, and extends through step 6-7. The device number loop can be repetitive in a situation in which there is more than one of the same device types at the base station (BS) node 28. For example, there may be two DSOP devices at the base station (BS) node 28, in which case for the device type DSOP the device number loop will be executed twice.

0071The device number loop comprises steps 6-4 through 6-6, which are consecutively performed for each device. At step 6-4, a determination is made of the amount of free resources at the device for the spreading factor of concern for this iteration. In the sense of <figref idref="f0011">Fig. 6</figref>, "free resources" includes, for example, the available Mips for a processor or bytes in memory, as ascertained from the device models 54. Then, at step 6-5, an integer division is performed by dividing the amount of the free resources (as determined at step 6-4) by the amount of the resources required per connection by this device for the spreading factor of concern for this iteration. At step 6-6 the integer quotient of the division of step 6-5 is added to the sum A_{sf-DEVICE_TYPE}, which represents the number of connections/allocations which can be added for this device type for the spreading factor involved in the iteration.

0072After the sum A_{sf-DEVICE_TYPE} has been accumulated for all devices of the same device, the device type loop is executed (as indicated by the negative arrow leading from block 6-8 to block 6-2) for the next device type. After it is determined at step 6-8 that all device types for the spreading factor have been considered, at step 6-9 the lowest A_{sf-DEVICE_TYPE} sum for all device types is reported as the A_sf for the spreading factor of concern for the iteration. Similar determinations are made for each spreading factor in use at the node by repeated executions of the spreading factor loop, until it is determined at step 6-10 that all spreading factors have been processed.

0073The logic of <figref idref="f0011">Fig. 6</figref>, including the integer division of step 6-5, gives a realistic assessment of how much usable capacity really exists at the devices of the node for each spreading factor. Such logic avoids the segmentation problem discussed above.

0074Thus, in the aforedescribed embodiments of the present invention, the device handler 52 has a detailed model 54 of each of the devices 52. Using these models 54, very accurate information is available regarding the load on the corresponding devices 52. Moreover, using the models 54 the base station resource measurement and reporting program 100 can calculate how many allocations of each spreading factor can be added before reaching a capacity limit.

0075In addition, the device handler 52 has a model 56 for the entire radio base station (RBS) 28. This base station node model 56 is the total capacity of the radio base station (RBS) 28 in terms of 'credits' and a consumption law, stating the 'credit consumption' for each SF per RLS separately for UL and DL. This model 56 is transferred to the radio network controller (RNC) 26 through certain fields of the standardized NBAP messages (RSI message 102). As it only considers the spreading factors (SF), the node model 56 is much less accurate than the internal device models 54.

0076The present invention therefore does not assume that resource usage depends only on the individual spreading factors (SFs), and does take into consideration the loss in efficiency through segmentation. Moreover, the present invention considers that several types of resources can be involved in a connection, with possible different characteristics to its use.

0077Other more detailed illustrative examples of radio network controller (RNC) node 26 and base station (BS) node 28 with which the invention can suitably be employed are illustrated in <figref idref="f0012">Fig. 7</figref> and <figref idref="f0013">Fig. 8</figref>, respectively. In this regard, <figref idref="f0012">Fig. 7</figref> illustrates, in somewhat more detail, an example non-limiting RNC node 26 of the present invention. It so happens that the RNC node 26 of <figref idref="f0013">Fig. 8</figref> is a switched-based node having a switch 120. The switch 120 serves to interconnect other constituent elements of RNC node 26. Such other constituent elements include extension terminals 122₁ through 122_n, as well as extension terminal 124. Extension terminals 122₁ through 122_n essentially function to connect RNC node 26 to the base stations 28 served by RNC node 26; extension terminal 124 connects RNC node 26 across the Iu interface to the core network.

0078Yet other constituent elements of RNC node 26 include diversity handover unit 126; an ALT unit 128; codex 130; timing unit 132; a data services application unit 134; and, a main processor 140. The person skilled in the art will appreciate generally the functions of these constituent elements, it being noted that the ALT unit 128 is a unit which provides, e.g., multiplexing and demultiplexing and (optionally) queuing with regard to differing protocols of cells.

0079<figref idref="f0013">Fig. 8</figref> illustrates, in non-limiting manner, more details of an example base station (BS) node 28 in accordance with one embodiment of the present invention. As with RNC node 26, the base station (BS) node 28 of <figref idref="f0013">Fig. 8</figref> is a switched-based node having a switch 220 which serves to interconnect other constituent elements of base station (BS) node 28. Such other constituent elements include extension terminal 222; ALT unit 228; BS main processor 240, and interface boards 242.

0080Extension terminal 222 connects base station (BS) node 28 to radio network controller (RNC) node 26, and thus comprises the Iub interface. As in the case of radio network controller (RNC) node 26, the ALT unit 228 is a unit which provides, e.g., multiplexing and demultiplexing and (optionally) queuing with regard to differing protocols of cells.

0081The embodiment of base station (BS) node 28 illustrated in <figref idref="f0013">Fig. 8</figref> is housed in a rack having multiple subracks. Each subrack has one or more boards, e.g., circuit boards, mounted thereon. A first subrack 250 contains boards for each of extension terminal 222; ALT unit 228; BS main processor 240, and interface boards 242. Each of the interface boards 242 is connected to a board on another subrack, e.g., one of the transmitter boards 260 or one of the receiver boards 270. Each receiver board 270 is connected to share certain transmitter/receiver resources in a corresponding transmitter board 260, with the transmitter board 260 being connected to a corresponding one of amplifiers and filters board 280. The amplifiers and filters board 280 is connected to an appropriate antenna 39. For example, interface board 242_1-T is connected to transmitter board 260₁, while interface board 242_1-R is connected to receiver board 270₁. The pair of transmitter board 260₁ and receiver board 270₁ is, in turn, competed to amplifiers and filters board 280₁. Similar connections exist for a second pairing of transmitter board 260₂ and receiver board 270₂, which interface via interface board 242_2-T and interface board 242_2-R, respectively. Each transceiver 38 of <figref idref="f0002">Fig. 2</figref> thus comprises a subrack which includes a transmitter board 260, a receiver board 270, and amplifiers and filters board 280.

0082In one example embodiment, base station (BS) node 28 is an ATM-based node, with interface boards 242 performing various ATM interfacing functions. The transmitter boards 260 and receiver boards 270 each include several devices. For example, each transmitter board 260 includes unillustrated elements such as an interface connected to its corresponding interface board 242; an encoder; a modulator; and, a baseband transmitter. In addition, the transmitter board 260 includes the transmitter/receiver sources which it shares with receiver board 270, including a D/G transmitter and an radio frequency transmitter. Each receiver board 270 includes unillustrated elements such as an interface connected to its corresponding interface board 242; a decoder; a demodulator; and a baseband receiver. Each amplifiers and filters board 280 includes amplifiers, such as MCPA and LNA amplifiers.

0083In the example base station (BS) node 28 of <figref idref="f0013">Fig. 8</figref>, BS main processor 240 executes base station resource measurement and reporting program 100. For the example radio network controller (RNC) node 26 shown in <figref idref="f0012">Fig. 7</figref>, main processor 140 executes UTRAN management program 104.

0084While 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 scope of the appended claims. For example, while nodes of the present invention have been illustrated for sake of example as being ATM-based nodes, it should be understood that the invention is not so limited, and that other communication protocols and/or cell structures can be utilized for communicating on an inter-node and intra-node bases.