JP5802049B2 - Device control apparatus and method, client apparatus, and device control system - Google Patents

Description

  The present invention relates to a device control apparatus and method, a client apparatus, and a device control system, and more particularly to a device control apparatus and method, a client apparatus, and a device control system having a function of controlling a device via a network. .

  With the widespread use of networks, a device server configured so that a device (peripheral device) that has been used by being locally connected to a personal computer (PC) or the like can be used from a client PC on the network has been announced.

  For example, several methods for using devices such as printers, storages, and scanners as shared devices from a client PC on a network via a device server have been proposed.

  As one method, dedicated application software (hereinafter referred to as “utility”) is installed in the client PC, and when the user tries to access the device, the installed utility is operated to Some devices allow a client PC on a network to access a device to be accessed as a locally connected device by virtually recognizing the device to be accessed as a locally connected device.

  In this method, the user needs to start / end the session (connection), and unless the user uses the utility to end the device, the session with the device server is exclusively used. Can not use the device.

  In order to solve such a problem, it is assumed that the device server is in a data transmission exclusive state only while block data having a data length specified by the block header is transmitted, and data transmission between the device and a specific client PC is performed. A network file management system that permits the above is disclosed (for example, see Patent Document 1).

JP 2007-317067 A

  Certainly, in the network file management system disclosed in Patent Document 1, a plurality of client PCs can share a device without performing a manual operation.

  However, in a state where the client PC occupies one device connected via the network, the client PC cannot occupy another device due to a technical limitation that other devices cannot be used. When a device requiring high frequency is connected, it becomes difficult for the client PC to use it simultaneously with other devices.

  For example, in the case of a device such as an IC card reader, it is necessary to periodically inquire (polling) whether or not an IC card has been detected, that is, to perform device monitoring processing (state change detection processing). The processing is generally executed by a device driver installed on the client PC.

  For this reason, the exclusive use of the device via the network by the client PC frequently occurs, and the traffic on the network increases significantly during the exclusive use of the device, so the exclusive use of such a device must be the minimum necessary. Is desirable.

  Further, when the device is frequently occupied and data is always transmitted on the network, the data is easily hacked, which is not desirable from the viewpoint of security.

  In addition, the above-mentioned device monitoring process (state change detection process) causes the device server to retain only the trigger detection algorithm suitable for a specific device in order to eliminate the dependence on the model whose processing contents differ for each device. In such a case, there is a problem that the versatility of the device server is impaired. On the other hand, if the device server holds all trigger detection algorithms that are compatible with various devices in the system, the device server can ensure versatility, but the device server requires a large storage area and costs There is a problem of causing an increase.

  The first object of the present invention is to provide the device control apparatus with a device monitoring process (state change detection process) that has been conventionally implemented in the client apparatus, so that the device control apparatus is independent without communication with the client apparatus. By monitoring device status changes and notifying client devices when device status changes are detected, device monitoring (polling) by client devices is unnecessary and traffic on the network is reduced. It is an object to provide a device control apparatus and method, a client apparatus, and a device control system.

  The second object of the present invention is that the client device communicates with the device in response to a change in the state of the device, so that the client device occupies the device only when necessary to reduce security vulnerabilities. It is an object of the present invention to provide a device control apparatus and method, a client apparatus, and a device control system that can simultaneously use a plurality of devices even if they are frequently required devices.

  A third object of the present invention is to dynamically install or download a trigger detection algorithm and definition file suitable for a device to be monitored to the device server, so that the device server can be used in various ways while ensuring versatility. It is an object to provide a device control apparatus and method, a client apparatus, and a device control system capable of executing a device detection process.

  In order to achieve the above object, a device control apparatus of the present invention is a device control apparatus that is connected to a client apparatus via a network and to which a device is to be locally connected, and for monitoring the state of the device The first detection means for monitoring the status of the device using the definition file and the trigger detection algorithm, and detecting the status change of the device, and detecting the status change when the status change of the device is detected Transmitting means for transmitting a trigger notification indicating to the client device; data communication control means for starting a session with the client device that has received the trigger notification and relaying data communication with the device that has detected the state change; The data communication with the device is terminated and the session with the client device is disconnected. And a second detecting means for detecting that the first detecting means resumes monitoring of the state of the device when a session with the client device is disconnected. .

  A client apparatus according to the present invention is a client apparatus connected to a device control apparatus to which a device is to be locally connected via a network, and for confirming an operation state of the device locally connected to the device control apparatus. Creation means for creating a definition file including request information and response information from the device accumulated when polling, transmission means for sending the created definition file to the device control apparatus, and A receiving unit that receives a trigger notification indicating detection of a change in the state of the device from the device control unit that has detected a change in the state of the device, and a session with the device control unit in response to the trigger notification received by the receiving unit Session control means for starting To.

  According to the above configuration, the device server monitors the corresponding device based on the “trigger detection algorithm” / “definition file”, and when a change in the state of the device is detected, trigger notification is made. The client PC that has received the trigger notification starts a session with the device server and executes data communication between the client PC and the device. When the data communication ends and the session is disconnected, the device server resumes monitoring of the corresponding device. As a result, since the device monitoring process implemented on the client PC side is performed by the device server, the monitoring process on the client PC side becomes unnecessary, and data communication is performed between the client PC and the device only when necessary. When finished, the monitoring of the device is resumed.

  Further, when the client PC detects the connection of the device, the client PC executes polling for confirming the operation state of the device, accumulates transmission / reception packets at this time, and sends them to the device server. Since the device server can execute the monitoring process by using the transmission / reception packet as the definition file, the monitoring process of the device can be performed even for a device for which a connection is newly detected.

It is a figure which shows schematic structure of the device control system which concerns on the 1st Embodiment of this invention. It is a sequence diagram used for demonstrating the operation | movement sequence of the device control system of FIG. It is a figure used for demonstrating the data structure of the definition file stored in the data storage part in FIG. It is a flowchart which shows the procedure of the trigger detection process performed by the device server in FIG. It is a sequence diagram used for demonstrating the operation | movement sequence of the device control system which concerns on the 2nd Embodiment of this invention. FIG. 6 is a diagram used for explaining a basic configuration of a packet transmitted and received in the operation sequence of FIG. 5. FIG. 6 is a diagram used to explain a data structure of a request / response packet transmitted in the operation sequence of FIG. 5 and a definition file created by accumulating these data structures.

  Hereinafter, the present invention will be described in detail with reference to embodiments shown in the drawings.

<Configuration of device control system>
FIG. 1 is a diagram showing a schematic configuration of a device control system according to the first embodiment of the present invention.

  1, the device control system according to the first embodiment of the present invention includes a client PC 100 (client device) and a device server 200 (device control device) to which a device 300 (300A, 300B) is locally connected. Prepare. The client PC 100 and the device server 200 are connected to each other via the network 500. The network 500 may be configured by a wired or wireless communication line.

  The device 300 is connected (locally connected) to the device server 200 by a connection cable 400 that conforms to a USB (Universal Serial Bus) interface. However, the connection cable 400 is not limited to the USB interface, and may be a cable that conforms to another interface such as IEEE1394.

  Next, the configuration of each device constituting the device control system will be described sequentially.

<Configuration of client PC 100>
The client PC 100 includes a CPU, an input unit, a display unit, a memory, a communication unit, and an external storage unit that are connected to each other via an internal bus, and can communicate with the device server 200 via the network 500.

  The external storage unit stores various data in addition to software components such as an operating system (hereinafter referred to as OS), an application program 101, a resident module 102, a device driver 103, a virtualization control unit 104, and a communication control unit 105 (not shown). The stored data storage unit 106 is stored. These software components and various data are read out on the memory and various controls are executed under the control of the CPU.

  The application program 101 is a software program for controlling the device 300 by instructing a data input / output request to the resident module 102 and the device driver 103.

  The resident module 102 (1) a function of acquiring device individual information for identifying each device 300 locally connected to the device server 200, and (2) identifying a device model for each individual based on the device individual information. (3) a function for uniquely identifying the device driver 103 and the virtualization control unit 104 necessary for data transmission / reception with the device 300, and dynamically generating and starting those software components sequentially, (4 ) A function for instructing start / disconnection of a session with the device server 200 via the communication control unit 105. (5) When a session with the device server 200 is started, the device driver 103 and the virtualization control unit 104 are used. And a function of controlling data transmission / reception with the device 300.

  The device driver 103 receives a data input / output request from an OS (not shown) or an application program 101 (hereinafter referred to as “upper layer software program”) in a data format corresponding to the device 300 (hereinafter referred to as “control command”). This is a software component that sends this control command to the virtualization control unit 104 and notifies the upper layer software program of a response to this control command.

  The virtualization control unit 104 converts the data input / output request converted into the control command by the device driver 103 into packet data conforming to the USB data format (hereinafter referred to as “USB data”), and is sent from the communication control unit 105. It is a software component that converts incoming USB data into a data format similar to a control command and sends it to the device driver 103. Further, in response to a data transmission / reception request to the device 300, a function (hereinafter referred to as “virtualization control”) that simulates the same behavior as when the device 300 is directly connected to the client PC 100 (local connection). It is a software component provided. This “virtualization control” enables data transmission / reception in the same state as when the device 300 is locally connected.

  The communication control unit 105 performs conversion processing between “USB data” sent via the virtualization control unit 104 and “network packet” when communicating with the device server 200 via the network 500. 200 is a software component that controls data transmission / reception to / from 200. Further, in response to a data transmission / reception request from an upper layer software program or device driver 103 sent via the virtualization control unit 104, the session start / disconnection control with the device server 200 is performed.

  The data storage unit 106 stores various data such as a definition file 107 and a trigger detection algorithm 108 in FIG. 3 to be described later.

  The definition file 107 is a data file that stores commands and information necessary for the trigger detection algorithm 108 when the device server 200 monitors the device 300.

  The trigger detection algorithm 108 is a program code in which an execution procedure for monitoring the device 300 in the device server 200 and detecting a change in the state thereof is described. By reading the definition file 107, the trigger detection algorithm 108 300 monitoring processes (hereinafter referred to as “trigger detection process”) are performed. This trigger detection process will be described later with reference to FIG.

  The definition file 107 and the trigger detection algorithm 108 are a set of “monitoring information” (monitoring program) for monitoring the device 300, and are different for each model of the device 300.

  FIG. 3 is a diagram used to explain the data structure of the definition file stored in the data storage unit 106 in FIG.

  The definition file in FIG. 3 is created based on the function (specification) of the device 300, and includes device identification information such as a vendor ID (VID) and product ID (PID), and a data pattern of a request packet issued to the device 300. And the data pattern of the response packet when the state of the device 300 changes. The data pattern of the response packet includes only the response packet returned from the device 300 when the state of the device 300 changes.

<Configuration of Device Server 200>
The device server 200 includes a CPU, a memory, a communication unit, a USB interface, and an external storage unit that are connected to each other via an internal bus. The device server 200 communicates with the client PC 100 via the network 500 and is connected locally. Data can be transmitted / received via the connection cable 400 with 300.

  The external storage unit stores software components such as an OS (not shown), a communication control unit 201, and a device control unit 202. These software components and various data stored in the data storage unit 203 are read out on the memory and various controls are executed under the control of the CPU.

  The communication control unit 201 has a function of controlling (starting and disconnecting) a session with the client PC 100 connected via the network 500 according to the control of the OS.

  The device control unit 202 has a function for controlling the device 300. In addition, the device control unit 202 acquires the device individual information 204, the definition file 205, and the trigger detection algorithm 206 via the communication control unit 201, and performs processing described below based on the acquired information (data). It has a function to execute.

  (1) Conversion processing between “network packet” for communicating with the client PC 100 and “USB data” transmitted and received between the device 300 and data between the client PC 100 and the device 300 in cooperation with the device control unit 202 Function to mediate (relay) transmission / reception, (2) Function to transmit device individual information 204 acquired from “device” to client PC 100, (3) Receive (acquire) definition file 107 / trigger detection algorithm 108 from client PC 100 Function, (4) “trigger detection process” for monitoring (polling) the device 300 at regular intervals using a definition file 205 and a trigger detection algorithm 206 (described later), and information indicating the detection when a state change is detected (Hereinafter referred to as trigger notification) to client P Function of transmitting to the 100, detects this when the session is disconnected between the client PC100 (5) Communication controller 201 has a function of resuming the "trigger detection processing" (4).

  The device individual information 204 is information for identifying the “device” for each individual, and for identifying the vendor ID (VID) and model assigned to each manufacturer that manufactured the device to identify the manufacturer. A product ID (PID) assigned for each model, a serial number assigned to each device in order to identify an individual device, and the like. The device individual information 204 is acquired from the device 300 by the device control unit 202 when the device 300 is connected.

  The definition file 205 and the trigger detection algorithm 206 are information necessary for monitoring (polling) of the device 300 connected to the device server 200 itself, and the device server 200 acquires it from the client PC 100 based on the device individual information 204.

<Configuration of Device 300>
The device 300 (300A, 300B) is a general-purpose input / output device (device) having a USB interface. For example, an input device such as a keyboard, a mouse, a card reader, a display (output) device such as a display, a single function peripheral device (SFP) such as a printer, or a scan function or a copy function in addition to a print function A multifunction peripheral device (MFP) having a storage function and the like. However, it is not limited to these, and another device may be used.

  For example, when the device 300 is a device such as an IC card reader, when the IC card is held over and the IC card reader executes an IC card reading process, the device server 200 changes the operation of the reading process to the state of the device 300. This is detected as a change, and a trigger notification is transmitted to the client PC 100.

  Here, the change in the state of the device 300 is a change in the operation state of the device. For example, an IC card reading operation (acquisition of a user ID) is performed on the IC card reader, an operation button, or the like. However, the present invention is not limited to these.

  The device server 200 and the device 300 described above have been described as separate apparatuses and devices, but the present invention is not limited thereto, and the device server 200 may be integrated with the device 300.

<When using a definition file created in advance for each device>
FIG. 2 is a sequence diagram used to explain an operation sequence of the device control system of FIG.

  The sequence diagram of FIG. 2 shows a process of transmitting and receiving data between the client PC 100 and the device 300A connected to the device server 200.

  In FIG. 2, when the device 300A is connected, the device server 200 acquires device individual information of the device 300A (step S201), and stores it as the device individual information 204 in the data storage unit 203 (step S202).

  At this time, the device server 200 determines whether or not a serial number is stored in the acquired device individual information 204. If the serial number is not stored, unique information (for example, a MAC address) of the device server 200 is stored. Etc.) and unique information corresponding to the serial number is generated from the unique information (for example, port number) of the port to which the device is connected, and added to the device individual information 204. This makes it possible to identify even when a plurality of the same models that do not store serial numbers are connected.

  Next, the resident module 102 of the client PC 100 transmits a search packet to the device server 200 via the communication control unit 105 in order to confirm the device 300 </ b> A locally connected to the device server 200. For example, the device server 200 is searched (inquired) using a protocol such as UDP (User Datagram Protocol). Upon receiving the search packet, the device server 200 transmits the device individual information 204 stored in the data storage unit 203 to the client PC 100 (Step S203).

  When the resident module 102 of the client PC 100 acquires the device individual information 204 from the device server 200, the “device” is identified by the vendor ID (VID), product ID (PID), serial number, etc. included in the device individual information 204. Based on the information for identifying the individual included in the device individual information 204, the device driver 103 and the virtualization control unit 104 are uniquely identified, and these software components are dynamically Generate and start. These software components enable the virtualization control of the device 300A (step S204).

Next, the client PC100 is the definition file 107 that is stored in the data storage unit 106, from the trigger detection algorithm 108, the definition file 107 corresponding to the model of the device 300 A which is identified based on the device identification information 204, the trigger The detection algorithm 108 is specified.

Then, the client PC 100 generates an installation packet including the specified definition file 107 and trigger detection algorithm 108, starts a session with the device server 200 by the communication control unit 105 (step S205), and generates the packet. An installation packet is transmitted to the device server 200 (step S206).

  If the session cannot be started for some reason such as no response (timeout), connection refusal, etc., the device server 200 notifies the device 300A of an error, for example, notifies the device 300A of an error, and notifies the device itself of an alarm. Etc.) to finish this processing.

  Upon receiving the installation packet, the device server 200 installs the definition file 107 and the trigger detection algorithm 108 included in the packet, and the data storage unit 203 as the definition file 205 (first definition file) and the trigger detection algorithm 206, respectively. (Step S207).

  Note that when the application program 101 of the client PC 100 identifies that the device is a “device” other than the device 300A as a result of the identification processing based on the device individual information 204, the software component generation processing is not executed.

<Start trigger detection process>
When the session between the client PC 100 and the device server 200 is disconnected (step S208), the device control unit 202 of the device server 200 uses the definition file 205 and the trigger detection algorithm 206 stored in the data storage unit 203, The trigger detection process (monitoring process) of FIG. 4 to be described later of the device 300A is started (step S209). The trigger detection process start condition includes a case where no session starts from the client PC 100 within a predetermined time after the trigger notification.

<Device control start to end>
FIG. 4 is a flowchart showing a procedure of trigger detection processing executed by the device server in FIG.

  The state change of the device 300A is monitored by the trigger detection process of FIG. 4 (steps S209 to S214 of FIG. 2). Also, the trigger detection process of FIG. 4 is interrupted if an interrupt process from the client PC 100 occurs during the execution of this process, and resumed when the interrupt process ends.

  In FIG. 4, first, monitoring (polling) starts when the session between the device server 200 and the client PC 100 is disconnected or the client PC 100 does not start a session within a predetermined time after the trigger notification (in step S401). YES), according to the request data pattern (request information) included in the definition file 205 (FIG. 3), the request packet is transmitted from the device control unit 202 to the device 300A via the communication control unit 201 (step S402). . The monitoring (polling) interval can be set in the definition file 205 (FIG. 3). This interval is for preventing the device server 200 from being exclusively used for the trigger detection process and allowing other functions (devices) to be used.

  Next, it is determined whether or not a response packet from the device 300A has been received (step S403). When the response packet is received, error information is returned as a response packet (for example, the connection with the device 300A is disconnected). Or the like) (step S405).

If error information is returned as a result of the determination in step S405, the process immediately ends, and if the response packet is not an error (NO in step S405), the device control unit 202 returns a response from the device 300A. Each data pattern (response information) of the response packet included in the definition file 205 is compared with the packet (step S406 (step S210 in FIG. 2)) (first detection means, first determination means).

  As a result of the comparison in step S406, when the data patterns of the response packet from the device 300A and the response packet included in the definition file 205 match, there is a state change in the device 300A (step S211 in FIG. 2). 1), it is determined that a trigger notification indicating this state change should be transmitted (YES in step S407), and the trigger notification is transmitted to the client PC 100 via the communication control unit 201 (step S409 (FIG. 2)). Step S213)) (transmitting means), this processing is terminated (Step S214 in FIG. 2).

  On the other hand, as a result of the comparison in step S406, when the data patterns of the response packet from the device 300A and the response packet included in the definition file 205 do not match (mismatch), there is no state change in the device 300A, and the trigger Since it should not be notified (NO in step S407), until the monitoring (polling) ends (YES in step S408), the processing of step S402 and subsequent steps is executed, and the next request packet is transmitted to the device 300A.

  If the response packet from the device is not received within a predetermined time (timeout) after transmitting the request packet as a result of the determination in step S403 (YES in step S404), monitoring (polling) is completed (step S404). Step S402 and subsequent steps are executed to send the next request packet.

  Returning to FIG. 2, when the client PC 100 receives the trigger notification from the device server 200, the client PC 100 starts a session with the device server 200 (step S <b> 215), and transmits / receives data to / from the device 300 </ b> A via the device server 200 ( Data communication relay) is started (step S216), and data transmission / reception is executed (step S217) (data communication control means). In step S213, the device server 200 may transmit a trigger notification to the client PC 100 and request a session start.

<Restart trigger detection process>
When the communication control unit 105 of the client PC 100 detects the end of data transmission / reception (device control) (for example, detection of the user's end operation) (step S218), the session with the device server 200 is disconnected. (Step S219). When the disconnection of the session is detected (second detection unit), the device server 200 starts trigger detection processing (step S220) and resumes monitoring (polling) of the device 300A (resumption unit). In step S213, even if there is no session start from the client PC 100 within a predetermined time after the trigger notification, the trigger detection process is similarly started (step S220), and the monitoring (polling) of the device 300A is resumed.

  As described above, according to the first embodiment, the control right (communication) for the device 300A is switched from the device server 200 to the client PC 100 by the trigger notification, and the client PC 100 returns to the device server 200 again when the session is disconnected. By switching, it becomes possible for the client PC 100 and the device 300A to perform data communication only when necessary, and when the data communication is completed, the device server 200 resumes monitoring of the device 300A.

<When request / response packets stored by client PC are used as definition files>
FIG. 5 is a sequence diagram used to describe the operation sequence of the device control system according to the second embodiment of the present invention. Between the client PC 100 and the device 300B connected to the device server 200, FIG. The process of transmitting and receiving data is shown.

  The device control system according to the second embodiment of the present invention has the same system configuration as that of FIG. 1, but unlike the first embodiment of the present invention described above, the client PC 100 The device 300B that detects the connection is polled, the request / response packets at that time are accumulated, and these are transmitted to the device server 200 as definition files.

  Specifically, the virtualization control unit 104 of the client PC 100 responds when the state does not change in the device 300B in accordance with an instruction from the application program 101, for example, “execution that the device 300B is not executing processing or control” In order to confirm the “standby state” response, polling is performed via the communication control unit 105, and the request / response packet transmitted and received at this time is stored in the data storage unit 106.

In the operation sequence of FIG. 5, in the trigger detection process of FIG. 4, each data pattern of the response packet from the device 300B and the response packet included in the definition file are compared. The difference from the first embodiment of the present invention is that a trigger notification is sent to the client PC 100 when the data patterns of the response packet and the response packet included in the definition file do not match (mismatch).

<Description of sequence operation>
In FIG. 5, the client PC 100 shows only the main configuration, and the operation sequence (steps S501 to S505) until the client PC 100 starts a session with the device server 200 is the same as the steps S201 to S205 in FIG. .

  Next, when the client PC 100 is instructed by the application program 101 to start polling for the device 300B for which connection is newly detected (step S511), the client PC 100 transmits and receives by polling via the device driver 103, which will be described later. The virtualization control unit 104 is instructed to start accumulation of packets (step S512) and to transmit a request packet for confirming the operation state of the device 300B (step S513).

  The virtualization control unit 104 sequentially transmits request packets for confirming the operation state of the device 300B (here, “execution standby state”) via the communication control unit 105 (step S514), and the request packet Is stored in the data storage unit 106 (step S515). In addition, the control unit 105 instructs the data storage unit 106 to accumulate the response packet received by the communication control unit 105 (step S516). This is repeated until a series of polling ends (steps S517 to S519) (creating means). Note that recording of the transmission / reception process (order, etc.) of these packets may be instructed.

<About packet data structure>
FIG. 6 is a diagram used for explaining the data structure of a request / response packet transmitted and received in the operation sequence of FIG.

  In FIG. 6, in the header part, “signature data” for identifying the protocol of this system, “message size” indicating the data size of the packet, “command ID” indicating the type of packet, device “Device information” (“vendor ID”, “product ID”, “serial number”) for identification is stored. Data corresponding to the type of packet (“command ID”) is stored in the data portion. Whether the packet is a request packet or a response packet is determined based on the difference in “command ID”.

  Returning to FIG. 5, when the virtualization control unit 104 is notified of the end of polling (step S <b> 520) from the application program 101, the virtualization control unit 104 is instructed to end the packet accumulation of FIG. 6 via the device driver 103. . The virtualization control unit 104 transmits the request packet and the response packet stored in the data storage unit 106 to the device server 200 as a definition file (second definition file) in FIG. 7 to be described later (step S521) (transmission unit).

<Definition file created with accumulated request / response packets>
FIG. 7 is a diagram used to explain the data structure of the request / response packet transmitted in the operation sequence of FIG. 5 and the definition file created by accumulating these data structures.

  The request packet and the response packet have the same data structure as the request / response packet described with reference to FIG. 6. The request packet or the response packet is discriminated based on the difference in “command ID”, and the data portion (USB transfer data). The data corresponding to the request or response is stored.

  For example, when n request packets are used in polling, n request packets and n response packets are stored in the data storage unit 106 and transmitted to the device server 200 as definition files.

<Trigger detection processing start to end>
Returning to FIG. 5, upon receiving the definition file (see FIG. 7) from the client PC 100 via the communication control unit 201, the device server 200 stores it in the data storage unit 106 as the definition file 205 (step S522).

  When the transmission of the definition file is completed, the session between the client PC 100 and the device server 200 is disconnected (step S523), and the trigger detection process of FIG. 4 is executed (steps S524 to S530).

  The device control unit 202 of the device server 200 starts polling similar to that of the client PC 100 using the definition file 205. That is, the trigger detection process of FIG. 4 for the device 300B is started.

  FIG. 4 is a flowchart showing a procedure of trigger detection processing executed by the device server 200 in FIG. The processing of FIG. 4 is basically the same as that described above as the first embodiment of the present invention, but differs in the following points.

  Specifically, according to the request data pattern included in the definition file 205, request packets are sequentially transmitted from the device control unit 202 to the device 300B via the communication control unit 201 (step S525 (step S402 in FIG. 4). )), A response packet is received from the device 300B (step S526 (step S403 in FIG. 4)).

The device control unit 202 compares each data pattern of the response packet from the device 300B and the response packet included in the definition file 205 (step S406 in FIG. 4), and determines whether or not they match. (First detection means, second determination means).

  For example, the threshold value is set and the number of bytes from the head of the packet is set in the determination process of whether or not the response packet from the device 300B matches each data pattern of the response packet included in the definition file 205. , And a method that determines that they do not match when they differ by a predetermined number of bytes (for example, 3 bytes or more), or the number of bytes that is different from any response packet compared to all n response packets If it is, it is performed by a method such as judging that they do not match.

  If the result of the determination process is “match” determination, it is determined that there is no state change, and the next request packet is transmitted to the device 300B. While it is determined as “match”, the request packets included in the definition file 205 are sequentially transmitted.

  If a response packet from the device is not received within a predetermined time after sending the request packet (timeout), the next request packet may be sent.

  In addition, when error information is returned from the device 300B in response to the request packet (for example, when the connection with the device 300B is disconnected), the trigger detection process is terminated. After the trigger detection process is completed, the definition file 205 may be deleted from the data storage unit, or stored in the data storage unit 203 and when the device 300B is connected again (matching between PID and VID) It is also possible to make it available for use.

  On the other hand, in the case of “mismatch” determination, it is determined that there is a state change in the device 300B and this state change (step S527) is detected, and a trigger notification (step S528) indicating this detection is sent via the communication control unit 201. The trigger information is transmitted to the client PC 100, and the trigger notification is received by the client PC 100 (step S529) (transmitting means, receiving means).

<Device control start to end>
Upon receiving the trigger notification from the device server 200, the client PC 100 starts a session with the device server 200 in response to the trigger notification (step S531) (session control means). The subsequent operation sequence (steps S532 to S536) is the same as the operation sequence (steps S216 to S220) of FIG.

  In this way, polling is performed on the device 300B in a state where no trigger notification is transmitted from the client PC 100, the request / response packets transmitted and received at this time are accumulated, and this is transmitted as a definition file to the device server 200. As a result, it becomes possible to monitor the change in state of the device (trigger detection processing).

<Determining whether a definition file exists>
In the second embodiment of the present invention, the client PC 100 may further include a function for determining whether or not the definition file suitable for the device 300 corresponding to the data storage unit 106 is held (stored). Good. In this case, a definition file created in advance according to the function (specification) of the device 300 (FIG. 3: the first embodiment of the present invention) or a definition created by polling a device of the same model as the corresponding device 300 When the file (see FIG. 7) is already held, the creation of the definition file by polling as described above is not executed, but the held definition file is transmitted to the device server 200 and is not held. Execute creation of definition file by polling.

  Note that the present invention is not limited to the above-described embodiments, and the embodiments described below are also possible, and can be appropriately changed without departing from the gist of the present invention.

<Sequence start timing>
In the operation sequences of FIGS. 2 and 5, it is described that the device individual information is acquired and the sequence is started when the device 300 is connected to the device server 200. For example, when the power of the device server 200 or the device 300 is turned on, when instructed from an application program of the client PC 100, when a predetermined connection operation is executed on one or both of the device server 200 and the device 300, the device Individual information may be acquired, and the operation sequence shown in FIG. 2 or 5 may be executed based on the device individual information.

<Execution program of definition file>
Further, the client PC 100 sends a simple program (for example, a shell, a script, etc.) that operates as a part of the trigger detection algorithm together with the definition file to the device server 200, and the device server 200 triggers using this definition file and the simple program. You may comprise so that a detection process may be performed.

  In this case, the trigger detection algorithm executes basic processing of trigger detection processing such as polling with the device 300 and trigger notification to the client PC 100 based on the definition file, and is specific to the device model ( It is configured to execute a part of the processing such as (specific) processing by a simple program. For example, since the condition for determining (detecting) the state change differs for each device model, this determination can be executed by a simple program.

  By configuring in this way, the trigger detection algorithm only needs to describe the basic execution procedure of the trigger detection process independent of the device model, and a simple program that executes the process according to the device model. It can be applied to a wide variety of devices just by creating.

<Another method for obtaining (installing) definition files / algorithms>
The device server 200 may acquire the definition file and the trigger detection algorithm not from the client PC 100 but from a portable storage medium.

<When the device server already holds the definition file / algorithm>
In addition, when the device server 200 has acquired and stored (installed) the corresponding definition file and the trigger detection algorithm when the device 300 of the same model was previously connected, the device server 200 does not perform acquisition and storage again. Also good. Further, the client PC 100 may be notified that the definition file and the trigger detection algorithm need not be transmitted.

<When there are multiple trigger notification destinations>
A system configuration in which a plurality of client PCs 100 are arranged is also possible. In this case, the device server 200 transmits a trigger notification to the plurality of client PCs 100, and permits the client PC 100 that has transmitted the session connection start request first to connect to the device 300 (data transmission / reception). That's fine. Alternatively, control may be performed so that only an arbitrary number of the client PCs 100 that have transmitted the connection start request are permitted to be connected to the device 300. In addition, when a specific one client PC 100 cannot receive a trigger notification due to power-off, failure, or the like, it may be controlled to transmit the trigger notification using another client PC 100 as an alternative destination. .

<About definition file and trigger detection algorithm>
The client PC 100 in FIG. 1 stores both the definition file 107 and the trigger detection algorithm 108 corresponding to the device 300, and the device server 200 receives the definition file 107 and the trigger detection algorithm 108 from the client PC 100 (configuration). However, the following method (configuration) is also possible.

  (1) The necessary trigger detection algorithm 108 is stored in the device server 200 in advance, and only the definition file 107 is stored in the client PC 100. In this case, the device server 200 receives only the definition file 107 corresponding to the model of the device 300 specified by the device information from the client PC 100.

  For example, access to the device server 200 is restricted due to software / hardware specifications / design, system operation / management reasons, etc., and trigger detection algorithm (program code) is received and executed This configuration can be applied when (or installation) is not possible. This configuration has an advantage that the trigger detection algorithm (program code) is stored in the device server in advance, so that tampering is difficult.

  (2) The device server 200 acquires a necessary trigger detection algorithm or definition file from the client PC 100 or the like only when the trigger detection algorithm or definition file corresponding to the specified device 300 model is not held. Also good.

  Further, the device server 200 or the client PC 100 may manage the trigger detection algorithm and the definition file to determine whether or not these additions / updates are necessary. With such a configuration, the device server 200 can acquire all or part of the trigger detection algorithm and the definition file only when the necessity for addition / update occurs.

  Further, as in the above-described embodiment, the device server 200 does not receive a trigger detection algorithm or definition file from the client PC 100, but the device server 200 accesses the client PC 100 to download (acquire). May be. In this case, the client PC 100 only has to notify the device server 200 that the corresponding trigger detection algorithm and definition file are held.

  By associating a plurality of definition files with one trigger detection algorithm described above, a plurality of devices 300 can be linked and controlled. For example, when the device A and the device B are controlled in cooperation, it is possible to perform control such that the operation of the device A is started after receiving the trigger notification from both devices.

  Note that the present invention is also applicable when a plurality of devices 300 of different models are connected to the device server 200. In this case, the device server 200 stores a definition file and a trigger detection algorithm corresponding to each device for each model (a plurality of sets are stored). Then, trigger detection processing is executed based on a combination of a trigger detection algorithm and a definition file suitable for each device, and a state change for each device 300 can be detected.

  Another object of the present invention is to supply a storage medium storing software program codes for realizing the functions of the above-described embodiments to a system or apparatus, and a computer (or CPU, MPU, etc.) of the system or apparatus. This can also be achieved by reading the program code stored in the storage medium and executing the processing.

  In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiments, and a computer-readable storage medium storing the program code constitutes the present invention. .

  Further, an OS (operating system) or the like running on the computer performs part or all of the actual processing based on an instruction of the program code, and the functions of the above-described embodiments are realized by the processing. May be.

  Further, after the program code read from the storage medium is written in a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer, the function expansion is performed based on the instruction of the program code. It includes the case where the CPU or the like provided in the board or the function expansion unit executes part or all of the actual processing and the above-described embodiment is realized according to the processing.

  In order to supply the program code, for example, a floppy (registered trademark) disk, a hard disk, a magneto-optical disk, an optical disk represented by CD or DVD, a magnetic tape, a nonvolatile memory card, a ROM, or the like is used. Can do. Alternatively, the program code may be downloaded via a network.

101 Client PC
102 Resident Module 103 Device Driver 104 Virtualization Control Unit 105 Communication Control Unit 106 Data Storage Unit 107 Definition File 108 Trigger Detection Algorithm 200 Device Server 201 Communication Control Unit 202 Device Control Unit 203 Data Storage Unit 204 Device Individual Information 205 Definition File 206 Trigger Detection algorithm
207 Definition file 300 (300A, 300B) Device 400 Connection cable 500 Network

Claims (13)

A device controller connected to a client device via a network and to which a device is to be locally connected,
First detection means for monitoring the state of the device using a definition file and a trigger detection algorithm for monitoring the state of the device, and detecting a change in the state of the device;
A transmission unit that transmits a trigger notification indicating detection of the state change to the client device when a state change of the device is detected;
Data communication control means for starting a session with the client device that has received the trigger notification and relaying data communication with the device that has detected the state change;
Second detection means for detecting that data communication with the device is terminated and the session with the client device is disconnected;
A device control apparatus comprising: a resuming unit that causes the first detection unit to resume monitoring of the state of the device when a session with the client device is disconnected. The definition file includes a first definition file that includes response information of the device when the state of the device changes.
The first detection means includes first determination means for determining whether or not the response information of the device matches the response information included in the first definition file,
The said transmission means transmits the said trigger notification to the said client apparatus, when the response information of the said device and the response information contained in the said 1st definition file correspond. Device controller. The definition file includes a second definition file including response information of the device when the state of the device has not changed,
The first detection means includes second determination means for determining whether or not the response information of the device matches the response information included in the second definition file,
The said transmission means transmits the said trigger notification to the said client apparatus, when the response information of the said device and the response information contained in the said 2nd definition file do not correspond. Device controller. 4. The device control according to claim 1, wherein the resuming unit causes the first detection unit to resume monitoring the state of the device when there is no response from the client device. 5. apparatus. When there is a session request from the client device to the device control apparatus while the first detection means is monitoring the device status, the first detection means monitors the device status. 5. The device control apparatus according to claim 1, wherein when the session is terminated and the session is disconnected, the resuming unit resumes monitoring of the state of the device. A device control method executed by a device control apparatus connected to a client apparatus via a network and to which a device is to be locally connected,
A first detection step of monitoring the state of the device using a definition file and a trigger detection algorithm for monitoring the state of the device and detecting a change in the state of the device;
A transmission step of transmitting a trigger notification indicating detection of the state change to the client device when the state change of the device is detected;
A data communication control step of starting a session with the client device that has received the trigger notification and relaying data communication with the device that has detected the state change;
A second detection step of detecting that data communication with the device is terminated and the session with the client device is disconnected;
A device control method comprising: a resumption step of causing the first detection unit to resume monitoring of the state of the device when a session with the client device is disconnected. The definition file includes a first definition file that includes response information of the device when the state of the device changes.
The first detection step includes a first determination step of determining whether or not the response information of the device matches the response information included in the first definition file,
The said transmission step transmits the said trigger notification to the said client apparatus, when the response information of the said device and the response information contained in the said 1st definition file correspond, The said client device is characterized by the above-mentioned. Device control method. The definition file includes a second definition file including response information of the device when the state of the device has not changed,
The first detection step includes a second determination step of determining whether or not the response information of the device matches the response information included in the second definition file,
The said transmission step transmits the said trigger notification to the said client apparatus, when the response information of the said device and the response information contained in the said 2nd definition file do not correspond. Device control method. 9. The device control according to claim 6, wherein the restarting step causes the first detection step to restart monitoring of the state of the device when there is no response from the client device. 10. Method. When there is a request for a session with the device control apparatus from the client device while the first detection step is monitoring the device state, the first detection step is to monitor the device state. The device control method according to claim 6, wherein when the session is disconnected and the session is disconnected, the restarting step restarts monitoring of the state of the device. A client device in which a device is connected via a network to a device control device to be locally connected,
Creating means for creating a definition file including request information and response information from the device stored when polling for confirming an operation state of a device locally connected to the device control apparatus;
Transmitting means for transmitting the created definition file to the device control apparatus;
Receiving means for receiving a trigger notification indicating detection of a change in the state of the device from the device control apparatus that has detected a change in the state of the device;
A client apparatus comprising: session control means for starting a session with the device control apparatus in response to the trigger notification received by the receiving means. A judgment unit for judging whether or not the device holds a definition file suitable for the device;
When it is determined that the definition file suitable for the device is held, the definition file is not created by the creation unit, and the held definition file is transmitted by the transmission unit. 11. The client device according to 11.   A device control system according to claim 1, wherein the device control apparatus according to claim 1 and the client apparatus according to claim 11 or 12 are connected to each other via a network.

Images