JP2000242594A - Information transmission system for terminal device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To easily produce an application and also to easily change the application when the number of devices is increased or decreased. SOLUTION: The requested application to be processed that is read out of a magnetic disk device 4 and stored in a main storage 3 is called out and started by a CPU 2. Then the started application notifies a management module having a prescribed table of a processing request and the processing contents information. The management module writes the processing contents into a table and then asks the first device 5-1 to perform its processing according to the processing contents information. Receiving the notification showing the end of the processing, the management module asks the next device 5-2 to perform its processing according to the processing contents information, and the management module repeats the said operation.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an information transmission system for a terminal device comprising a host device and a plurality of processing devices connected to the host device.

[0002]

2. Description of the Related Art As a conventional terminal device, a plurality of processing devices (hereinafter, referred to as devices) such as a touch panel display, a printer, and a card reader are connected to a host device including a central processing unit and a storage device. Some devices execute processing by notifying the device of processing request information from the host device to operate the device, or notifying the host device of various event information from the device.

In such a terminal device, an application corresponding to the content to be processed is prepared in a host device, and based on the application, transmission of processing request information to each device and transmission of event information from each device are performed. Is performed. FIG. 10 is a configuration diagram of software in the case of sequentially requesting a device to perform processing based on an application of a higher-level device and operating the device.

In this case, the application first notifies the first device of the processing request and the information of the processing contents, and thereby operates this device. When the operation of the device is completed and the end notification is sent from the first device to the application, the application notifies the next device of the processing request and the information of the processing content, thereby operating this device.

[0005] According to such a procedure, a plurality of devices are notified of processing requests and information of processing contents, and are operated. FIG.
FIG. 3 is a diagram illustrating a software concept when receiving event information from a device determined in advance based on an application of a higher-level device. In this case, assuming that the application receives predetermined event information from, for example, the first to third devices among the n-th device, the application is transmitted from any of the first to third devices. Each time event information is received, it is determined whether or not event information has been received from all other devices.If it is determined that event information has not been received from all devices, the next information is waited for. If it is determined that the event information has been received from the device, the receiving process ends.

[0006]

However, the above-mentioned prior art has the following problems. That is, FIG.
In the processing request described in (1), it is necessary to write the processing contents into the application for each device to be operated, and therefore, there is a problem that it takes time to create the application.

[0007] Further, in receiving information according to FIG. 11, every time information is received from each device, it is necessary for the application to check whether or not information has been received from all the other devices. It is necessary to provide the application with a process of repeatedly performing the above, so that there is a problem that the creation of the application is troublesome.

In addition, in both the cases of FIGS. 10 and 11, if the number of devices is increased or decreased due to a change in function or the like, it is necessary to significantly modify the application. In particular, if the number of devices is increased, the entire application must be changed. Work becomes difficult. Therefore, an object of the present invention is to provide a terminal device information transmission system that can solve these problems.

[0009]

Therefore, the present invention comprises a host device and a plurality of processing devices connected to the host device, and a plurality of processing devices based on a notification from an application prepared in the host device. In the information transmission system of a terminal device that operates, a management module having a table is interposed between the application and a plurality of processing devices, and a processing request to a processing device and processing content information are notified from the application to the management module. The management module writes processing content information in a table, and sequentially requests the plurality of processing devices to perform processing based on the processing content information.

[0010]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of an information processing system according to the present invention will be described below with reference to the drawings. FIG. 1 is a functional block diagram showing an embodiment. Referring to FIG. 1, reference numeral 1 denotes a host device, which comprises a central processing unit (CPU) 2, a main storage device 3, a magnetic disk device 4, and the like.

Reference numerals 5-1 to 5-n denote devices (processing devices). Each of the devices 5-1 to 5-n executes various processing based on a processing request of an application to be described later, and various information for the application. Is connected to the central processing unit 2 via the bus 6 together with the main storage device 3 and the magnetic disk device 4. These devices 5-1
Although 5-n is not limited, typical ones include, for example, a touch-panel display, a card reader / writer, a printer, a scanner, and various sensors.

On the other hand, the main storage device 3 is a memory such as a RAM, and stores data and programs as required. The magnetic disk device 4 is an external storage means for storing various data and various programs. The central processing unit 2 also stores a table and the like used by an application to be described later.
Is stored in the main storage device 3 and the devices 5-1 to 5-n are controlled based on the application stored in the main storage device 3.

FIG. 2 is a block diagram of software for processing requests operating on the system shown in FIG. 1. As shown in FIG. 2, the software uses an application and a plurality of devices 5-1 to 5-n. And the management module 7 is interposed between them. Here, the management module 7 transmits to the devices 5-1 to 5-n according to the processing request notification from the application and the information of the processing content.
, The application collectively recognizes the devices 5-1 to 5-n without individually recognizing the devices 5-1 to 5-n.
It is possible to output information on the processing contents for .about.5-n.

That is, the management module 7 has a role to make the application seem to be one device 5-1 to 5-n. Next, the operation of the above-described embodiment will be described. FIG. 3 is a flowchart showing a processing procedure when a device is operated in response to a processing request from an application, and will be described with reference to FIGS. 1 and 2 in accordance with the steps indicated by S in FIG.

First, in the host device 1, the central processing unit 2
As a result, the application of the processing request read from the magnetic disk device 4 into the main storage device 3 is called and activated, and the activated application notifies the management module 7 having a predetermined table of the processing request together with the processing content information ( S1). This processing content information includes a device name and a processing identifier. When the management module 7 receives the processing content information, it writes this in a table.

FIG. 4 is a diagram showing the contents of the table at this time, in which device names and process identifiers are written in areas divided for each index. Here, the device name is a character string indicating the device. The process identifier is a code representing the operation performed by the device. For example, “1” requests the driver of the device 5-1 to prepare for initial settings, and “2” indicates the device 5-2. Is a card reader or scanner, it requests reading of data from a card or a document.

From the contents of this table, the management module 7
Identifies the number of devices and the device name (S2). On the basis of the identification result, the management module 7 requests the device 5-1 corresponding to the first index to perform a process based on the process identifier (S3). And device 5-1
Is notified to the management module 7 of the end of the processing operation,
The management module 7 requests the device 5-2 corresponding to the second index to execute a process based on the process identifier (S4).

In the same manner, other devices are operated based on the contents of the table. Note that the number and order of devices that operate in this series of processing are not limited, and are determined by the contents of an application created in advance, and it is optional to operate the same device twice or more. . By executing the information transmission as described above, the application can be used for one or more devices.
It can be processed to handle two devices.

In other words, when notifying a processing request and information of the processing content to two or more devices, the application may notify the management module of the processing content information in a lump, and then the processing to each device may be performed. The request can be shared by the management module. Therefore, it is not necessary to write the processing contents to the application for each device to be operated, which makes it easy to create the application and minimizes the modification of the application even when the number of devices is increased or decreased due to a function change or the like. The application can be easily changed even when the number of devices is increased.

FIG. 5 is a block diagram of software for receiving event information. In this case, the management module 7 receives event information from a plurality of devices based on a notification from the application, and thereafter transmits the event information to the application. ing. That is, also in this case, the management module 7 has a role of making the application appear to have a plurality of devices.

FIG. 6 is a flowchart showing a processing procedure when event information notified asynchronously from a plurality of devices is received. The processing procedure will be described with reference to FIGS. 1 and 2 in accordance with the steps indicated by S in FIG. First, in the higher-level device 1, an application for receiving event information read from the magnetic disk device 4 to the main storage device 3 by the central processing unit 2 is called from the main storage device 3 and activated. To notify the information of the event information reception contents.

This information comprises a device name and an event type. When the management module 7 receives this information, it writes this information in a table and registers it (S1). FIG. 7 is a diagram showing the contents of the table at this time. The device name and the type of event to be received are written in areas divided for each index. Here, the device name is a character string indicating the device.

The event type is a code representing event information to be received. For example, “1” indicates information on the end of operation from the device 5-1 and “2” indicates that the device 5-2 is a printer or the like. In the case of, it indicates attention information such as progress or running out of paper. After that, the management module 7 waits for the event information notified from the devices 5-1 to 5-n, and
-n (S2), the event information is compared with the contents of the table, and if the event information is the corresponding event information notified from the corresponding device, the received information is written. It is determined whether or not the event information has been received and whether or not the processing has ended (S3).

Here, if there is event information that has not been received yet and it is determined that the event information has not been received, the management module 7 continues to wait for the event information to be notified. Is notified to the application (S
4). By executing the processing as described above, the application can process two or more devices so as to handle one device.

That is, when an application receives event information from two or more devices, it only needs to receive an end notification via the management module, and the actual reception of event information can be shared by the management module. This eliminates the need for the application to have a process of repeatedly referencing data, making it easier to create the application and minimizing the modification of the application even if the number of devices is increased or decreased due to functional changes. The application can be easily changed even when the number of devices is increased.

FIG. 8 is a block diagram of software for requesting a device for processing and receiving event information. As shown in FIG. 8, in this software, a device comprising processing content information and information on the content of event information reception is provided. The information file is stored in the magnetic disk device 4, and the management module 7 fetches device information according to a notification from the application and executes the process.

FIG. 9 is a flowchart showing a processing procedure in the case of performing both a processing request to a plurality of devices and receiving event information. FIG. 9, FIG. 2, FIG. This will be described with reference to FIG. First, in the host device 1, the application read from the magnetic disk device 4 into the main storage device 3 is called by the central processing unit 2 and started, and the started application manages a processing request for the device and a request for receiving event information. Notify module 7. (S1) Upon receiving a request from an application, the management module 7 calls up device information from a device information file and writes it in a table.

This device information is, for example, shown in FIGS.
Is the information shown in FIG. From the contents of this table, the management module 7 identifies the number of devices and device names for processing requests (S2). Based on the identification result, the management module 7 sends information based on the processing identifier to one of the devices 5-15-n to be operated, as in the case of FIG. 3, and sequentially operates the devices (S3).

Thereafter, the management module 7 sets the device 5-1.
When the management module 7 receives the event information from any of the devices 5-1 to 5-n (S4), the management module 7 checks the event information with the contents of the table. If it is the relevant event information notified from the relevant device, the received information is written, and it is determined whether or not all the event information has been received, and it is determined whether or not the process is completed (S5).

Here, if there is any event information that has not yet been received and it is determined that the event information has not been received, the management module 7 will continue to wait for the event information to be notified. Is notified to the application (S
6). In the above-described example, the notification of the processing request to the device and the notification of the event information reception request are simultaneously performed to the management module and are executed as a series of processes. Alternatively, information for receiving event information can be extracted from the device information file and performed as independent processing.

By executing the processing as described above, the application only needs to notify the management module of the processing request, and the processing of each device and the reception of information from the device are created separately from the application. Since the management module performs the operation based on the device information file, the number of devices can be increased or decreased without changing the application.

[0032]

As described above, according to the present invention, a management module is interposed between an application and a plurality of processing devices, and a request for processing to each device (processing device) by this management module and a request from each device for processing. In order to receive the event information, the application may notify the management module of the processing content information or the event information reception content information in a lump, and the subsequent management can be shared by the management module.

Therefore, it is not necessary to write the processing contents into the application for each device to be operated, or to provide the application with a process of repeatedly referring to data, thereby facilitating the creation of the application and changing the functions. For example, even when the number of devices is increased or decreased, the modification of the application can be minimized, and the effect of easily changing the application even when increasing the number of devices can be obtained.

[Brief description of the drawings]

FIG. 1 is a functional block diagram showing an embodiment of the present invention.

FIG. 2 is a configuration diagram of software for a processing request in the embodiment.

FIG. 3 is a flowchart illustrating a processing procedure when a device is operated according to a processing request.

FIG. 4 is a diagram showing the contents of a table at the time of processing request.

FIG. 5 is a configuration diagram of software for receiving event information in the embodiment.

FIG. 6 is a flowchart illustrating a processing procedure for receiving event information.

FIG. 7 is a diagram showing the contents of a table when receiving event information.

FIG. 8 is a configuration diagram of software for receiving a process request and event information in the embodiment.

FIG. 9 is a flowchart illustrating a processing procedure of a processing request and event information reception.

FIG. 10 is a configuration diagram of conventional software for processing requests.

FIG. 11 is a configuration diagram of conventional software for receiving event information.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Upper apparatus 2 Central processing unit 3 Main storage unit 4 Magnetic disk unit 5-1 to 5-n device (processing equipment) 7 Management module

Claims (3)

[Claims] 1. An information transmission system for a terminal device comprising a host device and a plurality of processing devices connected to the host device and operating the plurality of processing devices based on a notification from an application prepared in the host device. When a management module having a table is interposed between the application and the plurality of processing devices, and when a processing request to the processing device and processing content information are notified from the application to the management module, the management module stores the processing content information in the table. Writing, and sequentially requesting the plurality of processing devices to perform processing based on the processing content information. 2. A terminal device comprising a host device and a plurality of processing devices connected to the host device and receiving various event information from the plurality of processing devices based on a notification from an application prepared on the host device. In the information transmission system, when a management module having a table is interposed between the application and the plurality of processing devices, and when a request for receiving event information from the processing device and reception content information are notified from the application to the management module, the management module When the management module refers to the reception content information of the table each time receiving the event information from each processing device, and receives all the event information corresponding to the reception content information of the table, , The receiving end An information transmission system for a terminal device, which notifies an application. 3. A processing system comprising a host device and a plurality of processing devices connected to the host device, wherein the processing device operates a plurality of processing devices based on a notification from an application prepared on the host device side and a plurality of processing devices. In an information transmission system of a terminal device that performs at least one of a process of receiving various event information, a management module having a table is interposed between the application and a plurality of processing devices, and a process content information for the processing device and a processing module. A file comprising received content information to be received is provided, and when at least one of a processing request to a processing device and reception of event information from the processing device is notified from the application to the management module, the management module executes the file based on the notification. Processing information and received content from Writing the table is taken out at least one of broadcast, information transmission system of the terminal apparatus which is characterized in that at least one of receipt of the processing request and event information to the processing apparatus based on the contents of this table.