KR100742317B1 - Communication management network system and method for managing a communicaiton network - Google Patents

Abstract

A mechanism available in a communications management network system comprising a network element and an operating system portion is proposed, wherein adaptation information is transmitted from the network element to the operating system after the network element is physically connected to the operating system portion. The operating system configures one or more applications based on the metadata accessed using the adaptation information. The network element and all other network elements of the same type / release are then manageable by the operating system unit.

Description

COMMUNICATION MANAGEMENT NETWORK SYSTEM AND METHOD FOR MANAGING A COMMUNICAITON NETWORK}

1 shows a block diagram of a communication management network system according to a first embodiment of the present invention;

2 shows a block diagram of a communication management network system according to a second embodiment of the present invention;

3 shows a flow chart of a management method according to the first embodiment;

4 shows a flow chart of a management method according to the second embodiment;

5 shows a flow chart of the management method according to the third embodiment.

The present invention relates to a management mechanism used in a communication network. In particular, the present invention relates to a method for managing a communication network, a communication management network system, a device usable in a communication management network system, and a network element connectable to an operating system portion of the communication management network system.

In recent years, for example, wired-based communication networks such as Integrated Services Digital Networks (ISDN), or cellular third-generation communication networks such as cdma2000 (code division multiple access) systems, universal mobile communications systems (UMTS), universal packet radio services (GPRS) Or communication networks of wireless communication networks, such as other wireless communication systems such as WLANs, are gradually expanding around the world. Various organizations such as the 3rd Generation International Cooperation Project (3GPP), the International Telecommunication Union (ITU), the 3rd Generation International Cooperation Project 2 (3GPP2), and the Internet Engineering Task Force (IETF) have standardized for telecommunication networks and multiple access environments. Work is in progress.

In general, the system architecture of a telecommunications network is such that a mobile station, a mobile phone, a landline phone, a personal computer (PC), a laptop computer, a personal digital assistant (PDA) and a subscriber user equipment such as this can be used as a radio interface, This interface and transceiver allow access to the access network subsystem. The access network subsystem controls the communication connection to / from the user equipment and is connected to the corresponding core or backbone network subsystem via an interface. The core (or backbone) network subsystem switches over data sent to a destination party, such as another user equipment, service provider (server / proxy), or other communication network. Note that the core network subsystem is connected to a plurality of access network subsystems. Depending on the communication network used, the actual network structure may vary, for example as defined in the respective specifications for UMTS, GSM and the like and known to those skilled in the art.

Generally, such as control network elements, support nodes, or service nodes, in order to properly establish and handle communication connections between user equipment and network elements such as other user terminals, databases, servers, and the like. One or more intermediary network elements are included.

As the size and complexity of communication systems such as telecommunication networks expand rapidly, it is essential to provide appropriate services to manage communications. For example, configuration, accounting, performance, security, and such services are critical elements for managing critical resources within telecommunication networks that are widely distributed. For this purpose, in the case of telecommunication systems, the so-called telecommunications management network (TMN) concept is used to manage various types of networks, such as high speed fiber optic networks to distributed cellular and satellite based wireless communication systems.

Within this TMN, the management system includes several types of components. These components are particularly capable of monitoring and interacting with operating systems (OSs) or operating subsystems that monitor, coordinate, and control communication functions, data communication networks, and network management systems to users. Workstations that provide capabilities, network elements that provide agent services, such as network communication equipment such as a radio network controller (RNC), and proxy agents or the like. An OS provides management, monitoring, and control of a managed network, interacts with components in the network to collect information, and issues commands that affect the behavior of the network. Provide and provide services. The network element may comprise a component, a group of components, or a portion of telecommunication equipment that is part of a telecommunications network.

The TMN specifies a layered architecture for the management of telecommunication networks. TMN relates to the monitoring, control and coordination of resources in a network. Resources are components of a system that provides a service.

Management functions are classified into sub-components such as configuration management, fault management, performance management, accounting management and security management. These functions are provided by the applications.

Typically, the network management architecture also involves the use of two major components called managers and agents. The administrator provides a high level in terms of system performance to monitor and control the behavior of managed devices. An agent is a process residing on a managed device that provides an administrator with insight into the status of the managed equipment.

An administrator can connect to more than one agent. In contrast, one agent can be connected to more than one manager. Managers and agents communicate with each other through management protocols. Such protocols include, for example, Common Management Information Protocol (CMIP), Simple Network Management Protocol (SNMP), and the like.

SNMP provides a set of services that allow an SNMP manager to interact with an SNMP agent, which provides access to management information of the managed device (and / or software). Such management information is represented by a construct called a Management Information Base (MIB) that is defined through a set of primitives. The MIB consists of individually addressable objects that can take various forms, depending on the version of SNMP and the managed application. The protocol itself provides a set of mechanisms for managers and agents to exchange the values of the elements contained in the MIB.

If a new network element (new type or release / version of the network element) is to be connected to the telecommunications network, then access to the TMN is ensured to ensure that the network element can be managed by the TMN's operating system. It must also be established. When the SNMP concept is used, for this "integration" of new network elements, the SNMP MIB definitions recorded in the MIB file are downloaded by the developer or system integrator, and the operating system uses these MIB definitions to It is configured manually. Examples of such MIB definitions are given, for example, in the "MIB Quick Reference for the Cisco ONS 15500 series" available by Cisco Systems, Inc., 2001-2004 Internet. An example of a configuration procedure is given, for example, in "Adding Cisco Traps to HPOV for Windows Traps Using a GUI" of Cisco Systems, Inc., June 11, 2002, document ID 13442.

As mentioned above, in this TMN environment, there may be numerous types and releases or versions of network elements. Nevertheless, all these different network elements must be connected to the operating system to ensure overall network management.

However, connecting a new network type or release to an operating system is also a work intensive process that requires the work of a person, such as a software developer or system integrator or network operator. For example, certain information about network elements must be aggregated and organized into operating systems. Standard protocols such as 3GPP and SNMP exist, but network element-specific features require manual intervention on the operating system. For example, with an SNMP MIB definition specific to a particular network element, the information from the SNMP MIB definition must be configured with the OS. This is time consuming and expensive and will also cause errors in the adaptation of the operating system to network elements.

Features that require manual work include, but are not limited to, the additional features required for the visualization of network elements in the OS user interface, such as the provision of corresponding icons, descriptive text and / or labels, and operations and maintenance ( O & M) Restrictions or extensions of protocol implementations (so-called "statements of compliancy"), and the structure of transmitted configuration management data (managed object classification, attributes, containment hierarchy, inheritance tree ( inheritance tree, value constraints, structure and semantics of the transmitted performance management data (measurement type, counter name and descriptive text), and help texts of Chuka for defect management events, for example, and filtering Adaptations to common OS applications such as rules, aggregation rules, correlation rules, and rules that convert SNMP traps into defects. It is not limited to.

It is therefore an object of the present invention to provide a mechanism for managing a communication network in which efforts in a communication management system for integrating and connecting new network element types / releases are reduced.

In particular, it is an object of the present invention to provide an improved mechanism for managing a communication network that can reduce the work required in the operating system when adapting a network element type / release that is newly connected to the operating system of the management network.

This object is achieved by means defined in the appended claims.

In particular, according to one aspect of the proposed solution, a method is provided for managing a communication network comprising, for example, a network element and an operating system, the method comprising:

After the network element is physically connected to the operating system portion, transmitting adaptation information from the network element to the operating system, processing the adaptation information at the operating system portion, based on the adaptation information Configuring one or more applications in an operating system portion and executing a management process of the network element by the operating system portion.

In addition, according to one aspect of the proposed solution, there is provided a communication management network system for managing a communication network, comprising a network element and an operating system unit, wherein after the network element is physically connected to the operating system unit, The network element is adapted to send adaptation information to the operating system, wherein the operating system portion comprises: a processor for processing the adaptation information at the operating system portion, and one or more within the operating system portion based on the adaptation information. Configuration means for configuring applications, wherein the operating system portion is adapted to execute a management process of the network element.

Furthermore, according to one aspect of the presented solution, there is provided a device usable in a communication management network system for managing a communication network, for example, wherein the device is configured by an operating system unit and a network element is provided to the operating system unit. After physically connecting, further comprising adaptation information from the network element, the processor for processing the adaptation information and configuration means for configuring one or more applications within the operating system portion based on the adaptation information; Wherein the operating system unit is configured to execute a management process of the network element.

Furthermore, according to one aspect of the presented solution, there is provided a network element connectable to an operating system part of a communication management network system for managing a communication network, for example, wherein the network element is physically connected to the operating system part. Later, the network element is adapted to transmit adaptation information for the operating system used by the operating system unit to configure one or more applications within the operating system unit, where the operating system unit is a management process of the network element. Is supposed to run.

According to a further purification, the presented solution may comprise one or more of the following features:

The adaptation information may comprise metadata definition parts of a network element manageable by the operating system part;

The adaptation information may comprise identification data of the network element, wherein the identification data of the network element may comprise, for example, the type and release information of the network element;

The management mechanism requests, after processing of the adaptation information, further adaptation information for the network element from the library network part based on the identification data, and from the library network part, further adaptation information for the network element. Means for contacting the library network to receive a message, wherein the configuration of one or more applications of the operating system portion may be based on additional adaptation information received from the library network portion;

The adaptation information may also comprise one of metadata definitions of the network element or identification data of the network element manageable by the operating system unit. In such a case, the management mechanism may comprise means for determining the classification of the adaptation information after the processing of the adaptation information to distinguish whether the network element transmitted metadata or identification data. Thereafter, the management mechanism may include means for configuring one or more applications of the operating system portion based on the adaptation information from the network element, if it is determined that the adaptation information includes metadata. Otherwise, if it is determined that the adaptation information includes identification data, the management mechanism requests further adaptation information for the network element based on the identification data from the library network section, and the library network section. Means for contacting the library network portion to receive additional adaptation information for the network element, wherein the configuration of one or more applications of the operating system portion is further adaptation information received from the library network portion. Based on;

The configuration may in particular comprise at least one of a configuration management subcomponent, a performance management subcomponent, an account management subcomponent, a security management subcomponent and a defect management subcomponent;

The configuration comprises the addition of features required for the visualization of the network element in the user interface, the limitations of the operation and maintenance protocol implementation, the extensions of the operation and maintenance protocol implementation, the structure of the transmitted configuration management data, the transmitted performance At least one of the structure and meaning of management data, additional help texts for defect management events, and adaptations to general operating system applications;

The configuration may also include at least one of reconfiguration of the database scheme, modification of the relevant database tables, creation of new database tables, modification of the graphical user interface and modification of the messaging system;

The management mechanism may further comprise means for requesting the adaptation information from the network element by the operating system unit after establishment of a physical connection between the network element and the operating system unit;

The management mechanism may be implemented in a communication management network.

By the proposed solution, the following advantages can be achieved:

The mechanism presented allows adaptation of network element types / releases to operating systems with significantly reduced effort. Advantageously, said network element provides all the information necessary for its adaptation when first connected to said operating system. After the initialization, the network element is manageable without requiring additional adaptation steps, which also applies to all subsequently connected network elements of the same type / release. In other words, an automated adaptation process for the management of network element types / releases can be achieved.

The automation can be further improved when the adaptation information is transmitted to the operating system in the form of metadata in a predetermined format. Thereafter, the adaptation effort on the operating system side can be further reduced to almost zero.

Since the proper adaptation of the network element and the operating system to each other merely requires the exchange of new metadata information, the presented mechanism is also useful for further releases or updates of the network element connected to the operating system.

By the present invention, consumers can receive basic support for the network element directly by the network element itself, ie there is no problem of release synchronization between the network element and the operational support system.

By using a library network section for storing and retrieving the adaptation information, ie the metadata of the network element, the metadata can be kept in a centralized location, so that an update to the adaptive processing can be achieved as soon as possible . In addition, if only the identification data is transmitted when the network element is connected to the operating system, the storage capacity of the network element can be saved, and the operating system has access to the latest version of achievable application information (metadata). can do.

By using the mechanism presented above, R & D costs can be significantly reduced. In addition, the time-to-market for O & M support for new network elements can be improved.

The above and further objects, features and advantages of the present invention will become more apparent with reference to the accompanying drawings and detailed description.

In the following, embodiments of the present invention will be described with reference to the drawings.

The first embodiment is shown in connection with FIGS. 1 and 3.

In FIG. 1, a block diagram of a communications management network system is shown. According to Fig. 1, reference numeral 1 denotes an operating system part which is part of a management network component (manager component) of a telecommunications management network, for example, but not limited to. Reference numeral 2 denotes an agent component or a network element that is part of an agent component.

It should be noted that the system according to FIG. 1 represents a simplified architecture of a communication management network in which the present invention is implemented. In addition, the network elements (agent components) and operating system portions (administrator components) described herein may be implemented by software or hardware. In either case, the devices or network elements correspondingly used to carry out their respective functions comprise several means required for the control, processing and communication functions. Such means include, for example, a processor unit that executes instructions and processes data, and memory means (e.g., ROM, RAM, EEPROM, and the like) that store instructions and data that serve as a processor and a work area thereof. Input means (e.g., floppy diskette, CD-ROM, EEPROM and the like) for inputting data and instructions by software, and user interface means (e.g. screen, Keyboards and the like) and interface means (eg, wired and wireless interface means, antennas, and the like) for establishing a communication connection under the control of the processor unit.

In FIG. 3, a management mechanism for the communication management network system of FIG. 1 is shown.

When the network equipment 2 is physically connected to the communication management network system, that is, the operating system portion indicated by the solid line in FIG. 1, the network element 2 transmits the adaptation information to the operating system portion 1 (of FIG. 3). Step S10). This transmission is indicated by the dashed right arrow in FIG. 1.

According to the first embodiment, the adaptation information comprises metadata previously stored in the memory of the network element 2. Metadata is a generally known concept for machine understandable information for a network, which is "data about data." For example, they are used to describe the content, quality, conditions, and other characteristics of the data.

In this case, the metadata describes the manageable part of the type / release of the network element 2. That is, the network element 2 uses metadata to provide all the information necessary for the connection to the operating system (and the same type / release as the network element 2).

In general, the present invention relates to all manageable parts of a network element. These parts include, for example, subcomponents or functional management areas in each network element such as configuration management (CM), performance management (PM), account management (AM), security management (SM), and defect management. These include additional features required for the visualization of network elements in the OS user interface, such as the provision of corresponding icons, descriptive text and / or labels, as well as the operation and maintenance (O & M) protocol implementation. Restrictions or extensions (the so-called "statement of compliancy") and the structure of the transmitted configuration management data (managed item classification, attributes, containment hierarchy, inheritance tree, value constraints) value constraints, the structure and semantics of the transmitted performance management data (measurement type, counter name and descriptive text), for example, helper texts for defect management events, and filtering and aggregation rules. ), Adaptation to common OS applications such as correlation rules, and rules for converting SNMP traps to defects, and the like.

Adaptation information and metadata are metadata that describe the data sent from the network element to the OS. The data is CM data, FM data, PM data and the like. For example, CM data includes managed items with so-called attributes. The CM metadata describes managed item types, icons, textual descriptions, and the like supported by the network element. In SNMP terminology, CM data is in the MIB (particularly data), while metadata is a text file that can be downloaded. PM data includes counter values. The PM metadata includes the name of the counter, the textual description, and rules about how to aggregate the values.

As soon as the establishment of the physical connection of the network element 2 is recognized, for example, a request sent by the operating system unit 1 to the network element 2 causes the transmission of application information, ie metadata. The operating system, for example, recognizes the new network element after it has been turned on. Alternatively, it will recognize the new network element by a message or command from an end-user (eg, "connect to new NE on IP address 12.12.12.12"). Another possibility is so-called IP network discovery (pinging random IP addresses and / or traversing the MIB of known network elements).

As an alternative scheme for transmitting adaptation information (not shown), the network element (as long as a physical connection is assumed to be established) may be adapted to transmit the adaptation information via a given interface as soon as it is activated. This transmission can be stopped at the same time that an acknowledgment or the like is received by the network element 2 via the interface.

In Fig. 3, when the operating system unit 1 receives application information including metadata, the processing step of the metadata is executed (step S20). In this processing step, information about the type / release of the network element 2 included in the metadata is recognized. In other words, the operating system unit 1 retrieves information about the manageable portions of the type / release of the network element 2 to further process such as validating the information and converting the information into the required format internally. Uses this information,

Further processing of the operating system unit 1 includes configuring one or more applications based on the information contained in the metadata received from the network element 2 (step S30). This is because the operating system unit 1 coordinates / adapts the software in the management applications and / or operating system unit 1 so that the network element type / release is managed by the operating system unit 1 Interpret the information. For example, the operating system may be configured to reconfigure the database organization, such as modifying related database tables or creating new tables, modifying graphical user interfaces (GUIs), sending messages to the system, and the like.

When the configuration processing ends, the operating system unit 1 executes management of the network element 2 (step S40). This includes, for example, activating a network element, thereby causing data flow to begin from the network element. Thereafter, the procedure ends.

2 and 4, a second embodiment is described.

2, a block diagram of a communications management network system is shown. Similar to the first embodiment, according to FIG. 2, reference numeral 11 denotes an operating system portion that is part of a management network component (manager component) of a communication management network (such as, but not limited to TNN). , Reference numeral 12 denotes a network element that represents or is part of an agent component. Moreover, reference numeral 13 denotes a network element metadata library, which is an external database storing metadata information describing, for example, manageable portions of different network elements of different types and releases accessible to the operating system. . The network element metadata library 13 is connectable to the operating system unit 11.

The system according to FIG. 2 also shows a simple architecture of a communication management network in which the invention is practiced. Moreover, the network elements (agent components) and operating system portions (administrator components) described herein may be implemented by software or hardware and include the same components as described in connection with the first embodiment. .

4, a management mechanism for the communication management network system of FIG. 2 is described.

When the network equipment 12 is physically connected to the communication management network system, that is, the operating system section 11 indicated by the solid line in FIG. 2, the network element 12 transmits the adaptation information to the operating system section 11. (Step S110 in Fig. 4). This transmission is indicated by the dashed arrow on the right side of FIG.

According to the second embodiment, the adaptation information comprises for example identification information identifying the type and release of the network element 12.

The transmission of the application information, i. After being turned on), for example, by a request sent to the network element 12 by the operating system unit 11. Also the alternative approach described in the first embodiment of the transmission of the application information as soon as the network element is turned on is applicable.

In other words, the network element 12 responds to the request for adaptation information by the operating system unit by sending identification data identifying itself (or its type) and release.

In FIG. 4, when the operating system unit 11 receives application information including identification data of the type / release of the network element 12, the processing step of the application information is executed (step S120). In this processing step S210, the identification data of the type / release of the network element 2 is withdrawn from the application information received from the network element 12 and used for further processing.

In this further processing, the operating system unit contacts the network element metadata library 13 and requests additional application information for the specific network element type / release by using the received identification data (step S130). The network element metadata library 13 retrieves metadata about the type / release of the network element 12 based on the identification data received by the request from the operating system unit 11, to determine the network element 12. The metadata found in the database for the type / release is transmitted to the operating system unit 11. In this case, the metadata previously stored in the network element metadata library 13 describes the manageable portions of the type / release of the network element 12. In other words, the network element 12 provides the necessary information to the operating system section 11, so that the necessary adaptation information for accessing the operating system of the type / release of the network element 12 is provided by the metadata. It may be withdrawn from the data library 13.

Metadata received from the network element metadata library 13 when the operating system section 11 receives a response from the network element metadata library 13, that is, metadata about the type / release of the network element 12. Processing is executed similarly to the first embodiment (step S140). This is because the operating system unit 11 retrieves information about the manageable portions of the type / release of the network element 12, and in further processing such as validating the information and converting the information into an internally requested format. Use information, in other words, when the operating system portion 11 receives identification data from the network element 12, this is metadata from an online library, for example a particular type / release of the network element on the Internet. Download the information.

Further processing of the operating system unit 11 includes configuring one or more operating applications based on the information included in the metadata received from the network element metadata library 13 (step S150). This is because the operating system unit 11 interprets the metadata information to coordinate / adapt the management applications and / or software in the operating system unit 11 so that the type / release of the network element 12 is determined by the operating system. It means that it can be managed by the unit (11).

When the configuration procedure is finished, the operating system unit 11 executes management of the network element 12 (step S160). This includes, for example, activation of the network element 12, so that data flow from the network element begins. Thereafter, the procedure ends.

The second embodiment is usable, for example, when the network element cannot store metadata necessary for adaptation of the operating system, or when metadata information cannot be transmitted by the network element. Moreover, the second embodiment is available when the data contained in the metadata information is often changed, for example in the case of frequent update processes for the network element type.

In Fig. 5, a third embodiment of the present invention is described. The third embodiment represents a combination of the features described in the first and second embodiments.

The communication management network system architecture usable in the third embodiment is basically equivalent to that shown in FIG. 2 of the second embodiment. This means that the communication management network system of the third embodiment includes an operating system section 11, a network element 12 and a network element library 13.

In contrast to the second embodiment, the network element 12 according to the third embodiment is adapted to transmit adaptation information including metadata or identification data (step S210 of FIG. 5). What kind of application information is actually transmitted may depend, for example, on the type or release of the network element 12.

In step S220, the received adaptation information is processed in the operating system unit 11. This means that what kind of application information, ie metadata or identification data, is received. In step S230, when the adaptation information from the network element is discriminated to include metadata information, steps S240 and S250 are executed. These steps S240 and S250 correspond to the steps S20 and S30 of the first embodiment, and thus detailed description thereof is omitted. In summary, the configuration in the operating system section 11 is executed based on metadata information received directly from the network element 12.

On the other hand, in step S230, when the adaptation information from the network element is distinguished to include identification data, steps S260 and S280 correspond to steps S130 and S150 of the second embodiment, and thus The detailed description is thus omitted. In summary, the configuration in the operating system section 11 is executed based on metadata information indirectly received from the network element 12, that is, by the network element metadata library 13.

In step S290, when the configuration process is terminated as in the first and second embodiments, whether it is received directly from the network element 12 or based on metadata received from the network element metadata library 13 Without that, the operating system unit 11 executes management of the network element 12.

Preferably, in the above embodiments, the format of metadata information to be transmitted is standardized for all network element types. Thus, it is possible for an operating system part that receives adaptation information (or metadata) to implement management mechanisms for various network elements.

[Industry availability]

The present invention is applicable to all network elements requiring management. For example, these network elements may include GSM network elements (BSC, BTS, MSC, GGSN, SGSN, SMSC, MMSC, etc.), 3G / WCDMS network elements, WLAN network elements, IP network elements (routers, hubs). , Switches, firewalls, gateways, etc.), server computers (ie, normal servers hosting web application software, web servers, file servers, printer servers, etc.), desktop PCs, PDAs, mobiles, etc. It includes.

With the present invention, it is possible for a communication management network or operating system to recognize a network element to which it is newly connected. Afterwards, the management mechanism is responsible for the processing of the new NE type and its data, ie the automatic modification of the relevant database tables in a way that the network element is manageable by the operating system or the creation of new tables, graphical user interface (GUI). You can modify them, send messages to the system, and so on. In other words, the present invention provides a mechanism for the operating system to prepare any network element of a particular type / release to prepare for connection to the operating system.

Adaptation of network elements and operating systems in a communications management network or operating system is possible with significantly reduced effort. The network element provides all the necessary information when first connected to the operating system. After this initialization step, the network element is manageable without the additional step required. This is done in that each network element describes itself with metadata. When the operating system connects to the network element, the operating system retrieves metadata (directly or indirectly) from the network element. By using metadata from the network element, the software of the operating system is configured such that the network element is manageable from the operating system.

As described above, mechanisms available in a communications management network system comprising a network element and an operating system portion have been described, where adaptation information is transmitted from the network element to the operating system after the network element is physically connected to the operating system portion. . The operating system configures one or more applications that are accessed using the adaptation information based on the metadata. Thereafter, the network element and all further network elements of the same type / release are manageable by the operating system unit.

Claims (48)

A method of managing a communication network comprising network elements and an operating system portion, the method comprising: After the network element is physically connected to the operating system portion, transmitting adaptation information from the network element to the operating system portion; Processing the adaptation information in the operating system unit; Configuring one or more applications in the operating system unit based on the adaptation information; And And executing the management process of the network element by the operating system unit. 2. The method of claim 1, wherein the adaptation information includes metadata defining portions of the network element manageable by the operating system portion. . The method of claim 1, wherein the adaptation information includes identification data of the network element. The method of claim 3, wherein After the step of processing the adaptation information, contacting a library network portion; Requesting, from the library network unit, further adaptation information for the network element based on the identification data; Receiving, from the library network unit, the additional adaptation information for the network element, Wherein the step of configuring one or more applications of the operating system unit is based on the additional adaptation information received from the library network unit. The method according to claim 3 or 4, And wherein said identification data of said network element comprises a type and release information of said network element. The method of claim 1, And wherein the adaptation information comprises one of metadata definitions of the network element or identification data of the network element manageable by the operating system portion. . The method of claim 6, After the step of processing the adaptation information, the network element further comprising determining a sort of the adaptation information to distinguish whether the network element transmitted metadata or identification data; A method of managing a communication network comprising an operating system unit. The method of claim 7, wherein Wherein if the determining step determines that the adaptation information includes metadata, configuring the one or more applications of the operating system portion is based on the adaptation information from the network element. A method of managing a communication network comprising elements and an operating system portion. The method according to claim 7 or 8, If it is determined by said determining that said adaptation information includes identification data, After the step of determining the type of the adaptation information, contacting a library network unit; Requesting, from the library network unit, further adaptation information for the network element based on the identification data; And Receiving, from the library network unit, the additional adaptation information for the network element, Wherein the step of configuring one or more applications of the operating system unit is based on the additional adaptation information received from the library network unit. The method of claim 1, The configuring step includes at least one of a configuration management subcomponent, a performance management subcomponent, an account management subcomponent, a security management subcomponent, and a defect management subcomponent. A method of managing a communication network comprising a system unit. The method of claim 10, The configuration includes the addition of features necessary for the visualization of the network element in the user interface, the limitation of operating and maintenance protocol implementation, the extension of the operating and maintenance protocol implementation, the structure of transmitted configuration management data, the transmitted performance management data. And a network element and an operating system portion, characterized in that it comprises at least one of the structure and meaning of the data, additional help text for defect management events, and adaptation to general operating system applications. The method according to claim 1 or 11, wherein The configuring step includes at least one of reconfiguring a database scheme, modifying related database tables, creating new database tables, modifying a graphical user interface, and modifying a messaging system. A method of managing a communication network comprising a system unit. The method of claim 1, Requesting the adaptation information from the network element by the operating system unit after establishing a physical connection between the network element and the operating system unit. How to manage it. The method of claim 1, A method for managing a communication network comprising a network element and an operating system portion, characterized in that implemented in a communication management network. A communication management network system for managing a communication network, comprising a network element and an operating system unit, comprising: Wherein after the network element is physically connected to the operating system portion, the network element is adapted to send adaptation information to the operating system portion, Wherein the operating system unit: A processor for processing the adaptation information in the operating system unit; And Configuration means for configuring one or more applications in the operating system unit based on the adaptation information, Wherein the operating system unit is configured to execute a management process of the network element. The method of claim 15, And wherein said adaptation information comprises metadata defining portions of said network element manageable by said operating system portion. The method of claim 15, And wherein said adaptation information comprises identification data of said network element. The method of claim 17, Further comprising a library network unit connected to the operating system unit, Wherein the operating system is: Means for contacting the library network portion; And Means for requesting further adaptation information for the network element from the library network portion based on the identification data included in the adaptation data from the network element; Wherein said configuring means is adapted to configure said one or more applications of said operating system unit based on said additional adaptation information requested and received from said library network unit. The method of claim 17 or 18, And said identification data of said network element comprises type and release information of said network element. The method of claim 15, And wherein said adaptation information comprises one of metadata definitions of a network element manageable by said operating system portion or identification data of said network element. The method of claim 20, And said operating system unit further comprises determining means for determining a type of said adaptation information to distinguish whether said network element has transmitted metadata or identification data. . The method of claim 21, The determining means is adapted to configure the one or more applications of the operating system unit based on the adaptation information from the network element when the determining means determines that the adaptation information includes metadata. Communication management network system for managing a communication network. The method of claim 21 or 22, Further comprising a library network unit connected to the operating system unit, Wherein the operating system unit: Means for contacting the library network portion; And Means for requesting further adaptation information for the network element from the library network portion based on the identification data included in the adaptation data from the network element, Wherein if the determining means determines that the adaptation information includes identification data, the configuring means configures one or more applications of the operating system portion based on the additional adaptation information requested and received from the library network portion. And a communication management network system for managing a communication network. The method of claim 15, The configuration means is adapted to configure at least one of a configuration management subcomponent, a performance management subcomponent, an account management subcomponent, a security management subcomponent, and a defect management subcomponent. Communication Management Network System. The method of claim 24, The configuration means may add features required for the visualization of the network element in the user interface, limit the implementation of operating and maintenance protocols, extend the operation and maintenance protocol implementation, structure of transmitted configuration management data, and transmit performance management. A communication management network for managing a communication network, characterized by executing a configuration comprising at least one of the structure and meaning of the data, additional help texts for defect management events, and adaptation to general operating system applications. system. The method of claim 15 or 25, The configuration means is configured to execute at least one of reconfiguring a database scheme, modifying related database tables, creating new database tables, modifying a graphical user interface, and modifying a messaging system. Network system. The method of claim 15, And said operating system portion further comprises requesting means for requesting said adaptation information from said network element after establishing a physical connection between said network element and said operating system portion. A device usable in a communications management network system for managing a communications network, configured by an operating system portion, and adapted to receive adaptation information from the network element after physically connecting a network element to the operating system portion, A processor for processing the adaptation information; And Further comprising means for configuring one or more applications in the operating system unit based on the adaptation information, Wherein said operating system unit is adapted to execute a management process of said network element. The method of claim 28, And wherein said adaptation information comprises metadata defining portions of said network element manageable by said operating system portion. The method of claim 28, And said adaptation information comprises identification data of said network element. The method of claim 30, Means for contacting a library network portion that is part of the communication management network system; And Means for requesting further adaptation information for the network element from the library network unit based on the identification data included in the adaptation data from the network element; Wherein the means for configuring is configured to configure the one or more applications of the operating system unit based on the additional adaptation information requested and received from the library network unit. Possible device. 32. The method of claim 30 or 31 wherein And said identification data of said network element comprises type and release information of said network element. The method of claim 28, The adaptation information comprises one of metadata definitions of the network element or identification data of the network element manageable by the operating system portion; and a device usable in a communication management network system for managing a communication network. . The method of claim 33, wherein Determining means for determining the type of the adaptation information to distinguish whether metadata is received or identification data is received. The method of claim 34, wherein The determining means is adapted to configure the one or more applications of the operating system unit based on the adaptation information from the network element when the determining means determines that the adaptation information includes metadata. A device available in a communication management network system for managing a communication network. The method of claim 34 or 35, Means for contacting a library network portion that is part of the communication management network system; And Means for requesting further adaptation information for the network element from the library network portion based on the identification data included in the adaptation data from the network element; Wherein if the determining means determines that the adaptation information includes identification data, the configuring means configures the one or more applications of the operating system unit based on the additional adaptation information requested and received from the library network unit. And a device usable in a communication management network system for managing a communication network. The method of claim 28, The configuration means is adapted to configure at least one of a configuration management subcomponent, a performance management subcomponent, an account management subcomponent, a security management subcomponent, and a defect management subcomponent. A device available in a communications management network system. The method of claim 37, The configuration means may add features required for the visualization of the network element in the user interface, limit the implementation of operating and maintenance protocols, extend the operation and maintenance protocol implementation, structure of transmitted configuration management data, and transmit performance management. A communication management network for managing a communication network, characterized by executing a configuration comprising at least one of the structure and meaning of the data, additional help texts for defect management events, and adaptation to general operating system applications. Devices available in the system. The method of claim 28 or 38, The configuration means is configured to execute at least one of reconfiguring a database scheme, modifying related database tables, creating new database tables, modifying a graphical user interface, and modifying a messaging system. Devices available in network systems. The method of claim 28, And requesting means for requesting said adaptation information from said network element after establishment of a physical connection between said network element and said operating system portion. A network element connectable to an operating system portion of a communication management network system for managing a communication network, comprising: Wherein after the network element is physically connected to the operating system portion, the network element is configured to send adaptation information available by the operating system portion to configure one or more applications within the operating system portion. A network element connectable to an operating system portion of a communication management network system for managing a communication network. The method of claim 40, And wherein the adaptation information includes metadata defining portions of the network element manageable by the operating system portion. The network element accessible to the operating system portion of the communication management network system for managing the communication network. 42. The method of claim 41 wherein And the adaptation information includes identification data of the network element. The network element connectable to an operating system portion of a communication management network system for managing a communication network. The method of claim 43, And said identification data of said network element comprises type and release information of said network element. 42. The method of claim 41 wherein The adaptation information is available to configure at least one of a configuration management subcomponent, a performance management subcomponent, an account management subcomponent, a security management subcomponent, and a defect management subcomponent. A network element connectable to an operating system portion of a communication management network system. The method of claim 45, The configuration includes the addition of features necessary for the visualization of the network element in the user interface, the limitation of operating and maintenance protocol implementation, the extension of the operating and maintenance protocol implementation, the structure of transmitted configuration management data, the transmitted performance management data. An operating system portion of a communication management network system for managing a communication network, comprising at least one of the structure and meaning of the data, additional help texts for defect management events, and adaptation to general operating system applications. Accessible network elements. 47. The method of claim 41 or 46, The configuration includes at least one of reconfiguring a database scheme, modifying related database tables, creating new database tables, modifying a graphical user interface, and modifying a messaging system. A network element accessible to the operating system portion of the. 42. The method of claim 41 wherein Means for receiving and processing a request for the adaptation information from the operating system portion after establishing a physical connection between the network element and the operating system portion. A network element accessible to an operating system portion of a network system.

Images