FI110976B - Method and system for managing services and appliances in a computer network - Google Patents

Description

110976

Method and System for Managing Services and Devices in a Data Network Method and System for Managing Attachments and Apparatus

The method and system of the invention uniformly manage a particular 5 distributed set of services provided in the data network and active devices of the data network. In particular, the management mechanism according to the method and system of the invention readily adapts to the changing needs of the information network.

Service providers and network operators are expected to deliver high-performance, reliable applications for business. Teleoperators and service providers have 10 ongoing needs to grow their network services to end users. Often, the product or solution that implements the service comes from a third party, such as Firewall (FW), Remote Access (RA), Authentication, or Virtual Private Network (VPN). When these services are adapted to the network of the operator and / or the end user, they are adapted to the system 15, service and device at a time. This means that the service provider adapts each product individually to its own system, and thus individual solutions do not support other solutions used in the same network. Separate management of services also complicates the distribution of services and customer relationship management. As new services and customers continue to flow, such an approach will become unworkable, because sooner or later there will be too many issues to deal with, and operations will become ineffective.

There are many different types of managed devices, ranging from computer servers and related databases to various routing devices. All of these devices are associated with a network size that is the property of one or more network operators, end users, and / or service providers. Larger companies and public organizations also have internal information networks with similar services. Management means adding, changing, deleting, and monitoring information and parameters related to the operation of a computer network or the services provided on the network.

• · «<

Generally, data management is the responsibility of the data network owner. For example, when a user needs to be added to a service, the network operator must add user information to each network element or database separately so that the new user can access that service. The user's information must be updated in several places whenever it changes.

110976 2

Attempts have been made to solve the problem, for example, by creating a centralized database of users. This allows users' information to be accessed by application and service programs in one place. However, the updated database must be accessible to all service-providing rigid systems, and the data in the database will not be passed unless the server being used specifically uses this database. In addition, there is a problem with the centralized database that the information contained therein can be updated in a data-processing program. However, in this case, the information is not updated in the database itself, but the update remains one or a few random changes to a particular application. As a result, the information does not remain consistent and the Salo ma information is worth different places.

An object of the invention is to reliably handle updates and other data management for each data network device and application. A further object of the invention is to provide a flexible system that is simply expandable as the number of users and / or services increases. It is a further object of the invention to provide uniform management of the various services provided by different suppliers 15 by means of a specific management concept.

The objective is achieved by directing data management directly to each object containing variable or new information through management applications and interfaces.

The invention is characterized by what is said in the character-20 character parts of the independent claims. Preferred embodiments of the invention are described in the dependent claims.

According to the invention, an interface is created for each application and service of the data network through which all necessary information is updated. Thus, a kind of interface (layer) is created to manage the units and services of a given network. The data may be scattered, that is, each unit of the network contains the information it needs, and there may not be a separate database at all. Data managed in this way is not cached, but directly exported to each active device and converted to the format required by a particular server or application using an interface. The created interface also updates information 30 to each system device and / or database where the variable information resides. Through this interface, the data passes through each variable unit and the flow of information through the interface can be monitored.

The management application of the invention and the interfaces allow centralized management of various server, terminal and / or database units, for example by means of a user-friendly graphical user interface. The entire rigid system is displayed on the graphical display to the one who manages and controls the units and services. The display can operate. mia, that is, to add services or change their properties for a particular unit. In addition, activities such as message delivery can be monitored in real time. Such a hal-5 price solution supports business processes and customer management, and significantly shortens delivery times. In addition, as process management becomes easier, the likelihood of errors is reduced and the progress of a simpler delivery process is easier to predict.

The invention makes it possible to reach the desired number of servers, active devices, data sets and databases of different manufacturers. Thus, existing products do not need to be renewed or adapted to a specific network, but act as independent units of their own. The management application and interface interface of the invention manages and maintains various data network units and services, and connects network devices controlled by a particular operator to the Services without interrupting the active service, since the client-client architecture of the invention does not require changes to the existing network. According to the invention, the client applications forming the interface interface take care of the transmission of messages between the terminal units and the necessary data collection in the data network. This enables centralized management of service-to-user services provided to both the user and the service provider. The user interface presented to the user may be based on forms or be a graphical representation of the data network. The management application according to the invention is partly a user-specific solution, which in each case depends on the number and quality of services and interfaces to be managed.

In the following, the invention will be described in more detail with reference to the accompanying drawings, in which Figure 1 illustrates a preferred embodiment of the invention, Figure 2 illustrates another preferred embodiment of the invention and Figure 3 illustrates an operation according to a preferred embodiment of the invention.

Figure 1 illustrates the operation of the system of the invention in general. The management applications and interfaces shown in Figure 30 1 are created by client applications 102 on a desired data network or on an administrative part of a particular data network. By using a client-type solution as a connector, the advantage is that standard connections to other systems and applications can be maintained. The client application 102 may be implemented, for example, as an XML (Extensible Markup Lan-110976 4 guage) description. The client application may be, for example, a Network Device Interface, a Network Device Interface, an NDI, or an Application Programmable Interface, an API.

Figure 1 illustrates a so-called Message-Oriented Type of Middleware (MOM) 101 for controlling a service network centrally and combining all the services of a given operator into one minimal entity. The functionality of the switching software 101 is based on network device-specific distributed client applications (client) connected to the network services. The relay software 101 takes care of the transmission of information; of what is conveyed and to them. 10 The information required for this is defined in a separate data structure. In practice, old data can be retrieved for viewing, for example, to write new data to replace old data, to delete old data or to add completely new data. The changed, new information is stored, for example, in a specific memory location, parameter table, or base from which the system can utilize it.

All units of the administrative entity are interconnected by means of a single service-specific component, the so-called client application 102 of the invention. The control tools are also connected to the system through their own client applications 102 and communicate with other servers and applications via the middleware 101. In Fig. 1, the control tool could be, for example, a terminal 103, from which the user could change any information or feature of the network from the input device.

The client application 102 converts the message received from the relay software 101 into such a format that the terminal unit 103, 104, 105 can process the message. The client application 102 then initializes the connection request to the respective terminal unit 103, 25 104, 105 and when the connection is established, the client application 102 forwards the message to the terminal unit 103, 104, 105. If the message arrives from the terminal unit 103, 104, 105 to the client application 102 in the format transmitted by their terminals 103, 104, 105. The client application 102 then converts the message here to a specific message transmission format required by the relay software 101, or generally. All descriptions and data structures can be converted into a format that can be utilized, processed and transmitted on computer networks. The message-oriented switching software (MOM) 101 duplicates the message and sends it to each client application 102 affected by the change made to the terminal unit 103, 104, 105.

5, 110976

Figure 1 shows, by way of example, possible terminal units which can be controlled by means of the refining process according to the invention. The client application 102 may be created between the switching software 101 and a particular terminal 103. The network terminals 103 may be, for example, a computer, a router, or a server. In addition to these, the client application 102 may provide communication and exchange of information between the relay software 101 and a database 104. The data in the database 104 may be retrieved and modified by the client application 102. At the same time, the client application 102 ensures that when the information in the database 104 changes, it is also updated to other locations where the changed information is located. The data format 10 of the database is not relevant to the invention, i.e. it may be any known data format. The client application 102 may also connect the switching software 101 to the terminal 105, which is associated with other terminals 105a and databases 105b. Such a terminal 105 may be, for example, a central machine of a local area network. In the embodiment of Figure 1, the client application 102 takes care of the information flow in the correct form to the terminal 15, database 104 and terminal 105, which further transmits the information to its own sub-devices in a manner known per se for this local area network.

Considering a solution of another preferred embodiment, wherein the rigid system of the invention is utilized when an operator provides corporate customers with services that include a secure connection between multiple local area networks (LANs), through a firewall and through a client-selected bandwidth (QoS, Quality of Service).

Figure 2 illustrates the main components of a rigid system according to another embodiment, which are advanced middleware 204, tool module 202 and Network Device Interface (NDI) module 203. In addition, a preferred embodiment of the invention includes a design tool called a Computer Aided Software Engineering) tool 201 to determine the properties and functionality of an operator's data network. CASE Tool 201 provides the necessary description of the software, configuration information, service network description, and documentation of the service provider or network operator system. CASE-30 Tool 201 is used to design and configure management and interface interfaces for a particular multi-service network, as well as customer-specific applications. It is a development tool that describes the multi-service network in question and executes management solutions.

'CASE tool 201 combines an object library and classes to ensure that the network management and interface interfaces to be created are implemented using to-35 specific and configured components. This design tool can be used to design only waste systems that are functional and whose components really exist.

The tool module 202 includes various environments and tools 202a each having its own client application, or client 202b, which provides an interface between the actual application 202a and the central module 204. Such environments 202a may be, for example, an end-user interface, an operator interface or a rigid system user interface.

The said interfaces refer to the basic solution for establishing a client interface. The user interface can be customer-specific or up to 10 user-specific, so that the user interface is customized to the preferences of each user. The user interface can be provided, for example, as a Java-based solution, over the Internet, or as a Windows-based application. User view is a graphical representation of the service structure. Management operations can be activated by icons and the graphical image also shows the current status of the network and the services. The user screen view is thus a real-time description of the services and management operations. The user can, in a manner known per se, such as clicking with the mouse or pointing to the display pen, control and manage the system within the limits of his predefined permissions.

Let's say a customer orders a firewall service for their office. He will only see Service-20 with his order, the stage of the delivery process, and the firewall's standby status. For example, if a customer wants to change the speed (quality of service, QoS) between two offices, he can do all the necessary operations just by clicking on the service icon. This icon opens a window with the necessary fields to change the behavior. The service provider monitors the licensed activity, making sure that only those who have the right to access the data can make changes.

The operator interface controls the operation and features of the system. The basic architecture is quite similar to the user interface. The main difference is that the operator interface features allow the management of all services and associated data. You can configure different user permissions in the operator interface, for example, some users can be given read-only access.

The system administrator user interface consists of so-called database windows that present data and property tables. These are used for technical or administrative purposes.

7 110976

The device interface module NDI of Figure 2, Network Device Interface 203, consists of separate software or device interface 203a controlled by the host machine or the middleware and a client 203b of each module. Client 203b takes care of communication between the device interface module 203a and the central module 204. These device interface-5 modules 203a may be various process or service software. Third-party services, ie, separate databases and network equipment, is also connected to a service network of separate application-specific control surfaces, client applications (client) allows. The control tool (s) are integrated into the system through their own individual client applications. These tools communicate with the other 10 services through their client applications, through some middleware. This kind of architecture is thus called client-client architecture (cf. known client-server architecture). The client-client structure shown here does not have a centralized server, but only active client-side applications that communicate with each other.

15 Further, a variety of device interface modules 203 are considered. One group of these device interface modules 203 are services embedded in the infrastructure, such as, for example, a graphical network viewer graphical application, an automated task or activity control application, and service quality applications. The graph application describes the current status of the network service. This allows both the customer and the service provider's staff to monitor the status of the services provided over the network in real time. The software used by the user of the device, that is, the client, operator or system administrator, is a graphical description of the services where the user can open a data page for a particular service by clicking on the icon.

The quality of service application includes tools for managing network access on a network using the Internet protocol 25. The quality of service application is intended, for example, for end users who have multiple offices that need different quality, perhaps even more varied. For example, the level of service, speed, bandwidth used, levels of security, etc. can be varied. Both the operator and the end user have a simple management program to customize these features.

30 The message monitor server is used to monitor the transmission of messages and the transmission of information. For example, it can be used to monitor the progress of an update operation on a data network. The necessary information is collected and transmitted to the units of the information network affected by the changes. The message monitor also takes care of making backups when needed.

110976 8

As yet another device interface module 203, external applications, which are in practice usually servers or databases, can be connected to the rigid system. These are integrated into the administrative entity of the invention by means of their individual client applications in the same way as other modules. Third-party service providers may, by agreement, be managed by either the service user or the service provider.

A preferred embodiment of the invention is based on messages sent by tool clients 202b and device interface clients 203b. The central module 204 controls these messages. The messages can be any text or binary information. The central module 204 has a dedicated messaging unit that takes care of communication between different client-10 applications by transmitting messages to the correct recipients. In addition, this messaging unit takes care of the authentication and authorization of the control tool and the client interface of the device. The messaging unit does not process the data, but only transmits the data to the target client. The business details of the data parts and instructions for each message are handled by the receiving client. The central module 204 itself handles only administrative messages for configuring the system itself.

Figure 3 illustrates the operation of a system according to a preferred embodiment of the invention. The flow of information in the system of the invention is illustrated by arrows. In this exemplary case, the user has a terminal and 20 is assumed to change his address information. The user's information in this data network is locally stored in the memory of his or her own terminal device and, for example, in a register maintained by the employer in a database of the network.

Initially, the user changes his address information on his own terminal. The data is changed in the terminal memory as the user saves it, and furthermore the terminal client receives information from the modified data 301. Here is shown a client application as a device interface with two partitions: the first part being the standard interface from the messaging software to the user interface. The second part is the device dependent interface to the terminal (terminal client, database client). The connection to the terminal (301, 306) may be established, for example, by the following protocols or protocol configurations: SQL (Structured Query Language), Radius (Remote Authentication Dial In User Service), Lightweight Directory Access Protocol (LDAP), Single Secure Shell (SSH). ), Telnet or API (Application Programmable Interface).

Next, the first section of the client application of the terminal transmits 35 messages into a generic form 302 where it can be transmitted to the central computer. Asia-9 110976.

the second part of the cash application (terminal client) sends a connection redemption request to the central computer MOM 303 and forwards the message over the opened connection. MOM organizes messages into a tree structure that describes a managed service network. The messaging unit of the central computer MOM ensures that this message is transmitted to all destinations of this information network with variable information. The messaging unit knows nothing about the actual content of the message. The messaging unit identifies the device that sent the message (authentication), possibly approves the user on the basis of a password (authorization), and forwards the message to the receiving client applications. Now the variable information is also located in the database maintained by the employer, so that the central messaging unit is able to send a change message to the client application 304 of this database.

In step 304, the change message may be sent to multiple target clients if the changed information is located in multiple locations within the data network. The changed information may be located, for example, in the memory, register, or table of a network device. In this example, for the sake of clarity, only a change to one network database is tracked. The message received by the client application is converted 305 into a format that is processed by the terminal, which in this example is a database. The database-side client (client) initializes the connection request to the database and forwards the message to the database 306 through the established connection. The address information thus changed by the user terminal 20 is also updated in the correct format to the employer's central database.

Alternatively, the client application, which can insert messages into the message tree structure of the relay software, informs the receiving client (client) that the message in question is obtainable from the server 25 of the relay software.

4

Claims (10)

1. A method for handling devices and the services they provide in a data network, which devices use management data stored in conjunction with them to offer services selectively, characterized in that it exhibits steps in which a message (301) is formed , which contains the handling data, - the formed message, which contains the handling data, is converted into the switching mode (302), - the message, which contains the handling data, and which is in the switching mode, is distributed via the data network (303, 304) to such object devices. connected stored management data is affected by the message, - a received message intended for each object device is converted into a mode in which the management data contained in the message is stored in connection to (305) object device, - converted management data is stored in connection to (306). the object device, and 20. stored management data is used to perform the selection as requested affected object device performs to provide services. A method according to claim 1, characterized in that device-specific client applications (102, 202b, 203b) are created which operate in connection with a certain central module (to handle devices and the services they provide in a data network). 101, 204). Method according to claim 2, characterized in that the message, which contains the handling data, is converted by the client applications (102, 202b, 203b) into the switching mode, in which it is further distributed to the central module (101, 204). 110976 Method according to claim 2, characterized in that the message, which contains the handling data and is in switching mode, is distributed via the message module of the central module (204) to such object devices (203) whose connected stored handling data is affected by the message. Method according to claim 2, characterized in that a message received in each object device is converted by the client application (102, 203b, 305) in the object device into a mode where the management data contained in the message is stored in connection with (306). the object device in question. Apparatus for handling devices and the services they provide in a data network, where the management data stored in connection with the devices for providing services is used selectively, characterized in that the apparatus has: - means for forming (301) messages which contains handling data, - means for converting the formed messages, which contain handling data, into switching mode (102, 202b, 203b, 302), means for distributing the message, which contains handling data and is in for switching mode, via the data network (101, 204) to such object devices whose connected stored handling data is affected by the message, - means for converting a received message in each object device (102, 202b, 203b, 305) into a mode in which the management data contained in the message is storable in connection with the message object device, - means for storing transformed handling data in connection with (306) the object device , and - means for using stored management data to perform the selection of the object device concerned to provide services. ; 25 Apparatus according to claim 6, characterized in that there are client applications (102), a central module (101, 204) and devices, and that the services these intermediaries have been arranged to be managed in a data network by means of the device-specific / customized client applications (102), which are connected to the device's central module (101, 204). Apparatus according to claim 7, characterized in that the apparatus has client applications (102, 202b, 203b) for converting the message, which contains handling data, into the switching mode (302), in which it is distributable further to the central module ( 101, 204). Apparatus according to claim 7, characterized in that the central module (101, 204) of the apparatus includes a message conveying unit for conveying a message, which is in a conveying mode and containing handling data, to such object devices (203) in the data network whose connected stored handling data is affected. of the message. Apparatus according to claim 7, characterized in that the apparatus has device-specific client applications (102, 202b, 203b) for converting a message in the switching mode of the object device to a mode (305) where the management data contained in the message is stored in the message. connection to the object device in question.