MXPA00010947A - Arrangement, system and method relating to communication - Google Patents

Abstract

The present invention relates to an arrangement, a system and a method of providing communication between clients (1A1, 1B1, 1C1) and managed systems (6A1, 6B1, 6C1) via managing systems (21). The clients communicate with the managing system over a first network (10) using an IP-protocol and a managing system(s) (21) communicate with a number of managed systems (6A1, 6B1, 6C1) over a second network (201). Each managing system (21) comprises a service management node with information handling means for separating addressing information from other information of an incoming message and for adapting the information to the communication protocol used for communication with the addressed managed system.

Description

ARRANGEMENT TO PROVIDE COMMUNICATION BETWEEN CLIENTS AND ADMINISTERED SYSTEMS FIELD OF THE INVENTION The present invention refers to the provision of communication between clients and managed systems through administration systems where the managed systems are particularly network elements, in a more particular way they have form of telephone exchanges. Particularly, the invention relates to an arrangement for providing communication between clients and managed systems through an administration system, and to a method and system wherein communication is provided between clients and managed systems. STATE OF THE ART Many telecommunication systems have an architecture that was developed in the seventies. At that time, the limitations and design considerations were different from today, CPU cycles (Central Processing Unit) were expensive and communication between computers was almost non-existent. Due to large investments in time and money it is practically impossible to replace these systems or replace the architecture. An example of a structure is the AX structure developed by Ericsson. It has been proven that this architecture could be extended very easily. Applications in this structure are written as function blocks. AX defines a structure for communication between function blocks and the administration of the function blocks has been standardized. The administration is handled by a command language that is known as Man Machine Language (MML) (Man-Machine Language) that is communicated in an X.25 connection. The MML Man-Machine Language is a language for telecommunications applications. It has a complex natural language syntax. It is further described in ITU-T, before CCITT recommendations Z.311-Z.318, Z-341, November 1984. Communication with AX is handled with the Message Transfer Protocol (MTP) in X.25. This combination is responsible for transferring a string of commands to the central AX and returning a direct printed string or transferring a file. A management program requires a programmatic interface with AX. Many different interfaces have been designed but unfortunately all these interfaces are dedicated to AXE (similar for other exchanges) which makes it very difficult to use standard applications since they are not aware of these highly specialized interfaces. Until recently this was not considered as a problem since the management of AXEs was handled by people highly skilled in the subject of the dedicated control centers. However, this has now changed, mainly due to two factors. First, the enormous growth of telecommunications in terms of quantity and quality, which has multiplied the need for administration. The large number of services available to subscribers today must also be maintained. Second, telecom operators are more aware of what is possible today and do not accept solutions that are not as good as what is offered in the market. Operators want well-designed graphical user interfaces and the (possibility of) integration with other vendors' tools. Systems are known that use what is known as CGI manuscripts. Systems of this type offer a wide range of possibilities to access resources and these systems are based on a standard conversion of an HTTP format. However, a sufficiently high performance is not achieved and also the characteristics depend on the platforms. In addition, such solutions are not satisfactory and do not offer a total total system solution in terms of managing a network that employs several independent management functions. In known systems, generally, the specific programmatic must be built for each database, each table, user information, intelligent programmatic, etc., with which it operates. Thus, a specific interface must be provided for each application, which greatly limits flexibility. COMPENDIUM OF THE INVENTION What is required is therefore an arrangement to provide communication between clients and managed systems through a management system that is flexible and through which a uniform way of communication with the different managed systems is allowed. In addition, an arrangement is required that allows the administration of a network using several independent functions in a uniform manner. In addition, an arrangement is required through which high performance must be accomplished to a greater extent than was previously customary and through which platform independence is provided. It also requires an arrangement that does not require specific interfaces for communication with particular managed systems, such as network elements, particularly telephone exchanges such as AX, PBX, etc. In addition, an arrangement is required through which the use of standard applications is facilitated. A system that includes a number of clients in which applications are run and a number of management nodes and a number of managed systems where clients communicate with the management nodes using a first network and the management nodes communicate with the systems administered using a second network is also required, through which the objects mentioned above can be achieved. A method is also required to provide communication between clients where applications are executed, and managed systems, through which the objects mentioned above are achieved. Accordingly, an arrangement is provided to provide communication between clients and managed systems through a management system where clients communicate with the management system using a first network using an IP (Internet Protocol). The administration system in turn communicates with several managed systems in a second network and the administration system comprises a service management node that includes information to separate and distribute means for separating the address information from other information of an incoming message. of a client and to adapt the information to the communication protocol that is used for a communication with -the managed system to which it is being directed. Particularly, an application that contains most of the logic is executed in the client and the information used by said application is supplied in a Uniform Resource Locator (URL) provided to the administration system. In addition, each managed system acts as a network server and has experience in this activity. The managed systems are preferably network elements which may consist particularly of telecommunication exchanges such as for example AXEs or the like. Alternatively, the exchanges can be PBXs (PABXs) (Central Automatic Private Branch). In a particular embodiment, the adaptation means includes several converters to convert an incoming URL to the protocol used for communication with the managed system to which it is addressed. Particularly, there is a converter for each type of system handled, particularly network elements or, even more particularly, telephone exchange, with which communication is provided through the administration systems. The administration node may also contain several gates for communication with the managed systems such as network elements, telephone exchanges, where the respective conversion devices communicate with said gates in a third protocol such as Telnet. In accordance with different modalities, conversion means and gates may be provided in a common entity but may also be provided separately in accordance with the above mentioned in said case they are communicated in a protocol. Particularly, the communication with each managed system, for example, NE or even more particularly, telephone exchange, is provided uniformly regardless of the type of the administered system (network element, telephone exchange). The clients can be controlled by operator, but they can also operate without an operator and for example they can be programmed to go through information at a given frequency, store said information and reproduce or represent the information in an appropriate way for the administered system. Advantageously, each client comprises logical or intelligent processing means to decide to which managed system, for example, network element, or type of network element, the information is to be sent. • Managed systems, or particularly network elements (telephone exchanges), are configured through the use of an MML language. In particular, the execution functionality in a client contains structured data for each type of managed system (see, network element, telephone exchange), and the client also contains devices for selecting syntax and information intended for the managed system in question. In the conversion device the information in URL format is converted or mapped in the MML format and a gateway can be used for communication with the relevant managed system or network element. An administration node that communicates with several clients through a first network and that manages numerous managed systems in a second network is also provided. The first network is an IP network that uses an IP protocol and URLs are used for communication with the node. The node comprises information separation and distribution devices for separating the address information of a managed system from other information and for adapting the information to the protocol used for communication with the managed system to which it is addressed. Particularly, the administration node contains numerous means of protocol conversion, one for each type of managed system, particularly network element. As mentioned above, the managed systems are profitably network elements, particularly telephone exchanges such as AXEs (Ericsson); S 12 (Alcatel); E SD (Siemens) or similar, PBXs etc. A system is thus also provided that includes a number of clients where applications are run, a number of management nodes and a number of managed systems. Clients communicate with the management nodes using a first network and the management nodes communicate with the respective managed systems using at least one second network. The first network is in accordance with the invention an IP network using an IP protocol and the information of the executed application is provided in URLs containing information regarding the relevant administration node and the administration nodes include means of separation and distribution of information for separating the address information of a managed system to which it is being addressed and means of conversion is provided to convert the protocol of the incoming information, URLs, to the protocol used for communication with the managed system to which it is addressed. In each administration node there is preferably a conversion means for each type of managed system with which the particular management node communicates. From the URLs, it can be deduced to which specific managed system (type of managed system) is addressed. Particularly, managed systems are network elements that can consist of telephone exchanges such as AXEs or similar PBXs, etc., where the administration node is comprised of a management system, for example, in the form of an operating system (OS) , see TMN, Telecommunications Management Network, ITU-T M.3010, or OSSs (Operation and Support Systems) (Operation and Support Systems).

Accordingly, a method is provided for providing communication between clients and managed systems wherein the applications are executed on the clients running the particular managed systems (or types thereof). The method comprises the steps of providing information about the application that is running on a URL, employing a first IP network to provide the URL information to the relevant management system that manages the managed system to which it is addressed, set in the administration system which is the managed system to which it is directed, convert information in the form of a URL to the protocol used for communication with the managed system to which it is addressed and provide information converted using a second network to the managed system to which it is addressed. As mentioned above, managed systems can be particularly telephone exchanges. Particularly, in the separate management system conversion means are provided for each type of managed system and upon receipt of the URL in the managed system, comprising an administration node, the URL is transferred to the appropriate conversion means using the information of addressing. In particular, MML is used for communication between the administration system and the managed systems and the conversion medium converts the URL format into the MML format. DETAILED DESCRIPTION OF THE INVENTION The present invention will be described further below, in a non-limiting manner with reference to the accompanying drawings in which: Figure 1 shows a first implementation of an arrangement according to the invention; Figure 2 shows a second implementation of an arrangement according to the invention, Figure 3A shows a third implementation of an arrangement according to the invention, Figure 3B shows an alternative to the implementation of Figure 3A, Figure 3C shows another alternative to the implementation of Figure 3A, Figure 4 schematically shows the provision of URLs to an OSS, Figure 5 schematically illustrates a further embodiment wherein a URL is provided to a management system, and Figure 6 is a diagram of schematic flow. BRIEF DESCRIPTION OF THE DRAWINGS In a particular embodiment, the present invention relates to a system in which several clients are operated through several different operators that have access to a service administration, functionality in an IP network, the Internet or an intranet. , where the service management functionality is used to control the implementation of a service in a network with several network elements. The service management functionality can obviously be distributed in several different ways and a substantial part of the functionality can obviously also be executed on the client. The protocol to network elements may differ both in content and syntax. The network elements are configured in a particular way with the use of some type of machine language, ie, ASCII-based commands and impressions, these commands and responses are communicated using some underlying protocol. The Man-Machine Language (MML) can have a very simple construction. The command identifier may consist of a two-character function block name and a three-character command name. Some commands accept parameters. This can be a unique key but in general it consists of an attribute name followed by an equal sign and one or more values. Multiple values are separated by the symbol (&). If the value is a range, then a double symbol (&) can be used to separate the start and end values. Multiple key values are separated by commas, and all commands must end with a semicolon. The same commands can be used frequently in different ways. Key / value pairs can be optional and some combinations of key / value pairs are not allowed. This is described in more detail in the recommendations of ITU-T Z.311-Z.318, Z.341 in accordance with the aforementioned in this document. According to the present invention, the Internet (or an intranet) is used. This has advantages, compared to the OSI standard in that connectivity is ubiquitous, practical and efficient and the protocols are easy to use. In addition, this allows many different implementations for the same protocol and the number of users in practice is unlimited. Due to the development in these areas, the development of the programmatic has changed considerably. Traditionally, a program contained a large set of functions that belonged to the program. The Internet has made it much cheaper to connect to services, that is, functions outside the program. This significantly reduces both the complexity and the size of the applications. However, this requires a protocol for communication. This protocol should be as generic as possible since you should be able to use a huge amount of existing protocols on the Internet. This need has resulted in a combination of Internet standards such as the Uniform Resource Locator (URL) (Uniform Resource Locator) and Multi Purpose Internet Mail Extensions (MIME) (Multiple Purpose Internet Mail Extensions). Information in an application running on a client, for example, one of the clients in Figure 1, client 1A, IB, 1C, is placed in a URL in such a way that it is easy to convert this information in a standard manner into the commands and impressions and responses of a network element, for example, Nes 6A, 6B, 6C. It is possible to use the inherent address possibilities of the URL to direct the appropriate network element using the correct protocol. A URL allows applications to retrieve objects through many different channels from completely different sources by simply specifying a string. The URL mechanism is very flexible and contains a protocol, for example, HTTP, although others can also be used, a guest address with a port and a resource identifier in this guest. The identifier can be a simple name, a path name on a disk or a request. Here are some examples of valid URLs: http: // homel. swipnet.se/~w-16844 ft: /r.ope swipnet There are strictly defined rules regarding URLs such as what characters can be used and what rules apply. The HTTP protocol specifies a request format for a URL. The format of this petition is: <; query identifier > ? key = value [+ key = vaiue ..] When it is directed to an object, it is retrieved and enters the receiver system. The receiver either knows the type of the object or does not know the type of the object. In traditional systems, the receiver generally knows the type of the object. When someone retrieves a fax from a fax machine, they wait for a fax and not an email. When a computer program reads an email from a Simple Mail Transfer Protocol (SMTP) server, it waits for the family format 'and not a file in binary graphics exchange format. However, all this requires that the sender and receiver share a common model of the information they exchange. Common knowledge is always very difficult to maintain. This object typing problem is handled with MIME. MIME is an Internet standard to define a unique type code. It is described for example in RFC ((Request for Comment) by IETF (Internet Engineering Task Force Standars) (MIME 1521 and 1522 Multipurpose Internet Mail Extensions) (Extensions of Internet Mail for Multiple Purposes) to specify and describe the format of Internet message bodies (wv, - .. org.) RFC 1630 describes Universal Resource Identifiers on WWW and RFC 1738 refers to Uniform Resource Locators The only type code consists of two parts, a class identifier and a specific type, exact codings are defined through a standard body and companies that want to use a type of MIME Private can use this by adding a prefix to their codes with x- .. Some examples of MIME types are for example: application / postscript text / x-vCalendar video / quickt ime model / vrml An important amount of programmatic can be reduced in terms of complexity when coding objects with MIME. Since the objects are now self-classified, it is possible to reuse codes that would have to be unique if they were related to an object type. In addition, the MIME typing scheme allows a simple extension scheme. Java © and Netscape allow, for example, the installation of handlers of certain types. A URL makes the user of a resource virtually independent of the provider of the resource. Both parties are aware of the URL (and MIME) but neither party is aware of the other. This makes possible completely independent developments in the two parts since each independently developed product can continue to cooperate to achieve a task. The commercial WWW browser, Netscape, is fully described in the many services it currently uses and many services have been created without knowledge of the fact that they would be used in Netscape. It is therefore extremely beneficial to have access to a network element such as a telephone exchange, particularly AXE, even if obviously other exchanges or also possible and also PBXs, on the Internet using URLs If an MML command is specified as a URL with the request syntax, many tools become available. If the command: bgbgp: bg = lme; It is available through a URL: http: // dor is. ax. e icsscr .. se / bgbgp? bs = lr;; _ the following lines would have the form defined in HTML for any WWW browser. < PRE > < FORM actino = http: // dops. ax / bgbgp > BG < INPUT type = "text" name = "BG" value = "ALL" > < input type = "submit" value = "BGBGP" > < / FORM > < / PRE > This form would send the command to the http server at doris.axe.ericsson.se and the server would translate to the MML command, send it to AXE with the name DORIS and return the resulting print in the form of a text file. The WWW browser displays this text for the user. However, the URL can also be used from a programming language. A Java type language has extensive support for manipulating URLs. In Figure 1, clients 1A, IB, 1C communicate with a management system, particularly service management node 2 through a first network 10, for example an IP network. The administration system of the service management node 2 communicates with several network elements NE 6A, 6B, 6C in a second network 20. In the administration system 2, distribution and adaptation means 3 are provided to adapt the information of a network. incoming message from a client addressed to one of the network elements and to distribute the information to the intended network element and to adapt it to the form of the protocol employed between the administration system 2 and the respective network element 6A, 6B, 6C. A mapping is then carried out from a URL to MML and it can be said that the network elements are those used as WWW servers. If there is more than one administration system or service management node, the URL contains information about directing the information to the correct administration system. In Figure 2, an alternative modality is shown. Here also several clients lAi, 1BX, lCi communicate through an IP network 10-. with a service management node 2_ which in turn communicates through a second network 20 ?, for example, an X.25 network with several elements of "network 6A ?, 6B ?, 6C?. Service administration 2 is divided here into a conversion means and a gate part 5, between which a communication interface is used, such as Telnet.The network elements 6A ?, 6B ?, 6C ?, can be for example, telephone exchanges such as AXEs or similar, but also PBXs More generally, network elements are managed systems managed by the administration system, through the invention it is possible to have a very large amount of logic or "intelligence" that runs on a client and also to be a network element, or even a complete network acting as a WWW server with high performance.Specially, the execution of functionality in a client has structured data for each kind of network element and the choice of syntax and exact information for its transfer to a network element is selected in the client where the actual distribution to the correct address is made in the underlying management node 2 \. The conversion from the URL format to the final format and the protocol is done step by step, first converting the specific URL structure to the MML sent in a common protocol and then using different gates 5: which communicate with the use of specific protocols for parts of the networks. They may also have a substantial intelligence regarding the transformation of sessions. The information to build the Human-Machine Language strings in the URL is preferably divided into a primary string and a longer information string. The first string is preferably five characters long and is constructed in accordance with specific criteria so it can also be used as a basis for reviewing allowed operations in a distributed manner. Particularly, the primary string can be constructed in accordance with specific criteria which makes it useful as an address device as well. In Figure 3A, another embodiment is illustrated in which two clients 1A ?, 1B2, communicate with a service management node 22 through an IP network 102. The service management node 22 in turn communicates through of X.25, 20Ai, 20A networks: and through another 20A3 network with numerous network elements, in this case telephone exchanges, in second networks 20A ?, 20A2, 20A3. In this case, the 20A ?, and 20A2 networks are X.25 networks. Through the inherent routing mechanism of the IP network, the incoming URLs are sent to the appropriate conversion device for the particular type of network element to which they are addressed. Thus, in this case, there are three types of network elements, therefore there are three different conversion means C0NV1, 421, C0NV2 422, C0NV3 423, one for each type of network element managed by the service management node 22. With each conversion means 42i, 422, 4_3, a gate G / Wl, G / W2 and G / W3, respectively, is associated. G / Wl communicates through a second 20A network with AXElí, 6Au, AXE2? 6A2i, and AXE3 ?, 6A3_ where the index 1 in this case indicates that they are of the same type. G / W2 communicates with AXE12, 6BX2 and AXE22 6B2 which are also of the same type while G / W3 communicates through another network with a network element PBX 6C2. Obviously, there may be more than one service management node. This is illustrated in Figures 3B, 3C. The URL is also used to find the appropriate service management node. Figure 3B shows a modality similar to the modality of Figure 3A, but in this case there are two service administration nodes 2A2, 2B; Service management nodes generally have different physical or geographical locations, that is, they can be found in different cities. Here the node 2A2 contains a conversion device CONVl and gate G / Wl for communication with network elements 6 n, 6A2 ?, 6A31. (The reference numbers are the same as those in Figure 3A, simply for reasons of simplicity, however, it is clear that the configurations could be very different). The other node 2B contains C0NV2, C0NV3 which, through G / W2, G / W3 communicate with the network elements 6A12. 6A22 and 6C2 respectively. Figure 3C shows another modality in which three nodes 2C2, 2D2, 2E2, which can be provided in different geographical locations even though they may also be in the same geographical location. Here, each node contains only one converter and one gate and each node communicates with a number of network elements through a network. Obviously, several clients, nodes and network elements are possible as well as the arrangement in different nodes, the types of network elements are not limited to the modalities illustrated here but may be different. Obviously also any number of types of network elements is possible and it is also possible to use the same network but different protocols for communication with a particular type of network element. Telephone exchanges obviously do not have to be AXEs and PBXs (such as for example Ericsson MD110) but they can be of any type of any combination of telephone exchanges. However, it will be clear that the invention is not limited to the telephone exchange (here we refer to both public and private exchanges), but it can also be applied to other types of managed systems, for example, network elements administered by a management system that receives applications executed on a client. Figure 4 schematically illustrates a URL entering an administration system 23 in the form of an OSS (Operation Support System) 23 comprising a conversion means 43 since in this case there is just one type of network elements, ie AXE1 6A3, AXE2 6B3, AXE3 6C. Similarly, an implementation is illustrated in Figure 5. A URL is entering an administration system, here in the form of an OS 24 operating system that acts as a network server where a small server 74 is connected to provide communication with a gate 54 that in turn communicates with a telephone exchange ß4. Operating system 2 < It also supports access to database DB 84 and the like, for example, using CGI. Figure 6 is a schematic flow chart that presents the essence of the concept of the invention. First the information of an application running on a client is placed in a URL, 100. The URL is then provided (using the inherent address properties of the URL 100) to the appropriate administration system using a first network, using a protocol of IP, 101. When the URL is received in the administration system, particularly a service management node, the URL address functionality, or the address scheme is used to establish what type of network element it is to it directs NE, 102. The appropriate converter is then called 103, and the address information is separated from the rest of the information and the URL is provided to the appropriate conversion means that handles the type of NE to which it is addressed, 104. In the means of conversion, the information in a URL format is converted into an MML format or more generally the protocol used for communication with a particular NE to which it is addressed. 105. The information is then provided to the NE to which it is addressed, 106. It is clear that the invention is obviously not limited to the modalities presented in particular, but may vary in many ways within the appended claims.

Claims (23)

1. CLAIMS An arrangement to provide communication between clients (1A, IB, 1C; 1A-., LBi, Id; 1A2 1B2) and managed systems (6A, 6B, 6C; 6A ?, 6B1, 6C-; 6An, 6A2_. 6A3? , 6Ai2, 6A22, 6C2; 6A3 6B3 6C3, 6) through a delivery system (2; 2X; 22; 2A2; 2B2; 2C2; 2D2; 2E2), where the clients (1A, IB, 1C; lAi, lBi, Id, A2, 1B2) communicate with the administration system (2; 2_; 22; 2A2; 2B2; 2C2; 2D:; 2E2) in a first network (10; Id; 102;) using an IP protocol, the administration system (6A, 6J3, 6C; 6A1, 6B1, 6C_; 6An, 6A2i, 6A3 ?, 6A12, 6A22, 6C2; 6A3, 6B3, 6C3, 64) communicates with numerous administered systems (20; 20 ?; 20A 20A2; 2OA3) in a second network (20; 20 ?; 20AX, 20A2, 20A3), characterized in that the administration system (2; 2?; 22; 2A2; 2B2; 2C2; 2D2; 2E2) comprises a node of administration of services that includes means of separation and distribution of information to separate address information from other information of a. incoming message and to adapt the information to the communication protocol used for communication with the managed system to which it is addressed (6A, 6B, 6C; 6AX / 6B ?, 6C1; 6A1X, 6A21, 6A31, 6Ai2, 6A22, 6C2; 6A3, 6B3, 6C3. 64) and because a main part of the logic is in an application that is executed in the client (1A, IB, 1C; 1A :, 1B_, Id; 1A2, 1B2) and because the information used by said application is provided in a Uniform Resource Locator (URL) (Uniform Resource Locator) provided to the administration system (2; 2-_; 22; 2A2; 2B2; 2C2; 2D2; 2E).
2. An arrangement according to claim 1, characterized in that each system administered (6A, 6B, 6C; 6A ?, 6B ?, 6d; 6An, 6A2i, 6A3 ?, 6A12, 6A22, 6C2; 6A3, 6B3, 6C3, 64) acts as a network server and has experience in that activity.
3. An arrangement according to any of the preceding claims, characterized in that the administered systems (6A, 6B, 6C; 6A1, 6B_, 6d; 6Au, 6A2 ?, 6A31, 6Ai2, 6A22, 6C2; 6A3, 6B3, 6C3, 64) they are network elements.
4. An arrangement according to claim 3, characterized in that the network elements consist of telecommunication exchanges, for example AXEs.
5. An arrangement according to claim 4, characterized in that at least one of the network elements (6C2) is a PBX.
6. An arrangement according to any of the preceding claims, characterized in that the adaptation device comprises several converters (3; 4; 421; 422; 423; 43; 74).
7. An arrangement according to claim 6, characterized in that the administration node (s) contains (n) in addition a number of gates (5 ?; 54) for communication with the managed systems (6A, 6B, 6C; 6A; : 6B ?, 6d; 6AU, 6A ::, 6A31, 6A12, 6A22, 6C2; 6A3, 6B3, 6C3, 64), particularly the network elements, the converters (4; 42 ?, 422; 43; 43; 14) that communicates with the gates in a third protocol, for example, Telnet.
8. An arrangement according to claim 6, characterized in that the administration node (s) in addition to adaptation devices contain (n) several gate means and that the respective conversion means and corresponding gate means are combined in a common entity (2; 22; 22; 2A2; 2B2; 2d; 2D2; 2E2).
9. An arrangement according to claim 7 or according to claim 8, characterized in that there are several different types of managed systems, particularly network elements, with an adaptation device comprising conversion means for each type of managed system or element of network in the administration node.
10. 10. An arrangement in accordance with the claim. 9, characterized in that the communication with each administered system (6A, 6B, 6C; 6A ?, 6B ?, 6d; 6A_ ?, 6A21, 6A3 :, 6Ai2, 6A22, 6C2; 6A3, 6B3, 6C3, 6), for example , NZ, is provided uniformly regardless of what type of system is administered, for example NE.
11. An arrangement according to any of the preceding claims characterized in that the client (1A, IB, 1C; 1A :, IB., Id; 1A2 1B2) operates without an operator and because it is programmed to search for information at a given frequency, to store said information and to reproduce information in an appropriate manner.
12. 12. An arrangement according to any of claims 1-10, characterized in that the customer (1A, IB, 1C; lA ?, lBi, Id; 1A2, 1B2) is controlled by operator.
13. 13. An arrangement according to any of the preceding claims, characterized by each client (1A, IB, 1C; 1A2, 1BX, Id; 1A2, 1B2) comprises - processing means that contain logic to decide which managed system (6A, 6B, 6C; 6A_, 6B? , 6C?; 6An, 6A2i, 6A31, 6Ai2, 6A22, 6C2; 6A3, 6B :. , 6C3, 64), for example, network element, or type of network element, the information must be sent.
14. An arrangement according to any of the preceding claims, characterized in that the administered systems (6A, 6B, 6C; 6A :, 6B1, 6C_; 6An, 6A21, 6A3- ,, 6A12, 6A22, 6C2; 6A3, 6B3, 6C3, 64), particularly network elements, are configured by using the MML language.
15. An arrangement according to any of the preceding claims, characterized in that the execution functionality in a client (1A, IB, 1C; lAi, 1B2, lCi; 1A2, 1B2) contains structured data for each type of a number of system types administered (6A, 6B, 6C, 6A ?, 6B ?, 6d; 6An, 6A2 ?, 6A31, 6A12, 6A22, 6C2; 6A3, 6B3, 6C3, 64), (NE) and because the client also contains means to select syntax and information for the administered system (6A, 6B, 6C; 6AX, 6B_., 6C? 6An, 6A21, 6A3i, 6AX2 6A22, 6C2; 6A3, 6B3, 6C3, 64).
16. An arrangement at least in accordance with claim 1, characterized in that in the conversion medium (3; 4_; 421, 422 423; 43; 74) the information in URL format is converted (mapped) into the MML format and because it is employs a gateway for communication with the relevant managed system, particularly network element.
17. An administration node (2; 2 ?; 22; 2A2; 2B2; 2C2, 2D2, 2E2; 23; 24) that communicates with a number of clients (1A, IB, 1C; lAi, lBi, lCi; 1A2, 1B2) through a first network, said administration node handles a number of managed systems (6A, 6B, 6C; 6A :, 6Bi, 6d; 6An, 6A21, 6A3 ?, 6Ai2, 6A22, 6C2; 6A3, 6B3, 6C3, 64) in a second network (20; 20x; 20A ?, 20A2, 20A), characterized in that the first network is an IP network that uses an IP protocol, the URLs are used for communication with the administration node (2; 2; 22; 2A2 / 2B2; 2C2, 2D2, 2E2), and in that the management node comprises information management devices for separating the address information that is directed to a managed system from other information and for adapting the information to the protocol used for communication with the administered system to which it is directed (6A, 6B, 6C; 6Ai, 6B1, 6C1; 6Au, 6A2i, 6A1, 6A: 2, 6A22, 6C2; 6A3, 6B3, 6C3, 64), 6A) in the second net.
18. An administration node according to claim 17, characterized in that it comprises a number of protocol conversion devices (4 ?, 42?> 422, 423; 43; 74), one for each type of system administered, particularly one of net.
19. An administration node according to claim 17 or 18, characterized in that the managed systems are network elements, for example, telephone exchanges such as AXEs or the like, PBXs, etc.
20. A system that includes numerous clients (1A, IB, 1C; lAi, IBi, 1C_; 1A2, 1B2) where applications are executed, numerous administration nodes (2; 2:; 22; 2A2, 2B2; 2C2, 2D2, 2E2 ) and numerous administered systems (6A, 6B, 6C, 6A ?, 6B ?, 6d; 6An, 6A2i, 6A3i, 6A? 2, 6A22, 6C2; 6A3, 6B3 6C3, 64), where clients (1A, IB, 1C; lAi, lBi, lCi; 1A2, 1B2) communicate with the administration nodes (2; 22; 2A2; 2B2; 2C2; 2D2, 2E2) using a first network, the administration nodes communicate with the administered systems (6A, 6B, 6C; 6A ?, 6B ?, 6C ?, 6An, 6A2l, 6A3i, 6Ai2, 6A22, 6C2; 6A3, 6B3, 6C3, 64), 6C3 / 6), employing a second network, characterized in that the first network is an IP network that uses an IP protocol, the information of the executed applications is provided in URLs that contain information regarding the relevant administration node (2); 2X; 22; 2A2, 2B2; 2C2, 2D2, 2E2) and because the administration nodes include means of separating and distributing information to separate address information from a managed system to which it is addressed (6A, 6B, 6C; 6A1, 6B !, 6C1; 6An, 6A2 ?, 6A31, 6A12, 6A22 / 6C2; 6A3, 6B3, 6C3, 64), and conversion devices (3; 4¡; 421, 422, 43; 43; 74) provided for conversion from the incoming information protocol to the protocol used for communication with the managed system to which it is addressed.
21. 21. A system according to claim 20, characterized in that there is a conversion means for each type of managed system with which a particular administration node communicates.
22. 22. A system according to claim 20 or according to claim 21, characterized in that the managed systems are network elements, particularly telephone exchanges, such as AXE or similar, PBX etc.
23. 23. A method for providing communication between clients and managed systems, where client applications are executed, characterized in that it comprises the steps of: - providing information of the. implementation application in a URL, use a first IP network to provide URL information to the relevant administration system that manages the managed system to which the information is directed, - establish in the administration system what is the type of the system administered to which the information is directed, convert the information in the form of URL to the protocol used for communication with the managed system to which the information is directed, provide the information transferred using a second network to the managed system to which the information is directed. A method according to claim 23, characterized in that the managed systems are network elements, particularly telephone exchanges such as AXE and the like, PBX, etc. A method according to claim 23 or according to claim 24, characterized in that, in the administration system, separate conversion means are provided for each type of managed system, particularly network elements or telephone exchange. A method according to any of claims 23-25, characterized in that an MML is used for communication between the administration system and the managed systems and because in the conversion device the URL format is converted into MML format.