CA2339781A1 - Self-engineering telecommunications network including an operation and maintenance control point - Google Patents

Self-engineering telecommunications network including an operation and maintenance control point Download PDF

Info

Publication number
CA2339781A1
CA2339781A1 CA002339781A CA2339781A CA2339781A1 CA 2339781 A1 CA2339781 A1 CA 2339781A1 CA 002339781 A CA002339781 A CA 002339781A CA 2339781 A CA2339781 A CA 2339781A CA 2339781 A1 CA2339781 A1 CA 2339781A1
Authority
CA
Canada
Prior art keywords
network
omcp
results
suggested
traffic
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.)
Abandoned
Application number
CA002339781A
Other languages
French (fr)
Inventor
Bo Svensson
Roch Glitho
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
Individual
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 Individual filed Critical Individual
Publication of CA2339781A1 publication Critical patent/CA2339781A1/en
Abandoned legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/02Arrangements for optimising operational condition
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q3/00Selecting arrangements
    • H04Q3/0016Arrangements providing connection between exchanges
    • H04Q3/0062Provisions for network management
    • H04Q3/0075Fault management techniques
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/04Arrangements for maintaining operational condition

Abstract

An operation and maintenance control point (OMCP) (31) operates at an intermediate level in a telecommunications network between the network elements (32) and the network management system (NMS) (21). The OMCP reduces the processing load on the NMS, and rather than reporting symptoms, provides the NMS with suggested corrective (49) actions to correct reported problems.
The NMS executes the suggested corrective actions and compares the actual results (52) in the network with predicted results. Feedback on the results is then provided to the OMCP to improve its analysis and provide more effective corrective actions are suggested if the problem recurs. By automatically interfacing with the NMS, which analyzes and executes the suggested corrective actions, the OMCP creates a self-engineering telecommunications network.

Description

PCTlSE99/01346 SELF-ENGINEERING TELECOMMUNICATIONS NETWORK
INCLUDING AN OPERATION AND MAINTEhIANCE CONTROL POINT
BACKGROUND OF THE INVENTION
Technical Field of the Invention This invention relates to telecommunication systems and; more particularly, to a self engineering telecommunications network which includes an operation and maintenance control point.
Description of Related Art Existing telecommunications networks interface with aNetwork Management System (NMS) which oversees the operation and maintenance of the network. The NMS communicates with different network elements (NEs) in the network. The NEs send reports to the NMS indicating the performance. of the reporting NE. When a fault occurs in a NE, the NE sends an alarm and the fault symptoms to the NMS. ~-Iowever, the reported symptoms are often not enough to enable efficient management of the network. In addition, the NMS is centralized with many NEs reporting to the NMS.
The processing load is too great for the NMS to efficiently analyze the reported symptoms and determine the root causes of the problems.
. 20 There are no known prior art teachings of a solution to the aforementioned deficiency and shortcoming such as that disclose! herein. It would be advantageous to have an operation and maintenance control point which operates at an intermediate level in the network between the NEs and the NNlS. Such a device would reduce the processing load on the NMS and rather than reporting symptoms, would provide the NMS with suggested corrective actions to correct reported problems. By automatically interfacing with the NMS, which analyzes and executes the suggested corrective actions, the operation and maintenance control point would create a self engineering telecommunications network.

r WO 00/11884 . PCT/SE99/01346 SUMMARY OF THE INVENTION
In one aspect, the present invention is an operation and maintenance control point (OMCP) in a telecommunications network having a plurality of network elements that report to the OMCP and a network management system (NMS) to which ' the OMCP reports. The OMCP comprises a peri:ormance monitoring function that monitors performance of the network elements and determines quality of service (QoS) in the network, a trouble sniffer that receives performance and QoS data from the performance monitoring function and detects faults within the network, and an action proposal agent that receives performance and QoS data from the performance monitoring function and fault data from the troutrle sniffer, and provides suggested corrective actions to the NMS.
In another aspect, the present invention is a self engineering telecommunications network comprising a plurality of network elements (NEs), an operation and maintenance control point (OMCP) that receives preprocessed data from 1 S the NEs and determines suggested corrective actions, and a network management system (NMS) that receives the suggested corrective actions from the OMCP and executes them. Each of the NEs includes means. for collecting raw traffic data and exchange data, and means for preprocessing the raw data. The OMCP includes a performance monitoring function that monitors performance of the NEs and determines quality of service (QoS) in the network, a trouble sniffer that receives performance and QoS data from the performance monitoring function and detects faults within the network, and an action proposal .agent that receives performance and QoS data from the performance monitoring function and fault data from the trouble sniffer, and determines suggested corrective actions. The NMS includes means for predicting results within the network of executing the suggested corrective actions, means for executing the suggested corrective actions, means for determining the actual results of executing the suggested corrective actions, and means fox providing feedback to the action proposal agent regarding the actual results. The action proposal agent then utilizes the feedback to provide better suggested corrective actions.
In another aspect, the present invention is a method of implementing a self engineering telecommunications network. The method begins by automatically w0 00111884 PC'1'ISE99I01346 collecting information about the network's performance, detecting problems with the network's performance utilizing the collected information, and analyzing possible causes of the detected problems. The method continues by automatically determining suggested corrective actions to correct the causes, predicting results of executing the suggested actions, and executing the actions. This is followed by automatically comparing actual results of executing the suggested actions with the predicted results, and learning from the comparing step so that improved corrective actions are suggested when problems recur.
In yet another aspect, the present invention 'is a method of performing traffic load sharing between the cells of a self engineering cellular radio telecommunications network. The network includes a mobile switching center (MSC) and a plurality of radio base stations serving a plurality of cells. The method comprises the steps of collecting by the MSC, traffic measurements from all the cells in the service area of the MSC, sending the traffic measurements to an operation and maintenance control point (OMCP), determining in the OMCP whether there is adverse traffic loading in the cells that is adversely affecting network vperformance, and automatically determining in the OMCP, suggested changes in cell sizes to correct the adverse traffic loading.
In still another aspect, the present invention is a method of configuring and testing a new hardware or software device in a selif engineering telecommunications network. The method begins by installing the new device in the network to correct a reported problem, detecting the new device by a network element, generating by the network element, an event indicating what type; of device was installed and its predefined usage, and loading and configuring tlhe device with predefined default parameters. This is followed by reporting to an operation and maintenance control point (OMCP) that the new device has been insta.Iled; collecting raw exchange data and traffic data by the network element, and sending the collected data to the OMCP.
The OMCP then monitors the performance ofthe new device and the quality of service in the network, and determines whether the new device has failed. If it has failed, the OMCP performs fault analysis to determine why the new device failed, and reports a failure cause to a network management system (MvIS) for corrective action. If the new t ~y~, device did not fail, the method continues by reporl:ing to the NMS that the new device has been installed and is working properly, utilizing simulations by the NMS
to predict effects on network performance of utilizing the; properly working new device to process traffic in the network, and utilizing the new device in traffic processing. This ' is followed by determining actual results of utilizing the new device in traffic processing, comparing the actual results with the; predicted effects, and refining the simulations to increase the accuracy of the predicted effects.
In yet another aspect, the present invention is a method of analyzing a reported fault from a hardware or software device in a network element in a self engineering telecommunications network. The method begins by collecting by the network element a fault event from raw exchange data and traffic data, determining in the network element whether the event is new or whether it has been previously discovered and reported, and sending the event to an operation and maintenance control point (OMCP) if the event is new. This is followed by determining in a performance monitoring function in the OMCP whether a predefined performance threshold has been crossed, passing information regarding the event to a trouble sniffer function in the OMCP, determining a root cause of the fault event in the trouble sniffer function, and determining in an action propo:>al agent in the OMCP, suggested corrective actions to correct the fault event. The OMCP then sends the suggested corrective actions to a network management system (NMS) where simulation programs are utilized to predict results of executing the suggested corrective actions.
The method then determines whether the predicted results are acceptable, modifies the suggested corrective actions in the OMCP upon determining that the NMS's predicted results are unacceptable, and executes the suggested corrective actions upon determining that the NMS's predicted results a.re acceptable. This is followed by determining actual results of executing the suggested corrective actions;
comparing the actual results with the predicted results, and sending feedback to the action proposal agent to enable the agent to improve the suggested corrective actions.
BRIEF DESCRIPTION OF THE DRAWINIsS
The invention will be better understood and its numerous objects and advantages will become more apparent to those skilled in the art by reference to the following drawings, in conjunction with the accompanying specification, in which:
FIG. 1 (Prior Art) is a simplified block diagram of an existing telecommunications network and Network Managernent System (NMS);
FIG. 2 is a simplified block diagram of a telecommunications network in which the Operation and Maintenance Control Point (OMCP) of the present invention has been implemented;
FIG. 3 is a simplified black diagram illustrating the flow of information in a self engineering telecommunications network in which the OMCP of the present invention has been implemented;
FIG. 4 is a flow chart illustrating the steps involved in a method of performing traffic load sharing in the self engineering telecomnnunications network of FIG. 3;
FIG. 5 is a flow chart illustrating the steps involved in a method of configuring and testing the installation of new or changed hardware in the self engineering telecommunications network of FIG..3; and FIG. 6 is a flow chart illustrating the steps involved in a method of analyzing a reported fault in the self engineering telecommunications network of FIG. 3.
DETAILED DESCRIPTION OF EMBODIMEl'JTS
FIG. 1 is a simplified block diagram of an existing telecommunications network 10 and a Network Management System (t~lVIS) 11. A number of Network Elements (NEs) report symptoms and alarms to the; NMS. The NMS is centralized, and has many reporting NEs. In FIG. 1, the telecommunications network 10 is a cellular radio telecommunications network, and the NEs include a Short Message Service Message Center (MC) 12, a Radio Base Station (RBS) 13, a Mobile Switching Center (MSC) 14, a Home Location Register (HLR.) 15, and a Service Control Point (SCP) 16. In actual practice, many more NEs would be reporting to the NMS.
FIG. 2 is a simplified block diagram of a telecommunications network 20 in which the Operation and Maintenance Control Point (OMCP) of the present invention has been implemented. In the configuration ofFlG. :2, aNetwork Management System (NMS) 21 is connected via an open interface to two OMCPs, OMCP-1 and OMCP-2 22 and 23. OMCP-1 is connected via high speed, reliable interfaces to a plurality of NEs (NE, through NEN) 24. OMCP-2 is also connected via high speed, reliable interfaces to a plurality of NEs (NE, through NFL,,) 25. Although two OMCPs have been illustrated, the invention is not limited to two, and a greater or lesser number may ' S be utilized. The OMCP may be centralized or distributed, depending on the size of the network. In general, rather than just sending symptoms to the NMS 21, the OMCP
sends suggested corrective actions. In the following figures, the operation of a single w..
f.
OMCP is described, although it should be recognized that several such OMCPs may be operating in a network and interfacing with the: NMS in a similar manner.
FIG. 3_is a simplified block diagram illustrating the flow of information in a self engineering telecommunications network in which the OMCP 31 of the present invention has been implemented. A self engine~ening network is a network which automatically collects information about its performance, detects problems, analyzes the possible causes of the problems, determines suggested corrective actions, predicts the results of executing the actions, executes the actions, compares the actual results with the predicted results, and learns from the experience so that improved corrective actions are suggested the next time. The networl~: includes the NMS 21, the OMCP
31, and a NE 32 (MSC). The NE has raw data 3:3 (for example, a card or a line in a base station 30 is defective) which needs to be. reported to the NMS so that the network can be properly and efficiently managed.. Raw data may come from traffic data 34 or exchange data 35, and may includes, for example, exchange and cell configuration and performance data. In most NEs, approximately seven days of time-stamped data are stored.
The NE performs preprocessing to compress the data and sort it according to .
logical groups. Approximately 120 days of preprocessed data may be stored in order to enable accurate trend calculations to be performed. The preprocessed data is then sent to the OMCP 31 over the high speed interface.
Some of the preprocessed data enters the C>MCP 31 through a Performance and Quality of Service (QoS) Monitoring (PQSM) function 36, and some of the data enters through a Trouble Sniffer (TS) 37. The OMCP uses the PQSM function to monitor performance and QoS in the network. Perfoxmarice thresholds are defined (manually WO 00/11884 PCTlSE99/01346 and/or automatically), and performance is presented to assess the current situation and current utilization level in the network. QoS may b~e monitored for specified cases such as handoffs and call setups.
The PQSM function 36 determines whether l:here is a problem with the QoS.
If there is no degradation in the QoS exceeding any threshold, the data is passed directly from the PQSM function to an Action Proposal Agent (APA) 38. If there is QoS degradation, the PQSM function sends the data to the TS 37. The TS
performs calculations to detect the cause of the degradation in the QoS. In addition to the input from the performance monitoring function, the TS considers the configuration of the system, all of the current performance measurements, trend calculations, and fault states. The OMCP interfaces with external systems 43 utilizing various transport networks such as PDH, SS7, etc. The external systems also provide input to the APA
to assist in determining faults and corrective actions.
The suspected cause of the QoS degradation is then sent from the TS 37 to the APA 38. The APA analyzes the suspected cause of the problem, and determines suggested corrective actions which are then sent to the NMS 21. The suggested corrective actions may include, but are not limited ito proposals for:
Link performance (e.g., more/fewer links needed);
- Cell performance (e.g., change parameter settings, change frequencies);
- Hardware performance (e.g., more hardware needed, efficiency of hardware utilization, hardware out of order);
- System performance (e.g., more cells needed, load sharing efficiency);
- Mobile station performance (considering specific MS types);
- Remedy for a fault situation; and - Configuration changes in the network.
In a simulation block 39, the NMS may nm multiple simulations to predict what the results would be if the suggested corrective actions are executed in the network. If the NMS's predictions are unacceptable, feedback is sent to the which modifies its suggested corrective actions based on the feedback from the NMS.
If~the NMS's predictions are acceptable, the suggested corrective actions are then _g_ executed by an execution function 41, either manually or automatically. Areas suitable for automatic execution include frequency reallocations, temporary traffic load sharing, etc.
Following execution of the suggested actions, data is collected regarding the actual results of the actions in the network. A feedback function 42 in the then sends feedback to the APA 38 in the OMCP 31 regarding the actual results of executing the suggested corrective actions. The feedback includes trend analyses and a comparison of before and after results, both in t:he changed area and for total system performance.
I O If the results are not acceptable, the APA 38 may send additional suggested corrective actions to the NMS 21, utilizing the experience acquired from the results of the first actions. If the problem is corrected, then the OMCP passes NE
reports directly to the NMS since no corrective action is required.
The above process is a continuous ongoing process. It should also be noted that while the first illustrated step (preprocessing of raw data} takes only a few seconds, the final steps involve more lengthy measurements and trend analysis of the data;. and may take several hours or days to complete. Several examples of how the OMCP and the self engineering system operate .are described below.
Traffic Load Sharing FIG. 4 is a flow chart illustrating the step;. involved in a method of performing traff c load sharing in the self engineering telecommunications network ofFIG.
3. At step 45, traffic measurements from all cells is collected as raw data by the NE 32. In a preprocessing step at 46, the data is compressed and sorted into logical groups to facilitate performance monitoring and analysis. 'The preprocessed data is then sent to the OMCP 31 over a high speed interface. Dat<i related to system performance and quality of service is analyzed at 47 in the PQSM function 36. The PQSM
function utilizes performance "gauges" such as voice channel utilization, paging load, and registration load in each cell to determine whether any adverse loading is due to excess paging, registrations, or other causes. At 48, tile TS 37 analyzes the data to detect whether there is a fault, and to identify the fault if one is detected. The results of the _g_ analyses at steps 47 and 48 are sent to the APA 38 where possible corrective actions are determined at step 49. The possible corrective actions may include changing hysteresis values to temporarily change cell sizes and to shift the traffic load from heavily loaded cells to more lightly loaded cells, changing the capacity of various cells, or changing other cell parameters. The APA also analyzes long term trends to determine whether more capacity is needed in some cells.
The APA then suggests corrective actions to the NMS 21. At step 50, the NMS utilizes its simulation programs to predict what the. results would be if the suggested corrective actions are executed. The simulations predict, for example, the resulting traffic in each cell, the impact on the interference level in the network, and the impact on mobile station signal strength level. If the NMS's predictions are unacceptable, feedback is sent to the APA 38 which modifies its suggested corrective actions based on the feedback from the NMS. If the NMS's predictions are acceptable, the suggested corrective actions are then executed either manually or automatically at step 51. The NMS then collects reports from the rlEs and analyzes them to determine what the actual results of the corrective actions were. The actual results are fed back to the APA at step 52 to continuously improve the proposed actions.
As noted above, the self engineering system may change cell sizes automatically in order to shift traffic load and eliminate problems in the network. This process includes automatically changing the hysteo~esis values affecting where handoffs and cell reselections occur, and automatically adjusting transmitter power in the base station to increase or decrease the cell size. In the past, this has been a manual task performed by the system operator based on operator experience.
Detection of New/Chang_ed Hardware FIG. 5 is a flow chart illustrating the steps involved in a method of configuring and testing the installation of new or changed haxdware, such as a new piece of base station equipment, in the self engineering telecommunications network of FIG.
3.
When new base station equipment is installed in. a cell site at 55, the new equipment is detected by the MSC 32. An event is generated at 56 indicating the type of hardware installed and its predefined usage, in this case hardware for a base station.

Based on the hardware type and its predefined usage, the hardware is loaded and configured with predefined default parameters a1: S7. Knowledge that a new piece of equipment has been installed is then reported to the OMCP.
At step S8, the MSC 32 collects raw exclhange data and traffic data, and then S preprocesses the raw data at S9. The preprocessed data is then passed to the OMCP
31. The OMCP monitors the performance of the new equipment and the QoS in the network in accordance with predefined standards at steps 60 and 61, respectively. If the new equipment fails, the TS begins fault ana.Iysis at 62 to determine the cause of the failure. .The cause is reported through the APA to the NMS 21 for corrective action at 63. If the equipment is working properly, and the problem is corrected, the APA reports to the NMS at 63 that a new piece of equipment has been installed and is working properly. The NMS then predicts the; results of a properly working piece of equipment at 64, and then uses the equipment in traffic processing at 6S.
The actual results are compared with the predicted results at 66, and the results are fed back to the 1 S APA. If the results are good, the NMS may then close down any open. work order for the installation of the new piece of hardware.
Fault Analysis FIG. 6 is a flow chart illustrating the steps involved in a method of analyzing a reported fault in the self engineering telecommunications network of FIG. 3.
At step 71, the raw exchange and traffic data collected 'by the NE 32 indicates a fault event (alarm) from a hardware or software device. Ai: step 72, the event is filtered and/or correlated in the NE to determine whether it has been previously discovered and reported. If the event is new, the event is sent to the OMCP 31.
2S In the OMCP, performance monitoring may indicate a fault at step 73. The performance data is analyzed for quality of service at 74, and if a predefined threshold is crossed, an event may be generated indicating that levels of expected QoS
have not been reached. The TS then analyzes the data at 7S and pin-points a root cause.
The TS may be triggered to perform its analysis as a result of continuous monitoring, or as a result of a direct request by the APA. The root cause is then sent to the APA.
In the APA, inputs from external systems such as events from a transport network management system 43 are also utilized to analyze the root cause at 76.
Different types of correlation algorithms are then applied to the existing set of events to determine suggested corrective actions. At step 77, the NMS utilizes its simulation programs to predict what the results would be if the; suggested corrective actions are implemented. If the NMS's predictions are unacceptable, feedback is sent to the APA
which modifies its suggested corrective actions based on the feedback from the NMS.
If the NMS's predictions are acceptable, the suggested corrective actions are then executed either manually or automatically at step 7~3. The NMS then collects reports from the NEs and analyzes them to determine what the actual results of the corrective actions were. The actual results are fed back to the APA at step 79 to continuously improve the proposed corrective actions.
It is thus believed that the operation and construction of the present invention will be apparent from the foregoing description. While the system and method shown and described has been characterized as being prefe~~red, it will be readily apparent that I S various changes and modifications could be made therein without departing from the spirit and scope of the invention as defined in the Following claims.

Claims (20)

WHAT IS CLAIMED IS:
1. An operation and maintenance control point (OMCP) in a telecommunications network having a plurality of network elements that report to the OMCP and a network management system (NMS) to which the OMCP reports, said OMCP comprising:
a performance monitoring function that monitors performance of the network elements and determines quality of service (QoS) in the network;
a trouble sniffer that receives performance and QoS data from the performance monitoring function and detects faults within the network; and an action proposal agent, wherein the action proposal agent:
receives performance and QoS data from the performance monitoring function and fault data from the trouble sniffer;
provides suggested corrective actions to the NMS, the NMS
having means for predicting results within the network of executing the suggested corrective actions and providing the results to the action proposal agent;
receives the predictive results from the NMS;
determines whether the suggested corrective actions should be revised based on the predictive results; and provides revised suggest corrective actions to the NMS upon determining that they should be revised.
2. A self engineering telecommunications network comprising:
a plurality of network elements (NEs), each of said NEs including:
means for collecting raw traffic data and exchange data; and means for preprocessing the raw data;
an operation and maintenance control point (OMCP) that receives the preprocessed data from the NEs, said OMCP including:
a performance monitoring function that monitors performance of the NEs and determines quality of service (QoS) in the network;
a trouble sniffer that receives performance and QoS data from the performance monitoring function and detects faults within the network; and an action proposal agent that receives performance and QoS data from the performance monitoring function and fault data from the trouble sniffer, and determines suggested corrective actions, wherein the action proposal agent includes means for revising the suggested corrective actions upon receiving feedback from the means for predicting results that the predicted results are unsatisfactory; and a network management system (NMS) that receives the suggested corrective actions from the OMCP, said NMS including:
means for predicting results within the network of executing the suggested corrective actions, the means for predicting results including means for providing feedback to the action proposal agent if the predicted results are not satisfactory;
means for executing the suggested corrective actions;
means for determining the actual results of executing the suggested corrective actions; and means for providing feedback to the action proposal agent regarding the actual results, said action proposal agent including means for utilizing the feedback to provide better suggested corrective actions.
3. The self-engineering telecommunications network of claim 2 wherein the means for preprocessing the raw data includes means for compressing the raw data and sorting the data into logical groups.
4. The self-engineering telecommunications network of claim 2 wherein the NMS also includes means for performing trend analyses regarding performance of the NEs and quality of service (QoS) in the network.
5. The self-engineering telecommunications network of claim 2 wherein the network is a cellular radio telecommunications network, and the suggested corrective actions include automatically changing cell sizes to improve network performance.
6. The self-engineering telecommunications network of claim 2 wherein the OMCP also includes means for interfacing with external systems to obtain network management information.
7. The self-engineering telecommunnications network of claim 2 wherein:
one of the network elements is a mobile switching center (MSC) that collects traffic measurements from a plurality of cells in the MSC's service area and sends the measurements to the OMCP;
the OMCP determines that there is adverse traffic loading in the cells that is adversely affecting network performance; and the suggested corrective actions include changing cell sizes to correct the adverse traffic loading.
8. The self-engineering telecommunications network of claim 7 wherein the NMS simulates the resulting traffic in each cell resulting from the changing cell sizes to predict resulting signal strength levels and interference levels in the network.
9. A method of implementing a self-engineering telecommunications network comprising the steps of:
automatically collecting information about the network's performance;
automatically detecting problems with the network's performance utilizing the collected information;
automatically analyzing possible causes of the detected problems;
automatically determining suggested corrective actions to correct the causes;
automatically predicting results of executing the suggested actions;
automatically determining from the predicted results, whether the suggested corrective actions will correct the problems;
automatically determining improved suggested corrective actions to correct the causes, upon determining that the suggested corrective actions will not correct the problems;
automatically executing the actions;
automatically comparing actual results of executing the suggested actions with the predicted results; and automatically learning from the comparing step so that improved corrective actions are suggested when problems recur.
10. In a cellular radio telecommunications network having a plurality of radio base stations, a method of automatically changing cell sizes in order to shift traffic loads and eliminate performance and quality of service problems in the network, said method comprising the steps of:
automatically collecting information about network performance and quality of service;
automatically detecting problems utilizing the collected information;
automatically determining that a cause of the problems is adverse traffic loading in the cells;
automatically simulating results of shifting traffic from heavily loaded cells to more lightly loaded cells;

automatically changing hysteresis values affecting where handoffs and cell reselections occur based on the simulated results of shifting traffic; and automatically adjusting transmitter power in the radio base stations based on the simulated results of shifting traffic.
11. The method of automatically changing cell sizes of claim 10 wherein the step of automatically simulating results of shifting traffic includes:
simulating resulting traffic in each cell;
simulating resulting interference levels in the network; and simulating resulting impact on mobile station signal strength level.
12. In a self-engineering cellular radio telecommunications network having a mobile switching center (MSC) and a plurality of radio base stations serving a plurality of cells, a method of performing traffic load sharing between the cells, said method comprising the steps of:
collecting by the MSC, traffic measurements from all the cells in the service area of the MSC;
sending the traffic measurements to an operation and maintenance control point (OMCP);
determining in the OMCP whether there is adverse traffic loading in the cells that is adversely affecting network performance; and automatically determining in the OMCP, suggested changes in cell sizes to correct the adverse traffic loading, wherein the; step of determining suggested changes in cell sizes includes utilizing the results of simulation programs run to simulate resulting traffic in each cell, resulting interference levels in the network, and resulting impact on mobile station signal strength level.
13. The method of performing traffic load sharing of claim 12 further comprising, after the step of collecting traffic measurements by the MSC, the step of compressing and sorting the measurements into logical groups to facilitate performance monitoring and analysis.
14. The method of performing traffic load sharing of claim 12 wherein the step of determining whether there is adverse traffic loading in the cells includes analyzing voice channel utilization, paging load, and registration load in each cell to determines whether there is any adverse traffic loading.
15. The method of performing traffic load sharing of claim 12 wherein the step of automatically determining suggested changes in cell sizes includes determining changes in hysteresis values to modify handoff and cell reselection parameters.
16. The method of performing traffic load sharing of claim 12 further comprising analyzing long term trends to determine whether more capacity is needed in some cells.
17. The method of performing traffic load sharing of claim 12 further comprising, after the step of determining suggested changes in cell sizes, the steps of:
executing the suggested changes in cell sizes;
determining actual results of executing the suggested changes in cell sizes;
and refining the simulation programs to improve the suggested changes in cell sizes.
18. The method of performing traffic load sharing of claim 17 wherein the step of executing the suggested changes in celll sizes includes the steps of:
changing hysteresis values affecting where handoffs and cell reselections occur; and adjusting transmitter power in the radio base stations.
19. In a self engineering telecommunications network, a method of configuring and testing a new hardware or software device, said method comprising the steps of:
installing the new device in the network to correct a reported problem;
detecting the new device by a network element;
generating, by the network element, an event indicating what type of device was installed and its predefined usage;
loading and configuring the device with predefined default parameters;
reporting to an operation and maintenance control point (OMCP) that the new device has been installed;
collecting raw exchange data and traffic data by the network element;
sending the collected data to the OMCP;
monitoring by the OMCP, performance of the new device and the quality of service in the network;
determining in the OMCP whether the new device has failed;

performing fault analysis in the OMCP to determine why the new device failed, upon determining that it has failed;
reporting a failure cause to a network management system (NMS) for corrective action;
reporting to the NMS that the new device has been installed and is working properly upon determining that the new device has not failed;
utilizing simulations by the NMS to predicts effects on network performance of utilizing the properly working new device to process traffic in the network;
utilizing the new device in traffic processing;
determining actual results of utilizing the new device in traffic processing;
comparing the actual results with the predicted effects; and refining the simulations to increase the accuracy of the predicted effects.
20. In a self engineering telecommunications network, a method of analyzing a reported fault from a hardware or software device in a network element, said method comprising the steps of:
collecting by the network element, a fault event from raw exchange data and traffic data;
determining in the network element whether the event has been previously discovered and reported;
sending the event to an operation and maintenance control point (OMCP) if the event is new;
determining in a performance monitoring function in the OMCP, whether a predefined performance threshold has been crossed;
passing information regarding the event and the crossed threshold to a trouble sniffer function in the OMCP;
determining a root cause of the fault event in the trouble sniffer function;
determining in an action proposal agent in the OMCP, suggested corrective actions to correct the fault event;
sending the suggested corrective actions to a network management system (NMS);
utilizing simulation programs in the NMS to predict results of executing the suggested corrective actions;
determining whether the predicted results axe acceptable;
modifying the suggested corrective action in the OMCP upon determining that the NMS's predicted results are unacceptable;
executing the suggested corrective actions upon determining that the NMS's predicted results are acceptable;

determining actual results of executing the suggested corrective actions;
comparing the actual results with the predicted results; and sending feedback to the action proposal agent to enable the agent to improve the suggested corrective actions.
CA002339781A 1998-08-24 1999-08-06 Self-engineering telecommunications network including an operation and maintenance control point Abandoned CA2339781A1 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US09/138,719 1998-08-24
US09/138,719 US6233449B1 (en) 1998-08-24 1998-08-24 Operation and maintenance control point and method of managing a self-engineering telecommunications network
PCT/SE1999/001346 WO2000011884A1 (en) 1998-08-24 1999-08-06 Self-engineering telecommunications network including an operation and maintenance control point

Publications (1)

Publication Number Publication Date
CA2339781A1 true CA2339781A1 (en) 2000-03-02

Family

ID=22483311

Family Applications (1)

Application Number Title Priority Date Filing Date
CA002339781A Abandoned CA2339781A1 (en) 1998-08-24 1999-08-06 Self-engineering telecommunications network including an operation and maintenance control point

Country Status (6)

Country Link
US (1) US6233449B1 (en)
AR (1) AR021197A1 (en)
AU (1) AU758719B2 (en)
BR (1) BR9913166A (en)
CA (1) CA2339781A1 (en)
WO (1) WO2000011884A1 (en)

Families Citing this family (75)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100259864B1 (en) * 1998-03-06 2000-06-15 윤종용 A selecting method of location registration zone in code division multiple access system
US6832085B1 (en) * 1998-04-14 2004-12-14 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for radio network management
US7127499B1 (en) * 1998-11-25 2006-10-24 General Electric Company Medical diagnostic system service method and apparatus
US6446123B1 (en) * 1999-03-31 2002-09-03 Nortel Networks Limited Tool for monitoring health of networks
AU5156800A (en) * 1999-05-24 2000-12-12 Aprisma Management Technologies, Inc. Service level management
US6577597B1 (en) 1999-06-29 2003-06-10 Cisco Technology, Inc. Dynamic adjustment of network elements using a feedback-based adaptive technique
US6505244B1 (en) * 1999-06-29 2003-01-07 Cisco Technology Inc. Policy engine which supports application specific plug-ins for enforcing policies in a feedback-based, adaptive data network
US6584502B1 (en) * 1999-06-29 2003-06-24 Cisco Technology, Inc. Technique for providing automatic event notification of changing network conditions to network elements in an adaptive, feedback-based data network
US6765864B1 (en) 1999-06-29 2004-07-20 Cisco Technology, Inc. Technique for providing dynamic modification of application specific policies in a feedback-based, adaptive data network
US6539427B1 (en) 1999-06-29 2003-03-25 Cisco Technology, Inc. Dynamically adaptive network element in a feedback-based data network
US6459901B1 (en) * 1999-07-01 2002-10-01 At&T Corp. Wireless network resource allocation
US7716077B1 (en) 1999-11-22 2010-05-11 Accenture Global Services Gmbh Scheduling and planning maintenance and service in a network-based supply chain environment
US8032409B1 (en) 1999-11-22 2011-10-04 Accenture Global Services Limited Enhanced visibility during installation management in a network-based supply chain environment
US7124101B1 (en) 1999-11-22 2006-10-17 Accenture Llp Asset tracking in a network-based supply chain environment
US8271336B2 (en) 1999-11-22 2012-09-18 Accenture Global Services Gmbh Increased visibility during order management in a network-based supply chain environment
US7130807B1 (en) * 1999-11-22 2006-10-31 Accenture Llp Technology sharing during demand and supply planning in a network-based supply chain environment
DE10003534A1 (en) 2000-01-27 2001-08-16 Ebbecke Reinhard One-way container for self-heating or -cooling of liquids or solid materials has upper component rotatable with respect to lower component by thread and foil can be destroyed by this rotary movement
GB2361327A (en) * 2000-04-11 2001-10-17 Mitel Corp Automatically executing instruction sets in response to network error logs
GB2357391B (en) * 2000-05-12 2003-09-24 Ericsson Telefon Ab L M Telecommunications network
FI110746B (en) * 2000-05-31 2003-03-14 Nokia Corp Formation of a telecommunications network
US6832086B1 (en) * 2000-06-13 2004-12-14 Motorola, Inc. Manager-directed method for event pressure reduction
DE10035966A1 (en) * 2000-07-24 2002-02-21 Siemens Ag Interference suppression procedure for a higher-level NMC by correlating alarms with results of automatic tests
US6981039B2 (en) * 2000-08-01 2005-12-27 Qwest Communications International, Inc. Fault management in a VDSL network
US7058707B1 (en) 2000-08-01 2006-06-06 Qwest Communications International, Inc. Performance modeling in a VDSL network
JP2002132987A (en) * 2000-10-19 2002-05-10 Nec Corp Centralized maintenance and management system and method utilizing the internet
US7069309B1 (en) * 2000-10-19 2006-06-27 Cisco Technology, Inc. Apparatus and methods for requesting an event notification over a network
WO2002047406A2 (en) * 2000-12-06 2002-06-13 Bellsouth Intellectual Property Corporation Cellular/pcs management system and method
US20040260790A1 (en) * 2000-12-21 2004-12-23 Ge Medical System Global Technology Company, Llc Method and apparatus for remote or collaborative control of an imaging system
US6653434B2 (en) * 2000-12-29 2003-11-25 General Electric Company Process for the production of polycarbonate
EP1374049B1 (en) * 2001-03-26 2016-11-23 Accenture Global Services Limited Broadband communications
EP1395904B1 (en) * 2001-05-22 2016-07-20 Accenture Global Services Limited Broadband communications
WO2003005195A2 (en) * 2001-07-03 2003-01-16 Imagine Broadband Limited Broadband communications
ATE356518T1 (en) * 2001-08-09 2007-03-15 Ascom Schweiz Ag ANALYSIS OF A DATA TRANSMISSION SYSTEM
JP3987699B2 (en) * 2001-09-10 2007-10-10 株式会社エヌ・ティ・ティ・ドコモ Cell shape control method, mobile communication system, and base station and mobile device used in the system
US8977284B2 (en) 2001-10-04 2015-03-10 Traxcell Technologies, LLC Machine for providing a dynamic data base of geographic location information for a plurality of wireless devices and process for making same
US20030149786A1 (en) * 2002-02-06 2003-08-07 Mark Duffy Efficient counter retrieval
US20030217129A1 (en) * 2002-05-15 2003-11-20 Lucent Technologies Inc. Self-organizing intelligent network architecture and methodology
US7502610B2 (en) * 2002-06-28 2009-03-10 Qualcomm Incorporated System and method for application management through threshold events
US7839882B2 (en) * 2002-10-31 2010-11-23 Qualcomm Incorporated Resource allocation in a wireless communication system
EP1560450B1 (en) * 2002-11-04 2017-01-18 ZTE Corporation Wireless telecommunication system and a load control method and apparatus used in such a system
DE10251993B4 (en) 2002-11-06 2012-09-27 Actix Gmbh Method and apparatus for optimizing cellular wireless communication networks
US6954640B2 (en) * 2003-02-17 2005-10-11 Sbc Properties, L.P. Global roaming services for telecommunications systems
US20040168050A1 (en) * 2003-02-24 2004-08-26 Stephane Desrochers System and method for analyzing encrypted packet data
US7398272B2 (en) * 2003-03-24 2008-07-08 Bigfix, Inc. Enterprise console
US7370098B2 (en) * 2003-08-06 2008-05-06 International Business Machines Corporation Autonomic management of autonomic systems
US7092707B2 (en) * 2004-02-13 2006-08-15 Telcordia Technologies, Inc. Service impact analysis and alert handling in telecommunications systems
US20060041534A1 (en) * 2004-05-24 2006-02-23 Atwell Micah E Remote infrastructure management
US7409445B2 (en) * 2004-05-27 2008-08-05 International Business Machines Corporation Method for facilitating monitoring and simultaneously analyzing of network events of multiple hosts via a single network interface
US7551922B2 (en) * 2004-07-08 2009-06-23 Carrier Iq, Inc. Rule based data collection and management in a wireless communications network
US7609650B2 (en) * 2004-07-08 2009-10-27 Carrier Iq, Inc. Collection of data at target wireless devices using data collection profiles
US20060023642A1 (en) * 2004-07-08 2006-02-02 Steve Roskowski Data collection associated with components and services of a wireless communication network
US7302611B2 (en) * 2004-09-13 2007-11-27 Avaya Technology Corp. Distributed expert system for automated problem resolution in a communication system
US20060063521A1 (en) * 2004-09-21 2006-03-23 Benjamin Cheung Method of monitoring wireless network performance
US8155274B2 (en) * 2004-11-12 2012-04-10 Koninklijke Kpn N.V. Method and system for monitoring and improving the quality of interconnecting cabling systems
US8045484B2 (en) * 2005-05-20 2011-10-25 Yaron Menahem Peleg Method for problematic user detection
US7630327B2 (en) * 2005-07-13 2009-12-08 Andrew Llc Method for data maintenance and integration including interpolation
US20070066297A1 (en) * 2005-09-20 2007-03-22 Ghobad Heidari-Bateni Network monitoring system and method
US8161149B2 (en) 2007-03-07 2012-04-17 International Business Machines Corporation Pseudo-agent
US20100332640A1 (en) * 2007-03-07 2010-12-30 Dennis Sidney Goodrow Method and apparatus for unified view
US8495157B2 (en) * 2007-03-07 2013-07-23 International Business Machines Corporation Method and apparatus for distributed policy-based management and computed relevance messaging with remote attributes
US7941136B2 (en) 2007-09-14 2011-05-10 Actix Limited Mobile phone network optimisation systems
GB2461242B (en) 2007-09-14 2010-06-30 Actix Ltd Mobile phone network management systems
JP5284484B2 (en) * 2008-11-17 2013-09-11 テレフオンアクチーボラゲット エル エム エリクソン(パブル) Method and node capable of centrally processing local information
US9042264B2 (en) * 2009-03-30 2015-05-26 Qualcomm Incorporated Automatic configuration of the cell size parameter
US8966110B2 (en) * 2009-09-14 2015-02-24 International Business Machines Corporation Dynamic bandwidth throttling
US8665750B2 (en) * 2010-12-17 2014-03-04 At&T Mobility Ii Llc Methods, devices, and computer program products for auditing and repairing a wireless telecommunications network configuration
US8972361B1 (en) * 2011-06-22 2015-03-03 Emc Corporation Providing system management services
US8725869B1 (en) * 2011-09-30 2014-05-13 Emc Corporation Classifying situations for system management
US8972789B2 (en) * 2012-08-28 2015-03-03 International Business Machines Corporation Diagnostic systems for distributed network
CN104811331B (en) * 2014-01-29 2018-07-03 华为技术有限公司 A kind of visual network O&M method and apparatus
JP6375679B2 (en) * 2014-04-24 2018-08-22 富士通株式会社 Server information management apparatus, server information management program, and server information management method
US20160091913A1 (en) * 2014-09-30 2016-03-31 Cisco Technology, Inc. Smart power management in switches and routers
US10872099B1 (en) * 2017-01-24 2020-12-22 Tintri By Ddn, Inc. Automatic data protection for virtual machines using virtual machine attributes
EP3926891A1 (en) 2020-06-19 2021-12-22 Accenture Global Solutions Limited Intelligent network operation platform for network fault mitigation
US11204824B1 (en) * 2020-06-19 2021-12-21 Accenture Global Solutions Limited Intelligent network operation platform for network fault mitigation

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR2662879B1 (en) * 1990-05-30 1994-03-25 Alcatel Cit CENTRALIZED MAINTENANCE METHOD FOR A WIRELESS TELEPHONE NETWORK.
US5241685A (en) * 1991-03-15 1993-08-31 Telefonaktiebolaget L M Ericsson Load sharing control for a mobile cellular radio system
US5285494A (en) * 1992-07-31 1994-02-08 Pactel Corporation Network management system
US5408218A (en) * 1993-03-19 1995-04-18 Telefonaktiebolaget L M Ericsson Model based alarm coordination
US5504938A (en) * 1994-05-02 1996-04-02 Motorola, Inc. Method and apparatus for varying apparent cell size in a cellular communication system
US5713075A (en) * 1995-11-30 1998-01-27 Amsc Subsidiary Corporation Network engineering/systems engineering system for mobile satellite communication system
US5870676A (en) * 1996-02-16 1999-02-09 Hughes Electronics Corporation Method and apparatus for monitoring killer channels in a cellular system
US5726979A (en) * 1996-02-22 1998-03-10 Mci Corporation Network management system
US5845062A (en) * 1996-06-25 1998-12-01 Mci Communications Corporation System and method for monitoring network elements organized in data communication channel groups with craft interface ports
US6012152A (en) * 1996-11-27 2000-01-04 Telefonaktiebolaget Lm Ericsson (Publ) Software fault management system

Also Published As

Publication number Publication date
US6233449B1 (en) 2001-05-15
AU5767099A (en) 2000-03-14
WO2000011884A1 (en) 2000-03-02
AR021197A1 (en) 2002-07-03
AU758719B2 (en) 2003-03-27
BR9913166A (en) 2001-05-15

Similar Documents

Publication Publication Date Title
US6233449B1 (en) Operation and maintenance control point and method of managing a self-engineering telecommunications network
Barco et al. A unified framework for self-healing in wireless networks
RU2538766C2 (en) Method and system for receiving information via radio access network in cellular communication
Mueller et al. A cell outage detection algorithm using neighbor cell list reports
US20050064820A1 (en) Network analyzing method and apparatus for optimal performance of network, and a recording medium having programs to conduct said method
CN111242225A (en) Fault detection and diagnosis method based on convolutional neural network
WO2001045276A2 (en) Method and apparatus for detecting base station transceivers&#39; malfunctions
JP2015508948A (en) Self-organizing network coordination method, apparatus, and system
CN102017689A (en) A method of operating wireless communications network and base station for use in wireless communication network
KR20160147957A (en) Verification in self-organizing networks
CN107027138B (en) A kind of room divides hidden failure to check method and device
CN102695218B (en) Mode identification-based switching self-optimizing method
KR101436070B1 (en) Measurement reporting in communications systems
Soldani et al. Self-optimizing neighbor cell list for UTRA FDD networks using detected set reporting
Puttonen et al. Coverage optimization for minimization of drive tests in LTE with extended RLF reporting
Asghar et al. Correlation-based cell degradation detection for operational fault detection in cellular wireless base-stations
CN103517308A (en) Cell interrupt detecting method based on neighbor cell reference signal receiving power list
Kaada et al. Resilience analysis and quantification method for 5G-Radio Access Networks
WO2022017626A1 (en) Trajectory based performance monitoring in a wireless communication network
Manzanilla-Salazar et al. ENodeB failure detection from aggregated performance KPIs in smart-city LTE infrastructures
CN108668297B (en) Method, device and system for adjusting wireless switching timer
Khatib et al. Modelling LTE solved troubleshooting cases
US7184760B2 (en) Air interface management in mobile communications
KR100447698B1 (en) Apparatus for Analyzing for Optimizing Network Performance
Khanafer et al. A bayesian approach for automated troubleshooting for UMTS networks

Legal Events

Date Code Title Description
EEER Examination request
FZDE Discontinued
FZDE Discontinued

Effective date: 20090227