JPH0954734A - System and method for software distribution/maintenance utilizing network - Google Patents

Abstract

PROBLEM TO BE SOLVED: To make a user quickly and appropriately acquire and utilize software generated/updated by a provider between many software providers and many users. SOLUTION: This system is equipped with one or more first processing means(client program:CP) which manage a target software group on each user computer at every user and software, one or more second processing means(server program:SP) which provide a service to a software library group on each provider computer at every software library, and a network which connects the first processing means(CP) to the second processing means(SP) based on an integrated message protocol.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention enables a software provider to provide software to a large number of users via a network and update / maintain the software. Software distribution / maintenance system and method utilizing a network so that the latest version can be obtained at any time from a software provider of.

[0002]

2. Description of the Related Art The following is known as a conventional technique for distributing / obtaining software update information. (A) Method of Providing Software by Portable Medium The most usual method is to store the software in a portable medium such as a magnetic tape or a magnetic floppy disk and provide it.

In this case, it is necessary to individually provide the user with correction of a bug, addition of a function, provision of a new version (hereinafter referred to as updated software information), etc. using the same medium.

To install such software on the user's computer, the provider goes out to the user's place or the user himself or herself. (B) Method of sending software by provider via network Software and updated software information are sent from the provider to the user via the network in response to a request from the user (or under the initiative of the provider). These pieces of information are temporarily stored as data. In order to use it on the user computer, the user needs to (re) install according to the instruction information from the provider. (C) Method for user to obtain software via network Place a library of software on a computer file of a provider (or an alternative institution thereof), and a user accesses the library via a network to obtain necessary items. The updated software information is also acquired by the user. It is the user's responsibility to make the software available on the user's computer. The acquisition tool does not manage the update of the target software.

By the way, the above-mentioned method is (a) (b)
As shown in (4), the provider individually distributes the software, or, as shown in (c), the software is acquired by the user. And, the decision of which part of the software (module, etc.) to send / obtain, and the installation and re-installation of the software are all done manually, and this inconvenience causes many inconveniences and problems. Is occurring.

Further, from the viewpoint of the provider side, even one piece of provided software can be appropriately used because it is obtained by a large number of users at various times and managed separately. Assure and face many problems in servicing.

Therefore, as a system for automatically updating and maintaining software via a network, the following system was first proposed as a first prior application (1994 1994).
Application on August 8: Japanese Patent Application No. 6-14706).

FIG. 8 is a diagram showing the configuration of the above system. In FIG. 8, reference numerals 101-1 and 101-2 denote the computers of user A and user B, respectively, and the respective computers 101-1 and 101-2. Is installed with a client program (CP) 101a for automatically updating software on the user computer and transmitting fault information. Further, software 101b and software 101b 'are placed in the computers of user A and user B, respectively, and these are the client program 101a.
Is managed by

Reference numeral 102 denotes a provider computer, and the provider computer 102 has a server program (SP) 102a for automatically updating software on the user computer.
And a software library 102b managed by the server program 102a.

Further, 103 is a network, and the client program 101a and the server program 102a exchange information via the network. In the figure, a user A is a user computer 101-
When the software 101b on the first server is to be started, the client program 101a detects it, collects the information of the current version, and inquires via the network 103 to the server program 102a on the computer 102 of the provider. In the example of the figure, the software 101b of the user computer 101-1 has module groups Ma, ..., Mi ,.
This information is sent to the network 10 because it is composed of Mm.
3 to send an inquiry to the server program 102a.

When the above information is received, the server program 102a on the provider side receives the software library 1
In comparison with the configuration of 02b, software 101 of user A
The instruction information for updating b and the updated software are returned. In the example of the figure, the module Mi is updated to Mi *, and the instruction information for adding the module Mn, the updated version module Mi *, and the new module Mn are returned.

User A's client program 10
1a automatically updates the software 101b to the latest version by using the above information, and the software 101b of the user A is updated.
Is updated to the latest version like the software 101b 'of the computer of the user B. After that, the client program 101a activates the latest version of the software as instructed by the user A.

Further, even when a new user obtains the software, the above software main body can be obtained only by obtaining and installing the client program 101a whose software is updated and managed.

That is, when the client program is started as if the software already exists on the user's computer, the client program makes an inquiry to the computer of the provider and provides it as described above. You can get the latest software from your computer.

However, as a general situation these days, computer software has become large in number, large-scale, complicated, and sophisticated, and the number of users using it has increased rapidly (thousands, numbers). It's diversified and decentralized. On the other hand, even from the perspective of each user,
It uses various software.

Under such circumstances, it is a great burden on both the provider side and the user side to properly provide / obtain / manage / update / improve the computer software used by the user. There is.

The system shown in FIG. 8 is proposed from the above viewpoint, but the system in the first prior application also has the following limitations and problems. That is, the basic settings of the system of FIG. 8 are as follows. The provider's computer and the server computer on the provider's computer are each one, and the target software library managed by the server program is one.
One. Furthermore, there is one updated version (latest version) of the target software library. Although there are a large number of users and user computers, each user has one client program on the computer and each client program also manages one piece of target software. Furthermore, there is one updated version (latest version) of each target software. There is no limit to the network.

For this reason, the following limitations and problems occur. <Problem 1> There is a great deal of diversity among many users. For example, differences in the computer used, differences in the software environment on the computer used, differences in general proficiency with the computer, differences in proficiency and purpose of use of the target software, differences in the usage patterns of the user computer (multi-person Common use, personal use, etc.), etc.

In view of these diversity, the client
There is a lack of diversity in processing by the program, and
The software provider does not fully consider the adaptation to the variety of these users. <Problem 2> Diversity among many software
It also has many effects on distribution and management.

For example, "commercial software", "public shared software", "internal software", "hardware embedded", "basic software (OS)", "applied software", "operating system".
And "online software" and "batch run software",
There are various types of software such as "load module provision", "object module provision" and "source provision" that differ in distribution form / usage, type, provision form, etc. Has not been clarified and cannot be fully dealt with. <Problem 3> Even when one user handles one target software, there are some stepwise differences.

[0021] For example, "the stage where the right to obtain is not yet available"
And "stage of obtaining the right to obtain", "stage of initial installation not completed" and "stage completed""stage of beginner use", "stage of stable user" and "stage of advanced user"
There are differences such as "conventional version use stage", "new version acquisition trial stage", "new version switching use stage", "conventional environment stable use stage", "new environment transition trial stage", and "new environment use stage".

Even with respect to these stepwise differences, it is necessary to operate so that appropriate software services can be obtained.
Each user wants, but isn't fully considered. <Problem 4> One user uses a large number of target software, and the providers of these software are different from each other. The system shown in FIG. 8 is managed by an individual management system centered on each provider, but a more unified and convenient system is required for users.

That is, there is a need for a software providing form and its technology that can be used in a unified manner by many and various target softwares, many and various software providers, and many and various users.

In order to solve these four problems, the applicant of the present invention previously proposed a system described below as a second application (filed on February 8, 1994:
Japanese Patent Application No. 6-14710).

FIG. 9 is a basic block diagram of the software distribution / maintenance system in the second prior application. This system is an extension of the technology of the first prior application, and in order to enable distribution and maintenance of a large number and variety of target software, the client program CP on the user computer 111 is used by a plurality of users. Expanded to manage multiple target software at the same time,
Also, on the provider computer 113, the server program SP
Has extended it to manage multiple target software libraries.

Therefore, the user computer 111 is provided with user management data (UD) for software distribution and maintenance and a user processing procedure (UP) (not shown) corresponding to each target software of each user. Similarly, the provider computer 113 is provided with provider management data (VD) and a provider processing procedure (VP) (not shown) corresponding to each target software library.
The client program CP and the server program SP execute necessary processing using these data.

Further, the distribution / maintenance message protocol is extended so that software overview inquiry, new acquisition, additional acquisition, update inquiry, trouble report, and comment transmission can be performed under the initiative of the user.

The purpose of the second prior application is to solve the problems of the first prior application, that is, the above problems 1 to 4, and the main solution used in the second prior application is The following solutions 1 to 6.

Solution 1. A protocol for requesting software distribution / maintenance and a reply message between a provider and a user is determined so as to be general-purpose in consideration of the variety of software, users, and providers.

Solution 2. On the provider computer, various types of information for software distribution and maintenance are clearly separated and set as provider management data (VD) so that the variety of providers, software, and users can be handled. V
The content and internal structure of D may be individually set by the provider.

Solution 3. In order to handle the diversity of providers, software, and users on the provider computer, a server program (SP) that processes the server for software distribution / maintenance with a common skeleton It is clearly separated and set to the processing procedure (VP) group for the provider who performs the processing. The specific processing method of the VP may be individually set by the provider.

Solution 4. On the user computer, various types of information for obtaining and updating software are clearly separated and set as user management data (UD) so that the variety of users, software, and providers can be handled. U
The content and internal structure of D may be individually set by the user.

Solution 5. On the user computer, a client program (CP) that performs common skeleton processing for client processing for software acquisition / update and specific processing so that the diversity of users, software, and providers can be handled. And the processing procedure (UP) group for the user who performs The specific UP processing method may be individually set by the user.

Solution 6. A client program (CP) that performs common processing as described above on each user computer
One is placed, and the user management data (UD) and the user processing procedure (UP) are placed for each target software of each user. One CP handles acquisition / update processing for a plurality of users and a plurality of target software. Similarly, one server program (SP) that performs common processing is placed on each provider computer, and the provider management data (VD) and provider processing procedure (VP) are provided for each target software library. Put. 1 SP
Processes the distribution and maintenance of multiple target software libraries.

[0035]

With the technique of the second prior application, a method for solving the problems 1 to 4 in the first prior application has been found. However, the second prior application has a new problem which is not present in the first prior application.

As shown in FIG. 9, in the second prior application, a client program on a computer is expected to handle a plurality of target software of one or a plurality of users on each computer. Therefore, the client program CP is required to handle a plurality of users and a plurality of target software while permitting their versatility. Therefore, its design is complicated,
And becomes difficult, especially for user processing procedures (UP)
There was a problem that the handling of the interface for calling and the parallel processing of multiple processing requests from the user became complicated and difficult. The same problem occurred with the server program SP.

The present invention is a client program CP.
And to build a uniform technical framework suitable for the software distribution or software distribution on a global scale without complicating the design of the server program SP. In other words, it is a system that uses a communication network between computers, targeting a large number and a variety of software on a global scale, with a large number and a variety of software providers participating, and a large number and variety of software users. An object of the present invention is to provide a software distribution / maintenance system and method having a function that allows a user to quickly and appropriately obtain and use software created and updated by a software provider.

The objects of the present invention will be more specifically described by organizing the items, and summarized in the following first to tenth objects.
First, a first object of the present invention is to distribute a large number of various target software to a large number of various software providers and a large number of various users in a unified manner so that a software distribution utilizing a network can be performed. It is to provide a maintenance system and method.

A second object of the present invention is to provide a software distribution / maintenance system and method utilizing a network, which allows a user to quickly and appropriately obtain and use software created / updated by a software provider. It is to be.

A third object of the present invention is to allow a user of a computer connected to a network to mutually and swiftly and appropriately obtain software of another user. Software distribution and maintenance utilizing the network. A system and method are provided.

The fourth object of the present invention is to obtain a software outline inquiry, a new acquisition request, an update inquiry, a new service acquisition request,
It is an object of the present invention to provide a network-utilized software distribution / maintenance system and method by which a user can request / reference a software provider in various forms.

The fifth object of the present invention is to distribute and maintain various software such as product software, shareware, freeware, academic prototype software, software used in an organization, etc.
To provide a software distribution / maintenance system and method utilizing a network.

A sixth object of the present invention is that even unskilled users can obtain new software or updated software in a form that can be immediately used.
To provide a software distribution / maintenance system and method utilizing a network.

A seventh object of the present invention is to provide a software distribution / maintenance system utilizing a network, which allows a software provider to immediately recognize that a software failure has occurred and to promptly deal with the software failure. Is to provide a method.

An eighth object of the present invention is to provide a network in which a program for managing target software of each user of a user computer and a program for managing each software library of a provider computer can be made common. It is to provide a software distribution / maintenance system and method that utilize it.

A ninth object of the present invention is to allow a procedure to set a method of processing a message exchanged between a user computer and a provider computer, and to cope with various requests from the user and the provider. It is to provide a software distribution / maintenance system and method that utilizes a network.

The tenth object of the present invention is to confirm the provider,
PROBLEM TO BE SOLVED: To provide a software distribution / maintenance system and method utilizing a network, which can set a processing method for judging user qualification by a procedure and can cope with various distribution modes of software between users or providers. Is.

[0048]

FIG. 1 is a block diagram showing an example of the principle configuration of the present invention. In the figure, 1 to 3 are user computers, 4 and 5 are provider computers, and 6 is a general-purpose network connecting the user computer and the provider computer.

Each of the user computers 1 to 3 is generally one.
The user computer 1 is used by the user U1, the user computer 2 is used by the users U2 and U3, and the user computer 3 is used by the user U4. The provider computers 4 and 5 are generally used by one software provider respectively, and the provider computer 4 is a provider V1 and a provider computer 5 respectively.
Is used by provider V2.

On the user computer, generally, one or more target software (software to be distributed and maintained) corresponding to each of one or more users is generally placed, and corresponding to each target software. User management data UD and a first processing means such as a client program CP are placed.

For example, in the user computer 2, the target software S2.b and S1.c are placed corresponding to the user U2, and the user management data UD and the client program CP correspond to the respective target software. The target software S2.a, which corresponds to the user U3,
User management data UD and a client program CP are stored. Here, for example, S1 and S2 indicate the target software, and a, b, and c indicate the respective versions.

The first processing means, for example, the client program CP handles only one target software of one user, and has dedicated user management data UD.
And the user processing procedure (UP) group described later are used to distribute and maintain the target software. That is, various messages such as a software request from a user to a provider, an update inquiry, and a failure report are transmitted, and a reply message is received from the provider to perform processing such as updating the software of the user. In the process of sending / receiving this message, the process is executed according to the protocol unified in the software distribution / maintenance system.

The user management data UD is composed of user identification information, provider identification information, software management information, etc. This data is used in processing such as message transmission by the client program CP and user software update.

Each of the provider computers 4 and 5 is used by one provider. For example, inside the provider computer 4, SL (S1) and SL (S2) are provided as software libraries provided by the provider V1, and the management data VD for the provider is provided corresponding to each.
And a second processing means such as a server program SP.

The software library SL (Si) generally consists of a plurality of versions of the target software Si. For example, the software library SL (S3) inside the provider computer 5 has two version types S3.a of the target software S3. It consists of S3.b.

The management data VD for provider is composed of provider identification information, user management information, software management information, etc., and is used by the second processing means, for example, the server program SP.

Like the client program CP on the user computer, the server program SP handles only one target software library of one provider, and has a dedicated provider management data VD and a later-described provider program. A processing procedure (VP) group is used to perform distribution / maintenance processing of the target software. The network 6 is a general-purpose network, but the client program CP on the user computer and the server program S on the provider computer.
It enables message communication with P. By standardizing the protocol, it becomes possible to send and receive messages regarding distribution and maintenance of software between a user and a provider. The network 6 may be always connected, or may be connected as needed and may be capable of sending and receiving messages such as e-mail.

In FIG. 1, the user computer and the provider computer are generally different from each other, but some computers are used by the user who has both the role of the user and the provider, and one computer is used. It is also possible that the client program CP and the server program SP are mixed in each other, and in this case, the operations of the client program CP and the server program SP are exactly the same.

As described above, the provider side manages and provides a large number of versions of one piece of software to be provided to a large number of users, while the user side has a specific one version for each piece of software. However, they are using a large number of software (provided by different providers) simultaneously. In this way, the relationship between the provision / use of software is
The present invention is premised on the fact that it is a multi-provider x multi-user x multi-software.

The structure of the present invention will be further described below with reference to FIG. 1. The present invention uses a large number of users U1, U2 who use various types of target software S1, S2, ... ,, and a large number of software providers V1, V2 that provide the above target software.
... is a software distribution / maintenance system utilizing a network for managing the distribution of the target software via the computer network 6, and (a) is placed on each of the user computers 1 to 3 and has a user U1, U2. 、…
Target software groups S1, S2, ...
And one or a plurality of first processing means CP for managing the target software group (S1, S2, ...) For each target software and for each user who uses the target software, and (b) each. It is placed on the computer 4 or 5 of the software provider, and the software library group SL for the provider
(S1), SL (S2), ..., For each software library of the software library group, one or a plurality of second processing means SP for providing a service related to the software library, and (C). A network 6 connecting the first processing means CP on the user computer and the second processing means SP on the provider computer based on the unified message protocol is provided, and (d) each first processing The means CP responds to the instructions of the users U1, U2, ... Or the instruction of the program set by the user with respect to one piece of target software, and sends a message requesting distribution and / or maintenance of the target software via the network 6.
It transmits to the second processing means SP corresponding to the above target software, receives a reply message from the second processing means SP, and the content of the reply and the users U1, U2.
Has a function of performing processing for distribution and / or maintenance of the target software according to the setting of (...), and (e) each second processing means SP receives the above message from any first processing means CP. Then, for the target software specified in the message, the providers V1, V2 are set according to the contents of the received message and the settings of the providers V1, V2, ....
Software library SL (S managed by 2, ...
1), SL (S2), ..., Create a reply message for distribution and / or maintenance request of the target software, and reply to the first processing means CP of the sender of the message via the network 2. It is configured to have a function of sending a message.

Next, the distribution of software according to the present invention
The maintenance method is explained. In FIG. 1, user U
When 1, U2, ... Specify desired software (target software) and its providers V1, V2, ... And activate an acquisition inquiry command, the first processing means CP causes the software providers V1, V2 ,. Send an inquiry message to the user.

The second processing means SP corresponding to the target software library on the provider side receives this, checks the user's qualification, and automatically processes according to the setting of the management data VD for the provider, Return to.

The first processing means CP, which has transmitted the acquisition inquiry message, receives this reply and relays it to the user. When the body of the software is returned, the first processing means CP gives an instruction in the reply. Store the software according to the information.

Further, the first processing means CP can refer to the user management data UD, perform necessary translation / combination, etc. according to the setting, and automatically install the software in the prepared area.

Further, in the case where the software currently used by the users U1, U2, ... Is inquired as to whether or not there is any subsequent update / improvement, if a new version is automatically obtained if updated, The users U1, U2, ... Start the first processing means CP by designating the software name for which update inquiry is desired. The first processing means CP refers to the user management data UD, extracts the configuration of the software Si.V currently used by the user, adds the user identification information, and provides the providers V1, V2. ... Send an automatic update inquiry message to the address.

When the corresponding second processing means SP receives this, the qualification of the user is checked according to the setting of the management data VD for the provider, and the software update information is returned to the user. As update information, for example, when the software has not been updated, “no update” is returned to the qualified user, and when the software is updated, “update processing at user's site” "Method" and "Software required for update".

Upon receiving the reply, the first processing means CP first stores, for example, the updated software according to the setting of the management data UD for the user with respect to the content of the reply message, and then gives the update instruction during the reply. According to the information etc., it replaces the old version and, if necessary, translates and combines it to make the new version executable.

The update inquiry can be started up by the user, automatically when the software is called by the user, and the time specified by the daemon program (for example, every day,
Weekly, monthly, etc.)

When the software managed by the first processing means CP on the user computer terminates abnormally during its execution, the first processing means CP detects the cause and situation of the abnormality, and the provider V1 , V2, ... Automatically sends a failure report message.

The corresponding second processing means SP records this and reports it to the person in charge of development. Also, a message indicating that the failure information has been received is returned to the user. For bug correction work, the person in charge of development makes corrections manually and registers it in the target software library of the provider. After that, the updated version is provided to the user as the latest version.

The software distribution / maintenance method of the present invention will be further described with reference to FIG.
In the present invention, a large number of users U1, U2, who use various types of target software to be distributed, managed, and maintained.
... and a large number of software providers V1, V2, ... Providing the above target software, a software distribution / maintenance method utilizing a network for managing the distribution of the above target software via the computer network 6. , The target software groups S1, S2, ... For use by the users U1, U2 ,.
2, ...) for each target software and for each user who uses the target software, and one or a plurality of first processing means CP and a computer 4, 5 of each software provider. , Software library groups for providers SL (S1), SL (S2), ... And for each software library of the software library group, one or a plurality of first services that perform services related to the software library. Using the second processing means SP and the network 6 connecting the first processing means CP on the user computer and the second processing means SP on the provider computer based on the unified message protocol. The following processing is performed. (A) Each user U1, U2, ... Is the first corresponding to one target software by the command input by the user U1, U2 ,. The processing means CP is activated, and (b) the second processing means S corresponding to the target software is sent via the network 6 a message requesting distribution and / or maintenance of the target software.
(C) On the provider computer of the target software, the second processing means SP makes the first processing means C.
The message from P is received, and for the target software specified in (d) message, the provider V is in accordance with the contents of the received message and the settings of the providers V1, V2 ,.
Software library SL managed by 1, V2, ...
(S1), SL (S2), ... Referring to (S1), SL (S2), ... The reply message is sent, and (e) the users U1 and U who are the sender of the message.
2, the first processing means CP receives the reply message from the second processing means SP, and according to the contents of the reply and the settings of the users U1, U2, ... Perform processing for distribution and / or maintenance.

As described above, according to the present invention, the first processing means, for example, the client program CP is placed on the user computer for each target software and each user,
In addition, a second processing means, for example, a server program SP is provided for each software library on the provider computer,
Client program CP and server program S
By performing the message transfer with P under the unified protocol, even if it seems to be individual for each software, it can be unified in a very wide range, for example, on a global scale. It is possible to realize a software distribution / maintenance system and method.

[0073]

2 is a system configuration block diagram of an embodiment of a software distribution / maintenance system utilizing a network of the present invention. In the figure, a user computer 11, a provider computer 13, and a user / provider computer 14 are connected via a network 12. Compared with FIG. 1, which shows the principle configuration of the present invention, the point that the user / provider computer 14 is used by a user who also plays the roles of the user of the target software and the provider is different. The user / provider computer 14 is provided with a client program CP corresponding to the target software and the user, a software library provided by the provider, and here a server program SP corresponding to SL (S3). Has been.

Further comparing FIG. 2 with FIG. 1, in FIG. 2, the user processing procedure (UP) group corresponding to each client program CP and the server program S are shown.
The difference is that a provider processing procedure (VP) group corresponding to P is added. The user processing procedure (UP) group and the provider processing procedure (VP) group will be described later.

Embodiments of the present invention will be described in detail below item by item based on the system configuration of FIG. (1) Configuration of software distribution / maintenance system using network The system in Fig. 2 is composed of the following elements.

Server program (SP) It is placed on each provider's computer for each software library to be provided. It is a program that responds to various inquiries and requests from users by returning necessary information and software, and performs reception and reply processing according to the software distribution and maintenance protocol.

Provider processing procedure (VP) group Called and used by the server program for reception / reply processing. The method of confirming user qualification and reply processing can be defined by reflecting the distribution policy of the provider. The management data for the provider (VD) and the software library (SL) to be provided are referenced and operated to perform the processing required by the server.

Provider management data (VD) Corresponds to the software library to be provided. It includes provider identification information, user management information (user database, user provision history, etc.), software management information (software configuration information, software usage environment information, software development history, software failure report database, etc.). These management data should be set and managed by the provider according to the provider's software development, maintenance, and distribution policies and methods.

Software library (SL (S
i)) The provider manages each piece of software (Si) to be provided. Multiple version types can be included to accommodate user requirements. It is composed of a number of modules, each module can belong to one or more version types. How the older version of the module is managed is at the discretion of the provider, but at least the latest version of the software may be configured for each version type.

Client Program (CP) It is placed on each user computer for each target software of each user. A program that sends various messages from the user to the provider, such as software acquisition requests, update inquiries, and failure reports, and receives replies from the provider to perform processing such as acquisition and maintenance of the target software of the user. is there. Performs message transmission / reception processing according to the software distribution / maintenance system protocol.

User process procedure (UP) group Called and used by the client program (CP) for creating a transmission message and for reply reception processing. The client management data (UD) and the target software are referenced and operated to perform the processing required by the client. You can use a procedure that suits your environment.

User management data (UD) Corresponds to the target software. It includes user identification information, provider identification information, and software management information (version information, software configuration information, usage environment information, etc.).

Target Software The software used by each user, which is the target of the distribution / maintenance service by the software distribution / maintenance system.
It is a piece of software provided by a certain provider, and usually consists of a certain version.

Network Messages are transmitted / received between each client program (CP) of each user and each server program (SP) of each provider. When each client program (CP) specifies the target software managed and its provider, the server program (SP) that manages the relevant software library of the relevant provider can be designated as the destination of the message. Can send messages. Also, the server program (SP) that has received this message has a function of specifying the client program (CP) that has sent it and sending a reply message. The network may be connected at all times or may be in the form of being occasionally connected (especially on the user side) such as e-mail so that messages can be sent and received.

Although the above components are described above, the user sometimes needs to use multiple versions of a certain piece of software. For example,
When migrating from one version type to another enhanced version type, when experimenting with the new version along with the current stable version, two versions with different functions
For example, when the types are used together. In these cases, the simplest is to use different client programs (CP), user processing procedures (UP), and user management data (UD). If the handling of multiple versions is similar, the client program (CP) and user processing procedure (UP) can be shared by specifying multiple versions in the user management data (UD). Is.

Next, the components (1) to (5) will be described more specifically. Server Program (SP) One SP is placed for each software library on the computer of each provider.

Provider Processing Procedure (VP) Group The following types of procedures are prepared. User qualification confirmation procedure Unqualified user processing procedure Reception reply processing procedure group (corresponding to each received message below) Inform message correspondence, WantNew message correspondence, Want
Renew message support, CheckUpdate message support,
BugReport message support, Comment message support,
InstallAck message correspondence, InstallTrouble message correspondence, and each received message will be described later.

Management Data for Provider (VD) The following management data is prepared. Provider identification information: provider name, network address,
Postal address, other user identification information: User database (for each user,
User identification information, personal identification number, contract status, provided software version, provided history, etc.) Software identification information: software name, location of software library, version type, module configuration information for each version, and development / update work Environmental information such as history information and fault contact history information: Application environment information for each version The target software / library software (Si) is composed of many modules (Mm), and the version number of the module is increased with each update (Mm. 1). These modules are configured into several types of sets in consideration of the variety of users, each of which is given a version name (Si.v) of software (Si) and provided to the user. For each version name, the version number will be increased (Si.v.1) as it is updated. The configuration of each version of the module is set as software configuration information of the management data (VD) for the provider. Client program (CP) It is installed corresponding to each software of each user. Basically the same. User processing procedure (UP) group The following procedure is prepared. Distribution / maintenance inquiry / request message creation procedure group For Inform message, WantNew message, WantRene
For w messages, CheckUpdate messages, BugReport
Message, Comment message, FinishUse message, Provider confirmation processing procedure Reception / reply processing procedure group ReplyInfo message, NewInstall message, Re
For new message, Update message, NoUpdate message, BugAck message, Answer message,
For notice message, warning message, brase message User management data (UD) Set the following information corresponding to each target software of each user. User identification information: user name, network address, personal identification number, etc. Provider identification information: provider name, network address, etc. Software identification information: software name, version
Type, version name, software configuration, etc. Environmental information: Environmental information specified by the provider, user's usage environment information Target software for user Each version (Si.v) of the target software is stored under one directory on the user computer. Write and manage each module (Mm.1) as a file. Communication network An ordinary UNIX network is used, and it complies with the TCP / IP protocol. Client program (C
It enables direct message transmission from P) to the server program (SP).

The present invention is characterized in that messages are directly transmitted and received between the client program CP on the user computer and the server program SP on the provider computer. This will be further described.

In the present invention, a client program (of a certain user) (C) that manages one target software
P) and the server program (SP) that manages the corresponding software library of the provider who provides the target software are supposed to be able to perform message communication via the network. Such a communication function is a basic function of the network.

On each computer, each process that performs a group of processes (the above CP and SP can also be such processes) should be given a unique name under the operating system (OS). You can
In the case of the present invention, each client program (CP) (for example, on the user computer) combines the user name, the client program (CP) of this system, and the target software name,
You can try to create a unique process name.

In addition, a network system (for example, in
The ternet system) generally has the function of recognizing the processes in each computer and processing in parallel the transmission from each process to the outside and the reception from each process to the outside. If the network address of another computer connected to the network is designated, a message can be delivered to that computer.

Therefore, by designating the network address of the partner computer and the partner process name (in the present invention, the combination of the user / provider name, the CP / SP and the target software name), an appropriate network communication protocol (for example, , TCP / IP protocol in internet system), operating system (OS)
And a function of the network system to deliver a message from one process (for example, a client program (CP)) on one computer to one process (for example, a server program SP) on another computer. You can In this way, one-to-one (peer-to-peer) communication between CP and SP is possible.

Of course, there is also a method of setting a parent process in charge of communication of a plurality of client programs (CP) on each computer. In this case, the parent process needs to handle the sending / receiving message processing in parallel and perform the distribution processing. In this case, the destination of the communication message is expressed by the network address of the partner computer and the parent process as the partner process, and the actual distribution process to the CP / SP process is the user / provider name in the message content. And the target software are used in this parent process.

However, when considered, such message processing (particularly parallel processing and distribution processing) in the parent process is similar to the basic processing performed in the communication network. Therefore, it does not make a difference whether the parent process performs such processing in a general-purpose network system. (Furthermore, it is the gist of the present invention to let the general-purpose operating system (OS) and the network system perform the processing, instead of explicitly performing the processing in the parent process.) As described above, when there is a process group on each computer,
It is a well-known technique that one-to-one communication can be performed between processes, or they can be treated as a group and communicated between process groups.

For this purpose, "one-to-one" and "group-to-group"
In the sense including "," the communication in the present invention is referred to as "communication between processes by a general-purpose network". (2) Functions of software distribution / maintenance system The functions realized as the software distribution / maintenance system are explained below. (2-1) Initial acquisition and installation of software In order to acquire software, the user has to perform a two-step process of inquiring about the summary information and requesting the acquisition of the software (so-called ordering). Is the way.

First, in the first step, the user specifies the network address of the desired software (Si) and its provider (Vk) and activates the outline inquiry (Inform) command of the client program (CP). The client program (CP) automatically attaches the user identification information and asks the software provider for an overview (Infor
m) Send the message over the network.

The server program (SP) of the provider receives the information, checks the user's qualification, and provides a summary reply (ReplyI) with information that is useful for obtaining and purchasing the software.
(nfo) message is returned to the user. As the summary information, a demo program may be returned in addition to the usual catalog-like information.

Next, as a second step, the user clarifies the payment conditions and the like with reference to the received outline information, and sends a software acquisition request (WantNew) message. This includes a client program (CP)
In, the acquisition request command (WantNew) may be input, and some information such as the version type of the desired software to be acquired may be interactively input.

The server program (SP) of the provider is
Check the user's qualification, and if it is qualified, provide new version software suitable for the user (NewI
nstall) Reply as a message. In this message, specifications of the provided software, installation information, the software body, various documents, and the like can be included, and a personal identification number for user confirmation can also be sent.

User's client program (C
P) receives this reply and stores the software according to the installation information in the reply message. Further, when it is determined that it is appropriate, the client program performs necessary translation and combination according to the installation information to make the software executable. (2-2) Inquiry and update of software Inquires of the software provider whether the software currently used by the user has any subsequent updates or improvements, and if updated, the new version will be automatically updated. It can be easily obtained as follows.

The user inputs the update inquiry command (CheckUpdate) by designating the software name for which update inquiry is desired. The client program (CP) is started, the version information currently used is extracted, and the update inquiry message is automatically sent to the provider. (The update inquiry can also be started automatically by the user's daemon program, etc.) When the provider's server program (SP) receives this, the user's qualification is checked before the software update information is received. To the user. For a qualified user, for example, the following reply process is performed.

(1) If the software has not been updated, a message indicating no update is returned. (2) If the software has been updated, the update instruction information and the body of the software module required for the update are returned.

(3) If the software has been updated or improved on a large scale, a message is sent back inviting the user to obtain a new version of the software. And so on. The method of these reply processes can be set by the provider in the provider process procedure (VP) and the provider management data (VD).

The client program (CP) receives this reply and performs the receiving process. For example, when updated software is returned, the software body and attached information are first stored in a disc, and the update instruction information and user management data (UD) being returned are referred to and the updated version Replace and, if necessary, translate and combine to make the new version executable. Whether the storing / updating process of this software has been normally performed is checked from the client program (CP) to the server program (S
There is also a function for automatically reporting to P). (2-3) Automatic reporting of failure information when software terminates abnormally If the target software terminates abnormally during execution on the user's computer, the client program starts immediately through the exception handling function of the operating system (OS). To be done. The client program detects the cause and status of the abnormality (for example, the series of higher-order instructions that call the instruction that caused the abnormality), retrieves the necessary information from the user management data (UD), and automatically adds it. And report the problem to the server program (SP) of the provider (Bug
Report) Send a message automatically.

The server program (SP) of the provider is
Management data (VD) for providers by analyzing and classifying trouble reports
A message stating that the bug report was recorded in the
Ack) to the user. In addition, the content of the failure report message is reported to the person in charge of development and maintenance of the provider. (3) Message type and configuration Communication between the client program (CP) and the server program (SP) sends and receives messages of the following configurations and protocols via a network. (3-1) Main message types and functions Message from user to provider is "upbound message"
And a message from the opposite provider to the user will be referred to as a “downstream message”. In the software distribution / maintenance system of the present invention, a user initiative is adopted as a way of thinking, and there is a message of inquiry / request from a user, and a reply message from a provider is given as a response to the message. There is.

It should be noted that it is not necessary to exclude that there is a message led by the provider for an important notice or the like.
These notifications can be supplemented by methods other than this system, such as electronic mail and regular mail, if necessary, and are not taken up in the embodiment.

FIG. 3 shows the correspondence between the types of upstream messages and the types of downstream messages in response to them. These message types are distinguished by specifying the command name in the command line in the message. (3-2) Set of processing commands A set of processing commands as shown in Fig. 4 was used. (3-3) Correspondence Relationship between Uplink / Downlink Messages In the system of the present invention, the provider basically sends a reply (downlink) message to the inquiry (uplink) message from the user, and the main commands are It corresponds almost to one to one. There are response messages for exception handling, confirmation messages from users, etc. The correspondence is shown in FIG. (3-4) Structure of upstream message (from user to provider) The following structure is used.

(Header part) Destination: provider name at provider's network address Originator: user name at user's network address Command line: SDM system name Command name Software name Reply target: reply downstream message identification information ( (Exceptional) (Attribute part) User information: (Information that clarifies the access qualification of the user) Provider information: (Confirmation information of the provider) Software information: (Information that indicates the version of the user's existing software) Environment Information: (Information on user's hardware / software environment) (Instruction part) (Distribution / maintenance inquiry / Detailed instruction of request (optional)) (May be used depending on the type of command) (3- 5) Outgoing message (provider to user) configuration Take the following configuration: (header) Destination: User name at user's network address Origination : Provider name at Provider's network address Command line: SDM system name Command name Software name Reply target: Upbound message identification information to reply (attribute section) User information: (User confirmation information) Provider information: (Provider Software information: (Version information of the software to be provided, etc.) Environmental information: (Information such as specifications related to the hardware / software environment used by the target software) (Instruction part) (Distribution / maintenance reply contents (Details and instructions to users) (Instructions for installing or updating software) (Depending on command type, optional) (Module part) (Main body of new / update module to be provided) (3-6) Description method An outline of the description method inside the above-mentioned upstream message and downstream message is described below. However, the description here is in a human-readable format (text format), and the coding method for actually transmitting it on the network depends on the network system, so it is not described here.

It is indispensable to specify the destination, sender, and command line in the header section (in the text format, use a colon as a delimiter, for example). Keyword: A pair of a specified value (or a list of values) is specified in each line. Write and line up.

Similarly, in the description of the attribute part, keyword: value pairs are arranged on each line. However, if the value designation becomes complicated, enclose it in parentheses and make the inside into a keyword: value pair. Can be arranged in each line. A symbol that explicitly creates a list of values (for example, parentheses and semicolons,
However, if it is clear, it can be replaced with a blank), a line break symbol
(Eg CR) and continuation line symbols (eg \) are defined and used in the same way as the description of a general programming language.
That is, keyword 1: value 1 keyword 2: (keyword 21: value 21 keyword 22: (value 221; value 222; value 223) keyword 23: value 23). As described above, the keywords in the uppermost layer of the attribute section are the user information, the provider information, the software information, and the environment information.

The description of the instruction part can be similarly described in the keyword: value format. For example, an instruction (command) for adding a module group or deleting a module group is described in this format. The keyword used in the instruction part is selected depending on the command of the message.

The description of the module part (in the text format) is also arranged in the format of module: (module body). One of the advantages of writing keyword: value pairs, as described above, is that the information can be written in the same format (or by converting the keywords) to the user (especially for the information in the attribute section above). This is because it can be stored in the management data (UD) for management and the management data (VD) for providers. If the system of keywords (its name and meaning) is clearly defined, it is easy to update, search and analyze data in this format. (3-7) Example of system of keywords for message description As described in the previous section, it is preferable to hierarchically configure keyword: value pairs in the internal description of the message. The keyword system for this can be selected as follows, for example.

(Header part) receiver sender command line in reply to (Attribute part) (User information) user: name organization address network address status id & password (provider information) vendor: name organization address network address status id & password ( Software information: software: name version type current version configuration form description (environment information) environment: hardware: machine memory software OS directory path (instruction part) instruction: payment wanted old version treatment delete add (module part) module (4) User computer Message sending process on top (4-1) Overall configuration of client program (CP) process The client program (CP) is placed on the user computer, and obtains / updates one target software for each user. Is managing. In response to the user's request for new acquisition, update inquiry, etc., the upstream message is edited and transmitted via the network, and the reply is received from the server program (SP), and processing such as installation is performed. The overall structure of this processing is shown in FIG. 6, and each step thereof will be described below.

Step S1: In response to a command input from the user, a command input from the user software (daemon program, etc.), or a command input upon activation of the target software, the client program (C
P) is activated.

Step S2: In response to the input command, the user processing procedure (UP) P1 for inquiry / request editing is called to interactively or automatically edit the inquiry / request message. Refer to the user management data (UD) in the user processing procedure (UP).
Search and compose a message. The message includes an overview inquiry, new acquisition request, new service provision request, update inquiry,
There is a problem report.

Step S3: The message is recorded, the message is transmitted to the corresponding server program (SP) of the provider via the network, and the reply is awaited. In addition, in order to secure communication safety, a part or the whole of the message may be encrypted and transmitted.

Step S4: A reply is received from the server program (SP) of the provider via the network. Step S5: Call the user processing procedure (UP) P2 for confirming the provider, and manage the user management data (UD).
Use the records in to confirm that the reply was from a legitimate provider. At this time, when a part or all of the received message is encrypted, the code is decrypted using an appropriate key to prove the legitimacy of the user himself and the legitimacy of the provider.

Step S6: In response to the command of the received message, the user process procedure (UP) P3 of each reply reception process is called. In the received message, outline information, new provision, additional provision, update, no update, caution (No
Tice), warning, acceptance of trouble report, reply to comment, etc. In this user processing procedure (UP), the received message is analyzed, the received content is stored, and if it is determined to be appropriate, the installation is performed according to the instruction of the returning provider, and the user management data is stored. (UD) is updated. These processes refer to the user management data (UD) and the target software, and update them.

Step S7: If automatic report of the processing result of the received message is required (new provision, additional provision, and update message), step S6.
The processing result of is monitored, if it is successful, an installation confirmation message, if any problem occurs,
An installation trouble message is sent back to the server program (SP) of the provider.

Step S8: The reception of the reply and the processing result thereof are recorded, the processing control is returned to the process which called the client program (CP), and the CP ends (sleep).

The processing of the client program (CP) described above basically complies with the first prior application and the second prior application, but there are differences in the following points in particular. The difference from the first prior application is that the client program (CP) calls the user processing procedure (UP) group (using the method of the second prior application) and uses the user management data (UD). This is the point that made it clear. On the other hand, the difference from the second prior application is that the client program (CP) manages only one target software of one user (similar to the first prior application), so that a plurality of users or This means that the classification processing and parallel processing required for managing multiple target software are not necessary, and the processing for command input and reply message reception is simplified.

(Note that parallel processing and communication message classification processing due to the existence of a plurality of client programs (CP) are performed by the operating system (OS).
As a function of a network or a network, it can be processed more generally, and may not be a process inside the software distribution / maintenance system of the present invention. Therefore, the above simplification is possible. (4-2) Outgoing process of new acquisition request message Among the inquiry messages sent by the user, those that the user himself intentionally performs the outgoing process include Inform (Summary inquiry), WantNew (New acquisition request), There are four types of messages, WantRenew (request for new service) and Comment (comment). The processing of the client program (CP) when transmitting these messages is performed by steps S1 to S3 in the processing of FIG.

Taking a new acquisition request (WantNew) as an example, the transmission process is as follows. S1: The user inputs the WantNew command (including the new software name) and the client program (C
P) is activated.

S2: Client program (CP)
For the user (a basic type that has been prepared in advance) calls a user processing procedure (UP) for a new acquisition request (for the user who has made a summary inquiry in advance and stored summary information from the provider) A new acquisition request message (WantNew message) is created by referring to the management data (UD).

The following information is set in the message. User identification information (user name, network address, personal identification number, etc.), provider information (provider name, provider network address, etc.), software information (software name, version type designation, etc.), environment information (used model, memory) Capacity, OS used, etc.) The client program (CP) prompts the user to input a part of these pieces of information (specification of desired version type, user's usage environment, etc.).

S3: The created message content is stored as log information of the user management data (UD) and the client program (CP), and the message is sent to the server program (SP) of the provider via the network. send. (4-3) Process for sending update inquiry message The CheckUpdate message for update inquiry is S in FIG.
It is transmitted by the processing of 1 to S3. The main points are as follows.

S1: Chec by specifying the target software name
When the kUpdate command is input, the client program (CP) is started. The CheckUpdate command may be entered directly by the user. Alternatively, the target software may be automatically input at the time of starting, or may be automatically input at a timing preset by a daemon program (for example, early morning every day, weekly, monthly, etc.).

S2: Client program (CP)
Calls the user processing procedure (UP) for update inquiry, refers to the user management data (UD), and automatically creates an update inquiry message (CheckUpdate message).

The following information is set in the message. User identification information (user name, network address, personal identification number, etc.), provider identification information (provider name, provider network address, etc.), software management information (software name, existing version name, existing module configuration, etc.) environment information ( Instruction model ((optional) specific desired version type, etc.) S3: Store the created message content as log information of the client program (CP), and use the server program of the provider. (SP) via network,
Send a message. (4-4) Automatic transmission process of fault report message The automatic transmission can be performed by the processes of S1 to S3 in FIG.

S1: If the target software terminates abnormally during its execution, the BugR
You can invoke the eport command, which launches the client program (CP).

S2: Client program (CP)
Calls a processing procedure (UP) for a user for failure reporting, and uses the data of the management data (UD) for the user and the instruction execution sequence data provided by the operating system (OS) and the like to report the failure reporting message (Bu
gReport message).

The message includes the following information. User identification information (user name, network address, personal identification number, etc.), provider identification information (provider name, provider network address, etc.), software management information (software name, existing version name, existing module configuration, etc.) environment information ( Details such as model used, amount of memory, OS used, etc.) Instruction information: Indicates the instruction that caused the abnormal end, the instruction sequence leading to the abnormal end, and the content of the abnormal end (from the OS, etc.)
Message etc. S3: The created message content is stored as log information of the client program (CP) and is delivered to the server program (SP) of the provider via the network.
Send a message.

In addition to the automatic fault report as described above, when the target software behaves abnormally or erroneously, the fault report message can be interactively edited and transmitted. (5) Reply message reception process on the user computer Client program (CP) on the user computer
The overall configuration of the processing of is as shown in FIG. When the client program (CP) sends various inquiry / request messages (see (4-2) to (4-4)), the provider server program (SP) processes the response ((6)). ), A reply message will be sent back. As shown in steps S4 to S8 in FIG. 6, the client program (CP) receives these reply messages and calls the corresponding user processing procedure (UP) to process the received messages. In the received message,
In addition to the information that the user expected, such as summary information, new installation of target software, additional service installation, update, and comment reply, there are exception handling messages such as cautions and warnings. (5-1) Installation Process of Newly Obtained Software The process for receiving and installing the reply of the new software is performed as follows according to steps S4 to S8 of FIG.

S4: (Send the WantNew message,
Client program (CP) that was in a standby state
Receives a NewInstall message from the provider over the network.

S5: Client program (CP)
It is confirmed from the log information of the log that it was in the standby state for new acquisition, and the user processing procedure (UP) for confirming the provider
Call P2 and confirm that it is a reply from a legitimate provider.

S6: Calling the user processing procedure (UP) for the new installation message, referring to the user management data (UD), decoding the received message, storing the information, installing processing when judged appropriate, The user management data (UD) is updated. Specifically, for example, it is as follows.

First, the entire received message is temporarily stored in the disc. Then, while confirming that various information (particularly, software version type information and environment information) in the attribute part of the received NewInstall message is appropriate, it is updated and accommodated in the user management data (UD). Next, when the instruction part of the message is deciphered and it is determined that the installation instruction from the provider is appropriate (for example, that no special exceptional instruction information is specified), the message module is The main body of the software (and the accompanying documentation,
(Including attached tools, etc.), and further install processing including processing such as translation / combination of execution preparations. If we determine that the automatic installation process is inappropriate or dangerous, we will install it manually.

S7: Client program (CP)
Immediately returns a confirmation message indicating the result of the reception process to the server program (SP). If the installation process is successful, or if the installation process is postponed, an InstallAck message is sent.
Send a rouble message.

S8: The received reply message and transmitted confirmation message are recorded and returned to the process that called the control, and the client program (CP) ends.

If a new acquisition request message is issued, but the reply is not a NewInstall message but a Notice message, the client program (C
P) is processed as described in (5-3). (5-2) Reception of updated software information and its installation process The process in this case is the same as the process in (5-1), and is performed as follows.

S4: The client program (which was in the waiting state by sending the CheckUpdate message) (C
P) is updated from the provider via the network (Upda
te) Receive the message.

S5: Client program (CP)
It is confirmed from the log information of the user that the update was in the standby state, and the user processing procedure (UP) P for confirming the provider is confirmed.
Call 2 to confirm that the reply is from a legitimate provider.

S6: The user processing procedure (UP) for the update message is called, and the user management data (U
While referring to D), the received message is decrypted, the information is stored, the installation process when it is determined to be appropriate, the user management data (UD) is updated, and the like. Specifically, for example, it is as follows.

First, the entire received message is temporarily stored in the disc. Then, while confirming that various information (particularly, software version type information and environment information) in the attribute part of the received Update message is appropriate, it is updated and accommodated in the user management data (UD).
Then, when the instruction part of the message is deciphered and it is determined that the update instruction from the provider is appropriate (for example, no special exceptional instruction information is specified), the message module is processed according to this instruction information. The update module in the section is read, the target software is updated, and further, installation processing including processing such as translation / combination of execution preparation is performed. If we determine that the automatic update and installation process is inappropriate or dangerous, we will separately update and install it.

S7: Client program (CP)
Immediately returns a confirmation message indicating the result of the reception process to the server program (SP). An InstallAck message is sent if the update / installation process has been normally performed, or if the update / installation process has been postponed, and an InstallTrouble message is sent if the update / installation process has a problem.

S8: The received reply message and transmitted confirmation message are recorded and returned to the process that called the control, and the client program (CP) ends.

Note that NoUpda is displayed for the update inquiry message.
If a te message is returned, step S
Nothing is done in 6 and S7, and only the reply information is recorded in S8. (5-3) Processing of Notice message The Notice message from the provider is used for various inquiries (new request, new service acquisition request, update inquiry, comment, error report, etc.) of the user for the purpose of "attention" and "notification". ) Is returned as an exception handling. The client program (CP) processes as follows.

S4: Client program (CP)
Receives a Notice message from the provider via the network. S5: It is confirmed from the log information of the client program (CP) that it was in the standby state and the outgoing message before the standby, and the user processing procedure (U) for confirming the provider.
P) Call P2 to confirm that the reply is from a valid provider.

S6: The user message processing procedure (UP) for the Notice message is called, and the received message is stored and displayed while referring to the user management data (UD). Specifically, for example, it is as follows.

First, the entire received message is temporarily stored in the disc. Then, the information in the instruction part of the received Notice message (along with the information in the attribute part) is displayed to the user, and copied into the user's mailbox. Also, a cancel operation for the reply waiting state is performed according to the type of outgoing message (for example, waiting for the NewInstall message after canceling the WantNew message is canceled).

The confirmation message in S7 is unnecessary and S8
After recording the reception of the Notice message in the log information of the client program (CP), the control is returned to the calling process, and the client program (CP) ends.

Note that the user separately performs the actual decoding and processing of the contents of the Notice message. (6) Processing on the computer of the provider (6-1) Overall configuration of the processing of the server program (SP) The server program (SP) is placed on the computer of the provider, and each server program It manages the distribution and maintenance of one piece of software to be provided. Distribution / maintenance inquiries / request messages such as new acquisition requests and update inquiries are sent from client programs (CP) of many users via the network. Server program (S
P) receives them, creates a reply message for services such as new software provision and update information according to the protocol of the software distribution / maintenance system, and returns it to the requested client program (CP).

The overall structure of the process of processing a message by the server program (SP) of the provider is shown in FIG. Each step will be described below. Step S11: a server placed on the computer of the provider
The program (SP) is always started, and client programs (C) of many users are transmitted via the network.
It waits to receive various inquiry / request messages sent from P).

Step S12: Through the network
Receive a message from a client program (CP). [Normally, for parallel execution, a child process that processes this message is generated and the following S13-
Cause the client program (C
The parent process of P) immediately returns to the waiting state of S11. The following description does not distinguish between CP's parent and child processes for simplicity. Step S13: Extract the user name and user information in the message and call the provider processing procedure (VP) P11 for user qualification confirmation. This user qualification confirmation V
At P, the user information is examined using the provider management data (VD) to determine if this user is entitled to access with this command.

Step S14: In the case of an unqualified user, the unqualified user processing procedure (VP) P12 is called to compose an appropriate reply message such as refusal, warning, or contact for qualification acquisition method. Then, it progresses to S16.

Step S15: In the case of a qualified user, the provider processing procedure (VP) P13 for reception / reply processing corresponding to the command of the received message is called to create a reply message to the user. The reply message is created according to the protocol of the software distribution / maintenance system.

Within the provider processing procedure (VP), the received message is analyzed and the provider management data (V
D) and information is extracted from the provided software library to create a reply message. Further, the contents of provision and the like are recorded in the user information in the provider management data (VD). For reply message types, provide summary information,
In addition to new software provision, new service provision, update information reply, non-update contact, comment reply, etc., there are Notice message and Warning message as exception processing.

Step S16: The created reply message is sent back to the client program (CP) of the inquiry source user via the network. Step S17: Store the reception and reply processing in the log information of the server program (SP), user history information, and the like. After that, the server program (SP) returns to the standby state of S11. [In the case of parallel execution, the child process of the server program (SP) terminates and disappears here, and the termination is reported to the parent process of the server program (SP). (6-2) Example of Reply Process for New Acquisition Request (WantNew) The processes of steps S12 to S17 of FIG. 7 are performed as follows.

S12: Receive a message from the user's client program (CP). S13: A user who calls the user qualification confirmation procedure, confirms / inspects the user information of the message using the record of the management data (VD) for the provider, and (for example) has undergone the formal (purchase / acquire) procedure. Only when this Wa
Judged as a qualified person who allows access with the ntNew command. (Note: The method of determining this user qualification varies depending on the distribution policy of software such as commercial products, academic prototypes, and freeware.
See various operational examples. ) S14: For an unqualified person, call the unqualified person processing procedure, create a method of a formal procedure for new acquisition (for example) in the form of a Notice message, and proceed to S16.

S15: For a qualified person, the reception / reply processing procedure (VP) corresponding to the WantNew command is called, and the user identification information, environment information,
Or (if any), the information in the instruction part is analyzed to determine the version type (Si.v) to be provided, and the latest version (Si.v) in that version type is referred by referring to the management data (VD) for the provider. .
Clarify the module structure of vl). Then reply
Create a NewInstall message. Specifically, set provider identification information, software identification information (especially version type, version name, etc.), and environment information (especially restrictions / specifications of the hardware / software environment in use) in the attribute section of the message. Set the module installation instruction information in the instruction section, and attach the software body of the module group to be newly sent to the module section. Further, the user database of the management data (VD) for the provider is updated.

S16: The above NewInstall message (or a Notice message to an unqualified person) is returned to the client program (CP) of the requesting user through the network.

S17: The request by the user's WantNew message and the reply by the NewInstall (or Notice) message are recorded in the log information of the server program (SP). (6-3) Example of Reply Process for Update Inquiry (CheckUpdate) The processes of steps S12 to S17 of FIG. 7 are performed as follows.

S12: Receive a message from the user's client program (CP). S13: Call the user qualification confirmation procedure, confirm and inspect the user information of the message using the record of the management data (VD) for the provider, and (for example) the user is the party to whom the software was legally provided, and provided Only if the conditions (such as period) are still valid, it is judged as qualified person.

S14: In the unqualified person processing procedure, for example, the following measures are taken. (a) If the requester has obtained the formal procedure and the qualification has expired: The procedure for renewing the qualification is returned as a Notice message.

(B) When the client illegally acquires the software, not the legitimate one: A warning message is returned to warn. S15: Call the reception / reply processing procedure (VP) for the CheckUpdate command and determine the version type (Si.v ') to be provided using the information in the message attribute part (however, the version type in the specified part of the message , Is followed), the latest version (Si.v'.l ') in that version type is determined.

(A) If this is the same as the current version (Si.vl) of the user, a reply message indicating that updating is not necessary (NoUpdate) is created. (b) If the same version type has been updated, create an Update message for reply to update the current version (Si.vl) of the user to the latest version (Si.v.l '). That is, the module deletion / addition instruction information is set in the message instruction section, and the main body of the module (Mm.l ') group required for addition is set in the module section. In addition, management data (V
The user database in D) is updated and the sent version information is recorded.

(C) In the case of shifting to another version type by designating a user's message, an Update message for providing a new version type is created. On this occasion,
The new version information (especially software identification information and environment information) is set in the attribute section, the module deletion / addition instruction information is set in the instruction section, and the main body of the additional module group is set in the module section. The sent version information is recorded in the user database in the provider management data (VD).

(D) A version type (Si.v.) that includes a new service and is different from the existing version type (Si.v.) of the user.
If the provider determines that it is desirable to switch to v '), create a Notice message to inform them of the new version.

S16: The created reply message is sent back to the client program (CP) of the requesting user via the network. S17: The message reception and the record of the reply message are recorded in the log information of the server program (SP). (6-4) Example of Acceptance Process of Failure Report Message The processes S12 to S17 of FIG. 7 are performed. The characteristic parts of this are as follows.

S15: Failure report (BugReport command)
The receiving / reply processing procedure (VP) for analyzing and classifying the content of the problem report and providing the management data (VD)
It will be stored in the internal problem report database and a BugAck message stating that the problem report has been received will be created. It also forwards / displays a summary of problem report messages to the development / maintenance personnel of the provider. (7) Example of Bootstrap on User Side of Software Distribution / Maintenance System In the description so far of the present invention, when the user tries to obtain the target software, the software distribution / maintenance system of the present invention ( It was described as if it had the software for the user of the SDM system (that is, the client program (CP) and the processing procedure (UP) group for the user). Standard CPs and UPs may be obtained in advance by the conventional software distribution / maintenance method. However, in order to make the distribution / maintenance system well suited to the target software, it is desired that the provider of the target software also provides the user side software of the software distribution / maintenance system.

Therefore, according to the present invention, if the following is done, the user can obtain new target software and the corresponding software distribution / maintenance system at the same time with the minimum necessary preparation.

Step 1: The user sets up the user side SDM system (CP and UP) as necessary for transmitting the outline inquiry (Inform) message in the software distribution and maintenance system (SDM) and receiving and processing it. prepare.

For example, a standard version of this part has been released.
If provided, each user can easily obtain it by the conventional method (for example, the method by ftp). Step 2: The user uses the above SDM system to inquire the outline of any target software (Inform message)
Can be sent.

When returning the ReplyInfo message, the provider (with the outline information of the target software):
Provides the following: -The skeleton part of the client program (CP) suitable for the target software (that is, a part sufficient to request a new acquisition of the target software) -User processing procedure (U for requesting a new acquisition)
P) ・ User management data (U that is convenient for setting new acquisition requests)
D) Step 3: The user can use the client program (CP) provided in Step 2 to send a message of request for new acquisition (WantNew) of the target software to the provider.

In response to this, the provider makes a new provision (NewI
nstall) When returning a message, the following items of the software distribution / maintenance system are provided along with the provision of new target software.

• Overall client program (CP) suitable for the target software • Overall user processing procedure (UP) group • Installation instruction information for these CP and UP groups After that, software distribution that the user can configure as described above The maintenance system (SDM) can be used to smoothly obtain and update the target software. Further, using the same idea as above, the provider of the target software can also maintain the provided software distribution / maintenance system itself.

According to this embodiment, without burdening the user,
The software distribution / maintenance system itself suitable for each target software can be configured, and software distribution / maintenance can be made more reliable and easy. (8) Example of operation of software distribution / maintenance system In this example, all of the above-described examples (1) to (7) are applied, and on the other hand, the commercial policy / writing of the provider's software is applied. It shows how the provider should operate this software distribution / maintenance system, reflecting the differences in rights policy. Providers of these operational policies
It can be set in the provider processing procedure (VP) group and the provider management data (VD). Especially,
Policy regarding user qualification is important,
It can be set by the user qualification confirmation procedure and the unqualified person processing procedure. (8-1) Example of application software for software products Inquiry of outline → Teach anyone the outline information and purchase procedure.

Request for new acquisition → The purchase procedure is completed,
Send new software only to users with the same PIN. Request for new service → Complete new service purchase procedure,
Only for users with matching PIN.

Update inquiry → For regular users only.
Warning message to unauthorized users (8-2) Operation example of operating system for large-scale computer Overview inquiry → Send summary information to anyone and inform purchase contract procedure.

All other inquiries / requests → Only contract users with matching PIN numbers. (8-3) Example of distribution of software as shareware Inquiry of outline → Tell anyone about outline information and how to obtain it.

Request for new acquisition → Send to anyone to request donation after trial. New service acquisition request, update inquiry → For registered users,
Send to anyone. (8-4) Example of distribution of academic prototype software Inquiry of outline → Tell anyone about outline information and how to obtain it.

Request for new acquisition → Send to anyone to inform them of copyright handling, prohibition of commercial use, request for trial report, etc. New service acquisition request, update inquiry → For registered users,
Send to anyone. (8-5) Example of internal distribution of in-house developed software Inquiries about the outline → Teach only the members of the organization about the outline information and how to obtain it.

Request for new acquisition → Only the organization members will be sent to anyone to inform them of confidentiality. New service acquisition request, update inquiry → For registered users,
Send to anyone. (9) Message usage example (1) (9-1) Update inquiry message example As the simplest example, the provider provides software S1 having only a single version type. Suppose that the library has only the latest version of the module. When the user makes an update inquiry, it is sufficient to inform the provider of the module configuration of the user's existing version. When the user inputs the CheckUpdate command, the client program (CP) automatically creates the following message and the server program (SP)
Sent to.

Receiver: Vendor-S1@Vendor.co.jp sendor: User1@chem.su-tokyo.ac.jp command line: SDM CheckUpdate S1 software: (current version: VTa.3 configuration: M1.2, M2. 2, M3.3, M4.1, M5.1) Note that various information other than the above may be coded in the attribute part, but since these are optional, they are omitted in the above example. (9-2) Example of reply message to update inquiry Server program (SP) responds to the above update inquiry
However, an example of the Update message that sent the updated version is shown below.

Receiver: User1@chem.su-tokyo.ac.jp sendor: Vendor-S1@Vendor.co.jp command line: SDM Update S1 in reply to: 27 Oct 93, 10:24:15 JST, CheckUpdate software : (description: "A bug fixed, two new functions added." version: VTa.4 version date: 25 Oct 93) instruction: (old version treatment: delete delete: M1.2, M3.3, M5.1 add: M1.3, M5.2, M6.1) module: (Main body of module M1.3 Main body of module M5.2 Main body of module M6.1) (10) Message usage example (2) As a more complicated example , Shows the case of commercial software SM provided to three different models. In addition to A, B, and C for each model, there are a total of 6 types of new versions AX, BX, and CX that are being experimentally provided to beta site users. The software library of the provider has history information of all these versions, and if the version name is known, its module configuration can be reproduced. (10-1) Example of summary inquiry (Inform) message An example of an Inform message that a user is interested in this software and first made a summary inquiry is as follows.

Receiver: VendorM@VendorM.co.jp sendor: MN@Mecom.co.jp command line: SDM Inform SM The user receives a ReplyInfo message from the provider, receives an overview of the software, and the required hardware / Knowing information such as software environment, version type, and payment procedure, the client program (CP) stores the information in the user management data (UD). (10-2) Example of a new acquisition request (WantNew) message The above user read the obtained outline information and transmitted a new acquisition request message as follows.

Receiver: VendorM@VendorM.co.jp sendor: MN@Mecom.co.jp command line: SDM WantNew SM user: (name: Munetaka Nakata organization: Mecom Software Associates address: 2-1-15 Hongo, Bunkyo- ku, Tokyo 113, Japan) environment: (hardware: (machine: B) software: (OS: B-OS 4.1.3)) instruction: (payment: Schedule 1 %% Paying obligation in 2 weeks %%) (10- 3) Example of new provision (NewInstall) message In response to the above request, the provider's server program (S
P) returned the following NewInstall message to the user in order to provide the latest version of software of version type B.

Receiver: MN@Mecom.co.jp sendor: VendorM@VendorM.co.jp command line: SDM NewInstall SM in reply to: 03 Apr 95, 14:03:37 JST, WantNew vendor: (name: VendorM orgnization : SM Division, VendorM Corporation address: 1015 Kamikodanaka, Nakahara-ku, Kawasaki 211, Japan network address: VendorM@VendorM.co.jp) user: (password: DI9 # SP * 3) software: (description: Software SM for platform B version type: B current version: B.4 form: object code) environment: (hardware: (machine: Machine B memory: 4 MB) software: (OS: B-OS 4.1)) instruction: (payment: Schedule 1% % Paying obligation in 2 weeks %% add: M2.2, M5.2, M6.1) module: (main body of module M2.2 main body of module M5.2 main body of module M6.1) In response to this reply message , The client program (CP) installed the software SM on the user computer. (10-4) Example of additional acquisition (WantRenew) message of other version type The above user then decided to make a beta site contract and additionally acquired the experimental BX version. I sent the following WantRenew message.

Receiver: VendorM@VendorM.co.jp sender: MN@Mecom.co.jp command line: SDM WantRenew SM user: (password: DI9 # SP * 3) software: (current version: B.4 form: object code) environment: (hardware: (machine: Machine B memory: 80 MB) software: (OS: B-OS 4.1.3)) instruction: (old version treatment: hold wanted: (version type: BX form: source code) payment: contract done) In this example, in addition to the normal description of the attribute part, the description using the instruction part is required. The instruction section clearly states that the current version (object code of B version) of the user can be used as it is and that the additionally acquired content is the source code of BX version. (10-5) Example of additional provided Renew message In response to the above additional provided request, the server program (SP) of the provider confirms the user's qualification, and then sends a beta message by the following Renew message. We provided the experimental version BX for the site.

Receiver: MN@Mecom.co.jp sender: VendorM@VendorM.co.jp command line: SDM Renew SM in reply to: 24 Apr 95, 11:05:54 JST, WantRenew software: (description: Beta- site version BX version type: BX version: BX.4 version date: 21 Apr 95 form: source code) environment: (hardware: (machine: Machine B memory: 20 MB) software: (OS: B-OS 5.1)) instruction : (old version treatment: HOLD add: M2.3, M5.2, M6.2, M7.1) module: (Main body of module M2.3 Main body of module M5.2 Main body of module M6.2 Main body module M7.1 In response to this reply message, the user's client program (CP) stores the newly provided BX version in a directory different from the existing B version and uses the two versions in parallel. I made it possible.

[0192]

As described above, the software distribution / maintenance system of the present invention solves the following problems initially set.

Consider the form of software provision (or software distribution) on a global scale using computers and software, and build a uniform technical framework suitable for it. In other words, it is a system that utilizes a network and can be used by a large number and a variety of software users with a large number and a variety of software providers participating, targeting a large number of various types of software on a global scale. The software has a function that allows users to quickly and properly obtain and use software created and updated by users, and at the same time, use a unified protocol for messages for software distribution and / or maintenance. Thus, the constituent software of the above system used by each user and each provider can be limited to a single target software, so that the above system can be easily constructed.

The software distribution / maintenance system of the present invention is a unified technical framework that can be used by a very wide range of software / providers / users as described above. By utilizing the communication network between computers, It will be understood from the above description that the software provider makes the software created / updated available to the user promptly and appropriately at any time.

In particular, according to the present invention, as shown in the latter half of the above-mentioned problems, each of the constituent programs is handled by handling a single target software in which each program constituting the system is set and using a unified protocol. Can be simplified and easily created (because it is not necessary to handle various and many target software at the same time), and can be more adapted to the set target software.
It is an important effect of the present invention, which is an improvement of the first and second prior applications, that such simplification is made possible and it is possible to adapt to further variety.

Especially, in the future, if international standardization of the above-mentioned message protocol is carried out, it is expected that the distribution of software will bring about a revolutionary change according to the present invention.

[Brief description of drawings]

FIG. 1 is a block diagram showing a principle configuration of the present invention.

FIG. 2 is a block diagram showing a configuration of an embodiment of a software distribution / maintenance system utilizing a network of the present invention.

FIG. 3 is a diagram showing an up message and a down read message.

FIG. 4 is a diagram showing an example of a processing command.

FIG. 5 is a diagram showing a correspondence relationship between messages.

FIG. 6 is an overall processing flowchart of a client program CP.

FIG. 7 is an overall processing flowchart of a server program SP.

FIG. 8 is a block diagram showing a system configuration in a first prior application.

FIG. 9 is a block diagram showing a system configuration in a second prior application.

[Explanation of symbols]

 1 to 3 user computer 4,5 provider computer 6 network 11 user computer 12 network 13 provider computer 14 user / provider computer

Claims (20)

[Claims] 1. A large number of users (U1, U1) who use various kinds of target software to be distributed, managed, and maintained.
U2, ...) and a large number of software providers (V1, V2, ...) Providing the above target software distribute the above target software through a computer network.
In a software distribution / maintenance system using a network for performing maintenance, (a) one or more users (U1, U) placed on each user computer (1-3)
Target software group (S1,
S2, ...), one or a plurality of first processing means (CP) for managing the target software group for each target software and for each user, and (b) a computer (4) of each software provider. , 5), and the software libraries for the provider (SL (S1), SL (S2),
...), and for each software library of the software library group, one or a plurality of second processing means (SP) for performing a service related to the software library, and (c) a unified message protocol. A network connecting the first processing means (CP) and the second processing means (SP) to each other. (D) Each of the first processing means (CP) includes a user (U1, U2, ...) or user-specified program instructions, 1
For one piece of target software, a message requesting distribution and / or maintenance of the target software is transmitted to the second processing means (SP) corresponding to the target software via the network, and the second processing means (SP) is sent. Has a function of receiving a reply message from the user and performing processing for distribution and / or maintenance of the target software according to the reply content and the user (U1, U2, ...) Setting. When the second processing means (SP) receives the message from the arbitrary first processing means (CP), the contents of the received message and the provider (V1, V2, ...) Of the target software specified in the message.
According to the setting of, the software library (SL1, SL2, ...) Managed by the provider (V1, V2, ...) Is referred to, a reply message to the message of the distribution and / or maintenance request of the target software is created, and the network is created. A software distribution / maintenance system utilizing a network, which has a function of transmitting a reply message to a first processing means (CP) which is a source of the corresponding message via the. 2. In the software distribution / maintenance system, each of one or more computers uses a target software of one or more of the target software group (S1, S2, ...) And a target. And one or more of the first processing means (CP) and one or more of the first processing means (CP), which are used by a provider who provides one or more of the software. The software distribution / maintenance system utilizing a network according to claim 1, further comprising one or a plurality of the second processing means (SP). 3. A first processing means (CP) on the user computer (1 to 3) and a second processing means (SP) on the provider computer (4,5) via the network. Messages sent and received by the system are composed of a message header part, an attribute part as fixed form data, a request specific to each message, an instruction part as instruction data, and a module part as software body. A software distribution / maintenance system utilizing the network according to claim 1. 4. The attribute part forming the message is formed as hierarchical structure data of a pair of a keyword and a value,
Reference / update of user management data (UD) set for each user and for each target software and provider management data (VD) set for each provider and for each target software library A software distribution / maintenance system utilizing a network according to claim 3, which is facilitated. 5. A large number of users (U1, U1) who use various kinds of target software to be distributed, managed, and maintained.
U2, ...) and a large number of software providers (V1, V2, ...) Providing the above target software distribute the above target software through a computer network.
In a user computer (1 to 3) in a software distribution / maintenance system utilizing a network for performing maintenance, a target software group (S1, S2) for use by one or more users (U1, U2, ...) , ...) and one or a plurality of first processing means (CP) for managing the target software group for each target software and for each user.
A user management data (UD) set for each user and for each target software, and a processing procedure for the first processing means (CP) for distributing and maintaining the target software. A user processing procedure (UP) set for each target software and each target software, and the first processing means (CP), when the target software is distributed and / or maintained, has the user processing procedure (UP). ) Is called, and the management data (UD) for the user
Referring to, a message for requesting distribution / maintenance of the target software is transmitted to the provider side of the target software via the network based on each protocol unified in the system, and the provider for the transmission message is transmitted. A user computer in a software distribution / maintenance system utilizing a network characterized by performing processing for distribution / maintenance of target software according to the content of a reply message from the user. 6. The user management data (UD) includes user identification information corresponding to each user, provider identification information corresponding to a provider of each target software, software identification information corresponding to each target software, and A user computer in a software distribution / maintenance system utilizing a network according to claim 5, characterized in that it includes environmental information. 7. The user processing procedure (UP)
Distribution to the provider of the target software
Distribution / maintenance request message editing procedure group for editing maintenance request message, provider confirmation procedure for confirming target software provider, and reception processing procedure group for processing reply message from target software provider side A user computer in a software distribution / maintenance system utilizing a network according to claim 5, comprising: 8. In the software distribution / maintenance system, the user management data (UD) and the user processing procedure (U) are provided so that each user can simultaneously use a plurality of versions of the same target software.
P) and the first processing means (CP),
The user computer in a software distribution / maintenance system utilizing a network according to claim 5, wherein the user computer is provided corresponding to each of the plurality of versions. 9. In the software distribution / maintenance system, a plurality of versions of the same target software are designated in the user management data (UD) so that each user can simultaneously use the plurality of versions. 6. The network-based software distribution according to claim 5, further comprising: data to be used, wherein the user processing procedure (UP) and the first processing means (CP) are shared by the plurality of versions. -User computer in the maintenance system. 10. A large number of users (U) who use various kinds of target software to be distributed, managed, and maintained.
, U2, ...) and a large number of software providers (V1, V2, ...) Providing the above target software,
Provider computer (4, 5) in a software distribution / maintenance system that utilizes a network to distribute and maintain the above target software via a computer network
In the software library group (SL (S
1), SL (S2), ...), and for each software library of the software library group, one or a plurality of second processing means (SP) for servicing the software library, and Procedure for performing processing corresponding to a provider management data (VD) set for each provider and for each target software library, and the second processing means (SP) corresponding to a message from the user side regarding the target software. And a processing procedure for a provider (VP) set for each provider and for each target software library, and the second processing means (SP) supports a large number of arbitrary users. Then, upon receiving the software distribution / maintenance request message from the user side, a reply message for software distribution / maintenance is created. A provider computer in a software distribution / maintenance system utilizing a network, wherein a reply message is returned to a user side via the network based on a protocol unified in the system. 11. The provider management data (VD) is,
The user database as the user identification information of the target software, the provider identification information corresponding to the provider of the target software library, the software information corresponding to the target software library, and the environment information are included. Provider computer in software distribution and maintenance system utilizing network. 12. The provider processing procedure (VP)
11. The method includes a user qualification confirmation procedure for target software, an unqualified user processing procedure, and a reception / reply processing procedure for processing a message received from the user side and for creating a reply message. Provider computer in software distribution / maintenance system that utilizes the Internet network. 13. The target software library comprises a plurality of version types of target software, and one second processing means (SP) corresponding to the target software library corresponds to the plurality of version types. 11. Software distribution utilizing a network according to claim 10, wherein a service related to the target software library is provided by using one provider management data (VD) and one provider processing procedure (VP). Provider computer in maintenance system. 14. A large number of users (U) who use various kinds of target software to be distributed, managed, and maintained.
, U2, ...) and a large number of software providers (V1, V2, ...) Providing the above target software,
In a software distribution / maintenance system utilizing a network for distributing / maintaining the above target software via a computer network, the software is placed on each user computer (1-3) and one or more users (U1, U2) , ...) to be used by the target software group (S1, S2, ...) And one for managing the target software group for each target software and for each user,
Or it is placed on a plurality of first processing means (CP) and computers (4,5) of each software provider,
Software library group (SL (S
1), SL (S2), ...) and one or a plurality of second processing means (SP) for servicing the software library for each software library of the software library group. The first based on the established message protocol.
By using a network connecting the processing means (CP) and the second processing means (SP) of (a), each user (U1, U2,
...) is a user (U1, on the user computer (1 to 3))
U2, ...), or by activating a command from a program set by the user, the first processing means (CP) is activated, and (b) one target software is distributed and / or distributed. A maintenance request message is transmitted to the second processing means (SP) corresponding to the target software via the network, and (c) the second processing is performed on the provider computer (4, 5) of the target software. The means (SP) is the first
Received a message from the processing means (CP) of
For the target software specified in the message, the software library (SL1, SL2, ...) Managed by the provider (V1, V2, ...) Is managed according to the content of the received message and the setting of the provider (V1, V2, ...). See,
A reply message to the message of distribution and / or maintenance request of the target software is created, and the reply message is sent to the first processing means (CP) that is the sender of the message via the network. The first processing means (CP) receives the reply message from the second processing means (SP) on the computer (1 to 3) of the user (U1, U2, ...) As the sender of the message. , A software distribution / maintenance method utilizing a network, characterized by performing processing for distribution and / or maintenance of the target software according to the contents of the reply and the settings of the users (U1, U2, ...). 15. The first on the user computer (1-3)
Processing means (CP) of (a) user computer (1-3)
It is started by the user's command input on the above, or by the command start from the program of the user setting,
(B) A processing procedure for distributing and maintaining the target software, which is transmitted to the provider side of the target software within the user processing procedure (UP) set for each user and for each target software. Call the distribution / maintenance request message editing procedure for editing the distribution / maintenance request message, and (c) refer to the user management data (UD) set for each user and for each target software, and standardize within the system. The distribution / maintenance request message is edited based on the established protocol, and (d) second processing means (SP) corresponding to the target software library on the provider computer (4,5) corresponding to the target software. 15. The software utilizing the network according to claim 14, wherein the distribution / maintenance request message is sent to E A distribution and maintenance procedures. 16. The first on the user computer (1-3)
The processing means (CP) of (a) corresponds to the target software library on the computer (4,5) of the provider of the target software in response to the distribution / maintenance request message of the target software sent from the own computer. Receiving the reply message returned from the second processing means (SP), (b) confirming that the reply message is a reply from a legitimate provider, and (c) distributing the target software.
It is a processing procedure for performing maintenance, and calls a reception processing procedure for processing the reply message in a user processing procedure (UP) set for each user and for each target software. User management data (U
While referring to and updating D), the distribution / maintenance processing of the target software is performed according to the content of the reply message, and the execution of the target software is prepared according to the judgment of the first processing means (CP) itself. Claim 14
Software distribution / maintenance method utilizing the described network. 17. The first on the user computer (1-3)
Said processing means (CP) responds to the distribution / maintenance request message of the target software sent from its own computer, on the computer (4,5) of the provider of the target software, corresponding to the target software library. After receiving the reply message sent back from the second processing means (SP) and performing the distribution / maintenance processing of the target software according to the reply message, it is determined whether or not the distribution / maintenance processing result is satisfactory. Two
15. The software distribution / maintenance method utilizing a network according to claim 14, wherein the processing means (SP) is automatically returned. 18. The second on the provider computer (4,5)
The processing means (SP) of (i) the user computer (1 to
3) Above, the distribution / maintenance request message regarding the target software is received from the first processing means (CP) corresponding to the target software, and (b) is set for each provider and for each target software library. In the provider management data (VD), the user identification information of the target software is referenced to confirm that the distribution / maintenance request message is a message from a valid user, and (c) the second The processing means (SP) is a procedure for performing processing corresponding to a message from the user side, and for each of the providers,
In addition, within the provider processing procedure (VP) selected for each target software / library, the reception / reply processing procedure for processing the message received from the user side and reply message creation processing is called, and (d) the target software・ Received distribution while referring to the library and referring / updating the management data (VD) for the provider
15. The reply message for distribution / maintenance of the target software is created corresponding to the maintenance request message, and (e) the reply message is returned to the first processing means (CP). Software distribution / maintenance method that utilizes the Internet network. 19. The first on the user computer (1-3)
Second on the processing means (CP) and provider computer (4, 5) of
The message transmitted / received to / from the processing means (SP) via the network includes a header part of the message, an attribute part as fixed data, and an instruction part as request / instruction data peculiar to each message. 15. The software distribution / maintenance method utilizing a network according to claim 14, wherein the software distribution / maintenance method comprises a module unit as a software body. 20. A large number of users (U) who use various kinds of target software to be distributed, managed, and maintained.
, U2, ...) and a large number of software providers (V1, V2, ...) Providing the above target software,
In a method of obtaining new software in a software distribution / maintenance system utilizing a network for distributing / maintaining the above target software via a computer network, (a) the user is a user computer (1
~ 3) The provider computer (4, 4) equipped with the software library of the target software newly requested to be obtained from
5) A message for requesting an outline inquiry of the target software to a second processing means (SP) that provides a service corresponding to the above software library is networked based on a protocol unified in the system. (B) the second processing means (SP) sends the target software to each user on the user computer (1 to 3) as a part of the reply message to the summary inquiry.
And the first processing means (CP) for managing each software
And a processing procedure for distributing / maintaining the target software, which is set for each user and for each software, of the user processing procedure (UP)
A user processing procedure (UP) for requesting new software acquisition is provided to the user computer (1 to 3) side via the network, and (c) user computer (1 to 3).
Using the skeleton of the first processing means (CP) and a user processing procedure (UP) for requesting new acquisition of software, a message for requesting new acquisition of the target software is sent to the second processing means ( SP) via the network, and (d) the second processing means (SP).
However, together with the target new software, the entire first processing means (CP) and various user processing procedures (U).
P) and the user computer (1 to
3) side, and after (e), user computer (1-3)
On the side, a new software distribution / maintenance system utilizing a network characterized in that the target software is distributed / maintained using the first processing means (CP) and the user processing procedure (UP). How to get the software.