Method and system for optimising the performance of a network
FIELD OF THE INVENTION
The invention relates to a method and system for optimising the performance of a network.
BACKGROUND OF THE INVENTION
Telecommunications Management Network (TMN) model provides a widely accepted view about how the business of a service provider is to be managed. The TMN model consists of four layers, usually arranged in a triangle or pyramid, with business management at the top, service man- agement the second layer, network management the third layer, and element management at the bottom. Management decisions at each layer are different but related to each other. Working from the top down, each layer imposes requirements on the layer below. Working from the bottom up, each layer provides important source of data to the layer above. The TeleManagement Forum's (TMF) TMN sets the guidelines for the optimisation functionalities and processes. The 3rd Generation Partnership Project (3GPP) has adopted the same model. The scope of TMF is to find standardised way to define service quality, set requirements for networks in terms of quality of service (QoS) measurements, and make it possible to have QoS reports between providers and systems that implement the service.
According to the TMN model the information from the upper level systems flows down, guaranteeing seamless operation and optimisation possibili- ties for the network. The TMN model is depicted in Fig. 3. The information flow from the business management layers all the way down to the service management and network management layers is essential since the business aspects have to be considered carefully in the optimisation and network development process. The TMN model demonstrates the change of
the abstraction level in the operator's daily work. The business plan efficiency can be measured with capital and operational expenditure (CAPEX, OPEX) and revenue. The wanted business scenario is then translated to offered sen/ices, service priorities and service QoS requirements. On the lowest (network element) level of the TMN model the business related issues are converted into configuration parameter settings.
Functions supported by TMN's Business Management Systems are, for example, to create an investment plan, to define the main QoS criteria for the proposed network and its services, to create a technical development path (expansion plan) to ensure that the anticipated growth in subscriber numbers is provided for.
Functions supported by Sen/ice Management Systems are for example to take care of subscriber data, the provision of services and subscribers, to collect and rate bill offered services, to create, promote and monitor services.
Functions supported by Network Management Systems (NMS) are to plan the network, to collect information from the underlying networks and pre/post-process the raw data, to analyse and distribute information, to optimise network capacity and quality.
Element management systems can be considered as part of Network Element functionality with the responsibility to monitor the functioning of the equipment, to collect raw data (performance indicators), provide local graphical user interface (GUI) for site engineers, and to mediate towards the NMS system.
In addition to TMN, the TMF also defines a Telecom Operations Map (TOM). Telecom and data sen/ice providers must apply a customer ori-
ented service management approach using business process management methodologies to cost effectively manage their businesses and deliver the service and quality customers require. TOM identifies a number of operations management processes covering Customer Care, Sen/ice Management and Network Management. The Telecom Operations Map uses the layers of the TMN model as core business processes, but divides the service management layer into 2 parts: Customer Care and Service Development and Operations. Customer Interface Management is separately delineated, because Customer Interface Management may be man- aged within the individual Customer Care sub-process or, in combination across one or more of the Customer Care sub-processes.
Fig. 4 shows the high-level structure of Network Management processes and the supporting Function Set Groups. According to the framework pro- vided by TOM it is possible to map each of the high level processes to a series of component functions (arranged in function set groups). Provided that:
• Network performance management (PM) provides adequate measurements; • Network configuration management supports the whole TMF frame work;
• There is intelligence in network management system (NMS) to combine these two information.
It then identifies relationships and information flows between them. In Fig. 4 the TOM and its components are presented. The functionalities of the layers are the same as in Fig. 3 to indicate the corresponding management layers.
A detailed description of the TMN model and the TOM can be found on the homepage of the TMF (see http://www.tmforum.org).
In current cellular systems the radio resources are handled with numerous parameters, wherein the parameter value settings are fixed even in changing conditions. The task of an operator is to manually tune the parameter settings to meet the right operating point in terms of quality of service. Often the objective when doing optimising has been "just to get it working". This tuning has been relatively straightforward in simple GSM networks with pure speech services. In the case of WCDMA the complexity of these parameter settings is manifold: multiple services, service classes, even multi-radio environment. The WCDMA based cellular systems will offer variability of packet and circuit switched services and therefore are more complicated to plan and control than today's networks. The strong coupling of the cells adds the complexity. For an operator it is essential to utilise all possible resources to improve the capacity and Quality of Ser- vice (QoS) of the radio network.
A network optimising process serves to improve the overall network quality as experienced by the mobile subscriber and to ensure an efficient use of the network resources. The optimising process includes the analysis of the network and improvements in the network configuration and performance. Statistics of key performance indicators (KPI) for the operational network are fed to a tool for analysing the network status and the radio resource management (RRM) parameters can be manually tuned for the better performance. The key performance indicators (KPI) are defined in an initial phase of the optimisation process. They consist for example of measurements in the network management system (NMS) and of field measurement data or any other information, which can be used to determine the quality of service (QoS) of the network. For a second generation systems quality of service QoS has consisted for example of dropped call statistics, dropped call cause analysis, handover statistics and measurements of successful call attempts, while for third generation systems with a greater
variety of sen ices new definitions of quality of service QoS for quality analysis must be generated.
To optimise the overall revenue of a network operator or a service provider reducing the costs of the operation and maintenance of a network system has prompted the need for process automation in said network system.
SUMMARY OF THE INVENTION
It is therefore an object of the invention to improve the process of optimising network resources.
This object is solved by a method for optimising the performance of a network according to claim 1, a corresponding system according to claim 12.
The invention is based on the idea to optimise network resources by means of one centralised cost function rather than optimising the network resources separately.
Currently the radio resource management algorithms are parameterised separately: handover control, admission control, power control etc. parameter values are set independently and one can identify cases where for example hand over problems are due to wrong power control (CPICH) setting. Change in the admission control setting can result in a change in the quality of the packet data.
Therefore, when optimising the performance of the network, first of all, the relevant key performance indicators for a specific entity within the network as well as first parameters, which influence the key performance indica- tors, are determined. A number of entities similar to said specific entity is selected, wherein relevant key performance indicators are associated to
every entity. The key performance indicators as well as the selected number of entities are used as elements in a first cost function, i.e. said first cost function is calculated on the basis of the KPI and the number of entities. Said first cost function is calculated in order to evaluate the network performance. Accordingly, since said first parameters directly relate to the key performance indicators, the network performance will be depend on first values of said first parameters.
Thereafter the values of said first parameters are adjusted, so that a sec- ond set of values of said first parameters are obtained. The key performance indicators are determined again but this time on the basis of the second values of said first parameters and said first cost function is recalculated on the basis of these key performance indicators. The result of said first cost function calculated on the basis of said first values of said first parameters is compared to the result of said first cost function recalculated on the basis of said second values of said first parameters. This comparison is carried out to determine whether the network performance has improved. When the network performance has improved due to the adjusting of said first parameters, said second values of said first parame- ters are adopted as permanent parameters.
Setting separate parameters based on many algorithms rather than optimising a parameter set with a central control function can cause oscillations in the parameter values, since cases may occur where changing one parameter to optimise a KPI may adversely affect other KPI's. Therefore, it is advantageous to monitor the radio resource management as a whole by a centralised cost function rather than individual functions, in order to coordinate the changing of the respective parameters.
According to a development of the invention, the respective key performance indicators are weighted with different weight coefficients within said
first cost function. Using different weight coefficients allows to allocate more influence of one or more key performance indicators on the first cost function.
According to a further development of the invention, reference values for the key performance indicators are set and the key performance indicators in the first cost function are replaced by the difference between the current key performance indicators and the respective reference values (to define the "cost" see equation (1 )). Hence, the first cost function is now calcu- lated on the basis of the difference between the current key performance indicators and the respective reference of values. This allows to set quality of service targets based on the cost of the KPI(s) on the system.
According to a preferred development of the invention, said first cost func- tion is composed of a second and a third cost function, wherein said second cost function represents the quality requirements within the network and said third cost function represents the capacity requirements within the network. Said second cost function is weighted with a second weight coefficient while said third cost function is weighted with a third weight co- efficient. Providing the second and third cost function in connection with their respective weight coefficients makes it possible to incorporate the trade-off between capacity and quality within the first cost function.
According to a further preferred development of the invention, the second and third cost function are composed of the selected entities, wherein the determined key performance indicators are associated to each entity. This allows to incorporate a broad distribution of key performance indicators from across the network.
According to a further development of the invention, said entity can be represented by the cell or the user group within the network. Accordingly, the
cost function can be calculated for example on the basis of a cell or a cluster of cells.
According to a further preferred development of the invention, the steps for optimising the network performance are iterated, so that the optimising process can be automated.
According to still a further preferred development of the invention, the values of the KPI's together with the respective first parameters and the cor- responding result of the first cost function are stored to create a history database. The current result of said first cost function is compared with previous results thereof stored in the history database in order to determine whether the network performance has improved within a predetermined time interval. However, if no improvements of the network perform- ance have been made within said predetermined time interval a respective notification is being issued. Issuing the notification when no improvements are detected for a predetermined time interval, can avoid the occurrence of deadlock during the automated process and point out to possible problems.
BRIEF DESCRIPTION OF THE DRAWINGS
In the following, the present invention will be described in greater detail on the basis of preferred embodiments with reference to the accompanying drawings, in which:
Fig. 1 shows a flow chart of an automated process for optimising the network performance
Fig. 2 shows an example of a KPI cost function;
Fig. 3 shows a diagram of the telecommunications management network (TMN) model;
Fig. 4 shows a diagram of the Telecom operation map (TOM), and
Fig. 5 shows an illustration of the combination of monitoring and optimising functions to combine different management layers.
DESCRIPTION OF THE PREFERRED EMBODIMENT
In Fig 1 a flow chart of an automated process for optimising the network performance according to the first embodiment is shown. First of all, in the step S1, those key performance indicators, which describe the performance of the part of interest of the network, are selected. Then, in step S2 those configuration parameters, upon which the KPI's depend on, are determined. In step S3 the number of cells, which are to be included into the optimising process, are selected, i.e. selecting a cluster of cells. The current values of the KPI's are determined based on the respective configuration parameters in step S4. Thereafter, in step S5 the cost function is cal- culated on the basis of the current values of the KPI's and the number of cells. The result of the cost function, the values of the KPI's and the configuration parameters are stored in a history database in step S6.
At least one value of the respective configuration parameters is adjusted in step S7, resulting in a new set of configuration parameters. Based on this new set of configuration parameters new KPI values are determined in step S4 and the cost function is re-calculated in step S5 on the basis of the new KPI values and the (unchanged) number of cells as selected in step S3. The new result of the cost function, the new KPI and configura- tion parameter values are also stored in the history database in step S6. Subsequently, the new result of the cost function - based on the
new/adjusted set of configuration parameters - is compared to previous results of the cost function stored in the history database in step S8 in order to determine whether the network performance of interest has improved after adjusting the configuration parameters.
If the network performance has improved after adjusting the configuration parameters, the adjusted set of configuration parameters are adopted as permanent parameters in step S9. While, if it has been determined in step S8 that the network performance has not improved after adjusting the con- figuration parameters, the first set of configuration parameters, as stored in the history database in step S6, are adopted as permanent parameters in step S9.
In step S10 is checked whether the network performance has improved within a predetermined time interval. When the network performance has not improved during the predetermined time interval, i.e. the KPI history has not improved even though auto-tuning is performed, the network operator is notified in step S12 that a problem has occurred with the automated process for optimising the network performance. Since it is clear that many of the parameter values will not be auto-tuned, and that auto- tuning cannot always optimise the network, the operator can then check whether this problem is due to hardware problems or whether - under the current network conditions - it is not possible to automatically optimise the network performance. In such a case of the network operator will have to resume to manually optimise the network performance.
On the other side when the network performance has improved during the predetermined time interval the flow jumps to step S7 where the configuration parameters are adjusted again in order to further optimise the network performance. The flow will then continue as described above.
In a second embodiment not only the relevant KPI's are selected in step S1 but also a set of QoS targets is determined, which is expressed in a set of reference KPI. The automated process for optimising the network performance according to the second embodiment corresponds substantially to the optimising process according to the first embodiment. The only difference is that the difference between the KPI and the reference KPI is used instead of the KPI value when the calculating the cost function in step S5.
Accordingly, the operator sets capacity requirements for certain capacity KPIs denoted KPI_C with "ref" in the sub-index. Correspondingly, the operator sets quality requirements for certain KPI_Qs. The quality and capacity costs can then be calculated as in equation (1).
Quality Cost =
t * f(KPI _ Q -KPI_ Q
ref ) cellseCLUSTER i Capacity Cost =
cellseCLUSTER i
Different cost functions can be combined or summed with weight coefficients α and β. By controlling or changing weight coefficients α and β a certain type of cost can be emphasised and the overall some.
The mathematical formulation of the task of optimising the network performance can be seen as to find a combination of air interface configuration parameters based on which the KPIs are as close to the desired area as possible.
Fig. 2 shows an example of a KPI cost function f. In this example, the cost for KPI values higher than KPI_ref is increasing linearly. However, the cost functions can also take other shapes.
The total cost function to be optimised, i.e. minimized, is presented in equation (3). A trade-off between capacity and quality requirements can be accomplished using the parameter W. The minimization is performed by adjusting the configuration parameters (2). The KPI values also depend on the service distribution, e.g. different costs and parameter settings will be achieved depending on the service distribution.
KPI _C/ = /(Configuration parameters, Service Distribution) KPI Qj = /(Configuration parameters, Service Distribution) ( v2) '
Total COST = W * QualityCost + (l - W) * CapacityCost (3)
Factors that may affect the optimisation process are for example the traffic profile (service mix), traffic density, pricing of each service etc. The ulti- mate goals when minimizing the total cost include to optimise the operators revenue, to minimise CAPEX and OPEX, as well as to maintain good reputation of the operator.
A specific example of the cost function TOTAL COST can be calculated according to equations (4) to (8) as follows:
(4) TOTAL COST = C(Queuing Ratio) + C( BAD Quality Ratio) + C(Dropping Ratio) + C(Blocking Ratio)
with
(5) C(Queuing Ratio) = 0.05 * Dev (Queuing Ratio - allowed Queuing Ratio)
(6) C(Bad Quality Ratio) = 0.2 * Dev (Bad Quality Ratio - allowed Bad Quality Ratio) (6)
(7) C(Dropping Ratio) = 1 * Dev (Dropping Ratio - allowed Dropping Ratio)
(8) C(Blocking Ratio) = 0.10 * Dev (Blocking Ratio - allowed Blocking Ratio)
The optimisation challenge is to combine seamlessly all the different TOM management layers, wherein the fact, that the measurements (quality and cost indicators) from different layers use different language, should be taken into account.
When the optimising process is implemented in the NMS of a network, the operators' decision on the customer care and service management layers are supported. To be able to do this a derivation of cost functions including configuration and (PM) measurements performed on the lower layer are translated to "language" on the layer above. This can be carried out by:
Performing a technical translation (mapping) from Radio Access Network parameter (settings) to service related quality expectations/targets. In practise this means correlating the configuration management and per- formance management. I.e. certain configured functional entity is monitored by certain set of measurements. The performance of the entity is derived with a cost function utilising the defined measurements.
In practise the following means translation of measurements of larger en- tity (i.e. cell, traffic class, etc.) to user level entity be able to statistically conclude the quality of individual users. Also this step is performed with a with weighted cost function(s). Furthermore, it is possible to combine these individual translations with cost function to achieve wanted end user quality indication.
1) A technical translation (mapping) from Radio Access Network measurements (network performance) to end user flow level grade of service (experienced quality).
2) A technical translation from aggregate level (UMTS traffic classes) parameters settings to end user flow level grade of service (experienced quality),
3) A technical mapping from measurements per traffic class to settings to end user flow level grade of sen/ice (experienced quality),
and/or a combination function of traffic class and flow level information (parameters and settings) with a cost function to support the parameteris- ing and monitoring of end user GOS.
Fig. 5 shows an illustration of the combination of network monitoring and optimising functions which are used to combine different management layers within the network by mapping.
The mapping is carried out from one layer to the next one by combining the network measurements, the performance indicators PI and/or the KPI with a cost function
And cost function for the grade of service GOS as experienced by the subscriber can be calculated as described in equation (9):
(9) GOS = C(Service Availability) + C(Delay and Jittering) + C(Quality) + C(Dropping) + C(Service Accessibility) + C(Equivalent Bitrate or User throughput)
Wherein the delay is composed of Service Access Delay and Queuing Transmission Delay. Non real-time quality is influenced by packet loss, Radio Link Control RLC, Packet Data Convergence Protocol PDCP, i.e. by the bit error rate BER and the block error rate BLER. Regarding the realtime quality the quality is bad if uplink UL block error rate BLER is significantly higher than the target BLER. The real-time quality is influenced by the downlink DL connection power outage. The input of the above cost function comprises capacity requests and traffic distribution. The measurements of the total throughput is carried out in kbps/cell/MHz.
The spectral efficiency of the cost function equals to the throughput in kbps/cell/MHz when 98 % of the users are satisfied. This means that the service accessibility and the blocking probability is 2%. The equivalent bit- rate is greater than 10 % of the bearer service data rate and 98% of a us- ers are not dropped. The motivation behind this approach is to metrically assess the benefits of the optimisation in terms of GOS.
This mapping has to be done for all services which are provided, i.e. services which are controlled with different parameter settings or other attrib- utes.
Although, each translation is causing degradation in accuracy, the mapping is statistically correct. Due to the fact that the operation is carried out in statistical level the best location for the mapping functions is NMS. Fur- thermore, NMS implementation is also able to handle the Radio Network Controller RNC-RNC (or other network element) border areas. In each of these translations the proposed cost function method is applied. In some of the cases the service QoS targets can cause conflict in the parameter settings, therefore a cost function is needed to solve the conflict. This can be carried out by providing different weight coefficients for the different elements in the cost function. This idea will gain importance when different
customer classes (silver, bronze, gold, etc) are introduced into the network system.
Furthermore, the next major step when changing to the last management layer of TOM model is to perform the evaluation of the network optimisation, service prioritising as well as customer differentiation operation in terms of €, $ or £. At this stage the billing and charging information from the Invoicing/Collecting subsystem in the customer care layer of the TOM is needed. When utilizing the knowledge of the customer base/profiles and behaviour of those profiles it is possible - on the basis of a cost function - to optimise the business case of the operator to the direction that is the most beneficial. It is worth noting that changing the customer priorities and offered QoS for business reasons will cause change in the customer behaviour and the business management level optimisation is thus iterative.
To guarantee the optimum performance of a cellular network, it is preferable for the operator to have flexible means to set the QoS target based on the system KPIs (key performance indicator) and/or a cost function derived from those. The QoS targets may either be set for a cell cluster or per cell basis. The QoS can be evaluated in terms of blocked calls due to hardware resources, "soft" blocked calls (in interference limited networks), dropped calls, bad quality calls, number of retransmissions and delay in case of packed data, diversity handover probability, hard handover success rate, loading situation (uplink UL or downlink DL), ratio of packed data to circuit switched services etc.
In multi-radio environments (GSM-WCDMA Global System for Mobile Communications - Wideband Code Division Multiple access) it is important to have the possibility to pool the resources of both of the networks for op- timised capacity, coverage and quality. This requires an over all control functionality (quality manager) on higher (KPI) level, i.e. the optimising
process according to the invention can be implemented as the quality manager.
The quality manager QM, i.e. the optimising process, provides a central monitoring function and monitors the status of the parameter values and identify automatically the problem situation by comparing the history information of the parameter values as stored in the history database. E.g. GERAN and UMTS Terrestrial Radio Access Network UTRAN can be split into auto-tuning subsystems as small and independent as possible. Inter- dependencies between subsystems are taken into account in upper layers of quality manager, by providing weight coefficients for the KPI's of their respective subsystems.
In another embodiment, the optimising process is carried out on the basis of user groups (like business users, free time uses etc.).
Summarising it can be said that, currently for all the parameter values default value are proposed. Up till now was the operator's task to optimise the network cell by cell (trying to take the multi-cell environment into ac- count). However, by using the method and/or the system for optimising the network performance according to the invention the initial parameter setting could be made less important. For example in the beginning of the network operation the admission control and handover control could work with very "loose" limits admitting all the users to the network, based on the current QoS situation (KPIs at the operating service system OSS) and the set QoS targets the relevant parameters can be auto-tuned. After the parameter change the new situation, i.e. the new KPI values, is compared to the KPI history data and the "test" parameters are accepted if the change in the QoS performance (or the cost function of the QoS requirements) is improved. The length of the history data depends on the amount of the traffic in the network (total number of samples should be high enough). It
is important that the QoS cost function contains items from the whole RRM and multi-radio area.
The key parameters (in terms of optimum capacity and quality) are currently initially set to a "default" value, which in most cases guarantees operation of the network but not the optimum performance. The optimising process according to the invention automatically changes the settings for the essential parameters to the optimum operating point in terms of overall QoS.
The adjustments of the configuration parameters can be constant increments or decrements. Alternatively, the increments or decrements can be made variable.