[go: up one dir, main page]

WO2000075802A1 - Commande de serveur adaptative et evolutive - Google Patents

Commande de serveur adaptative et evolutive Download PDF

Info

Publication number
WO2000075802A1
WO2000075802A1 PCT/US2000/011786 US0011786W WO0075802A1 WO 2000075802 A1 WO2000075802 A1 WO 2000075802A1 US 0011786 W US0011786 W US 0011786W WO 0075802 A1 WO0075802 A1 WO 0075802A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
server
request
service level
sufficient
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/US2000/011786
Other languages
English (en)
Other versions
WO2000075802A8 (fr
Inventor
Dickson K. T. Chan
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Sycamore Networks Inc
Original Assignee
Sycamore Networks Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Sycamore Networks Inc filed Critical Sycamore Networks Inc
Priority to AU49791/00A priority Critical patent/AU4979100A/en
Publication of WO2000075802A1 publication Critical patent/WO2000075802A1/fr
Publication of WO2000075802A8 publication Critical patent/WO2000075802A8/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5019—Ensuring fulfilment of SLA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H04L67/1012—Server selection for load balancing based on compliance of requirements or conditions with available server resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/10015—Access to distributed or replicated servers, e.g. using brokers

Definitions

  • the present invention relates generally to network management systems, and more particularly to a system for managing the scalability of a system including software and hardware resources.
  • the amount of work (or "workload") the combined hardware and software resources can process is known as the "capacity" of the system.
  • capacity In order for the system to process an increased workload, its capacity must be increased, often by adding hardware resources.
  • scaling The potential for the system to increase its capacity, with a minimum impact on performance and availability, is referred to as its "scalability".
  • the system should enable a network operator or manager to manage a network management system as its capacity limits are approached and reached.
  • the system should further enable a network operator or manager to effectively determine the hardware resources necessary to maintain a desired level of service within the network management system, m the face of an increasing workload.
  • a system for server process control including an administration server process which monitors the performance of a number of server processes and which is responsive to a minimum level of service that the system must meet when it accepts a request for service from a client system.
  • the minimum level of service is referred to as a Quality of Service (QoS) .
  • the server processes include a Network Management Server (NMS) of which the administration server is a part.
  • the QoS of the NMS is referred to as the QoNMS.
  • QoS or QoNMS may be specified by the user or the network operator on a per session basis, for example, within each request for service, or on a per user basis, or as a single value across all users and all sessions.
  • the system When the system accepts a request for service, it may create one or more additional server processes to provide service to the requesting user. The system further shuts down one or more unneeded server processes when the demand for the particular service type associated with those server processes falls below a pre-determined level. In addition, the system monitors utilization of hardware resources that are available to support future service requests. When the amount of available hardware resources drops below a predetermined threshold, the present system provides an alarm or other notification to the network operator or user.
  • the disclosed server control system efficiently manages the scalability of a software system without relying on simulation results, and alerts the user when additional hardware resources are likely to be required.
  • the disclosed system provides a predefined level of performance to each service user, automatically creates new server process instances as needed to meet increasing service demand, and adaptively deactivates server processes as demand decreases.
  • Fig. 1 is a block diagram showing the architecture of an illustrative embodiment of the disclosed system
  • Fig. 2 is a block diagram showing organization of software functionality in an illustrative embodiment of the disclosed system
  • Fig. 3 is a functional block diagram of an illustrative administration server
  • Fig. 4 is a block diagram showing operation of a service brokerage mechanism
  • Fig. 5 shows an illustrative host table
  • Fig. 6 shows an illustrative service instantiation table
  • Fig. 7 is a flow chart showing steps performed during operation of the disclosed system. DETAILED DESCRIPTION OF THE INVENTION
  • An illustrative embodiment of the disclosed system includes a client system 10, first server system 12, managed element 14, and second server system 16.
  • the client system 10 is, for example, a workstation, personal computer (PC) , or other microprocessor based system, and supports execution of software including a client process 18, shown for purposes of illustration as a JavaTM application within a Java Applet 20, which in turn is part of a Java Plug-in 22 executing in the context of a Web Browser 24.
  • a client process 18 shown for purposes of illustration as a JavaTM application within a Java Applet 20, which in turn is part of a Java Plug-in 22 executing in the context of a Web Browser 24.
  • the embodiments shown in Fig. 1 and elsewhere employ aspects of the JavaTM language and runtime environment developed by Sun Microsystems Inc., the invention is not limited to such implementations, and other appropriate computer programming languages and software runtime environments may be used in other embodiments of the invention.
  • the client process 18 communicates with a first server process 28 executing on the server system 12 via the Java RMI (Remote Method Invocation) protocol.
  • the server system 12 is also for example a workstation, personal computer, or other microprocessor based system.
  • the software executing on the server system 12 includes a server process 28, shown for purposes of illustration as a Java application executing on a Java virtual machine (VM) 30, within a Network Management Server 32.
  • the server process 28 also communicates via the Java RMI protocol with a second NMS server 34, which similarly includes a server process executing on a Java virtual machine (VM) , and which is also shown executing on the server system 12.
  • VM Java virtual machine
  • the server process 28 further communicates via Java RMI with a managed element object 36, shown as a Java application, executing within a run-time environment 38 such as TornadoTM for Java as provided by WindRiver SystemsTM, Inc., on a microprocessor based embedded system running a real-time operating system 40 such as VxWorksTM, also provided by WindRiver SystemsTM, Inc.
  • the first server process 28 further communicates via the Java RMI protocol with an element simulator process 42 executing on a Java virtual machine 44 within an element simulator process 46 on the second server process 16.
  • the embodiment of Fig. 1 provides several advantages. First, by executing the element simulator 46 in conjunction with the actual operation of other system components, more accurate estimates of system performance including the simulated element may be obtained.
  • Fig. 2 illustrates organization of software processes in an embodiment of the disclosed system.
  • an NMS Client 50 communicates with an administration server 52, which provides service brokerage and system administration services.
  • the NMS Client 50 further communicates with services 54, which include both a Java RMI registry, as well as an HTTP server.
  • the RMI registry stores RMI references to server processes on the local host.
  • the HTTP server within the services 54 communicates with a Remote Service Repository 56, which stores executable code of remote server processes.
  • the administration server 52 and services 54 operate within an NMS Server 51.
  • the NMS Server 51 further includes a number of managed server processes 58, database alert functionality 60, a database access interface 62, polling notification service 64, interrupt notification service 66, and network access functionality 68 for accessing the managed element in the embedded system 70.
  • the server processes 58 are shown including servers corresponding to network management layers defined in the telecommunications managed network (TMN) developed by the International Telecommunications Union (ITU) , including an element management layer (EML) , network management layer (NML) , service management layer (SML) , and business management layer (BML) .
  • TTN telecommunications managed network
  • EML element management layer
  • NML network management layer
  • SML service management layer
  • BML business management layer
  • the database alert functionality 60 and database access interface 62 communicate with the database server 72, which stores the host table and service instantiation table, and provides the associated database services.
  • Fig. 3 is a functional block diagram of an illustrative embodiment of an administration server and other software components in the disclosed system. As shown in Fig. 3, a service
  • a first service brokerage system 84 communicates with a first service brokerage system 84 through a user interface 82, which is for example a graphical user interface (GUI) .
  • Administration client software 90 communicates with the service brokerage system 84 through an administration interface 91.
  • the administration interface 91 provides the ability to add or delete a server instance on a host (as during an upgrade to a new server release) , modify the QoS or QoNMS thresholds for the system or a specified host, obtain a list of activatable server instances on a host, obtain a list of executing server instances on a host, create or shutdown a server instance, or obtain a status report with regard to executing server instances .
  • the service brokerage system 84 communicates with a second administration server 86, for example using the Java RMI protocol.
  • the service brokerage system 84 communicates with the database 88 through a database interface 93, which includes both database access and change notification functionality.
  • the change notification functionality is capable of notifying the service brokerage system 84 when pre-specified types of changes occur in the contents of the database 88.
  • the service brokerage system 84 also communicates with an RMI registry 94 through an RMI interface 92. Also in Fig. 3, a Java RMI activation system daemon (RMID) 98 is shown in communication with a number of managed server instances 96, as well as with the RMI interface to the service brokerage system 84.
  • RMID Java RMI activation system daemon
  • the managed server processes 96 are shown as FCAPS_1.0_00, FCAPS_1.0_01, FCAPS_2.0_00, FCAPS_2.0_01, in order to depict a variety of server processes within the OSI (Open Systems Interconnection) defined standard categories of Fault, Configuration, Accounting, Performance, and Security (FCAPS) management.
  • OSI Open Systems Interconnection
  • FCAPS Fault, Configuration, Accounting, Performance, and Security
  • each service type is given a name, for example DBEventService for database event servers, and each server process of that type is named DBEventServicelmpl.
  • An "incarnation number" representing the total number of server processes of the same service type that had been instantiated on the relevant host, at the time the server process was instantiated, and a release or version number of the server process are then both appended.
  • a server process with a name of DBEventServiceImpl_2.0_00 is a database event server instantiation (as indicated by the portion of the name "DBEventService”); is the second version or release of that server process (as indicated by the "2.0” appended value); and is the first instance of that service type to be created on its host (as indicated by the "00” appended value) .
  • Fig. 4 illustrates operation of a transparent service brokerage system, corresponding to the service brokerage system 84 in Fig. 3.
  • Fig. 4 shows how the present system operates to provide pointers (known as "references") to server instances on the host 110.
  • the references provided by the present system may be used directly in the local virtual machines of the remote systems 120 and 122. Because the references are for server instances that are remote to the systems 120 and 122, the references are considered to be, and referred to as "remote references”.
  • the remote references provided by the administration server in the illustrative embodiment are implemented using the Java Remote Method Invocation (RMI) protocol, but may alternatively be implemented using any other remote procedure call (RPC) mechanism which permits pointers to server object instances on a server system to be passed from the server system to a client system, and then permits the client system to refer to the server object instances as if they were local objects.
  • RRC remote procedure call
  • Such an alternative embodiment may, for example, implement the Common Object Request Broker Architecture (CORBA) , as defined by the Object Management Group (OMG) .
  • CORBA Common Object Request Broker Architecture
  • OMG Object Management Group
  • the host 110 is shown having a Java RMI registry 112.
  • the Java RMI registry 112 includes a number of entries which may be indexed by the administration server using • Uniform Resource
  • Locators in order to obtain Java remote references to the server instances associated with the entries.
  • Each entry within the RMI registry 112 contains an RMI reference corresponding to the URL which indexes that entry.
  • the RMI references in the RMI registry 112 correspond to server instances within the local host
  • the RMI reference 112a in the RMI registry 112 corresponds to the server instance "namel" as available on the
  • the RMI reference 112b in the RMI registry 112 corresponds to the server instance "name2" as available on "port 2" of the host 110
  • the RMI reference 112c in the RMI registry 112 corresponds to the server instance "name3" as available on "port 3" of the host 110.
  • Fig. 5 shows an illustrative embodiment of a host table, as is stored in the database 88 shown in Fig. 3, or in the database server 72 as shown in Fig. 2.
  • the host table includes entries (142, 144 and 146) which each store information regarding a type or category of server instances on a particular host system.
  • the information regarding a type of services on a given host includes the host IP (Internet Protocol) address 130, a ServiceName 132 indicating the service type, a QoSThreshold value 134 indicating the maximum number of server instances of the service type which can be created on the host system, a NumOfInstances value 136 indicating a current number of server instances of the service type which have been created on the host system, and a Version 138 which reflects the version of the current server instances of the service type on that host.
  • entry 142 contains information related to server instances that are of type ConfigService (configuration servers), on a host system having an IP address of 10.1.1.120.
  • Entry 142 indicates that no more than 100 instances of such servers may be created on that host at any one time, in order to provide the Quality of Service (QoS) that has been guaranteed to all users. Entry 142 further indicates that there are currently 5 instances of Version 1.0 ConfigService servers on the 10.1.1.120 host. Similarly, entry 144 indicates that for host 10.1.1.224, there are currently 2 instances of Version 1.0 FMService (fault management) servers, out of a possible maximum 10 instances, and entry 146 contains values indicating that one instance of a version 1.0 DBAccService (database access service) server is currently on host 10.1.1.224, out of a possible maximum 100 instances of that server type that may be created on that host. Fig.
  • QoS Quality of Service
  • the service instantiation table includes entries (170, 172 and 174), each of which contains information regarding the state of a server instance on a particular host. For a particular table entry, the location of the associated server instance is identified by a URL field 162, a status field value 164 indicates the current status of the server instance, a load field 166 value indicates the utilization level of the server instance, and the version of the server instance is shown by the contents of a version field 168.
  • a server instance that has been created may be in either the "Up” or "Activatable” state. A newly created process begins in the Activatable state. Upon the first reference to that instance, a fault occurs causing the Java RMID to activate the server instance. The server instance is then executing, and is considered to be in the Up state.
  • the load value 166 may represent the number of user sessions with the server instance associated with the entry, the average request queue length for each session with the server instance, the rate at which requests are being processed by the server instance, an error rate associated with the instance, the time that the instance has been executing, the number of threads of execution associated with the instance, or some other suitable statistic which would be useful in examining the current utilization of the instance.
  • the entry 172 contains field values indicating that an instance located at RMI://10.1.1.224:1099/FMService_2.0_00 is the 20 th incarnation of a server of type FMService on the host system, version 2.0, that it is currently executing, and that its current utilization is reflected by a load value of 9.
  • the entry 174 corresponds to a server process instance which is located at RMI://10.1.1.224/FMService_1.0_01, which is the 30 th incarnation of the service type FMService version 1.0 on the host system, and which is currently activatable. An instance that is not "Up” is not executing, and accordingly will have a load value of zero.
  • server instances are created, for example in response to configuration parameters provided by a network operator, they each register themselves in the RMI registry of their local host, as well as in the host table and service instantiation table data structures of the local administration server. More specifically, when a server process registers itself, it creates an entry in the service instantiation table as shown in Fig. 6.
  • the URL of the server instance is stored as an RMI reference, by prepending the IP address of the host on which the server instance is located, as well as the port number of the port on that host through which the instance is reachable, to the server instance name.
  • the server instance name DBEventServiceImpl_2.0_00 could have a URL field value in the service instantiation table of RMI://10.1.1.120:1099/DBEventServiceImpl_2.0_00.
  • This RMI reference would be used to bind a user request for a database event server to a remote reference to the specific server instance accessed through this RMI reference. In this way a JAVA remote reference is returned by the administration server to the client that made the service request. The client may then use the provided remote reference to invoke methods directly with the server instance. If the server instance is in the "activatable" state, the first such invocation will transition the server instance into the "up" state.
  • Fig. 7 shows steps performed during operation of the disclosed system.
  • Services are exposed to the client through a unified view of a service type that may actually be provided from various remote, shared resources.
  • the server instance that actually supplies the requested service is an implementation entity (a server or service "instance") that is hidden from the client except for a reference provided by the administration server which may be used by the client to invoke methods on the server instance as if it were located within the local client system.
  • the disclosed system acts as an intermediary between service users and service providers.
  • a service user instead of directly looking up a service implementation in the RMI registry, sends a service request 178 to the administration server, asking for a service by specifying the type of service that is needed. For example, if the user requires a configuration server, the service request 178 would simply indicate that a server process of type "ConfigurationService" was needed.
  • the service request 178 may also include a minimum level of service, or Quality of Service (QoS) that must be met for the request to be granted. Quality of Service may alternatively be provided by a system administrator on a system wide basis.
  • QoS Quality of Service
  • the specific parameters which are used to indicate the minimum Quality of Server may specify one or more of the following attributes of a server instance's performance:
  • the administration server analyses the current number and utilization of "available" server instances of type ConfigurationService (those that are either currently executing ("Up") and not fully loaded, or that are Activatable) , and the guaranteed Quality of Service (QoS) . Based on this information, the administration server determines at step 180 whether there are sufficient resources available in the system to grant the request. The administration server may also, at step 180, contact one or more candidate servers to determine whether they have sufficient available resources to provide the requested service. Alternatively or additionally, at step 180, the administration server may compare a requested minimum service level (QoS) contained within the request for service with a current system capacity, as determined at step 176, to determine if there are sufficient available resources to satisfy the request.
  • QoS requested minimum service level
  • step 180 is followed by step 182 at which point the request is denied. If the request can be granted, then step 180 is followed by step 184, in which the request is accepted and the administration server returns a reference to a server instance.
  • the reference returned at step 184 is a remote reference to a JAVA object that is the server instance, and that is executing on a server system that is remote from the client system from which the service request was received.
  • the reference returned at step 184 may be any pointer with which the requesting client can subsequently directly invoke methods on the server instance, without requiring the requesting client to perform any additional steps to determine the specific location the server instance.
  • the administration server creates any necessary server instances of the service type indicated in the service request 178. For example, the administration server creates a new server instance in the case where all currently executing server instances are fully utilized and the Quality of Server (QoS) related thresholds for maximum numbers of instances would not be exceeded. Subsequent invocations of the newly created server instance are performed directly by the client using the server reference provided by the administration, without intervention of the administration server.
  • QoS Quality of Server
  • activation of server instances occurs in response to the client's first use of the remote reference provided by the administration server.
  • Such activation is accomplished in the illustrative embodiment using the Java RMI object activation protocol, through the JAVA RMID activation daemon. Any other activation system providing persistent references to objects, as well as the ability to control object execution on an as-needed basis may alternatively be used for this purpose.
  • the system when an activatable server instance is accessed (via a method invocation) , if that server instance is not currently executing, the system initiates execution of the server instance within a JVM (Java Virtual Machine) on the server system.
  • JVM Java Virtual Machine
  • the utilization of each instantiated server is determined by the administration server using information within the host table (Fig. 5) and the service instantiation table (Fig. 6) . If the average load level for a given group of server instances of a single service type, for example as indicated by the load field contents of the associated entries in the service instantiation table, falls below a predetermined level associated with that service type, then some number of those server processes are identified at step 188 as being unneeded. The number of server instances identified as unneeded is such that if each unneeded server instance is shutdown, the average load level for the remaining server instances remains below a second predetermined level. If no server instances are identified that are unneeded, then step 188 is followed by step 192. Otherwise, step 188 is followed by step 190.
  • step 190 the server instances that were determined to be unneeded in step 188 are shutdown, for example using the Java RMID (Remote Method Invocation Daemon) utility, such that their state is changed from “Up” to "Activatable” in the service instantiation table. Resources necessary for execution of each shutdown process are deallocated, and thus made available for other processes.
  • step 192 the administration server determines whether the hardware resources of the system are loaded to a point where they are nearing their maximum processing capacity. This determination uses information stored within the host table and the service instantiation table.
  • the administration server determines that the difference between the number of instances of a particular service type on a particular host, and the Quality of Service (QoS) threshold for that service type on that host, is less than a predetermined value, then the administration server notifies the NMS client or network manager at step 194.
  • the notification may be through an electronic mail message, an alarm mechanism, or an entry in an event log that is accessible to the network manager or NMS client.
  • FIG. 7 Another feature of the embodiment of the disclosed system shown in Fig. 7 provides monitoring of the number of times that a request for service is denied at step 182. As this number increases, the network operator can assume that the capacity of the system has been or will shortly be reached. Accordingly, the administration server can be configured to automatically lower the minimum service level in response to the number of times requests for service are denied reaching or exceeding a predetermined limit. In addition, the administration server will lower the minimum service level in response to an indication to do so received from a network operator interface, such as the administration interface 91 as shown in Fig. 3.
  • a network operator interface such as the administration interface 91 as shown in Fig. 3.
  • the programs defining the functions of the present invention can be delivered to a computer in many forms; including, but not limited to: (a) information permanently stored on non-writable storage media (e.g. read only memory devices within a computer such as ROM or CD-ROM disks readable by a computer I/O attachment) ; (b) information alterably stored on writable storage media (e.g. floppy disks and hard drives) ; or (c) information conveyed to a computer through communication media for example using baseband signaling or broadband signaling techniques, including carrier wave signaling techniques, such as over computer or telephone networks via a modem.
  • non-writable storage media e.g. read only memory devices within a computer such as ROM or CD-ROM disks readable by a computer I/O attachment
  • writable storage media e.g. floppy disks and hard drives
  • information conveyed to a computer through communication media for example using baseband signaling or broadband signaling techniques, including carrier wave signaling
  • the invention may be embodied in computer software, the functions necessary to implement the invention may alternatively be embodied in part or in whole using hardware components such as Application Specific Integrated Circuits or other hardware, or some combination of hardware components and software. While the invention is described through the above exemplary embodiments, it will be understood by those of ordinary skill in the art that modification to and variation of the illustrated embodiments may be made without departing from the inventive concepts herein disclosed. Specifically, while the preferred embodiments are disclosed with reference to certain properties and features of the Java programming language and execution environment, the present invention is generally applicable to any other programming language or execution environment which provides persistent references to objects, peer-to-peer inter-process communication capabilities, and the ability to control object execution on an as-needed basis.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)

Abstract

Cette invention se rapporte à un système de commande de serveur, qui utilise un processus serveur d'administration (28) qui surveille la performance d'un certain nombre d'instances de serveur (12) et qui réagit à un niveau de service minimum que le système doit être capable de satisfaire afin d'accepter une requête de service de la part d'un système client (18). Le niveau de service minimum est appelé qualité de service (QOS). Parmi les instances serveur (12), on trouve un serveur de gestion de réseau (NMS) (51), dont le serveur d'administration fait partie. La qualité de service (QOS) du serveur NMS (51) est appelée QOSNMS. La qualité QOS ou le serveur NMS peuvent être spécifiés par l'utilisateur ou par l'opérateur réseau à chaque session, tels qu'indiqués par un opérateur réseau. Lorsque le système accepte une requête de service, il peut individualiser (instancier) une instance de serveur additionnelle, pour fournir le service à l'utilisateur qui en a fait la requête.
PCT/US2000/011786 1999-06-03 2000-05-02 Commande de serveur adaptative et evolutive Ceased WO2000075802A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU49791/00A AU4979100A (en) 1999-06-03 2000-05-02 Adaptive and scalable server control

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US13735499P 1999-06-03 1999-06-03
US60/137,354 1999-06-03
US41952199A 1999-10-18 1999-10-18
US09/419,521 1999-10-18

Publications (2)

Publication Number Publication Date
WO2000075802A1 true WO2000075802A1 (fr) 2000-12-14
WO2000075802A8 WO2000075802A8 (fr) 2001-06-21

Family

ID=26835169

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2000/011786 Ceased WO2000075802A1 (fr) 1999-06-03 2000-05-02 Commande de serveur adaptative et evolutive

Country Status (2)

Country Link
AU (1) AU4979100A (fr)
WO (1) WO2000075802A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2389481A (en) * 2002-06-07 2003-12-10 Hewlett Packard Development Co Maintaining availability of requested network resources
GB2389479B (en) * 2002-06-07 2005-12-28 Hewlett Packard Co Method of serving out video over a network of video servers
US7886042B2 (en) * 2006-12-19 2011-02-08 Yahoo! Inc. Dynamically constrained, forward scheduling over uncertain workloads
WO2011060810A1 (fr) 2009-11-17 2011-05-26 Nokia Siemens Networks Oy Gestion basée sur les caractéristiques
CN102148709A (zh) * 2011-02-25 2011-08-10 中兴通讯股份有限公司 一种实现主备单板升级的方法及装置
CN112416594A (zh) * 2020-11-30 2021-02-26 四川长虹智能制造技术有限公司 一种微服务分配方法、电子设备和计算机存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5341477A (en) * 1989-02-24 1994-08-23 Digital Equipment Corporation Broker for computer network server selection
US5668995A (en) * 1994-04-22 1997-09-16 Ncr Corporation Method and apparatus for capacity planning for multiprocessor computer systems in client/server environments
US5680325A (en) * 1995-08-24 1997-10-21 Bell Atlantic Network Services, Inc. Network capacity creation for video dial tone network
US5774656A (en) * 1994-05-06 1998-06-30 Hitachi, Ltd. Information processing system and method and service supplying method for use within a network
US6047322A (en) * 1997-05-27 2000-04-04 Ukiah Software, Inc. Method and apparatus for quality of service management
US6085222A (en) * 1997-07-31 2000-07-04 Fujitsu Limited Distributed communication system with adaptive data sending control in a computer network

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5341477A (en) * 1989-02-24 1994-08-23 Digital Equipment Corporation Broker for computer network server selection
US5668995A (en) * 1994-04-22 1997-09-16 Ncr Corporation Method and apparatus for capacity planning for multiprocessor computer systems in client/server environments
US5774656A (en) * 1994-05-06 1998-06-30 Hitachi, Ltd. Information processing system and method and service supplying method for use within a network
US5680325A (en) * 1995-08-24 1997-10-21 Bell Atlantic Network Services, Inc. Network capacity creation for video dial tone network
US6047322A (en) * 1997-05-27 2000-04-04 Ukiah Software, Inc. Method and apparatus for quality of service management
US6085222A (en) * 1997-07-31 2000-07-04 Fujitsu Limited Distributed communication system with adaptive data sending control in a computer network

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2389481A (en) * 2002-06-07 2003-12-10 Hewlett Packard Development Co Maintaining availability of requested network resources
GB2389479B (en) * 2002-06-07 2005-12-28 Hewlett Packard Co Method of serving out video over a network of video servers
GB2389481B (en) * 2002-06-07 2005-12-28 Hewlett Packard Development Co Method of maintaining availability of requested network resources
US7441261B2 (en) 2002-06-07 2008-10-21 Hewlett-Packard Development Company, L.P. Video system varying overall capacity of network of video servers for serving specific video
US7590746B2 (en) 2002-06-07 2009-09-15 Hewlett-Packard Development Company, L.P. Systems and methods of maintaining availability of requested network resources
US7886042B2 (en) * 2006-12-19 2011-02-08 Yahoo! Inc. Dynamically constrained, forward scheduling over uncertain workloads
WO2011060810A1 (fr) 2009-11-17 2011-05-26 Nokia Siemens Networks Oy Gestion basée sur les caractéristiques
US8768327B2 (en) 2009-11-17 2014-07-01 Nokia Solutions And Networks Oy Feature based management
CN102148709A (zh) * 2011-02-25 2011-08-10 中兴通讯股份有限公司 一种实现主备单板升级的方法及装置
CN112416594A (zh) * 2020-11-30 2021-02-26 四川长虹智能制造技术有限公司 一种微服务分配方法、电子设备和计算机存储介质

Also Published As

Publication number Publication date
WO2000075802A8 (fr) 2001-06-21
AU4979100A (en) 2000-12-28

Similar Documents

Publication Publication Date Title
US8082318B2 (en) Controlling service requests transmitted from a client to a server
US7412501B2 (en) Event consumers for an event management system
US6950874B2 (en) Method and system for management of resource leases in an application framework system
US7660887B2 (en) Systems and methods for providing dynamic quality of service for a distributed system
US7287179B2 (en) Autonomic failover of grid-based services
US7124062B2 (en) Services search method
EP1308844B1 (fr) Système et méthode pour surveiller une application sur un serveur
US8276166B2 (en) System and method for providing interoperability between different programming protocols
US8032623B2 (en) Context-based dynamic policy assignment in a distributed processing environment
US6732168B1 (en) Method and apparatus for use in specifying and insuring policies for management of computer networks
US20040167980A1 (en) Grid service scheduling of related services using heuristics
JPH11312153A (ja) オブジェクト・サ―バ間の作業負荷管理方法および装置
JPH0962523A (ja) 分散演算環境におけるイベント管理方法及びシステム
CN1968283B (zh) 一种网络管理的系统和方法
US20050138156A1 (en) Grid application customization
US7661030B2 (en) Propagating debug information in a web services environment
US8954584B1 (en) Policy engine for automating management of scalable distributed persistent applications in a grid
US20220174588A1 (en) Method for evaluating the devices of a network infrastructure for deploying a virtualised function
US7275250B1 (en) Method and apparatus for correlating events
US20090172158A1 (en) Memory management system and method for open platform
US20020174362A1 (en) Method and system for network management capable of identifying sources of small packets
US7908294B2 (en) Interoperable management of application servers
WO2000075802A1 (fr) Commande de serveur adaptative et evolutive
Hegering et al. Cooperative computing and integrated system management: A critical comparison of architectural approaches
US20020124087A1 (en) System and method for providing dynamic service using front-end

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AU CA JP

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE

121 Ep: the epo has been informed by wipo that ep was designated in this application
AK Designated states

Kind code of ref document: C1

Designated state(s): AU BR CA CN IN JP KR

AL Designated countries for regional patents

Kind code of ref document: C1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE

CFP Corrected version of a pamphlet front page

Free format text: REVISED ABSTRACT RECEIVED BY THE INTERNATIONAL BUREAU AFTER COMPLETION OF THE TECHNICAL PREPARATIONS FOR INTERNATIONAL PUBLICATION

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP