WO2009072941A1 - Procédé et dispositif pour la gestion de performance dans un réseau de communication - Google Patents

Procédé et dispositif pour la gestion de performance dans un réseau de communication Download PDF

Info

Publication number
WO2009072941A1
WO2009072941A1 PCT/SE2007/050930 SE2007050930W WO2009072941A1 WO 2009072941 A1 WO2009072941 A1 WO 2009072941A1 SE 2007050930 W SE2007050930 W SE 2007050930W WO 2009072941 A1 WO2009072941 A1 WO 2009072941A1
Authority
WO
WIPO (PCT)
Prior art keywords
performance
node
level
indicator
monitoring
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/SE2007/050930
Other languages
English (en)
Inventor
Anna Pucar Rimhagen
Erik Westerberg
Per-Daniel STÅLNACKE
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Priority to PCT/SE2007/050930 priority Critical patent/WO2009072941A1/fr
Publication of WO2009072941A1 publication Critical patent/WO2009072941A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks

Definitions

  • the present invention relates to a communications node in a cellular communica- tions network, a monitoring node in a cellular communications network and a monitoring method in a cellular communications network.
  • All communications networks today employ some kind of performance monitoring to monitor the function of the nodes or units in the network.
  • the performance data are reported from each node to a supervising node that is responsible for collecting and processing performance data for the whole network.
  • each network element is arranged to moni- tor performance management data. Which data to collect, and how they should be handled, is normally predefined in the network. Either a measurement is subscribed to or not. If it is subscribed to. it is stored for a certain amount of time in the network element as well as forwarded to the Domain Manager, where it is stored for a relatively long period of time, typically months. If it is not subscribed to. it is not collected at all.
  • a node for use in a communications network, said node comprising a monitoring unit arranged to collect performance data arranged hierarchically on at least a first and a second level, said performance data comprising at least one first level performance indicator re- lated to the operation of the network and at least one second level performance indicator associated with the first level performance indicator, the node being further arranged to forward at least part of said performance data to a domain manager arranged to control the radio network functions in the communications network, said node being characterized in that the monitoring unit is arranged to forward perform- ance data to the domain manager in dependence of the values of at least one kind of performance data.
  • the object is also achieved by method of performance monitoring in a communications network comprising the steps of - collecting performance data comprising at least one first level performance indicator related to the operation of the network, and
  • each network element may decide which data to collect, or to forward to the domain manager, in dependence of the situation in the network. The decision is usually made based on one or more key performance indicators. For example, for each key performance indicator a threshold may be set and if the registered value exceeds the threshold, one or more additional performance indicators associated with this key performance indicator are also collected. There may be a hierarchy so that if one or more of the additional performance indicators exceed a preset threshold, data associated with this performance indicator may be collected on a more detailed level. For clarity, in the claims the key performance indicators are referred to as "first level performance indicators" and the additional performance indicators are referred to as ''second level performance indicators " .
  • the monitoring unit is arranged to forward the second level performance indicator to the domain manager only if the associated first level performance indicator is outside of a first acceptable range defined for the first level performance indicator.
  • the method in this case preferably comprises the steps of
  • Typical first level performance indicators include the amount of traffic and the number of lost calls.
  • Performance indicators may be, for example, counters, events, recordings, traces and logs. Counters are simple indicators counting, for example, the number of lost calls. Events may occur once or in an irregular way, or may be peri- odic. For example, status reports may be periodic events. Recordings, traces and logs are used for specific measurements when a problem has been identified by means of counters or events.
  • an additional acceptable range should be set, that will be exceeded before the key performance indicator or performance indicator reaches the alarm level.
  • the node can identify an increased risk that an alarm level will be exceeded and start monitoring additional performance indicators before the alarm level is reached. For example, if a 2% increase in a particular error rate will constitute the alarm level, the threshold for collecting data according to the inven- tion could be 1%. In this way. if the alarm level is reached, performance data related to the situation that led to this situation will have been collected and stored. At the same time, data related to normal situations, in which performance data is of no interest does not have to be collected at all.
  • the network element can collect all data all the time, and the data to be forwarded to the DM and/or NMS may be selected in dependence of the situation. In this way the data collecting functions in the network element do not have to be activated and deactivated, which may simplify the design of the network element.
  • Which data to forward to the DM and/or NMS may be selected by the network ele- ment itself, or may be determined by the DM/NMS on the basis of key performance indicators received from the network element. In the latter case, the DM/NMS should request the desired additional data from the network element and the monitoring unit is arranged to collect performance data in dependence of information received from the domain manager.
  • the node may use the values of data on a higher level to determine which data on the next level should be forwarded.
  • the key performance indicator values may be used to determine which per- formance indicators should be forwarded. It may also use the value of the data itself to determine if it should be forwarded to the DM.
  • the performance indicators may be sampled at regular intervals and if they fall outside the accepted range they will be reported.
  • the node further comprises memory means, and said monitoring means is arranged to store performance data in the memory means.
  • the monitoring means may be arranged to collect the key performance indicator only if the key performance indicator is outside of the first acceptable range.
  • the monitoring step of the method comprises both the step of collecting the data and the step of forwarding the data to the domain manager.
  • the monitoring means may be arranged to collect a more detailed indica- tor associated with the performance indicator and to forward it to the domain manager, only if the performance indicator is outside of a second acceptable range defined for the performance indicator.
  • the monitoring step of the method comprises only the step of fon ⁇ arding the data to the domain manager.
  • the monitoring means may be arranged to collect the more detailed indicator only if the performance indicator is outside of the second acceptable range, or to collect it all the time but only forward it to the domain manager if it is outside of the second acceptable range.
  • the network is a cellular communications network.
  • the node may be a base station, such as an enhanced Node B, for controlling connections between a base station and a mobile terminal in the network.
  • the node may also be a radio network controller or a base station controller.
  • the invention also relates to a domain manager arranged to receive performance data from at least one node as defined in any one of the preceding claims, said domain manager comprising processing means for determining, on the basis of performance data received from the at least one node, the types of performance data it should receive from the node and communication means for instructing the node to forward the determined types of performance data to the domain manager. For example, if the key performance indicator is the number of lost calls in the network, and the threshold according to the invention is exceeded, additional performance indicators related to this key performance indicator may be monitored to give more detailed information, for example related to the reasons why calls are lost.
  • Calls may be lost, for example, because the radio conditions are poor, for example because of poor coverage or interference, or because the terminal's battery is empty. The reason why an unusually high amount of calls are lost will be decisive for the actions to be taken.
  • Figure 1 illustrates a first cellular network in which the invention may be implemented.
  • Figure 2 illustrates a second type of cellular network in which the invention may be implemented.
  • Figure 3 is an example of how performance indicators may be divided into different levels to be used according to the invention.
  • Figures 4a and 4b illustrate the recording of performance indicators on different levels in dependence of the performance of the network and over time, respectively.
  • Figure 5 is a flow chart of a method according to the invention.
  • the invention can be implemented in any type of communications network in which one or more nodes collect performance data and report said data to a supervising or monitoring node or system.
  • a possible im- plementation of the invention in a cellular network will be discussed.
  • the skilled person will realize that the inventive ideas can also be applied to other types of communications networks.
  • FIG. 1 illustrates a cellular network according to the Long Term Evolution (LTE) standard.
  • a core network 1 comprises one or more MMEs and one or more SAE Gateways (not shown) in a way well known to the skilled person.
  • Each core network 1 is connected to a radio network comprising a number of base stations 7, which in LTE are called enhanced node B or eNodeB.
  • the base stations 7 are used to connect to user equipment, which includes various types of user terminals 9.
  • Each base station 7 comprises a monitoring unit 8 for collecting performance data related to the performance in the network and a memory unit 10 for storing the performance data.
  • the performance data are stored in the base station 7 for a predetermined period of time, for example, 48 hours.
  • a domain manager 1 1 monitors the function of the radio network.
  • the domain manager 1 1 comprises communications means 12 for receiving performance data from the base stations 7. According to one embodiment the domain manager 1 1 also comprises processing means 13 for determining, based on the values of the performance data it has received, which types of performance data it should receive from each base station. In this case, the communications means 12 is also used for transmitting a request for these types of performance data to the base station.
  • Figure 1 only shows connections between the domain manager 1 1 and one of the base stations, for clarity.
  • the domain manager is typically an operation support system OSS which receives performance data recorded by the base stations 7 and may also forward it to a network management system NMS 15.
  • the NMS receives performance data from a number of different domain managers.
  • Figure 2 illustrates a different type of cellular network, which may be a Global System for Mobile communications (GSM) or a Wideband Code Division Multiple Access (WCDMA) system.
  • GSM Global System for Mobile communications
  • WCDMA Wideband Code Division Multiple Access
  • the network comprises a core network 1 communicating with a number of base stations 7.
  • a concentrating element 4 between the core network 1 and the base stations 7, each concentrating element connecting a plurality of base stations 7 to the core network 1.
  • the concentrating element 4 is a Base Station Controller (BSC).
  • the concentrating element 4 is a Radio Network Controller (RNC).
  • Each concentrating element comprises a monitoring unit 8 for mom ' toring performance indicators in the network and a memory unit 10 for storing the performance indicators.
  • a domain manager 1 1 is used to monitor the function of the core network 1 , the concentrating elements 4 and the base stations 7, and to forward information from the network elements to a network management system 15.
  • the domain manager 1 1 is arranged to monitor the base stations through the concentrating elements 4.
  • the domain manager 11 performs the same type of functions as in the network shown in Figure 1, but is arranged to communicate with the concentrating elements 4 instead of directly with the base stations 7.
  • each base station and/or each concentrating element is arranged to collect performance data from each node and report measurement results to the domain manager 11.
  • the rules for which performance data to collect and report are predetermined and are normally not changed very often. Typically, therefore, when making such rules, a compromise is made between the need for adequate data when a problem arises and the desire to keep the measurements and communication at a reasonable level.
  • the number and types of measurements to be made, and the types of data to be collected and forwarded to the DM are determined dynamically in dependence of the current situation in the network.
  • a number of key performance indicators should always be collected and forwarded. These key performance indicators should relate to the general functionality of the network and will typically include downlink latency, downlink and uplink throughput, number of calls made, setup success rate, abnormal release rate, and handover success rate.
  • all data are always collected by the relevant node. Instead, the inventive method is used to determine which data should be forwarded from the node to the domain manager.
  • FIG 3 illustrates a hierarchy of three levels: KPI level, PI level and more detailed level, respectively, the KPl level being the highest level, in which the key performance indicators are placed.
  • KPI 1 and KPI 2 which may be, for example, downlink Ia- tency and downlink throughput.
  • KPI 1 and KPI 2 which may be, for example, downlink Ia- tency and downlink throughput.
  • the relevant node should start collecting and forwarding more detailed data related to this key performance indicator at some point before the alarm level is reached.
  • the more detailed data related to KPI 1 involves one performance indicator, PI 1.1 , which may in this case be, for example, DL Send time, which is located on the pi level.
  • the value of this performance indicator may be used in a similar way, to trigger the monitoring of more detailed indicators on the more detailed level.
  • the more detailed indicators include three counters. Counter 1.1.1 , Counter 1.1.2 and Counter 1.1.3. Counter 1.1.2. in turn, may trigger the monitoring of counters on the next level.
  • Deterioration of PI 1.1 will trigger collection and forwarding of more detailed indicators as discussed above. Deterioration of the performance indicator PI 2.1 or PI 2.3 will not trigger any data collection on the next level. Performance indicator PI 2.2 will trigger collection of Counter 2.2.1 and Counter 2.2.2 on the third, more de- tailed level. Deterioration of the performance indicator PI 2.4 will trigger collection of a number of more detailed indicators on the more detailed level: Counter 2.4.1, Counter 2.4.2 and Counter 2.4.3. Counter 2.4.3 in turn may trigger collection of Counter 2.4.3.1 and Counter 2.4.3.2.
  • the node concerned may alternatively collect all performance indicators and indicators at all times but may select which ones to forward to the domain manager based on the values of the higher level indicators, as discussed above.
  • the collected data should also be stored in a memory unit in the relevant node for a predete ⁇ nined period of time, for example 48 hours, in case it becomes useful.
  • Figure 4a illustrates variations in the level of detail required for performance data.
  • the radio network performance spans from good, to the left, to poor, to the right.
  • the level of detail ranges from key performance indicators only, through performance indicators and detailed counters up to events and recordings. If the radio network performance is good, only key performance indicators are collected and forwarded to the domain manager. As the radio network performance deteriorates the relevant node will proceed to collect and forward performance indicators on the PI level, more detailed indicators on the more detailed level, such as detailed counters, and finally, logs, traces and recordings, which may be seen as a fourth level but are also shown on the third level in Figure 3. Alternatively, as explained above, all data may be collected and stored at all times, but only some, determined as discussed above, will be forwarded to the do- main manager.
  • Figure 4b shows an example of the variation of level of detail in collecting, storing and/or forwarding performance data over time.
  • the vertical axis shows increasing level of detail in the same way as Figure 4a. while the horizontal axis shows time.
  • the level of detail increases with time, to decrease again as time progresses further.
  • the curves shown in Figures 4a and 4b may relate to all collection/forwarding of performance indicators or to performance indicators related to one key performance indicator only, depending on the situation in the network.
  • Figure 5 is a flow chart of a method according to an embodiment of the invention.
  • step S51 a key performance indicator of a node is collected and stored in the node and also forwarded to the DM. At the same time, the performance indicators associated with this key performance indicator are collected and stored in the node.
  • step S52 it is determined whether the key performance indicator is within limit values set for this key performance indicator, typically, if it is below or above a threshold. If it is within the acceptable range, the node repeats steps S51 and S52 until the key per- formance indicator falls outside of the acceptable range. If so. the method continues with step S53.
  • step S53 the performance indicators related to this key performance indicator are forwarded to the domain manager along with the key performance indicators.
  • the node starts collecting and storing the more detailed indicators.
  • step S54 the node determines if each of the performance indicators is within its acceptable range. If so. steps 53 and 54 are repeated. If not. the method continues with step S55, in which the detailed indicators are also forwarded to the domain manager along with the key performance indicators and performance indicators. If at some point during the procedure the problem is solved, and all detailed indicators are within their acceptable range, the procedure may go back to repeating steps S53 and S54. If the performance indicators are also within their acceptable range, the procedure may go back to repeating steps S51 and S52.
  • steps S52 and S54 may be taken by the relevant node as described above. Alternatively, they may be taken by the domain manager or another node arranged to monitor the functions of the network. If the decision steps are performed by the node itself, no data need to be forwarded to the domain manager before a key performance indicator is outside of its acceptable range.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un nœud (4, 7) et un procédé de surveillance de performance dans un réseau de communication, ledit nœud comprenant une unité de surveillance (8) agencée pour collecter des données de performance comprenant au moins un indicateur de performance clé en relation avec le fonctionnement du réseau et au moins un indicateur de performance associé à l'indicateur de performance clé et acheminant au moins une partie desdites données de performance vers un gestionnaire de domaine (11) agencé pour contrôler les fonctions du réseau radio dans le réseau de communication. L'unité de surveillance (8) est agencée pour surveiller les données de performance en fonction des valeurs d'au moins un type de données de performance. Une hiérarchie de niveaux peut être définie pour les données de performance et la surveillance à chaque niveau peut être lancée par le dépassement d'un seuil sur le niveau plus élevé.
PCT/SE2007/050930 2007-12-03 2007-12-03 Procédé et dispositif pour la gestion de performance dans un réseau de communication Ceased WO2009072941A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/SE2007/050930 WO2009072941A1 (fr) 2007-12-03 2007-12-03 Procédé et dispositif pour la gestion de performance dans un réseau de communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/SE2007/050930 WO2009072941A1 (fr) 2007-12-03 2007-12-03 Procédé et dispositif pour la gestion de performance dans un réseau de communication

Publications (1)

Publication Number Publication Date
WO2009072941A1 true WO2009072941A1 (fr) 2009-06-11

Family

ID=40717946

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2007/050930 Ceased WO2009072941A1 (fr) 2007-12-03 2007-12-03 Procédé et dispositif pour la gestion de performance dans un réseau de communication

Country Status (1)

Country Link
WO (1) WO2009072941A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013066241A1 (fr) * 2011-11-04 2013-05-10 Telefonaktiebolaget L M Ericsson (Publ) Réduction de la quantité de reporting fait à un nœud de gestion
EP2836004A1 (fr) * 2013-08-07 2015-02-11 Alcatel Lucent Procédés et dispositifs pour déterminer une politique de signalement d'un indicateur de performance d'une cellule
WO2015127976A1 (fr) * 2014-02-27 2015-09-03 Nokia Solutions And Networks Oy Données de performance de réseau
WO2018082697A1 (fr) * 2016-11-07 2018-05-11 Huawei Technologies Co., Ltd. Système et procédés de surveillance des performances de tranches
CN110363379A (zh) * 2019-05-30 2019-10-22 中国电力科学研究院有限公司 一种电力系统的搜索及监控方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5905868A (en) * 1997-07-22 1999-05-18 Ncr Corporation Client/server distribution of performance monitoring data
EP1152570A2 (fr) * 2000-05-03 2001-11-07 Agilent Technologies, Inc. (a Delaware corporation) Systéme de surveillance de réseau avec collecte intégrée de données de surveillance
US20040193709A1 (en) * 2003-03-24 2004-09-30 Selvaggi Christopher David Methods, systems and computer program products for evaluating network performance using diagnostic rules
US20060023646A1 (en) * 2004-07-30 2006-02-02 George David A Method and apparatus for anonymous data transfers

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5905868A (en) * 1997-07-22 1999-05-18 Ncr Corporation Client/server distribution of performance monitoring data
EP1152570A2 (fr) * 2000-05-03 2001-11-07 Agilent Technologies, Inc. (a Delaware corporation) Systéme de surveillance de réseau avec collecte intégrée de données de surveillance
US20040193709A1 (en) * 2003-03-24 2004-09-30 Selvaggi Christopher David Methods, systems and computer program products for evaluating network performance using diagnostic rules
US20060023646A1 (en) * 2004-07-30 2006-02-02 George David A Method and apparatus for anonymous data transfers

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013066241A1 (fr) * 2011-11-04 2013-05-10 Telefonaktiebolaget L M Ericsson (Publ) Réduction de la quantité de reporting fait à un nœud de gestion
US8909208B2 (en) 2011-11-04 2014-12-09 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for mode driven node monitoring
EP2836004A1 (fr) * 2013-08-07 2015-02-11 Alcatel Lucent Procédés et dispositifs pour déterminer une politique de signalement d'un indicateur de performance d'une cellule
WO2015018488A1 (fr) * 2013-08-07 2015-02-12 Alcatel Lucent Procédés et appareils permettant de déterminer une politique de communication d'un indicateur de performance de cellule
WO2015127976A1 (fr) * 2014-02-27 2015-09-03 Nokia Solutions And Networks Oy Données de performance de réseau
CN106233665A (zh) * 2014-02-27 2016-12-14 诺基亚通信公司 网络性能数据
WO2018082697A1 (fr) * 2016-11-07 2018-05-11 Huawei Technologies Co., Ltd. Système et procédés de surveillance des performances de tranches
US10827366B2 (en) 2016-11-07 2020-11-03 Huawei Technologies Co., Ltd. System and methods for monitoring performance of slices
CN110363379A (zh) * 2019-05-30 2019-10-22 中国电力科学研究院有限公司 一种电力系统的搜索及监控方法

Similar Documents

Publication Publication Date Title
US8542627B2 (en) System and method for determining air interface information for radio resource management in wireless communications
US10588035B2 (en) Method and apparatus to separate coverage limited and co-channel limited interferences
US8125919B1 (en) Method and system for selectively releasing network resources
US9674713B2 (en) Arrangements and methods in communication nodes
US20070259671A1 (en) Generation, Deployment and Use of Tailored Channel Quality Indicator Tables
US20110130137A1 (en) Outage Recovery In Wireless Networks
EP1238480A2 (fr) Procede et dispositif de detection de defaillances d'emetteurs-recepteurs de station de base
EP3183903A1 (fr) Classification de brouilleur sur la base de la force de signal reçu de cellules de réseau cellulaire
WO2009072941A1 (fr) Procédé et dispositif pour la gestion de performance dans un réseau de communication
US7236795B2 (en) Controlling processor load in a wireless telecommunications network node
WO2006068559A1 (fr) Procedes et systemes destines a l'estimation de la couverture ascendante dans des reseaux de telecommunications sans fil avec une couverture dynamique de cellules
EP2571314A1 (fr) Procédé et appareil permettant des statistiques de fréquence de resélection intersystème
KR100452621B1 (ko) 이동 통신 시스템에서의 호 접속실패 원인 분석 방법
KR20210103753A (ko) 간섭원 검출장치 및 간섭원 검출방법
US20050083900A1 (en) Event based reporting method
CN116709406B (zh) 一种基于5g通信的业务组网管理系统
KR20050001000A (ko) 네트워크 관리 시스템의 티켓 발행방법 및 그 장치

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07852202

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 07852202

Country of ref document: EP

Kind code of ref document: A1