Virtual network management
Claim Score by NHIP
Abstract
A system providing for virtual network management is disclosed. A system in accordance with the present invention allows a service provider to remotely manage one or more client network management systems. The security of the client network management systems is advanced by only allowing communications between a client network management system and the service provider that have been initiated by the client network management system. A mirror image of a client network management system is maintained by the service provider as a virtual network management system. Data included in the virtual network management system is periodically updated with data received from the client network management system. Instructions or data may be passed from the service provider to the client network management system in reply to communications initiated by the client network management system. The present invention is particularly useful in connection with the remote management of client networks with respect to which security is a concern.

Term
Term ended
Projected expiry passed 5 March 2024, 2.6 years ago.
- Priority and filed
- Published
- Projected expiry
- Today
20 claims: 3 independent, 17 dependent
- 1Broadest claimClaim Score 77, broad(NHIP)A method for remotely managing a network, comprising:providing a client network comprising a client network management system;providing a service provider network management system;providing a communication link between said client network management system and said service provider network management system;initiating in said client network a communication addressed to said service provider network management system, wherein said service provider network management system cannot initiate communications with said client network.
- 9A system for remotely managing a network, comprising:a client network, comprising: a plurality of communication nodes;a communication link interconnecting said nodes;a client server;a service provider network management system, comprising: a communication network interconnecting said client network and said service provider network, wherein communication between said client network and said service provider network may be initiated by said client network and may not be initiated by said service provider network.
- 15A method for remotely managing a client network from a service provider network management system, comprising:receiving at said service provider network a first communication;generating a response to said first communication, wherein said response comprises at least one of substantive information related to operational aspects of a client network and a request for data, and wherein a communication initiated by said service provider network will not receive a response from said client network.
Independent claims3
35 paragraphs in 5 sections, as filed
FIELD OF THE INVENTION
[0001] The present invention relates to virtual network management. In particular, the present invention relates to managing client networks from a remote location.
BACKGROUND OF THE INVENTION
[0002] Computer networks are vital to the operation of many business enterprises. Such networks include interconnected computers, telecommunications systems, or converged environments in which voice and data are passed across a common network. Because such networks provide functions that are critical to the operation of business enterprises, their maintenance is of considerable importance.
[0003] In order to maintain and troubleshoot networks, outside service providers may be employed. If outside service providers are provided access to the client network, many maintenance and repair operations can be performed remotely. However, remote access to a client network is often undesirable from the perspective of the client, as the access channel provided for the service provider can be exploited by third parties. For example, modem access in connection with software, such as PC ANYWHERE, that allows for the remote operation of computer systems, can potentially be exploited by unauthorized persons to access the client network.
[0004] In order to address client concerns regarding network security, virtual private networks, firewalls, and password protection has been utilized. However, such solutions can add expense to the operation of a network, and have certain vulnerabilities.
SUMMARY OF THE INVENTION
[0005] The present invention is directed to solving these and other problems and disadvantages of the prior art. Generally, according to the present invention, a client network management system is interconnected to a communication network, such as the Internet. According to the present invention, the client network management system may contact a service provider network management system over the communication network to post various types of information. In reply to the posting, the service provider network management system can request additional data, or provide updated configuration information, code, or both updated configuration information and code to the customer network management system. The service provider network management system cannot initiate communications with the client network management system. Accordingly, the client network management system controls whether communications are initiated with the service provider network management system.
[0006] In accordance with an embodiment of the present invention, the service provider network management system maintains a virtual database, that mirrors the information concerning the operation of the client network management system stored on a client network management system database. In this way, the service provider network management system is capable of establishing a virtual copy of the client network management system. The establishment of a virtual network management system allows the service provider to appropriately manage the client network management system, to troubleshoot hardware and software related problems on the client system, and to repair software related problems on the client system, without requiring access to the actual client network management system in real time.
[0007] These and other advantages and features of the invention will become more apparent from the following description of an illustrative embodiment of the invention taken together with the drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
P-0008[0008]FIG. 1 is a block diagram of client networks interconnected to a service provider network management system in accordance with an embodiment of the present invention;
P-0009[0009]FIG. 2 is a block diagram of a client network in accordance with an embodiment of the present invention;
P-0010[0010]FIG. 3 is a functional block diagram illustrating a client network management system in accordance with an embodiment illustrating the present invention;
P-0011[0011]FIG. 4 is a functional block diagram of a service provider virtual network management system in accordance with an embodiment of the present invention; and
P-0012[0012]FIG. 5 is a flow chart illustrating the operation of a remote network management system in accordance with an embodiment of the present invention.
DETAILED DESCRIPTION
P-0013[0013] With reference now to FIG. 1, a remote network management system <b>100</b> in accordance with an embodiment of the present invention is illustrated. The system <b>100</b> generally includes a service provider network management system <b>104</b> interconnected to one or more client networks (or switches) <b>108</b> by a communication network <b>112</b>. In general, the service provider network management system <b>104</b> may be implemented using one or more general purpose computers. The client network <b>108</b> may comprise any voice and/or data network. For example, the client network <b>108</b> may comprise a private branch exchange (PBX). In the embodiment of the remote network management system <b>100</b> illustrated in FIG. 1, the communication network <b>112</b> comprises the Internet. In addition or as an alternative, the communication network <b>112</b> may comprise a switched circuit network, such as the public switched telephone network (PSTN), a private intranet, or another communications system.
P-0014[0014] For each of the client networks <b>108</b>, a virtual network management system <b>116</b> is established on the service provider network management system <b>104</b>. The establishment of virtual network management systems <b>116</b> on the service provider network management system <b>104</b> allows the service provider to remotely manage client networks <b>108</b>, even in the absence of real time access to the client networks <b>108</b>.
P-0015[0015] In FIG. 2, a client network <b>108</b> is illustrated in block diagram form. As shown in FIG. 2, a client network <b>108</b> in accordance with the present invention includes a client network management system <b>204</b> interconnected to the communication network <b>112</b>, for communicating with the service provider network management system <b>104</b>. In addition, the client network <b>108</b> includes a communications server <b>208</b>. The communications server <b>208</b> may control and facilitate communications between nodes on the client network <b>108</b>. The communications server <b>208</b> may also provide interfaces to interconnect the client network <b>108</b> to communications networks, including the communication network <b>112</b>. For example, in FIG. 2, the communications server <b>208</b> is illustrated as interconnecting the client network <b>108</b> to both the communication network <b>112</b> used to interconnect the network management system <b>204</b> to the service provider network management system <b>104</b>, and to the public switched telephone network (PSTN) <b>212</b>. Accordingly, the communications server <b>208</b> may facilitate communications between communication nodes associated with the client network <b>108</b> and communication nodes located outside of the client network <b>108</b>.
P-0016[0016] Examples of communication nodes that may be associated with the client network <b>108</b> include client computers <b>216</b> and desk telephones <b>220</b>. Accordingly, it can be appreciated that the client network <b>108</b> may comprise a data network, a voice network, or a combined voice and data network. As a further example, it should be appreciated that the client network <b>108</b> may comprise a private branch exchange (PPX) telephony network. The various components that may be associated with the client network <b>108</b> (e.g., the client network management system <b>204</b>, the communications server <b>208</b>, the client computers <b>216</b>, and the desk telephones <b>220</b>) may be interconnected to one another by a local communication network <b>224</b>, such as a local area network (LAN).
P-0017[0017] The communications server <b>208</b> may include basic communications functions, including telecommunications functions such as voice messaging and other telephony features. The communications server <b>208</b> may also include an interface with the PSTN <b>212</b> and an interface with the communication network <b>112</b>. The communications server may comprise a general purpose computer. Where the client network <b>108</b> comprises a PBX, the communications server <b>208</b> may comprise a Definity Server available from Avaya, Inc. The client computers <b>216</b> may include general purpose computers, such as personal computers. In addition, the client computers <b>216</b> may include devices such as personal digital assistants (PDAs) and other computing devices, including devices capable of implementing soft telephones. The desk telephones <b>220</b> may comprise dedicated Internet protocol (IP) telephones. In addition to wire line connections, it should be appreciated that the local communication network <b>224</b> may comprise wireless interconnections with the various components of the client network <b>108</b>, such as the client computers <b>216</b> and the desk telephones <b>220</b>.
P-0018[0018] With reference now to FIG. 3, major functional components of a client network management system <b>204</b> in accordance with an embodiment of the present invention are illustrated. In general, the client network management system <b>204</b> includes a virtual data server <b>304</b>, which serves to interconnect the client network management system <b>204</b> to the service provider network management system <b>104</b> (see FIG. 1) across the communication network <b>112</b>. In addition, the virtual data server <b>304</b> initiates contact with the service provider network management system <b>104</b> according to a predetermined schedule, or in response to the collection of certain data concerning the client network <b>108</b> with which the virtual data server <b>304</b> is associated. For example, if a particular number of faults of a certain type are observed, the virtual data server <b>304</b> may autonomously initiate an unscheduled communication with the service provider network management system <b>104</b>.
P-0019[0019] The client network management system <b>204</b> may additionally include one or more data collectors <b>308</b>. In general, the data collectors <b>308</b> each collect a particular type of data concerning the client network <b>108</b>. For example, a first data collector <b>308</b><i>a </i>may collection information regarding the current configuration of the client network <b>108</b>. A second data collector <b>308</b><i>b </i>may collect information regarding one or more performance parameters concerning the client network <b>108</b>. As a further example, a third data collector <b>308</b><i>n </i>may collect information regarding general or specific faults detected in connection with the client network <b>108</b>. Accordingly, it can be appreciated that a data collector <b>308</b> may be established for each category or type of information concerning the client network <b>308</b> for which monitoring is desired.
P-0020[0020] The data scheduler <b>312</b> may be used to determine when data is collected by the data collectors <b>308</b> established in connection with the client network <b>108</b>. For example, the first data collector <b>308</b><i>a </i>in the present example may be scheduled by the data scheduler <b>312</b> to collect current configuration information hourly or whenever the configuration of the client network <b>108</b> has been altered. As a further example, the second data collector <b>308</b><i>b </i>may be scheduled by the data scheduler <b>312</b> to collect performance information every half hour. As still a further example, the third data collector <b>308</b><i>n </i>may be instructed by the data scheduler <b>312</b> to continuously monitor the client network <b>108</b> for faults.
P-0021[0021] One or more registered graphical user interfaces (GUIs) <b>316</b> may be provided to allow a local administrator or administrators to configure various aspects of the operation of the client network <b>108</b>. For example, a registered GUI client <b>316</b> may be used by an administrator to indicate to a data collector <b>308</b> the internet protocol (IP) address of the switch (i.e. the client network <b>108</b>) for which data is being collected. In addition, a registered GUI client <b>316</b> may be used to assign local network addresses or extensions to devices (e.g., client computers <b>216</b> and desk telephones <b>220</b>) associated with the client network <b>108</b>.
P-0022[0022] A database <b>320</b> may be provided for storing various information used by the client network <b>108</b>. For example, the database <b>320</b> may serve as a repository for data collected by the various data collectors <b>308</b>. In addition, the database <b>320</b> may serve as a repository for various configuration information concerning the client network <b>108</b>.
P-0023[0023] With reference now to FIG. 4, the major functional components of a service provider network management system <b>104</b>, and in particular of a virtual network management system <b>116</b>, in accordance with an embodiment of the present invention are illustrated. In general, the virtual network management system <b>116</b> includes a virtual request server <b>404</b>. The virtual request server <b>404</b> receives communications from the virtual data server <b>304</b> (see FIG. 3) of the client network management system <b>204</b> transmitted over the communication network <b>112</b>. The virtual request server <b>404</b> formulates replies to the communications received from the virtual data server <b>304</b>. For instance, the virtual request server <b>404</b> may reply to communications from the client network management system <b>204</b> that contain information regarding faults occurring on the client network <b>108</b> with a request that certain diagnostic procedures be executed by the network management system <b>204</b>, and that the results of the testing be provided to the service provider network management system <b>104</b> in a later communication.
P-0024[0024] A virtual data manager <b>408</b> mirrors the virtual data server <b>304</b> of the client network management system. In general, the virtual data manager <b>408</b> receives data sent from the client network management system <b>204</b>, and stores that data in a virtual database <b>412</b>.
P-0025[0025] A virtual data notifier <b>416</b> may issue alerts, or initiate some other notification procedure in response to faults or other conditions detected in connection with the client network <b>108</b> received from the client network management system <b>204</b>. For example, the virtual data notifier <b>416</b> may sound an alarm or page a technician when a condition requiring immediate attention is detected.
P-0026[0026] A graphical user interface <b>420</b> may be used by a technician or technicians at the service provider to diagnose fault conditions or to otherwise take action to maintain or repair a client network <b>108</b> remotely. In particular, from the data received according to scheduled reports or in response to requests from the virtual request server <b>404</b> that is placed in the virtual database <b>412</b> by the virtual data manager <b>408</b>, a technician has access to a virtual or mirrored copy of the client network management system <b>204</b>. Accordingly, the service provider network management system <b>104</b> comprises a virtual network management system <b>116</b>. Furthermore, a virtual network management system <b>116</b> may be established on a service provider network management system <b>104</b> for each client network <b>108</b> managed by a service provider.
P-0027[0027] With reference now to FIG. 5, the operation of an embodiment of a remote network management system <b>100</b> in accordance with an embodiment of the present invention is illustrated. Initially, at step <b>500</b>, the client network management system <b>204</b> associated with a client network <b>108</b> initiates communication with the service provider's network management system <b>104</b>, and in particular with the virtual network management system <b>116</b> associated with that client network management system <b>204</b> of the client network <b>108</b>. It should be appreciated that, according to the present invention, communication sessions between the client network management system <b>204</b> and the virtual network management system <b>116</b> are always initiated by the client network management system <b>204</b>. That is, although a virtual network management system <b>116</b> may request certain information from the client network management system <b>204</b>, such requests are made in the context of a response to a communication from the client network management system <b>204</b>.
P-0028[0028] At step <b>504</b>, data from the client network management system <b>204</b> is posted to the virtual network management system <b>116</b>. The data may include data routinely collected by the client network management system <b>204</b>. In addition or alternatively, the data may include information that was requested by the virtual network management system <b>116</b> as part of a response to an earlier client network management system <b>104</b> initiated communication.
P-0029[0029] At step <b>508</b>, the virtual network management system <b>104</b> determines whether it is holding data or instructions for transmission to the client network management system <b>204</b>. If data or instructions for the client network management system <b>204</b> are being held by the virtual network management system <b>116</b>, the data or instruction is transmitted to the client network management system as part of the acknowledgment of the communication initiated by the client (step <b>512</b>). An example of data that may be provided from the virtual network management system <b>116</b> to the client network management system <b>204</b> includes revised configuration data, such as changes in the dialing plan used by the client network <b>108</b>. An example of instructions provided from the virtual network management system <b>116</b> to the client network management system <b>204</b> includes instructions to test an aspect of the operation of the client network <b>108</b> and return the results of that testing. If the data or instruction transmitted to the client network management system <b>204</b> includes a request for additional data from the client network management system <b>204</b> (step <b>516</b>) the system returns to step <b>504</b>, during which step additional data from the client network management system <b>204</b> is posted to the service provider virtual network management system <b>104</b>.
P-0030[0030] If at step <b>516</b> the data or instruction transmitted as part of the acknowledgment does not include a request for additional data, the data transfer sequence is ended (step <b>520</b>). It should be appreciated that, in response to a request for additional data from the client network management system <b>204</b> (step <b>516</b>), the client network management system <b>204</b> may acknowledge the request and terminate the data transfer sequence. The requested data may then be provided to the service provider network management system <b>104</b> in a later communication initiated by the client network management system <b>204</b>.
P-0031[0031] If at step <b>508</b> it is determined that the service provider network management system <b>104</b> is not holding data or instructions for the client network management system <b>204</b>, the communication from the client network management system <b>204</b> is acknowledged (step <b>524</b>) and the data transfer sequence then ends (step <b>520</b>).
P-0032[0032] The communications between the client network management system <b>204</b> and the virtual network management system may be according to the protocol or protocols required by the communication network. For example, the communications may be according to the HTTPS protocol where a Server Socket Layer (SSL) encryption session is used in connection with communications conducted over a communication network <b>112</b> that comprises the Internet.
P-0033[0033] From the above description, it can be appreciated that a remote network management system <b>100</b> in accordance with the present invention provides a virtual network management system <b>116</b> for each client network management system <b>204</b> administered by the service provider. Accordingly, by providing, for example, a Web address allowing contact from client contact management systems <b>204</b>, a service provider may remotely manage a number of client networks <b>108</b> from a service provider network management system <b>104</b> that is remote with respect to the client networks <b>108</b>.
P-0034[0034] In addition, it should be appreciated that a remote network management system <b>100</b> in accordance with an embodiment of the present invention does not allow for communication sequences that are initiated by the service provider. Instead, communications sequences are initiated by the client network management system <b>204</b>. Accordingly, the present invention may provide for the remote management of client networks <b>108</b>, without requiring additional hardware, such as virtual private network routers, and without requiring that the client network <b>108</b> accept communications initiated by a system external to the client network <b>108</b>.
P-0035[0035] The foregoing discussion of the invention has been presented for purposes of illustration and description. Further, the description is not intended to limit the invention to the form disclosed herein. Consequently, variations and modifications commensurate with the above teachings, within the skill and knowledge of the relevant art, are within the scope of the present invention. The embodiments described hereinabove are further intended to explain the best mode presently known of practicing the invention and to enable others skilled in the art to utilize the invention in such or in other embodiments and with various modifications required by their particular application or use of the invention. It is intended that the appended claims be construed to include the alternative embodiments to the extent permitted by the prior art.
Contents5
6 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US2004019803A1 | Cited by | United States of America | Pre-grant |
| US2004139371A1 | Cited by | United States of America | Pre-grant |
| US7673036B1 | Cited by | United States of America | Search report |
| US7350203B2 | Cited by | United States of America | Search report |
| US7206972B2 | Cited by | United States of America | Search report |
| US2002091821A1 | Cites | United States of America | Pre-grant |
| US2002100036A1 | Cites | United States of America | Pre-grant |
| US6009274A | Cites | United States of America | Pre-grant |
| US6070012A | Cites | United States of America | Pre-grant |
| US6085243A | Cites | United States of America | Pre-grant |
| US6131112A | Cites | United States of America | Pre-grant |
| US6349337B1 | Cites | United States of America | Pre-grant |
| US6629138B1 | Cites | United States of America | Pre-grant |
| US6725377B1 | Cites | United States of America | Pre-grant |
| US6748525B1 | Cites | United States of America | Pre-grant |
| US6751794B1 | Cites | United States of America | Pre-grant |
| US6779023B2 | Cites | United States of America | Pre-grant |
| US6829687B2 | Cites | United States of America | Pre-grant |
| US6877037B1 | Cites | United States of America | Pre-grant |
2 members in 1 office; this record represents the family
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 11750902 | United States of America | A | |
| US20020117509 | – | – | – |
Members2
| Document | Office | Kind | |
|---|---|---|---|
| US2003191830A1 | United States of America | A1 | |
| US7058711B2 | United States of America | B2 |
64 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Maintenance fee paymentMAFP | MAFP | |
| AssignmentAS | AS | |
| Fee paymentFPAY | FPAY | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Fee paymentFPAY | FPAY | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS |
Numbers
- Publication, DOCDB
- 2003191830
- Publication, EPODOC
- US2003191830
- Application
- 10117509
- Application, DOCDB
- 11750902
- Application, EPODOC
- US20020117509
Titles
- English
- Virtual network management
Classification
- CPC, 5
- H04L41/28
- H04L41/18
- H04L63/10
- H04L63/20
- H04L41/40
- IPC, 4
- G06F15 16
- G06F15 173
- H04L12 24
- H04L29 06
- USPC, 2
- 709223000
- 709203000