JPH11288398A - Network control method, medium and network control system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a network control method and a medium capable of executing setting for each category on a controller side, setting control for handling only a specified category or the control for uniformly handling the specified category on the controller side and automatically installing only the control information of a device belonging to the category to be handled to a controller. SOLUTION: In this network control method, the device 20 is provided with category data 20b relating to the present device 20 and the setting relating to the connection of the present device 20, the controller 10 is provided with the setting relating to the connection of the device 20 for each category of the device 20 and the controller 10 decides whether or not to obtain the device driver and control information of the device 20 corresponding to the combination of the setting on the side of the device 20 and the setting on the side of the controller 10.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a network control technique, and more particularly, to a technique executed between a plurality of devices and a plurality of controllers connected on a network in which a controlled device and a controlling controller coexist. The present invention relates to a network control method for acquiring control information to be performed, and a medium and an apparatus recording the method.

[0002]

2. Description of the Related Art Devices to be controlled (for example, computer peripherals and information appliances) and controllers to be controlled (for example, personal computers (PCs)) are connected to a mixed network. In a conventional network control method for obtaining control information between devices, for example, many types of devices (devices and controllers) are connected to a certain range of networks.
Is connected, the controller automatically obtains control information for all devices in the range, the controller automatically obtains control information for some limited devices, or controls devices In doing so, all the necessary settings on the controller side must be performed manually or selectively.

[0003]

However, in such a conventional network control method, the controller automatically obtains control information of all devices or the control information of a limited part of the devices. A simple and easy setting in advance before the execution of the network control method is set whether or not to obtain control information, such as whether to automatically obtain or to manually perform all control information necessary for the controller to control the device. There was a technical problem that was difficult.

An object of the present invention is to solve such a conventional problem. In particular, a device (device to be controlled) has category data relating to its own device and settings relating to its connection. , The controller (device to be controlled) has settings related to device connection for each device category, and the controller acquires the device driver and control information of the device according to the combination of the device-side settings and the controller-side settings By deciding whether to perform the setting, the controller can execute the setting for each category, and the controller can set the control to handle only a specific category or the control to handle the specific category in a unified manner. A network that can automatically install only control information on the controller And its object is to provide a control method and medium.

[0005] In addition, since it is possible to make settings relating to connection for each category on the controller side, it is possible to install a device driver and control information for controlling a device having a particularly important role even within the same category. It is possible to make settings that require user's instructions at all times, and for general devices, automatically install the device driver and control information on the appropriate controller, so that when the user installs the device, It is an object of the present invention to provide a network control method and a medium that can reduce necessary labor.

[0006]

According to the first aspect of the present invention, which is achieved by the present invention to solve the above-mentioned problems, a device to be controlled 20 and a controller 10 to be controlled are connected to a network 30 in which the devices are mixed. Device 20
And a network control method for the controller 10, wherein at least one or more controllers 10 for controlling the device 20 are controlled based on the timing specified by the user, the device 20, or the controller 10. A device-side processing step including a step of discriminating from the inside, a step of instructing the controller 10 of control information necessary for controlling the device 20 or an address on the network included in the device driver 20a; At least one from device 20 connected on 30
When one or more controllers 10 are designated, the control information specified by the device 20 or the address on the network included in the device driver 20a is accessed to control the control information or the device driver 2.
0a, and transferring the collected control information or device driver 20a to the designated controller 1
And a controller-side processing step including a step of installing the controller on the network.

According to the first aspect of the present invention, when the device 20 is connected to the network 30, it is determined which controller 10 acquires the control information or the device driver 20a required for controlling the device 20. Since the determination can be made almost automatically and the number of manual operations can be reduced, the control information or the device driver 20a
The user-side effort required to install the software can be reduced. In particular, many different types of devices 20
It is considered that the effect is great when a large number of different types of controllers 10 are connected on the network 30.

According to a second aspect of the present invention, which is made by the present invention to solve the above-described problem, in the network control method according to the first aspect, the device-side processing performed by the device 20 is performed by itself. Control information or a device driver 20a necessary for controlling the
Category data 20b indicating a category to which the user belongs;
Default setting data 20c including at least an instruction as to whether to transmit the control information or the device driver 20a to the controller 10 and to instruct the destination controller 10 to install the control information or the device driver 20a. A device category return step of returning category data 20b relating to its own category to the requesting controller 10 in response to a category name inquiry from the controller 1
0, the controller-side processing step is performed as follows:
When the category data 20b is received, the category data 20b registered in advance in the category correspondence table 11 of the controller 10 is compared with the received category data 20b. A category recognizing step of recognizing an operation corresponding to the category, and preparing the control information or device driver 20a commonly set for the recognized category or the device 20 when the default setting data 20c is received. Control information or device driver 20a for each device 20
A device driver determining step of determining, for each category of the device 20, an operation selection as to whether to install the device driver itself according to the contents of the default setting data 20c, and the device driver 20a according to the execution result of the device driver determining step. And an installation step of deciding whether or not to install the program and executing an installation operation based on the decision result.

According to the second aspect of the present invention, the first aspect is provided.
In addition to the effects described in (1), the device 20 (the device on the controlled side) includes category data 20b
The controller 10 (controlling device) has settings relating to the connection of the device 20 for each category of the device 20, and the settings of the device 20 and the settings of the controller 10 are provided. By performing the step of determining whether the controller 10 acquires the device driver or the control information of the device 20 according to the combination of the above, the setting for each category can be executed on the controller 10 side, and only the specific category can be set. The control to be handled or the control to handle a specific category in a unified manner can be set on the controller 10 side, and only the control information of the devices 20 belonging to the handled category can be automatically installed in the controller 10.

[0010] Further, since the setting for connection for each category can be performed on the controller 10 side, the device 20 having a particularly important role even in the same category can be set.
When a device driver or control information for controlling the device is installed, a setting that always requires a user's instruction can be performed. For a general device 20, the device driver and the control are automatically assigned to the appropriate controller 10. By performing the step of installing information (ie, the step of installing according to the setting of the “device” operation), when the device 20 is connected to the network 30, which controller 10
Control information or device driver 20 required for control of 0
Since it is possible to automatically determine whether or not to acquire the “a” and to reduce the number of manual operations, it is possible to reduce the effort on the user side required for installing the control information or the device driver 20a.

According to a third aspect of the present invention to solve the above-mentioned problem, in the network control method according to the second aspect, the controller-side processing step executes the category recognition step. When the category specified by the category data 20b received by the controller 10 is not registered in the category correspondence table 11 of the controller 10, the device driver determination step is executed. A network control method comprising: automatically instructing a new setting; and automatically generating an entry for the new setting.

According to the invention described in claim 3, according to claim 2,
In addition to the effects described in the above, the device 20 unknown to the controller 10 because it is not registered in the category correspondence table 11
Even if it is determined that the control information or the device driver 20a is installed in the future expansion of the connection device 20 by executing the step of automatically creating an entry relating to the new category, It is possible to flexibly respond by minimizing the extra labor on the user side required for the operation.

According to a fourth aspect of the present invention, which is made by the present invention to solve the above-mentioned problem, in the network control method according to the second aspect, the controller-side processing step includes the steps of: A device detecting step of detecting that the device 20 is connected to the network 30;
A default setting requesting step of requesting the category data 20b and the default setting data 20c to the controller 1; and a device driver determining step.
This is a network control method for determining whether or not to install on the side of the device 0 when a new device 20 is connected.

According to the invention described in claim 4, according to claim 2,
In addition to the effects described in the above, the controller-side processing step can detect that the new device 20 is connected to the network 30 when the new device 20 is connected, and the network 30 of such a new device 20 can be detected.
As a result, the control information or the device driver 20a can be installed and executed in synchronization with the connection to the device 30. As a result, after the connection of the new device 20 to the network 30, the user can obtain the control information or the device required to control the new device 20. The labor for instructing the installation of the driver 20a on the controller 10 can be omitted, and an autonomous network system having advanced man-machine interface can be constructed.

According to a fifth aspect of the present invention, which is made by the present invention to solve the above-mentioned problems, in the network control method according to the second aspect, the controller-side processing step comprises the steps of: Is an identifier transmitted to the controller 10 by the device I.
A connection history storing step of storing the correspondence between the D data 20d and the past connection state data as a past connection state table;
Determining whether or not the device 20 has been connected in the past; and determining that the device 20 which has been connected in the past has been connected again. This is a network control method including a past connection state calling step of calling the past connection state data 10a of the first embodiment, and a resume step of reproducing the past controllable state of the device 20 based on the called connection state data 10a.

According to the invention set forth in claim 5, according to claim 2,
In addition to the effects described above, by executing the connection history storage step, the correspondence between the device ID data 20d and the past connection status data can be stored as a past connection status table. As a result, when a known device 20 that has been connected in the past is connected on the network 30, the device 20 is connected to the device ID data 20.
d, the past connection status table can be searched based on the device ID data 20d, and the past controllable state of the known device 20 that has been connected in the past can be obtained. Can be reproduced. By doing so, even if a specific setting is limited to only a specific device 20 in the past connection mode, when the device 20 is connected to the network 30 again, the device 20 Information or device driver 2 required to control the
0a does not need to be manually reset each time the device 20 is connected, and after the device 20 having a connection history in the past is connected to the network 30, the user can set the control information or the device driver 2 required for controlling the device 20.
This makes it possible to save the labor for instructing the installation of the controller 0a into the controller 10, and to construct an autonomous network system having advanced man-machine interface.

According to a sixth aspect of the present invention to solve the above-mentioned problem, in the network control method according to the second aspect, the device 20 includes the device-side processing step and the controller-side processing step. And a network control method for executing at least one of the device-side processing step and the controller-side processing step in accordance with a connection condition to the network 30.

According to the invention described in claim 6, according to claim 2,
In addition to the effects described in (1), since the device 20 has the function of executing the device-side processing step and the controller-side processing step, the device connected on the network 30 has the role of the device 20 and the function of the controller 10. Both roles can be satisfied at the same time. For example, for a device having a higher control right than itself, the device is regarded as the controller 10 and the device itself is referred to as the device 2.
In a similar manner, a flexible connection mode in which a device having a lower control right than itself is regarded as a device 20 and the device itself is set in the controller 10 is automatically realized. Will be able to do it. In other words, by having the functions of the device 20 and the controller 10 at the same time, it is possible to realize a controller 10 and device 20 device (a device for one and two roles) in which several devices 20 are collectively operated as one device 20. Become like As a result, a network 30 and a control system having a tree topology can be constructed, and an autonomous network system having advanced man-machine interface can be constructed.

According to a seventh aspect of the present invention to solve the above-mentioned problem, in the network control method according to the second aspect, the device-side processing step comprises:
A plurality of types of the device drivers or a plurality of types of the control information can be executed, and a predetermined device driver or the control information 20 is selected from the device drivers or the control information according to a connection condition to the network 30.
This is a network control method for selecting a.

According to the invention of claim 7, according to claim 6,
Device 20 and the controller 1
0 function at the same time, some devices 20
Work together as one device 20,
It becomes possible to realize the controller 10 and the device 20 (a device that plays two roles). As a result, a predetermined device driver or control information 20a can be autonomously selected from the device driver or control information 20a and installed in a predetermined controller 10 in accordance with a connection condition to the network 30 having a tree topology. A control system can be constructed, and an autonomous network system having advanced man-machine interface can be constructed.

In order to solve the above-mentioned problem, the invention according to claim 8 according to the present invention is characterized in that, in the network control method according to claim 2, the device-side processing step comprises:
A step of internally storing control information or a device driver 20a for controlling itself, and a step of transferring the control information or the device driver 20a to the controller 10 via a network 30. Referring to the control information or the device driver 20a, and the device 2 that has transferred the device driver or the control information 20a based on the referred device driver or the control information 20a.
0 is a network control method including a step of controlling 0.

According to the invention described in claim 8, according to claim 2,
In addition to the effects described in the above, by providing the device-side processing step of internally storing a device driver or control information 20a for controlling itself, the device driver or control information 20a can be provided inside the device 20. become able to. By holding the device driver or the control information 20a inside the device 20 in this way, it is not necessary to procure the device driver or the control information 20a required for controlling the device 20 from outside, and the device 20 is installed on the network 30. In this case, the autonomous installation work can be performed only with the device driver or the control information 20a held in the own storage device, and an autonomous network system having advanced man-machine interface can be constructed.

According to a ninth aspect of the present invention for solving the above-mentioned problem, in the network control method according to the second aspect, the category indicated by the category data 20b is changed according to the operation of the device 20. A network control method including a step of forming a hierarchical structure based on categories.

According to the invention of claim 9, according to claim 2,
In addition to the effects described in the above, category data 20 having a hierarchical structure
By having b, it becomes possible to set a category of a fine classification in a category of a coarse classification. As a result, when the setting for the category of the fine classification is prioritized over the setting for the category of the coarse classification, among the devices 20 belonging to a certain coarse classification category, in particular, the category of a certain fine classification Can be set for the device 20 belonging to. As a result, finer connection settings can be made, and a system having advanced man-machine interface properties can be realized.

According to a tenth aspect of the present invention, which has been made to solve the above-mentioned problem, a device 2 to be controlled
Device 20 and controller 1 connected on a network where controller 0 and controller 10 to be controlled coexist
0 is a medium in which a control program code of 0 is recorded, and at least one controller 10 for controlling the device 20 is connected to the network based on the timing designated by the user, the device 20 or the controller 10. A device code including a program code for determining from the controller 10 and a program code for instructing the controller 10 of control information necessary for controlling the device 20 or an address on the network included in the device driver 20a. When at least one or more controllers 10 are designated from the device 20 connected to the network 30 by the side processing program code, the control information indicated by the device 20 or the device driver 20a on the network And a device-side processing program code having a program code for accessing the address of the controller 10 and collecting the control information or the device driver 20a, and a program code for installing the collected control information or the device driver 20a in the designated controller 10. Is recorded.

According to the tenth aspect, the same effect as that of the first aspect is obtained.

[0027] In order to solve the above-mentioned problems, the invention according to claim 11 has been achieved by the present invention, in the medium according to claim 10, control information necessary for controlling itself or program code of the device driver 20a. And category data 20b indicating a category to which the device belongs, and control information or a device driver 20a.
And the default setting data 20c including at least an instruction as to whether or not to instruct the destination controller 10 to install the control information or the device driver 20a and the own category in response to the inquiry of the category name from the controller 10. Category data 2
0b to the requesting controller 10, the device-side processing program code read and executed by the device 20, and the controller 10 when the category data 20b is received.
Category data 20b registered in advance in the category correspondence table 11 and the received category data 2
0b and a category recognition program code for recognizing an operation corresponding to the category of the device 20 that has transmitted the category data 20b, and a common mode for the recognized category when the default setting data 20c is received. Of the control information or the device driver 20a set in the default setting data 20c or the control information or the device driver 20a of the device 20 prepared for each device 20 according to the contents of the default setting data 20c. Select device 2
0, a device driver determination program code determined for each category, and whether to install the device driver 20a is determined according to the execution result of the device driver determination program code, and an installation operation is performed based on the determination result. And a controller-side processing program code which is read and executed by the controller 10.

According to the eleventh aspect, the same effect as that of the second aspect is obtained.

According to a twelfth aspect of the present invention for solving the above-mentioned problem, in the medium according to the eleventh aspect, the category received by the controller 10 by executing the category recognition program code. When the category indicated by the data 20b is not registered in the category correspondence table 11 in the controller 10, when the device driver determination program code is executed, control information or new setting of the device driver 20a is automatically instructed. And a program code for automatically generating an entry for the new setting.

According to the twelfth aspect, the same effect as that of the third aspect is obtained.

According to a thirteenth aspect of the present invention for solving the above-mentioned problem, in the medium according to the eleventh aspect, the new device 20 is connected to the network 30 when the new device 20 is connected. A device driver detection program code, a program code for requesting the category data 20b and the default setting data 20c to the newly connected device 20, and a device driver determination program code. Newly connected device 2
And a program code for determining whether or not to install control information 0 on the controller 10 when a new device 20 is connected.

According to the thirteenth aspect, the same effect as the fourth aspect is obtained.

According to a fourteenth aspect of the present invention, which is made by the present invention to solve the above-mentioned problem, in the medium according to the eleventh aspect, each of the devices 20 on the network 30 is provided.
Executes a connection history storage program code for storing a correspondence relationship between device ID data 20d, which is an identifier transmitted to the controller 10, and past connection status data as a past connection status table, and the device 20 detection program code. The program code for determining whether the device 20 has been connected in the past when the connection has been made, and the connection history storage program code when the device 20 having been connected in the past is determined to be connected again. The controller side having a program code for calling the stored past connection state data 10a of the device 20 and a program code for reproducing the past controllable state of the device 20 based on the called connection state data 10a. Processing program code is recorded It is a body.

According to the fourteenth aspect, the same effect as the fifth aspect can be obtained.

According to a fifteenth aspect of the present invention made to solve the above-mentioned problem, in the medium according to the eleventh aspect, control information for controlling itself or a device driver 20a is stored therein. The device-side processing program code including a program code, a step of transferring control information or a device driver 20a to the controller 10 via the network 30, and a program code referring to the control information or the device driver 20a; And a controller-side processing program code having a program code for controlling the device 20 that has transferred the device driver or the control information 20a based on the device driver or the control information 20a.

According to the fifteenth aspect, the same effect as the eighth aspect can be obtained.

According to a sixteenth aspect of the present invention, which is made by the present invention to solve the above problems, the controlled device 2
This is a network control system of the device 20 and the controller 10 connected on the network 30 in which the controller 10 and the controller 10 to be controlled coexist.

Here, the device 20 has a device-side processor 201 and a device-side memory 202.

The device-side processor 201 includes a user,
At least one device for controlling the device 20 based on the timing specified by the device 20 or the controller 10
One or more controllers 10 are identified from among the controllers 10 connected to the network, and control information necessary for controlling the device 20 or an address on the network included in the device driver 20a is determined by the controller. 10.

The device-side memory 202 holds the control information or the device driver 20a.

The controller has a controller-side processor 101 and a controller-side memory 102.

When at least one or more controllers 10 are designated by the devices 20 connected to the network 30, the controller-side processor 101 executes the control information specified by the devices 20 or the control information included in the device driver 20 a. The control information or device driver 20a is collected by accessing an address on the network, and the collected control information or device driver 20a is installed in the designated controller 10.

The controller-side memory 102 holds the control information or the device driver 20a.

According to the sixteenth aspect, when the device 20 is connected to the network 30,
Since it is possible to almost automatically determine which controller 10 acquires the control information or the device driver 20a required for controlling the device 20, the number of manual operations can be reduced.
It is possible to reduce the labor on the user side required for the installation of a. In particular, many different types of devices 2
It is considered that the effect is great when a large number of controllers 10 of zero or many different types are connected on the network 30.

Claim 1 has been made to solve the above problems.
The invention described in 7 is a network control method of the device 20 and the controller 10 connected on the network 30 in which the device 20 to be controlled and the controller 10 to be controlled coexist, and the controller 10 is distinguished from the network 30. This is a network control method including a process and a device-side processing step of instructing the controller 10 of information necessary for controlling the device 20 and causing the controller 10 to install the information.

According to the seventeenth aspect, when the device 20 is connected to the network 30,
Since it is possible to almost automatically determine which controller 10 acquires the control information or the device driver 20a required for controlling the device 20, the number of manual operations can be reduced.
It is possible to reduce the labor on the user side required for the installation of a. In particular, many different types of devices 2
It is considered that the effect is great when a large number of controllers 10 of zero or many different types are connected on the network 30.

Claim 1 has been made to solve the above problems.
The invention described in 8 is a network control method of the device 20 and the controller 10 connected on the network 30 in which the device 20 to be controlled and the controller 10 to be controlled are mixed, and the device 20 is distinguished from the network 30. This is a network control method including a step and a controller-side processing step of instructing the device 20 of information necessary for controlling the controller 10 and installing the information in the device 20.

According to the eighteenth aspect, the same effect as that of the seventeenth aspect can be obtained.

Claim 1 made in order to solve the above-mentioned problem
The invention described in 9 is a medium in which the control program code of the device 20 and the controller 10 connected on the network 30 in which the device 20 to be controlled and the controller 10 to be controlled are mixed is recorded. A device-side processing program code including a program code for determining from within the network 30 and a program code for instructing the controller 10 of information necessary for controlling the device 20 and causing the controller 10 to install the information is recorded. It is a medium characterized by being performed.

According to the nineteenth aspect, the same effect as that of the first aspect is obtained.

Claim 2 has been made to solve the above problem.
0 is a medium in which a control program code of the device 20 and the controller 10 connected on the network 30 in which the device 20 to be controlled and the controller 10 to be controlled are mixed is recorded. The controller 10 side processing program code including a program code for determining from the network 30 and a program code for instructing the device 20 of information necessary for controlling the controller 10 and causing the device 20 to install the information is A medium characterized by being recorded.

According to the twentieth aspect, the same effect as that of the first aspect is obtained.

Claim 2 made in order to solve the above-mentioned problem
The invention described in 1 is a network control system of the device 20 and the controller 10 connected on the network 30 in which the device 20 to be controlled and the controller 10 to be controlled coexist, and the controller 10 is identified from the network 30. The network control system includes a device-side processor 201 that instructs the controller 10 with a program code and information necessary for controlling the device 20, and causes the controller 10 to install the information.

According to the twenty-first aspect, when the device 20 is connected to the network 30,
Since it is possible to almost automatically determine which controller 10 acquires the control information or the device driver 20a required for controlling the device 20, the number of manual operations can be reduced.
It is possible to reduce the labor on the user side required for the installation of a. In particular, many different types of devices 2
It is considered that the effect is great when a large number of controllers 10 of zero or many different types are connected on the network 30.

Claim 2 has been made to solve the above problem.
The invention described in 2 is a network control system of the device 20 and the controller 10 connected on the network 30 in which the device 20 to be controlled and the controller 10 to be controlled coexist, and the device 20 is identified from the network 30. The network control system includes a controller processor 101 for instructing the device 20 with a program code and information necessary for controlling the controller 10 and causing the device 20 to install the information.

According to the twenty-second aspect, the same effect as that of the twenty-first aspect is obtained.

[0057]

FIG. 1 is a basic configuration diagram of a network for explaining a connection form of a network 30 according to the present invention. FIG. 1A is a basic configuration diagram of a device 20 and a controller 10. FIG. 1B shows a device 2 connected on a network 30 in which a device 20 to be controlled and a controller 10 to be controlled coexist.
FIG. 1 is a connection configuration diagram of a controller 0 and a controller 10;
FIG. 3C is a connection configuration diagram of the device 20 and the controller 10 connected on the network 30 in which the device 20 to be controlled is connected to the common controller 10. FIG. 2 is a network configuration diagram in which a plurality of types of peripheral devices and a plurality of types of CPUs coexist.

Each of the devices 20 of the present embodiment corresponds to FIG.
As shown in FIG. 1A, the device has a device-side processor 201 and a device-side memory 202.

The device-side processor 201 is a means for mainly executing the device-side processing steps. At least one or more controllers 10 for controlling the device 20 based on the timing designated by the user, the device 20 or the controller 10. From the controller 10 connected to the network, and instructs the controller 10 to provide control information necessary for controlling the device 20 or an address on the network included in the device driver 20a, Specifically, the logic section of the parallel processing RAM and the DS
It is realized by an LSI operable by a program such as a P or CPU.

The device-side memory 202 holds control information or a device driver 20a, and when a program code describing a network control method recorded on a medium is read, holds it. Is realized by a RAM.

The controller has a controller-side processor 101 and a controller-side memory 102.

The controller-side processor 101 is a means for mainly executing a controller-side processing step. When at least one or more controllers 10 are designated from the devices 20 connected on the network 30, the controller 20 is activated. The control information to be instructed or the address on the network included in the device driver 20a is accessed to access the control information or the device driver 20a.
And the collected control information or device driver 2
0a is installed in the designated controller 10, and is specifically realized by the CPU.

The controller-side memory 102 holds control information or a device driver 20a, and when a program code describing a network control method recorded on a medium is read, holds the program code.
Specifically, it is realized by a RAM. The medium includes a removable (removable) recording medium such as a CDROM, a magneto-optical disk, and an IC card, and a recording device such as a hard disk capable of reading a program using a communication line or a network such as a LAN. Contains.

In the following description, the network 30
As shown in FIG. 1 (b), the controlled devices 20,
, 20 and the controllers 10,..., 10 to be controlled are mixed and connected. On this network, a plurality of devices 20,. It is connected.

As the network 30, FIG.
As shown in (c), the controlled devices 20,.
0 is a network connected to the common controller 10 (controller-side processor 101).

More specifically, as shown in FIG. 2, a plurality of types of PCs (CPs)
U), a network configuration in which computer peripheral devices such as a memory device, a hard disk device, a monitor, a keyboard, and a printer, and information home appliances such as a video camera are mixed in a serially connected state.

FIG. 3 is a network configuration diagram for explaining a specific configuration of the network 30 in FIG.
FIG. 1 is a network configuration diagram in which computer peripheral devices and information home appliances are connected to a personal computer (PC) via a serial communication line.

As an interface for each device connected to the serial connection network 30 shown in FIG. 2, for example, a high-speed serial interface called IEEE 1394 can be used. By using such a high-speed serial interface, multimedia data such as moving image data and audio data can be transmitted at high speed and in real time.

Specifically, the network 30 includes a computer peripheral device having an IEEE 1394 interface represented by an image reader, a laser printer, a keyboard, a CRT, a mouse, a hard disk, and the like;
X, a video camera, a communication karaoke apparatus, an information home appliance having an IEEE 1394 interface typified by a toaster, and a PC or a notebook computer having an IEEE 1394 interface are connected via a serial communication line to form a network. .

FIG. 4A shows the basic configuration of the category correspondence table 11 used in the controller-side processing performed by the controller 10 (controller processor 101), which is registered in the category correspondence table 11 in advance. FIG. 4B is a table for explaining the operation corresponding to the category data 20b and the category name in which the category data 20b is transmitted by the device-side processor 201.
6 is a chart for explaining an example of an operation corresponding to the operation. Note that the same parts as those already described in the above embodiment are denoted by the same reference numerals, and redundant description will be omitted.

The category correspondence table 11 shown in FIG.
For each of the categories of the device-side processor 201, control information of the device 20 or information relating to settings relating to installation of the device driver 20a is described, and is stored in a storage unit such as a memory or a hard disk of the controller 10. In addition, category data 20b specifying a category and an operation corresponding to the category name are described.

Specifically, in the category correspondence table 11,
A plurality of categories identified by A, B, C, D,... Are stored, and control information of the controller 10 or operation of installing the device driver 20a corresponding to each of the categories is described.

In the following embodiment, for example, FIG.
As shown in FIG. 7, in the category A, the user is requested to input control information or data of the device driver 20a (for example, input of data using a floppy disk), and the control information of all the device-side processors 201 or the device driver 20a is requested. The operation of "install" for installing the device 20a corresponds to the category B. In the category B, the device 20 inquires of the control operation of the device 20 for the control information or the operation of the device driver 20a, and the device 20 responds to the setting of the device 20 which the device 20 has returned. The operation corresponds,
In the category C, the user is inquired about whether to install the control information of the device 20 or the device driver 20a or not, and the “user” according to the operation selected by the user from “install”, “device”, or “ignore”. The operation corresponds to the category D, and the operation of “ignore” in which the control information of all the devices 20 or the device driver 20a is not installed corresponds to the category D.

Here, all the devices 20 (device-side processors 201) have data 20b representing the category to which the own device 20 belongs, and control information of the own device 20 or settings relating to the installation of the device driver 20a in the controller 10 ( The data can be transmitted to the controller 10 (controller-side processor 101) on the network 30 through an interface.

Similarly, all the controllers 10 (controller-side processors 101) set the control information of the device 20 or the setting related to the installation of the device driver 20 a (“device” according to the setting of the device 20) for each category of the device 20. Setting, control information of all devices 20 or "install" to install device driver 20a, control information of all devices 20 or "ignore" not to install device driver 20a, control information of device 20 or device It has data indicating "user" for asking the user whether or not to install the driver 20a, and these data can be referred to from a program on the controller 10 system.

As will be described later, the device 20 (device-side processor 201) executes the category recognition step (step P).
According to the execution of 4), as shown in FIG. 4B, the category data 20b specifying the above-described category and operation can be transmitted. When the controller 10 (controller-side processor 101) executes the controller-side processing step, the controller 10 (the controller-side processor 101) receives the category data 20b registered in advance in the category correspondence table 11 and the device 20 from the device 20 via the network 30. A category recognizing step (step P4) for comparing the category data 20b with the category data 20b and recognizing an operation corresponding to the category name of the device 20 that has transmitted the category data 20b is executed.

FIG. 5 is a flowchart for explaining one embodiment of the network control method according to claims 1, 2, 10 and 11 of the present invention. In addition, about the same part as what was already described in the said embodiment,
The same reference numerals are given and duplicate explanations are omitted. In the following description of the embodiment, control information or device driver 2
0a, a case where the device driver 20a is installed will be described. However, the same installation process can be executed for control information.

The network control method shown in FIG. 5 includes a device-side process executed on the device 20 side and a controller-side process executed on the controller 10 (steps P2, P4, P5,..., P9). It has a central logical configuration.

All the devices 20 (device-side processors 201) have data 20b representing the category to which the device 20 belongs, and settings relating to the installation of the device driver 20a of the device 20 in the controller 10 (always install / always install). (Inquiry to the user whether to install or not to install), which can be transmitted to the controller 10 (controller processor 101) on the network 30 through the interface.

All the controllers 10 (controller-side processors 101) perform device driver 20 a of the device 20 for each category of the device 20.
(Installation settings to install the device drivers 20a of all the devices 20; “Ignore” settings to not install the device drivers 20a of all the devices 20) , A user inquiring the user whether or not to install the device driver 20a of the device 20), and these data can be referred to from a program on the controller 10 (controller processor 101) system.

The device-side processing step is a step executed by the device-side processor 201. Basically, the device-side processor 201 controls the device 20 based on the timing specified by the user, the device 20, or the controller 10 (controller-side processor 101). Determining at least one or more controllers 10 to be controlled from among the controllers 10 connected on the network 30;
And instructing the controller 10 the address on the network 30 of the device driver 20a necessary to control the device driver 20a.

Specifically, when the IEEE 1394 interface is used, a virtual bus address (1394) is used.
Bus address) is defined, each node can map memory to an address. The connection (input / output stream) is obtained by mapping the memory of the controller 10 (controller-side processor 101) to a certain address and accessing the address by the device 20. The binary data of the device driver 20a built in the device 20 can also be transmitted through the connection obtained here.

The controller-side processing step (step P
, P4, P5,..., P9) are basically at least one device 20 connected to the network 30.
When one or more controllers 10 (controller-side processors 101) are designated, a step of accessing the address of the device driver 20a specified by the device 20 on the network 30 (Step P2) and collecting the device drivers 20a (Step P2) P6 → P6A → P6B
→ P6C → P10, P7 → P7A → P7B → P5, P8
→ P8A → P8B → P5, P9 → P9A → P10)
Installing the collected device driver 20a in the designated controller 10 (controller-side processor 101).

By providing the device-side processing step and the controller-side processing step, when the device 20 is connected to the network 30,
(The controller-side processor 101) is the device 2
0 can be almost automatically (autonomously) determined whether to acquire the device driver 20a required for control of the device driver 20a, and the number of manual operations can be reduced. The required labor can be reduced. In particular, it is considered that the effect is great when many different types of devices 20 and many different types of controllers 10 are connected on the network 30.

Each of these steps is performed by the user and the device 2
0 or a program code for discriminating at least one or more controllers 10 that control the device 20 from the controllers 10 connected on the network 30 based on the timing specified by the controller 10 and the device 20 Device-side processing program code including a program code for instructing the controller 10 of the address of the device driver 20a required on the network 30 to the controller 30, and at least one or more controllers 10 are designated from the devices 20 connected on the network 30. Then, the program code for accessing the address on the network 30 of the device driver 20a specified by the device 20 (step P2) and collecting the device driver 20a, and the collected device driver 20a Named controller 10 is recorded on the aforementioned medium as a device side processing program code and the controller-side processing program code and a program code to be installed on the (controller-side processor 101).

The program codes describing the device-side processing steps are read and held in the device-side memory 202, and are read out and executed by the device-side processor 201.

The program code describing the controller-side processing steps is read and held in the controller-side memory 102, and is read out and executed by the controller-side processor 101.

This will be described in more detail.

The device-side processing executed by the device 20 is a step executed by the device-side processor 201, and includes a device driver 20a necessary for controlling itself, category data 20b indicating a category to which the device belongs, and Sends the device driver 20a to the controller 10 (controller-side processor 101) and instructs the destination controller 10 to install or not install the device driver 20a (specifically, "device", "install" , "Ignore" or "user") can be transmitted and received.

The device-side processing executed by the device-side processor 201 includes specifying its own category name in response to a command of a category name inquiry (step P2) from the controller 10 (controller-side processor 101) via the network 30. Category data 2
0b is returned to the controller 10 (controller-side processor 101) that has sent the inquiry to the device category (step P3). Each of these steps is stored in a medium described below in a state described by a program code generated by using a programming language such as Java which can be executed by the device 20.

The program code describing the device-side processing steps is read and held in the device-side memory 202, and is read and executed by the device-side processor 201.

Further, the device-side processing step (device-side processor 201) includes a device driver 20a to be controlled.
Can be executed, and a step of selecting a predetermined device driver 20a from the device drivers 20a,..., 20a in accordance with the connection conditions to the network 30 can be executed.

That is, by having the functions of the device-side processor 201 and the controller 10 at the same time, the controller 10 and the device 20 (one of two roles), such that several devices 20 collectively operate as one device 20. Equipment) can be realized. As a result, the device drivers 20a,..., 20a depend on the connection conditions to the network 30 having the tree topology.
, It is possible to construct a control system that can autonomously select a predetermined device driver 20a from among them and install it in a predetermined controller 10 (controller-side processor 101). You can build a network system.

On the other hand, the controller-side processing steps executed by the controller 10 (controller-side processor 101) include a category recognizing step (step P4) and a device driver determining step (steps P5, P6, P7, P7).
8, and P9), the installation process (step P6A)
→ P6B → P6C → P10). Each of these steps is stored in a medium described below in a state described by a program code generated using a programming language such as Java that can be executed by the controller 10.

The program code describing the controller-side processing steps is read and held in the controller-side memory 102, and is read out and executed by the controller-side processor 101.

The category recognition step (step P4) is performed when the category data 20b specifying the category name is received via the network 30 (step P2 → P
3), controller 10 (controller-side processor 1)
01), the category data 20b registered in advance in the category correspondence table 11 is compared with the category data 20b received from the device-side processor 201 via the network 30 at this time, and the category data 20b is transmitted. This is a step of recognizing an operation (specifically, any one of “device”, “install”, “ignore”, or “user”) corresponding to the category name of the device 20 that has been performed.

Device Driver Determination Step (Step P
5, P6, P7, P8, and P9) are device drivers that are commonly set for the recognized category name when the default setting data 20c is received via the network 30 (step P2 → P3). 20a or the device driver 20a for each device 20 prepared for each device-side processor 201 is stored in the contents of the default setting data 20c (specifically, “device”,
This is a step of deciding, for each category of the device 20, the selection of the operation of whether to install the device itself according to “install”, “ignore”, or “user”.

Installation process (Step P6A → P6)
B → P6C → P10) are “device”, “install”, “install” according to the execution result of the device driver determination process (steps P5, P6, P7, P8, and P9).
This is a step of deciding whether or not to install the device driver 20a in accordance with the operation of "ignore" or "user", and performing an installation operation based on the decision result.

Here, the device 20 (device-side processor 201) can execute the above-described device-side processing step and controller-side processing step, and can execute the device-side processing step or the controller-side processing step depending on the connection conditions to the network 30. Can be performed.

More specifically, the device 20 of the present embodiment
The (device-side processor 201) can simultaneously execute the device-side processing step and the controller-side processing step. Also, on one piece of hardware, a plurality of devices 20,..., 20, a plurality of controllers 10,.
It is also possible to execute processing steps corresponding to 10 at the same time. In addition, the device 20 (device-side processor 201) of the present embodiment can function as a device for a higher-level device and can function as a controller for a lower-level device.

That is, since the device 20 (device-side processor 201) has the function of executing the device-side processing step and the controller-side processing step, the devices connected to the network 30 play the role of the device 20. Controller 10 (controller processor 10
Both roles as 1) can be satisfied simultaneously. For example, for a device having a higher control right than the device itself, the device is regarded as the controller 10 and the device 20 is set as the device 20. It is possible to autonomously realize a flexible connection mode in which the device is regarded as the device 20 and the device itself is set in the controller 10 (controller-side processor 101). In other words, by having the functions of the device 20 and the controller 10 at the same time, it is possible to realize a controller 10 and device 20 device (a device for one and two roles) in which several devices 20 are collectively operated as one device 20. Become like As a result, a network 30 and a control system having a tree topology can be constructed, and an autonomous network system having advanced man-machine interface can be constructed.

Each of these steps includes a program code of the device driver 20a necessary for controlling itself,
Category data 20b indicating a category to which the user belongs;
Default setting data 20c for transmitting the device driver 20a to the controller 10 (controller processor 101) and instructing the destination controller 10 to instruct whether to instruct the controller 10 to install the device driver 20a, and the controller 10 (controller side). A program code for transmitting the category data 20b and the default setting data 20c from the processor 101) to the inquiring controller 10 in response to a command for inquiring of a category name (step P2) via the network 30; ), A program code for returning category data 20b specifying its own category to the controller 10 of the inquiry source in response to the request of the inquiry source from the device 20. And the device-side program code executed is incorporated seen, when receiving the category data 20b via the network 30 (step P2 →
P3), controller 10 (controller-side memory 10)
The category data 20b registered in advance in the category correspondence table 11 prepared in 2) is compared with the category data 20b received from the device 20 via the network 30, and the category data 20b is transmitted. When the category recognition program code for recognizing the operation corresponding to the category name of the device 20 and the default setting data 20c are received via the network 30 (step P2 → P3), they are commonly set for the recognized category name. Device driver 20a, or the individual device driver 20a prepared for each device 20, the default setting data 20c.
Of the device 2 (specifically, any of “device”, “install”, “ignore”, and “user”).
0, and a program code for determining whether to install the device driver 20a according to the execution result of the device driver determination program code, and performing an installation operation based on the determination result. Are recorded on the above-described medium as controller-side processing program code read and executed by the controller 10.

The following is a specific example.

For example, consider a case where a certain device B (20) is connected to the network 30 to which a certain controller 10 (controller processor 101) is connected.

The controller 10 (controller-side processor 101) already connected to the network 30
In order to control the device B (20), it is necessary to read a device driver 20a for the device B (20) into a memory inside the controller 10 and make it available from a program on the controller 10 system. However, if there is no need to control the device B (20), there is no need to acquire the device driver 20a.

First, the controller 10 (controller processor 101) acquires the category data 20b from the device B (20) via the network 30 (step P2 → P3).

The controller 10 (controller-side processor 101) converts the acquired category data 20b into
Referring to the setting for each category, the device driver 20a
The operation related to the installation of the server (step P
4). If it is necessary to refer to the connection setting in the device B (20), this is also referred to and the operation is determined accordingly.

When the operation determined by the above operation is the setting of “install” (step P6), the controller-side processing step executes a step of requesting a device driver from the user (step P6A), Executes the step of loading the device driver 20a from the floppy disk (Step P6B), and the controller-side processing step executes the step of installing the loaded device driver 20a (Step P6C).

When it is determined that the device driver 20a of the device B (20) is to be installed in the controller 10 (controller processor 101) (“device” setting, step P7), the device B
The device driver 20a incorporated in (20) is read through the network 30, and the device driver 20a is set up in a usable state (steps P7 → P7A → P7B).

If it is determined not to install the device driver 20a of the device B (20) in the controller 10 (controller processor 101) ("ignore" setting, step P5), the device driver 20a is not installed. , Controller 10
The initialization work for the device B (20) is ended (step P5 → P10).

If it is determined to ask the user whether to install the device driver 20a of the device B (20) in the controller 10 (controller processor 101) ("user" setting, step P8), the controller 10 Waiting for a user instruction through the controllable user interface (step P8)
A). In response to this result, the controller 10 performs a predetermined operation such as installing the device driver 20a of the device B (20) (Step P8A → P8B →
P5).

If the category does not exist in the category correspondence table 11 (step P9), an error message is displayed on a CRT or the like, and the initialization is completed (step P9A → P10).

The above operation is performed on all the controllers 10
The (controller-side processor 101) repeats the process for all the devices 20, whereby the initialization work of all the controllers 10 is completed semi-automatically (autonomously) (step P10).

As described above, according to the present embodiment, the device 20 (the device to be controlled) has the category data 20b relating to the own device 20 and the setting relating to the connection of the own device 20, and the controller 10 (the control device). Device 20) for each device category.
The controller 10 has a device driver 20a of the device 20 in accordance with a combination of the setting of the device 20 and the setting of the controller 10.
(Steps P4 to P4)
10), the setting for each category can be executed on the controller 10 side, and the control for handling only a specific category or the control for uniformly handling a specific category can be set and handled on the controller 10 side. Only the device driver 20a of the device 20 belonging to the category can be automatically (autonomously) installed in the controller 10 (controller processor 101).

Further, since the setting for the connection for each category (that is, the setting of the “installation” operation) on the controller 10 (controller-side processor 101) becomes possible, it is particularly important even within the same category. When the device driver 20a for controlling the device-side processor 201 having a role is installed, a setting that always requires a user's instruction (that is, a setting of the “user” operation) is possible. As for the device 20, the step of installing the device driver 20a in the suitable controller 10 (controller-side processor 101) automatically (independently) (ie, the step of installing according to the setting of the "device" operation) enables the network Device 20 is connected on 30 To come, the device driver 20 to which controller 10 is required to control the device 20
a can be determined almost automatically (autonomously) and the number of manual operations can be reduced, so that the user-side installation work required for installing the device driver 20a can be reduced. Become.

FIG. 6 is a flowchart for explaining one embodiment of the network control method according to claims 3 and 12 of the present invention. Note that the same parts as those already described in the above embodiment are denoted by the same reference numerals, and redundant description will be omitted.

In the network control method of the present embodiment, as shown in the portion surrounded by the dashed line in FIG.
In addition to the above-described embodiment, the controller-side processing step executes the category recognition step (step P4), and the category indicated by the category data 20b received by the controller 10 is the controller 10 (controller-side processor 101). Correspondence table 1 prepared in Japan
1 is not registered, the device driver determination step (steps P5, P6, P7, P8, and P
9) is characterized in that it has a step of automatically (autonomously) instructing a new setting of the device driver 20a and a step of automatically (autonomously) generating an entry for the new setting. Have.

Here, generating an entry for a new setting means creating a task portion that can be called from another task. In particular,
This means that a setting request for a new setting and a display for the request are made on an OS such as Windows or Unix.

That is, the controller-side processing steps (steps P2, P4, P5,..., P9) are basically performed by the device-side processor 2 connected to the network 30.
When at least one or more controllers 10 (controller-side processors 101) are designated from 01, an address on the network 30 of the device driver 20a specified by the device 20 is accessed (step P
2) Step of collecting device drivers 20a (steps P6 → P6A → P6B → P6C → P10, P7 → P7A)
→ P7B → P5, P8 → P8A → P8B → P5, P9 →
P9B → P9C → P9D → P5), a step of installing the collected device driver 20a in the designated controller 10 (controller processor 101), and a category recognition step (step P4). When the category indicated by the data 20b is not registered in the category correspondence table 11 prepared in the controller 10 (controller memory 102), the device driver determination step (steps P5, P6, P7, P8, and When P9) is executed, a step of automatically (independently) instructing a new setting of the device driver 20a and a step of automatically (independently) generating an entry for the new setting are included.

The controller-side processing steps executed by the controller 10 (controller-side processor 101) include a category recognizing step (step P4) and a device driver determining step (steps P5, P6, P7, P7).
8, and P9), the installation process (step P6A)
→ P6B → P6C → P10), the category recognition step (step P4) is executed, and the category indicated by the category data 20b received by the controller 10 is the controller 1
0 in the category correspondence table 11 prepared in the controller memory 102 (step P5, P6, P7,
When P8 and P9) are executed, the device driver 2
The logical configuration is centered on a step of automatically (autonomously) instructing a new setting of 0a and a step of automatically (autonomously) generating an entry for the new setting. Each of these steps is performed by Java executable by the controller 10.
Is stored in a medium described below in a state described by a program code generated using a programming language such as.

The program code describing the controller-side processing steps is read and held in the controller-side memory 102, and is read out and executed by the controller-side processor 101.

A category recognition step (step P4)
When the category indicated by the category data 20b received by the controller 10 is not registered in the category correspondence table 11 prepared in the controller 10 (controller side memory 102), the device driver determining step (step When P5, P6, P7, P8, and P9) are executed, a step of automatically (independently) instructing a new setting of the device driver 20a, and an entry for the new setting is automatically (independently). It has a logical configuration centering on the generation process. Each of these steps is stored in a medium described below in a state described by a program code generated using a programming language such as Java that can be executed by the controller 10.

Such a program code is stored in the controller-side memory 102 or the device-side processor 201.

In each of these steps, the category designated by the category data 20b received by the controller 10 by executing the category
When the device driver determination program code is executed in a case where it is not registered in the category correspondence table 11 prepared in the (controller side memory 102), a new setting of the device driver 20a is automatically (independently) instructed. And a program code for automatically (autonomously) generating an entry for a new setting are recorded on the above-described medium as a controller-side processing program code.

Hereinafter, specific examples will be described.

For example, consider a case where a certain device B (20) is connected to the network 30 to which a certain controller 10 (controller processor 101) is connected.

Controller 10 (controller-side processor 101) already connected to network 30
In order to control the device B (20), it is necessary to read a device driver 20a for the device B (20) into a memory inside the controller 10 and make it available from a program on the controller 10 system. However, if there is no need to control the device B (20), there is no need to acquire the device driver 20a.

First, the controller 10 sends the device B (2
0) via the network 30 to the category data 20b
(Step P2 → P3).

The controller 10 (controller-side processor 101) converts the acquired category data 20b into
Referring to the setting for each category, the device driver 20a
The operation related to the installation of the server (step P
4). If it is necessary to refer to the connection setting in the device B (20), this is also referred to and the operation is determined accordingly.

If the determined operation is the setting of “install” (step P6) by the above operation, the controller-side processing step executes a step of requesting a device driver from the user (step P6A), Executes the step of loading the device driver 20a from the floppy disk (Step P6B), and the controller-side processing step executes the step of installing the loaded device driver 20a (Step P6C).

If it is determined that the device driver 20a of the device B (20) is to be installed in the controller 10 (controller processor 101) (“device” setting, step P7), the device B
The device driver 20a incorporated in (20) is read through the network 30, and the device driver 20a is set up in a usable state (steps P7 → P7A → P7B).

If it is determined not to install the device driver 20a of the device B (20) in the controller 10 (setting "ignore", step P5), the device B of the controller 10 is not installed without installing the device driver 20a. The initialization work related to (20) is completed (step P5 → P10).

When it is determined to inquire the user whether to install the device driver 20a of the device B (20) in the controller 10 (controller-side processor 101) (“user” setting, step P8), Waiting for a user instruction through the controllable user interface (step P8)
A). In response to this result, the controller 10 performs a predetermined operation such as installing the device driver 20a of the device B (20) (Step P8A → P8B →
P5).

If the category is not in the category correspondence table 11 (step P9), a step of inquiring the user of an operation corresponding to this category to automatically (independently) generate an entry for a new setting (step P9) P9
Execute B). In response to the inquiry about the operation, the user selects one of “install”, “device”, and “ignore” from a keyboard or the like, and returns it to the controller 10 via the network 30 (step P9C).
Controller 10 (controller-side processor 101)
Responds to this by registering the category and the corresponding operation in the category correspondence table 11 (step P9).
D), repeat the initialization work (step P9D → P
5).

The above operation is performed for all the controllers 10
(The controller-side processor 101) repeats for all the device-side processors 201,
The initialization work of all the controllers 10 is completed semi-automatically (step P10).

As described above, according to the present embodiment, it is determined that the device 20 is unknown to the controller 10 (controller processor 101) because it is not registered in the category correspondence table 11. Also,
By executing a process for automatically (autonomously) creating an entry for a new category, the expansion of the connection device 20 in the future can be performed with minimum extra effort on the user side required for installing the device driver 20a. To be able to respond flexibly.

FIG. 7 is a flowchart for explaining one embodiment of the network control method according to claims 4 and 13 of the present invention. Note that the same parts as those already described in the above embodiment are denoted by the same reference numerals, and redundant description will be omitted.

In the network control method shown in FIG. 7, the device-side processing performed by the device-side processor 201 and the controller-side processing performed by the controller 10 (controller-side processor 101) (steps Q2, P4 , P5,..., P9).

In the device-side processing step, basically, at least one or more controllers 10 for controlling the device 20 are connected to the network 30 based on the timing designated by the user, the device 20 or the controller 10. It includes a step of determining from the controller 10 and a step of instructing the controller 10 on an address on the network 30 of the device driver 20a necessary for controlling the device 20.

The controller-side processing step (step Q
1, Q2, P4, P5,..., P9) are a device detection step (step Q1) for detecting that the new device 20 is connected to the network 30 when the new device-side processor 201 is connected. At least one controller 10 (controller-side processor 10)
When 1) is designated, the address of the device driver 20a specified by the device 20 on the network 30 is accessed, and the category data 20b and the default setting data 20c are assigned to the newly connected device 20.
Setting requesting process for requesting (Step Q2)
(Steps P6 → P6A → P6B → P6C → Q10, P7 → P7A)
→ P7B → P5, P8 → P8A → P8B → P5, P9 →
P9A → Q10) and collected device driver 20a
Is installed in the designated controller 10, and the category indicated by the category data 20b received by the controller 10 by executing the category recognition step (Step P4) is a category prepared in the controller 10 (controller memory 102). When the device driver determination process (steps P5, P6, P7, P8, and P9) is executed when the device processor 20 is not registered in the correspondence table 11, the newly connected device-side processor 20
A step of deciding whether or not to install the first device driver 20a on the controller 10 side at the time of connection of a new device 20 and automatically (autonomously) instructing a new setting of the device driver 20a; Automatically (independently) generating entries.

By providing a device-side processing step and a controller-side processing step, when the device-side processor 201 is connected to the network 30, which controller 10 (controller-side processor 101) is required to control the device 20. Device driver 20
a can be almost automatically determined, and the number of manual operations can be reduced.
It is possible to reduce the labor required for the installation work on the user side necessary for the installation of a. In particular, it is considered that the effect is great when many different types of devices 20 and many different types of controllers 10 are connected on the network 30.

Each of these steps is performed by the user and the device 2.
0 or a program code for determining at least one or more controllers 10 that control the device 20 from among the controllers 10 connected to the network 30 based on the timing specified by the controller 10 and a device for controlling the device 20 Device-side processing program code including a program code for instructing the controller 10 on an address of the device driver 20a required on the network 30 for the device driver 20a; The program code for accessing the address of the device driver 20a specified by the device 20 on the network 30 (step Q2) and collecting the device driver 20a, and the collected device driver 20a It is recorded on the aforementioned medium as a device side processing program code and the controller-side processing program code and a program code to be installed on the named controller 10.

This will be described in more detail.

The device-side processing executed by the device-side processor 201 includes a device driver 20a necessary for controlling itself, category data 20b indicating a category to which the device belongs, and a device driver 20a.
a to the controller 10 (the controller processor 10
1) and instructs the destination controller 10 to instruct the controller 10 to install the device driver 20a (specifically, “device”, “install”,
The default setting data 20c for “ignore” or “user” can be transmitted and received.

In the device-side processing step, the controller 10 (controller-side processor 101) inquires of a category name via the network 30 (step Q).
The controller 10 which inquires of the category data 20b specifying its own category name in response to the command of 2)
Device category return process (Step P3)
have. These steps are stored in a medium described later in a state described by a program code generated using a programming language such as Java which can be executed by the device-side processor 201.

[0146] Such a program code is held in the device-side processor 201.

Further, in the device-side processing step, the device driver 20a to be controlled can be executed, and the device driver 20a,
, 20a can be executed.

That is, by having the functions of the device-side processor 201 and the controller 10 at the same time, the controller 10 and the device 20 (one for two roles), which collectively operate several devices 20 as one device 20. Equipment) can be realized. As a result, the device drivers 20a,..., 20a depend on the connection conditions to the network 30 having the tree topology.
, It is possible to construct a control system that can autonomously select a predetermined device driver 20a from among the above and install it in the predetermined controller 10, and can construct an autonomous network system with advanced man-machine interface. become.

On the other hand, the controller-side processing steps executed by the controller 10 (controller-side processor 101) include a category recognizing step (step P4) and a device driver determining step (steps P5, P6, P7, P
8, and P9), the installation process (step P6A)
→ P6B → P6C → Q10), the category recognition step (step P4) is executed, and the category indicated by the category data 20b received by the controller 10 is the controller 1
0 in the category correspondence table 11 prepared in the controller memory 102 (step P5, P6, P7,
When P8 and P9) are executed, the device driver 2
The logical configuration is centered on a step of automatically (autonomously) instructing a new setting of 0a and a step of automatically (autonomously) generating an entry for the new setting. Each of these steps is performed by Java executable by the controller 10.
Is stored in a medium described below in a state described by a program code generated using a programming language such as.

Such a program code is held in the controller-side memory 102.

The category recognition step (step P4) is performed when the category data 20b specifying the category name is received via the network 30 (step Q2 → P
3), controller 10 (controller-side memory 10)
The category data 20b registered in advance in the category correspondence table 11 prepared in 2) is compared with the category data 20b received from the device-side processor 201 via the network 30 at this time, and the category data 20b is transmitted. This is a step of recognizing an operation (specifically, any one of “device”, “install”, “ignore”, or “user”) corresponding to the category name of the device 20 that has been performed.

Device Driver Determination Step (Step P
5, P6, P7, P8, and P9) are device drivers that are commonly set for the recognized category name when the default setting data 20c is received via the network 30 (step Q2 → P3). 20a or the device driver 20a for each device 20 prepared for each device-side processor 201 is stored in the contents of the default setting data 20c (specifically, “device”,
An operation to be installed by itself according to “install”, “ignore” or “user”) is determined for each category of the device 20, and the device driver 20a of the newly connected device 20 is determined by the controller. This is a step of determining whether or not to install on the side of the controller 10 (controller-side processor 101) when a new device 20 is connected.

Installation process (Step P6A → P6)
B → P6C → Q10) correspond to “device”, “install”, “install” according to the execution result of the device driver determination process (steps P5, P6, P7, P8, and P9).
This is a step of deciding whether or not to install the device driver 20a in accordance with the operation of "ignore" or "user", and performing an installation operation based on the decision result.

On the other hand, a category recognition step (step P4)
When the category indicated by the category data 20b received by the controller 10 is not registered in the category correspondence table 11 prepared in the controller 10 (controller memory 102), the device driver determining step (step When P5, P6, P7, P8, and P9) are executed, a step of automatically (independently) instructing a new setting of the device driver 20a, and an entry for the new setting is automatically (independently). The logical configuration is centered on the step of generating and the step of determining whether or not to install the device driver 20a of the newly connected device-side processor 201 on the controller 10 when the new device 20 is connected. Each of these steps is performed by Java executable by the controller 10.
Is stored in a medium described below in a state described by a program code generated using a programming language such as.

Such a program code is held in the controller-side memory 102.

Here, the device 20 (device-side processor 201) can execute the above-described device-side processing step and controller-side processing step. Can be performed.

That is, since the device 20 (device-side processor 201) has a function of executing the device-side processing step and the controller-side processing step, the devices connected on the network 30 play the role of the device 20. Controller 10 (controller processor 10
Both roles as 1) can be satisfied simultaneously. For example, for a device having a higher control right than itself, the device is regarded as the controller 10 and the device 20 is set to the device 20. It becomes possible to autonomously realize a flexible connection form in which the device is regarded as the device 20 and the device itself is set in the controller 10. In other words, by having the functions of the device 20 and the controller 10 at the same time, the controller 10 and the device 20 (a device that plays two roles) that collectively operates several device-side processors 201 as one device 20 It can be realized. As a result, a network 30 and a control system having a tree topology can be constructed, and an autonomous network system having advanced man-machine interface can be constructed.

Each of these steps includes a program code of the device driver 20a necessary for controlling itself,
Category data 20b indicating a category to which the user belongs;
Default setting data 20c for transmitting the device driver 20a to the controller 10 (controller processor 101) and instructing the destination controller 10 to instruct whether to instruct the controller 10 to install the device driver 20a, and the controller 10 (controller side). A program code for transmitting the category data 20b and the default setting data 20c from the processor 101) to the query source controller 10 in response to a command for a category name inquiry (step Q2) via the network 30; ), A program code for returning category data 20b specifying its own category to the controller 10 of the inquiry source in response to the request of the inquiry source from the device 20. And the device-side program code executed is incorporated seen, when receiving the category data 20b via the network 30 (Step Q2 →
P3), controller 10 (controller-side memory 10)
The category data 20b registered in advance in the category correspondence table 11 prepared in 2) is compared with the category data 20b received from the device processor 201 via the network 30 at this time, and the category data 20b is transmitted. A category recognition program code for recognizing an operation corresponding to the category name of the device 20
When the default setting data 20c is received via the network 30 (step Q2 → P3), a device driver 20a commonly set for the recognized category name or a device prepared for each device-side processor 201 20 individual device drivers 20a
Is the content of the default setting data 20c (specifically,
A device driver determination program code for determining, for each category of the device-side processor 201, the selection of an operation to install itself according to “device”, “install”, “ignore” or “user”; A program code for determining whether or not to install the device driver 20a according to the execution result of the device driver determination program code and performing an installation operation based on the determination result;
A device 20 detection program code for detecting that a new device 20 is connected to the network 30 at the time of connection, a program code for requesting category data 20b and default setting data 20c to the newly connected device 20, and a device driver And a program code for determining whether or not to install the device driver 20a of the newly connected device 20 on the side of the controller 10 (controller-side processor 101) when the new device 20 is connected. The side processing program code is recorded on the medium as the controller side processing program code read and executed by the controller 10.

The following is a specific example.

For example, consider a case where a certain device B (20) is connected to the network 30 to which a certain controller 10 is connected.

The controller 10 (controller processor 101) already connected to the network 30
In order to control the device B (20), it is necessary to read a device driver 20a for the device B (20) into a memory inside the controller 10 and make it available from a program on the controller 10 system. However, if there is no need to control the device B (20), there is no need to acquire the device driver 20a.

First, the controller 10 sets the device B (2
0) via the network 30 to the category data 20b
(Step Q2 → P3).

The controller 10 (controller-side processor 101) converts the acquired category data 20b into
Referring to the setting for each category, the device driver 20a
The operation related to the installation of the server (step P
4). If it is necessary to refer to the connection setting in the device B (20), this is also referred to and the operation is determined accordingly.

If the operation determined by the above operation is the setting of “install” (step P6), the controller-side processing step executes a step of requesting a device driver from the user (step P6A), and Executes the step of loading the device driver 20a from the floppy disk (Step P6B), and the controller-side processing step executes the step of installing the loaded device driver 20a (Step P6C).

If it is determined that the device driver 20a of the device B (20) is to be installed in the controller 10 (controller-side processor 101) ("device" setting, step P7), the device B
The device driver 20a incorporated in (20) is read through the network 30, and the device driver 20a is set up in a usable state (steps P7 → P7A → P7B).

If it is determined not to install the device driver 20a of the device B (20) in the controller 10 (“ignore” setting, step P5), the controller 10 (controller side) is installed without installing the device driver 20a. The initialization work for the device B (20) of the processor 101) ends (step P5 → Q10).

When it is determined to inquire the user whether to install the device driver 20a of the device B (20) in the controller 10 (“user” setting, step P8), the controller 10 (controller processor 101) Waiting for a user instruction through the controllable user interface (step P8)
A). In response to this result, the controller 10 performs a predetermined operation such as installing the device driver 20a of the device B (20) (Step P8A → P8B →
P5).

If the category does not exist in the category correspondence table 11 (step P9), an error message is displayed on the CRT or the like, and the initialization is completed (step P9A → Q10). 101) are all device-side processors 20
By repeating the above operation, the initialization work of all the controllers 10 is completed semi-automatically (step Q10).
I do.

The network control method according to the present embodiment includes a device detecting step (step Q1) for detecting that a new device 20 is connected to the network 30 when a new device 20 is connected, and a device detecting step (step Q1).
A default setting requesting step (step Q2) for requesting category data 20b and default setting data 20c for 0, and a device driver determining step (step P
5, P6, P7, P8, and P9), and determines whether or not to install the device driver 20a of the newly connected device 20 on the controller 10 (controller processor 101) side.
This is a network control method determined at the time of connection.

As described above, according to the present embodiment, the device 20 (the device to be controlled) has the category data 20b relating to the own device 20 and the settings relating to the connection of the own device 20, and the controller 10 (the control device). Device 20) for each device category.
Determining whether the controller 10 acquires the device driver 20a of the device 20 according to a combination of the setting on the device 20 side and the setting on the controller 10 (controller processor 101) side. By executing (steps P4 to Q10), the setting for each category is performed by the controller 1.
The controller 1 can execute control that handles only a specific category or control that handles a specific category in a unified manner.
Device 20 that can be set on the 0 side and belongs to the category to be handled.
Only the device driver 20a can be automatically installed in the controller 10.

In addition, since the setting for the connection for each category (that is, the setting of the “installation” operation) on the controller 10 (controller-side processor 101) side becomes possible, even in the same category, it is particularly important. When installing the device driver 20a for controlling the device-side processor 201 having a role, a setting that always requires a user's instruction (that is, a setting of a “user” operation) can be performed. For the device 20 the automatically suitable controller 10
By performing the step of installing the device driver 20a on the network 30 (that is, the step of installing according to the setting of the “device” operation), when the device 20 is connected to the network 30,
0 can acquire the device driver 20a required for controlling the device 20 almost automatically, and the number of manual operations can be reduced. The required labor can be reduced. In addition, the controller-side processing step is a new device 2
0, the connection of the new device 20 to the network 30 can be detected, and the installation of the device driver 20a can be executed in synchronization with the connection of such a new device 20 to the network 30. As a result, after connecting the new device 20 to the network 30, the user can save the labor of instructing the controller 10 to install the device driver 20a required for controlling the new device 20. An autonomous network system with machine interface can be constructed.

FIG. 8 is a flowchart for explaining one embodiment of the network control method according to claims 5 and 14 of the present invention. FIG. 9 is a chart for explaining an example of various data used in the embodiment shown in FIG. 8. FIG. 9A shows a controller-side processing step executed by the controller 10 (controller-side processor 101). Is an embodiment corresponding to the categories A, B, C, D,... Registered in the category correspondence table 11 in advance, and installations corresponding to these category names. ,
FIG. 9 is a table for explaining operations such as ignore,.
FIG. 9B is a table for explaining an example of device ID data and category data transmitted by the device 20 and an operation corresponding to the data. FIG. 11 is a chart for explaining a correspondence relationship between device ID data 20d stored in a past connection status table and past connection status data. Note that the same parts as those already described in the above embodiment are denoted by the same reference numerals, and redundant description will be omitted.

The network control method shown in FIG. 8 includes a device-side process executed on the device 20 side and a controller-side process executed on the controller 10 (steps R1 to R5, P2, P4, P5,...). , P9)
It has a logical configuration centered on.

The network control method of the present embodiment has the functions of the embodiment of the network control method shown in FIG. 5, and furthermore, the individual device-side processors 201 on the network 30 are directed to the controller 10 (controller-side processor 101). To send (unique ID)
The connection history storing step (step R6) for storing the correspondence between the device ID data 20d, which is the past, and the past connection state data as a past connection state table, and the device detection step (step P1). (Steps R1 → R2 → R3 → R4, R4 → R4-1 → R10, R10)
4 → R5) and device 2 that has been connected in the past
When it is determined that 0 has been connected again (step R4), a past connection state calling step (step R4-1) for calling the past connection state data 10a of the device 20 stored in the connection history storage step (step R6).
And a resume step (Step R4-1) for reproducing a past controllable state of the device 20 based on the called connection state data 10a.

The category correspondence table 11 shown in FIG.
For each category of the device 20, control information of the device-side processor 201 or information relating to the setting relating to the installation of the device driver 20a is described. The category data 20b, which is held in the means and specifies a category, and the operation corresponding to the category name are described.

Specifically, in the category correspondence table 11,
A plurality of categories identified by A, B, C, D,... Are stored, and the control information of the controller 10 (controller processor 101) or the operation of installing the device driver 20a corresponding to each category is described. Have been.

In the following embodiment, for example, FIG.
As shown in (1), in the category A, the user is requested to input control information or data of the device driver 20a (for example, input of data using a floppy disk), and the control information of all the devices 20 or the device driver 20a is transmitted. The operation of “install” to be installed corresponds to the category B, and the operation of the “device” according to the setting of the device 20 to which the device 20 has returned is inquired to the device 20 for control information or the operation of installing the device driver 20a. Correspondingly, the category C includes the control information of the device 20 or the device driver 2
Ask the user whether to install 0a or not, and select "Install", "Device", or "Ignore"
Corresponds to the operation of the "user" according to the operation selected by the user, and the category D corresponds to the operation of "ignore" in which the control information of all the devices 20 or the device driver 20a is not installed.

Here, each of the devices 20 (device-side processor 201) includes data 20b representing a category to which the own device 20 belongs, and control information of the own device 20 or the controller 10 (controller-side processor 101) of the device driver 20a. And data indicating settings related to installation on the network 30 (always install / not always install / inquire the user whether or not to install), and these can be transmitted to the controller 10 on the network 30 through the interface.

Similarly, all the controllers 10 (controller-side processors 101) set the control information of the device 20 or the setting relating to the installation of the device driver 20 a (“device” according to the setting of the device 20) for each category of the device 20. Setting, "install" setting for installing control information of all devices 20 or device driver 20a, "ignore" setting for not installing control information of all devices 20 or device driver 20a, control information or device of device 20 It has data indicating "user" for asking the user whether or not to install the driver 20a, and these data can be referred to from a program on the controller 10 system.

As will be described later, the device 20 (device-side processor 201) executes the category recognition step (step P).
According to the execution of 4), as shown in FIG. 9B, the category data 20b specifying the above-described category and operation can be transmitted. When the controller 10 (controller-side processor 101) executes the controller-side processing step, the controller 10 (the controller-side processor 101) receives the category data 20b registered in advance in the category correspondence table 11 and the device 20 from the device 20 via the network 30. A category recognizing step (step P4) for comparing the category data 20b with the category data 20b and recognizing an operation corresponding to the category name of the device 20 that has transmitted the category data 20b is executed.

On the other hand, in the past connection status table 11 shown in FIG. 9C, connection statuses identified by device IDs are stored. Of the past installation of the device driver 20a.

For example, as shown in FIG. 9C, the device ID = 2063 stores that the setting of the installation operation of the device driver 20a of the device 20 is "installed".

In the device-side processing step, basically, at least one or more controllers 10 for controlling the device 20 are connected to the network 30 based on the timing specified by the user, the device 20 or the controller 10. It includes a step of discriminating from the controller 10 and a step of instructing the controller 10 on an address on the network 30 of the device driver 20a necessary for controlling the device 20.

The controller-side processing steps of this embodiment are as follows:
A step (step R1) of inquiring the device 20 of device ID data 20d, which is an identifier (unique ID) transmitted by each device 20 on the network 30 toward the controller 10, and searching the past connection status table 11 For retrieving the connection status (step R)
3) and if a connection has been made before (step R
4) Step of reproducing past controllable state (step R)
4-1) to complete the initial setting (step P
10).

If no connection has been made before (step R4 → R5), a step of inquiring the designated device 20 about the category name is executed (step P2).
It is characterized by points.

The controller-side processing step (step R)
1 to R5, P2, P4, P5,..., P9) basically determine whether or not the device-side processor 201 has been connected in the past when the device detection step (step P1) was executed. Judgment process (step R1 → R2 → R3
→ R4, R4 → R4-1 → R10, R4 → R5) and when it is determined that the device 20 which has been connected in the past has been connected again (step R4), it is stored in the connection history storing step (step R6). Device 20
A past connection state calling step (step R4-1) for calling the past connection state data 10a of the device 20 and a resume step (step R4-) for reproducing the past controllable state of the device 20 based on the called connection state data 10a.
1) and the device 20 connected on the network 30
Device driver 2 specified by the device 20 when at least one or more controllers 10 are designated by
0a on the network 30 (step P2) to collect the device driver 20a (step P6 → P6A → P6B → P6C → P10,
P7 → P7A → P7B → P5, P8 → P8A → P8B →
P5, P9 → P9A → P10), and installing the collected device driver 20a in the designated controller 10.

By providing the device-side processing step and the controller-side processing step, when the device 20 is connected to the network 30,
The device driver 20 required by the (controller processor 101) to control the device processor 201
a can be determined almost automatically (autonomously) and the number of manual operations can be reduced, so that the user-side installation work required for installing the device driver 20a can be reduced. Become.
In particular, many different types of devices 20 and many different types of controllers 10,.
It is considered that the effect is great when a large number are connected above.

[0188] These steps are performed by the user and the device 2.
0 or a program code for determining at least one controller 10 controlling the device 20 from the controllers 10 connected to the network 30 based on the timing designated by the controller 10 and controlling the device-side processor 201 Device-side processing program code including a program code for instructing the controller 10 of an address of the device driver 20a on the network 30 necessary for performing the operation, and at least one of the devices 20 connected on the network 30
When one or more controllers 10 are designated, the address of the device driver 20a specified by the device 20 on the network 30 is accessed (step P2).
The medium described above as a device-side processing program code and a controller-side processing program code including a program code for collecting the device driver 20a and a program code for installing the collected device driver 20a in the designated controller 10 (controller-side processor 101). Recorded above.

A more detailed description will be given.

The device-side processing steps executed by the device-side processor 201 include a device driver 20a necessary for controlling itself, category data 20b indicating a category to which the device belongs, and a device driver 20a.
a to the controller 10 (the controller processor 10
1) and instructs the destination controller 10 to instruct the controller 10 to install the device driver 20a (specifically, “device”, “install”,
The default setting data 20c for “ignore” or “user” can be transmitted and received.

In the device-side processing step, the controller 10 (controller-side processor 101) inquires of the category name via the network 30 (step P
The controller 10 which inquires of the category data 20b specifying its own category name in response to the command of 2)
Device category return process (Step P3)
have. Each of these steps is stored in a medium described below in a state described by a program code generated by using a programming language such as Java which can be executed by the device 20.

[0192] Such a program code is held in the device-side processor 201.

In the device-side processing step, the device driver 20a to be controlled can be executed, and the device driver 20a,
, 20a can be executed.

That is, by having the functions of the device 20 (device-side processor 201) and the controller 10 (controller-side processor 101) at the same time, the controller 10 is capable of operating several devices 20 as one device 20 collectively. The device of the device 20 (a device that plays two roles) can be realized. As a result, the device drivers 20a,..., 20a depend on the connection conditions to the network 30 having the tree topology.
, It is possible to construct a control system that can autonomously select a predetermined device driver 20a from among the above and install it in the predetermined controller 10, and can construct an autonomous network system with advanced man-machine interface. become.

On the other hand, the controller-side processing steps executed by the controller 10 (controller-side processor 101) include a category recognition step (step P4) and a device driver determination step (steps P5, P6, P7, P
8, and P9), the installation process (step P6A)
→ P6B → P6C → P10). Each of these steps is stored in a medium described below in a state described by a program code generated using a programming language such as Java that can be executed by the controller 10.

[0196] Such a program code is held in the controller-side memory 102.

The category recognition step (step P4) is performed when the category data 20b specifying the category name is received via the network 30 (step P2 → P
3), controller 10 (controller-side memory 10)
The category data 20b registered in advance in the category correspondence table 11 prepared in 2) is compared with the category data 20b received from the device 20 via the network 30 at this time, and the category data 20b is transmitted. The operation corresponding to the category name of the device 20 (specifically, “device”, “install”, “ignore”,
Or “user”).

Device Driver Determination Step (Step P
5, P6, P7, P8, and P9) are device drivers that are commonly set for the recognized category name when the default setting data 20c is received via the network 30 (step P2 → P3). 20a or a device driver 20a prepared for each device 20 by default setting data 20a.
In response to the content of c (specifically, any one of “device”, “install”, “ignore”, and “user”), the device 2 selects the operation to install itself.
This is a step of determining for each of the 0 categories.

Installation Step (Step P6A → P6)
B → P6C → P10) are “device”, “install”, “install” according to the execution result of the device driver determination process (steps P5, P6, P7, P8, and P9).
This is a step of deciding whether or not to install the device driver 20a in accordance with the operation of "ignore" or "user", and performing an installation operation based on the decision result.

Here, the device 20 (device-side processor 201) can execute the above-described device-side processing step and controller-side processing step. Can be performed.

That is, since the device 20 (device-side processor 201) has a function of executing the device-side processing step and the controller-side processing step, the devices connected on the network 30 play the role of the device 20. Controller 10 (controller processor 10
Both roles as 1) can be satisfied simultaneously. For example, for a device having a higher control right than itself, the device is regarded as the controller 10 and the device 20 is set to the device 20. It becomes possible to autonomously realize a flexible connection form in which the device is regarded as the device 20 and the device itself is set in the controller 10. In other words, the device 10 and the device 20 are devices that have the functions of the device 20 and the controller 10 at the same time so that some devices 20 operate collectively as one device 20 (a device that plays two roles).
Can be realized. As a result, a network 30 and a control system having a tree topology can be constructed, and an autonomous network system having advanced man-machine interface can be constructed.

Each of these steps includes the program code of the device driver 20a necessary for controlling itself,
Category data 20b indicating a category to which the user belongs;
Default setting data 20c for transmitting the device driver 20a to the controller 10 (controller processor 101) and instructing the destination controller 10 to instruct whether to instruct the controller 10 to install the device driver 20a, and the controller 10 (controller side). A program code for transmitting the category data 20b and the default setting data 20c from the processor 101) to the inquiring controller 10 in response to a command for inquiring of a category name (step P2) via the network 30; ) To return the category data 20b specifying the category of the device itself to the controller 10 of the inquiry source in response to the request of the inquiry source from the device 20 ( When the device-side processing program code read and executed by the device-side processor 201) and the category data 20b are received via the network 30 (steps P2 → P3), the controller 10 is prepared in the controller 10 (controller-side memory 102). The category data 20b registered in advance in the category correspondence table 11 is compared with the category data 20b received from the device 20 via the network 30 at this time, and the device 20 that has transmitted the category data 20b is compared.
When a category recognition program code for recognizing an operation corresponding to the category name and default setting data 20c are received via the network 30 (step P2 →
P3), a device driver 20a commonly set for the recognized category name, or a device driver 2 for each device 20 prepared for each device 20
In response to the content of the default setting data 20c (specifically, any one of “device”, “install”, “ignore”, and “user”), the user selects whether or not to install the device 20a. A device driver determination program code determined for each category, a program code for determining whether to install the device driver 20a according to the execution result of the device driver determination program code, and performing an installation operation based on the determination result; A connection history storage program code for storing, as a past connection status table, a correspondence relationship between device ID data 20d, which is an identifier transmitted by each device 20 on the distributed network 30 toward the controller 10, and past connection status data. And the device 20 (device-side processor 01) A program code for determining whether the device 20 has been connected in the past when executing the detection program code, and a program code for determining whether the device 20 having been connected in the past has been connected again. A program code for calling the past connection state data 10a of the device 20 stored in the connection history storage program code, and a program code for reproducing the past controllable state of the device 20 based on the called connection state data 10a, It is recorded on the aforementioned medium as a controller-side processing program code read and executed by the controller 10.

Hereinafter, specific examples will be described.

For example, consider a case where a certain device B (20) is connected to the network 30 to which a certain controller 10 (controller processor 101) is connected.

The controller 10 (controller processor 101) already connected to the network 30
In order to control the device B (20), it is necessary to read a device driver 20a for the device B (20) into a memory inside the controller 10 and make it available from a program on the controller 10 system. However, if there is no need to control the device B (20), there is no need to acquire the device driver 20a.

First, the controller 10 (the controller-side processor 101) acquires the category data 20b from the device B (20) via the network 30 (step P2 → P3).

The controller 10 (controller-side processor 101) converts the acquired category data 20b into
Referring to the setting for each category, the device driver 20a
The operation related to the installation of the server (step P
4). If it is necessary to refer to the connection setting in the device B (20), this is also referred to and the operation is determined accordingly.

If the determined operation is the setting of “install” (step P6) by the above operation, the controller-side processing step executes a step of requesting a device driver from the user (step P6A), Executes the step of loading the device driver 20a from the floppy disk (Step P6B), and the controller-side processing step executes the step of installing the loaded device driver 20a (Step P6C).

When it is determined that the device driver 20a of the device B (20) is to be installed in the controller 10 (controller-side processor 101) (“device” setting, step P7), the device B
The device driver 20a incorporated in (20) is read through the network 30, and the device driver 20a is set up in a usable state (steps P7 → P7A → P7B).

If it is determined not to install the device driver 20a of the device B (20) in the controller 10 (“ignore” setting, step P5), the individual devices 20 on the network 30 are connected to the controller 10 (controller side). A connection history storing step (step R6) for storing the correspondence between the device ID data 20d, which is an identifier (unique ID) transmitted to the processor 101), and the past connection status data as a past connection status table. After executing the step of registering in the past connection status table 11, the device B (2) of the controller 10 is installed without installing the device driver 20a.
0) is completed (step P5 → P1)
0).

If it is determined to ask the user whether to install the device driver 20a of the device B (20) in the controller 10 (controller-side processor 101) ("user" setting, step P8), the controller 10 Waiting for a user instruction through the controllable user interface (step P8)
A). In response to this result, the controller 10 performs a predetermined operation such as installing the device driver 20a of the device B (20) (Step P8A → P8B →
P5).

If the category does not exist in the category correspondence table 11 (step P9), an error message is displayed on a CRT or the like, and the initialization is completed (step P9A → P10).

The above operation is performed on all the controllers 10
The (controller-side processor 101) repeats for all the devices 20 (the device-side processor 201), whereby the initialization work of all the controllers 10 is completed semi-automatically (independently) (step P10).

As described above, according to the present embodiment, the device 20 (device to be controlled) has the category data 20b relating to the own device 20 and the settings relating to the connection of the own device 20, and the controller 10 (the control device). Device 20) for each device category.
The controller 10 has a device driver 20a of the device 20 in accordance with a combination of the setting of the device 20 and the setting of the controller 10.
(Steps P4 to P4)
10), the setting for each category can be executed on the controller 10 side, and the control for handling only a specific category or the control for uniformly handling a specific category can be set and handled on the controller 10 side. Only the device driver 20a of the device 20 belonging to the category can be automatically (autonomously) installed in the controller 10.

[0215] Further, since the setting for the connection for each category (that is, the setting of the "installation" operation) on the side of the controller 10 (controller-side processor 101) becomes possible, even in the same category, it is particularly important. When the device driver 20a for controlling the device 20 having the role is installed, a setting that always requires a user's instruction (that is, a setting of “user” operation) is possible. Automatic (autonomous) for (device-side processor 201)
By installing the device driver 20a in the controller 10 suitable for the device (ie, the installation process according to the setting of the “device” operation)
When the device 20 is connected to the network 30, it is possible to almost automatically (autonomously) determine which controller 10 acquires the device driver 20 a required for controlling the device 20. Since the number of operations can be reduced, the labor required for the installation work on the user side required for installing the device driver 20a can be reduced. In addition, by executing the connection history storage step (step R6), the correspondence between the device ID data 20d and the past connection status data can be stored as a past connection status table.
As a result, when a known device 20 that has been connected in the past is connected on the network 30, the device 20 (device-side processor 201) is recognized based on the device ID data 20d, and the device ID data 20d is recognized. , A past connection status table can be searched, and a past controllable state can be reproduced for a known device 20 that has been connected in the past and has a track record. By doing so, even if a specific setting is limited to only a specific device 20 in the past connection mode, when the device 20 is connected to the network 30 again, the device 20 Driver 2 required to control the
0a does not need to be manually reset each time the device 20 is connected. After the device 20 having a connection record in the past is connected to the network 30, the user can use the controller 10a of the device driver 20a required to control the device 20. This makes it possible to save the labor of instructing the installation on the network and to construct an autonomous network system having advanced man-machine interface.

FIG. 10 is a flowchart for explaining one embodiment of the network control method according to claims 8 and 15 of the present invention. FIG. 11 is a chart for explaining an example of the category data 20b transmitted by the device 20 and the corresponding operation in the flowchart of FIG. Note that the same parts as those already described in the above embodiment are denoted by the same reference numerals, and redundant description will be omitted. The network control method shown in FIG. 10 includes a device-side process executed on the device 20 side and a controller 10 (controller processor 10).
The logic configuration has a controller-side processing step (steps P2, P4, P5,..., P9) executed on the side 1).

[0217] The device-side processing step basically involves connecting at least one or more controllers 10 that control the device 20 (device-side processor 201) to the network 30 based on the timing specified by the user, the device 20, or the controller 10. It includes a step of determining from among the controllers 10 connected above, and a step of instructing the controller 10 on an address on the network 30 of a device driver 20a necessary for controlling the device 20.

The controller-side processing step (step P
, P4, P5,..., P9) are basically at least one device 20 connected to the network 30.
The device driver 20 specified by the device 20 (device-side processor 201) when one or more controllers 10 (controller-side processor 101) are designated
a step of accessing the address on the network 30 (step P2) and collecting the device driver 20a (step P6 → S1 → S2 → P6C → P10, P7)
→ P7A → P7B → P5, P8 → P8A → P8B → P
5, P9 → P9A → P10), and a step of installing the collected device driver 20a in the designated controller 10.

In addition, the network control method of the present embodiment differs from the embodiment of the network control method shown in FIG. 5 in that the category data 20b returned from the device 20 in step P4 is “installed”.
When the operation has been designated (step P6), the device-side processing step includes a step of storing a device driver 20a for controlling itself, and a step of storing the device driver 20a in the controller 10 via the network 30.
(Step S2) of transferring to the (controller-side processor 101), and the controller-side processing step refers to the device driver 20a in response to a device driver request step (step S1); The feature is that a step of controlling the device 20 (device-side processor 201) that has transferred the device driver 20a based on the driver 20a is executed.

By providing the device-side processing step and the controller-side processing step, when the device 20 is connected to the network 30,
Can almost automatically (autonomously) determine whether to acquire the device driver 20a required for controlling the device 20 (device-side processor 201), and can reduce the number of manual operations. The labor required for the user-side installation work required for the operation can be reduced. In particular, the effect is considered to be significant when many different types of devices 20 and many different types of controllers 10 (controller-side processors 101),... In addition, by providing a process for storing the device driver 20a for controlling itself in the device-side processing process, the device driver 20a can be provided inside the device 20. By holding the device driver 20a inside the device 20 (device-side processor 201) in this way, it is not necessary to procure the device driver 20a required for controlling the device 20 from outside, and the device 20 is installed on the network 30. In this case, the autonomous installation work can be performed only with the device driver or the device driver 20a held in the own storage device, and an autonomous network system having advanced man-machine interface can be constructed.

Each of these steps is performed by the user and the device 2
0 or a program code for determining at least one or more controllers 10 that control the device 20 from among the controllers 10 connected to the network 30 based on the timing specified by the controller 10 and a device for controlling the device 20 Device-side processing program code including a program code for instructing the controller 10 on the address of the device driver 20a required on the network 30 for the device 20, and the device 20 (device-side processor 201) connected on the network 30
Device driver 2 specified by the device 20 when at least one or more controllers 10 are designated by
Device-side processing program code including a program code for accessing the address of the network driver 0a on the network 30 (step P2) and collecting the device driver 20a, and a program code for installing the collected device driver 20a in the designated controller 10. And, it is recorded on the above-mentioned medium as a controller-side processing program code.

This will be described in more detail.

The device-side processing performed by the device 20 includes a device driver 20a necessary for controlling itself, category data 20b indicating a category to which the device belongs, and the device driver 20a stored in the controller 10 (controller processor 101). ) To instruct the destination controller 10 to install the device driver 20a (specifically, any one of “device”, “install”, “ignore”, or “user”). ) Can be transmitted and received.

In the device-side processing step, the controller 10 (controller processor 101) inquires of the category name via the network 30 (step P
The controller 10 which inquires of the category data 20b specifying its own category name in response to the command of 2)
Device category return process (Step P3)
have. Each of these steps is stored in a medium described below in a state described by a program code generated by using a programming language such as Java which can be executed by the device 20.

[0225] Such a program code is held in the device-side processor 201.

Further, in the device-side processing step, the device driver 20a to be controlled can be executed, and the device driver 20a,
, 20a can be executed.

That is, by having the functions of the device 20 (device-side processor 201) and the controller 10 (controller-side processor 101) at the same time, the controller 10 can be configured such that several devices 20 operate collectively as one device 20 The device of the device 20 (a device that plays two roles) can be realized. As a result, the device drivers 20a,..., 20a depend on the connection conditions to the network 30 having the tree topology.
, It is possible to construct a control system that can autonomously select a predetermined device driver 20a from among the above and install it in the predetermined controller 10, and can construct an autonomous network system with advanced man-machine interface. become.

On the other hand, the controller-side processing step executed by the controller 10 (controller-side processor 101) is a step of referring to the device driver 20a in accordance with a device driver request step (step S1).
A step of controlling the device 20 that has transferred the device driver 20a based on the referred device driver 20a, a category recognition step (step P4), and a device driver determination step (steps P5, P6, P7, P8,
And P9), installation process (step S1 → S2)
→ P6C → P10). Each of these steps is stored in a medium described below in a state described by a program code generated using a programming language such as Java that can be executed by the controller 10.

[0229] Such a program code is held in the controller-side memory 102.

The category recognition step (step P4) is performed when the category data 20b specifying the category name is received via the network 30 (step P2 → P
3), controller 10 (controller-side memory 10)
The category data 20b registered in advance in the category correspondence table 11 prepared in 2) is compared with the category data 20b received from the device 20 via the network 30 at this time, and the category data 20b is transmitted. The operation corresponding to the category name of the device 20 (specifically, “device”, “install”, “ignore”,
Or “user”).

At this time, the device 20 (device-side processor 201) can transmit the category data 20b designating the category and the operation in accordance with the execution of the category recognition step (step P4). Controller 10
When the controller-side processing step is executed, the (controller-side processor 101) stores the category data 20b registered in advance in the category correspondence table 11 and the category data received from the device 20 via the network 30. 20b and category data 2
A category recognition step (step P4) for recognizing an operation corresponding to the category name of the device 20 that has transmitted 0b is performed. For example, the device 20 (device-side processor 201) performs a category recognition process (step P4).
, The category name "B" as shown in FIG.
Data 20 for specifying the operation and the operation "install"
b can be transmitted. When the controller 10 (controller-side processor 101) executes this controller-side processing step, the category data 20b registered in advance in the category correspondence table 11 and the category name “ Category data 20b designating "B" and operation "install"
And a category recognizing step (step P4) for recognizing the operation “install” corresponding to the category name “B” of the device 20 that has transmitted the category data 20b.

Device Driver Determination Step (Step P
5, P6, P7, P8, and P9) are device drivers that are commonly set for the recognized category name when the default setting data 20c is received via the network 30 (step P2 → P3). 20a or a device driver 20a prepared for each device 20 by default setting data 20a.
In response to the content of c (specifically, any one of “device”, “install”, “ignore”, and “user”), the device 2 selects the operation to install itself.
This is a step of determining for each of the 0 categories.

Installation process (step S1 → S2 →
(P6C → P10) is one of “device”, “install”, “ignore”, or “user” according to the execution result of the device driver determination process (steps P5, P6, P7, P8, and P9). Is a step of deciding whether or not to install the device driver 20a in accordance with the operation described above, and executing an installation operation based on the decision result.

Here, the device 20 (device-side processor 201) can execute the above-described device-side processing step and controller-side processing step. Can be performed.

That is, since the device 20 (device-side processor 201) has a function of executing the device-side processing step and the controller-side processing step, the devices connected on the network 30 have the role of the device 20. Both roles as the controller 10 can be satisfied at the same time. For example, for a device having a higher control right than itself, the device is regarded as the controller 10 and the device 20 is set to the device 20. Consider the device as device 20 and call itself controller 1
A flexible connection mode such as setting to 0 can be realized autonomously. In other words, by having the functions of the device 20 and the controller 10 at the same time, it is possible to realize a controller 10 and device 20 device (a device for one and two roles) in which several devices 20 are collectively operated as one device 20. Become like As a result, a network 30 and a control system having a tree topology can be constructed, and an autonomous network system having advanced man-machine interface can be constructed.

Each of these steps includes the program code of the device driver 20a necessary for controlling itself,
Category data 20b indicating a category to which the user belongs;
The default setting data 20c for transmitting the device driver 20a to the controller 10 and instructing the destination controller 10 to install or not to install the device driver 20a, and the controller 10 (the controller-side processor 101) to transmit the network 30 And a program code for transmitting the category data 20b and the default setting data 20c to the controller 10 of the inquiry source in response to the command of the inquiry of the category name (step P2) via the controller 10 (controller processor 101). Category data 20b that specifies its own category in response to a request
Is returned to the inquiring controller 10, and when the device-side processing program code read and executed by the device 20 and the category data 20b are received via the network 30 (steps P2 → P3 ), Compares the category data 20b registered in advance in the category correspondence table 11 prepared in the controller 10 (controller memory 102) with the category data 20b received from the device 20 via the network 30 at this time. When receiving the category recognition program code for recognizing the operation corresponding to the category name of the device 20 that has transmitted the category data 20b and the default setting data 20c via the network 30 (step P2 → P3), the recognized category Against the name The device driver 20a set as the default or the device driver 20a prepared for each device 20 is stored in the default setting data 20c (specifically, "device", "install", "ignore" Or "user"
), A device driver determination program code that determines, for each category of the device 20, an operation selection of whether to install the device driver itself, and whether to install the device driver 20a according to the execution result of the device driver determination program code. Program code for determining whether or not to perform the installation work based on the determination result, a program code for internally storing a device driver 20a for controlling itself, and the device driver 20a for the controller 10 via the network 30. A device-side processing program code having a program code to be transferred, and a device driver 20a
And a controller-side processing program code having a program code for controlling the device 20 that has transferred the device driver 20a based on the referenced device driver 20a. It is recorded on the medium as the side processing program code.

The following is a specific example.

For example, consider a case where a certain device B (20) is connected to the network 30 to which a certain controller 10 is connected.

Controller 10 (controller-side processor 101) already connected to network 30
In order to control the device B (20), it is necessary to read a device driver 20a for the device B (20) into a memory inside the controller 10 and make it available from a program on the controller 10 system. However, if there is no need to control the device B (20), there is no need to acquire the device driver 20a.

First, the controller 10 sends the device B (2
0) via the network 30 to the category data 20b
(Step P2 → P3).

The controller 10 (controller-side processor 101) converts the acquired category data 20b into
Referring to the setting for each category, the device driver 20a
The operation related to the installation of the server (step P
4). If it is necessary to refer to the connection setting in the device B (20), this is also referred to and the operation is determined accordingly.

If the operation determined by the above operation is the setting of “install” (step P6), the controller-side processing step refers to the device driver 20a in accordance with the device driver requesting step (step P6). Step S1) is performed, and the device-side processing step includes:
Device driver 20a for controlling itself
And the step of transferring the device driver 20a to the controller 10 via the network 30 (step S2), and the controller-side processing step executes the device driver 20a based on the referenced device driver 20a. A step of installing a device driver in the transferred device 20 (step P6
Execute C).

Also, the device B (2
0) is determined to be installed (device setting, step P
7) The device driver 20a incorporated in the device B (20) is read through the network 30, and the device driver 20a is set up in a usable state (step P7 → P7A → P7B).

If it is determined not to install the device driver 20a of the device B (20) in the controller 10 (“ignore” setting, step P5), the device B of the controller 10 is installed without installing the device driver 20a. The initialization work related to (20) is completed (step P5 → P10).

If it is determined to inquire the user whether or not to install the device driver 20a of the device B (20) in the controller 10 (“user” setting, step P8), through the user interface controllable by the controller 10 Wait for an instruction from the user (step P8A). In response to this result, the controller 10 operates the device driver 20a of the device B (20).
Is performed (steps P8A → P8B → P5).

If the category does not exist in the category correspondence table 11 (step P9), an error message is displayed on the CRT or the like, and the initialization is completed (step P9A → P10).

The above operation is performed on all the controllers 10
The (controller-side processor 101) repeats the process for all the devices 20, whereby the initialization work of all the controllers 10 is completed semi-automatically (autonomously) (step P10).

As described above, according to the present embodiment, the device 20 (device to be controlled) has the category data 20b relating to the own device 20 and the setting relating to the connection of the own device 20, and the controller 10 (control device). Device 20) for each device category.
The controller 10 has a device driver 20a of the device 20 in accordance with a combination of the setting of the device 20 and the setting of the controller 10.
(Steps P4 to P4)
10), the setting for each category can be executed on the controller 10 side, and the control for handling only a specific category or the control for uniformly handling a specific category can be set and handled on the controller 10 side. Only the device driver 20a of the device 20 belonging to the category can be automatically (autonomously) installed in the controller 10.

[0249] Also, since the setting for the connection for each category (that is, the setting of the "installation" operation) on the controller 10 side becomes possible, the device 20 having a particularly important role even within the same category can be used. When installation of the device driver 20a for control is performed, a setting that always requires a user's instruction (that is, setting of “user” operation) is possible, and the general device 20 is automatically (independently set). The step of installing the device driver 20a in the controller 10 suitable for the target (that is, the step of installing according to the setting of the “device” operation) enables the network 3
When the device 20 is connected to the device 0, it is almost automatically (independently) which controller 10 acquires the device driver 20a required for controlling the device 20.
Since the number of manual operations can be reduced, the labor required for the installation work on the user side required for installing the device driver 20a can be reduced.

The network control method shown in FIG. 12 includes a device-side processing step executed by the device 20 and a controller-side processing step (steps P2, P4, P5,..., P9) executed by the controller 10. It has a central logical configuration.

In the device-side processing step, basically, at least one or more controllers 10 that control the device 20 are connected to the network 30 based on the timing specified by the user, the device 20 or the controller 10. It includes a step of discriminating from the controller 10 and a step of instructing the controller 10 on an address on the network 30 of the device driver 20a necessary for controlling the device 20.

The controller-side processing step (step P
, P4, P5,..., P9) are basically at least one device 20 connected to the network 30.
When one or more controllers 10 are designated, the address of the device driver 20a specified by the device 20 on the network 30 is accessed (step P2).
Step of Collecting Device Drivers 20a (Step P6)
→ P6A → P6B → P6C → P10, P7 → P7A → P
7B → P5, P8 → P8A → P8B → P5, P9 → P9
A → P5) and a step of installing the collected device driver 20a on the designated controller 10. Also, the controller side processing step (step P
2, P4, P5,..., P9) are as shown in FIG.
When the category is not in the category correspondence table 11 (step P
9) is characterized in that the initialization operation is completed (step P9A → P5) after executing the step (step T1) of forming a category indicated by the category data 20b into a hierarchical structure based on the category according to the operation of the device 20 (step T1). ing.

As an operation of the device 20 described in the category, specifically, there is an automatic mode setting. The automatic mode includes an autonomous mode in which the installation process is unconditionally executed, an inquiry mode inquiring whether or not to execute the installation process, a prohibition mode in which the installation process is not executed until instructed, and the previous mode for the known device 20. There is a mode to return to the state. As a selection item, a category can be set for each unique ID.

That is, the category data 20 of the hierarchical structure
By having b, it becomes possible to set a category of a fine classification in a category of a coarse classification. As a result, when the setting for the category of the fine classification is prioritized over the setting for the category of the coarse classification, among the devices 20 belonging to a certain coarse classification category, in particular, the category of a certain fine classification Can be set for the device 20 belonging to. As a result, finer connection settings can be made, and a system having advanced man-machine interface properties can be realized. Further, by providing the device-side processing step and the controller-side processing step, when the device 20 is connected to the network 30,
It is possible to almost automatically (autonomously) determine which controller 10 acquires the device driver 20a required for controlling the device 20, and it is possible to reduce the number of manual operations, so that it is necessary to install the device driver 20a. The labor required for the installation work on the user side can be reduced. In particular, many different types of devices 20 and many different types of controllers 10,
.., 10 are considered to be highly effective when many are connected on the network 30.

Each of these steps is performed by the user and the device 2.
0 or a program code for discriminating at least one or more controllers 10 that control the device 20 from the controllers 10 connected on the network 30 based on the timing specified by the controller 10 and the device 20 Device-side processing program code including a program code for instructing the controller 10 of the address of the device driver 20a required on the network 30 to the controller 30, and at least one or more controllers 10 are designated from the devices 20 connected on the network 30. Then, the program code for accessing the address on the network 30 of the device driver 20a specified by the device 20 (step P2) and collecting the device driver 20a, and the collected device driver 20a It is recorded on the aforementioned medium as a device side processing program code and the controller-side processing program code and a program code to be installed on the named controller 10.

A more detailed description will be given.

The device-side processing executed by the device 20 includes transmitting a device driver 20a necessary for controlling itself, category data 20b indicating a category to which the device belongs, and a device driver 20a to the controller 10. The controller 10 instructs the controller 10 to instruct whether to instruct the controller 10 to install the device driver 20a (specifically, “device”, “install”,
The default setting data 20c for “ignore” or “user” can be transmitted and received.

In the device-side processing step, the controller 10 (controller-side processor 101) inquires of a category name via the network 30 (step P
The controller 10 which inquires of the category data 20b specifying its own category name in response to the command of 2)
Device category return process (Step P3)
have. Each of these steps is stored in a medium described below in a state described by a program code generated by using a programming language such as Java which can be executed by the device 20.

[0259] Such a program code is held in the device-side processor 201.

In the device-side processing step, the device driver 20a to be controlled can be executed, and the device driver 20a,
, 20a can be executed.

That is, the device 20 and the controller 1
0 function at the same time, some devices 20
Work together as one device 20,
It becomes possible to realize the controller 10 and the device 20 (a device that plays two roles). As a result, a control system capable of autonomously selecting a predetermined device driver 20a from among the device drivers 20a,... Can be constructed, and an autonomous network system with advanced man-machine interface can be constructed.

On the other hand, the controller-side processing executed by the controller 10 includes a category recognizing step (step P4) and a device driver determining step (step P4).
5, P6, P7, P8, and P9) and a logical configuration centering on the installation process (steps P6A → P6B → P6C → P10). Each of these steps is stored in a medium described below in a state described by a program code generated using a programming language such as Java that can be executed by the controller 10.

[0263] Such a program code is held in the controller-side memory 102.

In the category recognition step (step P4), when the category data 20b specifying the category name is received via the network 30 (step P2 → P
3), controller 10 (controller-side memory 10)
The category data 20b registered in advance in the category correspondence table 11 prepared in 2) is compared with the category data 20b received from the device 20 via the network 30 at this time, and the category data 20b is transmitted. The operation corresponding to the category name of the device 20 (specifically, “device”, “install”, “ignore”,
Or “user”).

Device Driver Determination Step (Step P
5, P6, P7, P8, and P9) are device drivers that are commonly set for the recognized category name when the default setting data 20c is received via the network 30 (step P2 → P3). 20a or a device driver 20a prepared for each device 20 by default setting data 20a.
In response to the content of c (specifically, any one of “device”, “install”, “ignore”, and “user”), the device 2 selects the operation to install itself.
This is a step of determining for each of the 0 categories.

Installation process (Step P6A → P6)
B → P6C → P10) are “device”, “install”, “install” according to the execution result of the device driver determination process (steps P5, P6, P7, P8, and P9).
This is a step of deciding whether or not to install the device driver 20a in accordance with the operation of "ignore" or "user", and performing an installation operation based on the decision result.

Here, the device 20 (device-side processor 201) can execute the above-described device-side processing step and controller-side processing step, and can execute the device-side processing step or the controller-side processing step depending on the connection conditions to the network 30. Can be performed.

That is, since the device 20 (device-side processor 201) has the function of executing the device-side processing step and the controller-side processing step, the devices connected on the network 30 have the role of the device 20. Both roles as the controller 10 can be satisfied at the same time. For example, for a device having a higher control right than itself, the device is regarded as the controller 10 and the device 20 is set to the device 20. Consider the device as device 20 and call itself controller 1
A flexible connection mode such as setting to 0 can be realized autonomously. In other words, by having the functions of the device 20 and the controller 10 at the same time, it is possible to realize a controller 10 and device 20 device (a device for one and two roles) in which several devices 20 are collectively operated as one device 20. Become like As a result, a network 30 and a control system having a tree topology can be constructed, and an autonomous network system having advanced man-machine interface can be constructed.

Each of these steps includes the program code of the device driver 20a necessary for controlling itself,
Category data 20b indicating a category to which the user belongs;
The default setting data 20c for transmitting the device driver 20a to the controller 10 and instructing the destination controller 10 to install or not to install the device driver 20a, and the controller 10 (the controller-side processor 101) to transmit the network 30 And a program code for transmitting the category data 20b and the default setting data 20c to the controller 10 of the inquiry source in response to the command of the inquiry of the category name (step P2) via the controller 10 (controller processor 101). Category data 20b that specifies its own category in response to a request
Is returned to the inquiring controller 10, and when the device-side processing program code read and executed by the device 20 and the category data 20b are received via the network 30 (steps P2 → P3 ), Compares the category data 20b registered in advance in the category correspondence table 11 prepared in the controller 10 (controller memory 102) with the category data 20b received from the device 20 via the network 30 at this time. When receiving the category recognition program code for recognizing the operation corresponding to the category name of the device 20 that has transmitted the category data 20b and the default setting data 20c via the network 30 (step P2 → P3), the recognized category Against the name The device driver 20a set as the default or the device driver 20a prepared for each device 20 is stored in the default setting data 20c (specifically, "device", "install", "ignore" Or "user"
The device driver 20a is installed in accordance with the device driver determination program code that determines, for each category of the device 20, the selection of the operation to be installed or not in accordance with any one of the following. A program code for determining whether or not to perform the installation operation based on the determination result is recorded on the above-described medium as a controller-side processing program code that is read and executed by the controller 10.

The following is a specific example.

For example, consider a case where a certain device B (20) is connected to the network 30 to which a certain controller 10 is connected.

Controller 10 (controller-side processor 101) already connected to network 30
In order to control the device B (20), it is necessary to read a device driver 20a for the device B (20) into a memory inside the controller 10 and make it available from a program on the controller 10 system. However, if there is no need to control the device B (20), there is no need to acquire the device driver 20a.

First, the controller 10 sends the device B (2
0) via the network 30 to the category data 20b
(Step P2 → P3).

The controller 10 (controller-side processor 101) converts the acquired category data 20b into
Referring to the setting for each category, the device driver 20a
The operation related to the installation of the server (step P
4). If it is necessary to refer to the connection setting in the device B (20), this is also referred to and the operation is determined accordingly.

When the operation determined by the above operation is the setting of “install” (step P6), the controller-side processing step executes a step of requesting a device driver from the user (step P6A), and Executes the step of loading the device driver 20a from the floppy disk (Step P6B), and the controller-side processing step executes the step of installing the loaded device driver 20a (Step P6C).

The device B (2
0) is determined to be installed (device setting, step P
7) The device driver 20a incorporated in the device B (20) is read through the network 30, and the device driver 20a is set up in a usable state (step P7 → P7A → P7B).

If it is determined not to install the device driver 20a of the device B (20) in the controller 10 (“ignore” setting, step P5), the device B of the controller 10 is installed without installing the device driver 20a. The initialization work related to (20) is completed (step P5 → P10).

When it is determined to inquire of the user whether or not to install the device driver 20a of the device B (20) in the controller 10 (“user” setting, step P8), through the controllable user interface of the controller 10 Wait for an instruction from the user (step P8A). In response to this result, the controller 10 operates the device driver 20a of the device B (20).
Is performed (steps P8A → P8B → P5).

In the network control method according to the present embodiment, as shown in FIG. 12, when a category does not exist in the category correspondence table 11 (step P9), the category indicated by the category data 20b is changed according to the category to which the device 20 belongs. It is characterized in that the initialization operation is repeated (step P9A → P5) after executing the step of forming the structure (step T1).

That is, the category data 20 having a hierarchical structure
By having b, it becomes possible to set a category of a fine classification in a category of a coarse classification. As a result, when the setting for the category of the fine classification is prioritized over the setting for the category of the coarse classification, among the devices 20 belonging to a certain coarse classification category, in particular, the category of a certain fine classification Can be set for the device 20 belonging to. As a result, finer connection settings can be made, and a system having advanced man-machine interface properties can be realized.

The above operation is performed for all the controllers 10
The (controller-side processor 101) repeats the process for all the devices 20, whereby the initialization work of all the controllers 10 is completed semi-automatically (autonomously) (step P10).

As described above, according to the present embodiment, the device 20 (device to be controlled) has the category data 20b relating to the own device 20 and the settings relating to the connection of the own device 20, and the controller 10 (control Device 20) for each device category.
The controller 10 has a device driver 20a of the device 20 in accordance with a combination of the setting of the device 20 and the setting of the controller 10.
(Steps P4 to P4)
10), the setting for each category can be executed on the controller 10 side, and the control for handling only a specific category or the control for uniformly handling a specific category can be set and handled on the controller 10 side. Only the device driver 20a of the device 20 belonging to the category can be automatically (autonomously) installed in the controller 10.

[0283] Also, since the setting for connection for each category (that is, the setting of "installation" operation) on the controller 10 side is possible, the device 20 having a particularly important role even within the same category can be used. When installing the device driver 20a for control, a setting that always requires a user's instruction (that is, setting of “user” operation) becomes possible, and the general device 20 is automatically (independently set). The step of installing the device driver 20a in the controller 10 suitable for the target (that is, the step of installing according to the setting of the “device” operation) enables the network 3
When the device 20 is connected to the device 0, it is almost automatically (independently) which controller 10 acquires the device driver 20a required for controlling the device 20.
Since the number of manual operations can be reduced, the labor required for the installation work on the user side required for installing the device driver 20a can be reduced.

Further, by having the category data 20b having a hierarchical structure, it becomes possible to set a category of a fine classification among categories of a coarse classification. As a result, when the setting for the category of the fine classification is prioritized over the setting for the category of the coarse classification, among the devices 20 belonging to a certain coarse classification category, in particular, the category of a certain fine classification Can be set for the device 20 belonging to. As a result, finer connection settings can be made, and a system having advanced man-machine interface properties can be realized.

[0285]

According to the first and tenth aspects of the present invention,
When a device is connected to the network, it is possible to almost automatically determine which controller acquires control information or a device driver required for controlling the device, and the number of manual operations can be reduced.
It is possible to reduce the effort on the user side required for installing the control information or the device driver. Especially,
The effect is considered to be significant when many different types of devices and many different types of controllers are connected in large numbers on the network.

According to the invention described in claims 2 and 11, in addition to the effect described in claim 1, the device (the controlled device) sets category data relating to the own device and settings relating to the connection of the own device. The controller (device on the controlling side) has settings related to device connection for each device category, and the controller has a device driver and control information of the device in accordance with a combination of the settings on the device side and the settings on the controller side. By performing the step of determining whether or not to obtain, the setting for each category can be executed on the controller side, the control to handle only a specific category or the control to uniformly handle the specific category can be set on the controller side, Only the control information of the devices belonging to the category to be handled can be automatically installed in the controller Uninaru. In addition, since the settings for connection for each category can be made on the controller side, even when installing device drivers and control information for controlling devices that have a particularly important role even within the same category, When a device is connected to a network by setting a device that always requires the user's instructions and by automatically installing a device driver and control information in a suitable controller for a general device. In addition, since it is possible to almost automatically determine which controller obtains control information or a device driver required for controlling the device and reduce the number of manual operations, it is necessary to install control information or a device driver. The effort on the user side can be reduced.

According to the third and twelfth aspects of the present invention, in addition to the effect of the second aspect, it is also possible to determine that the device is unknown to the controller because it is not registered in the category correspondence table. However, by implementing steps to automatically create entries for new categories, future expansion of connected devices will also minimize the extra user-side effort required to install control information or device drivers. To be able to respond flexibly.

According to the fourth and thirteenth aspects of the invention, in addition to the effect of the second aspect, the controller-side processing step can detect that a new device is connected to the network when a new device is connected. As a result, when the new device is connected to the network, the installation of the control information or the device driver can be performed in synchronization with the new device. It is possible to save labor for instructing control information required for control or installation of a device driver in a controller, and to construct an autonomous network system having advanced man-machine interface.

According to the fifth and fourteenth aspects of the present invention, in addition to the effect of the second aspect, by executing the connection history storing step, the correspondence between the device ID data and the past connection status data can be obtained. Relationships can be saved as past connection status tables. As a result, when a known device that has been connected in the past is connected on the network, the device is recognized based on the device ID data, and a past connection status table is searched based on the device ID data. This makes it possible to reproduce the past controllable state of a known device that has been connected in the past and has a track record. In this way, even if a special setting is limited to a specific device only in the past connection mode, the device is controlled when the device is connected to the network again. This eliminates the need to manually reset the control information or device driver required each time a device is connected, and allows the user to connect to the network of a device that has a track record in the past, The labor for instructing the installation of the device driver to the controller can be omitted, and an autonomous network system having advanced man-machine interface can be constructed.

According to the invention described in claim 6, according to claim 2
In addition to the effects described in the above, since the device has a function of executing the device-side processing step and the controller-side processing step, the device connected on the network can perform both the role as the device and the role as the controller. Can be satisfied at the same time. For example, for a device having a higher control right than itself, the device is regarded as a controller and the device itself is set as a device. It becomes possible to autonomously realize a flexible connection mode in which the device is regarded as a device and the device itself is set in the controller. In other words, by having the functions of the device and the controller at the same time, it is possible to realize a controller / device device (a device that plays two roles) in which several devices operate collectively as one device. As a result, a network or control system having a tree topology can be constructed, and an autonomous network system having advanced man-machine interface properties can be constructed.

According to the invention set forth in claim 7, according to claim 6,
Similar to the effects described in the above, by having the functions of the device and the controller at the same time, several devices can be
It is possible to realize a controller / device device (a device for two roles) that operates as one device. As a result, a control system is constructed in which a predetermined device driver or control information can be autonomously selected from device drivers or control information and installed in a predetermined controller according to connection conditions to a network having a tree topology. And an autonomous network system with advanced man-machine interface can be constructed.

According to the eighth and fifteenth aspects of the invention, in addition to the effect of the second aspect, the step of internally storing a device driver for controlling itself or control information is included in the device-side processing step. With this arrangement, a device driver or control information can be held inside the device. By holding the device driver or the control information inside the device in this way, it is not necessary to procure the device driver or the control information required for controlling the device from the outside. Independent installation work can be performed using only the device driver or control information stored in the system, and an autonomous network system having advanced man-machine interface can be constructed.

According to the ninth aspect, the second aspect
In addition to the effects described in (1), by having category data of a hierarchical structure, it becomes possible to set a category of a fine classification among categories of a coarse classification. As a result, when the setting for the category of the fine classification is made to take precedence over the setting for the category of the coarse classification, among devices belonging to one coarse classification category,
It becomes possible to make settings for devices belonging to a certain sub-category. As a result, finer connection settings can be made, and a system having advanced man-machine interface properties can be realized.

[0294] According to the seventeenth aspect, when the device 20 is connected to the network 30,
Since it is possible to almost automatically determine which controller 10 acquires the control information or the device driver 20a required for controlling the device 20, the number of manual operations can be reduced.
It is possible to reduce the labor on the user side required for the installation of a. In particular, many different types of devices 2
It is considered that the effect is great when a large number of controllers 10 of zero or many different types are connected on the network 30.

According to the eighteenth aspect, the same effect as that of the seventeenth aspect can be obtained.

According to the nineteenth aspect, the same effect as that of the first aspect is obtained.

According to the twentieth aspect, the same effect as the first aspect can be obtained.

According to the twenty-first aspect, when the device 20 is connected to the network 30,
Since it is possible to almost automatically determine which controller 10 acquires the control information or the device driver 20a required for controlling the device 20, the number of manual operations can be reduced.
It is possible to reduce the labor on the user side required for the installation of a. In particular, many different types of devices 2
It is considered that the effect is great when a large number of controllers 10 of zero or many different types are connected on the network 30.

According to the twenty-second aspect, the same effect as that of the twenty-first aspect is obtained.

[Brief description of the drawings]

FIG. 1 is a basic configuration diagram of a network for explaining a connection mode of a network according to the present invention. FIG. 1A is a basic configuration diagram of a device and a controller, and FIG. FIG. 3C is a connection configuration diagram of devices and controllers connected on a network in which devices to be controlled and controllers to be controlled coexist, and FIG. 3C illustrates a connection configuration on a network in which controlled devices are connected to a common controller. It is a connection block diagram of the connected device and controller.

FIG. 2 is a network configuration diagram in which a plurality of types of peripheral devices and a plurality of types of CPUs are mixed.

FIG. 3 is a network configuration diagram for explaining a specific configuration of the network of FIG. 1, wherein computer peripheral devices and information home appliances are personal computers (PCs);
Is a network configuration diagram connected via serial communication lines.

FIG. 4A is a basic configuration of a category correspondence table used in a controller-side processing step executed by a controller, and includes category data registered in advance in the category correspondence table and an operation corresponding to the category; (B) is a chart for explaining an example of category data transmitted by the device and an operation corresponding to the category data.

FIG. 5 is a flowchart for explaining an embodiment of a network control method according to claims 1, 2, 10 and 11 of the present invention.

FIG. 6 is a flowchart illustrating an embodiment of a network control method according to claims 3 and 12 of the present invention.

FIG. 7 is a flowchart for explaining one embodiment of a network control method according to claims 4 and 13 of the present invention.

FIG. 8 is a flowchart for explaining one embodiment of a network control method according to claims 5 and 14 of the present invention.

FIG. 9 is a chart for explaining an example of various data used in the embodiment shown in FIG. 8; FIG. 9A shows a category correspondence table used in a controller-side processing step executed by a controller; In one embodiment, categories A, B, C, D,... Registered in advance in a category correspondence table and operations corresponding to these categories, such as installation, device user, ignore,. FIG. 4B is a table for explaining an example of device ID data, category data, and an operation corresponding to the data transmitted by the device, and FIG. 4C is a controller-side process. 6 is a chart for explaining a correspondence relationship between device ID data stored in a past connection status table and past connection status data in a process of executing a process.

FIG. 10 is a flowchart illustrating an embodiment of a network control method according to claims 8 and 15 of the present invention.

11 is a chart for explaining an example of category data transmitted by a device and an operation corresponding to the category data in the flowchart of FIG. 10;

FIG. 12 is a flowchart for explaining one embodiment of a network control method according to claim 9 of the present invention.

[0000]

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 10 ... Controller 101 ... Controller side processor 102 ... Controller side memory 10a ... Connection state data 11 ... Category correspondence table 20 ... Device (computer peripheral device, information home appliance) 201 ... Device side processor 202 ... Device side memory 20a ... Control information or device Driver 20b Category data 20c Default setting data 20d Device ID data 30 Network

Claims (22)

[Claims] 1. A network control method for a device and a controller connected on a network in which a device to be controlled and a controller to be controlled are mixed, wherein the device is controlled based on a timing designated by a user, a device, or a controller. At least one to control
Determining one or more controllers from among the controllers connected to the network; and instructing the controller of control information necessary for controlling the device or an address of a device driver on the network. And at least one of the devices connected on the network.
When one or more controllers are designated, a step of accessing the address on the network included in the control information or the device driver specified by the device and collecting the control information or the device driver; and A controller-side processing step including a step of installing control information or a device driver in the designated controller. 2. The device-side processing step executed in the device includes control information or a device driver necessary for controlling itself, category data indicating a category to which the device belongs, and a category indicating a category to which the device belongs. Data and default setting data including at least an instruction as to whether to transmit the control information or the device driver to the controller and instruct the destination controller to install the control information or the device driver, and a category from the controller. A device category return step of returning category data relating to its own category to the requesting controller in response to a name inquiry, wherein the controller-side processing step executed in the controller receives the category data. Control A category recognition step of comparing category data registered in advance in a category correspondence table with the received category data and recognizing an operation corresponding to a category of a device which has transmitted the category data; When the setting data is received, the control information or device driver commonly set for the recognized category, or the device-specific control information or device driver prepared for each device is described in the contents of the default setting data. A device driver determining step of determining, for each device category, an operation selection of whether to install the device driver in accordance with the device driver, and determining whether to install the device driver according to the execution result of the device driver determining step. Installation work based on the decision Network control method according to claim 1, characterized in that it comprises a installation step of the execution. 3. The device according to claim 2, wherein the controller-side processing step executes the category recognizing step, and the device indicates that the category indicated by the category data received by the controller is not registered in a category correspondence table of the controller. 3. The method according to claim 2, further comprising a step of automatically instructing a new setting of control information or a device driver when the driver determining step is executed, and a step of automatically generating an entry for the new setting. 2. The network control method according to item 1. 4. The controller-side processing step includes: detecting a connection of a new device to a network when a new device is connected; and executing the category data and the default for the newly connected device. A default setting requesting step of requesting setting data; and the device driver determining step, wherein it is determined whether or not to install the control information of the newly connected device on the controller side when a new device is connected. Claim 2
2. The network control method according to item 1. 5. The controller-side processing step stores, as a past connection status table, a correspondence relationship between device ID data, which is an identifier transmitted by each device on the network to the controller, and past connection status data. A connection history storing step, a step of determining whether a device has been connected in the past when the device detecting step is performed, and a step of determining that a device connected in the past has been connected again And a past connection state calling step for calling the past connection state data of the device stored in the connection history storage step, and reproducing the past controllable state of the device based on the called connection state data. The network control method according to claim 2, further comprising a resume step. 6. A device having a function of executing the device-side processing step and the controller-side processing step, and executing at least one of the device-side processing step and the controller-side processing step according to a connection condition to a network. The method according to claim 2, wherein the method is performed. 7. The device-side processing step is capable of executing a plurality of types of the device drivers or a plurality of types of the control information, and selects one of the device drivers or the control information according to a connection condition to a network. The network control method according to claim 2, wherein a predetermined device driver or control information is selected. 8. The device-side processing step includes a step of internally storing the device driver or the control information for controlling itself, and transferring the device driver or the control information to the controller via a network. The controller-side processing step refers to the device driver or the control information, and controls a device that has transferred the device driver or the control information based on the referenced device driver or the control information. The network control method according to claim 2, further comprising the step of: 9. A category indicated by the category data,
3. The network control method according to claim 2, further comprising a step of forming a hierarchical structure based on categories according to device operations. 10. A medium in which a control program code of a device and a controller connected to a network in which a device to be controlled and a controller to be controlled coexist is recorded, and wherein the program is executed at a timing designated by a user, a device or a controller. At least one controlling said device based on
A program code for discriminating one or more controllers from the controllers connected on the network, and control information necessary for controlling the device or an address of a device driver on the network for the controller. A device-side processing program code including a program code;
When one or more controllers are designated, a program code for accessing the control information specified by the device or an address on the network included in the device driver to collect the control information or the device driver; and And a controller-side processing program code having a program code for installing the selected control information or device driver in the designated controller. 11. Transmitting control information necessary for controlling itself or a program code of a device driver, category data indicating a category to which the device belongs, control information or a device driver to a controller, and transmitting the control information or the device driver to the controller at the transmission destination. A program code for returning the control information or default setting data including at least an instruction as to whether or not to order the installation of the device driver, and the category data relating to the own category to the requesting controller in response to a category name inquiry from the controller The device-side processing program code read and executed by the device; category data previously registered in a category correspondence table in the controller when the category data is received; and the received category Recognizing category recognition program encoding operation corresponding to the by comparing the data category of the device that has transmitted the category data,
When the default setting data is received, the control information or device driver commonly set for the recognized category or the device-specific control information or device driver prepared for each device is converted to the default setting data. Device driver determining program code for determining, for each device category, an operation selection of whether or not to install the device driver according to the content of the device, and whether to install the device driver according to the execution result of the device driver determining program code And a program code for executing an installation operation based on the determination result, wherein the controller-side processing program code read and executed by the controller is recorded.
The medium according to 0. 12. When the category indicated by the category data received by the controller by executing the category recognition program code is not registered in the category correspondence table of the controller, the device driver determination program code is executed. In this case, the controller-side processing program code including a program code for automatically instructing a new setting of control information or a device driver and a program code for automatically generating an entry for the new setting is recorded. The medium according to claim 11, wherein: 13. A device detection program code for detecting that a new device is connected to a network when a new device is connected, and a program for requesting the category data and the default setting data for the newly connected device. And a program code for determining whether to install the control information of the newly connected device on the controller side when a new device is connected, the controller-side processing program having a code and the device driver determination program code. The medium according to claim 11, wherein a code is recorded. 14. A device I which is an identifier transmitted by an individual device on the network to the controller.
A connection history storage program code for storing the correspondence between D data and past connection status data as a past connection status table, and whether a device has been connected in the past when the device detection program code was executed. Program code for determining whether or not a device has been connected in the past, and a program code for calling past connection state data of the device stored in the connection history storage program code when it is determined that the device has been connected again 12. The medium according to claim 11, wherein the controller-side processing program code including a program code for reproducing a past controllable state of the device based on the called connection state data is recorded. . 15. The device, comprising: a program code for internally storing the device driver or the control information for controlling itself; and a step of transferring the device driver or the control information to the controller via a network. Side processing program code, a program code that refers to the device driver or the control information, and a program code that controls a device that has transferred the device driver or the control information based on the referenced device driver or the control information. The medium according to claim 11, wherein the controller-side processing program code is recorded. 16. A network control system of a device and a controller connected on a network in which a device to be controlled and a controller to be controlled coexist, wherein the device is based on a timing designated by a user, a device or a controller. Determining at least one or more controllers that control the device from among controllers connected to the network, and controlling information necessary for controlling the device or an address on the network included in a device driver. And a device-side memory that holds the control information or the device driver. The controller is configured to control at least one or more controllers from devices connected on a network. When a roller is designated, the device accesses the control information or the address on the network included in the device driver specified by the device, collects the control information or device driver, and collects the collected control information or device driver. A network control system, comprising: a controller-side processor that installs the control information in the designated controller; and a controller-side memory that holds the control information or the device driver. 17. A network control method for a device and a controller connected to a network in which a device to be controlled and a controller to be controlled coexist, wherein the step of determining the controller from the network and the method of controlling the device A network control method comprising a device-side processing step of instructing the controller of necessary information and installing the information on the controller. 18. A network control method for a device and a controller connected on a network in which a device to be controlled and a controller to be controlled coexist, wherein the step of determining the device from the network and the method of controlling the controller A network control method comprising a controller-side processing step of instructing the device of necessary information and installing the information in the device. 19. A medium in which a control program code of a device and a controller connected to a network in which a device to be controlled and a controller to be controlled coexist is recorded, wherein a program code for discriminating the controller from the network is provided. And a program code for instructing the controller on information necessary for controlling the device and installing the information on the controller. 20. A medium in which a control program code of a device and a controller connected to a network in which a device to be controlled and a controller to be controlled coexist is recorded, wherein a program code for identifying the device from the network is provided. And a program code for instructing the device on information necessary for controlling the controller and installing the information on the device. 21. A network control system of a device and a controller connected to a network in which a device to be controlled and a controller to be controlled coexist, wherein a program code for determining the controller from the network and a device for controlling the device. A network control system, comprising: a device-side processor for instructing the controller on information necessary for the device and installing the information on the controller. 22. A network control system for a device and a controller connected on a network in which a device to be controlled and a controller to be controlled are mixed, wherein a program code for determining the device from the network and a controller for controlling the controller are provided. A network control system, comprising: a controller-side processor for instructing the device of information necessary for the device and installing the information in the device.