Communicating a network event

[0001] The invention relates to the field of telecommunications networks and the handling of events in a communication network. In particular, the invention relates to a method for detecting the use of an automatic function, an agent device, a method for detecting in the management device the use of an automatic function, a management device, a computer readable medium for controlling at least one of the methods, a data structure, a recording medium and the use of an object in accordance with the 3GPP TS standard 32,622 to store the type of automatic function used.

Background of the Invention [0002] Automatic network functions may enable the implementation of the tasks of a network management system in a communication network. Automatic functions can enable self-organization of network functionalities such as self-configuration, self-optimization, self-healing and / or automated software management. Many of the automated functionalities implemented in the network can be called "self-X" functionalities. Self-X functionalities may allow to reduce OPEX ( Operational Expenditure) for network maintenance and maintenance (OAM) Operation Administration Maintenance), in particular for telecommunications or cellular networks. Network elements that support self-X functionality can perform tasks that are usually performed by management applications or human OAM operators.

[0003] However, self-X functionalities can also reduce network transparency for a network operator. The operator may not get information about network activities because the network can be organized using self-X functionality or it can be managed by self-X functionality. Thus, the operator can be kept in "darkness" in relation to what may actually happen in the network or in relation to what happened when self-X functionality could be applied or performed. The network operator can only receive indications that the data on the network may have changed. In the example, the network operator may receive indications that the data that can be reflected in a database such as MIB ( Management Information Base) in the network management center (NMC) Network Management Center) can be created, changed or deleted. Generating or creating a mirror copy of data can only provide raw data without transmitting any content or impact of the functions performed. Thus, the operator or network management system (NMS) Network Management System), which should know the status of the network, may be better or worse informed about the fact that something may have happened on the network, but not about what happened.

[0004] 3GPP (3rd Generation Partnership Project) TS 32.302, "3rd Generation Partnership Project, Technical Specification Group Services and System Aspects,

-2Telecommunication Management, Configuration Management (CM), Notification Integration Reference Point (IRP), Information Service (IS) ", Version 8, V8.0.0, 2008-12, can specify the interface through which IRPManager can subscribe to IRPAgent for receiving notification.

[0005] 3GPP TS 32.662, "3rd Generation Partnership Project, Technical Specification Group Services and System Aspects, Telecommunication Management, Configuration Management (CM), Kernel CM Information Service (IS) ", Version 8, v8.0.0, 2008-16 may specify Integration Reference Point (IRP) through which "IRPAgent", for example, Element Manager (EM) or Network Element (NE) can communicate configuration management information to one or more "IRPManagers", for example, network managers.

[0006] 3GPP TS 32.663, "3rd Generation Partnership Project, Technical Specification Group Services and System Aspects, Telecommunication Management, Configuration Management (CM), Kernel CM Integration Reference Point (IRP)", Common Object Request Broker Architecture (CORBA), Solution Set (SS) ", Version 8, V8.0.0, 2008-12, may specify CM IRP: IS Kernel mapping to the detailed protocol data necessary to implement this IRP into the CORBA / IDL environment Interface Definition Language).

[0007] 3GPP TS 32.665, "3rd Generation Partnership Project, Technical Specification Group Services and System Aspects, Telecommunication Management, Configuration Management (CM), Kernel CM Integration Reference Point (IRP), eXtensible Markup Language (XML) definitions", Version 8, V8.0.0, 2008-12 may specify XML definitions for the Kernel CM Integration Reference Point (IRP) because it can be used in the Itf-N interface.

[0008] 3GPP TS 32.502, "3rd Generation Partnership Project, Technical Specification Group Services and System Aspects, Telecommunication Management, SelfConfiguration of Network Element Integration Reference Point (IRP), Information Service (IS)", Version 8, V8.0.0, 2008-12 may specify the Information Service (IS) part for the SelfConfiguration IRP (SCIRP).

[0009] In 3GPP TS 32.503, "3rd Generation Partnership Project, Technical Specification Group Services and System Aspects, Telecommunication Management, SelfConfiguration of Network Element Integration Reference Point (IRP), Common Object Request Broker Architecture (CORBA) Solution Set (SS) ", Version 8, v8.0.0, 2008-12, a set of CORBA solutions for IRP software management for IRP can be described, whose semantics can be specified in the information service for managing IRP software.

[0010] 3GPP TS 32.532, "3rd Generation Partnership Project, Technical Specification Group Services and System Aspects, Telecommunication Management, Software Management Integration Reference Point (IRP), Information Service (IS)", Version 8, V8.0.0,

-32008-12, may describe an information service for managing the IRP software interface.

[0011] 3GPP TS 32.533, "3rd Generation Partnership Project, Technical Specification Group Services and System Aspects, Telecommunication Management, Software Management Integration Reference Point (IRP), Common Object Request Broker Architecture (CORBA) Solution Set (SS)", Version 8, V8.0.0, 2008-12, can describe a set of CORBA IRP software management solutions for which semantics can be specified in the IRP software management service.

[0012] Document WO 2004/004384 A1 may describe a method and apparatus for reallocation of circuit switched channels that are associated with a gate node. A method of reallocating channels, including automatically monitoring one or more sources 31, 41, 51 information on communication performance and based on data received from sources, automatically determining whether the condition for triggering reallocation is met, and if the condition for triggering reallocation is met, automatic calculation of reassignment of channels with switched circuits between control units.

[0013] Document SA5-080990 contains an earlier working version of TS 32.501 V0.1.2, which aims to describe the requirements for self-establishment of base stations (eNodeBs) for LTE networks. An earlier version document may describe the requirement that there must be a function that is able to monitor the self-configuration method and allow the operator to control the implementation of the self-configuration method.

[0014] Document US 2006/248407 A1 may describe a method of rapid fault isolation and resolution in a communication network in which an alarm message originating from the communication network is received on the management platform and a reason analysis is performed on the management platform to determine the most probable source of failure, and a derivative alarm is generated, indicating equipment damage, and further related network information is stored with a derivative alarm. If the derived alarm matches the predefined sequence of actions associated with handling the derived alarm, this predefined sequence of actions is triggered to process the error, report the associated error and acknowledge the error on the operator's display.

[0015] There may be a need to provide more efficient network management.

Summary of the Invention [0016] According to an embodiment of the invention, a method for detecting the use of an automatic function, an agent device, a computer readable medium, a program element, a data structure and a recording medium may be provided.

[0017] According to an embodiment of the invention, a method of detecting the use of an automatic function may be provided. In the example, the method may include detecting the execution of an automatic function in a communication network, determining the type of the automatic function and storing information representing the type of the automatic function in a predefined

- a storage area of ​​the recording medium or data structure. In the example, the end of the automatic function can be detected.

[0018] According to a further embodiment of the invention, an agent device may be provided comprising a detection device, a type determining device and a recording device. The detection device may be adapted to detect the automatic function in the communication network. In the example, the type determining device may be adapted to determine the type of automatic function performed and the recording device may be adapted to record information representing the type of automatic function in a predefined storage area of ​​the recording medium.

[0019] In the example, saving information representing the type of automatic function may include creating an object, deleting the object and / or changing the object. The object in the example can be a managed object. In the next example, saving the automatic function type may include using the notifyObjectCreation method, applying the notifyObjectDeletion method, and / or using the notifyAttributeValueChange method.

[0020] The concept of creating, deleting and / or changing managed objects may enable communication between the agent device and the management device. In other words, the agent device may write, delete and / or change values ​​in predefined storage areas of the recording medium. Thus, the management device may have access to predefined storage areas to read the corresponding values. In order to inform the management device about the creation, deletion and / or change of managed objects, the agent's device may use an appropriate method and / or message, e.g. way notifyObjectCreation, way notifyObjectDeletion and / or notifyAttributeValueChange.

[0021] Creating a managed object may include structuring an unstructured recording medium with an address scheme, e.g. according to the object definition. Having an agreed object model between the agent's device and the management device can enable the agent's device to communicate with the management device by accessing the appropriate parameter. Thus, in the example, the addressing structure or address medium of the recording medium can generally exist only when the managed object exists.

[0022] According to yet another example, the method for detecting in the management device the use of an automatic function in a communication network may include read information representing the type of automatic function of the predefined recording medium storage area and determining the use of the automatic function using the read information.

[0023] In an example, a method of detecting the use of an automatic function or detecting the use of an automatic function may include detecting the execution of the automatic function e.g. by receiving a corresponding message. The message or method corresponding to the message may be a list of parameters or an interface. The interface can be an Itf-N interface.

[0024] According to a further example, the management device may comprise a reading device for reading information, which information may represent the type of automatic function performed. The information can be read from a predefined storage area of ​​the recording medium. In addition, the management device may include a determining device that may be adapted to determine the use of an automatic function using information that may have been read. Thus, the information read may provide information to the determining device, which information may allow determining whether an automatic function may have been used or performed.

[0025] In an example, the reading device may be adapted to detect the performance of an automatic function, e.g. by receiving a corresponding message, e.g. a notification message or an alarm message.

[0026] According to yet another embodiment of the invention, a medium readable by a computer comprising a program code may be provided, which program code, when executed on the processor, may be adapted to perform at least one method according to the invention for detecting the use of an automatic function in a communication network and how to detect in the management device the use of the automatic function in a communication network.

[0027] According to a further embodiment of the invention, a data structure may be provided which may be based on the 3GPP TS 32.662 standard. The data structure may contain a parameter for storing in the network the type of automatic function performed, and the parameter may be addressable by an address scheme based on the object definition. The object definition may allow the reading device to be controlled to enable the reading device to find information related to a parameter stored in the data structure, and in particular on a recording medium described or structured by the data structure. In the example, the data structure can be an object model.

According to a further embodiment of the invention, a recording medium may be provided, wherein the recording medium may comprise a storage area, e.g. register for storing the type of automatic function performed. The automatic function may have been performed on the network and may be the reason for the changed network configuration. The storage area can be addressable by an address scheme based on the object or object model definition. In other words, the object definition may allow addressing of the physical storage area so that the required parameter can be accessed. Thus, the object model may allow the reading device and / or recording device to be located in the respective storage area of ​​the recording medium. The storage area can be a storage unit in physical memory.

[0029] Examples of a recording medium and / or a computer readable medium may be a floppy disk, USB mass storage device (Universal Serial Bus), RAM (Random Access Memory), ROM (Read Only Memory) or EPROM ( Erasable Programmable Read Only Memory). The medium read by the computer may also be a data communication network, e.g. the Internet, which may allow the program code to be downloaded.

[0030] According to another embodiment of the invention, a program element may be provided, which program element, during execution by the processor may be adapted to perform at least one of the methods of the invention for detecting the use of an automatic function in a communication network and a detection method in device managing the use of the automatic function in the communication network.

[0031] In a self-managed network, the performance of a network management task may be triggered by an automatic function or automatic functionality, in particular by self-X functionality in the network. This self-X functionality, automatic function or automatic functionality may include reorganization and reconfiguration of network elements to adapt the network to the changed situation. Performance of self-X functionality may include creation of an appropriate managed object.

[0032] The network configuration change can occur for various reasons. The reason may be the configuration reason, the optimization reason, the reason for the repair, or the reason for automatic software management. In other words, the network itself can respond to changed conditions, such as added network nodes, software changes, failures, and the network can try to cope with the changed situation by itself. Such automated behavior or self-X functionality can reduce the burden on the network operator who may be responsible for maintaining the network.

[0033] In a self-managed network or in a network with self-X functionalities, there may be a control circuit, closed-loop control or open-loop control to regulate the control of self-X functionality, respectively. A self-managed network, in particular a control circuit, may include a measuring device that can be adapted to measure additional network parameters. A self-managed network may also contain predefined messages exchanged between network elements (NEs), where self-X functionalities can be distributed to some locally separated NEs. This can be called distributed or decentralized architecture. Messages can be exchanged between NEs, in particular NEs with self-X functionalities, and messages can bypass the interface (e.g. Itf-N) to the management system. Thus, the management system may not generally be involved in performing self-X functionality.

[0034] Measurements can be made in real time and / or statistically. In order to collect statistical data, data such as measured values ​​can be collected at a fixed time and evaluated. Data can be used to determine the progression of curves related to resource use or to determine statistics on resource use. Data can be collected for a period of one day, week or month. Measurement values ​​are generated by sampling a given value, e.g. applying the resource at regular intervals. The value can be sampled over a 15 minute grid.

[0035] In the self-X network control circuit, there may be a device that can be adapted to set a range of values ​​in which the range of values ​​of the self-X function may decide on the selection of a predefined parameter. Control devices can

Also affect the time behavior of self-X within a predefined range of parameters.

[0036] However, support for reconfiguration over the network or responding to failure scenarios over the network may leave the operator unaware of what is happening in the network. Thus, the operator may not have all the information required to identify the actual network status. Thus, self-X functionalities may make the network opaque to the network operator. It may not be possible to identify which changes in the network have been triggered by self-X functionality. Thus, the network operator may see that something has happened inside the network, but may not receive information about the cause, root cause or reason why something may have happened on the network. In particular, the network operator may not know why self-X functionality may have been performed. In other words, the operator may see that the automatic function may have been performed, but may not be able to find out the reason for performing or using the function.

[0037] The same may apply to configuration management, network management or network management system (NMS), which can also only see changed network configuration compared to the initial network configuration. However, NMS may not know the reason for the changed configuration and may believe that the changed configuration is the result of a malfunctioning network. In this case, NMS may try to repair or reconfigure the network configuration to achieve the initial network configuration. In the example, NMS and self-X may work against each other.

[0038] Therefore, indication of the reason for the changes may allow the operator or network management system to understand that the changed network configuration may result from self-X functionality. This allows NMS to ignore the changed configuration.

[0039] According to an example, the automatic function may exclude the use of a network management system. A network, such as a communication network or mobile communication network, may not include a network management system for reconfiguring the network in the event of a changed situation.

[0040] The network itself, i.e. the network elements themselves or the self-healing server may attempt to reconfigure the network without involving a network management system. Thus, the network management system can support network management objects without caring about the reasons for the changes that may occur within the network. Thus, on the one hand, the load on the network management system can be reduced, but on the other hand, the network can become opaque to the network management system. Automatic functions or self-X functions can be performed without the participation of the network management system.

[0041] According to yet another embodiment of the invention, the type of automatic function may be at least one type of self-X function selected from the group of self-X function types, consisting of self-configuration, self-optimization of interference coordination, automatic management of a list of neighboring cells, self-optimization of load balancing , self-optimization of interference coordination, self-optimization of the direct access channel (RACH, Random Accsess Channel), self-optimizing bandwidth,

- 8 self-optimization of coverage, self-management of software and self-healing.

[0042] In the example, the interference coordination may be adapted to reduce the effect of interference between at least two adjacent cells.

In another example, automatic management of a neighbor cell list (ANR) may be adapted to update the list of corresponding neighbor cells. The list can be automatically updated by using the appropriate self-X function. For example, when the installation and launch of a new base station can be detected, the function of automatically managing the list of adjacent cells can update the appropriate list, database, repository or inventory.

[0043] In the example, the self-configuration may include reconfiguring the network to environmental conditions that may have changed.

[0044] In another example, self-optimization of interference coordination (IC) may be provided. Self-optimization of interference coordination may include adapting interference between UE (User Equipment) or MS (Mobile Stations) connections and base stations (BS) to a balanced situation.

[0045] In another example, load balancing may include moving a user to another base station or handing a user, mobile station or user equipment to another base station (handover) so that connections in the network can be balanced.

[0046] In the example, self-optimization of the handoff parameter may also include handing over user equipment from one base station to another. In the example, self-optimization of the forwarding parameter may include establishing conditions for triggering forwarding. This may include establishing a threshold for initiating an MS transfer from one base station to another base station.

[0047] In a further example, the automatic function may include direct access channel optimization (RACH).

In another example, RACH may be a channel used by user equipment, such as a cellular telephone or mobile station, to contact the base station. In the event that the number of requests for connections may be higher than the available resources or channels, not all requests can be met. On the other hand, providing too many resources or channels can mean losing too much bandwidth for actually useful data channels using the same frequency. Thus, RACH optimization may include finding a compromise between the available channels and the used bandwidth.

[0048] In a further example, the automatic function may include bandwidth optimization and / or coverage optimization.

[0049] In yet another example, the automatic function may include software management such as release control or verification of the correct software version.

[0050] In another example, the automatic function may include self-healing, which may allow it to respond to an emergency.

[0051] According to another embodiment of the invention, the recording medium storage area, parameter or data structure may be addressed by the sourceIndicator parameter of at least one method and / or message selected from the group of methods and / or messages according to 3GPP TS 32.662, group of methods and / or messages can consist of the notifyObjectCreation method, the notifyObjectDeletion method, and the notifyAttributeValueChange method. In the example, the method may be a parameter list and / or an interface description containing the parameter list. An appropriate storage area may be adapted to store the reason for the self-X function. In the example, the reason can be represented by a bit pattern.

[0052] In an example, an object or managed object may represent stored data or may assist in addressing stored data. The object may allow access to stored data on a recording medium or in memory. An object may allow defining an addressing scheme for a recording medium, a computer readable medium, for a storage area, or for a memory that allows finding information that may have been placed in a storage area.

[0053] According to an embodiment of the invention, the method for detecting the use of an automatic function in a network may include storing information that may allow a more detailed determination of the automatic function used. Such detailed information may be stored in the next predefined storage area of ​​the addressable recording medium by the object.

[0054] In the example, an additional storage area for additional information may allow a more detailed description of the cause, root cause or reason that may have made it necessary to use or perform the appropriate self-X functionality. The additional storage area may allow providing more detailed information to the network management system to notify the network management system of the reasons for the automatic function performed.

[0055] According to another embodiment of the invention, the next predefined storage area may be another parameter and may correspond to the next parameter of at least one method and / or message from the group of methods and / or messages according to the 3GPP TS 32.662 standard, consisting of the notifyObjectCreation method, how to notifyObjectDeletion and how to notifyAttributeValueChange.

In another example, the method may be a method according to object architecture.

[0056] According to yet another embodiment of the invention, the method may further comprise communicating information showing the type of function performed

Automatic between the agent device and the management device and / or between the agent device and the self-X server.

In another example, information may be communicated based on a subscription. Communication of detailed information may enable notification of the relevant management device, NMS and / or self-X server about the behavior inside the network and about the stages that may have been carried out on the network and in addition to the reason for which the appropriate stages may have been carried out. This can make the behavior inside the network more transparent to the management device, e.g. for NMS or for self-X server. Thus, information may be provided about the cause that may have triggered the network reconfiguration or execution of the automatic function in the network. Thus, a communication relationship can be established between the network and administrative instances, such as network management or a selfX server, to explain the reasons for the actual network configuration.

[0057] In the example, NMS may have an initial network configuration and may be surprised if the initial network configuration can be different or different from the actual network configuration. To clarify the reasons that could lead to this difference, you can establish a communication relationship with the network, in particular with an agent inside the network. In the example, the manager e.g. IRPManager ( Integration Reference Point Manager) can establish a communication relationship with an agent within the network, e.g. IRPAgent ( Integration Reference Point Agent). The communication between the agent and the manager can use an established or subscribed interface, for example an Itf-N interface. In the example, the Itf-N interface may be the interface between the agent device and the management device.

[0058] According to another example of the invention, the agent device, e.g. IRPAgent can be included or integrated in at least one network device selected from the group of network devices consisting of the Element Management System (called Element Management System, EM), Network Element (NE), self-X server or self-X client, BTS (ang. Base Transceiver Station, Base Transceiver Station), RNC Radio Network Controller, NodeB and eNodeB. In the example eNodeB it can be the macro eNodeB, home NodeB or femto eNodeB.

[0059] In the example, the agent and / or manager may be based on at least one standard selected from the group of standards consisting of GSM (Global System for Mobile communication), UMTS (Universal Mobile Telecommunication System) and LTE ( Long Term Evolution). In particular, the agent and / or manager may use objects that meet appropriate standards.

[0060] According to another embodiment of the invention, a program element may be provided, which program element, during execution by the processor, is adapted to perform at least one of the methods for detecting the use of an automatic function in a communication network and a method of detecting the use of an automatic function in a management device in the communication network.

In other words, after the automatic function has been completed, information about the reason or reason for the automatic configuration can be provided by the network for

- 11 transparent notification of the management system or any other instance concerned about behavior within the network.

The invention is further defined by the appended claims.

It should also be noted that embodiments of the invention and aspects of the invention have been described with reference to various objects. In particular, some embodiments have been described with reference to the claims regarding types of devices while other embodiments have been described with reference to the claims regarding types of methods. However, those skilled in the art deduce from the above and the following description that, unless otherwise specified, in addition to any connection between the features of one type of object, any connection between the features of various items, in particular between the features of the patent claims and features according to the method claims.

[0061] These and other aspects of the invention will be better understood and explained with reference to the embodiments described below.

[0062] Embodiments of the invention will be described in more detail below with reference to the following figures.

Brief description of the figures [0063]

Fig. 1 shows a block diagram of an agent device according to an embodiment of the invention.

Fig. 2 shows a block diagram of a management device according to an embodiment of the invention.

Figures 3a to 3c show the various stages of the self-X method according to an embodiment of the invention.

Fig. 4 is a block diagram of a network management architecture according to an embodiment of the invention.

Fig. 5 shows a message flow network for exchanging object information according to an embodiment of the invention.

Fig. 6 shows a flow network of a method for detecting the use of an automatic function according to an embodiment of the invention.

Fig. 7 shows a flow network of a method for detecting in a management device that an automatic function has been used in a communication network.

Detailed description [0064] The illustration in the figures is schematic. In different figures, similar or identical elements have the same reference numerals.

[0065] Fig. 1 is a block diagram of an agent device according to an embodiment of the invention.

[0066] The agent device 100 includes a detection device 104, a type determining device 105 and a recording device 108. The detection device contacts the network 101 via interfaces 109 and 110. In the example, the agent device is contained in a network element, e.g. network node or base station of network 101. As symbolically shown by means of the dotted line 111, the detection device 104 may detect the performance or use of an automatic function or a self-X function in the network 101. In the example, the detection device detects the end of the automatic function. For example, the detection device communicates with the self-X server 102, which can initiate self-X functionality in the network and notify the agent device 100 when the self-X function has been performed. In other words, the detection device is adapted to monitor network 101 for changes.

[0067] The agent device 100 may be part of the network 101. Through the network interfaces 109, 110, the agent device 100 or the network node 100 may be in contact with the communication network 101.

[0068] In a case in which the detection device 104 detects an auto-configuration or reconfiguration in the network 101, the detection device 104 reports such a change by connecting 112 to the type determining device 105. The type determination device is responsible for determining the type of automatic function that has been performed. In other words, the type determination device detects the self-X method indication as the reason for the data change in the network. Data change can be detected when a parameter in the network element has been changed.

[0069] Thus, the type determination device may allow identifying which changes in the network have been triggered by self-X functionalities. The type determining device can also be adapted to determine the type of self-X functionality used and more details about the reasons for performing self-X functionality. Examples of different types of self-X functionality are self-configuration, self-optimization, self-healing and automatic software management, etc. In other words, as soon as the network itself becomes active with respect to the network configuration, activities are recorded in the agent's device.

[0070] The type determining device 105 uses a recording device 108 to record information representing the type of automatic function, the type of the corresponding self-X functionality detected, or the reason for performing the automatic function in the predefined storage area of ​​the recording medium 103. In the example, the recording medium may be memory, RAM or EPROM, which may be adapted to receive information from a type determining device.

[0071] The recording device 108 may be controlled by an addressing scheme, which may be defined as an object model, to find a suitable predefined location or location of the storage medium of the recording medium. Fig. 1 shows an example of a predefined storage area 113. In other words,

-13 object definition can be used to place a recording device in the storage area to record the type of detected self-X functionality that was made in network 101. The management device can use the same object model to control the reading device to the appropriate storage area for reading the type or reason self-X function completed.

[0072] The recording device and / or reading device may be adapted to access the storage area next to the storage area for storing additional text information or correlated notifications, i.e. a set of notifications that are correlated with the subject notification.

[0073] Bidirectional link 114 connects recording medium 103 to communication device 106, which communication device 106 is adapted to communicate information representing the type of automatic function performed between the agent device 100 and the management device (not shown in Fig. 1) and / or between the agent device 100 and the self-X server 102. In the example, the communication device 106 may include a reading device for accessing the predefined storage area 103 of the recording medium 103. For controlling or positioning the reading device to gain access to the predefined storage area 113, the communication device 106 may use the same object model as the recording device 105. In the example, the communication device, in particular the integrated reading device of the communication device 106 may be controlled by a management device that may request information detected by the detection device 104. For communication with the management device or with the NMS, the communication device 106 uses a two-way network connection 115 that is connected to the communication network 107.

[0074] Fig. 2 is a block diagram of a management device 200 according to an embodiment of the invention.

[0075] The management device 200 or NMS 200 includes a reading device 201. The reading device 201 of the management device 200 in the example may control the communication device 106 in particular the integrated reading device of the agent device 100 (not shown in figure 2).

[0076] In another example, the reading device 201 is adapted to read information representing the type of automatic function performed from a predefined storage area of ​​the recording medium contained in the agent device 100. For reading the recording medium (not shown in Fig. 2), the management device 200 may establish a connection with the agent device 100 via the two-way network connection 202 and via the communication network 107.

[0077] In the example, the communication connection 115, 202 may be established via the Itf-N interface. In other words, via the Itf-N network interface 202, 115 or the 202, 115 Itf-N interface, the management device 200 may establish a connection to the agent device 100. In other words, the management device 200 can

-14subscribe to the agent 100, event manager, or event creating instance. In the example, the management device is IRPManager 200 and the agent device is IRPAgent 100.

[0078] The reading device 201 may determine the type of automatic function performed in the network 101 (not shown in Figure 2) and may forward the collected information to the determining device 203. The determining device 203 is adapted to determine whether an automatic function has been used or performed in the network 101.

[0079] To determine whether an automatic function has been used in the network 101, the determining device 204 uses information read by the reading device 201. In other words, the determining device may access the recording media 103 of the agent device 100. Thus, the determining device can be notified of the type of self-X function that has been used in network 101. The determining device 203 is adapted to determine whether the automatic function was performed in the network 101 and / or what type of function was performed and / or what reason was the reason for the automatic function.

[0080] The information determined by the determining device 203 may be communicated via communication port 204, common port 204 or management port 204 to another management system 200a or to user terminal 205. Thus, either the management system 200a or the operator can be informed about the type of self-X functionality that has been made on the network 101. Thus, an indication of the self-X method as a reason for the change of data in the network 101 can be communicated to the user terminal 205 or the NMS system 200a. This information can make it transparent what is happening on the 101 network. Thus, information on operations or changes in network 101 can be provided via the communication interface 204.

[0081] In other words, the network operator using the user terminal 205 is able to identify which changes in its network have been triggered by the self-X functions.

[0082] Table 1 illustrates an example of a data structure that can be used to address a predefined storage area of ​​a recording medium 103. Tab.1 shows the notifyObjectCreation method. This notifyObjectCreation method is optional and may be based on the 3GPP TS 32.662 standard. IRPAgent 100 notifies IRPManager 200 that a new managed object has been created using the notifyObjectCreation method. IRPManager can be subscribed via link 202, 115 and via network 107 to IRPAgent. Thus, information or notification is sent from IRPAgent to IRPManager 200 as soon as the recording device 108 writes the automatic function type or the detected self-X function type to the recording medium 103. The self-X function type may be associated with the reason for the self-X function. The notification header can be a link to technical standard parameters.

[0083] The creation of a new managed object can only be communicated with IRPAgent 100 to IRPManager 200 if the new object meets the filter limit expressed in the IRPManagers subscription operation that was used to establish the communication connection between IRPAgent 100 and IRPManager 200. Table 1 presents parameters input

-15 notifyObjectCreation method, notifyObjectCreation notification or notifyObjectCreation message. Performing the appropriate method (e.g. notifyObjectCreation, notifyObjectDeletion, notifyAttributeValueChange) with the appropriate input parameters causes these parameters to be sent as notifications to the manager.

[0084] Table 1 contains four columns. The first column shows the name of the parameter, the second column shows the qualifier, the third column shows the matching information, and the fourth column shows the comment. Thus, the parameters or description of the object presented in tab. 1 may correspond to the addressing scheme of the recording medium 103. The predefined storage area 103 may correspond to an appropriate parameter as indicated in column 1 of Table 1.

[0085] The matching information may be a filtering parameter that may allow determining which messages or notifications should be visible to the NMS 200, 200a or operator 205. This matching mechanism may enable determining which information can be recorded in an online processing log or off-line. The matching information may be the data type for the corresponding filter.

[0086] For example, notifyObjectCreation contains an object class that can carry the name of the entity's managed class.

[0087] In other words, the notificationObjectCreation or notifyObjectCreation method as well as notifyObjectDeletion and / or notifyAttributeValueChange can describe which parameter can be notified when an object can be created, deleted or when the corresponding attributes can be changed. This may apply to the IRP notification described in the 3GPP TS 32.302 standard. These methods can be predefined subscriptions to the event creation mechanism.

[0088] Furthermore, notifyObjectCreation includes an instance parameter of the notificationId object, eventTime, systemDN, notificationType, correlatedNotifications.

[0089] The optional correlatedNotifications parameter can be used to display further notifications that originate from the same event. This origin information can be used in the self-X function.

Tab. 1

<td>Name parameter</td><td>Qualifier</td><td>Matching information</td><td>Comment</td>

<td>objectClass</td><td>M, Y</td><td>ManagedEntity.objectClass</td><td>Notification header. It should be named ManagedEntity.</td>

<td>objectInstance</td><td>M, Y</td><td>ManagedEntity.objectInstance</td><td>Heading notice.</td>

<td>Name parameter</td><td>Qualifier</td><td>Matching information</td><td>Comment</td>

<td></td><td></td><td></td><td>Should carry DN for ManagedEntity.</td>

<td>notification Id</td><td>M, N</td><td>-</td><td>Heading notifications</td>

<td>EVENTTIME</td><td>M, Y</td><td></td><td>Heading notice. He should carry time creation ManagedEntity.</td>

<td>systemDN</td><td>C, Y</td><td>-</td><td>Heading notifications</td>

<td>notification^Typ^e</td><td>M, Y</td><td>Mapping to notificationType</td><td>Heading notice.</td>

<td>correlatedNo tifications</td><td>Oh</td><td></td><td>Notification set correlated with item notification.</td>

<td>additionalText</td><td>Oh</td><td></td><td>May contain further information in the text regarding creation MO.</td>

<td rowspan="2">sourceIndicator</td><td rowspan="2">Oh</td><td rowspan="2">ENUM (Resource_operation, Management_operation, Self_configuration, Self_optimization_IC, ANR List Management, Self_opt_load balancing, Self_opt_HO_parameters, Self_opt_IC, Self_opt_RACH, Self_opt_Capacity, Self_opt_Coverage, Self_optimization, Self_healing, Unknown)</td><td>This parameter, when present, indicates source or reason for the operation that led to generate this notice. It can have one of the following values:</td>

<td>1. resource operation: Notification was generated in response to</td>

<td>Name parameter</td><td>Qualifier</td><td>Matching information</td><td>Comment</td>

<td></td><td></td><td></td><td>internal action resource; 2. management action: Notification was generated in response to management operation applied to object boundary managed outside managed facility; 3. self-configuration: Notification was generated in the result of the self-configuration method. 4. self opt_IC: Notification was generated in result of the method mainly about interference coordination. 5. self opt_load_balancing: Notification was generated as a result of method mainly about self-optimization balancing load</td>

<td>Name parameter</td><td>Qualifier</td><td>Matching information</td><td>Comment</td>

<td></td><td></td><td></td><td>6. self opt_HO_parameters: Notification was generated as a result of method mainly about self-optimization parameters transfer. 7. self opt_RACH: Notification left generated as a result of method mainly about RACH self-optimization. 8. self opt_capacity: Notification left generated as a result of method mainly about self-optimization of bandwidth. 9. self opt_coverage: Notification left generated as a result of method mainly about self-optimization of coverage. 10. self optimization: Notification has been generated in</td>

<td>Name parameter</td><td>Qualifier</td><td>Matching information</td><td>Comment</td>

<td></td><td></td><td></td><td>result of the method mainly about self-optimization (if allocation cannot be made for the above-mentioned purposes) 11. self-healing: Notification was generated as a result of self-healing method. 12. unknown: No. you can specify sources operations.</td>

<td>attributeList</td><td>Oh</td><td>SEQUENCE LIST &lt;AttributeName, attributeValue&gt;</td><td>Attributes (pairs name / value) created MO.</td>

[0090] In a sequence beginning with objectClass, notifyObjectCreation includes the additionalText parameter following the correlationNotifications parameter. This additionalText parameter can be an optional parameter.

[0091] In tables O can be used to indicate an optional parameter, M can be used for mandatory parameters.

[0092] N means that the parameter cannot be used for a filtering operation, and Y means that the parameter can be used for a filtering operation.

[0093] The AdditionalText parameter or additional text parameter may contain additional information in the text about the creation of the MO (Managed Object).

[0094] The managed object is a representation of the actual object in the database. The person may be presented in the operator's database as a subscriber's object. Physical eNodeB (eNB) can be presented by ManagedObject (MO) eNBfunction.

[0095] The additional text parameter may be used for any additional text that cannot be defined by the standard.

[0096] The additional text parameter may for example contain an identifier that allows determining which self-X method has triggered the event. For example, creating an object, deleting an object, and changing the attribute value can be an event.

[0097] Furthermore, the notifyObjectCreation method includes a sourceIndicator parameter. It is an optional parameter that can contain matching information or a value selected from Resource_operation, Management_operation, Self_configuration, Self_optimization_IC, ANR_list_management, Self_opt_load_balancing, Self_opt_HO_parameters, Self_opt_IC, Self_opt_RACH, Self_opt_capacity, Self_opt_control,

[0098] The sourceIndicator parameter or source pointer parameter, when present, indicates the source of the operation that led to the generation of the corresponding notification (e.g. notifyObjectCreation). The source indicator indicates the type of automatic function or selfX function that has been performed on the network.

[0099] The values ​​of resource_operation, management_operation, unknown can be extended or extended with the values ​​of automatic functions, such as self-configuration values, self-optimization, self-healing, automatic software management, Self_configuration, Self_optimization_IC, ANR_list_management, Self_opt_load_balancing, Self_opt_HO_parameters, Self_opt_opt_opt, Self_opt_opt, self_optimization, Self_healing. Other names for other automatic functions may also be included in the source indicator. Thus, the source indicator may indicate the source of self-X functionality.

[0100] SourceIndicator may have, for example, the value of Resource_operation. The source pointer is Resource_operation if a notification was generated in response to an internal resource operation.

[0101] SourceIndicator may have a value of Management_operation if a notification was generated in response to a management operation applied at the managed object boundary outside of the managed object.

[0102] SourceIndicator is set to Self_configuration if a notification has been generated as a result of the self-configuration method.

[0103] SourceIndicator has the value Self_opt_IC if the notification was generated as a result of a method mainly related to interference coordination (IC).

[0104] SourceIndicator has the value Self_opt_load_balancing if a notification has been generated as a result of a method mainly related to self-optimization of load balancing.

[0105] SourceIndicator or the type of automatic function may have the value Self_opt_HO_parameters if the notification was generated as a result of a method mainly related to self-optimization of the transfer parameters.

[0106] SourceIndicator or the self-X function type may be Self_opt_RACH if the notification was generated as a result of a method mainly related to RACH self-optimization.

[0107] SourceIndicator may have a value of Self_opt_capacity if a notification has been generated as a result of a method mainly related to self-optimization of bandwidth.

[0108] In the example, sourceIndicator may have a value of Self_opt_coverage if a notification was generated as a result of a method mainly related to self-optimization of coverage.

[0109] SourceIndicator may have a value of Self_optimization if a notification has been generated as a result of a self-optimization method where allocation cannot be made for the above-mentioned purposes.

[0110] SourceIndicator may have a value of Self_healing if a notification has been generated as a result of the self-healing method.

[0111] SourceIndicator may be set to unknown if the source of the operation cannot be determined.

[0112] Thus, the sourceIndicator value represents the source of the operation, i.e. the name of the operation type.

[0113] In addition, the notifyObjectCreation method may include an attributeList parameter, which is a list of sequences containing AttributeName and AttributeValue for attributes (name / value pairs) of the created MO. An example of a name and / or value pair could be the name of the subscriber of the network operator.

[0114] Self_configuration can mean entering a new eNodeB in the field and equipping the eNodeB automatically with a start parameter.

[0115] The Self_opt_IC example may include detecting interference on a frequency and determining the cause of interference in an adjacent cell. This can be done by reducing the transmission power. Like all self-X functions, Self_opt_IC functions without involving NMS, i.e. essentially any communication through the Itf-N interface, may prevent you from performing the self-X function.

[0116] Self_opt_load_balancing may include regularly receiving an alert message informing about a cell overload situation. Free bandwidth of an adjacent cell can be used by reducing the antenna angle of the overloaded cell, thereby reducing the occupied space of the cell. The load can be reduced because the occupied space of the cell can be reduced and the load can be taken over by neighboring cells having slow bandwidth.

[0117] Self_opt_HO_parameter to indicate if HO optimization can be performed. HO optimization can be used if handover statistics show that in an area, e.g. on the border of two cells so-called ping-pong transmission. An MS or mobile phone regularly changes the connection from one base station to another. Function

For example, -22self-X may increase the hysteresis for the forwarding threshold to prevent this ping-pong forwarding.

[0118] Self_opt_capcaity can be used if not all available channels are used. The reason for not using all channels may be energy saving. However, if you have increased the number of users in the appropriate cell, you can activate additional channels for unused channels.

[0119] Self_opt_coverage can be performed if measurements show that some areas are not covered by cellular radio signals, and therefore radio reception is not possible in these areas. The self-X Self_opt_coverage functionality can respond by increasing the transmission power of the base station. The self-X or network functionality decides how to react. You can prevent communication via the Itf-N interface or the network management system interface.

[0120] Self_opt_RACH functionality can detect that available RACH channels are not fully occupied. Thus, using the Self_opt_RACH functionality may result in using at least one of the lightly loaded RACH channels as a data channel.

[0121] Self_healing functionality may reconfigure adjacent cells to replace a damaged or broken cell. When a cell is damaged in an adjacent cell, the transmit power can be increased and / or the angle of the antenna can be reduced so that the occupied space of the damaged cell can be delivered substantially by the adapted cell. Self-healing will be described in more detail in Figs. 3a 3b.

[0122] Using different values ​​for the sourceIndicator parameter may allow the source of self-X functionality to be identified. Different values ​​can be represented by different bit patterns. In other words, the source indicator can identify which changes in the network have been triggered by self-X functionality.

[0123] Table tab.2 shows the input parameters of the notifyObjectDeletion method. According to the notifyObjectCreation method, the input parameters or list of input parameters includes an additional text parameter and / or a source indicator parameter defined in the table tab. 1.

[0124] IRPAgent 100 notifies the subscribed IRPManager 200 of the deleted managed object using the notifyObjectDeletion method. Managed objects represent real physical objects, such as a subscriber to the network operator. The subscriber object can be created when the subscriber subscribes to the operator and can be deleted when the subscriber withdraws the subscription. Managed objects can be created, changed and / or deleted using the appropriate method. The method can be used by an agent and / or manager. The agent and / or manager can be controlled through rules.

[0125] IRPAgent invokes the notifyObjectDeletion notification because the item notification meets the filter constraint expressed in the IRPManager subscription operation. This notification is sent from IRPAgent 100 to IRPManager 200.

-23Tab. 2

<td>Name of the parameter</td><td>Qualifier</td><td>Matching information</td><td>Comment</td>

<td>objectClass</td><td>M, Y</td><td>ManagedEntity.obj ectClass</td><td>See tab. 1</td>

<td>objectInstance</td><td>M, Y</td><td>ManagedEntity.obj ectInstance</td><td>See tab. 1</td>

<td>notificationId</td><td>M, N</td><td>-</td><td>See tab. 1</td>

<td>EVENTTIME</td><td>M, Y</td><td></td><td>Heading notice. He should carry time remove ManagedEntity.</td>

<td>systemDN</td><td>C, Y</td><td>-</td><td>See tab. 1</td>

<td>NotificationType</td><td>M, Y</td><td>Mapping to notificationType.</td><td>See tab. 1</td>

<td>correlatedNotifications</td><td>Oh</td><td>-</td><td>See tab. 1</td>

<td>additionalText</td><td>Oh</td><td>-</td><td>See tab. 1</td>

<td>sourceIndicator</td><td>Oh</td><td>See tab. 1</td><td>See tab. 1</td>

<td>attributeList</td><td>Oh</td><td>SEQUENCE LIST &lt;AttributeName. attributeValue&gt;</td><td>Attributes (pairs name / value) of the deleted MO.</td>

[0126] After deleting the managed object, all child managed objects, i.e. the full child MIB, are also deleted. In addition, all associations in which the managed object participates are removed.

[0127] Table tab.3 shows the input parameters of the notifyAttributeValueChange method. The use of the notifyAttributeValueChange method can be explained by the example of the self-X method or the self-X Self_opt_coverage function. The Self_opt_coverage method in this example increases the physical power of eNodeB physical transmission. Physical eNodeB is represented by related objects. If the eNodeB transmission power is increased, you can change the value of the parameter representing the transmission power in the associated eNB. This change in the eNB function is reported using notifyAttributeValueChange when a change is detected.

-24Tab. 3

<td>Name of the parameter</td><td>Qualifier</td><td>Matching information</td><td>Comment</td>

<td>objectClass</td><td>M, Y</td><td>ManagedEntity.obje ctClass</td><td>See tab. 1</td>

<td>objectInstance</td><td>M, Y</td><td>ManagedEntity.obje ctInstance</td><td>See tab. 1.</td>

<td>notificationId</td><td>M, N</td><td>-</td><td>See tab. 1</td>

<td>EVENTTIME</td><td>M, Y</td><td></td><td>Heading notice. It should have the value (values) of the attribute (attributes) of the changed time.</td>

<td>systemDN</td><td>C, Y</td><td>-</td><td>See tab. 1</td>

<td>NotificationType</td><td>M, Y</td><td>Mapping to notificationType.</td><td>See tab. 1</td>

<td>correlatedNotifications</td><td>Oh</td><td>-</td><td>See tab. 1</td>

<td>additionalText</td><td>Oh</td><td>-</td><td>See tab. 1</td>

<td>sourceIndicator</td><td>Oh</td><td>See tab. 1</td><td>See tab. 1</td>

<td>attributeValue Chage</td><td>M, N</td><td>LIST OF SEQUENCES &lt;AttributeName, NewAttributeValue, CHOICE [NULL, OldAttributeValue]&gt;</td><td>Changed Attributes (name / value pairs) MO (with new and optional old ones values).</td>

[0128] The nnotifyAttributeValueChange method also includes an additional text parameter and / or source indicator as described in Table 1. The structures for notifyObjectCreation, notifyObjectDeletion and notifyAttributeValueChange correspond to each other.

[0129] IRPAgent 100 notifies the subscribed IRPManager 200 about the change of one or more attributes of a managed object in NRM (ang. Network Resource Model). NRM is a description or definition of objects, content of objects, and relationships between objects. IRPAgent 100 issues a notification because the item notification meets the filter limit expressed in the IRPManager 200 subscription operation. The filtering mechanism can be integrated with the agent writing device and / or the manager reading device.

[0130] Definition of the additional text parameter from tab.1, tab.2 and tab.3 used in notifyObjectCreation, notifyObjectDeletion and notifyAttributeValueChange notifications

-25 can be extended to include a description, where the additional text parameter may, e.g. contain an identifier that allows to identify which self-X method initiated the event.

[0131] In an alternative example, the additional text parameter may be used to enter a specific new parameter or a subsequent parameter indicating the identifier that allows identifying which self-X method initiated the event. Thus, a separate parameter can be added to the table tab.1, tab.2 and / or tab.3, which may e.g. contain an identifier that allows to identify which self-X method initiated the automatic function.

[0132] The object defined in 3GPP TS 32.662 can be reused.

[0133] For notifyObjectCreation, notifyObjectDeletion and / or notifyObjectAttributeValueChange notifications that are triggered by the self-configuration functionality, use the self-configuration value for the sourceIdentifier input parameter.

[0134] Figs. 3a to 3c show the use of the self-X method in a network according to an embodiment of the invention.

[0135] Fig. 3a illustrates a scenario in which seven different cells 301, 302, 303, 304, 305, 306, 307 generate a communication network 101 or a space occupied by a cellular communication network. In other words, seven cells 301 to 307 are generated by seven base station antennas if all antennas and / or all base stations are operational. Similarly, the terms cell and base station can be used.

[0136] Fig. 3b illustrates the network scenario 101 of Fig. 3a, where one base station 307 has failed in accordance with an embodiment of the invention. In Fig. 3b, intermediate base station 307 (BTS) has failed. Base station 307 failure generates area 307 that is no longer covered.

[0137] Fig. 3c shows the network configuration after execution or use of the self-X function according to an embodiment of the invention.

[0138] A failure was detected in network 101. For example, a self-X server, not shown in fig. 3a, 3b, 3c detected that BTS 307 or cell 307 has failed. Due to the use of self-healing functionality, self-healing functions or self-healing methods, the occupied space of the 301 ', 303', 305 'cells has been adapted in such a way that the changed shape of the cells now also covers the damaged middle cell 307. Self-healing can also be combined with self-configuration. This self-healing or activation of the replacement configuration was carried out either by the network 101 itself or by the corresponding self-repair server 102. However, the network management system 200 may not be notified of self-healing functionality. NMS may not be involved in reconfiguring the 101 network.

[0139] By reading the recording media 103 of the corresponding agent device in the network 101, the NMS can identify that self-healing has been performed and that self-healing was the cause of the network configuration change.

[0140] Thus, the notified NMS may not attempt to change the configuration because the NMS understands that this was generated by the required self-healing operation to cover the missing middle cell.

[0141] In other words, in the scenario as shown in Figs. 3a to 3c, the cells or radio cells 301 to 307 cover a predefined geographical area. In Fig. 3a, each station 301 to 307 covers an area of ​​substantially the same size.

[0142] Fig. 3b shows the failure of one antenna 307 cells 301-307. Self-healing server 102 has been notified of cell 307 failure. The self-healing server or self-X server 102 has a surrogate configuration for such failure scenarios and activates one of the surrogate configurations without involving the system 200 network management (NMS). Thus, for self-healing, you can prevent the exchange of messages via the Itf-N interface.

[0143] This NMS 200 and / or all other NMS 200a, 200b are informed by notification of the sourceIndicator parameter set to self_healing (sourceIndicator = self-healing). In other words, you can call notifyAttributeValueChange when you set sourceIndicator to self_healing. This method informs NMS or IRPManager 200 about changing the configuration of each individual cell. The sourceIndicator value informs NMS or IRP Manager 200 about the use of self-X on a 101 network. To enable NMS to know that individual messages of each reconfigured cell belong to the same event, correlated notifications for different cells can be listed in the correlatedNotifications parameter in related notifications.

[0144] Cell 307 failure may additionally be reported by an alarm notification.

[0145] This may prevent NMS from recognizing the configuration change in each individual cell 301 to 307 as independent and as a violation of a certain configuration policy (e.g., for a policy requiring not to set a transmission power higher than a certain value during normal operation). Therefore, NMS, which is responsible for handling failures, does not need to inform other NMS in order to change the configuration. Thus, NMS may not receive notification with the source indicator set to management_operation.

[0146] Because the changes were made inside the network and were not triggered by the network management, it is also prevented that NMS attempts to change the configuration of cells 301 to 306 [0147] Thus, using the sourceIndicator parameter set to self_healing allows showing NMS 200 that without participation network management system error, i.e. 307 antenna defective, was served by the self-healing server 102. This can also prevent one of the NMSs from detecting, for example, the changed configuration of Fig. 3c and may specify a failure in the policy parameters and may attempt to reconfigure the scenario shown in Fig. 3c. Each NMS can be informed using the sourceIndicator parameter that the configuration shown in fig. 3c was initiated by the network, which determined that the configuration had been changed.

[0148] Fig. 4 is a block diagram of a network management architecture according to an embodiment of the invention.

[0149] The agent device 100 includes an element management system (EMS) 401 and a network element 400 (NE). EMS and NE are in a 402 communication connection. Agent 100 may be part of a communication connection 101 (not shown in Figure 4). The self-X server 102, e.g. a self-healing server, is connected via a communication link 403 to EMS 401. In addition, through the 404 Itf-N interface, NMS NMS1 200, NMS2 200a and NMS n 200b are connected to agent 100 or to EMS 401.

[0150] Fig. 5 shows a message flow network for exchanging object information according to an embodiment of the invention.

[0151] Many NE 400 communication networks 101 are represented by one NE 400. NE

400 at step S500, it sends an alarm message to EMS 401 to inform EMS 401 that the antenna has failed, e.g. cell antenna 307. EMS 401 at step S501 forwards the alarm message from NE 400 to server self-X, e.g. server self repair 102. EMS 401 in step S502 sends the same NE 400 alarm message about antenna failure 307 to at least one NMS 200 from the NMS 200, 200a, 200b group.

[0152] Upon receiving the alarm message from step S501, in step S503 the self-X server 102 determines that antenna failure 307 can be handled by the self-X server 102.

[0153] In step S504, the self-X server 102 sends information to the NMS 200 that the self-X server supports the replacement configuration of the defective antenna in the network represented by NE 400. The message sent from the self-X server 102 to the NMS 200 may include an identifier X. The NMS does not care about the failure, so no further information is sent to the NMS 200 via the Itf-N interface, while the 102 self-X server organizes reconfiguration on network 101.

[0154] In step S505, the self-X server 102 specifies a replacement configuration, and in step S506 the server self-X 102 sends a replacement configuration for multiple NE 400 to the EMS 401. The replacement configuration includes the identifier X.

[0155] EMS 401 defines a replacement configuration for each NE 400 and sends the corresponding replacement configuration to each individual NE 400 (step S506 '). Thus, the self-X server 120 manages the backup configuration of the network 101, informing the corresponding NE 400 about the new configuration.

[0156] In step S507 EMS 401 or the agent device 100 sends, create message, delete message and change message (create / delete / change message) containing sourceIndicator set for self-repairing, including - in parameter additionalText identifier X to server 102 self- X.

[0157] The identifier X may identify the event with a unique ID or unique event number. The NMS configuration and / or the log evaluating application may use the X identifier to determine if the changes in cells 301 to 306 and / or NE 400 correspond to each other or are based on the same cause. The X identifier can also be used for

Requesting or reading information about events that were caused by a method and / or an event having an identifier X. Further information, such as the duration of initiated events, the duration of the self-repairing method, etc. can also be saved or read.

[0158] The self-X server 102 receives the corresponding message or parameter list as the response, confirmation or response to the replacement configuration sent in step S506.

[0159] In parallel with the create / delete / change message, EMS 401 sends the create / delete / change message to NMS 200 in step S508. NMS 200 receives the corresponding message or parameter list as an information or update message to inform NMS 200 of the actual configuration or network status. In the example, NMS 200 is informed about the reason for the self-healing function.

[0160] In other words, the list of parameters described in the tables tab. 1 to tab. 3 can be sent to the self-X server 102 and / or NMS 200. The create / delete / change message can be used as confirmation message or as informational message.

Fig. 6 shows a flow network of a method for detecting the use of an automatic function according to an embodiment of the invention.

[0162] The method starts in an idle state S600.

[0163] In step S601, an automatic function performed in a communication network is detected.

[0164] Step S602 includes determining the type of the corresponding automatic function.

[0165] Information representing the type of automatic function in the step S602 is recorded in the predetermined storage area of ​​the recording medium before the method returns to the idle state in the step S604.

[0166] Fig. 7 shows a flow network of a method for detecting in a management device that an automatic function has been used in a communication network.

[0167] The method starts in an idle state S700.

[0168] In step S701, a request to justify the network configuration change is made with the information read representing the type of automatic function of the previously defined recording medium storage area.

[0169] In another example, the request does not need to be sent because a message containing the required information or parameter list is received.

[0170] If the NMS configuration, i.e. NMS responsible for network configuration, must know who or what was the initiator of the detected change, you can read the recording medium. Self-X functions, in particular self-X self-optimization functions, may not use alarm messages or alert notifications. Thus, a read or request from the recording medium can be used to obtain information about the cause of the change, which would otherwise only be available to NMS 200 if an alarm message was generated.

[0171] Thus, the recording medium can be used as a "mailbox" for exchanging messages between NMS 200 and network 101, in particular for exchanging the type of selfX function used in network 101.

[0172] In step S702, the use of the automatic function for reconfiguring the network is determined using the information that was read in step S701.

[0173] In step S703, the idle state is again reached, waiting for the next operation.

[0174] It should be noted that the term "comprising" does not exclude other elements or steps, and the singular does not exclude many. Also, the elements described in connection with the various embodiments can be combined.

[0175] It should also be noted that the markings in the claims are not used to limit their scope.

[0176] Acronyms and terminology

CM Configuration Management

MIB Management Information Base

OAM Operation, Administration, Maintenance (Operation, management, maintenance)