TW466434B - Object-oriented message transmission interface used in heterogeneous area network - Google Patents

Abstract

The invention relates to an object-oriented message transmission interface used in heterogeneous area network, in which an application system communicates with a kernel in the network including several nodes to transmit a message. Each node includes a message queue manager (MQM) composed of several outbound queues and several inbound queues, in which message is written to the outbound queue and read from the inbound queue so as to communicate with the application system; and a forwarding message system (FMS), which is electrically connected to the MQM and is composed of several outbound threads and several inbound threads. The outbound thread corresponds to the outbound queue and communicates with the kernel by means of reading the message from the outbound queue with the outbound thread and writing the message to the inbound queue with the inbound thread.

Description

466434 A7 B7 V. Description of the invention () Message transmission is the most commonly used method to communicate with each other's application programs on the local network, but the general method is to directly call the Transmission Control Protocol (TCP) or User Data Packet Communication Protocol (User Datagram Protocal, UDP) is used to send and receive messages, and the application that receives the message uses a switch statement to process the message separately according to the type of message. The disadvantages of this approach are as follows: (1) Poor reusability The result of directly invoking TCP or UDP makes it necessary to rewrite this program when developing a new application on a local area network. (2) It is not easy to maintain. Use switch statements to process messages according to the type of message. 'When there are many types of messages, the program becomes magical and difficult to read. What's more, adding new types of messages requires modifying this program and declaring it. The header file of the message type increases the difficulty of maintenance. (3) Lack of flexibility When the configuration of the local network needs to be changed, for example, the node changes from two to three or the Internet Protocol (IP) address of the node is changed, the code of the above practice must be changed; The application on the network is complicated enough and there are enough messages. At this time, if you want to use the process mu (multi-thread) or multi-thread (multi-thread) to process different types of messages, you cannot use the above method. Unless a major change is made to improve the lack of practice, this case is the "object-oriented message transmission interface used in heterogeneous area networks", which also includes an automatic execution process. 2 (CNS) A4 specification (210X297 mm ti · :: ..: III----i I -I----I-ψ 4 ° (Please read the note ^ κ on the back before filling in this Page) Central Standards Bureau of the Ministry of Economic Affairs®: Printed by the Industrial and Consumer Cooperatives 466434 A7 B7 V. Description of the Invention (Printed by the Consumers' Cooperatives of the Central Standards Bureau of the Ministry of Economic Affairs, the purpose of this case is to provide a highly reusable, high-quality Network material delivery interface; Secondly, it also provides-automatic execution process to improve the convenience of application system design. Brief description is as follows: Λ heterogeneous local area network objects: the network of the two dry nodes, the application system disk A kernel communicates with each other to deliver a message. The system includes:-Message queue management (Gu), which consists of a queue and a number of inward queues. By writing the message to The outward-facing queue and the message are read from the inward-facing frame to communicate with the application system; and-the message transceiver (FMS), which is electrically connected to the message manager (MQM), is composed of a number of outward-oriented threads (threads) ) Is composed of a number of inward threads that correspond to the outward The inbound thread reads the message from the outbound queue and the inbound thread writes the message to the inbound queue to communicate with the core. ~ As described above, it is used in a heterogeneous local area network. An object-oriented message transmission interface, where the network is a local area network. Of course, the number of outward-facing queues is equal to the number of nodes in the local network, and the inbound queue is defined by the application system. The The number of inward threads is equal to the number of nodes in the local area network other than itself. The object-oriented message transmission interface used in the heterogeneous local area network as described, wherein one of the inward threads does not pass through the network. , And directly send the message to the node itself through the message transceiver (FMS). The object-oriented message transmission interface used in the heterogeneous area network as described, wherein the message transceiver (FMS) is an object (Object), take the message from the outside queue to the network, and receive it from the network. Read the precautions on the back first and then bind the page. Paper size 通 财 @ 邮 料 （CNS) 从 卫 （21Gx 297 Send) ------ 46643 4 A7 B7 V. Description of the Invention (The message printed by the Central Standards Bureau of the Ministry of Economic Affairs, the Shellfish Consumer Cooperative, is placed in the inbound queue, and the message transceiver (FJJS) also includes several transmission connections (TCPConnect ) Object, each transmission connection object uses one of the threads to perform its task through a socket object. The object-oriented message transmission interface used in a heterogeneous local area network as described above, wherein the message is The row manager is an object that is used to maintain the outbound rows and the inbound queues. It also provides a shared memory management CSyncBuddy object and a Persist object to solve the message process problem. The object-oriented message transmission interface used in the heterogeneous local area network as described, wherein the shared memory management (SyncBuddy) object is inherited from a Buddy object. The object-oriented message transmission interface used in a heterogeneous local area network as described above, wherein the inbound queue and the outbound queue are a SyncQueue object, inherited from a Queue object, and then A Mutex object and a CondVar object are used to solve the synchronization problem. The object-oriented message transmission interface used in the heterogeneous local area network as described above further includes: a message (RootMsg) object, and the user's message is inherited from the {^ 〇〇1 ^ 32 object, and the The R〇〇tMsg object is inherited from a virtual object (peudoRootMsg) without a data member, only a virtual method; and a system information (Sys lnf0) object, which is electrically connected to the root message which contains A Node Info object describing the information of each node and a ProcInf object describing the information of each process of the application system. As mentioned in the object-oriented message transmission interface used in heterogeneous local area networks, the node information object contains an IP address and a file belonging to the f. Please read the precautions on the back before filling this page. Order-Distribution. Printed by the Central Bureau of Standards, Ministry of Economic Affairs, Shellfish Consumer Cooperative, 466434 A7 ______ _B7___________ V. Description of the Invention () The name of the process of the node; the main content of the process information includes the execution of the process. ) Instruction name, the path where an instruction is located, and one or more inbound queue names that the process (process) will use. An execution automation process for an object-oriented message transmission interface for a heterogeneous local area network, including the following steps: inputting a system initial file (sys.ini), parsing (Parser) to generate a system definition file (sysdefs. h) and a system information building (sysinfo.mmf); input a message initial file (msg.ini), parse and encode (code) to generate a message definition file (msgdefs.h) and a "* msg. h "file; and enter the message definition building (msgdefs.h) to generate a" Message.h "file and a" Persist.h, "file by code. As mentioned, the object-oriented message transmission interface used in the heterogeneous local area network executes the automation process, where the "* msg.h" file represents the header file of the individual message. In this case, we can gain a deeper understanding through the following diagrams and detailed descriptions: Figure 1. Typical STREAM and STREAM using TCP as an example. Figure 2: Schematic diagram of STREAM after the expansion of this case. Figure 3: In a local area network with three nodes, the receiving and sending diagram is taken as an example of node three. Figure 4: The logical concept of the case. Figure 5: The static conceptual structure of the case. Figure 6: Conceptual structure of the entity in this case. Figure 7: Process view of the conceptual structure of the entity in this case. ’(Read the precautions on the back before filling in this page) Installation ·% 466434 A7 _________B7_ V. Description of the invention () Figure 8: System configuration file automatic processing program. Figure 9: System message file automation process. The main components of the above diagram are as follows: 11: Message transmission header. 12: Drive side. 13: — Confrontation. 14: Transmission Control Protocol (TCP). 15: Internet Protocol (IP). 21: Message queue manager (MQM). 22: Message Transceiver (FMS). OBx: outward-bounded. IBx: Inward queue. OBTx: outgoing threads. IBTx: Inward Thread. Printed by the Central Bureau of Standards of the Ministry of Economic Affairs—Consumer and Cooperative Cooperatives ------------ Installation --- I --- Order (诮 Please read the precautions on the back before filling out this page) The present invention utilizes object-oriented features And automatic code generation techniques, and extended the STREAM mechanism invented by Dennis Ritchie from the kernel space (kernel space) to the user space (user · Space), and got this kind of declaration instead of writing programs. Simple and practical message transmission mechanism. The left diagram in Figure 1 is a typical STREAM, the right diagram in Figure 1 is a STREAM architecture using TCP as an example, and Figure 2 is the intention of the present invention to expand the architecture. Figure 1 on the left illustrates a typical STREAM including information transmission head 11 (str e a m h e a d), driver 12 (d r i v e r en d), and zero or more modules between them. Stream head provides the interface with the application system. The driverend directly communicates with the device (device). The standard for Chinese paper (CNS) A4 (2I0X 297 mm) 466434 A7 B7. 5. Description of the invention (), the module is used to Handle intermediate data. Each module contains a pair of queues 13--read queue and write queue, stream head and driver end also contain a pair of queues, and write queues send messages down by the application At the driver end, the read queue (read queue) reversely sends the message up from the driver end to the application. The inodu 1 e in the middle can also generate other messages to send down or up. Figure 1. The right figure inserts TCP1 4 and IP15 modules between the stream head and driver end. The driver is usually a local area network (such as Ethernet). Figure 2 Adds a message as a queue manager 21 (MQM) module in the user space. The message queue manager 21 (MQM) provides the interface with the application system instead of the stream head. The message queue manager 21 (MQM) Simultaneously manage and maintain two types of queues-outward queues and inward queues. Outward queues are equivalent to writing queues, and inward queues are equivalent to reading queues. The number of outbound queues is equal to the number of nodes on the local network. The queue defined by the application system to receive messages is an inbound queue. Therefore, the number of inbound queues will vary depending on the number of queues defined by the application system. different. Message Transceiver 22 (FaciUty Message Service'FMS) is a process containing multiple threads. It is responsible for the virtual sending and receiving of messages in the user space. It is also the only interface for communicating with the kernel space stream. Every two Outbound threads correspond to an outward thread, which is responsible for fetching messages from the outbound queue to send the messages out; inward threads receive messages from other nodes. 'After receiving, put the message into the inward queue, so except for yourself If there are several nodes on the network, there will be several inward threads. Figure 2 is a three-node regional network (7 CNS of node three) (210x297 ^^) HI— HI n ^ i. I— i — ^ K ^^^ 1 * ^ — ^ 1TJ " e (read the precautions on the back before filling out this page) Printed by the Central Standards Bureau of the Ministry of Economic Affairs Printed by Beigong Consumer Cooperative 46463 4 at B7 V. Description of the invention () Message sending schematic diagram, in addition to the message transceiver (FMS) process, node 3 has five process SERI, .USER5 application systems; message queue management (MQM) has three external Xiang Zilie (〇Β1, 〇Β2, 〇Β3), where the message of 0B1 is sent to node 1, then 2 is sent to node 2, 0B3 is sent to itself, that is, the message of 0B3 directly borrows FMS for IPC without going through the network ( Inter Process Communication), there are seven inbound queues (IB1., IB7) defined by the process of three nodes, of which only three are IB3, IB4, and IB5; corresponding to other nodes, FMS will generate an outward thread (0BT) and an inward thread (IBT), for example, corresponding to node 1, there must be an outward thread (0BT1) and an inward thread (IBT1), 0BT1 will send the message of 0B1 to node 1, and I BT 1 will cost you Receives the message sent by node one and puts the message in the inward queue designated by the message. Corresponding to node three, it has only an outward thread 0BT3, which is responsible for IPC of 0B3's message. In the example in Figure 3, USER1 queues through the message. The manager (MQM) sends the message to node one and node two; USER3 sends the message to USER2, and USER2 receives the message from the inbound queue IB3 specified by the message; USER4 specifies that IB4 receives the message sent by node one or node two The following are respectively Use Alan Burns's four viewpoints to explain the architecture of the case. • Logical viewpoints explain the object model for designing the case. • Static viewpoints explain the organizational structure of the software of the case. • Dynamic viewpoints explain the parallel and synchronous issues during design. • Entity perspective Use a decentralized perspective to explain how to map the software to the paper size. Applicable fmtm- {cks) am (210x297 ^ 1 Please read the notice on the back before filling out this page. Ju 4 6 6 4 3 4 A7 __________B7 V. Description of the invention () The structure of the logical view The structure of the logical view of this case is shown in Figure 4. There are four main types of class descriptions: • The negative f of the FMS object is passed outward. Take out the message to the network, or receive the message from the network and put it in the inbound queue. When the application system has a total of N nodes, for each node other than itself, each node needs a TCPConnect object for network reception. And the operation of distributing messages, FMS needs to use 2 * (N-1) TCPConnection objects. Each TCPConnection uses a thread to perform its task through the socket object, so FMS needs to use at least 2 thread (N-1) thread objects. Message queue manager (MQM) object management maintains outbound queues and inbound queues and is accessed by all processes The only window. When the application system has N nodes, the message queue manager (mqm) manages N outbound queues and inbound queues defined by all application systems (AP). In addition, it provides shared memory management for messages (S ync Buddy) objects and Persist objects used to solve the problem of cross-process messages. Outbound queues and inbound queues managed by the Message Queue Manager (MQM) are synchronization queue objects SyncQueue, and the synchronization queue objects inherit from the Buddy object , And then use the Mutex object to solve the synchronization problem. The root message (RootMsg) object is the source of the message, and all messages are directly and indirectly inherited from the Root Msg object. In order to solve the problem, different compilers (comp i 1 er) may use the same message object. There will be different layouts in the memory. RootMsg inherits from a virtual paper with no data member and only virtual law (virtua 丨 method). The paper size applies the Chinese National Standard (CNS) A4 specification (210X 297 mm). ---------- Equipment ------ ix ------ d .. (谙 Please read the notes on the back before filling this page) Printed by the agency 466434 A7 ___B7_ V. Description of the invention () Prototype object PeudoRootMsg. The system information (SysInfo) object describes the overall system configuration according to the system configuration file, including the Nodeinfo object describing each node information and the Proclnfo object describing each process information. When the system has groups, it also contains Grouplnfo objects describing the information of each group. The group information describes the name of the node that belongs to the group. The main content of the node information is the IP address and the name of the process that belongs to the node. The main content of the process information includes the name of the instruction that executes the process, the path where the instruction is located, and the The inbound queue name that the process will use. The Sysnfo object is the only window for the outside world to ask for system configuration information. The structure of the static view This case is divided into four levels, and the objects belonging to each level are shown in Figure 5. The bottom layer is the operating system layer that directly uses the operating system 1 ibrary. The operating systems currently used are NT and So 1 ar s. The hardware can use PC or SUN workstations. The second layer is the basic objects that have nothing to do with the operating system. Some objects, such as Queue, Buddy, Syslnfo, Persist, etc., use ANSI-C. Their code is the same in NT and Solaris. But like Thread, Mutex, CondVar, Shm, etc., you must use bridge, abstract factory 'and singleton three design patterns to make them objects that are not related to the operating system. In this way, all iiifdef NT, #ifdef SOLARIS scattered all over The reduction is concentrated in the abstract factory. The third layer is the application system interface level. The objects in this level are composed of basic objects in order to provide the easiest interface for the application system. _ __10 This paper size applies to the Chinese national standard (CNS M4 specification (21〇 × 297 mm) '' ---------------------------- Note on the back, please fill out this page again) A7 4 6 6 A 3 ^-B7 V. Description of the invention () For example, TCPC ο η necti ο η is combined with S 〇cket; the message queue manager (MQM) is created by SyncQueue and SyncBuddy is combined, SyncQueue is combined by Queue, Mutex, and CondVar, and SyncBuddy is combined by Buddy and Mutex. The fourth layer is the application system level. This layer only provides FMS objects. It uses TCPConnection and the message queue manager. (MQM) provides services, and uses Thread to allow messages to circulate between nodes on the network. All other objects defined by the process belong to this layer, they only need to use the service queue provided by the message queue manager (MQM). You can complete the sending of messages and the processing after receiving the messages. The architecture of the dynamic view Because SyncQueue and SyncBuddy are resources shared by each process on the same node, the following situations will cause parallel control problems: (1) When the application system (AP) puts information into the external queue, the FMS thread corresponding to the external queue may also take out the message from the external queue. 0 (2) When a node has more than one AP, and these several When Ap wants to send a message to a node at the same time, that is to say, he rushes to put the message in the outbound queue corresponding to the node. (3) In the first case, when the AP wants memory with SyncBuddy, the FMS thread may need to Return the memory to Qiao ". (4) In the second case, there are several ap and sync B ud bodies at the same time. P Jiyin -----... n This paper size applies to Chinese national standards (CNS ) A4 specification (2) OX 297 mm) (Please read the precautions on the back before filling out this page)-Binding and ordering stamps for employees' consumer cooperatives of the Central Standards Bureau of the Ministry of Economic Affairs 4 6 6 4 3 4 Central Standards Bureau of the Ministry of Economic Affairs Employee Consumer Cooperative Co-print A7 B7 V. Description of the Invention () (5) When the AP wants to get the message from the inward queue, the FMS thread corresponding to this inward queue may also put the message in the inward queue. 6) When a node has not only _ Aps, but these Aps must be from the same Within a queue out the message. (7) The fifth case AP memory when you want to return SyncBuddy the same, may FMS thread is to keep SyncBU (jdy to memory. (8) In the sixth case, there are several Aps that return the memory to SyncBuddy. 0 Based on the above analysis, we know that as long as each SyncQueue and

SyncBuddy each uses its own jjutex. Prior to the action, Mutex's Lock method is used to lock the related actions, so that other threads are not inserted in the middle of the execution. When the action is completely completed, then use the Mutex Unlock method to unlock the lock. Let the threads waiting to execute come in to execute. Structure of the Entity View We use a simpler terminal radar system to illustrate the structure of the Entity View. As shown in Figure 6, there are a total of six nodes, divided into three groups. The first group is the Monitor Subsystem (Monitor Control System), which has two nodes as backups to each other. The second group is the Terminal Radar System. The two nodes serve as backups for each other; the third group is the Controller Radar Positi0n. There are two nodes in this group. This group does not necessarily have to be aided, so it is not necessary to have exactly two nodes. Depending on the virtual needs, there can be one or More than one node. The functions of each group are described as follows: the monitoring subsystem needs to know the status of the software and hardware of each node, so each node must use its own monitoring information ______12 This paper size is applicable to the Chinese national standard (CNS > A4 specification (210X297) ) (Zinc read the precautions on the back before filling out this page) Binding · Order 4 Printed by the Employees 'Cooperatives of the Central Bureau of Standards of the Ministry of Economic Affairs ^ 6 6 4 3 4 A7 _____B7___ 5. Description of the invention () "' Report with the monitoring system , Also sends monitoring orders to other nodes through the monitoring subsystem; the terminal radar subsystem receives the radar signal, and after tracking processing, the latest position of the flying object is transmitted to the control radar table; the control radar table provides a radar display screen for the convenience of the controller Control flying objects. Two nodes that are backups of each other need to send backup messages to each other in order to know the status of the other party-problems can be dealt with immediately. • Figure 7 shows the pr0cess performed by each node, and each node must First execute the FMS process in order to transmit the message, because the LMC (Local Monitor Control) process controls the completion of processes other than FMS For faulty functions, each node must execute rLMC. • TSC (Time Synchronization Control) Process is used to coordinate and unify the internal time of each node, so each node must execute the TSC 〇 # GMD (Global Monitor Control) process to provide graphic users The interface allows the maintenance personnel to know the status of the software and hardware of each node of the system, and can also send monitoring commands to each node. GMD is only executed in the monitoring subsystem. #MDF (Monitor Data Fofmat) The process is the representative of GMD's external communication. The status report message provided by the node LMC or the LMC that issued a monitoring command message to a node is completed by the MDF. After receiving the status report message, the MDF records the status in the memory shared with gMD 'as the source of GMD display data; When someone gives an order, GMD also records the order in the memory shared with MDF. When MDF sees it, it turns it into a message and sends it out. MDF only executes in the monitoring subsystem. • RDP (Radar Data Processing) process provides receiving radar signals And radar signal tracking processing and other functions, tracking results and benefits _____13 This paper standard CNS) A4 size (210X 297 mm) i:. Binding I! (谙 Please read the notes on the back before filling this page) 466434 A7 B7 V. Description of the invention (printed by the Consumer Cooperatives of the Central Standards Bureau of the Ministry of Economic Affairs) To the control radar seat. RDP is only implemented in the terminal radar subsystem. DSP (DispIay) prGce_ is for the graphical user interface so that J members can know the latest position of the flying object and the delivery manager. The chat is only performed on the control radar seat. _KDF (Radar Data Format) Process is the external representative of the DSP. After receiving the radar information from the RDP, RDF records the data in the memory shared with the DSP as the source of the Dsp display data. When the controller orders, the DSP will also f The command records are stored in the memory shared by RDF. After RDF sees it, it turns it into a message and sends it to RDp for processing. The gas monitoring subsystem executes it. The solid line in Figure 7 represents the message transmission channel between nodes and between nodes. The messages are transmitted to other nodes through FMS. The messages in the nodes are the messages that the LMC communicates with other nodes except the same nodes. In fact, the transmission of these messages is also through? 1. The use procedure is as follows: 1. The user prepares to enter the file A. The entire application system defines a system configuration file “sys_ini” ° This file describes the system's f 卩 points and Pr 〇ces S, node description Including the IP address and all prcess names executed at the point, the process description includes the execution file name and all inbound queue names used to receive messages, the syntax is shown in Appendix I. B. The entire application system defines a message Building case "msg. 丨 n 丨". Please read the S-item first and then install i ---- 丨 -------- 1¾ This paper size applies to China National Standards (CNS) Central Bureau of Standards, Ministry of Economic Affairs Printed by the Consumer Goods Cooperatives 46743 4 a7 B7 V. Invention Description () This file describes all the messages. The message description includes the destination, the name of the inbound queue used to receive the message, the name of the object used to process the message, For the data structure of the information carried by this message, etc., its grammar is shown in Appendix 2. When the application system is very complex and there are hundreds or thousands of types of messages, it is not easy to maintain all messages declared in the same file. Files, which are included in the message file "msg. Ini". C. Each node defines itself as a node file "ge 1 f. Ini" Each node must have this file, indicating that at present The name of the node. II. Executing the automation program A. Input "sys · ini" through the parser of the same grammar and process it twice to produce "sysdefs.h" and "sysinfor.mmr, respectively, as shown in Figure 8. The contents of" sysdefs.h "are all except the definition In addition to the IDs of nodes, processes, and inward queues, there are constants such as the total number of nodes and the total number of inward rows and columns. "Sysinfo.nunf" is the binary label of the Syslnfo object, and only it is associated with "self, ini". Two external files to be used for run time execution: B. Enter "msg_ini" through Parser and Code

After generation, "rasgdefs.h" and "* Msg.h" are produced, as shown in the left figure of Figure 9. The content of "msgdefs.h" defines 11} of all messages and the total number of messages 0 "* msg.h" represents the header f i le of individual messages. 15 This paper size is applicable to China National Standard (CNS) A4 specification (2) 0X297 mm)-win-(Please read the precautions on the back before filling this page) Printed by the cooperative 4 6 6 4 3 ^ a7 _____B7 _ 5. Description of the invention () C. Input "msgdefs_h" after Code Generation processing to produce "Message.h" and "Persist, h", as shown in the right figure of Figure 9. According to the message object defined by "Mssage.h", the memory it occupies is the largest of all messages, and this object is always used to receive messages to ensure that it will not be wrong. "Persist, h" is used to solve the problem that messages will use different virtual tables for dynamic binding in different processes. How to solve it is transparent for the user, he will not use this object. 0 III. Each message header file automatically generated in the previous step 骡 B 'is except for the method of processing the message: Proc () is not defined, other Met hod is automatically defined, and proc () is recommended to use XXX:: Instance ()-> HandleYYY (1: his), where XXX is the object class of the application and only one instance is used, otherwise global Object; γγγ is the type of message. This statement is the only code that needs to be written by the user. In addition, an example of how the application sends messages is as follows:

XyMs ^ iata data (Hi, send a msg to you "); // prepare message data XyMsg mgg = XyMsg (data); // get a lcxal message that is an instance of

XyMsg Position :: InstaeCK >Send〇nsg); // ㈣ the local message An example of an application receiving a message is as follows:

Message rasg; // get a naxinum sise local msg used to receive any kind of msg. While (l) {16 This paper size is applicable to the China Mapper Standard (CNS) A4 specification (21 ^ 297 mm) ----- --- f ------- ΐτ ------ M (Please read the notes on the back before filling out this page) Printed by the Consumer Cooperatives of the Central Standards Bureau of the Ministry of Economic Affairs A7 B7 V. Description of Invention () MQM:: Instance ()-> Receive (MY_Q, msg): // receive message from queue: MY_Q msg.ProceO; // prooess the received message} IV. Compile-and-link application V. Run "f ms .exe ". The simplest example is used to illustrate the above five steps. This example contains only two nodes. AP1_PR0C of node N0DE1 sends a message ToAP2Msg to AP2_PR0C of node N0DE2. After receiving AP2_PR from the inward queue AP2_Q, it sends back the acknowlege message ToAP2AckMsg 'AP1_PR0C. Receive this message from the inbound queue AP1_Q. The content of the system configuration file "sys.ini" in Step 1 is as follows: [Nodes] N0DE1 ip__addrs = 128.12.23.88 // Allow more than one processes = ΑΡ1_Μχ) // Allow-more than N0DE2 ip_addr = 128.12.23.89 processes = AP2_H? 0C [Processes]

APl.PROC exec = " apl.exe " queues = AP1_Q // Allow more than one

AP2_PR〇C 17 ____ The size of this paper is applicable to China National Standard (CNS) A4 (210X297 male thin) --------- d ---- „--- IT ------ ♦ {Please First read the notes on the back before filling out this page) A7 4 ο 643 4 B7 V. Description of the invention ()

exec = " ap2.exe " queues = AP2_Q The information right case "m s g. i n i" in step 1 is as follows:

ToAP2Msg to = N0DE2 queue = AP2_Q data = {char msg [128);}

ToAP2AckMsg to = N0DE1 queue = API JQ The content of "self.ini" of node one of step one is as follows: current node = NODE 1 The content of "se 1 f.ini" of node two of step one is as follows: current node = N0DE2 step 骡Second, execute a shell script. Step Lai San added the content of the header file automatically generated in Step 2: Proc () method, for example, add the italicized part to ToAP2Msg.h:

ToAP2Msg :: Proc〇 {Ap20bi :: InstaiK ^ 〇- > HandleToAP2 ^^ (this);} Add the italicized part to ToAP2AckMsg.h:

ToAP2AckMsg::? T〇c, 〇 {Ap20bj :: Instance ()-> HandleToAP2AckMsg (this);} Then develop the application according to the example in step 3. The program of the relevant message of AP1_PR0C is as follows: _18_ This paper size is applicable to Chinese countries. Standard (CNS) A4 specification (2) 0X297 mm J Ί -------- iT ------ ^ 1, (Please read the notes on the back before filling in this purchase) Central Ministry of Economic Affairs Printed by the Standards Bureau's Consumer Cooperatives' 46643 4 a7 B7 V. Description of Invention () class AplObj () {

AplObj :: AplObj () {...} public: static AplObj * InstanceO {...} void HandleToAP2AckMsg (ToAP2AdiMsg present) {· _} main () {

ToAP2Ms ^ & ta dataCHi, send a msg to you "); // prepare message data ToAP2Msg msg = ToAP2Msg (data); // construct message MQM :: Instance ()-> Send (nisg); // send the local message

Message msg; while (l) {MQM:: Instance ()-> Receive (APljQ, &msg); // receive message msg.ProcO; // process the received message} ^ (Please read the precautions on the back before filling this page)} The procedure for AP2_PR0C messages is as follows: class Ap20bj {

Ap20bj :: Ap20bj () {...} public: 19 This paper size applies to the Chinese National Standard (CNS) A4 (210X297 mm) Printed by the Bayer Consumer Cooperative of the Central Bureau of Standards of the Ministry of Economic Affairs ¾ A7 Β7 V. Description of the invention () .A. Static Ap20bj * InstanoeO {...} void HandleToAP2Msg (ToAP2Msg Jtmsg) {ToAP2AckMsg rasg; M® (:: Instance〇- > Send (nisg); nain () {

Message insg; while (l) {lM :: Instance ()-> Receive (AP2_Q, &nisg); // receive message msg.ProcO; // process the received message}} Step 5 is performed "f ms. Exe The FMS process of each node will automatically execute all processes of that node. Although this example is simple, it is the same even if it is as complicated as the procedures and methods of the air traffic control system. The advantages of the message transmission mechanism in this case are as follows: (1) High reusability: Whether it is a simple decentralized application system or a complex air traffic management system, it is generated internally by thread synchronization, memory management, etc. Of cross-operating system objects is more reusable. (2) The transmitted message is just pure data but a message object, so ____ 20 This paper size applies to China's national standard (CNS) Α4ϋ (210X297 mm) —-. I order 1 i Μ (read the back of the book first) Please note this page, please fill in this page) 166434 A7 B7___ 5. Description of the invention () Dynamic switch technology can be used to replace the switch statement. Even if new information is added, the application program does not need to be modified and compiled (comp Π e), As long as it is relinked with the object code of the newly added message object, the maintainability of the application system can be increased. (3) Easy to use: The application system only needs to receive and send the two service rules (service met hod) and the method of the message object to process the message, and even the code of the message object is automatically generated by a declaration method. (4) This case provides a separate process that is virtually responsible for message transmission. The application system can be completely unaware of the existence of this process, that is, the transmission of the message is transparent to the developer. And this process does not need to recomp i 1 e and link0 due to the change of system configuration or the increase of messages. (5) High scalability: Since the concept of STREAM is borrowed, various communication protocols can be implemented according to different needs. (6) Multi-area networks are allowed, and the development of applications on nodes allows the use of multi-process and multi-thread. When each node on the local network uses the same computer, we call it a homogeneous local network; otherwise it is called a heterogeneous local network. The use of heterogeneous area networks has another problem of byte order. Although TCP class libraries are currently on the market, which solves the first disadvantage, the level of reusability is still too low. The ideal method is that the application only needs to prepare the message data to use the method of the object. ---- 21 This paper size applies to China National Standards (CNS) A4 regulations (21 OX 297 mm) L-- -.----- Installation ---- ^ --- Order ---------- line (锖 Read the precautions on the back before filling this page) Printed by a member of the Central Standards Bureau of the Ministry of Economic AffairsΗConsumer Cooperative Switch 46743 4 A7 B7 V. Description of the invention () The application that sends and receives the message only needs to prepare the object that processes the message. 'After receiving the message, control is directly passed to the object that processes the message. Thod' Write the application only the message. As for how to send messages, how to receive them, and the various shortcomings and problems mentioned above, the present invention is completely handed over to the present invention to handle 'for the person writing the application program, this paragraph is transparent. This case may be modified by anyone who is familiar with the art, but it is not as bad as the protection of the patent scope attached. (Please read the "I" on the back of the page before writing this page)-Installed by the Central Consumers Bureau of the Ministry of Economic Affairs and printed by the Consumer Cooperatives. The paper size applies to the Chinese National Standard (CNS) A4 (210 X 297 mm)

Claims (1)

4bb43 4 A8 BS C8 DS r, printed by the Ministry of Standards, Central Bureau of Standards, Consumer Cooperatives, patent application scope: an object-oriented message transmission interface used in heterogeneous local area networks, which is based on a 'network with several nodes' The application system communicates with a kernel to transmit a message, each node of which includes: a message queue manager (MQM), which consists of a number of outward queues and a number of inward queues Composition, and by writing the message to the outside " Dingle and reading the child's message from the inside to the queue to communicate with the application system; and the message transceiver (FMS) 'is electrically connected to the message 伫Column Manager (MQM), consisting of a number of outbound threads and a number of inward threads. The outbound thread corresponds to the outbound thread, and the message is read from the outbound thread by the outbound thread. And the inward thread writes the message to the inward queue to communicate with the core. 2 · If the patent period is requested, please! The item-oriented message transmission interface for a heterogeneous local area network described in the above item, wherein the network is a local area network. 3 · The object-oriented message transmission interface used in heterogeneous local area network as described in item 2 of the patent, where the number of the outward-facing rows is equal to the number of nodes in the local network, and the inward-facing rows It is defined by the application system. 4 as applied 4 rules! The object-oriented message transmission interface used in the heterogeneous local area network described in the second mouth, wherein the number of nodes of the local area network in the inward thread except itself. Department of the temple in 5 * As described in the scope of the patent application No. 2 object-oriented message transmission interface used in heterogeneous local area network 'where the inward thread-the network is not detailed,-and directly send and receive by this message The device (FMS) sends the message to the point itself. --I n II n-I-1 I t 锖 Please read the notes on the back before filling in this page} Order. Line.- ~ .1! --------- 23 This paper size applies to China National Standard (CNS) A4 specification (210X297 public shame. I 1-, printed by A8, B8, C8, D8, Consumer Cooperatives of the Central Standards Bureau of the Ministry of Economic Affairs) 6. Scope of patent application 6: as described in item 丨 of the Patent Application Park Object-oriented message transmission interface in heterogeneous local area network, in which the message transceiver (FMs) is an object, which is responsible for fetching messages from the external queue to the network, and receiving messages from the network. To the inbound list, the message transceiver (FMS) further includes a number of transmission connection (TCpc〇nnect) objects, and each transmission connection object uses one of the threads to perform its operation through a socket object. Task 7. The object-oriented message transmission interface for heterogeneous local area network as described in the patent application Fan Yuan No. 1 item, in which the message queue management device is used to maintain the outbound queue and the inbound queue, and more Providing a shared memory management (SyncBuddy) object for the message and A solution to the problem of persistence of message objects. ^ 8 · An object-oriented message transmission interface for a heterogeneous local area network as described in item 7 of the scope of patent application, wherein the shared memory management (SyncBuddy) The object is inherited from the Buddy object. 82. The object-oriented message transmission interface used in the heterogeneous local area network as described in item 1 of the scope of patent application, wherein the inward queue and the outward queue are a synchronous queue (SyncQueue) object, inherited from a Queue object, and then uses a Mutex object and a CondVar object to solve the synchronization problem. 9. Used in heterogeneous local area network as described in item 1 of the scope of patent application The object-oriented message transmission interface further includes:-the root message CEootMsg) object, the message is inherited from the RootMsg object, and the RootMsg object is inherited from a data member, only virtual rules (Virtual meth〇d) -_______ 24 Paper size 1¾Cai County (CNS) A4 inspection (2 songs 297 books) 1 ^. 1¾.. ~ Order —----- ". (Please read the back first Note ^^^ (Fill in this page) ABCD 466434 VI. Patented virtual object (PeudoRootMsg); and a system information (Sy s I nf 〇) object, which is electrically connected to the root message which contains a Modelnfo object describing each node information and a Proclnfo object describing the process information of the application system. 10. The object-oriented message transmission interface used in a heterogeneous local area network as described in item 9 of the scope of patent application, wherein the node information object includes an IP address and a process name belonging to the node; the process The main content of the (Process) information includes a command name for executing the process, a path where the command is located, and an inbound queue name that the process (process) will use. 1 1 · An automated process for implementing an object-oriented message transmission interface for a heterogeneous local area network, which includes the following steps: Enter a system initial file (sy s · ini), and use parser to generate a system Definition file (sysdefs ♦ h) and a system information file (sysinfo.mmf); enter a message initial file (rosg.ini), parse and code (gram) to generate a message definition file (mSgdefs.h) and a “氺 rasg · h” file; enter the message and specify ^ S ^ sgdefs.h) to generate a “Message.” Per s is t · h ”file by code. 1 2 · If item No. of the scope of patent application The implementation automation process of the object-oriented message transmission interface used in the heterogeneous local area network described above, wherein the "* msg.h" file represents the header file of individual messages. 25 This paper standard applies to China Standard (CNS) A4 specification (21 OX 297 mm) ---: -------- install -------- order -------- Tip. (Please read the note on the back first (Please fill in this page for matters) Printed by the Consumer Cooperatives of the Central Standards Bureau of the Ministry of Economic Affairs