JPH0449740A - Non-procedure communication control method - Google Patents

Abstract

PURPOSE:To perform the transmission/reception of all the data including binary code data without generating a transmission error by comprising a method of a non-procedure communication application task, a non-procedure control task, and a 232C driver. CONSTITUTION:When a transmission request is received from a host computer 7a, it is informed to a non-procedure communication control task 3a via an RS-232C driver 4a. The task 3a attaches a transmission block header (SOH), a block number (01, FE), and a check sum on (data 1), and transmits the (data 1) to the host computer 7a via the driver 4a. By employing such configuration, the transmission of the binary code data of a object code and document file data, etc., can be performed without generating the transmission error such as data change or data loss, etc., on data transmission.

Description

DETAILED DESCRIPTION OF THE INVENTION [Field of Industrial Application] The present invention relates to a non-procedural communication control method, and more particularly to a non-procedural communication control method having an error detection function.

[Conventional technology]

Conventional non-procedural communication control methods are error-free in data transmission and cannot detect errors.

[Problem to be solved by the invention]

The conventional non-procedural communication control method described above has the following drawbacks because it cannot detect errors in data transmission, even though it can be easily connected to a host computer over a public communication network using an intelligent modem. Ta.

■Even if data is garbled or lost during data transmission, it is not possible to detect errors, so the reliability of data transmission is extremely poor.

■Since it is not possible to transmit binary code data such as object codes and document file data, it can only be used for data transmission within a very narrow range.

[Means to solve the problem]

The non-procedural communication control method of the present invention is a non-procedural communication control method for a personal computer connected in a non-procedural communication method within a public communication network, and includes a non-procedural communication application task that operates according to instructions from an operator, and an error detection method. It consists of a non-procedural communication control task that controls a functional non-procedural communication protocol, and an R8-232C driver that controls the R8-232C board and transmits data, and sends and receives all data including binary code data. It consists of

〔Example〕

Next, the present invention will be explained with reference to the drawings.

FIG. 1 is a block diagram showing the configuration of an embodiment of the present invention and a control method of a non-procedural communication protocol having an error detection function.

The present invention includes a non-procedural communication application task 2a that operates according to instructions from an operator, a non-procedural communication control task 3a that controls a non-procedural communication protocol having an error detection function, and an R8-23 on a personal computer la.
R8-232 that controls the 2C board 5a and transmits data
C driver 4a, and realizes a non-procedural communication control method having an error detection function. When a NAK (request for transmission) is received from the host computer 7a through the public communication network 6a, the rNAK (request for transmission) is notified to the non-procedural communication control task 3a through the RS-232C driver 4a, and this non-procedural communication control is performed. Task 3a is
rNAK (transmission request)" is notified to the non-procedural communication application 1 task 2a as a transmission start request (processing L
A).

Upon receiving this transmission start request, the non-procedural communication application control task 2a starts transmission and requests the non-procedural communication control task 3a to request the transmission of "data 1". The non-procedural communication control task 3a adds the transmission block header rsOHJ and block number r01. to "data 1". Add FEJ and checksum, and write R in the data format shown in Figure 8(a).
Sends "data 1" to the host computer 7a through the S-232C driver 4a (processing 2A), and sends rACK (OK)J from the host computer to the R8-23.
After receiving it through the 2C driver 4a, it notifies the non-procedural communication application task 2a that the transmission of "data 1" has been completed. The non-procedural communication application task 2a requests the non-procedural communication control task 3a to transmit "data 2" as the next data transmission process. The non-procedural communication control task 3a adds a transmission block header "80" to "data 2".
(J, block number r02.FDJ, and checksum are added, and "data 2" is transmitted to the host computer 7a through the RS-232C driver 4a in the data format shown in FIG. 8(b) (processing 3A).

rACK (OK) J from host computer 7a
Received through the 8-232C driver 4a (processing 4
A) After that, go to the non-procedural communication application Keiron Task 2a.
Notify the completion of transmission of "Data 2". The non-procedural communication application task 2a performs rEOT (
A request is made to the non-procedural communication control task 3a to send "rEOT (end of transmission)" to the host computer 7a through the R8-232C driver 4a (processing 5A).

Next, the non-procedural communication application cage task 2a sends an rNAK requesting start of transmission from the host computer 7a.
(send request)" to the non-procedural control task 3a, the non-procedural communication control task 3a transmits rNA to the host computer 7a through the R8-232C driver 4a.
Process 6A) to send "Data A" in the data format shown in FIG. 8(e) from the host computer 7a through the R8-232C driver 4a (Process 7A).゜After checking the FEJ and checking the checksum, the transmission block header rsOHJ, block number, and checksum are deleted, and then the non-procedural communication application task 2a is executed.
Notify "Data A" to. As the next reception process, the non-procedural communication application cage pin task 2a requests the non-procedural communication control task 3a to send rACK (OK)J notifying completion of reception preparation. The non-procedural communication control task 3a is r
Process 8A) to send ACK (OK)J to the host computer 7a through the RS-232C driver 4a;
From the host computer, the data format shown in Figure 8(f) is
When data B'' is received through the R8-232C driver 4a (processing 9A), block number rQ2. After checking the FDJ and checking the checksum, the transmission block header rsOH, block number and checksum are deleted, and then the non-procedural communication application 1 task 2a is notified of ``data B''. The non-procedural communication application cage bin task 2a performs the following data reception processing:
Requests the non-procedural communication control task 3a to send rACK (OK)J to notify reception completion, and sends rAC to the host computer 7a through the R8-232C driver 4a.
K(OK)J is transmitted (processing 10A).

The non-procedural communication control task 3a is performed by the host computer 7a.
rEOT (end of transmission) through the R8-232C driver 4a, the non-procedural communication application cage task 2a is notified of the end of transmission, and the non-procedural communication application cage NSO task 2a ends the reception process (processing 1
1A).

FIG. 2 is a block diagram showing an error detection protocol control method when an error is detected in transmission data according to this embodiment.

The non-procedural communication control task 3b sends a NAK (transmission request) from the host computer 7b to the R8-232C driver 4.
When the data is received through the process IB (processing IB), the non-procedural communication application task 2b is notified of the start of transmission. The non-procedural communication application task 2b starts the transmission process and
A request to send "Data 1" is made to the non-procedural communication control task 3b.

The non-procedural communication control task 3b adds a transmission block header rsOHJ, block number "01, FEJ, and checksum" to "data 1", and sends it to the host computer 7b through the R8-232G driver 4b in the data format shown in FIG. 8(a). After transmitting "data" (processing 2B) and receiving rACK (OK) J from the host computer 7B, the non-procedural communication application task 2b is notified of the completion of transmission of "data 1" (processing 3B).

The non-procedural communication application task 2b issues a transmission request for "data 2" to the non-procedural communication control task 3b as the next data transmission process. The non-procedural communication control task 3b is “
Add the transmission block header rsOHJ, block number “o3°FDJ” and checksum to “data 2”, and
In the data format of figure (C) (block number 03 is incorrect)
When "Data 2" is transmitted to the host computer 7b through the 8232C driver 4B and rNAK(NG)J indicating error detection is received from the host computer 7b, the transmission block header is added to "Data 2" again as a retransmission process. rsOHJ and block number r02. FDJ and checksum are added, and "data 2" is retransmitted to the host computer 7b through the R8-2320 driver 4b in the data format shown in FIG. 8(b) (processing 4B).
.

Subsequently, upon reception of rACK (OK) J, the non-procedural communication control task 3b notifies the non-procedural communication application task 2b of the completion of transmission of data 2 (5B), and the non-procedural communication application task 2b performs the following transmission process: A request to send "data 3" is made to the non-procedural communication control task 3b. The non-procedural communication control task 3b adds the transmission block header rsOHJ and block number r03. to "data 3". After adding FCJ and checksum, "data 3" is sent to the host computer 7b in the data format shown in FIG. 8(d) (processing 6B), and after receiving rAcK (OK)J, the thermal procedure communication application task 2b The completion of transmission of "data 3" is notified to (process 7B). The non-procedural communication application task 2b requests the non-procedural communication control task 3b to send "rEOT (end of transmission)" requesting the end of transmission, and the non-procedural communication control task 3b sends "rEOT (end of transmission)" to the R8-232C driver 4b. After transmitting the data to the host computer 7b through the
B).

FIG. 3 is a block diagram showing an error detection protocol control method when an error is detected in received data according to this embodiment.

The non-procedural communication application task 2C requests the non-procedural communication control task 3C to send rNAK (transmission request) requesting the start of transmission, and the non-procedural communication control task 3C requests r
NAK (send request)” with R8-232C driver 4
0 to the host computer 7C.
), when data A in the data format shown in FIG. 8(e) is received from the host computer 7C through the R8-232C driver 4C, the block number and checksum are checked, and then the transmission block header "SOH" and the block number are The checksum is deleted, and "data A" is notified to the non-procedural communication application login task 2c (processing 2G).

The non-procedural communication application task 2C requests the non-procedural communication control task 3C to send rACK (OK)J as completion of preparation for the next reception process. After sending rACK (OK)J to the host computer 7C through the R8-232C driver 4C, the non-procedural communication control task 3C sends the 8th
When data B in the data format shown in Figure (e) is received, the block number and checksum are checked, and when an error is detected in the block number (block number 03 is incorrect, correct is 02), error detection rNAK (NG)J R8-2
The data is sent to the host computer 7c through the 32G driver 40 (processing 3C). When the non-procedural control task 3C receives the retransmission data of data B (FIG. 8(f)) from the host computer 7C, it checks the block number (block number 02.FD is normal) and the checksum, and if it is normal. Transmission block header rsQ, HJ
and block number r02. The FDJ and checksum are deleted, and data B is notified to the non-procedural communication application engine task 2C (processing 4C).

The non-procedural communication application task 2C requests the non-procedural communication control task 3C to send rACK (OK)J indicating the completion of preparation for the next reception process, and sends it to the host computer 7C through the R8-2320 driver 40 (
Processing 5C). The non-procedural communication control task 3c receives an rEOT from the host computer 7C indicating the end of transmission (end of transmission).
”, the non-procedural communication application cage day task 2
The non-procedural communication application cage task 2c notifies C of the end of transmission, and ends the reception process (process 6C).

FIG. 4 shows a protocol control method for handling abnormalities during data transmission and data reception.

rNA requests start of transmission from host computer 7d
When the non-procedural communication control task 3d receives "K (transmission request)" through the RS-232C driver 4d, a transmission start request is notified to the non-procedural communication control application task 2d (processing ID). The non-procedural communication application task 2d requests the non-procedural communication control task 3d to send "data 1" as a transmission start process, and the non-procedural communication control task 3d sends a transmission block header rsO to data 1.
HJ and block number r01. After adding FEJ and checksum, R8-23 is created in the data format shown in Figure 8(a).
It is transmitted to the host computer 7d through the 2G driver 4d (processing 2D). When the host computer 7d does not respond, the non-procedural communication control task 3d causes the response code reception monitoring timer (60 seconds timer) to time out.
rCAN (cancel) indicating transmission cancellation.
8-232C driver 4d to the host computer 7d, non-procedural communication application task 2
d of the abnormal end of transmission (processing 3D).

Next, when the non-procedural communication application task 2d sends an rNAK (transmission request) requesting the start of transmission to the non-procedural communication control task 3d, the non-procedural communication control task 3d receives the NAK through the RS-232C driver 4d.
Processing to send K (transmission request) to the host computer 7d (4D), data A in the data format shown in FIG. 8(e)
is received, after checking the block number rot, FEJ and checksum, the transmission block header “5OH
J, block number, and checksum are deleted, and "data A" is notified to the non-procedural communication application task 2d (processing 5D).

After the non-procedural communication application task 2d completes preparation for the next data reception process, the non-procedural communication application task 2d returns to the non-procedural communication control task 3d.
When a request to send ACK (OK) J is made, the non-procedural communication control task 3d sends rACK (OK) J to the host computer 7d through the R8-232C driver 4d, and when the host computer 7d does not respond, it monitors block reception. When the timer (which can be set to any value from 00 to 99 seconds) times out, rACK (OK) J is retransmitted. The non-procedural communication control task 3d repeatedly sends rACK (OK) J if the host computer 7d does not respond.
R8-232C sets rCAN (cancel)j, which indicates cancellation of reception when the
After transmitting the data to the host computer 7d through the driver 4 (1), the non-procedural communication application task 2d is notified of the abnormal end of reception (processing 7D).

FIG. 5 shows the format of transmission block data.

The format of the transmission block data is [transmission block header rsOHJ E, [block number] 100, [255
- block number], [transmission block data code] and [check sum] 101. Block numbers are 0018~FF! 8, starting from 01□8 and F
When it exceeds F 1e, it goes up to 0One. The checksum is the remainder of the total transmission block data divided by 256.

FIG. 6 shows the control code. rsOHJ is the transmission block header, rNAKJ is the request to start transmission or negative response, rAcKJ is the acknowledgment, "EOTj is the end of transmission,
rCANJ indicates cancellation.

FIG. 7 shows types of timer monitoring and timer values.

The "transmission start request (NAK) J monitoring timer is 60 seconds, and rCANj transmission is performed after a timeout occurs. The block reception monitoring timer is a monitoring timer after rACKJ transmission, and the timer value can be set in the range of 00 to 99 seconds. The rCANJ transmission is performed with the rAcKJ retransmission tryover (IJ) number of tries (can be set in the range of 00 to 99 times).In addition, the response code reception monitoring timer It is a monitoring timer, and sends "rCAN" when a 60 second timeout occurs. Moreover, FIGS. 8(a) to 8(f) are explanatory diagrams showing examples of transmission block data.

〔Effect of the invention〕

As explained above, the present invention includes a non-procedural communication application task that operates according to instructions from an operator, a non-procedural control task that controls a non-procedural communication protocol with an error detection function, and a non-procedural control task that controls an R8-232C board and performs data transmission. By being configured with the R8-2320 driver, all data including binary food data such as object data 0 document file data can be sent and received without transmission errors such as data corruption or data loss.

[Brief Description of the Drawings] Figure 1 shows the configuration of an embodiment of the present invention, including a non-procedural communication application program, a non-procedural communication control task, and R8-2.
FIG. 2 is a block diagram showing a control method of a non-procedural communication protocol with an error detection function performed by the 32G driver, and FIG. Fig. 3 is a block diagram showing an error detection protocol control method when an error is detected in received data according to this embodiment, and Fig. 4 shows a protocol control method for abnormality processing during data transmission and reception according to this embodiment. A block diagram, FIG. 5 is an explanatory diagram showing the format of transmission block data, FIG. 6 is a diagram showing the types of control codes,
FIG. 7 is an explanatory diagram showing types of timer monitoring and timer values, and FIGS. 8(a) to (f) are explanatory diagrams showing examples of transmission block data. la~1d...Personal computer, 2a~2d
...Non-procedural communication application tasks, 3a-3d
...Non-procedural communication control task, 4a-4d...R8-
232C driver 5 a ~ 5 d...RS
-232C board, 6a to 6d... public communication network,
7a-7d...Host computer.

Claims (1)

[Claims] A non-procedural communication control method for a personal computer connected via a non-procedural communication method in a public communication network, which controls a non-procedural communication application task that operates according to instructions from an operator and a non-procedural communication protocol that has an error detection function. Non-procedural communication control task and RS-232
A non-procedural communication control method comprising an RS-232C driver that controls a C board and transmits data, and transmits and receives all data including binary code data.