Software distribution and maintenance system and method

• US 5,835,911 A
• Filed: 08/21/1995
• Issued: 11/10/1998
• Est. Priority Date: 02/08/1994
• Status: Expired due to Term

• Current Assignee: Fujitsu Limited
• Original Assignee: Fujitsu Limited
• Inventors: Takada, Yuji, Nakagawa, Toru
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): LEWIS, CHERYL RENEA
• Application Number:
  US08/517,133
• Time in Patent Office: 1,177 Days
• Field of Search: 395/608, 395/610, 395/619, 395/500, 395/200.09, 395/700, 395/200.33, 395/200.51, 364/401, 364/300, 707/203, 707/10, 707/3
• US Class Current: 1/1
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

A number of sets of software may be systematically distributed and maintained via a network connecting many vendors and users of client/server software. A client program in a user computer detects when software subject to maintenance is activated and transmits an inquiry over the network to the software vendor'"'"'s computer for information on the current version of the software. The server program compares data in the inquiry with data relating to the latest version of the software and returns update instruction information and updated software if appropriate. The client program automatically updates the software to the latest version according to the update instruction information when it is received. The client program can also send inquires at predetermined times, or in response to a user command. The inquiry can include a request for purchase information in which case the server checks qualifications of the user, processes the inquiry according to vendor management data and returns the requested software, if appropriate. Other inquiries can also be made in response to user commands or automatically, e.g., to obtain information on the most recent version and transmission of data from client to server in response to an abnormal termination of client software.

Claims

1. A software distribution/maintenance system having a plurality of user computers and a vendor computer connected to the user computers via a network to manage and automatically update over the network a set of object software sent and stored in the user computers from the vendor computer via the network, comprising:

an object software library in the vendor computers;

first process means in the user computers for sending an inquiry with current configuration information of the object software stored in the user computers to the vendor computer via the network to inquire about a latest configuration, for receiving an answer from the vendor computer, and for updating the object software stored in the user computers according to an instruction in the answer; and

second process means in the vendor computer for receiving the inquiry from said first process means in the user computers, for generating update instruction information for the object software to match the current configuration of the object software in the user computers with the latest configuration of an updated version in said object software library stored in the vendor computer, and for returning via the network to said first process means the answer with the update instruction information and the updated version of the object software.

2. The software distribution/maintenance system according to claim 1, wherein said first process means in the user computers automatically informs via the network the vendor computer of an abnormal termination and state if an operation of the object software abnormally terminates in the user computers.

3. The software distribution/maintenance system according to claim 2, wherein said first process means automatically informs the vendor computer of the abnormal termination, an instruction causing the abnormal termination, a reason for the abnormal termination, a series of instructions which invoked the instruction causing the abnormal termination, and an environment of software and hardware used when the abnormal termination is detected.

4. The software distribution/maintenance system according to claim 2 or claim 3, wherein said first process means can automatically inform, via the networks the vendor computer of the abnormal termination by general-purpose electronic mail.

5. A software distribution/maintenance method for managing and automatically updating a set of object software stored in user computers from a vendor computer via a network, comprising:

sending, by a first process in the user computers, current configuration information of the object software to a second process in the vendor computer via the network with an inquiry for a latest configuration of the object software;

receiving by said second process in the vendor computer the inquiry from said first process;

generating update instruction information for the object software to update a configuration of the object software in the user computers with the latest configuration of an updated version of the object software in an object software library stored in the vendor computers;

returning via the network to said first process an answer with the update instruction information and the updated version of the object software; and

processing by said first process stored in the user computers the answer from said second process to update the object software according to the update instruction information in the answer, including preparing for compiling and linking of programs if necessary.

6. The software distribution/maintenance method according to claim 5, wherein when the object software is activated in the user computers, said first process

immediately sends the current configuration information of the object software to said second process in the vendor computer via the network to inquire about the latest configuration,

receives the answer from said second process,

updates the object software according to the update instruction information in the answer, and

prepares for compiling and linking programs if necessary.

7. The software distribution/maintenance method according to claim 5, wherein when said first process is activated in the user computers at a predetermined time, said first process

sends the current configuration information of the object software to said second process in the vendor computer via the network to inquire about the latest configuration,

receives the answer from said second process,

updates the object software according to the update instruction information in the answer, and

prepares for compiling and linking of programs if necessary to realize an automatic update of the object software.

8. The software distribution/maintenance method according to claim 5, wherein when a user instructs the user computers to activate said first process, said first process

sends the current configuration information of the object software to said second process in the vendor computer via the network to inquire about the latest configuration,

receives the answer from said second process,

updates the object software according to the update instruction information in the answer, and

prepares for compiling and linking of programs if necessary.

9. The software distribution/maintenance method according to claim 5, wherein following processes are interchangeably performed:

when the object software is activated in the user computers, said first process

immediately sends the current configuration information of the object software to said second process in the vendor computer via the network to inquire about the latest configurations,

receives the answer from said second process,

updates the object software according to the update instruction information in the answer, and

prepares for compiling and linking programs if necessary;

when said first process is activated in the user computers at a predetermined time, said first process

sends the current configuration information of the object software to said second process in the vendor computer via the network to inquire about the latest configuration,

receives the answer from said second process,

updates the object software according to the update instruction information in the answer, and

prepares for compiling and linking of programs if necessary to realize an automatic update of the object software; and

when a user instructs the user computers to activate said first process, said first process

sends the current configuration information of the object software to said second process in the vendor computer via the network to inquire about the latest configuration,

receives the answer from said second process,

updates the object software according to the update instruction information in the answer, and

prepares for compiling and linking of programs if necessary.

10. A software distribution/maintenance system for managing distribution of object software via a network by users who use one or more sets of the object software to be distributed, managed, and maintained and by software vendors who supply the users with the object software, comprising:

first process means for managing plural sets of the object software in each user computer;

vendor software libraries in at least one vendor computer;

second process means for providing services relating to said vendor software libraries in the at least one vendor computer; and

a network for connecting each user computer and the at least one vendor computer,

said first process means sending via the network an object software distribution/maintenance request message according to an instruction of the users or an instruction of a user-written program to said second process means of the at least one vendor computer containing desired object software, receiving an answer message from the second process means, and distributing or maintaining the object software; and

said second process means receiving the message from said first process means, referring to said vendor software libraries managed by the software vendors according to the message and settings made by the software vendors, generating an answer message in response to the object software distribution/maintenance request message, and sending the answer message to said first process means of a message sender.

11. The software distribution/maintenance system according to claim 10, wherein

when any object software managed by said first process means in the user computer abnormally terminates during its operation, said first process means detects and analyzes an abnormal condition, and then automatically sends a fault report to said second process means of the vendors over the network;

and

said second process means of the vendors receives the fault report and informs the vendors of the fault report.

12. The software distribution/maintenance system according to claim 10 or claim 11, wherein when each version of the object software is provided for a number of the users by the vendors, a single computer user can be a user of a version of one piece of software and also a vendor of a version of another piece of software, and furthermore, a single computer can be provided with one or more first process means and one or more second process means.

13. The software distribution/maintenance system according to claim 10, claim 11, or claim 12, wherein

each user computer can be designed to store user management data for each of the users or each user group, and the data can be set for each object software;

and

said first process means refers to the user management data to manage one or more sets of the object software.

14. The software distribution/maintenance system according to claim 13, wherein said user management data includes at least one of user identification information of each user or each user group, software management information of each object software used by each user, software configuration information, and message process method specification information.

15. The software distribution/maintenance system according to claim 14, wherein in specifying a method of processing a message according to the user management data, the users can specify a process method as a procedure for each function performed by said first process means.

16. The software distribution/maintenance system according to claim 15, wherein

in specifying a method of processing a message according to the user management data., a vendor confirmation procedure can be used so that the vendor can be conformed to protect user software.

17. The software distribution/maintenance system according to claim 10, claim 11, or claim 12, wherein when said second process means of the at least one vendor computer offers services using said vendor software libraries, said second process means can refer to vendor management data stored for each vendor software library.

18. The software distribution/maintenance system according to claim 17, wherein said vendor management data includes at least one of vendor identification information, software management information, software configuration information, message process method specification information, customer information, and fault history information.

19. The software distribution/maintenance system according to claim 18, wherein when a message process method is specified using the vendor management data, the software vendors can specify a procedure for each function performed by said second process means.

20. The software distribution/maintenance system according to claim 19, wherein a user confirmation procedure can be selected when a message process method is specified using the vendor management data.

21. The software distribution/maintenance systems according to claim 10 or claim 11, wherein

Each of the users can simultaneously obtain and use a plurality of versions of each object software.

22. A software distribution/maintenance method for managing distribution of object software via a network by users who use one or more sets of object software to be distributed, managed, and maintained and by software vendors who supply the users with the object software using, in user computers, the object software to be used by the users and a first process for managing one or more sets of object software;

in each vendor computer, vendor software libraries and a second process for providing services relating to the vendor software libraries; and

the network connecting each user computer to at least one vendor computer, comprising;

activating by a sending user the first process through a command input by the sending user in one of the user computers or through a command from a user program;

sending by the sending user from the first process in the one of the user computers via the network, an object software distribution/maintenance request message to the second process of the at least one vendor computer from which the object software is provided;

receiving by the second process in the at least one vendor computer, from which the object software is provided, the object software distribution/maintenance request message from the first process;

referring by the second process to the vendor software libraries managed by the software vendors according to the object software distribution/maintenance request message and settings made by the software vendors;

generating an answer message in response to the object software distribution/maintenance request message;

sending the answer message to the first process of the sending user;

receiving by the first process in the one of the user computers of the sending user the answer message from the second process; and

performing processes for distributing or maintaining the object software according to the answer message and settings made by the users.

23. The software distribution maintenance method according to claim 22,

wherein when executing object software managed by the first process in one of the user computers abnormally terminates during operation, the first process detects and analyzes an abnormal condition, and then sends a fault report message to a vendor of the executing object software via the network, and

wherein the second process receives the fault report message via the network, and informs the vendor of the abnormal condition.

24. The software distribution/maintenance method according to claim 22 or claim 23, wherein

each user computer stores user management data for each of the users or each user group, identifying one or more sets of the object software;

and

said first process refers to the user management data to manage the one or more sets of the object software.

25. The software distribution/maintenance method according to claim 24, wherein the user management data includes at least user identification information of at least one of the users, software management information of each object software used by each user in an object software group, software configuration information, and message process method specification information;

and

said first process refers to the user management data.

26. The software distribution/maintenance method according to claim 25, wherein in referring to a method of processing a message according to the user management data, the sending user can specify and use a process method as a procedure for each function performed by the first process.

27. The software distribution/maintenance method according to claim 26, wherein in referring to the method of processing the message according to the user management data, a user-defined vendor confirmation procedure is used so that the message received by the first process can be recognized as a correct message from a predetermined vender.

28. The software distribution/maintenance method according to claim 25, wherein when the sending user activates the first process in one of the user computers by inputting a command, the first process

obtains a user name, a command name, and an object software name to generate an interactive screen displaying messages according to the command,

promotes generation of a message in response to the command from the sending user by referring to the user management data of the sending user and the object software or by invoking a user-defined process procedure,

sends the message to the second process of the computer of the software vendors of the object software, and

returns to a standby state after recording transmission of the message.

29. The software distribution/maintenance method according to claim 25 or claim 26, wherein if the first process is activated in the one of the user computers by an input command from a program defined by the sending user or through an abnormal termination of the object software managed by the first process, the first process

obtains a user name, a command name, and an object software name,

promotes generation of a message in response to a command from the sending user by referring to the user management data of the sending user and the object software or by invoking a user-defined process procedure,

sends the message to the second process in the at least one vendor computer, and

returns to a standby state after recording transmission of the message.

30. The software distribution/maintenance method according to claim 25 or claim 26, wherein if the first process is activated in the one of the user computers by a message received from the network, then the first process

obtains from a header of the answer message a destination user name identifying a specified user, a command name, and an object software name,

uses the user management data for the specified user and the object software,

then obtains a sender name from the header of the answer message,

confirms that the message was sent by a correct vendor of the object software,

also confirms that the first process is in an answer-wait state,

refers to the user management data or invokes the user-defined process procedure depending on the command in the answer message,

analyzes or stores message data or stores or installs the software specified by the answer message, returns, in response to a specific message which requires acknowledgment, an acknowledgment or a process state in an acknowledgment message to the second process via the network, and

then returns to a standby state after recording transmission of the acknowledgment message.

31. The software distribution/maintenance method according to any of claim 25 to claim 27, wherein said first process performs following processes depending on a cause activating the first process:

when the sending user activates the first process in the sending user computers by inputting a command, the first process

obtains a user name, a command name, and an object software name to generate an interactive screen displaying message according to the input command,

promotes generation of a first message in response to the command from the sending user by referring to the user management data of the sending user and the object software or by invoking a user-defined process procedure,

sends the message to the second process of the at least one vendor computer storing the object software, and

returns to a standby state after recording transmission of the object software distribution/maintenance request message;

if the first process is activated in the one of the user computers by an input command from a program defined by the sending user or through an abnormal termination of the object software managed by the first process, the first process

obtains a user name, a command name, and an object software name,

promotes in response to an activated command generation of a second message in response to a command from the sending user by referring to the user management data of the sending user and the object software or by invoking a user-defined process procedure,

sends the second message to the second process of the at least one vendor computer storing the object software, and

returns to a standby state after recording transmission of the second message; and

if the first process is activated in the one of the user computers by a received message from the network, then the first process

obtains from a header of the received message a destination user name, a command name, and an object software name,

uses the user management data for a specified user and the object software,

then obtains a sender name from the header of the received message,

confirms that the received message was sent by a correct vendor of the object software,

also confirms that the first process is in an answer-wait state,

refers to the user management data or invokes the user-defined process procedure depending on the command name in the received message,

analyzes or stores message data or stores or installs the software specified by the received message,

returns, if the received message requires acknowledgment, an acknowledgment message with an acknowledgment or a process state to the second process via the network, and

then returns to a standby state after recording a transmission of the acknowledgment message.

32. The software distribution/maintenance method according to claim 31, wherein each time the first process is activated, a new process is generated to allow plural processes to be performed in parallel on processes other than for a single set of object software for a single user.

33. The software distribution/maintenance method according to claim 22 or claim 23, wherein when the second process in the at least one vendor computer offers services using the vendor software libraries, vendor management data, stored for each vendor software library, is referred to.

34. The software distribution/maintenance method according to claim 33, wherein when the second process refers to the vendor management data, reference is made corresponding to the vendor software library to at least vendor identification information, software management information, software configuration information, message process method specification information, customer information, update history information, and fault history information.

35. The software distribution/maintenance method according to claim 34, wherein when a message process method is referred to using the vendor management data, a procedure each function performed by the second process is invoked.

36. The software distribution/maintenance method according to claim 35, wherein when the message process method is referred to using the vendor management data, a user confirmation procedure can be invoked to confirm an identification of the sending user of the object software distribution/maintenance request message, determine a qualification of the sending user, and return an appropriate answer to the sending user.

37. The software distribution/maintenance method according to claim 36, wherein in the user confirmation procedure as a part of the vendor management data, the qualification of the sending user can be determined based on commercial relations including at least one of contracts relating to the object software, payments relating to the object software, and payments relating to new services for the object software.

38. The software distribution/maintenance method according to claim 36, wherein in the user confirmation procedure depending on the vendor management data, the object software is provided and distributed only to qualified users by referring to identification information including at least one of organizations, titles, and personal names thereof.

39. The software distribution/maintenance method according to claim 36, wherein

in the user confirmation procedure as a part of the vendor management data, the user can be identified by a password.

40. The software distribution/maintenance method according to claim 22 or claim 23, wherein the one of the user computers and the at least one vendor computer are connected to the network only when sending and receiving messages between each other or a relaying device in the network.

41. The software distribution/maintenance method according to claim 22, or claim 23 wherein the object software distribution/maintenance request message transmitted via the network has a destination and a source of the message, and a title column specifying a name of a software distribution/maintenance system, a name of a software distribution/maintenance process type, and a name of the object software.

42. The software distribution/maintenance method according to claim 22, claim 23, or any of claims 33 to 39, wherein the second process in the at least one vendor computer is normally in a standby state, and upon being activated by receiving the object software distribution/maintenance request message from the first process via the network

obtains a command name and an object software name of specified software from a header of the object software distribution/maintenance request message,

assigns processes to be performed,

obtains a name of the sending user and user identification information from the object software distribution/maintenance request message,

compares the name of the sending user with vendor management data to determine a user access qualification relating to the command name,

analyzes the object software distribution/ maintenance request message if the sending user qualifies,

provides summary information of the specified software,

provides new services for the specified software,

supplies updated software and instructions to correctly update the specified software, retrieves information of other messages,

generates the answer message,

records a summary of the answer message to the sending user,

sends the answer message to the first process of the sending user via the network, and

returns to the standby state.

43. The software distribution/maintenance method according to claim 42, wherein each time the second process is activated, a new process is generated to allow a plurality of processes to be concurrently performed on processes other than for a single set of object software for a single user.

44. The software distribution/maintenance method according to claim 22, or claim 23 wherein when the users obtain summary information of the object software not yet used by the users, following processes are performed:

in the one of the user computers,

the sending user

enters a summary inquiry command,

activates the first process in the one of the user computers,

sets a name of specified object software, a name of a specified vendor, a network address of the specified vendor, and an answer information storage directory, and

generates a summary information inquiry message;

the first process sends the summary information inquiry message to the second process of the specified vendor;

in the at least one vendor computer,

the second process is activated when the summary information inquiry message is received via the network;

the second process

refers to vendor management data about the specified object software cited by the summary information inquiry message to confirm an identification of the sending user and determine access qualification of the sending user;

invokes, if the sending user is qualified, a vendor-defined procedure to provide summary information in a summary information message; and

sends the summary information message to the first process of the sending user via the network.

45. The software distribution/maintenance method according to claim 22 or claim 23, wherein when the users newly obtain the object software not yet used by the users, following processes are performed:

in the one of the user computers,

the sending user

enters a new installation command,

activates the first process in the one of the user computers,

sets user identification information, software information of specified object software, vendor identification information, and user installation process information, and

generates a new installation request message; and

the first process sends the new installation request message to the second process managing the specified object software;

in the at least one vendor computer,

the second process is activated when the new installation request message is received via the network,

the second process

refers to vendor management data about the specified object software to confirm identification of the sending user and determine access qualification of the sending user;

invokes, if the sending user is qualified, a vendor-defined procedure for new installation to determine a version to be provided,

obtains a set of modules of the version to be provided,

organizes instruction information of the new installation in the one of the user computers, and

generates a new installation message as the answer message,

sends the new installation message as the answer message to the first process of the sending user via the network;

in the user computer,

the first process is activated when the new installation message is received via the network,

the first process

obtains a name of a destination user and a name of specified object software from a header of the new installation message,

refers to corresponding user management data,

confirms that the first process is currently in a new installation standby state and that a correct vendor sent the new installation message,

invokes a user-defined new installation process procedure,

refers to installation information in the new installation message,

stores the specified object software to be newly installed in the one of the user computers,

installs the set of modules if the new installation is acceptable,

records the new installation message and a process result, and

returns to the standby state.

46. The software distribution/maintenance method according to claim 22, or claim 23, wherein when the users add or switch to a new service of the object software already used by the users, following processes are performed:

in the one of the user computers,

the sending user

enters a new service request command,

activates the first process in the one of the user computers,

sets user identification information, software information of specified object software, vendor identification information, and user installation process information, and

generates a new service request message;

the first process sends the new service request message to the second process of the at least one vendor computer;

in the at least one vendor computer,

the second process is activated when the new service request message is received via the network;

the second process

refers to vendor management data about the specified object software cited by the new service request to confirm identification of the sending user and determine access qualification of the sending users,

invokes, if the sending user is qualified, a vendor-defined procedure for a supply of the new service to determine a version to be provided,

obtains a set of modules of the version to be provided,

organizes instruction information of installation in the one of the user computers,

specifies a process to be performed on an old service,

generates a new installation message as an answer, and

sends the new installation message as the answer to the first process of the sending user via the network;

in the user computer,

the first process is activated when the new installation message is received via the network;

the first process

obtains a name of a destination user and the name of the specified object software from a header of the new installation message,

refers to corresponding user management data,

confirms that the third process is currently in a new installation standby state and a correct vendor sent the new installation message,

invokes a user-defined process procedure,

refers to installation information in the new installation message,

stores specified software supplied as the new service in the one of the user computers,

stores the new service of the specified software if the new service is acceptable,

records the new installation message and a process result, and

returns to the standby state.

47. The software distribution/maintenance method according to claim 22 or claim 23, wherein when the users inquire of the vendors about an update state of installed object software already used by the users and request updated object software, following processes are performed:

in the one of the user computers,

the sending user

enters an update inquiry command,

activates the first process in the one of the user computers,

sets user identification information, software information of the installed object software, vendor identification information, software management information, and user installation process information, and

generates an update inquiry message;

the first process sends the update inquiry message to the second process of a specified vendor identified by the vendor identification information;

in the at least one vendor computer,

the second process is activated when the update inquiry message is received via the network;

the second process

refers to vendor management data about the installed object software cited by the update inquiry message to confirm identification of the sending user and determine access qualification of the sending user,

invokes, if the sending user is qualified, a vendor-defined update inquiry answering procedure to determine a version type to be supplied and a latest version and compares the latest version with a current version of the sending user;

if the current version of the sending user matches the latest version, then the second process

generates a non-update message, and

sends the non-update message to the first process of the sending user;

if the undated object software with the version type of the current version of the installed object software exists, then the second process

generates module delete/add instruction information about modules to be added in an update instruction message as an answer, and

sends the answer to the first process of the sending user via the network;

if the current version should be switched to a newly served version of the installed object software, then the second process

generates the non-update message and an information message about the newly served version, and

sends the non-update message and the information message to the first process of the sending user via the network;

in the one of the user computers,

the first process is activated when a received message is the update instruction message or the non-update message received via the network;

the first process

obtains a name of a destination user and a name of specified object software from a header of the received message,

refers to corresponding user management data, and

confirms that the first process is currently in a standby state after inquiry and that a correct vendor sent the received message;

if the non-update message is received, the first process records the non-update message and returns to the standby state;

if the update instruction message is received, the first process

invokes a user-defined update reception process procedure,

refers to the module delete/add instruction information in the received message,

stores in the one of the user computers the specified object software specified by the update instruction message,

installs the specified object software if the specified object software is acceptable, and

records the received message and a process result, and returns to the standby state.

48. The software distribution/maintenance method according to claim 22 or claim 23, wherein when the users inquire about an update state of installed object software already used by the users and request updated object software, following processes are performed:

in the one of the user computers,

the first process

is activated according to an update inquiry command instruction of a user program,

invokes a user-defined automatically-editing update inquiry procedure,

refers to user management data, and

generates an update inquiry message;

the first process sends the update inquiry message to the second process of a specified vendor of the installed object software;

in the at least one vendor computer,

the second process is activated when the update inquiry message is received via the network;

the second process

refers to vendor management data about the installed object software cited by the update inquiry message to confirm identification of the sending user and determine access qualification of the sending user, and

invokes, if the sending user is qualified, a vendor-defined update inquiry answering procedure to determine a version type to be supplied and a latest version and compare the latest version with the current version of the sending user;

if the current version of the sending user matches the latest version, then the second process

generates a non-update message, and

sends the non-update message to the first process of the sending user;

if the installed object software of the version type of the current version of the sending user has been updated, then the second process

generates module delete/add instruction information and information about modules to be added in an update instruction message as an answer, and

sends the updated instruction message to the first process of the sending user via the network;

if the current version should be switched to a newly served version of the installed object software, then the second process

generates a non-update message and an information message about the newly served version, and

sends the non-update message to the first process of the sending user via the network;

in the user computer,

the first process is activated when the update instruction message or the non-update message is received from the second process via the network;

the first process

obtains a name of a destination user and a name of the object software from a header of a received message,

refers to corresponding user management data, and

confirms that the first process is currently in a standby state after inquiry and that a correct vendor sent the received message;

if the non-update message is received, the first process records the received message and returns to the standby state;

if the update instruction message is received, the first process

invokes a user-defined update reception process procedure,

refers to the module delete/add instruction information in the received message,

stores in the one of the user computers the modules to be added specified by the update instruction message,

installs the modules to be added if acceptable,

records the received message and a process result, and

returns to the standby state.

49. The software distribution/maintenance method according to any of claim 45 to claim 48, wherein if the first process receives a message from a sending vendor, and stores or installs in the one of the user computers new software, newly served software, or updated software received from the sending vendor, then the first process monitors a result of processes and sends to the second process via the network a process result confirmation message informing whether the processes have terminated normally or abnormally.

50. A software distribution/maintenance system having a plurality of user computers and a vendor computer to manage and automatically update object software provided for the plurality of user computers from the vendor computer, comprising:

network means for connecting the user computers to the vendor computer; and

process means in each of the user computers, for sending current configuration information of the object software stored in the user computers to the vendor computer via said network means to inquire about a latest configuration, for receiving an answer from the vendor computer, and for updating the object software stored in the user computers according to an instruction in a received answer.

51. The software distribution/maintenance system according to the claim 50, wherein said process means in the user computers automatically informs via said network means the vendor computer of an abnormal termination and state if an operation of the object software abnormally terminates in the user computers.

52. The software distribution/maintenance system according to claim 51, wherein said process means automatically informs the vendor computer of the abnormal termination, an instruction causing the abnormal termination, a reason for the abnormal termination, a series of instructions which invoked the instruction causing the abnormal termination, and an environment of software and hardware used when the abnormal termination is detected.

53. The software distribution/maintenance system according to claim 51, wherein said process means automatically informs via said network means the vendor computer of the abnormal termination by general-purpose electronic mail.

54. A software distribution/maintenance system having a plurality of user computers and a vendor computer to manage and automatically update object software provided for the plurality of user computers from the vendor computer, comprising:

network means for connecting the user computers to the vendor computers; and

process means in the vendor computer for receiving an inquiry from the user computer, for generating update instruction information for the object software to match a configuration of the object software in the user computer with the configuration of an updated version in an object software library stored in the vendor computer, and for returning via said network means to the user computer the update instruction information and the updated version of the object software.

55. A software distribution/maintenance method for managing and automatically updating a set of object software stored in user computers from a vendor computer via a network, comprising:

sending by a process in the user computers current configuration information of the object software to the vendor computer via the network to inquire about a latest configuration;

receiving by the process an answer with update instruction information from the vendor computer; and

updating the object software according to the update instruction information about the object software to match a configuration of the object software with the latest configuration stored in an object software library in the vendor computer, including preparing for compiling and linking of programs if necessary.

56. The software distribution/maintenance method according to claim 55, wherein when the object software is activated in the user computers, the process in the user computers

immediately sends the current configuration information of the object software to the vendor computer via the network to inquire about the latest configuration,

receives the answer from the vendor computer, updates the object software according to the update instruction information in the answer, and

prepares for compiling and linking of programs if necessary.

57. The software distribution/maintenance method according to claim 55, wherein when the process is activated in the user computers at a predetermined time, the process

sends the current configuration information of the object software to the vendor computer via the network to inquire about the latest configuration,

receives the answer from the vendor computer,

updates the object software according to the update instruction information in the answer, and

prepares for the compiling and linking of programs if necessary to realize an automatic update of the object software.

58. The software distribution/maintenance method according to claim 55, wherein when a user instructs the user computers to activate the process, the process

sends the current configuration information of the object software to the vendor computer via the network to inquire about the latest configuration,

receives the answer from the vendor computer, updates the object software according to the update instruction information in the answer, and

prepares for the compiling and linking of programs if necessary.

59. The software distribution/maintenance method according to claim 55, wherein following processes are interchangeably performed:

when the object software is activated in the user computers, the process

immediately sends the current configuration information of the object software to the vendor computer via the network to inquire about the latest configuration,

receives the answer from the vendor computer,

updates the object software according to the update instruction information in the answer, and

prepares for compiling and linking of programs if necessary;

when the process is activated in the user computers at a predetermined time, the process

sends the current configuration information of the object software to the vendor computer via the network to inquire about the latest configuration,

receives the answer from the vendor computer,

updates the object software according to the update instruction information in the answer, and

prepares for the compiling and linking of programs if necessary to realize an automatic update of the object software; and

when a user instructs the user computers to activate the process, the process

sends the current configuration information of the object software to the vendor computer via the network to inquire about the latest configuration,

receives the answer from the vendor computer,

updates the object software according to the update instruction information in the answer, and

prepares for the compiling and linking of programs if necessary.

60. A software distribution/maintenance method for managing and automatically updating a set of object software stored in user computers from a vendor computer via a network, comprising:

receiving by a process stored in the vendor computer an inquiry from an inquiring user computer about current configuration information of the object software, in the user computer;

generating update instruction information about the object software to update the current configuration of the object software in the user computer with a latest configuration version in an object software library in the vendor computer; and

returning the update instruction information and an updated version of the object software to the inquiring user computer via the network.

61. A software distribution/maintenance system for managing distribution of object software via a network accessed by users of user computers who use sets of the object software distributed, managed, and maintained by software vendors who supply the users with the object software from at least one vendor computer, comprising:

a network for connecting each user computer and the at least one vendor computer; and

process means in each user computer for executing the object software to be used by the users, for managing the sets of object software in each user computer, for sending via the network an object software distribution/maintenance request message according to an instruction of the users or an instruction of a user-written program to the at least one vendor computer which has a software library containing the object software, for receiving an answer message from the at least one vendor computer, and for distributing or maintaining the object software.

62. The software distribution/maintenance system according to claim 61, wherein when any object software managed by said process means in each user computer abnormally terminates during operation, said process means detects and analyzes an abnormal condition, and then automatically sends a fault report to the at least one vendor computer via said network.

63. The software distribution/maintenance system according to claim 61, wherein

each user computer can store user management data for each of the users or each user group, and for each set of the object software;

and

said process means refers to the user management data to manage one or more sets of the object software.

64. The software distribution/maintenance system according to claim 63, wherein said user management data includes user identification information of each user or each user group, software management information of each set of the object software used by each user, software configuration information, and message process method specification information.

65. The software distribution/maintenance system according to claim 64, wherein in specifying a method of processing a message according to the user management data, the users can specify a process method as a procedure for each function performed by said process means.

66. The software distribution/maintenance system according to claim 65, wherein in specifying a method of processing a message according to the user management data, a vendor confirmation procedure can be used so that the vendor can be confirmed to protect user software.

67. A software distribution/maintenance system for managing distribution of object software via a communications network accessed by users of user computers use sets of the object software distributed, managed, and maintained by software vendors who supply the users with the object software from at least one vendor computer, comprising:

network means for connecting each user computer and the at least one vendor computer;

vendor software libraries; and

process means for providing services relating to said vendor software libraries, for receiving an object software distribution/maintenance request message from an inquiring user computer via said network means, for referring to one of said vendor software libraries, managed by a vendors according to contents of the object software distribution/maintenance request message and settings of the vendor, for generating an answer message in response to the object software distribution/maintenance request message, and for sending the answer message to the inquiring user computer via said network means.

68. The software distribution/maintenance system according to claim 67, wherein when any object software abnormally terminates during operation in one of the user computers, said process means sends a fault report received from the one of the user computers via said network means to the vendor of the object software which abnormally terminated.

69. The software distribution/maintenance system according to claim 67, wherein when said process means of the at least one vendor computer offers services using said vendor software libraries, said process means refers to vendor management data stored for each vendor software library.

70. The software distribution/maintenance system according to claim 69, wherein

said vendor management data can be designed to comprise vendor identification information, software management information, software configuration information, message process method specification information, customer information, and fault history information.

71. The software distribution/maintenance system according to claim 70, wherein when a message process method is specified using the vendor management data, the software vendors can specify the message process method as a procedure for each function performed by said process means.

72. The software distribution/maintenance system according to claim 70, wherein

a user confirmation procedure can be selected when a message process method is specified using the vendor management data.

73. A software distribution/maintenance method for managing distribution of object software via a network accessed by users of user computers who use sets of the object software distributed, managed, and maintained by software vendors who supply the users with the object software from at least one vendor computer using, in each user computer, the object software to be used by the users and a process managing the sets of the object software, and the network connecting each user computer and the at least one vendor computer, comprising:

activating by the users the process through a command input by the users or through a command from a user-written program;

sending by the process via the network an object software distribution/maintenance request message to the at least one vendor computer from which the object software is provided;

receiving by the process the answer message from the at least one vendor computer; and

performing processes for at least one of distributing and maintaining the object software according to the answer message and settings made by the users.

74. A software distribution/maintenance method for managing distribution of object software via a network accessed by users of user computers who use sets of the object software distributed, managed, and maintained by software vendors who supply the users with the object software using, in each vendor computer, vendor software libraries and a vendor process providing services relating to the vendor software libraries, the network connecting each user computer and each vendor computer, said software distribution/maintenance method comprising:

receiving by the vendor process an object software distribution/maintenance request message from one of the user computers via the network;

referring by the vendor process to the vendor software libraries managed by one of the vendors according to the object software distribution/maintenance request message and settings made by the one of the vendors;

generating an answer message in response to the object software distribution/maintenance request message; and

sending the answer message to the one of the user computers which issued the object software distribution/maintenance request message.

75. A software distribution and maintenance system using a network in which a plurality of users using a number of types of object software to be distributed, managed, and maintained, and a plurality of software vendors supplying the object software manage the distribution and maintenance of the object software over a computer network, comprising:

one or more first process means CP installed in each of user computers, that manage a plurality of object software groups to be used by one or more users individually for every object software and for every user;

one or more second process means installed in one or more software vendor computers, that each providing services to a Plurality of vendor software libraries for each of the software libraries; and

a network that connects the first process means installed in the user computer to the second process means, based on standardized communications protocols,

said first process means having a capability to perform distribution or maintenance of the object software by sending a message a request of distribution or maintenance of the object software for one piece of object software over the network, according to instructions given by one or more of the users or a user defined program, receiving an answer message from the second process means SP, and processing based on contents of the answer message and settings made by the users, and

said second process means having a capability to receive the message from each first process means to reference one or more of the software libraries managed by one or more of the vendors depending on the contents of the message and settings made by the vendors for the object software specified with the message, to generate the answer message to answer the request of distribution or maintenance of the object software, and to send the answer message to said first process means that generated the message.

76. The software distribution and maintenance system using a network according to claim 75, used by the users taking advantage of one or more pieces of the object software included in the object software groups, and the vendors supplying one or more pieces of the object software in the object software groups, wherein one or more computers each comprise both said one or more first process programs and said one or more second process means.

77. The software distribution and maintenance system using a network according to claim 75, wherein the message, sent and received over said network between said first process means installed in one of the user computers, and said second process means installed in one of the vendor computers, consists of a header part of the message, an attribute part as fixed data, an instructing part as a specific request and instruction data, and a module part as corresponding software.

78. The software distribution and maintenance system using a network according to claim 75, wherein the attribute part forming a part of the message is configured as hierarchical structure data of a pair of a keyword and a value, facilitates referencing and updating management data for user set for every object software and for every user, and management data for vendor set for every object software library and for every vendor.

79. User computers used in a software distribution and maintenance system using a network in which a plurality of users using a plurality of types of object software to be distributed, managed, and maintained, and a plurality of software vendors supplying the object software manage the distribution and maintenance of the object software over said network, comprising:

one or more process means that manage a plurality of object software groups to be used by the users individually for every object software and for every user using the object software; and

storage means for storing management data for user set for every user for every object software and user process procedures which are process procedures for said process means to distribute and maintain the object software, set for every object software and for every user, said process means calling said user process procedures to reference the management data for user, send a message to request distribution and maintenance of the object software to the vendor of the object software over said network according to standardized protocols in the system, and perform distribution and maintenance of the target software.

80. The user computers in the software distribution and maintenance system using a network according to claim 79, wherein the management data for user includes user identification information corresponding to each user, vendor identification information corresponding to each object software vendor, software identification information corresponding to each object software, and environment information.

81. The user computers in the software distribution and maintenance system using a network according to claim 79, wherein each user process procedure comprises:

message-editing procedures that edit a message to request distribution and maintenance sent from said user process procedure to the vendor of the object software;

a vendor verification procedure that verifies a vendor of the object software; and

reception process procedures that process an answer message from the vendor of the object software.

82. The user computers in the software distribution and maintenance system using a network according to claim 79, each comprises said management data for user, said user process procedures, and said first process means for each of the plurality of versions of the object software so that every user can utilize the plurality of versions.

83. The user computers in the software distribution and maintenance system using a network according to claim 79, each comprises data for specifying a plurality of versions for said management data for user, and both said user process procedures and said first process means for the plurality of versions so that every user can utilize a plurality of versions of an identical piece of the object software at the same time.

84. A vendor computer in a software distribution and maintenance system using a network in which a plurality of users using a plurality of types of object software to be distributed, managed, and maintained, and a plurality of software vendors supplying the object software manage the object software distribution for distributing the object software over said network, comprising:

at least one process means for providing services of each of the software libraries and each of the vendor software libraries; and

storage means for storing management data for vendor set for every vendor and for every software library, and vendor process procedures which are process procedures for said process means to distribute and maintain the object software on the user computers, set for every vendor and for every software library, said process means performing a corresponding process for a message of the object software from the user, set for every vendor and for every object software library.

85. The vendor computer in the software distribution and maintenance system using a network according to claim 84, wherein said management data for each vendor includes user identification information concerning all the users of the object software, vendor identification information concerning the vendor of the object software library, software information concerning the object software library, and environment information.

86. The vendor computer in the software distribution and maintenance system using a network according to claim 84, wherein said vendor process procedures include a user qualification verification procedure for the object software, an unqualified user process procedure, reception and answer process procedures for analyzing a message received from the user, and generating an answer message.

87. The vendor computer in the software distribution and maintenance system using a network according to claim 84, wherein said object software library includes a plurality of versions of the object software, and said process means corresponding to the object software library gives services to said object software library using management data for vendor and vendor process procedures that correspond to a plurality of versions.

88. A software distribution and maintenance method in which a plurality of users using a plurality of types of object software to be distributed, managed, and maintained, and a plurality of software vendors supplying the object software, manage distribution and maintenance of the object software, said method utilizing at least one first process in each of a plurality of user computers, that manage object software groups to be used by the users individually for every object software and for every user using the object software, at least one second process in vendor computers, that provide services to vendor software libraries for each of the vendor software libraries, and a network that connects the user computers to the vendor computers standardized communication protocols, said method comprising:

invoking a first process with a command entered by one of the users on one of the user computers or with a command invoked from a user-defined program;

sending a request message from the first process to request distribution or maintenance of at least one piece of the object software to a second process managing at least one of the vendor software libraries of the object software;

receiving the request message by the second process in one of the vendor computers;

generating an answer message to answer the request message by referencing at least one of the vendor software libraries managed by at least one of the software vendors for the at least one piece of the object software specified by the request message;

returning the answer message to the first process;

receiving the answer message by the first process; and

processing the answer message depending on contents of the answer message and settings made by the one of the users for the distribution or maintenance of the at least one piece of the object software.

89. The software distribution and maintenance method using a network according to claim 88, wherein the first process means installed in the user computers, which is invoked with a command entered by the user on the user computers, or a command in a user-defined program, calls a message-editing procedure which is one of user process procedures for distributing and maintaining the object software, edits a message to request distribution and maintenance based on the standardized protocols within the system while referencing the management data for user set for message and generating an answer message, references the object software library while referencing and updating said management data for vendor, and generates an answer message for distribution and maintenance of the object software in response to the received message to request distribution and maintenance, and returns the answer message to the first process means.

90. The software distribution and maintenance method using a network according to claim 88, wherein the first process installed in the user computers,

receives the answer message returned from the second process in response to the request message sent by the first process to request distribution or maintenance of the object software,

verifies that the answer message is returned from a legal vendor,

calls a reception process procedure which is one of user process procedures set for the one of the users and for the object software,

performs distribution and maintenance of the object software according to contents of the answer message, and

prepares for execution of the object software according to a determination made by the first process while referencing and updating management data for user set for the one of the users and for the object software.

91. The software distribution and maintenance method using a network according to claim 88, wherein the first process installed in the one of the user computers

receives the answer message returned by the second process in response to the request message sent by the first process to request distribution and maintenance of the object software,

performs distribution and maintenance of the object software according to the answer message, and

then automatically returns a response message to the second process indicating whether the distribution and maintenance was properly executed on the one of the user computers.

92. The software distribution and maintenance method using a network according to claim 88, wherein said second process installed in the vendor computers

receives the request message from the first process to request distribution and maintenance of the object software belonging to the vendor software libraries managed by the second process,

verifies that the request message to request distribution and maintenance is sent from a legal user by referencing user identification information included in vendor management data set for the software vendors and for the vendor software libraries,

calls a reception/answer process procedure for analyzing the request message and generating the answer message,

references the at least one of the vendor software libraries while referencing and updating the vendor management data,

generates the answer message for distribution and maintenance of the object software in response to the request message to request distribution and maintenance, and

returns the answer message to the first process.

93. The software distribution and maintenance method using a network according to claim 88, wherein a message, which is sent and received over the network between the first process means (CP) installed in one of the user computers and the second process means installed in one of the vendor computers, consists of a header part of the message, an attribute part as fixed data, an instructing part, a specific request and instruction data, an instructing part as instruction data, and a module part as corresponding software.

94. A method for purchasing new software in a software distribution and maintenance system using a network, in which a plurality of users using a plurality of types of object software to be distributed, managed, and maintained, and a number of software vendors supplying the object software manage the distribution and maintenance of the object software over a network, comprising:

one of the users sending a message to request summary information of the object software from first process means in the user computers to second process means over said network by use of any of the first process means which simply has the capability to request summary information and of receiving an answer message to the request of summary information;

the second process means providing basic components of the first process means and user process procedures sufficient for a new purchase of the object software as part of the answer message in response to the summary inquiry to the user computers over the network;

the user sending a message to request a new purchase to the second process means over the network using the basic components of the first process means and the user process procedures;

the second process means providing the whole set of said first process means and user process procedures appropriate for the distribution and maintenance of the object software to the user'"'"'s first process means over the network;

the user computers thereafter distributing and maintaining the object software using the first process means and the user process procedures.