JPS6033761A - Operating system of local network system - Google Patents

Abstract

PURPOSE:To improve the utilizing efficiency of a line by transmitting a data while confirming the exclusive possessing state and the common sharing state of a terminal device to select freely the kind of connecting terminal device and the number of connecting terminal devices. CONSTITUTION:A packet entering a controller 1 via a line Ri is fed to a transfer sharing section 21 and when the destination described in a header of the packet exists in the controller, the packet is fed to an exclusive and common possession processing section 27, and when not, the packet is fed to the next controller via an output line Ro. An exclusive possession and common sharing table 29 performs management at each terminal device. The number of common sharing terminal devices is counted and when the number equals to a prescribed number or below, the table allows the terminal device to be shared in common to other terminal devices. The exclusive possession and common use processing section 27 recognizes the communication enable state by managing the exclusive possession common use table.

Description

DETAILED DESCRIPTION OF THE INVENTION The present invention relates to an operating system for a local network system, and in particular to a low network system with a simple configuration that allows the user to freely select the type of terminal and the number of connected terminals, and improves line utilization efficiency. Regarding operating systems.

In general, configuration methods for computer networks 1 to work systems include star type, loop type, etc.

In addition, as line control methods, there are well-known methods such as no control method and hauling selective method.

However, for local network systems used only in factories or specific areas, the system must be configured depending on the type of connected terminal, its scale, or economic considerations. , the existing] network system cannot be used as is.

Types of connections 9N in the local network system include a plurality of numerically controlled machine tools, computer computers, keyboards, video display devices such as CRTs, magnetic tape devices, line printers, and the like.

In a local network system, it is necessary that these terminals can be freely connected, and that the connections can be easily changed and expanded.

Furthermore, it is desirable that the operating system in this local network system can be controlled with a relatively small storage capacity.

Conventional local network systems, which are implemented under many constraints including economic conditions, do not necessarily have sufficient performance. For example, in an economically advantageous uncontrolled network system l~, there is a high possibility that a transmission signal from another terminal will interrupt data transmission.

An object of the present invention is to provide an operating system for a cocal network system with a simple configuration that allows the user to freely select the connection endpoints and the number of connected terminals, and also takes line usage efficiency into consideration.

To achieve the above object, the present invention provides an operating system for a local network system in which a plurality of terminals are connected to a network controller, in which each terminal transmits data to a storage device of one code to the network controller. 1 exclusive state daple indicating the state in which each terminal is transmitting data, and a common state daple for each terminal showing the state in which each terminal is transmitting data.
This is an operating system for a [1-Cal network system], which establishes a link in response to a call signal from each terminal while recognizing the operating system, and transmits data using a store-and-forward method.

Hereinafter, this invention will be described in detail by way of examples.

FIG. 1 shows a state in which terminals 3 are connected to a network controller (hereinafter simply referred to as controller) 1 in a star shape.

In Figure 2, a plurality of controllers 1 and rollers 1, 1 are connected in a loop shape, and a plurality of terminals 3, 3 are connected to each controller 1 to the rollers.
are connected in a star shape.

FIG. 3 shows a block diagram of the configuration of the controller 1.

Controller 1 is CI) U 5, ROM7, RA I
It has a VI 9 and a bus controller 11. The data bus 13, address bus 15, and control [-]-ruba bus 1 perform monthly processing in parallel. A plurality of serial/parallel transfer interfaces for connecting a plurality of terminals are provided. Serial/parallel transfer interface is, for example, UAR for asynchronous transfer.
T (universal asynchronous
receiver/transmitter).

Controller 1 performs packet assembly and disassembly functions, and performs packet assembly or disassembly for terminals that do not have packet assembly and resolution capabilities (hereinafter referred to as N P 1-). Let's do it.

CP[J5 centrally processes the control signals necessary for the operation of the roller 1 in the engine 1. The ROM 7 stores software for the CPU 5 to centrally process the controller 1. RAM
9 is a status table (
A buffer>, respective data buffers for temporarily storing transfer data for transmission and reception, and a work area for storing necessary intermediate progress, etc. Each input/output data is transferred via a buffer using a store-and-forward method.

A desired number of controllers can be connected in a loop.

The hardware connected to each controller is a keyboard, personal computer, 〕【〕tsupidisk, printer, bu【】vine, numerical control device, hard disk, etc. A terminal that controls the assembly and disassembly functions of buckets 1~ (hereinafter referred to as PT)
, and a terminal NPT that does not have packet assembly and disassembly functions.
Both can be connected.

The number of terminals to be connected is determined by considering the system scale.

The transmission method is a store-and-forward method, and the data is transmitted in units of packets, with a header placed at the beginning and a stop code fq at the end. The header of the packet includes the destination, source, and control code for the song.

FIG. 4 is a block diagram functionally explaining the controller 1. As shown in FIG. Terminal 3 shows four examples.

] Controller 1 to roller have an exchange device 1a inside, and it is possible to transmit data, for example, from terminal T3 to T+ and simultaneously from terminal T4 to T2. Note that, as will be described later, if terminals T3 and T1 are communicating, for example, transmission from terminal T4 to T1 will be rejected.

FIG. 5 is a block diagram showing in more detail the exchange function of the roller 1. Terminal 3 is illustrated with one each of l)T and NPl. The input side of the terminal is shown as in, the output side is shown as out, the loop input line from another controller 1 is shown as R1, and the loop output line to another controller 1 is shown as Ro.

The NJ-Roller 1 has a transfer distribution unit 2'l that transfers and distributes input packets, and a transfer distribution unit 2'l that transfers and distributes input packets, and transfers transmission data from the NPT to buckets 1 to 1.
The packet generating section 23 separates the data to be transmitted to the NPT, and the packet disassembling section 25 separates the data to be transmitted to the NPT. Also, the exclusive sharing processing section 27, the exclusive sharing table 29, and the message packet generation section 31 for packetizing the control information generated in the exclusive processing section are covered to the right.

The transfer distribution unit 21 transfers the packet 1- to the controller.
is transferred to the proprietary sharing processing section 27. Other con 1-[1-
The packet sent to Ro is sent to the output line Ro.

Since the next adjacent controller also has the same configuration as the controller, processing in the next controller is handled in the same way as if the packet were received at the input circuit F7IR+ of the 21st controller.

That is, a packet that enters the controller [1-RA via the line R1] is sent to the transfer distribution unit, and if the destination written in the header of the packet in [A] is within the controller, it is sent to the exclusive and shared processing unit 27, Otherwise, it is sent to the next controller via the output line RO.

The proprietary shared table 29 manages each terminal, and when a certain terminal is currently being accessed and exported from another terminal, etc.
It should be exclusive, and the exclusive flag of that terminal is set to '1. Also, if a certain terminal is writing, etc., it may be allowed to be shared, so please set the number of shared terminals by one (i.e., if the number of shared terminals is less than a predetermined number). If so, other terminals can share the terminal.

The proprietary sharing processing unit 27 can know the communicable state by managing the proprietary sharing table.

6 and 7 are flowcharts I/-1 to 1 showing the control state of data transmission.

A transmission request from a certain terminal is made by sending an interrupt signal to the operating system.

This interrupt signal may be from another controller, from one controller with packet assembly function, or from N
Whether the PI is different or not is determined in steps 102, 103, and 104, respectively. Data from NPT is step 10
A packet is generated in step 5 and the process moves to step 106.

In step 106, it is determined whether the bucket 1~ is addressed to the controller in question, and if it is addressed to another controller, this bucket I- is sent from the output line RO to the next controller. All you have to do is leave it to us (step 107).

The transfer distribution unit 21 transfers the packet to the controller l-[:I-
If the packet is addressed to a terminal within the network, the packet is taken into the exclusive/shared processing unit 27.

In step 108, if the destination is in online communication and is exclusive to i1, then the process moves to step 112. Further, even if the destination is being shared such as writing in step 110, if it is determined in step 111 that it is not the concentric processing bucket 1~, the process moves to step 112. In step 112, the message packet generator 31 generates an error indication that communication is not possible, and sends an error indication packet to the sender. Note that, if necessary, this can be displayed on the CRT display.

If a shared processing packet is determined in step 111, the process moves to step 113 and subsequent steps.

Steps 113, 115, and 117 extract the exclusive request command or shared request command that the packet to be processed has. If it is data transmission, step 1
Step 19 to send it directly to the target terminal.

If a dedicated request command is determined in step 113, the process moves to step 114, where exclusive registration is performed to prevent intervention by other terminals.

In step 115, if "Right N: 12 command 1 type y11 side 6 is selected," in step 116, shared registration is performed.

If a command to cancel exclusive use or sharing is determined in step 117, the exclusive use or shared registration is canceled in step 118.

In steps 114, 116, and 118, message buckets 1 to 1, which are registered connections, are respectively generated, and the contents thereof are sent to the source terminal to start transmission. Incidentally, if necessary, it is also possible to display a message on a disc press device such as CR7.

As is clear from the above description, this invention, which is characterized by transmitting data while checking the exclusive status and shared status of each terminal, allows the connection terminals and the number of connected ML terminals to be freely selected, and improves line usage efficiency. It is possible to run an operating system for a local network system with a large and simple configuration (;t1).

[Brief explanation of the drawing]

Fig. 1 is an explanatory diagram showing a star type local network system, Fig. 2 is an explanatory diagram showing a star loop type local network system, Fig. 3 is a block diagram of the network controller, and Fig. 4 is an explanatory diagram showing the network controller functions. Figure 5 is a block diagram showing the exchange function of the network controller in more detail.
Fig. 6 (Control floor V-top. 1...Network controller 1 Roller 3...Terminal 29...Special table right table Patent applicant AMADA Co., Ltd. 1 Fig. 2 D-i No. 351! 4f!1 Procedural amendment (method) December 22, 1980 Director General of the Patent Office Kazuo Wakasugi 1, Indication of the case 1981 Patent application No. 141863 2, Title of the invention Local network system operating System 3, person making an amendment Patent applicant address (residence) 200-4 Ishida, Isehara-shi, Kanagawa Prefecture Agent postal code 105 Address 5th floor, Toranomon 1-2-3, Toranomon, Minato-ku, Tokyo Telephone Tokyo (504) 3075.3076.3
No. 077 (Delivery date: November 29, 1982) 6. Subject of amendment (υ Brief explanation of one drawing of the specification) column. 7. Contents of amendment (1) Line 4 of page 12 of the specification From the second line to the fifth line, the phrase "Figure 6 is a control flowchart." is corrected to "Figures 6 and 7 are control flowcharts."

Claims (1)

[Claims] In an operating system for a local network system in which multiple terminals are connected to a network controller, the storage device of the network controller contains a proprietary state table indicating the state in which each terminal is transmitting data, and a proprietary state table indicating the state in which each terminal is transmitting data. J-
and a shared status table, and the network controller establishes a link in response to a call signal from each terminal while confirming the transmission enabled status using the exclusive and shared tables, and transmits data using a store-and-forward method. An operating system for local network systems.