JP3373932B2 - System construction method - Google Patents

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention comprises, for example, a software bus having a common "attribute" interface and "event" interface, and a control module. For example, "commands" are passed between control modules. It relates to a construction method of a terminal emulator that operates. The present invention can be applied to communication software in general regardless of the terminal emulator.

[0002]

2. Description of the Related Art A conventional terminal emulator comprises modules such as a driver section 7, a communication protocol control section 6, a screen control section 1 and a printer control section 2 as shown in FIG. Figure 8
In the figure, 1 is a screen control unit and a data stream analysis unit 5
Is a module for displaying a screen on the window system 9 based on the information from. Reference numeral 2 denotes a printer control unit, which is similar to the screen control unit 1 and is a module for converting the data into printer printable data based on the information from the data stream analysis unit 5 and outputting the data to the printer. A file transfer control unit 3 is a module for reading data from a specified file and passing the data to the data stream analysis unit 5, and conversely writing data to the file based on information from the data stream analysis unit. Reference numeral 4 denotes an interface unit with the screen control unit 1, the printer control unit 2, and the file transfer control unit 3, which is a module for performing interface processing as shown in FIGS. 9 and 10 described later. Reference numeral 5 denotes a data stream analysis unit, which is a module for analyzing a data stream and converting it into a data format and a code to be passed to a higher order in this example. 6 is a communication protocol unit. 7 is a driver unit for communication H /
It is a module that exists between the W8 and the communication protocol unit 6 and passes data. Reference numeral 8 indicates communication H / W. 9
Is a window system, and 10 is an operating system. The screen control unit 1 to the file transfer unit 3 are connected to the data stream analysis unit 5 to the communication H / W 8 via the interface unit 4.

The interface between each module defines an original interface arranged between individual programs. For example, the screen control unit 1 to the file transfer unit 3
The interface between the interface unit 4 and the interface unit 4 is as shown in "Example interface of conventional terminal emulator" of FIG. 9, and FIG. 10 shows the example of FIG. 9 in more detail. This can be used only between the screen control unit 1 to the file transfer unit 3 and the interface unit 4,
Screen control unit 1-file transfer unit 3 and interface unit 4
It is uniquely defined according to the protocol used between the two.

As shown in FIG. 8, the conventional terminal emulator has a communication protocol control unit 6 / data stream analysis unit 5 / driver unit 7 adapted to a supported communication protocol.
In order to change the protocol, it is necessary to replace the driver unit 7, the communication protocol control unit 6, and the data stream analysis unit 5 according to the protocol.
Further, the interface with the screen control unit 1 to the file transfer unit 3 is also an interface depending on the protocol used, and it is necessary to reconstruct the interface unit 4 and the screen control unit 1 to the file transfer unit 3 according to the protocol. Become. Therefore, in order to realize the multi-protocol function support and the multi-emulation function with the conventional terminal emulator, it is necessary to move a plurality of modules in series, and problems such as memory size and resources used tend to occur.

FIG. 11 is a diagram showing the flow of installation and definition of a conventional terminal emulator. This indicates that the environment definition file is accessed at the time of installation (1) and subsequent environment definition (2), and at the start of emulator execution (3). In the conventional terminal emulator, as shown in FIG.
As shown in, the setting of the parameter that defines the operation of the terminal emulator is defined when the series of modules is installed or when the environment is defined thereafter. When the execution of the terminal emulator is started, the definition contents and environment definition file 15 are read and the operation is performed after initialization. Therefore, the operating environment cannot be easily changed while the terminal emulator is operating.

[0006]

[Problems to be Solved by the Invention] As shown above,
In the conventional terminal emulator, communication H / W, driver unit,
Communication protocol control etc. are built in one, so it is difficult to dynamically switch protocols or change the operating environment.
In addition, when trying to realize multi-protocol support or multi-emulation function, it is difficult to support multiple protocols due to problems such as memory size during operation and resources used. There was a problem that the software that supported one protocol had to be terminated and then switched to the software that supported another protocol.

The present invention has been made in order to solve such a problem, and an object thereof is to enable dynamic protocol switching and change of operating environment in a terminal emulator. The purpose is to enable support for the multi-emulation function.

[0008]

A system construction method according to the present invention has the following elements. (A) a plurality of control units each having an individual function and performing data processing in collaboration with others, (b) a shared data area provided between the plurality of control units,
(C) A software bus provided between the plurality of control units to provide a common software interface to the control units and dynamically couple the control units using the shared data area.

The software bus is attached to each control unit, and an attribute interface that defines the operating environment and function of the control unit, an event interface that defines the format and meaning of the message to be transferred between the control unit and the software bus, and each control unit. It is characterized in that the above-mentioned control units are combined by a different name.

The control unit generates an instruction including at least route information using a name and a processing request indicating a request content in the shared data area, and the software bus is a control unit to be connected based on the route information. Is identified and the processing request is notified to the control unit to be combined through the attribute interface and the event interface.

In the above route information, the distribution destination of the execution result can be designated, the control unit which has processed the command generates an instruction for transmitting the execution result to the distribution destination, and the software bus distributes the execution result. Is characterized by.

[0012]

In the system construction method according to the present invention, the control unit for realizing each function is arranged on the software bus having the common software interface. The software bus is defined so as to provide information for enabling dynamic connection with each control unit and environment setting. Further, by allowing any control unit on the bus to arbitrarily access the bus, arbitrary communication and control between the control units is possible through the software bus. In this way, it becomes possible to dynamically connect and disconnect between the control units via the software bus, and for example, it becomes possible to dynamically switch the protocol and change the operating environment.

The software bus has an attribute interface and an event interface as common software interfaces. The attribute interface defines the operating environment and functions of each control unit, and is, for example, a display attribute such as color, a line definition, and a pointer of a command to be passed. The event interface defines the format and meaning of messages passed between the control unit and the software bus. A name is given to each control section, which allows the control section to be uniquely identified. The control unit can change the operating environment and function of the control unit designated by the name using the event interface and the attribute interface.

The control unit can catch the execution of the specified operation with respect to the other control units. This can be achieved via instruction generation, event interfaces and attribute interfaces. The command includes at least route information having a name and a processing request. In some cases, this may include data. When a request is generated, the control unit generates an instruction in the shared data area and notifies the software bus via the event interface. The software bus notifies the pointer of the generated instruction to the control unit indicated by the route information via the attribute interface and the event interface. This allows a request to be transmitted from one control unit to another control unit.

Further, the distribution destination of the execution result can be designated as the route information. In this case, the control unit that has processed the instruction generates an instruction for transmitting the execution result to the distribution destination, and notifies the software bus via the event interface. The software bus notifies the destination control unit of the generated instruction pointer through the attribute interface and the event interface.

[0016]

【Example】

Example 1. FIG. 1 is a block diagram showing the configuration of the terminal emulator in this embodiment. In the terminal emulator, a software bus having a common interface and a control module that implements each function on the software bus are arranged around the bus control unit. Reference numeral 21 denotes a bus control unit, which is a module that performs control for enabling pre-registered "attributes", "events", and "names" to be transferred between the control modules. A software bus 22 is a module for transmitting the “attribute”, “event”, and “name” used by each control module to each control module via the bus control unit 21. 23 is a display / input control control, for example, A
This module performs screen display on the window system 9 and key input processing from the window system 9 based on information from the terminal stream analysis control 25. 24
Is a printer control control module, which performs printer printing based on information from the A terminal stream analysis control 25. Reference numeral 25 is an A terminal stream analysis control, which is a module for analyzing the A terminal data stream and converting it into a data format and code to be passed to the upper layer. Reference numeral 26 is a B terminal stream analysis control, which is a module for analyzing the B terminal data stream and converting it into a data format and code to be passed to the upper layer. Reference numeral 27 denotes a setup control, which is a module for setting an operating environment. Reference numeral 28 is a control for performing various communication controls. T procedure 29, S procedure 30, D procedure 31, F procedure 3
It is a module that performs communication procedure processing such as 2. 33-3
Reference numeral 6 indicates communication H / W.

This is a software bus 22 having a common interface, its control unit 21, and a control module 2 for realizing each function on the software bus 22.
3 to 32. Software bus 22
Has a role as a bus for passing data and messages between each control module.
1 has a function of controlling data and messages flowing on the bus. Each control module 23-32 is an object having a closed environment in which each function can be executed by itself. Further, the bus can be arbitrarily accessed from any control module on the software bus 22.

Next, the software bus 22 has a common interface for the control module. The relationship among "attribute", "event", "command", and "name" will be described with reference to FIG. Each control module and software bus has a common "attribute" and "event"
It is bound to the interface by "name". Via a software bus to pass "commands" between each control module. The “name” of the control module is an identifier attached to identify each control module. For example, the control modules 41 to 44 in FIG. 2 are given names A to D.

The "attribute" is definition information for defining the operating environment and function of each control module. Also,
The "attribute" can be set to the pointer of the "command" to be passed. The “attribute” is, for example, Reset or Command.
d, Status, etc., which have the specifications described below. Reset (Int) is "when initial processing is requested."
0 "is set, and switching is performed by setting" 1 "at the time of termination processing request. Command (Long) and S
The status (Long) can set the pointer of the “instruction” passed by the control module (including the bus control unit). When this value is set,
The attribute change notification of the "event" notifies the transfer destination of the "command" that the "attribute" has been changed. The notified control module reads "attribute" and then "attribute"
The "instruction" indicated by the pointer set in is read and executed. Command is used for parameter setting of the control module and data transmission request. Sta
tus is used to obtain the operating status of the control module. An example of "attribute" is shown in FIG. These “attributes” are on the bus control unit 21 and are used when passing “instructions”, parameters, data, etc. between control modules. As shown in FIG. 2, each control module has its own attribute area on the attribute area 45. For example, the control module 41 has an area of attribute A on the attribute area 45 and uses this area as a dedicated area for passing attributes.

The "event" defines the format and meaning of a message that is asynchronously notified to give an operation trigger between each control module and the bus control unit.
“Event” includes, for example, Request, Error, attribute change notification, etc., and an example thereof is shown in FIG. Request
st occurs when a control module wants to pass a "command" to another control module. It has the following parameters. Name (String): name of the control module for notifying the "command", Index (Int): identifier of the "attribute" to be set 1 = "Command" 2 = "Status" PT (Long): pointer of the "command" The "attribute change notification" is for notifying the corresponding control module when an attribute change occurs.

The "command" describes the processing request to each control module and the notification destination of the processing result. An example of "instruction" is shown in FIG.

The "attribute" and the "event" must be common to each control module according to the software bus used. Further, since there are some commands and some commands that can be used by each control module, those that can be used are registered in advance for each control module.

The relationship between "attribute", "event", "command" and "name" and the operation between control modules will be described with reference to FIG. It is assumed that each control module has previously registered a "name" used in the control module with respect to the software bus (bus control unit).

Reference numerals 41 to 44 are control modules. The name of the control module 41 is A.
The name of the control module 42 is B. Also,
The control modules 43 and 44 are named C and D, respectively. Reference numeral 45 is an attribute area in the bus control unit 21. This attribute area is divided into areas A to D corresponding to the control module. A in the attribute area corresponds to the control module A, and data to be passed to the control module A is set. 46 is a shared data area, which is shared by the control modules 41 to 44 and the bus control unit 21. Reference numeral 47 is a command, which is composed of route information command data. The instruction is set in the shared data area 46.

(1) The control module 41 notifies the software bus 22 of the "name" and "command" of the request destination by "event" in order to prompt the execution of the operation specified by the "command" of the control module 42. To do. Here, the control module 41 sends the "event" REQ.
By issuing (B, CMD), the attribute Comma for the control module 42 is sent to the bus control unit 21.
Requests that nd be set to a value. Where REQ is R
It is an abbreviation for request, and B is the name of the control module 42. CMD is an abbreviation for Command. At this point, the control module 41 sets an instruction 47 in the shared data area 46 and sends the pointer of the instruction 47 to the bus control unit 21 together with the CMD. Instruction 4
7, “A → B” as the route information and “Li
nkOpen ”is set. The data is "none".

(2) The bus control unit 21 uses the REQ (B, C
MD) and sets the pointer of the previously set instruction 47 in the CMD of attribute B. Then, the bus control unit 21
Issues a "attribute change notification" of "event" to the control module 42. Here, the attribute B is an attribute area dedicated to the control module 42, and when the operating environment or function of the control module 42 is desired to be changed, it is notified by changing the "attribute" parameter. Alternatively, when the "instruction" is desired to be transmitted to the control module 42, the instruction pointer can be set in the "attribute". (3) The control module 42 reads the attribute B. (4) Next, the control module 42 sets C of attribute B
The instruction 47 indicated by the MD pointer is read. Instruction 4
The LinkOpen communication connection shown in FIG. 7 is executed.

The roles and operations of the "event", "attribute", "name", and "command" when the control module makes a request to another control module have been described above.

Here, "name", "event", "attribute",
The features of "instruction" are summarized as follows. "Name": Each control module has a "name" that can be used to create route information for the request stream. "Event": Communication between the control module and the software bus is performed by "event". "Attribute": The bus control section 21 has an attribute area 45, and an attribute area dedicated to each control module is provided here. By changing the "attribute" parameter, the operating environment of the control module can be dynamically changed. It also serves as a relay point for the "command" pointer. “Instruction”: The “instruction” is created in the shared data area 46 by the issuing control module. This "command"
Is notified to the software bus by "event", and the bus transmits it to the control module indicated by "name" of the destination via "attribute" on the bus control unit 21.

Further, by having the "attribute" interface and the "event" interface as described above, the control module 41 can control
At the same time that the above processes (1) to (4) are carried out for the second item, another control module can perform the same process for the control modules other than itself.

Next, the operation of "attribute" and "event" between the terminal and the protocol control module will be described. FIG. 6 shows an operation flow between the A terminal stream analysis control 25 and the communication control T procedure control 29 in FIG. This will be described with reference to FIG. (1) The software bus (bus control unit) 22 has 0 (initial processing request) in the "attribute" Reset on the software bus.
Is set, and each control module is notified by an "event" message. Each control module receives the message and accordingly the software bus 2
The value 0 set in the attribute Reset is read from 2.
Since the value is 0, the initial processing is executed.

(2) The software bus is the "name" of all control modules already connected on the bus.
To notify. (3) The A terminal stream analysis control 25 prompts the software bus 22 to execute the operation defined by the “command” of the communication control T procedure control 29, and thus the “name” and “command” of the request destination are “event”. Will be notified.
Here, it is required to set the pointer of the "instruction" described below in the "attribute" Command of the communication control T procedure control 29 by the "event" Request. The “command” to be notified is the notification from the A terminal stream analysis control 25 to the communication control T procedure control 29 as the route information, and the LinkOpen as the request content.
(Communication connection request), no attached data is shown. This “command” is created in the shared data area 46 by the A terminal stream analysis control 25. (4) The software bus sets a value for the “command” from the A terminal stream analysis control 25 to the communication control T procedure control 29 in the “attribute” area for the communication control T procedure control 29, and Notify by attribute change notification. (5) The communication control T procedure control 29 is an “attribute” of the communication control T procedure control 29 from the software bus.
Is read, the "command" is read by the pointer of the "command" notified by the "attribute", and the operation specified by the "command" is executed. Here, LinkOpen is performed. Hereinafter, (6), (7), (8), (9), (10),
(11) is the same operation as (3), (4) and (5) above. In (6), it is required to set the "attribute" Command of the communication control T procedure control 29 by the "event" Request. The “command” to be notified indicates a notification from the A terminal stream analysis control 25 to the communication control T procedure control 29 as route information, Send (processing request of transmission data) as request contents, and attached data indicates transmission data “abc”. ing. In (9), it is requested to set the "attribute" Status of the communication control T procedure control 29 by the "event" Request. The “command” to be notified is, as route information, notified from the A terminal stream analysis control 25 to the communication control T procedure control 29, then the execution result is notified to the A terminal stream analysis control 25, and Li as the request content.
nkIP (acquisition of IP address) and no attached data are shown. (12) Communication control T procedure control 29 is "command"
In order to notify the control module indicated by the route information in the "instruction" of the execution result of the "command", notify the software bus by the "event" of the "name" of the notification destination and the "command" that describes the execution result. To do. The "command" to notify is
From the communication control T procedure control 29 as route information,
Notification to the terminal A stream analysis control 25, LinkIp as request contents, and attached data 144.13
It is 0.255.255. (13) The software bus has a communication control T procedure control 29 for the A terminal stream analysis control 25.
"Command" from A terminal stream analysis control 2
A value is set in the "attribute" area for 5 and the "event" attribute notification is sent. (14) The A terminal stream analysis control 25 reads the “attribute” of the A terminal stream analysis control 25 from the software bus. The “instruction” is read from the pointer of the “instruction” notified by the “attribute”, and the execution result IP address 144.130.
It is possible to recognize 255.255.

As described above, in this embodiment, the software bus 22 having the common "attribute" interface and "event" interface, and the selectable control modules 21 to 32 connected to the software bus 22 are connected.
The terminal emulator is characterized in that the "command" defined according to the control module is passed through the "attribute" and "event" interfaces to operate, and the control module is a common component. A software bus with such a software interface enables dynamic connection with each control module and environment setting. Further, in the terminal emulator of this embodiment, it is possible to dynamically change the operating environment and the protocol, and by using a software bus having a common interface, a terminal emulator with high expandability and high reliability can be obtained. It became possible to build.

Example 2. This example describes the support of multiple protocols by multiple combinations of control modules. Since the software bus has the "attribute" interface and the "event" interface common to the control modules as in the above embodiment, the description of the same points will be omitted. FIG. 1 is a block diagram showing the configuration of the terminal emulator of this embodiment.

In FIG. 7, the A terminal stream analysis control 25 issues a request to the communication control T procedure control 29, and at the same time, the A terminal stream analysis control 25 issues a request to the communication control S procedure control 30, and at the same time, the B terminal stream analysis control. FIG. 26 is a diagram showing operations of “event” and “attribute” in the case where 26 issues a request to the communication control S procedure control 30. It will be described with reference to the drawings. (1) A terminal stream analysis control 25 is REQ
Issue (D, CMD). At the same time, the instruction 51 is created in the shared data area 46. (2) The software bus 22 receives the event from the A terminal stream analysis control 25 and sets the pointer of the instruction 51 to the attribute D in the attribute area. Then, the communication control T procedure control 29 is notified by the attribute change notification of "event". (3) Communication control T procedure control 29 reads the attribute D assigned to itself. (4) The instruction 51 in the shared data area 46 is read from the pointer of the instruction notified by the attribute D. (5) The A terminal stream analysis control 25 outputs REQ (E, CMD) to the software bus 22 depending on the event. At this time, the A-terminal stream analysis control 25 creates the instruction 52 in the shared data area 46. (6) The software bus 22 sets the pointer of the instruction 52 in the attribute E. Then, an attribute change notification is issued to the communication control S procedure control 30. (7) Communication control S The procedure control 30 reads the attribute E. (8) Communication control S The procedure control 30 reads the instruction 52 from the shared data area 46 by the instruction pointer obtained from the attribute E. Then, the Li shown in the instruction 52
Run nkOpen. (9) The B terminal stream analysis control 26 issues a request to the software bus 22 by the event REQ (E, STS). At the same time, command 5 is sent to the shared data area 46.
Create 3. In this case, the B terminal stream analysis control 26 requests the communication control S procedure control 30 to set the IP address of the connection partner, and the route information is C, E, C. (10) The software bus 22 sets the pointer of the instruction 53 to the attribute E and issues an attribute change notification to the communication control S procedure control 30. (11) Communication control S The procedure control 30 reads the attribute E. (12) Communication control S The procedure control 30 reads the instruction 53 from the pointer of the instruction indicated by the attribute E from the shared data area 46. (13) Communication control S procedure control 30 is event REQ
(C, CMD) issues a request to the software bus.
At the same time, the instruction 54 is created in the shared data area 46. (14) The software bus 22 sets the pointer of the instruction 54 to the attribute C and notifies the B terminal stream analysis control 26 by the attribute change notification. (15) The B terminal stream analysis control 26 reads the attribute C. (16) The B terminal stream analysis control 26 moves from the pointer of the instruction indicated by the attribute C to the shared data area 46.
Command 54 is read. Then, it knows that the IP address of the connection partner requested in (9) was 144.130.255.

In the conventional terminal emulator, communication hardware, a driver section, communication protocol control, etc. are integrally constructed. Therefore, in the conventional example of FIG. 8, it is difficult for the data stream analysis unit 5 that has made a request to the communication protocol control unit 6 to make a request to another communication protocol control unit to dynamically switch the protocols. there were. In order to realize the above-described processing flow, conventionally, it was necessary to temporarily terminate the software supporting the first protocol and then switch to the software supporting the latter protocol. Further, it has been difficult to realize support for a plurality of protocols such as the above-described communication control with the A terminal and communication control with the B terminal, because of problems such as the memory size during operation and the resources used. However, as mentioned above,
Through the common "attribute" and "event" interface, the A terminal stream analysis control 25 issues a request to the communication control T procedure control 29 as described above, and then the same A terminal stream analysis control 25 transmits the communication control S. It is possible to support a plurality of protocols such as issuing a request to the procedure control 30, and it is possible to dynamically switch the protocols. Further, a plurality of protocols can be supported such that the B terminal stream analysis control 26 issues a request to the communication control S procedure control 30.

Thus, common "attributes" and "events"
According to the system construction method having the software bus with the interface, it is possible to dynamically switch the emulation functions between different host computers and terminals and execute the emulation functions at the same time as in the example of the above protocol. Become.

Further, the operating environment can be changed, that is, the parameters required for the operation can be easily changed from the outside. This includes display attributes such as colors, character string changes, line definitions,
That is, it is possible to change the speed, the change between the private line and the public line by changing the attribute of the attribute area from the external user level.

As described above, in this embodiment, the control modules can be dynamically connected and disconnected through the software bus, and the protocol can be dynamically switched or the operating environment can be changed. Similarly, a multi-protocol function that supports a plurality of different protocols and a multi-emulation function that serves as a terminal of a plurality of different host computers can be realized by dynamically combining with a control module that supports each protocol and emulation.

[0039]

According to the present invention, it is possible to dynamically connect and disconnect the control units to each other through the software bus, and by using the software bus having a common interface, the expandability and the reliability are high. It is possible to build a system.

According to the present invention, the common software interface is divided into the attribute interface and the event interface to provide an easy-to-use interface. In addition, this interface enables dynamic coupling between the control units. Further, the operating environment and function of the control unit designated by name can be easily changed from the outside by the event interface and the attribute interface.

According to the present invention, the command defined by the control unit can be passed through the event interface and the attribute interface, so that one control unit can transmit a request to another control unit. Further, by using the event interface and the attribute interface, it is possible to arbitrarily combine the control units, and it is possible to simultaneously process requests for a plurality of combinations.

According to the present invention, the request can be transmitted to other control units and the distribution destination of the execution result can be designated. Therefore, it is a more user-friendly interface. In addition, by specifying multiple distribution destinations, efficient execution results can be distributed.

[Brief description of drawings]

FIG. 1 is a block diagram showing the structure of a terminal emulator according to an embodiment of the present invention.

[FIG. 2] “attribute”, “event”, “command”,
The figure showing the relationship and operation of "name".

FIG. 3 is a diagram showing an example of “attribute” of the present invention.

FIG. 4 is a diagram showing an example of “event” of the present invention.

FIG. 5 is a diagram showing an example of an “instruction” according to the present invention.

FIG. 6 is a diagram showing a flow of A terminal stream analysis control, software bus, and communication control T procedure control control in the emulator of the present invention.

FIG. 7 is a diagram showing operations of “event” and “attribute” of the present invention.

FIG. 8 is a block diagram showing the structure of a conventional terminal emulator.

FIG. 9 is a diagram showing an example of an interface in a conventional terminal emulator.

FIG. 10 shows a more detailed interface of the example of FIG.

FIG. 11 is a diagram showing a flow of installation and definition of a conventional terminal emulator.

[Explanation of symbols]

1 screen control unit, 2 printer control unit, 3 file transfer control unit, 4 interface unit, 5 data stream analysis unit, 6 communication protocol control unit, 7 driver unit, 8 communication H / W, 9 window system, 10
Operating system, 14 execution modules, 1
5 environment definition file, 21 bus control unit, 22 software bus, 23 display / input control control, 2
4 Printer control control, 25 A terminal stream analysis control, 26 B terminal stream analysis control, 27 setup control, 28 various protocol control controls, 29 communication control (1)
T procedure control, 30 communication control (2) S procedure control, 31 communication control (3) D procedure control, 3
2 Communication control (4) F procedure control, 33, 34,
35, 36 communication H / W, 41, 42, 43, 44 control module, 45 attribute area, 46 shared data area, 47 command, 51, 52, 53, 54
order.

─────────────────────────────────────────────────── ─── Continuation of the front page (56) Reference JP-A-3-158947 (JP, A) JP-A-2-234234 (JP, A) JP-A-6-52079 (JP, A) JP-A-4- 318644 (JP, A) JP-A-5-224956 (JP, A) JP-A-3-85653 (JP, A) (58) Fields investigated (Int.Cl. ⁷ , DB name) G06F 13/00 G06F 9 / 46

Claims (3)

(57) [Claims] 1. A plurality of control units each having an individual function and performing data processing in cooperation with others, a shared data area provided between the plurality of control units, and a plurality of control units between the plurality of control units. provided, as well as providing a common software interface to the control unit, and software bus for dynamically coupling the control unit to jointly using the shared data area
And the software bus is an operation ring of each control unit of the plurality of control units.
Boundaries and functions are defined for each control unit.
Between the control interface and the software bus, and the attribute interface that has a security area.
An event interface that defines the format and meaning of the delivered message
And each control unit of the above multiple control units
And the multiple attribute areas of the above attribute interface.
With the name corresponding to one-to-one, the message format and meaning defined by the above event interface are defined.
Of the above multiple names from the taste
Once the name is obtained, the multiple attribute
Select the attribute area that corresponds to the above name one to one from a.
And extract the operating environment and functions from the selected attribute area
It is characterized by connecting the control unit by
System construction method 2. The control unit is at least a name
The life including the route information using and the processing request indicating the request content.
The above software is generated in the shared data area.
Bus is a control unit that should be connected based on route information
Identify the attribute interface and event interface
Notify the control unit that should combine the processing request via
The system construction method according to claim 1, wherein 3. The distribution destination of the execution result is included in the route information.
Can be specified and the control unit that processed the instruction
Generate an instruction to convey the execution result to the distribution destination, and
The airbus distributes the execution result.
The system construction method described in 2.