JPH0721105A - Information processing terminal device - Google Patents

Abstract

(57) [Abstract] [PROBLEMS] To provide an information processing terminal device capable of connecting an input device which is not provided with environmental control by a protocol such as MCR to a client server type information processing terminal device. [Structure] A means for recognizing input data from a non-regular input device such as a magnetic stripe reader or a bar code reader which is not provided with a control environment by the protocol of the information processing terminal device, and the input data is processed into data that can be processed by the protocol. A means for converting is provided.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a client-server type information processing terminal device, and more particularly to an X terminal or X workstation (hereinafter referred to as XWS) equipped with an X server program of an X window system.
It is about.

[0002]

2. Description of the Related Art X-terminals and XWS are typical examples of conventional client-server type information processing terminal devices.

The X terminal is a terminal device equipped with an X server and operates under the control of a client program (hereinafter referred to as an X client) operating on a host. X
The communication between the server and the host is realized by the X protocol defined by the X Window System (registered trademark of Massachusetts Institute of Technology).

The X Window System is intended to provide a control environment for a display device, a keyboard and a mouse.

For this reason, the X protocol defines only the data of the display device, the keyboard, and the mouse.
The input device of the X terminal is limited to the display device, the keyboard, and the mouse.

[0006]

The X terminal equipped with the X window system of the prior art aims to provide a control environment for a display device, a keyboard, and a mouse.
It does not provide a control environment for input devices other than the above, such as CR).

Therefore, no consideration is given to connecting an input device such as MCR to the X terminal and XWS, and there is a problem that an input device such as MCR cannot be connected to the X terminal and XWS.

An object of the present invention is to provide an information processing terminal device capable of connecting a non-specified input device which is not provided with environmental control by a protocol such as MCR to a terminal and a workstation adopting a client server system. It is in.

[0009]

In order to achieve the above object, information inputted from a non-specified input device such as a magnetic stripe reader, a bar code reader or the like which is not provided with a control environment by a protocol of an information processing terminal device is used as information. A means for causing the processing terminal device to recognize it and a means for converting the input data into data that can be processed by the protocol are provided.

Alternatively, there is provided means for converting input data from a non-standard input device such as a magnetic stripe reader or a bar code reader into data of an input device provided with a control environment by the protocol of the information processing terminal device.

Alternatively, a magnetic stripe reader whose control environment is not provided by the protocol of the information processing terminal device,
A unique protocol for processing data from non-standard input devices such as bar code readers is added.

Alternatively, while processing data of a non-standard input device such as a magnetic stripe reader or a bar code reader, a control that does not accept input of a keyboard, a mouse, etc., which is provided with a control environment by the protocol of the information processing terminal device Provide means.

[0013]

The means for causing the information processing terminal device to recognize the input data from the non-specified input device such as the magnetic stripe reader, the bar code reader or the like, which is not provided with the control environment by the protocol of the information processing terminal device, and the input data by the protocol. In the configuration provided with the means for converting into processable data, the X server of the X terminal and the XWS reads the MCR data, and delivers the key code indicating the MCR data as a key event before the delivery of the MCR data. .

When the MCR data delivery is completed, the MC
A key code indicating that the delivery of the R data is completed is delivered as a key event.

As a result, the delivered key event is MC
It can be shown that it is R data.

Further, the X server of the X terminal or the XWS retrieves the continuous MCR data as a character code for each character, and embeds the character code in the key code field of the key event for each character to thereby store the MCR data. It can be converted into a keyboard event.

As a result, the X server of the X terminal or the XWS can deliver the MCR data to the host side as a key event defined by the X protocol, and the host identifies the MCR data as keyboard data and processes it. Is possible.

Also, by converting the character code of the MCR data into the key code of the keyboard which the character code means, the X client can process the MCR data by the same means as the keyboard data, and it is delivered. It becomes possible to recognize that the key event is MCR data.

Further, by defining the key code and the key symbol indicating the MCR data independently of that of the keyboard, the MCR data and the keyboard data are not discriminated at the key code stage, and the MCR is converted at the stage when the key symbol is converted. Differentiate between data and keyboard data.

This makes it possible to omit the control for delivering the key code indicating the start and end of MCR data delivery, and
It is possible to deliver MCR data independently of the keyboard surface.

Then, in a configuration provided with means for converting input data from a non-specified input device such as a magnetic stripe reader or a bar code reader into data of an input device provided with a control environment by the protocol of the information processing terminal device. Removes the control for delivering the key code indicating the delivery start and delivery end of the MCR data, and delivers the MCR data to the X client side as keyboard data.

This enables the X client to process the MCR data as keyboard data using the standard X window system.

In a configuration in which a unique protocol for processing data of a non-specified input device such as a magnetic stripe reader or a bar code reader, which is not provided with a control environment by the protocol of the information processing terminal device, is added, the MCR data is MC specified for reading and X protocol independently
The MCR data is delivered based on the protocol for R (a completely independent protocol or a protocol obtained by extending the X protocol).

As a result, the X terminal or the X server of the XWS can deliver the MCR data to the X client.

Further, while processing the data of the non-specified input device such as the magnetic stripe reader and the bar code reader, the control that does not accept the input of the keyboard, the mouse, etc., which is provided with the control environment by the protocol of the information processing terminal device. In the configuration provided with the means, the input data from the keyboard is suspended or stopped while the MCR data is delivered.

As a result, the operator can perform keyboard input while avoiding the mixture of MCR data and keyboard data without being aware of the input / non-input of MCR data.

[0027]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS A detailed description will be given below by taking an example of connecting an MCR to an X terminal to which the present invention is applied.

An embodiment of the present invention corresponding to claim 1 will be described with reference to FIGS.

FIG. 1 is an overall configuration diagram of the host and the X terminal of this embodiment. In FIG. 1, 1 is a client program in the X window system. Reference numeral 2 denotes an X library in the X window system, which will be referred to as Xlib. An operating system 3 controls the host and is referred to as an OS. 4 is an X protocol defined by the X window system. 5 is an operating system for controlling the X terminal, which is also an OS
Is written. Reference numeral 6 is a central part of the X server program, which is a control unit that does not depend on the hardware or the OS, and is referred to as DIX. Reference numeral 7 denotes a control unit for controlling the display device, the keyboard, and the mouse, which includes hardware for interfacing with the input device and is referred to as DDX.

Here, 1 to 7 are components of a standard X window system. Reference numeral 8 denotes a control unit for controlling MCR, which includes hardware for handling MCR and is referred to as DCR for MCR. 9 indicates the system of the entire host. 10 indicates the system of the entire X terminal. 11 is an MCR.

FIG. 2 is a diagram for explaining the operation until the MCR data is delivered as a key event by the MDX for DCR 8 and DIX 6.

In FIG. 2, reference numeral 12 is a place for receiving and buffering MCR data in the DCR 8 for MCR.
This is referred to as a receive buffer. 13 is M from the receiving buffer
This is a part for controlling CR data to be fetched one character at a time and delivered to the DIX as keyboard data. This is referred to as an event handling part.

Reference numeral 14 is MCR data read from the MCR. Reference numeral 15 is a key code defined in advance to indicate the start of MCR data delivery, which will be referred to as a start code. 1
6 is the first character code of the MCR data, and is referred to as character code (1). Reference numeral 17 is a final character code of the MCR data, which is referred to as a character code (72). Reference numeral 18 denotes a key code that is defined in advance as an end of MCR data delivery, and will be referred to as an end code.
Reference numeral 19 is a header portion indicating a key event in the X protocol.

The X terminal and X workstation (XWS) of this embodiment are provided with a DDX 8 for MCR for converting MCR data into a key event in the conventional X terminal and XWS.

MCR read from DDX8 for MCR
The data is stored in the reception buffer 12. Here, M
This is an example when the CR data 14 is continuous data consisting of 72 characters.

When the event handling unit 13 detects the reception end of the MCR data 14, it generates a start code 15 and delivers it to the DIX 6 as a key code.

Next, the event handling unit 13 takes out the 7-bit character code (1) 16 and
It is delivered to DIX6 as a key code by adding 1-bit padding. Similarly, the character codes of MCR are sequentially processed in the same manner, and the character code (72) 1
After finishing the process of 7, the end code 18 is generated and delivered to the DIX 6 as a key code.

The DIX 6 takes in the delivered 8-bit start code, character code, and end code as the key code portion of the key event defined by the X protocol, attaches the header 19 to generate a key event packet, Deliver to the host side sequentially.

Then, the client program 1 is X
When the start code is detected from the key event delivered via the lib2, the key event is recognized as an MCR character code and processed until the end code is detected.

As a result, the X terminal can deliver the MCR data 14 as a key event for each character, and the client program 1 recognizes that the MCR data is the MCR data by the start code and the end code.
It becomes possible to process the character code of the R data.

That is, the feature of this embodiment is that the start code indicating the start of MCR data delivery and the end code indicating the end of MCR data delivery are specified in advance, and the MCR
A mechanism for dividing data into character codes and embedding it in the key code field of the key event is provided, and the MCR data is read by delivering the start code, the end code, and the character code of the MCR data as the key event. It means that was made possible.

Next, another embodiment of the present invention corresponding to claim 1 will be described with reference to FIGS.

FIG. 3 shows the MDX DDX8 and DIX6.
FIG. 9 is a diagram for explaining an operation until a character code of MCR data is converted into a key code and is delivered as a key event by.

In FIG. 3, reference numeral 20 denotes a table for converting a character code into a key code, which will be referred to as a key code conversion table. 21 is a key coded table 20
The key code corresponding to the character code (1) converted by is referred to as a key code (1). Reference numeral 22 is a key code corresponding to the character code (72) converted by the key encoding table 20 and is referred to as a key code (72).

As described in the above embodiment, the MCR data is delivered as a key event between the start code and the end code.

In this embodiment, by providing the key coding table 20, the character code is converted into a key code corresponding to the keyboard and delivered.

Client program 1 has start code 1
5 and the end code 18 make it possible to recognize that the MCR data has been delivered as a key event.

The client program is MCR.
Since the character code of is converted into a key code corresponding to the keyboard and delivered, Xlib2 uses the function provided by the X window system to send M
The data from the CR can be processed.

That is, the feature of this embodiment is that by providing a key coding table for converting the character code of the MCR data into a key code, the MCR data is key coded and then a plurality of key events are generated as a host event. And the information for identifying the MCR data and the keyboard data to the host.

Next, another embodiment of the present invention corresponding to claim 1 will be described with reference to FIG. FIG. 4 is a block diagram of key symbol values indicating MCR data in this embodiment.

In FIG. 6, reference numeral 23 denotes an MCR identifying section, which indicates that it is MCR data. 24 is an MCR data part which is the MCR data itself.

The X terminal and the host predefine the key code and the key symbol indicating the MCR data independently of the key symbol of the keyboard. The X terminal delivers the MCR data as a key event by the procedure described in the above two embodiments.

However, in the present embodiment, the start code 15 and the end code 18 for identifying the MCR data by the key symbol need not be delivered. The client program 1 obtains a key symbol from a key event using a function provided by Xlib.

As shown in FIG. 4, the key symbol is composed of an MCR identifying section 23 which indicates MCR data and an MCR data section 24 which is the MCR data itself.

The client program 1 recognizes that the data delivered by the MCR identification unit 27 of this key symbol is MCR data, and the MCR data unit 28
To process.

That is, the feature of this embodiment corresponding to claim 1 is that the key symbol corresponding to the MCR data is provided independently of the key symbol of the keyboard.
The CR data is delivered.

As a result, the X terminal can deliver the MCR data without depending on the keyboard surface, and it is not necessary to deliver the start code and the end code indicating the MCR data.

Next, an embodiment of the present invention corresponding to claim 2 will be described with reference to FIGS.

In an embodiment corresponding to claim 1,
It has been described that MCR data is converted into a key code and delivered to the client program 1. At that time, a start code 15 and an end code 18 indicating that it is MCR data
However, in the embodiment corresponding to claim 2, by not delivering the start code 15 and the end code 18, the MCR data is recognized as input data from the keyboard and delivered to the client program. is there.

As a result, the MCR data delivered to the client program is delivered as input data from the keyboard, and the MCR data can be delivered to the host that does not recognize the start code and the end code.

That is, the feature of the present embodiment is that the start code and the end code are not generated, and a mechanism for converting the character code of the MCR data into a key code and delivering it as a key event is provided. Instead of being recognized as MCR data, it is recognized as keyboard data for which a control environment is provided by the protocol and delivered to the host.

Next, an embodiment of the present invention corresponding to claim 3 will be described with reference to FIG.

FIG. 5 is an overall configuration diagram of the host and X terminal system of this embodiment. In FIG. 5, reference numeral 25 is provided for the purpose of delivering the MCR data delivered from the X terminal to the client program 1. This is referred to as an MCR library. 26 is a protocol defined in advance between the X terminal 10 and the host 9 for handling MCR data, and is referred to as MCR protocol. 27
Is for receiving data from the MCR 11 and delivering MCR data based on the MCR protocol 26, and is referred to as an MCR driver.

The MCR driver 27 includes MCR 11 to MCR.
The CR data is received and the MCR data is delivered to the host based on the MCR protocol 26. Here, the MCR protocol 26 includes the MCR driver 27 and the MCR library 2
5 may be independent of the X protocol, or may be an extended protocol of the X protocol.

The MCR library 25 is a collection of information for receiving the MCR data delivered based on the MCR protocol 26 and further delivering it to the client program 1.

As a result, the X terminal can deliver the MCR data to the host independently of the X window system, and the client program processes the MCR data independently or partially of the X window system. It becomes possible to do.

That is, the feature of this embodiment is that the MCR data can be delivered to the client program by providing the MCR protocol independent of the X protocol.

Next, an embodiment of the present invention corresponding to claim 4 will be described with reference to FIGS.

FIG. 6 is a block diagram of an X terminal in an embodiment corresponding to claim 4. In FIG. In FIG. 6, 28 is an MCR
A delivery control unit that controls delivery of data and keyboard data.

The X terminals are MDX DDX7 and DDX8.
The key event generated by is taken into the delivery control unit 28. When the delivery control unit 28 receives the start code 15 from the MCR DDX 8, the delivery control unit 28 sets the end code 18 to DIX.
The input data from the DDX 7 is buffered or discarded until the data is delivered to the D6.

As a result, the key event delivered between the delivery of the start code 15 and the delivery of the end code 18 is only MCR data, and keyboard data is prevented from being erroneously mixed during MCR data delivery. To be

That is, the feature of this embodiment is that the X terminal is provided with a control unit for stopping or holding the keyboard data delivery during the MCR data delivery, whereby the MCR data and the key data are delivered together to the client program. Is to prevent that.

That is, as shown in each of the above embodiments, according to the present invention, it is possible to connect an input device which is not provided with environmental control by a protocol such as MCR to a terminal and a workstation which employs a client server system, It is possible to provide an environment for delivering the data of the input device to the X client.

The case where the MCR is connected to the X terminal and the X terminal equipped with the X window system has been described above with reference to the embodiments corresponding to the first to fourth aspects. It does not depend on the amount of data, and is not limited to MCR, and can be applied to all input devices such as bar code readers.

[0075]

As described above, according to the present invention, X
Read the MCR data to the terminal or X server of XWS,
Distributing the start code and the end code and delivering the MCR data to the host by using the key event defined by the X window system by providing a mechanism for controlling the delivery of the character code of the MCR data as a key event. It is also possible to notify the host that the delivered key event is MCR data.

As a result, the host can leave the processing for handling MCR data to the client program, and the MCR can be processed without modifying the X window system.
There is an effect that it is possible to support an attached X terminal or an XWS with MCR.

By converting the MCR data into key code data and delivering the key code data to the host, the client program can process the delivered MCR data using the function provided by X1ib of the X window system. Moreover, there is an effect that the data can be recognized as the input data from the MCR.

Further, by identifying the MCR data and the keyboard data by the key symbol, the MCR data can be delivered without issuing a key code indicating the start and end of delivery.
There is an effect that it is possible to notify that it is CR data.

Further, the character code of the MCR data can be converted into a key code independently of the keyboard board surface, and the data can be delivered independently of the keyboard board surface.

Further, by not delivering the key code indicating the start and end of delivery of the MCR data, the host does not need to recognize the key code.

As a result, the X client can handle the MCR data as keyboard data.
There is an effect that CR data can be delivered.

By providing a protocol for handling the MCR data independently of the X protocol, it is possible to deliver the MCR data to the host in an arbitrary format.

Further, there is an effect of preventing the mixture of MCR data and keyboard data by controlling delivery of MCR data and keyboard data on the X terminal side.

Therefore, according to the present invention, it is possible to provide an information processing terminal device capable of connecting an input device which is not provided with environment control by a protocol such as MCR to the client server type information processing terminal device.

[Brief description of drawings]

FIG. 1 is an overall configuration diagram of an X terminal and a host according to an embodiment of claim 1.

FIG. 2 is a diagram for explaining an operation according to an embodiment of claim 1;

FIG. 3 is a diagram for explaining an operation according to an embodiment of claim 1;

FIG. 4 is a block diagram of a key symbol showing MCR data according to an embodiment of claim 1;

FIG. 5 is an overall configuration diagram of an X terminal and a host according to an embodiment of claim 3.

FIG. 6 is a configuration diagram of an X terminal for explaining an operation according to an embodiment of claim 4;

[Explanation of symbols]

1 ... Client program, 2 ... X1ib, 3 ... Host side OS, 4 ... X protocol, 5 ... X terminal side OS, 6 ...
DIX, 7 ... DDX, 8 ... DCR for MCR, 9 ... Host, 10 ... X terminal, 11 ... MCR, 12 ... Receive buffer, 13 ... Event handling unit, 14 ... MCR data, 15 ... Start code, 16 ... Charactor Code (1), 17 ... Character code (72), 18 ... End code, 19 ... Header, 20 ... Key coding table,
21 ... Key code (1), 22 ... Key code (72),
23 ... MCR identification part, 24 ... MCR data part, 25 ... M
CR library, 26 ... MCR protocol, 27 ... MC
R driver, 28 ... Delivery control unit.

Claims (4)

[Claims] 1. A client-server type information processing terminal device, which processes input data from a non-standard input device such as a magnetic stripe reader or a bar code reader which is not provided with a control environment by a protocol of the information processing terminal device. An information processing terminal device, comprising: a device for recognizing the terminal device; and a device for converting input data into data processable by the protocol. 2. In a client-server type information processing terminal device, input data from a non-standard input device such as a magnetic stripe reader or a bar code reader, which is not provided with a control environment by the protocol of the information processing terminal device, is transferred to the protocol. An information processing terminal device comprising means for converting control environment into data of an input device provided. 3. A client-server type information processing terminal device, which is unique to process data of a non-specified input device such as a magnetic stripe reader, a bar code reader, etc. which is not provided with a control environment by the protocol of the information processing terminal device. An information processing terminal device characterized in that a protocol is added. 4. A client-server type information processing terminal device, while processing data of a non-regular input device such as a magnetic stripe reader or a bar code reader which is not provided with a control environment by the protocol of the information processing terminal device. The information processing terminal device according to claim 1, further comprising a control unit that does not receive an input of a keyboard, a mouse, or the like provided with a control environment by the protocol.