JP2000047856A - Software resource distribution system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enable a user to freely specify distribution systems for every distributed matter by providing a host system with a means which stores distribution control information corresponding to software resources and a means which distributes the software resources according to the distribution control information. SOLUTION: The host system 201 distributes a distribution management table wherein distributed matter (program, system, etc.), needed for distribution- destination terminals and distribution systems by the distributed matter are defined to a host system 202 and a terminal system 102. The host system 202 stores received programs and systems in a data base 411 and stores the received distribution management table in a data base 412. Similarly, the terminal system 102 stores pieces of information in the data bases 412 and 422. Then the host system 202 and terminal system 102 distribute the programs, systems, and distribution management table to a terminal system 103 according to the distribution management table.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to a software resource distribution management system for distributing various software resources distributed from a host and a terminal according to distribution conditions.

[0002]

2. Description of the Related Art Conventionally, when software is downloaded from a host computer system or a terminal system to a terminal system, for example, as described in Japanese Patent Application Laid-Open No. 1-152536, an identifier of a target terminal system in which the software is to be incorporated is provided in a providing medium. When downloading a software resource, the download control function of the host computer system and the terminal system checks the identifier of the terminal system to be installed, and executes the download only when the identifier matches. As a result, the provided software is provided only to the terminal system based on the software use contract.

Japanese Patent Laid-Open Publication No. 1-245346 discloses a method of distributing a program while checking the version number of the program.

As described above, there are various distribution methods such as a distribution management method according to the contents of a contract and a method of managing distribution using information unrelated to a contract such as a version number. In a system that performs such distribution, distribution conditions are uniformly determined for each system. For example, as shown in FIG.
When distributing the program or map 3 from the host 2 to the terminal 1, if the distribution systems of the host and the terminal 2 to distribute are the A, B, and C systems, respectively, each system executes software distribution only by this distribution system. are doing.

[0005]

According to the above-mentioned prior art, when software such as a program is distributed from a host to a terminal, the distribution conditions are uniformly determined, and a user selects various distribution methods or various distribution methods. There is a problem that a combination of methods cannot be specified. For example, as shown in FIG. 2, a system that supports the A method can only distribute by the A method, and the user can freely select the A, B, and C methods, There is a problem that a distribution request cannot be made.

[0006] In addition, since distribution management to all network system hosts and terminals is performed by one host, there is a problem that a load of distribution management processing is applied to one host.

An object of the present invention is to provide a software resource management system that allows a user to freely specify a distribution method for each distribution.

[0008]

According to the present invention, there is provided a software resource distribution management system for distributing software resources from a higher system to a lower system connected thereto. And means for distributing software resources according to the distribution control information.

[0009] A distribution management table in which a user defines a distribution method for each distribution is managed by a host or terminal that executes distribution. When a program distribution request is issued, the host or terminal that performs distribution controls distribution of the program according to the distribution method specified in the distribution management table, so that the user can freely select the distribution method. When distributing, the distribution management table and the distributed material are distributed as a set, and the distribution is requested to the distribution destination host or terminal to the terminal etc. managed by these. Will no longer be required for distribution management.

[0010]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described below in detail with reference to the drawings.

FIG. 1 is an overall configuration diagram showing an embodiment of the present invention. The terminal device 101 is a management terminal, and inputs a program to be distributed, a system that has undergone generation or system integration, a distribution management table indicating a distribution method required at the time of distribution, and a database 401, 402 managed by the host system 201. accumulate. The database 401 stores distribution items such as programs and systems to be distributed, and the database 402 stores a distribution management table. The program and the system are distributed to the host system 201 in accordance with the contents of the distribution management table stored in the database 402.

In FIG. 1, instead of direct distribution from the host system 201 to the terminal systems 103-a, b, c, d, e, and f, the host system 201 sends a distribution request to the host system 202 and the terminal system 102. Terminal system 103-
The example which distributes to a, b, c, d, e, and f is shown. The terminal system 102 is a distribution terminal, and is a terminal system that distributes programs and systems. Host system 201
Is the distribution destination terminal of each system to the host system 202 and the terminal system 102 (the host system 202 is the terminal system 103-a, b, c. The terminal system 102 is the distribution system required for the terminal system 103-d, e, f). (Programs, systems, etc.) and distribution management tables defined for each distribution. The host system 202 stores the received program and system in the database 411,
The received distribution management table is stored in the database 412. Similarly, the terminal system 102 has the database 42
The respective information is stored in 1, 422. After that, the host system 202 and the terminal system 102 distribute the program, the system, and the distribution management table to the terminal system 103 according to the distribution management table. The terminal system 103 receiving the distribution loads the program and the system,
Alternatively, different redefinition is performed for each terminal system, and the program and the system are made usable. The distributed management table is stored in the database 432 of each terminal system, and the programs, systems, and the like currently owned by each terminal system are managed by the database 432. what if,
If there are any programs, systems, etc. that are no longer used in the terminal system, they are deleted, and at the same time, the information of the corresponding management table is deleted. If the management table of the same distribution item is at the distribution destination before distribution, the distribution destination system updates the newly transmitted management table.

FIG. 3 is a view showing a distribution management table before distribution stored in the database 402 of FIG. The program A and the system B are programs and systems that have performed generation and system integration. The configuration of this management table is composed of attribute types and attribute values indicating the distribution method for each distribution.

FIG. 4 explains the meaning of various attribute values (attribute values) defined in the management table of FIG. As described above, the value to be input differs for each attribute and is used at the time of distribution. There are types of attributes other than the present embodiment, and the present invention is not limited to the types of attributes.

The distribution method of each distribution in FIG. 3 will be described. The distribution process to be described next is performed by distribution from 202 and 102 to 103 in FIG. These distribution management tables may be input at the same time as inputting the distribution, or the distribution management table may be input after inputting the distribution. Distribution is performed according to the attribute type and attribute value of the distribution management table. The distribution method differs for each attribute type, for example, as follows.

Distribution destination attribute: Only the distribution destination indicated by the attribute value distributes the distribution.

Distribution number attribute: Distribution not exceeding the value indicated by the attribute value is not performed. For example, if the attribute value is 5, it means that there are only five places to distribute, and no distribution to six or more places.

Distribution date attribute: Means that distribution starts after the schedule indicated by the attribute value.

Application date attribute: It indicates the schedule for the user of the distribution destination to replace the old distribution material with the new distribution material. Effective when you want to replace all systems at the same time. This attribute is not directly related to the distribution method. It simply sends the value of this attribute to the distribution destination.

Version attribute: Indicates the version number of the distribution. If the distribution destination has the same distribution (identified by the distribution name), the distribution is distributed if the version number of the distribution is newer than the version number of the distribution.

In the distribution system (201, 202, and 102 in FIG. 1 in this embodiment), control is performed in accordance with the above-described various attributes (distribution methods).

Next, regarding the distribution of the program A, the third
This will be described with reference to the management table shown in FIG. FIG. 5 is a flowchart showing a program distribution process.

A distribution date is specified in the management table of the program A, and it is checked whether or not the distribution date has passed. The check is performed immediately after the system is started (501). If it is after the distribution date, distribution is performed according to the number of distributions. First, it is checked whether the number of distributions is 0 (502). If the value is 0, distribution cannot be performed any more, and the distribution ends. If the number of distributions is 0 or more, distribution is possible, and if there is a distribution request from the distribution destination WS, the program A is distributed (503). Thereafter, the number of distributions is subtracted by 1 (504). If the number of distributions becomes 0, the distribution ends. If not, the distribution request from the WS is waited for (505).

After the distribution, on the WS side, the user updates the program A after the application date.

Further, the distribution of the system B will be described with reference to the management table shown in FIG. 3 and FIG. FIG. 6 is a flowchart showing the distribution processing of the system B.

The distribution date is specified in the management table of the system B, and it is checked whether or not the distribution date has passed. The check is performed immediately after the system is started (601). If it is after the distribution date, it will be available for distribution,
If there is a distribution request from the distribution destination WS (602), the distribution request
If the WS name is in the distribution destination of the management table (50
3) Distribute system B (604). If not, the distribution is rejected (605). In this way, the processing is continued until the operation of the distribution host ends.

As described above, in this embodiment, a distribution attribute can be specified for each distribution, and management can be performed according to the user's system. In addition, there is a distribution management table for distribution items at the distribution destination,
By collecting the distribution management table, the distribution status of which program has been distributed to which system can be known.

In this embodiment, as shown in FIG. 1, the host system 201 distributes a set of a distribution and a distribution management table to the host system 202 and the terminal system 102, and distributes them to these systems. Since distribution is requested based on the distribution management table, distributed processing can be performed without imposing a load on one host system 201.

[0029]

According to the present invention, there is an effect that the distribution freely selected by the user can be realized by the system administrator defining the distribution attribute indicating the distribution method for various distributions from the management terminal. .

[Brief description of the drawings]

FIG. 1 is an overall configuration diagram showing one embodiment of the present invention.

FIG. 2 is a diagram showing a conventional distribution method.

FIG. 3 is a diagram showing a format of a distribution management table.

FIG. 4 is a diagram for explaining the meaning of an attribute value in FIG. 3;

FIG. 5 is a flowchart illustrating a distribution process of a program A;

FIG. 6 is a flowchart illustrating a distribution process of a system B;

[Explanation of symbols]

 101: Terminal system (management terminal) 102: Terminal system (distribution terminal) 103: Terminal system 201, 202: Host system

────────────────────────────────────────────────── ───

[Procedure amendment]

[Submission date] August 9, 1999 (1999.8.9)

[Procedure amendment 1]

[Document name to be amended] Statement

[Correction target item name] Name of invention

[Correction method] Change

[Correction contents]

[Title of the Invention] Software resource distribution system

[Procedure amendment 2]

[Document name to be amended] Statement

[Correction target item name] Claims

[Correction method] Change

[Correction contents]

[Claims]

[Procedure amendment 3]

[Document name to be amended] Statement

[Correction target item name] 0001

[Correction method] Change

[Correction contents]

The present invention relates to a software resource distribution system for distributing various software resources distributed from a computer according to distribution conditions.

[Procedure amendment 4]

[Document name to be amended] Statement

[Correction target item name] 0007

[Correction method] Change

[Correction contents]

It is an object of the present invention to provide a software resource distribution system that allows a user to specify a distribution method for each distribution.

[Procedure amendment 5]

[Document name to be amended] Statement

[Correction target item name] 0008

[Correction method] Change

[Correction contents]

In order to achieve the above object, according to the present invention, in a software resource distribution system for distributing software resources from a higher system to a lower system connected thereto, distribution control information corresponding to the software resource is transmitted to the higher system. There are provided means for storing and means for distributing software resources according to the distribution control information.

[Procedure amendment 6]

[Document name to be amended] Statement

[Correction target item name] 0009

[Correction method] Change

[Correction contents]

[0009] A distribution management table in which a user defines a distribution method for each distribution is managed by a host or terminal that executes distribution. When a program distribution request is issued, the host or terminal that performs distribution controls distribution of the program according to the distribution method specified in the distribution management table, so that the user can freely select the distribution method. When distributing, the distribution management table and the distributed material are distributed as a set, and the distribution is requested to the distribution destination host or terminal to the terminal etc. managed by these. Will not be distributed.

[Procedure amendment 7]

[Document name to be amended] Statement

[Correction target item name] 0028

[Correction method] Change

[Correction contents]

In this embodiment, as shown in FIG. 1, the host system 201 distributes a set of a distribution product and a distribution management table to the host system 202 and the terminal system 102. Requesting distribution based on the distribution management table, distributed processing can be performed without imposing a load on one host system 201. Further, according to the present embodiment, there is an effect that the distribution freely selected by the user can be realized by the system administrator defining the distribution attribute indicating the distribution method for the various distribution materials from the management terminal.

[Procedure amendment 8]

[Document name to be amended] Statement

[Correction target item name] 0029

[Correction method] Change

[Correction contents]

According to the present invention, there is an effect that distribution can be performed by specifying a distribution method for each distribution.

 ──────────────────────────────────────────────────の Continuing on the front page (72) Inventor Keizo Mizuguchi 5030 Totsuka-cho, Totsuka-ku, Yokohama-shi, Kanagawa Prefecture Inside the software factory of Hitachi, Ltd. (72) Takeo Nakayama 5030 Totsuka-cho, Totsuka-ku, Yokohama, Kanagawa Prefecture Inside the Hitachi Ltd. software factory

Claims (4)

[Claims] In a software resource distribution management system including a first computer for distributing software resources and a second computer for receiving the software resources, a first storage unit for storing programs and storing distribution control information. And a distribution control unit for distributing the software resource based on the distribution control information. 2. The software resource distribution management system according to claim 1, further comprising a third computer, wherein the second computer transfers the software resource received from the first computer based on the distribution control information. A software resource distribution management system for distributing to software resources. 3. The software resource distribution management system according to claim 1, wherein said distribution control information distributed to said second computer is referred to by said second computer, and said second control information is distributed based on said distribution control information. A software resource distribution management system, wherein the software resource is used in a computer. 4. The software resource distribution management system according to claim 1, wherein the software resource is a program.