JPH0675892A - Remote procedure managing device - Google Patents

Abstract

PURPOSE:To call a remote procedure provided by a system, even if the remote procedure of the system is not defined in an interface of an application service. CONSTITUTION:When a remote procedure call of a system service is executed by a system remote procedure request part 11, and it is decided that a stub of a remote side is not a remote procedure of an application service, a system procedure pre-processing part 14 is called, a system remote procedure managing part 13 is retrieved by a requested remote procedure identifier, and by determining a system remote procedure executing part 12 for executing a service to be called, the processing is executed, by which the remote procedure of the system service can be executed, even if the remote procedure of the system service is not defined in an interface between applications.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a remote procedure management device for managing a remote procedure call provided by a system used in a distributed application program via a network.

[0002]

2. Description of the Related Art In recent years, remote procedure call has been widely used to develop a client / server model distributed application program via a network. In the form of this distributed application, the client is positioned as the side requesting the remote procedure call, and the server is positioned as the side receiving the request for the remote procedure call, performing the requested processing, and returning the result. A typical example of such a remote procedure call is "Implementing
remote procedures calls, "by Andrew D. Birrel and
Bruce Nelson in ACM Trans. On Computer Systems,
Vol. 2, No. 1, Feb. 1984, pp. 35-39. Are known.

Management of procedures in the conventional remote procedure call will be described below. FIG. 3 is a block diagram showing a schematic configuration of a conventional remote procedure calling device. In FIG. 3, 31 is a client system, and 32 is
Is a client application program that requests a remote procedure call, and 33 is a client stub that executes a remote procedure call on the client side created from one interface that defines a plurality of remote procedures. 34 is a server system connected to the client system 31 via a network, and 35
Is a server stub that executes a remote procedure call on the server side created from the same interface as the client system 31, and 36 is a server application program that executes the processing of the requested remote procedure.
This remote procedure call interface can use a plurality of client stubs of an interface that requests a plurality of types of services on the client system 31 side, but one server stub of an interface that provides one type of service on the server system 34 side. Only.

With respect to the remote procedure calling device configured as described above, a method of determining a called remote procedure will be described below. First, the client system 31
When the client application program 32 of the client executes one remote procedure call from the procedures defined in the interface definition, the client stub 3
3 sets an identifier for uniquely identifying the corresponding remote procedure in the interface definition in the communication message and sends it to the server system 34 side together with the procedure call argument. Upon receiving this, the server stub 35 refers to the remote procedure identifier in the communication message, determines the remote procedure to call, extracts the argument data from the communication message, and calls the corresponding remote procedure of the server application program 36. When the server application program 36 calls the remote procedure for the callback of the client application program 32, the server stub 35 sets the remote procedure identifier in a communication message and sends it to the client system 1 side, and the client stub 33 This is analyzed and the remote procedure of the callback to be called is determined.

[0005]

However, in the procedure management in the above-mentioned conventional remote procedure calling device,
It can only uniquely identify the remote procedure defined in the interface definition defined by the application program, and also identifies the remote procedure provided by other systems, for example, the procedure when memory management is to be performed uniformly by the system. Can not do it. In particular, the server side is also limited to use one type of service interface. Therefore, when an attempt is made to provide an application with a remote procedure having a function that provides a common service, the interface definition of the application service is defined. There was a problem that it was necessary to additionally define the remote procedure of the system.

The present invention solves the above-mentioned problems of the prior art and provides a remote procedure management device capable of calling a remote procedure provided by a system without defining a remote procedure of the system in an application service interface. The purpose is to provide.

[0007]

To achieve the above object, the present invention executes a system remote procedure requesting unit for requesting a remote procedure for a service provided by a system and a remote procedure process for a service provided by the system. A system remote procedure execution unit, a system remote procedure management unit that manages a plurality of remote procedures of services provided by the system in association with the system remote procedure execution unit based on a unique remote procedure identifier in the network system; It is called from a stub that executes a procedure call, makes an inquiry to the system remote procedure management unit, determines the remote procedure of the system to be called, and has a system procedure preprocessing unit that calls the corresponding system remote procedure execution unit. .

[0008]

According to the present invention, when the remote procedure call of the system service is executed, if the remote side stub determines that the remote procedure is not the remote procedure of the application service, the system procedure preprocessor is called to perform the system procedure preprocess. The system searches the system remote procedure management unit with the requested remote procedure identifier, determines the system remote procedure execution unit that executes the service to be called, and causes the interface between the applications to execute the system service remote procedure. It is possible to execute the remote procedure of the system service without defining the.

[0009]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described below with reference to the drawings. FIG. 1 shows a schematic configuration of a remote procedure call device including a remote procedure management device of a client / server system that executes a remote procedure call provided by a system according to an embodiment of the present invention. Figure 1
In the figure, 1 is a client system, 2 is a client application program requesting a remote procedure call, and 3 is a client stub for executing a remote procedure call on the client side created from one interface defining a plurality of remote procedures. Is. 4 is a server system connected to the client system 1 via a network, 5 is a server stub for executing a remote procedure call on the server side created from the same interface as the client system 1, and 6 is the requested remote It is a server application program that executes the processing of procedures.

In FIG. 1, a remote procedure management device according to the present invention is shown by reference numeral 10, and both the client system 1 and the server system 4 have the same configuration. In the remote procedure management device 10, 11 is a system remote procedure requesting unit that provides a local service of a service provided by the system and requests a remote procedure, and 12 is a system remote that executes remote procedure processing of the service provided by the system. A procedure execution unit, 13 is a system remote procedure management unit that manages a plurality of remote procedures of services provided by the system based on a unique remote procedure identifier in the network system, and 14 is called from a stub that executes a remote procedure call, This is a system procedure preprocessing unit that makes an inquiry to the system remote procedure management unit 13, determines the remote procedure of the system to be called, and calls the corresponding system remote procedure execution unit 12.

Next, the remote procedure call processing from the client side shown by the solid line arrow in FIG. 1 in the case of providing the system service of the remote procedure management apparatus in the remote procedure call apparatus configured as described above will be described. It will be described with reference to the flowchart of FIG. First, the client application 2 of the client system 1
When a request for a service provided by the system is made, the system remote procedure requesting unit 11 that performs this service processing is called, and the client system 1 executes the local processing for the required system service (step 2).
1). Then, the remote procedure identifier of this service which is unique in the network system is added to the communication message, and the remote procedure call is executed (step 22).
The server stub 5, which receives this request via the network, checks the remote procedure identifier of the communication message,
It is determined whether the remote procedure is the application defined in the interface (step 23). If it is the remote procedure of the application, the remote procedure of the server application program 6 is called, and the remote procedure call processing of the application is executed (step 2).
4). If it is not the remote procedure of the application, the system procedure preprocessing section 14 on the server system 4 side is called, and the system remote procedure management section 13 is inquired whether or not the system service of this remote procedure identifier is held. The system remote procedure management unit 13 retrieves the management information of the system procedure held therein based on the remote procedure identifier, and the corresponding system remote procedure execution unit 1
2 is determined, and the information is returned to the system procedure preprocessing unit 14 (step 25). The system procedure preprocessing unit 14 determines whether or not the corresponding system remote procedure execution unit 12 exists based on the result from the system remote procedure management unit 13 (step 26). An error is returned to the requested client application program 2, and if it exists, the system remote procedure execution unit 12 on the server system 4 side is called to execute the processing (step 27). The results from the system remote procedure execution unit 12 are sequentially returned from the system procedure preprocessing unit 14 on the server system 4 side to the server stub 5, and from the system remote procedure request unit 11 on the client system 1 side to the client application program 2. (Step 28).

On the other hand, when a request for a service provided by the system is made from the server application program 6, the client system 1 side and the server system 4 side execute reverse processing as indicated by the broken arrow in FIG. To be done. First, when a request for a service provided by the system is made from the server application program 6, the system remote procedure request unit 11 on the server system 4 side that performs this service processing is called to execute the local processing on the server system 4 side ( Step 21). afterwards,
The remote procedure identifier of this service, which is unique in the network system, is added to the communication message, and the remote procedure call of the callback is executed (step 22).
The client stub 3, which has received this request via the network, checks the remote procedure identifier of the communication message and determines whether it is the callback remote procedure of the application defined in the interface (step 2).
3). If it is an application callback remote procedure, the callback remote procedure of the client application program 2 is called, and the application remote procedure call process is executed (step 24). If not, the system procedure preprocessing unit 14 on the client system 1 side is called, and the system remote procedure management unit 13 is inquired whether or not the system service of this remote procedure identifier is held. The system remote procedure management unit 13 retrieves the system procedure management information stored therein based on the remote procedure identifier, determines the corresponding system remote procedure execution unit 12, and returns the information to the system procedure preprocessing unit 14. (Step 2
5). The system procedure preprocessing unit 14 judges whether or not the corresponding system remote procedure execution unit 12 exists based on the result from the system remote procedure management unit 13 (step 26). An error is returned to the application program 6, and if it exists, the system remote procedure execution unit 12 on the client system 1 side is called to execute the processing (step 27). The result from the system remote procedure execution unit 12 is
System procedure preprocessing unit 1 on the client system 1 side
4 to the client stub 3, and further to the server application program 6 from the system remote procedure request unit 11 on the server system 4 side.

As described above, according to the above embodiment, when the system remote procedure request unit 11 executes the remote procedure call of the system service, if it is determined that the stub on the remote side is not the remote procedure of the application service, the system By calling the procedure preprocessing unit 14, searching the procedure management unit 13 based on the requested remote procedure identifier, and determining the system remote procedure execution unit 12 that executes the service to be called and executing the processing.
Even if the system service remote procedure is not defined in the interface between applications, it is possible to execute the system service remote procedure.

[0014]

As described above, according to the present invention, the remote procedure call device is provided with the remote procedure management device for managing the remote procedure call provided by the system.
When the system remote procedure request unit executes the remote procedure call of the system service, if it judges that the remote side stub is not the remote procedure of the application service, the system procedure preprocessor is called and the requested remote procedure identifier is added. Search the Procedure Management Department based on
By determining the system remote procedure execution unit that executes the service to be called and performing the processing, the system service remote procedure can be executed without defining the system service remote procedure in the interface between the applications.

[Brief description of drawings]

FIG. 1 is a block diagram showing a schematic configuration of a remote procedure calling device including a remote procedure management device according to an embodiment of the present invention.

FIG. 2 is a flowchart showing a system service remote procedure calling process in the same device.

FIG. 3 is a block diagram showing a schematic configuration of a conventional remote procedure calling device.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 client system 2 client application program 3 client stub 4 server system 5 server stub 6 server application program 10 remote procedure management device 11 system remote procedure request unit 12 system remote procedure execution unit 13 system remote procedure management unit 14 system procedure preprocessing unit

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Ivan Petch 1006 Kadoma, Kadoma City, Osaka Prefecture Matsushita Electric Industrial Co., Ltd. (72) Inventor Yoshihiko Suzuki, 1006 Kadoma, Kadoma City, Osaka Matsushita Electric Industrial Co., Ltd. (72) Inventor Hiroki Shinohara 1006 Kadoma, Kadoma-shi, Osaka Prefecture Matsushita Electric Industrial Co., Ltd.

Claims (1)

[Claims] 1. A system remote procedure request unit for requesting a remote procedure of a service provided by the system, a system remote procedure execution unit for executing a remote procedure process of the service provided by the system, and a plurality of service provided by the system. A system remote procedure management unit that manages a remote procedure in association with the system remote procedure execution unit based on a unique remote procedure identifier in a network system, and a system remote procedure management that is called from a stub that executes a remote procedure call. A remote procedure management device comprising: a system procedure preprocessing unit for making an inquiry to a unit to determine a remote procedure of the system to be called and for calling the corresponding system remote procedure execution unit.