Patent Application
20050128952
The present invention relates to computer network systems and in particular to a method for establishing the servicing, execution and implementation of establishing a network connection between a client system and the network.
Despite advances in hardware and software technology, computer users frequently encounter situations in which they cannot establish a connection to a service provider or network. What is meant by establishing a connection in the context of the present application is either creating a first connection to a network or repairing a connection to a network. Repairing a connection to a network can be the result of an improperly installed or configured software program or device driver, or the device being used to attempt the connection may simply be disabled. In the case of a wired connection, the problem may be caused by a defective interconnect cable, or in the case of a wireless connection, a bad transmitter or antenna connection. In addition to such defects, other problems in the network can prevent the user from getting connected. For example, in the case of an Ethernet network, the failure of the network's Dynamic Host Configuration Protocol, or DHCP server, can prevent the user from getting connected to the network.
Because the majority of these problems are not communicated to the user, the user cannot determine the cause, and sees the problem as simply “no connection.” Moreover, even if the user was able to determine the source of the problem, e.g., through an error message generated by the system, he or she would most likely not know how to resolve the problem.
Accordingly there is a need for a service provider to be able to work with a client having such issues and determine the cause of a connectivity problem and repair the connection. The system and method should be automatic and transparent to the user. The present invention addresses such a need.
A method for establishing, deploying and implementing a network connection, between a service provider and at least one party having a computer system, optionally using a computer readable medium, between a client system and a network, is disclosed. In a first aspect, the method preferably comprises the steps of engaging with a client, evaluating as part of the service the client's business infrastructure, collecting real time connectivity information from the client's system and utilizing the real time connectivity information of the client system to establish a connection with the network. In a second aspect, a method utilizing a client's computer system coupled to a network including at least one network adapter for monitoring and collecting real time connectivity information from the network, memory for storing the real time connectivity information, and a processor coupled to the memory and to the at least one network adapter, where the processor is configured to execute program instructions for utilizing the real time connectivity information to repair a failed network connection between the computer system and the network following the steps of establishing an engagement arrangement with a client and evaluating as part of the service the client's business infrastructure, is provided for.
The following description is presented to enable one of ordinary skill in the art to make and use the invention and is provided in the context of a patent application and its requirements. Various modifications to the preferred embodiment and the generic principles and features described herein will be readily apparent to those skilled in the art. Thus, the present invention is not intended to be limited to the embodiment shown but is to be accorded the widest scope consistent with the principles and features described herein.
In general, the methods set forth herein may include the involvement of service providers (such as those engaged in the business of systems integration, customized software development, identification and analysis of critical system requirements, etc.), independent of size, who work and possibly contract with system owners for providing their services to those system owners (also used herein as customers, clients, etc.). More specifically, here, those services may also include or involve the managing and controlling of establishing, deploying and implementing a network connection, between a service provider and at least one party having a computer system, creating customized software product solutions and applications that are able to perform the functionality further detailed herein, formally establishing agreements and contracts for the provision of the services and executing those agreements and contracts so the services are provided to the system owners.
For instance, where a service provider is providing the described service to a client, under an engagement agreement, of establishing, deploying or implementing a network connection between a client system and a network, those services may include the use of software, preferably created by the service provider but not necessarily required to be so, where the service provider: identifies the characteristics of at least a portion of a customer's computer system (i.e., including architecture, operating, system, components, peripherals, etc.), establishes requirements for a customer's system (i.e., client system), employs a technical analysis process to establish a network connection between a client system and a network in relation to the characteristics and requirements of the client's system (wherein the term identifies may recognition by the service provider that the service provider may need to customize an existing application or create a new application for the customer in view of the needs), and identifies a solution for the client based on the results determined from the technical analysis process. In a preferred aspect, the solution is then implemented for the client. In a further preferred aspect, a software product or other computer-readable medium is used by the service provider to assist in the technical analysis process to generate a solution for the client based on results therefrom. As used herein, the term “engagement relationship” may include a formal written relationship between a service provider and customer, such as that of a contract, or may be informally established such that there is a cooperative understanding between the service provider and the customer where the service provider is to assist the customer with certain tasks or activities.
The preferred embodiment of the present invention determines the cause of a connectivity problem and attempts to repair the connection by applying changes to the operating software and/or device configuration in an iterative fashion until a connection is established. It determines the types of changes or repairs to make by collecting information related to the network and to the status of system components, and based in part on that information, begins an iterative process of attempting to establish the connection. The system and method according to a preferred embodiment of the present invention includes an inference engine that determines the cause of the connection failure and the appropriate corrective action based on information contained in several sources, including but not limited to, a local persistent knowledgebase, a real time network list, a set of local rules, and a server-resident database. In a preferred embodiment, the system and method of the present invention evaluates the conditions of a particular connection, and by consulting one or more of the above listed sources, determines a hierarchy of potential solutions and applies each potential solution iteratively until a connection is established. The result of each iterative attempt is monitored, and if unsuccessful, the result, e.g., an error message, is used as feedback to the inference engine.
In a preferred embodiment, the inference engine 302 analyzes one or more error messages 316 generated by the client 200 relating to the failed connection to assist it in determining the cause of the connectivity failure. In addition, the inference engine 302 invokes the verify function 304, which audits each of the communication devices to determine which, if any, can be potential candidates for connectivity. Based on the information received from the verify function 304 and on its analysis of the error messages 316, the inference engine 102 determines the cause of the connectivity failure.
The inference engine 302 utilizes connectivity information stored in the client computer system 200 to repair the connection based on its diagnosis of the cause for failure. The connectivity information includes a set of local rules or preferences 308, a local persistent knowledgebase 310 a real time network list 314 and optionally, a remote/server-resident knowledgebase. The local rules 308 indicate the client's 200 connection preferences. For example, if the client 200 is capable of establishing a wired and wireless connection, but prefers a wireless connection, the inference engine 302 will attempt to establish a wireless connection before other modes of connectivity. The local persistent knowledgebase 310 includes static configuration information, e.g., parameters and settings. The local persistent knowledgebase 310 can be downloaded and/or updated from the remote/server-resident knowledgebase 312 stored on the company server 112 (
According to a preferred embodiment of the present invention, the real time network list 314 is a weighted list that includes connectivity information gathered by the network adapter 219 (
With the connectivity information, the inference engine 302 formulates a best solution, which is then passed to the connection manager 306 and implemented, i.e., a network connection is attempted using the solution. If the solution fails, such information is transmitted back to the inference engine 302, e.g., via an error message 316, so that a new diagnosis of the connection failure can be generated if necessary. This process repeats until a connection is established.
If a connection error is determined then an error message is transmitted and in step 406, the root cause of the connection failure is determined. In a preferred embodiment, the inference engine 302 is called automatically once a connection failure is detected. In another embodiment, the user can invoke the inference engine 302. In any event, once the inference engine 302 is called, the inference engine 302 invokes the verify function 304. The verify function 304 audits each communication device to determine its status, e.g., functional or failed, thereby determining which of them are potential candidates for connectivity. The results of the audit are returned to the inference engine 302, which then analyzes the results and the error message(s) 316 in order to determine the root cause of the connection failure.
Once the root cause has been determined, the inference engine 102 generates a best solution (in step 408) using the connectivity information based on the root cause. For example, in one case, the inference engine 302 monitors the range of IP addresses that are assigned by a DHCP server 114. It then selects an address in the range and instructs the connection manager 306 to “ping” that address to determine if it is in use. If the address is not in use, the inference engine 302 temporarily assigns the IP address to the client 200 and sets up its network settings for that connection. In another example, if the inference engine 302 determines that the root cause of a connection failure is due to a missing field, e.g., an IP address for the DHCP server 114 or DNS server 160, from the current discovered configuration, the inference engine 302 will insert the appropriate IP address from the real time network list 314, effectively “filling in the blanks.” Because the real time network list 314 is a weighted list, the inference engine 302 applies the most frequently utilized IP addresses, which are also those most likely to succeed.
In step 410, the connection manager 306 implements the best solution. If the connection is unsuccessful (step 412), i.e., the best solution fails, then that result is passed back to the inference engine 302 which reexamines its diagnosis based, in part, on the previous unsuccessful attempt and generates a next best solution (step 414). The process ends when the connection is successful or when all potential solutions have been exhausted.
In summary, the preferred embodiment of the present invention automatically determines the root cause of a connection failure and attempts to repair the connection without intervention from a user. To do this, the inference engine 302 is invoked to analyze one or more error messages 316 related to the connection failure to determine the root cause of the failure. Once the cause is determined, the inference engine 302 utilizes connectivity information stored in the client 200 to repair the connection. The connectivity information includes real time network information, e.g., IP addresses of the DHCP servers and domain name servers, collected by the client's network adapter 219. The real time network information is stored in a weighted list 314, with the most frequently assigned addresses at the top. By utilizing the preferred embodiment of the present invention, the client 200 seamlessly and transparently repairs a failed network connection.
In another exemplary embodiment of the present invention, a service provider offer a services integration offering (such as a contract or agreement or similar) to at least one customer in view of establishing a transactional relationship with the customer. Upon establishment of a service provision agreement, the service provider is able to provide service related to the computer program product-based solution that addresses the needs of the customer, as further set forth herein and above.
Although the present invention has been described in accordance with the embodiments shown, one of ordinary skill in the art will readily recognize that there could be variations to the embodiments and those variations would be within the spirit and scope of the present invention. Accordingly, many modifications may be made by one of ordinary skill in the art without departing from the spirit and scope of the appended claims.
The subject matter of this application is related to two (2) U.S. patent application Ser. Nos. ______ and ______ filed Dec. 11, 2003 as attorney docket numbers RPS920030249US1 and RPS920030164US1, the teachings of which are incorporated herein by reference.
