NETWORK NODE AND A METHOD PERFORMED THEREBY FOR CONGENSTION CONTROL OF A RADIO BASE STATION

Abstract

A network node and a method performed by the network node for congestion control in a Radio Base Station, RBS, are provided. The method comprises determining that the RBS is congested. The method further comprises determining an interference level in a neighbouring RBS caused by wireless devices currently being served by the RBS, or determining a level of inter-cell coupling between the RBS and the neighbouring RBS. Still further, method comprises increasing a value of an average received signal level target, P.sub.0, for wireless devices currently being served by the RBS if the RBS is congested, if the determined interference level in the neighbouring RBS is below an interference threshold or if the level of inter-cell coupling is below a coupling threshold.

Claims

1. A method performed by a network node for congestion control of a Radio Base Station, RBS, the method comprising: determining that the RBS is congested; determining one of: an interference level in a neighbouring RBS caused by wireless devices currently being served by the RBS; and a level of inter-cell coupling between the RBS and the neighbouring RBS; and increasing a value of an average received signal level target, P.sub.0, for wireless devices currently being served by the RBS if one of: the RBS is congested; if the determined interference level in the neighbouring RBS is below an interference threshold; and if the level of inter-cell coupling is below a coupling threshold.

2. The method according to claim 1, wherein both the interference level in a neighbouring RBS caused by wireless devices currently being served by the RBS and the level of inter-cell coupling between the RBS and the neighbouring RBS are determined, wherein the average received signal level target, P.sub.0, is increased, if the determined interference level in the neighbouring RBS is below the interference threshold and if the level of inter-cell coupling is below the coupling threshold.

3. The method according to claim 1, further comprising determining a received signal quality in the neighbouring RBS, wherein the average received signal level target, P.sub.0, is increased, if the received signal quality in the neighbouring RBS is also above a signal quality threshold.

4. The method according to claim 1, further comprising determining a ratio of power limited samples received by the RBS from wireless devices currently being served by the RBS, wherein the average received signal level target, P.sub.0, is increased, if the ratio of power limited samples is also below a power limiting threshold.

5. The method according to claim 1, wherein determining that the RBS is congested comprises comparing a Congestion Indicator parameter against a congestion threshold, wherein the RBS is determined to be congested if the Congestion Indicator parameter is at least equal to the congestion threshold.

6. The method according to claim 1, wherein determining the ratio of power limited samples comprises determining a number of received transmissions, from wireless devices, having been transmitted at a limited transmission power, determining a total number of received transmission samples from wireless devices, and determining the ratio of power limited samples received by the RBS from wireless devices currently being served by the RBS by dividing the determined number of received transmissions, from wireless devices, having been transmitted at a limited transmission power by the determined total number of received transmission samples from wireless devices.

7. The method according to claim 1, wherein determining the interference level in a neighbouring RBS caused by wireless devices currently being served by the RBS comprises receiving a report from the neighbouring RBS indicating a percentage of average interference in the neighbouring RBS caused by wireless devices currently being served by the RBS.

8. The method according to claim 1, wherein increasing P.sub.0 is performed by adding a step value to the current P.sub.0.

9. The method according to claim 1, wherein determining an interference level in a neighbouring RBS caused by wireless devices currently being served by the RBS, is performed for every neighbouring RBS of the RBS for which congestion control is being performed.

10-12. (canceled)

13. A network node for congestion control of a Radio Base Station, RBS, the network node being configured to: determine that the RBS is congested; determine one of: an interference level in a neighbouring RBS caused by wireless devices currently being served by the RBS; and determining a level of inter-cell coupling between the RBS and the neighbouring RBS; and increase a value of an average received signal level target, P.sub.0, for wireless devices currently being served by the RBS if one of: the RBS is congested; if the determined interference level in the neighbouring RBS is below an interference threshold; and if the level of inter-cell coupling is below a coupling threshold.

14. The network node according to claim 13, wherein the network node is configured to determine both the interference level in a neighbouring RBS caused by wireless devices currently being served by the RBS and the level of inter-cell coupling between the RBS and the neighbouring RBS, wherein the network node is configured to increase the average received signal level target, P.sub.0, if the determined interference level in the neighbouring RBS is below the interference threshold and if the level of inter-cell coupling is below the coupling threshold.

15. The network node according to claim 13, further configured to determine a received signal quality in the neighbouring RBS, wherein the average received signal level target, P.sub.0, is increased, if the received signal quality in the neighbouring RBS is also above a signal quality threshold.

16. The network node according to claim 13, further configured to determine a ratio of power limited samples received by the RBS from wireless devices currently being served by the RBS, wherein the average received signal level target, P.sub.0, is increased, if the ratio of power limited samples is also below a power limiting threshold.

17. The network node according to claim 13, wherein determining that the RBS is congested comprises the network node being configured to compare a Congestion Indicator parameter against a congestion threshold, wherein the RBS is determined to be congested if the Congestion Indicator parameter is at least equal to the congestion threshold.

18. The network node according to claim 13, wherein determining the ratio of power limited samples comprises the network node being configured to determine a number of received transmissions, from wireless devices, having been transmitted at a limited transmission power, to determine a total number of received transmission samples from wireless devices, and to determine the ratio of power limited samples received by the RBS from wireless devices currently being served by the RBS by dividing the determined number of received transmissions, from wireless devices, having been transmitted at a limited transmission power by the determined total number of received transmission samples from wireless devices.

19. The network node according to claim 13, wherein determining the interference level in a neighbouring RBS caused by wireless devices currently being served by the RBS comprises the network node being configured to receive a report from the neighbouring RBS indicating a percentage of average interference in the neighbouring RBS caused by wireless devices currently being served by the RBS.

20. The network node according to claim 13, wherein the network node is configured to increase P.sub.0 by adding a step value to the current P.sub.0.

21. The network node according to claim 13, wherein the network node is configured to determine an interference level in a neighbouring RBS caused by wireless devices currently being served by the RBS, for every neighbouring RBS of the RBS for which congestion control is being performed.

22-24. (canceled)

25. A computer readable medium storing compute executable code which when, run in a processing unit of a network node, causes the network node to perform a method for congestion control of a Radio Base Station, RBS, the method comprising: determining that the RBS is congested; determining one of: an interference level in a neighbouring RBS caused by wireless devices currently being served by the RBS; and a level of inter-cell coupling between the RBS and the neighbouring RBS; and increasing a value of an average received signal level target, P.sub.0, for wireless devices currently being served by the RBS if one of: the RBS is congested; if the determined interference level in the neighbouring RBS is below an interference threshold; and if the level of inter-cell coupling is below a coupling threshold.

26. (canceled)

Description

BRIEF DESCRIPTION OF DRAWINGS

[0016] Embodiments will now be described in more detail in relation to the accompanying drawings, in which:

[0017] FIG. 1a is a flowchart of a method performed by a network node for congestion control in a Radio Base Station, RBS, according to an exemplifying embodiment.

[0018] FIG. 1b is a flowchart of a method performed by a network node for congestion control in an RBS, according to yet an exemplifying embodiment.

[0019] FIG. 1c is a flowchart of a method performed by a network node for congestion control in an RBS, according to still an exemplifying embodiment.

[0020] FIG. 1d is an exemplifying illustration of a network architecture in conjunction with a centralised solution.

[0021] FIG. 1e is an exemplifying illustration of a network architecture in conjunction with a distributed solution.

[0022] FIG. 2a is a block diagram of an exemplifying embodiment of the method.

[0023] FIG. 2b is a flowchart of an exemplifying embodiment of the method.

[0024] FIG. 2c is a flowchart of an exemplifying embodiment of the method.

[0025] FIG. 3 is a block diagram of a network node for congestion control in an RBS, according to an exemplifying embodiment.

[0026] FIG. 4 is a block diagram of a network node for congestion control in an RBS, according to another exemplifying embodiment.

[0027] FIG. 5 is a block diagram of an arrangement in a network node for congestion control in an RBS, according to an exemplifying embodiment.

DETAILED DESCRIPTION

[0028] Briefly described, a network node and a method performed by the network node are provided for congestion control of an RBS. Different factors may be taken into account in addition to the RBS being congested before taking measures what to do in order to relief the congestion of the RBS.

[0029] Embodiments herein relates to a method performed by a network node for congestion control of an RBS. Embodiments of such a method will now be described with reference to FIG. 1a. FIG. 1a illustrates the method comprising determining 110 that the RBS is congested. The method further comprises determining 120 an interference level in a neighbouring RBS caused by wireless devices currently being served by the RBS, or determining 125 a level of inter-cell coupling between the RBS and the neighbouring RBS. Still further, method comprises increasing 140 a value of an average received signal level target, P.sub.0, for wireless devices currently being served by the RBS if the RBS is congested, if the determined interference level in the neighbouring RBS is below an interference threshold or if the level of inter-cell coupling is below a coupling threshold.

[0030] In a wireless communication network, or system, users of wireless devices typically move about as described above. When users of wireless devices move around, they typically go from one cell to another. The RBS typically has a limited amount of resources, e.g. with regards to radio resources, such that the RBS may be more or less loaded with traffic generated by the wireless devices.

[0031] If an RBS becomes congested, i.e. the network node determines that the RBS is congested 110, meaning that there are a relatively large amount of UEs within the cell being served by the RBS of the cell thereby making use of all or a majority of the radio resources, the network may decide to take some actions in order to somewhat relieve the RBS of the congestion, e.g. the heavy load the RBS is experiencing. Instead of simply handing over UEs being close to the cell border of neighbouring cells to the respective RBSs of the neighbouring cells, the network node determines 120 the interference level in the neighbouring RBS caused by wireless devices currently being served by the RBS, or determines 125 the level of inter-cell coupling between the RBS and the neighbouring RBS. It shall be pointed out that it is not an exclusive or, the RBS may determine both the interference level in the neighbouring RBS caused by wireless devices currently being served by the RBS and the level of inter-cell coupling between the RBS and the neighbouring RBS.

[0032] There are difference ways to determine the interference level in the neighbouring RBS caused by wireless devices currently being served by the RBS. An example is receiving a value of a parameter called SinrTargetSamples. The parameter SinrTargetSamples is cell-level indicator showing percentage of uplink data transmitted with a SINR.sub.UL>SINR.sub.UL,min (i.e. acceptable Signal to Interference and Noise Ratio, SINR, value, since SINR.sub.UL,min is a minimum value) in neighbouring cell or RBS for a period under analysis. SINR.sub.min is an internal constant that is assumed to be fixed, e.g. to −3 dB, as suggested in the literature for the Physical Uplink Shared Channel, PUSCH. A threshold value is defined for the SinrTargetSamples parameter, TH.sub.4, referred to as the interference threshold. A low ratio of acceptable SINR samples in the neighbouring cell or RBS is due to interference problems (and not due to coverage problems) when SinrTargetSamples(j)<TH.sub.4 in the neighbouring cell or RBS j. This indicator may be exchanged between neighbouring RBSs or transmitted to e.g. node implementing an Operations Support System, OSS, or a node implementing a Network Management System, NMS, as will be explained in more detail below.

[0033] There are difference ways to determine the level of inter-cell coupling between the RBS and the neighbouring RBS. An example is a parameter called CouplingInterCell indicators, which is an adjacency-based indicator showing the percentage of average uplink interference in the neighbouring cell or RBS originated by users in the cell of the RBS for the period under analysis. A threshold value may be defined for this parameter, TH.sub.5, referred to as coupling threshold. In this disclosure, it is considered that neighbouring cell or RBS is not significantly interfered by the RBS for which the congestion control is being performed when CouplingInterCell(i,j)<TH.sub.5.

[0034] Values of CouplingInterCell(i,j) may be obtained from calculations in network planning tools, from network measurements, or by detecting correlation between load and interference patterns. These computations are out of the scope of this disclosure. This indicator may be computed e.g. in the OSS or in the RBS, for which the required network performance measurements have to be exchanged between RBSs. i represents the RBS for which congestion control is performed and j represents neighbouring RBS j.

[0035] Then, the network node increases 140 the value of the average received signal level target, P.sub.0, for wireless devices currently being served by the RBS if the RBS is congested, if the determined interference level in the neighbouring RBS is below the interference threshold or if the level of inter-cell coupling is below the coupling threshold.

[0036] A reason for the determined interference level in the neighbouring RBS being below the interference threshold or if the level of inter-cell coupling being below the coupling threshold in order for the network node to increase the value of the average received signal level target, P.sub.0, for wireless devices currently being served by the RBS, is that such an increase may affect the neighbouring RBS negatively. If the interference level in the neighbouring RBS is above the threshold, it means that UE(s) served by the RBS is already causing relatively severe interference in the neighbouring RBS, wherein an increase of P.sub.0 would increase the interference caused by wireless devices currently being served by the RBS in the neighbouring RBS. If the level of inter-cell coupling is above the threshold, it means that the RBS and the neighbouring RBS have overlapping cells or coverage areas. This may lead to that an increase of P.sub.0 would increase the interference caused by wireless devices currently being served by the RBS in the neighbouring RBS.

[0037] It shall be pointed out that the network node may perform the actions described above for each and every neighbouring RBS or cell of the RBS in question.

[0038] The method performed by the network node may have several advantages. One possible advantage is that congestion problems may be solved in situations where all other congestion relief methods (e.g. HO-based or tilt-based load balancing) fail to work, e.g. indoor cells deployed for the underground, where limited cell overlapping exists and load patterns are highly correlated between adjacent cells. Another possible advantage is that the method may detect isolated cells, which are decoupled (from the interference point of view) from other cells in the network. Thus, increasing P.sub.0 does not have a significant impact on interference in surrounding cells. Still a possible advantage is that the method may be triggered based on statistical cell measurements, which may be collected by RBSs. The changes of P.sub.0 is reliable provided that a sufficiently long Report Output Period is selected for measurements (e.g. 1-2 days). Yet a further possible advantage is that the method is based on comparing key performance measurements against certain thresholds and it increases P.sub.0 by a certain value (linear operation) when congestion is detected, thereby the computational load is low. A possible advantage is that the method does not need external parameters, wherein internal parameters, such as thresholds, may be set based on field trials, thus making the method simple and easy to use. Further, an aim of the method is to detect congested cells that are isolated and increase their P.sub.0 to reduce their traffic load. It is a straight-forward method that is very easy to understand by network operators. Another possible advantage is that the method is applicable to heterogeneous (e.g. macro-indoor), multi-vendor and multi-RAT (Radio Access Technology) scenarios, since all the required information is available in all these cases.

[0039] In an example, both the interference level in the neighbouring RBS caused by wireless devices currently being served by the RBS and the level of inter-cell coupling between the RBS and the neighbouring RBS are determined, wherein the average received signal level target, P.sub.0, is increased, if the determined interference level in the neighbouring RBS is below the interference threshold and if the level of inter-cell coupling is below the coupling threshold.

[0040] In this example, since both the interference level in the neighbouring RBS caused by wireless devices currently being served by the RBS and the level of inter-cell coupling between the RBS and the neighbouring RBS are determined, both conditions must be fulfilled in order for the network node to increase P.sub.0. The two characteristics are correlated. In case there is no inter-cell coupling between the RBS and the neighbouring RBS, it means that users in the RBS may not cause interference in the neighbouring RBS. However, the inter-cell coupling between the RBS and the neighbouring RBS may be high, but the UEs within the cell of the RBS may be distributed geographically in such a manner that they do not cause much interference in the neighbouring cell. However, since the UEs are likely to move about, an increase of P.sub.0 may soon lead to interference in the neighbouring RBS. Further, it shall be pointed out that the RBS may have a plurality of neighbouring RBSs. Assuming that the inter-cell coupling between the RBS and some, or all, of the neighbouring RBSs is high, then an increase of P.sub.0 may cause an increase of interference in at least a part of the neighbouring RBS having a high inter-cell coupling with the RBS being congested.

[0041] The method may further comprise, as illustrated in FIG. 1b, determining 126 a received signal quality in the neighbouring RBS, wherein the average received signal level target, P.sub.0, is increased, if also the received signal quality in the neighbouring RBS is above a signal quality threshold.

[0042] In addition to the previously described actions, or method steps, if the received signal quality in the neighbouring RBS is above the signal quality threshold, then an increase of P.sub.0 may possible, or even likely, not likely cause an increased interference situation in the neighbouring RBS (or the cell of the neighbouring RBS) to such an extent that the received signal quality in the neighbouring RBS becomes unacceptable.

[0043] Consequently, should the received signal quality in the neighbouring RBS be below the signal quality threshold, this may serve as an indication that the received signal quality in the neighbouring cell is already relatively poor. Thus, even if the determined interference level in the neighbouring RBS is below the interference threshold and if the level of inter-cell coupling is below the coupling threshold, an increase in P.sub.0 may still affect the received signal quality in the neighbouring RBS negatively and therefore, the network node does not increase P.sub.0.

[0044] The network node may obtain the information regarding the received signal quality in the neighbouring RBS by the neighbouring performing measurements and then sending measurement reports to the network node.

[0045] The method may still further comprise, as illustrated in FIG. 1c, determining 130 a ratio of power limited samples received by the RBS from wireless devices currently being served by the RBS, wherein the average received signal level target, P.sub.0, is increased, if also the ratio of power limited samples is below a power limiting threshold.

[0046] The ratio of power limited samples may be determined by a parameter, or indicator, referred to as PowerLimitedSamples(i), which may be expressed in %. It is a cell-level indicator showing percentage of uplink data transmissions from power-limited samples (i.e. P.sub.TX=P.sub.TX,max) compared to the total number of uplink data transmission samples for the period under analysis. A threshold value may be defined for this parameter, TH.sub.2, referred to as the power limiting threshold, In this disclosure, an RBS i is said to contain few power-limited samples when PowerLimitedSamples(i)<TH.sub.2.

[0047] In case of a high ratio of power limited samples, an increase of P.sub.0 may not be effective because most of the wireless devices are already transmitting at maximum power. The term “sample” in the expression “power limited samples” refer to uplink data transmissions made by a certain set of wireless devices which corresponding transmission power figures is/are monitored (i.e. “sampled”), and which transmission power figures equates to the maximum transmission power. In other words, the transmission power utilised by a wireless device on an uplink transmission may be monitored/sampled, and the collected—monitored/sampled—transmission power figures (referred herein as “power limited samples”) may be utilised as described in the embodiments herein.

[0048] Determining 110 that the RBS is congested may in an example comprise comparing a Congestion Indicator parameter against a congestion threshold, wherein the RBS is determined to be congested if the Congestion Indicator parameter is equal to or above the congestion threshold.

[0049] There may be several ways to determine that the RBS is congested. Merely for illustrative purposes, an example of congestion may be a level of available buffer space in relation to the total buffer space within the RBS; another example is a load level of one or more processors within the RBS.

[0050] The network node may determine that the RBS is congested by means of a parameter referred to as CongestionIndicator(i), which may be expressed in %, where (i) represents the RBS. Any cell-level indicator measuring traffic congestion in a cell may be used, e.g. Physical Resource Block, PRB, utilisation (average percentage of uplink PRB occupied in a cell for the period under analysis) or Call Blocking Ratio (blocked over accepted connections/calls). A threshold value may be defined for this parameter, TH.sub.1, referred to as a congestion threshold. In this disclosure, an RBS i is said to be congested when CongestionIndicator(i)>TH.sub.1, i.e. when the congestion indicator is above the congestion threshold.

[0051] In an example, determining 130 the ratio of power limited samples comprises determining a number of received transmissions, from wireless devices, having been transmitted at a limited transmission power, determining a total number of received transmission samples from wireless devices, and determining the ratio of power limited samples received by the RBS from wireless devices currently being served by the RBS by dividing the determined number of received transmissions, from wireless devices, having been transmitted at a limited transmission power by the determined total number of received transmission samples from wireless devices.

[0052] When a wireless device transmits data, packets, or signals (referred to as transmissions) to the RBS, the wireless device does so at a certain transmission power. Some transmissions may be done at so-called nominal transmission power and some transmissions may be done at limited transmission power. One wireless device may perform some transmissions at nominal transmission power, some transmissions at limited transmission power, or all its transmission at either nominal or limited transmission power. Since the RBS typically is serving a plurality of wireless device, all performing uplink transmissions, the RBS receives a total amount of uplink transmissions from the different wireless devices, also referred to as UEs, during a certain period of time. Out of all those received uplink transmissions, some are transmitted at nominal transmission power and some are transmitted at limited transmission power.

[0053] By dividing the number of received uplink transmissions having been transmitted at the limited transmission power by the determined total number of received uplink transmission samples, the network node obtains the ratio of power limited samples.

[0054] Determining 120 the interference level in the neighbouring RBS caused by wireless devices currently being served by the RBS may in an example comprise receiving a report from the neighbouring RBS indicating a percentage of average interference in the neighbouring RBS caused by wireless devices currently being served by the RBS, i.e. the RBS for which congestion control is being performed.

[0055] The neighbouring RBS, or neighbouring RBSs, generally perform different measurements in the uplink in order to evaluate the radio conditions in its cell or coverage area. Further, wireless devices being served by the neighbouring RBS may perform different measurements in the downlink that they then report to the neighbouring RBS, e.g. by sending measurement reports.

[0056] Based on these different measurements, either in uplink or downlink or both, the neighbouring RBS determines the interference level in the neighbouring RBS caused by wireless devices currently being served by the RBS. The neighbouring RBS may then send this information, e.g. in a report, to the network node.

[0057] In an example, increasing 140 P.sub.0 is performed by adding a step value to the current P.sub.0.

[0058] This means that there are different predefined values of P.sub.0 that are used by the RBS. For example, a lowest value is defined for P.sub.0 and also an incremental value, i.e. the step value, is defined, e.g. ΔP.sub.0, which is added to a current value of P.sub.0 when P.sub.0 is to be increased. ΔP.sub.0 may be computed in an Operations Support System, OSS, in a centralised solution, whereas, in a distributed solution, may be calculated in each RBS. The centralised and distributed solutions will be described in more detail below.

[0059] According to an embodiment, determining 120 an interference level in a neighbouring RBS caused by wireless devices currently being served by the RBS, is performed for every neighbouring RBS of the RBS for which congestion control is being performed.

[0060] As briefly mentioned above, the RBS, referred to as RBS(i), may have a plurality of neighbouring RBSs, referred to as RBS(j) where 1≦j≦N, where j is an integer and N is the total number of neighbouring RBSs. Thus, the method steps or actions described above with reference to RBS(i) being the RBS in question and RBS(j) being the neighbouring RBS are performed for every neighbouring RBS(j), where 1≦j≦N, where j is an integer and N is the total number of neighbouring RBSs.

[0061] In other words, the network node determines 110 that the RBS(i) is congested. The network node determines 120 an interference level in neighbouring RBS(j) caused by wireless devices currently being served by the RBS(i), or determines 125 a level of inter-cell coupling between the RBS(i) and the neighbouring RBS(j) for all neighbouring RBS where 1≦j≦N, where j is an integer and N is the total number of neighbouring RBSs. Still further, network node increases 140 the value of the average received signal level target, P.sub.0, for wireless devices currently being served by the RBS if the RBS is congested, if the determined interference level in all the neighbouring RBS(j) is below the interference threshold or if the level of inter-cell coupling for all neighbouring RBS(j) is below the coupling threshold. Then the method continues as described above, which will not be repeated here in order to avoid unnecessary repetition.

[0062] In an example, illustrated in FIG. 1e, the network node is a node implementing an Operations Support System, OSS, or a node implementing a Network Management System, NMS.

[0063] The network node in this example can be said to comprise a centralised implementation of the network node. FIG. 1e illustrates an OSS 1000, which alternatively could be an NMS. The OSS 1000 may communicate with the RBSs 1011, 1012, . . . , 101n via a transport network 1100. The RBSs serve respective plurality of wireless devices 1111, 1112, . . . , 111n.

[0064] The network node may then perform congestion control for each and every RBS it communicates with via the transport network. Thus, the network node may obtain information from each and every RBS, the information pertaining to the different characteristics as described above, e.g. interference level in a neighbouring RBS(j) caused by wireless devices currently being served by the RBS(i), just to mention one.

[0065] In another example, the network node is the RBS for which congestion control is being performed.

[0066] In this example, the RBS(i) itself performs the method comprising the actions described above. RBS(i) may communicate with its neighbouring RBS(j), 1≦j≦N, where j is an integer and N is the total number of neighbouring RBSs, for example by means of an X2 interface in case the wireless communication network in which the RBSs are operating employs Long Term Evolution, LTE. Alternatively, the RBSs may communicate with each other by means of e.g. a Radio Network Controller, RNC, or a Base Station Controller, BSC.

[0067] In still a further example, the network node is a Radio Network Controller, RNC, or a Base Station Controller, BSC, controlling at least the RBS for which congestion control is being performed.

[0068] Depending on the type of wireless communication network, LTE, Universal Mobile Telecommunications System, UMTS, or GSM, Global System for Mobile Communications, the network architecture is somewhat different. In UMTS the RNC may control a plurality of RBSs, of which some may be neighbouring RBSs to other RBSs that the RNC is controlling. Thus the RNC may obtain the above described information and characteristics of the RBSs it is controlling and thereby increase (or decrease) P.sub.0 as it sees fit according to the method described above. The RNC may then inform the RBSs in question which P.sub.0 it is supposed to employ.

[0069] For GSM, the BSC may control a plurality of RBSs in the same or similar manner as for the RNC in UMTS. If the network node is the BSC, then the BSC may obtain the above described information and characteristics of the RBSs it is controlling and thereby increase (or decrease) P.sub.0 as it sees fit according to the method described above. The BSC may then inform the RBSs in question which P.sub.0 it is supposed to employ.

[0070] The method described above may achieve congestion relief in the Physical Uplink Shared Channel, PUSCH, of a congested RBS or cell by changing Uplink Power Control, ULPC, settings instead of diverting wireless devices to other cells. This may be critical when congestion occurs in an RBS or cell whose wireless devices cannot be served by any neighbour, either because the latter is also congested or there is no overlapping between them. When any of the previous situations is detected (i.e. congestion in many surrounding cells or congestion in an isolated cell), the method decreases RBS/cell load by increasing pzeroNominalPusch parameter (P.sub.0) in the congested cell(s). The aim of increasing P.sub.0 is to improve uplink signal quality in terms of SINR for users close to the RBS (i.e. non-power-limited users). The uplink SINR value determines the Modulation and Coding Scheme, MCS, selected for each transmission by Adaptive Modulation and Coding, AMC, mechanism in the RBS. The selected MCS is then sent to the wireless device in the Physical Downlink Control Channel, PDCCH. This MCS field determines the modulation scheme and code rate used by wireless device in PUSCH transmissions, so that the higher its value, the more effective the modulation and code used by the wireless device. Thus, any uplink SINR improvement is translated directly into higher MCSs used by the wireless device (unless restricted by higher layers). The use of more effective modulation schemes by the wireless device leads to a reduction in the number of used PRBs by the wireless device, and hence a congestion relief effect in the uplink.

[0071] To ensure adequate performance, the method may check, before modifying P.sub.0 in an RBS or cell, if: a) the cell is isolated from surrounding or neighbouring RBSs or cells, so that the increase in P.sub.0 does not cause interference problems in neighbouring RBSs or cells and, optionally, if b) the ratio of power-limited samples in the cell is small, so that changes in P.sub.0 have a non-negligible impact on congestion performance indicators in the RBS or cell.

[0072] As describe above, there are two possible implementations for the proposed method: a centralised solution, located in the OSS/NMS, or a distributed solution, located in the RBS or RNC/BSC. An exemplifying centralised system architecture is illustrated in FIG. 1e. The base station collects network performance measurements for a certain reporting period and current network configuration data. Both configuration and performance data is sent to the OSS by means of a transport network. Such data is delivered to a processor, responsible for computing new P.sub.0 settings on a cell basis. The resulting values of P.sub.0 in each cell, [P.sub.0.sup.(1), . . . , P.sub.0.sup.(n)], are sent back to the OSS and later downloaded to the base stations. The new P.sub.0 parameter value is sent to the user equipment (UE) by a signalling channel. As a result of the process, the user modifies UL transmit power, which has a direct impact on experienced connection quality and, ultimately, on uplink performance in a network level.

[0073] Alternatively, the distributed solution resides in the base station and is shown in FIG. 1f. For this purpose, RBS must exchange network performance data with its neighbour RBSs. Thus, each RBS may calculate its own network data, as would be done in the OSS in the centralised solution. In the subsequent description, unless stated otherwise, it is assumed that both implementations are identical.

[0074] FIG. 2a illustrates an example of the method as a ‘black-box’, showing its inputs and output. As shown in the figure, the method has six cell performance indicators, whereof some or all may be considered when determining whether or not to increase P.sub.0, pzeroNominalPusch. These indicators may be either directly provided as described above or other by network equipment or obtained after some calculations. In addition, five thresholds and a P.sub.0 modification step, Δpzero, may also be set as described above. These thresholds and modification step are not considered as input data, but configuration parameters. System output is the change in pzeroNominalPusch (if required). Indicators and parameters are defined as follows, where (i) is the RBS for which congestion control is performed and (j) are individual neighbouring RBSs:

[0075] CongestionIndicator(i) [%] and, PowerLimitedSamples(i) [%] as described above. Interf(j) [dBm/PRB]: cell-level indicator showing 95%-tile of uplink interference per PRB in neighbour j for the period under analysis. A threshold value is defined for this parameter, TH.sub.3. In this disclosure, a neighbour cell j is labelled as experiencing high interference when Interf(j)>TH.sub.3. This indicator may be exchanged between neighbours in the distributed solution. SinrTargetSamples(j) [%] and CouplingInterCell(i,j) [%] as described above. δpzero: step in P.sub.0 (when required). Δpzero.sup.(n) is δpzero if certain conditions are fulfilled, 0 otherwise. This variable may be computed in the OSS in the centralised solution, whereas, in the distributed solution, may be calculated in each RBS. pzeroNominalPusch.sup.(n)(i), pzeroNominalPusch.sup.(n+1)(i) [dBm]: the value of P.sub.0 before and after iteration n. The method in this example is defined as an incremental controller, where Δpzero.sup.(n) is the parameter change in iteration n, i.e. pzeroNominalPusch.sup.(n+1)(i)=pzeroNominalPusch.sup.(n)(i)+Δpzero.sup.(n). The new value of the parameter may be calculated in each RBS in the distributed solution.

[0076] The method comprises in this example an iterative process executed on a cell/RBS basis (i.e. the process is repeated for every cell/RBS in the centralised solution and in each RBS in the distributed solution). FIG. 2b illustrates an embodiment of the method by means of a flowchart. The analysis of a cell i comprises three stages. Stage 1 and 2 check if pzeroNominalPusch in cell/RBS i should be modified or not, by analysing the performance of cell i and its neighbours j, respectively. Stage 3 (if applicable) modifies pzeroNominalPusch in cell i. Along the different stages, the method may discard any modification of pzeroNominalPusch in cell i, so that the analysis of next cell/RBS i+1 starts. Different thresholds are used in different stages, as pointed out in the figure.

[0077] A detailed description of the different stages is given in FIG. 2c. Stage 1 checks first if the cell/RBS under study is congested (CongestionIndicator(i)>TH.sub.1), and, then, optionally, if cell/RBS i does not contain too many power-limited samples (PowerLimitedSamples(i)<TH.sub.2). If any of the two conditions is not fulfilled, modifications in pzeroNominalPusch, P.sub.0, are discarded and the analysis of a new cell/RBS starts.

[0078] Stage 2 aims to check if any neighbour cell/RBS experiences uplink interference problems first, and then if those interference problems come from the cell/RBS under study (cell i). For this purpose, stage 2 comprises an additional iterative process where all neighbour cells/RBSs of cell i are analysed. For every iteration, two different checks are implemented for every neighbour cell jε{1, 2, . . . , N.sub.c(i))} (N.sub.c(i) is the number of neighbours of cell i). A first check tries to find out if cell/RBS j experiences interference problems. A neighbour cell/RBS is considered to have interference problems when a) Interf(j)>TH.sub.3, and b) SinrTargetSamples(j)<TH.sub.4. A second check aims to find out if interference problems in cell/RBS j are not originated by uplink transmissions in cell i (CouplingInterCell(i,j)<TH.sub.5). In case cell/RBS j experiences uplink interference problems, and those problems are coming from uplink transmissions in cell i, any change in pzeroNominalPusch is discarded, and the analysis of a new cell starts.

[0079] Stage 3 implements pzeroNominalPusch increases for those cells/RBSs eligible to be modified. Increments may made by adding a step value as δpzero, pzeroNominalPusch.sup.(n+1)(i)=pzeroNominalPusch.sup.(n)(i)+δpzero.

[0080] Embodiments herein also relate to a network node for congestion control of an RBS. The network node has the same technical features, objects and advantages as the method performed by the network node. The network node will thus only be described in brief in order to avoid unnecessary repetition.

[0081] The network node will be described with reference to FIGS. 3 and 4. FIG. 3 and for illustrates the network node 300, 400 configured to determine that the RBS is congested; to determine an interference level in a neighbouring RBS caused by wireless devices currently being served by the RBS, or to determine a level of inter-cell coupling between the RBS and the neighbouring RBS. The network node 300, 400 is further configured to increase a value of an average received signal level target, P.sub.0, for wireless devices currently being served by the RBS if the RBS is congested, if the determined interference level in the neighbouring RBS is below an interference threshold or if the level of inter-cell coupling is below a coupling threshold.

[0082] The network node 300, 400 may be implemented or realised in different ways.

[0083] FIG. 3 illustrates one exemplifying implementation or realisation of the network node 300. FIG. 3 illustrates the network node 300 comprising a processor 321 and memory 322, the memory comprising instructions, e.g. by means of a computer program 323, which when executed by the processor 321 causes the network node 300 to determine an interference level in a neighbouring RBS caused by wireless devices currently being served by the RBS, or to determine a level of inter-cell coupling between the RBS and the neighbouring RBS. The memory further comprises instructions, which when executed by the processor 321 causes the network node to increase a value of an average received signal level target, P.sub.0, for wireless devices currently being served by the RBS if the RBS is congested, if the determined interference level in the neighbouring RBS is below an interference threshold or if the level of inter-cell coupling is below a coupling threshold.

[0084] FIG. 3 also illustrates the network node 300 comprising further functionality 340. The further functionality 340 may comprise hardware of software necessary for the network node 300 to perform different tasks that are not disclosed herein.

[0085] An alternative exemplifying implementation of the network node is illustrated in FIG. 4. FIG. 4 illustrates the network node 400 comprising a determining unit 403 for determining an interference level in a neighbouring RBS caused by wireless devices currently being served by the RBS, or for determining a level of inter-cell coupling between the RBS and the neighbouring RBS. The network node 400 further comprises an increasing unit 404 for increasing a value of an average received signal level target, P.sub.0, for wireless devices currently being served by the RBS if the RBS is congested, if the determined interference level in the neighbouring RBS is below an interference threshold or if the level of inter-cell coupling is below a coupling threshold.

[0086] FIG. 4 also illustrates the network node 400 comprising further functionality 409. The further functionality 409 may comprise hardware of software necessary for the network node 400 to perform different tasks that are not disclosed herein.

[0087] The network node has the same possible advantages as the method performed by the network node. One possible advantage is that congestion problems may be solved in situations where all other congestion relief methods (e.g. HO-based or tilt-based load balancing) fail to work, e.g. indoor cells deployed for the underground, where limited cell overlapping exists and load patterns are highly correlated between adjacent cells. Another possible advantage is that the method may detect isolated cells, which are decoupled (from the interference point of view) from other cells in the network. Thus, increasing P.sub.0 does not have a significant impact on interference in surrounding cells. Still a possible advantage is that the method may be triggered based on statistical cell measurements, which may be collected by RBSs. The changes of P.sub.0 is reliable provided that a sufficiently long Report Output Period is selected for measurements (e.g. 1-2 days). Yet a further possible advantage is that the method is based on comparing key performance measurements against certain thresholds and it increases P.sub.0 by a certain value (linear operation) when congestion is detected, thereby the computational load is low. A possible advantage is that the method does not need external parameters, wherein internal parameters, such as thresholds, may be set based on field trials, thus making the method simple and easy to use. Further, an aim of the method is to detect congested cells that are isolated and increase their P.sub.0 to reduce their traffic load. It is a straight-forward method that is very easy to understand by network operators. Another possible advantage is that the method is applicable to heterogeneous (e.g. macro-indoor), multi-vendor and multi-RAT (Radio Access Technology) scenarios, since all the required information is available in all these cases.

[0088] According to an embodiment, the network node 300, 400 further is configured to determine both the interference level in a neighbouring RBS caused by wireless devices currently being served by the RBS and the level of inter-cell coupling between the RBS and the neighbouring RBS, wherein the network node is configured to increase the average received signal level target, P.sub.0, if the determined interference level in the neighbouring RBS is below the interference threshold and if the level of inter-cell coupling is below the coupling threshold.

[0089] According to yet an embodiment, the network node 300, 400 further is configured to determine a received signal quality in the neighbouring RBS, wherein the average received signal level target, P.sub.0, is increased, if also the received signal quality in the neighbouring RBS is above a signal quality threshold.

[0090] According to still an embodiment, the network node 300, 400 further is configured to determine a ratio of power limited samples received by the RBS from wireless devices currently being served by the RBS, wherein the average received signal level target, P.sub.0, is increased, if also the ratio of power limited samples is below a power limiting threshold.

[0091] According to another embodiment, wherein determining that the RBS is congested comprises the network node 300, 400 being configured to compare a Congestion Indicator parameter against a congestion threshold, wherein the RBS is determined to be congested if the Congestion Indicator parameter is equal to or above the congestion threshold.

[0092] According to yet an embodiment, wherein determining the ratio of power limited samples comprises the network node 300, 400 being configured to determine a number of received transmissions, from wireless devices, having been transmitted at a limited transmission power, to determine a total number of received transmission samples from wireless devices, and to determine the ratio of power limited samples received by the RBS from wireless devices currently being served by the RBS by dividing the determined number of received transmissions, from wireless devices, having been transmitted at a limited transmission power by the determined total number of received transmission samples from wireless devices.

[0093] According to still an embodiment, wherein determining the interference level in a neighbouring RBS caused by wireless devices currently being served by the RBS comprises the network node 300, 400 being configured to receive a report from the neighbouring RBS indicating a percentage of average interference in the neighbouring RBS caused by wireless devices currently being served by the RBS, i.e. the RBS for which congestion control is being performed.

[0094] According to a further embodiment, the network node 300, 400 is configured to increase P.sub.0 by adding a step value to the current P.sub.0.

[0095] According to yet an embodiment, the network node 300, 400 is configured to determine an interference level in a neighbouring RBS caused by wireless devices currently being served by the RBS, for every neighbouring RBS of the RBS for which congestion control is being performed.

[0096] According to still an embodiment, the network node 300, 400 is a node implementing an OSS, or a node implementing an NMS.

[0097] According to another embodiment, the network node 300, 400 is the RBS for which congestion control is being performed.

[0098] According to yet another embodiment, the network node 300, 400 is a Radio Network Controller, RNC, or a Base Station Controller, BSC, controlling at least the RBS for which congestion control is being performed.

[0099] In FIG. 4, the network node 400 is also illustrated comprising a communication unit 401. Through this unit, the network node 400 is adapted to communicate with other nodes and/or entities in the wireless communication network. The communication unit 401 may comprise more than one receiving arrangement. For example, the communication unit 401 may be connected to both a wire and an antenna, by means of which the network node 400 is enabled to communicate with other nodes and/or entities in the wireless communication network. Similarly, the communication unit 401 may comprise more than one transmitting arrangement, which in turn may be connected to both a wire and an antenna, by means of which the network node 400 is enabled to communicate with other nodes and/or entities in the wireless communication network. The network node 400 further comprises a memory 402 for storing data. Further, the network node 400 may comprise a control or processing unit (not shown) which in turn is connected to the different units 403-404. It shall be pointed out that this is merely an illustrative example and the network node 400 may comprise more, less or other units or modules which execute the functions of the network node 400 in the same manner as the units illustrated in FIG. 4.

[0100] It should be noted that FIG. 4 merely illustrates various functional units in the network node 400 in a logical sense. The functions in practice may be implemented using any suitable software and hardware means/circuits etc. Thus, the embodiments are generally not limited to the shown structures of the network node 400 and the functional units. Hence, the previously described exemplary embodiments may be realised in many ways. For example, one embodiment includes a computer-readable medium having instructions stored thereon that are executable by the control or processing unit for executing the method steps in the network node 400. The instructions executable by the computing system and stored on the computer-readable medium perform the method steps of the network node 400 as set forth in the claims.

[0101] FIG. 5 schematically shows an embodiment of an arrangement 500 in a network node. Comprised in the arrangement 500 in the network node are here a processing unit 506, e.g. with a Digital Signal Processor, DSP. The processing unit 506 may be a single unit or a plurality of units to perform different actions of procedures described herein. The network node may also comprise an input unit 502 for receiving signals from other entities, and an output unit 504 for providing signal(s) to other entities. The input unit and the output unit may be arranged as an integrated entity or as illustrated in the example of FIG. 4, as one or more interfaces 401.

[0102] Furthermore, the arrangement in the network node comprises at least one computer program product 508 in the form of a non-volatile memory, e.g. an Electrically Erasable Programmable Read-Only Memory, EEPROM, a flash memory and a hard drive. The computer program product 508 comprises a computer program 510, which comprises code means, which when executed in the processing unit 506 in the arrangement in the network node causes the network node to perform the actions e.g. of the procedure described earlier in conjunction with FIGS. 1a-1c.

[0103] The computer program 510 may be configured as a computer program code structured in computer program modules 510a-510e. Hence, in an exemplifying embodiment, the code means in the computer program of the network node comprises a determining unit, or module, for determining; for determining that the RBS is congested; and determining an interference level in a neighbouring RBS caused by wireless devices currently being served by the RBS, or determining a level of inter-cell coupling between the RBS and the neighbouring RBS. The computer program further comprises an increasing unit, or module, for increasing a value of an average received signal level target, P.sub.0, for wireless devices currently being served by the RBS if the RBS is congested, if the determined interference level in the neighbouring RBS is below an interference threshold or if the level of inter-cell coupling is below a coupling threshold

[0104] The computer program modules could essentially perform the actions of the flow illustrated in FIGS. 1a-1c, to emulate the network node 400. In other words, when the different computer program modules are executed in the processing unit 506, they may correspond to the units 403-404 of FIG. 4.

[0105] Although the code means in the embodiments disclosed above in conjunction with FIG. 4 are implemented as computer program modules which when executed in the processing unit causes the network node to perform the actions described above in the conjunction with figures mentioned above, at least one of the code means may in alternative embodiments be implemented at least partly as hardware circuits.

[0106] The processor may be a single Central Processing Unit, CPU, but could also comprise two or more processing units. For example, the processor may include general purpose microprocessors; instruction set processors and/or related chips sets and/or special purpose microprocessors such as Application Specific Integrated Circuits, ASICs. The processor may also comprise board memory for caching purposes. The computer program may be carried by a computer program product connected to the processor. The computer program product may comprise a computer readable medium on which the computer program is stored. For example, the computer program product may be a flash memory, a Random-Access Memory RAM, Read-Only Memory, ROM, or an EEPROM, and the computer program modules described above could in alternative embodiments be distributed on different computer program products in the form of memories within the network node.

[0107] It is to be understood that the choice of interacting units, as well as the naming of the units within this disclosure are only for exemplifying purpose, and nodes suitable to execute any of the methods described above may be configured in a plurality of alternative ways in order to be able to execute the suggested procedure actions.

[0108] It should also be noted that the units described in this disclosure are to be regarded as logical entities and not with necessity as separate physical entities.

[0109] While the embodiments have been described in terms of several embodiments, it is contemplated that alternatives, modifications, permutations and equivalents thereof will become apparent upon reading of the specifications and study of the drawings. It is therefore intended that the following appended claims include such alternatives, modifications, permutations and equivalents as fall within the scope of the embodiments and defined by the pending claims.