JPH07129498A - Inquiry type remote procedure processor - Google Patents

Abstract

(57) [Abstract] [Purpose] In the remote procedure processing on the client / server system, to execute the remote procedure processing without interrupting the processing of the client AP at the time of request and obtain the result. Furthermore, even if the number of clients increases, the input queue processing load on the server should be reduced. [Configuration] A procedure requesting device including a request identifier generation device, an output queue management device, a collection reception device, and a remote procedure execution device, and a monitoring device, a request collection device, a remote procedure execution device, and an output queue management device By providing the procedure execution device configured as described above, the main object for starting the remote procedure process is the server, and the above object is achieved.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an inquiry type remote procedure processing device using a client / server processing system used in a distributed processing environment constructed on a network system.

[0002]

2. Description of the Related Art In recent years, when constructing a distributed processing environment on a network system, a side that requests processing called a client / server processing method from a method that conventionally completes all processing in one computer (hereinafter referred to as a client) There is an increasing tendency to adopt a system in which the functions are separated into a processing execution side (hereinafter referred to as a server) and commands and data are exchanged between them via communication means. This client
One technique for realizing a system that employs a server processing method is a remote procedure processing device.

A conventional remote procedure processing device will be described below. FIG. 9 shows an example of the configuration of a client / server system using a conventional remote procedure processing device. In FIG. 9, 901 is a conventional remote procedure processing device, 102 is a request entity that activates a remote procedure process request and obtains a result, 103 is a response entity that executes remote procedure process and responds with the result, and 104 is a remote procedure process request. A procedure requesting device for performing an actual remote procedure processing on the side, a reference numeral 105 is a procedure executing device for performing an actual remote procedure processing on the side, and a reference numeral 108 is a procedure for receiving a remote procedure processing request from a request entity using a communication means. The remote procedure execution device of the client which receives the post-processing result passed to the execution device,
Reference numeral 110 denotes a remote procedure execution device of a server which receives a remote procedure processing request from a procedure requesting device, passes it to a response entity, and returns the processing result to the procedure requesting device using a communication means, 9
An input queue device 02 temporarily stores a remote procedure processing request from an arbitrary client.

The operation of the conventional remote procedure processing performed by the remote procedure processing apparatus configured as described above will be described below with reference to FIG. In FIG. 10, an arbitrary request entity 102 uses the procedure requesting device 104 of the remote procedure processing device 901 to make a remote procedure processing request at any time, and the procedure execution device 105 of the remote procedure processing device 901 receives the request. Notify the response entity 103,
After the completion of the remote procedure processing, the response entity 103 makes a remote procedure processing response by using the procedure execution device 105, and the procedure requesting device 104 receives the response and replies to the request entity 102 as a confirmation. It is shown according to the flow of time.

At this time, if the request entity 102 needs time remote procedure processing at time T1 during the internal processing, it interrupts the internal processing and issues a remote procedure processing request. After that, when the processing result is returned from the remote procedure processing device 901 at time T2, the internal processing is continued again. In this way, the request entity 102 suspends its internal processing when the remote procedure processing request is activated (time T1, T3, and Tn-1). Furthermore, an interrupt occurs at the time when the remote procedure processing result is responded (time T2, T4, and Tn).

In addition, in the conventional remote procedure processing device,
Since it is necessary to receive requests from a plurality of clients at the same time and perform processing, a method is adopted in which the requests are temporarily suspended and the sequential processing is performed. This mechanism is shown in Figure 9.
Follow the explanation below. Requests from multiple clients are temporarily stored in the input queuing device 902 corresponding to or independent of the clients. The procedure execution device 105 takes one out of them and notifies the response entity. Alternatively, the response entity 103 sends a request from the input queuing device 902 through the procedure execution device at any time.
Take out one.

As described above, the conventional remote procedure processing device is characterized in that the main body for initiating the remote procedure processing is the client and the server is the passive body.

[0008]

However, in the above conventional configuration, when the client desires the remote procedure processing, the internal processing of the client itself must be temporarily suspended until the processing result is returned from the server. There is a problem that the client system cannot be operated efficiently. Furthermore, the number of input queue devices of the server increases in proportion to the number of clients that the server must support, and the control thereof becomes complicated. Therefore, the processing load on the input queue of the server increases as the number of clients increases. It had the problem of increasing. In addition, even when the client does not need to suspend the internal processing when the client makes a remote procedure processing request by some means,
When the client responds to the result of the remote procedure process from the server, an interrupt occurs, so it is necessary to temporarily suspend its own internal processing and respond to the response as described above. It has a problem that it cannot operate efficiently. Further, in the conventional configuration, since the client is the main body for initiating the remote procedure processing, there is a problem that the server cannot manage the processing frequency and the processing priority of the remote procedure processing request of an arbitrary client.

The present invention solves the above-mentioned conventional problems. Even when a client requests a remote procedure process, the server efficiently operates the system without interrupting the internal process of the client. Even if the number increases, the processing load on the input queue of the server is reduced. Even if the client receives a response from the server as a result of remote procedure processing after the internal processing of the client is not interrupted, the internal processing of the client The object of the present invention is to efficiently operate the system without interrupting the processing, and to manage the processing frequency and processing priority of the remote procedure processing request of an arbitrary client by the server.

[0010]

In order to achieve the above-mentioned object, the inquiry type remote procedure processing device of the present invention comprises:
A request identifier generation device that generates and notifies an identifier corresponding to a request, an output queue management device that temporarily stores requests and identifiers, a collection reception device that retrieves arbitrary requests and identifiers for request collection, and a procedure execution of requests and identifiers A procedure requesting device composed of a remote procedure executing device transmitting and receiving to the device, a monitoring device for monitoring the status of the response entity, a request collecting device for collecting requests to the procedure requesting device, a response and an identifier for the procedure requesting device A remote procedure execution device that sends and receives,
A procedure execution device configured by an output queue management device for temporarily storing a request and an identifier, and a procedure execution device configured to activate a request for remote procedure processing.

A second aspect of the present invention is, in the inquiry-type remote procedure processing device constituted by the above-mentioned device 1, a procedure request including an inquiry generation device for passing an identifier to a procedure execution device in response to a response inquiry accompanied by the identifier. The procedure requesting device comprises a device, an output queue managing device having means for temporarily storing a response to a request and an identifier, and a procedure executing device having an inquiry accepting device for fetching a response corresponding to the identifier. The response is activated.

In a third aspect of the present invention, in the inquiry type remote procedure processing device constituted by the above-mentioned device, the procedure requesting device of the above-mentioned 1 and the frequency of requests are measured, and the requests are collected in descending order of frequency. A procedure execution device including a request frequency measuring device for instructing the request collecting device,
The request collection sequence for any procedure requesting device is dynamically changed.

In a fourth aspect of the present invention, in the inquiry type remote procedure processing device constituted by the above-mentioned device, the request collecting device is arranged in the order of the above-mentioned procedure requesting device and the procedure requesting device designated by the request of the user. And a procedure execution device to which a collection priority management device having means for instructing the request collection device is added, and the request collection order for an arbitrary procedure request device is statically changed.

[0014]

According to the first aspect of the present invention, when the request entity issues the remote procedure processing request, the identifier corresponding to the request is generated by the request identifier generation device and returned to the request entity, and the request is the identifier. Together with this, it is temporarily stored in the output queue management device. Therefore, the request entity can continue the internal processing until the procedure request device notifies the result response corresponding to the identifier returned immediately after the remote procedure processing request. When the collection accepting device receives an inquiry as to whether or not there is a request issued by the request collecting device unless there is a stop command for the monitoring device, the request and identifier stored in the output queue management device are passed to the remote procedure executing device, and both It is passed to the procedure execution device by the communication means. on the other hand,
The remote procedure execution device of the procedure execution device temporarily stores the received request and identifier in the procedure output queue management device,
The procedure execution device extracts only the request from the procedure execution device, passes it to the response entity, and then obtains a response to the request from the response entity.
Retrieve the corresponding identifier from the output queue manager,
With the response, the remote procedure executing device is used to deliver the request to the remote procedure executing device in the requesting device. The procedure requesting device notifies the request entity of the response and the identifier. If the identifier accompanying the response matches the one at the time of the remote procedure processing request, the request entity determines that it is a response to the request. As a result, even when the request entity requests remote procedure processing, the internal processing of the request entity is not interrupted, which enables efficient operation of the client system, and even when the number of request entities supported by the response entity increases. The processing load can be reduced because the processing of the input queue does not occur in the response entity.

According to the second aspect of the present invention, the response corresponding to the remote procedure processing request can be obtained by activating the request entity side. First, when the procedure execution device obtains a response from the response entity, it temporarily stores it in the output queue management device together with the corresponding identifier. When the request entity passes the identifier at the time of request to the procedure requesting device, the inquiry generating device passes the identifier to the inquiry receiving device using the communication means. On the other hand, the inquiry reception device obtains a response corresponding to the request for the received identifier from the output queue management device and passes it together with the identifier to the remote procedure execution device, and both are passed by communication means to the remote procedure execution device of the procedure request device. Be done. The procedure requesting device notifies the request entity of the received response and the response among the identifiers. As a result, the request entity can obtain the remote procedure processing result at an arbitrary point of time, so that there is no sudden processing result notification and the internal processing of itself is not interrupted, so that the client system can operate efficiently.

According to the third aspect of the present invention, the request frequency measuring device in the procedure executing device measures a remote procedure processing request generated for each of a plurality of corresponding procedure requesting devices for a certain period of time and requests the request. The request collecting device is instructed periodically to collect the requests in the order of the procedure requesting device having the highest frequency. This allows the server system side to manage the processing frequency of the remote procedure processing request of the corresponding client system.

According to the fourth aspect of the present invention, the user of the inquiry-type remote procedure processing device requests the remote procedure processing requests for a plurality of procedure requesting devices corresponding to the procedure executing device to change the order of collecting requests. In the event of occurrence, the collection priority management device in the procedure execution device instructs the request collection device to collect the requests in the order requested by the user. This allows the server system side to manage the processing priority of the remote procedure processing request of an arbitrary client system.

[0018]

【Example】

(First Embodiment) A first embodiment of the present invention will be described below with reference to the drawings. FIG. 1 is a system configuration diagram of a client / server system according to a first embodiment of an inquiry type remote procedure processing device of the present invention. In FIG. 1, 101 is an inquiry type remote procedure processing device according to the present invention, 102 is a request entity for issuing a request for remote procedure processing and obtaining its response, 103 is a response entity for receiving a remote procedure processing request and returning a response after the request. 104 is a procedure requesting device for executing remote procedure processing in the client system, 105 is a procedure executing device for executing remote procedure processing in the server system, 106 is a request for remote procedure processing and 107 is a request identifier generating apparatus. An output queue management device that temporarily stores the generated identifier, 107 is a request identifier generation device that generates an identifier corresponding to a request for arbitrary remote procedure processing, and 108 is transmitting and receiving to and from the procedure execution device 105 using communication means. Remote procedure execution device,
Reference numeral 109 denotes a collection accepting device that passes an identifier corresponding to an arbitrary request in response to a remote command processing request collection command from the output queue management device 106 to the remote procedure execution device 108, and 110 uses communication means to 104. Remote procedure execution device for transmitting / receiving to / from the procedure requesting device, 111 is a request collecting device for periodically issuing a command for collecting requests for remote procedure processing to 104 procedure requesting devices unless a stop command is issued, and 112 is a remote device for 110 An output queue management device for temporarily storing the request and identifier of the remote procedure processing received by the procedure execution device, 113 monitors the response entity 103 and cancels the collection command to the request collection device 111 when an error is detected Is a monitoring device that commands.

The operation of the inquiry type remote procedure processing device configured as described above will be described with reference to FIG. In FIG. 2, reference numerals 102 to 113 denote the respective elements constituting the inquiry type remote procedure processing device described above, and (1) to (13) are the order of processing steps.
First, when the request entity 102 issues a request for remote procedure processing to the procedure request device 104 (step (1)),
The identifier corresponding to the request is the request identifier generation device 107.
And is returned to the request entity 102 (step (2)). The request is output queue management device 10 in procedure request device 104 together with the generated corresponding identifier.
It is temporarily stored in step 6 (step (3)). Request entity 10
In step 2, the internal processing continues without interruption until the procedure request device 104 notifies the response corresponding to the returned identifier. On the other hand, the monitoring device 113 uses the response entity 1
03, receives a processing interruption command from the response entity 103, or detects an abnormality in the application entity 103, instructs the request collection device 111 to stop collecting requests for remote procedure processing (step (4)). . The request collection device 111
Unless there is a cancel instruction from the monitoring device 113, a collection instruction of the remote procedure processing request is periodically issued to the collection acceptance device 109 of the arbitrary procedure requesting device 104 using the communication means (step (5)).

At this time, the collection acceptance device 1 that has received the collection instruction
If there is a request in the output queue management device 106, the device 09 passes the identifier corresponding to the arbitrary request to the remote procedure execution device 108 (step (6)). The remote procedure execution device 108 uses the communication means to communicate the received request and identifier to the remote procedure execution device 11 in the procedure execution device 105.
Pass to 0 (step (7)). Remote procedure execution device 11
0 temporarily stores the received request and identifier in the output queue management device 112 (step 8). Then, the procedure execution device 105 extracts only the request from the output queue management device 112 and passes it to the response entity 103 (step (9)). After that, the procedure execution device 105 determines that the response entity 1
When the response of the remote procedure processing to the request is obtained from 03 (step (10)), the identifier corresponding to the response,
That is, the identifier corresponding to the request corresponding to the response is taken out from the output queue management device 112 and passed to the remote procedure execution device 110 together with the response (step (11)).
The remote procedure execution device 110 passes the received response and identifier to the remote procedure execution device 108 in the procedure request device 104 using the communication means (step (12)). Then, the procedure request device 104 notifies the request entity 102 of the response and the identifier received by the remote procedure execution device 108 (step (13)).

If the identifier accompanying the response matches the previously issued remote procedure process request, the request entity 102 determines that the request is a response to the request. As a result, even if the request entity 102 requests the remote procedure processing, the internal processing of the request entity 102 is not interrupted, so that the client system can be operated efficiently. Further, the response entity 103 can reduce the processing load of the server system because the response entity 103 does not perform the processing of the input queue even when the number of request entities 102 that the response entity 103 has to handle increases.

(Second Embodiment) A second embodiment of the present invention will be described below with reference to the drawings. FIG. 3 is a system configuration diagram of a client / server system according to a second embodiment of the inquiry type remote procedure processing device of the present invention. In FIG. 3, 101 is an inquiry type remote procedure processing device according to the present invention similar to that of the first embodiment, 102 is a request entity similar to the first embodiment, 103 is a response entity similar to the first embodiment, and 104 is the first embodiment. Procedure requesting device similar to 10
5 is a procedure execution device similar to that of the first embodiment, 106 is an output queue management device similar to that of the first embodiment, 107 is a request identifier generation device similar to that of the first embodiment, and 108 is a remote procedure execution similar to that of the first embodiment. A device, 109 is a collection acceptance device similar to that of the first embodiment, 110 is a remote procedure execution device similar to that of the first embodiment, 111 is a request collection device similar to that of the first embodiment, and 301 is a remote procedure process in addition to the first embodiment. An output queue management device that temporarily stores an identifier corresponding to a response, 113 is a monitoring device similar to that of the first embodiment, and 302 is the procedure execution device 10 that uses the communication means to identify the identifier input from the request entity 102.
An inquiry generating device to be passed to the inquiry receiving device in 5,
Reference numeral 303 denotes an inquiry accepting device that extracts a response to the remote procedure process corresponding to the identifier received from the inquiry generating device 302 in the procedure requesting device 104 from the output queue managing device 301 and transfers it to the remote procedure executing device.

The operation of the inquiry type remote procedure processing device configured as described above will be described with reference to FIG. In FIG. 4, 102 to 113 and 301 to 303 are the respective elements that constitute the inquiry type remote procedure processing device described above, and (1) to (15) are the order of processing steps. The processing (steps (1) to (10)) from when the request entity 102 issues a request for remote procedure processing to the procedure requesting device 104 until the procedure execution device 105 receives the response from the response entity 103 is the embodiment. Since it is equal to 1, it is omitted. After that, the procedure execution device 10
Reference numeral 5 denotes an identifier corresponding to the response to the request for remote procedure processing obtained from the response entity 103 and the output queue management device 3
It is temporarily stored in 01 (step (10)). At this time, the identifier corresponding to the response is the same as the identifier stored in the output queue management device together with the request corresponding to the response. Then, when the request entity 102 wants to obtain a response to the request for the remote procedure processing performed previously, the request entity 102 sends the identifier obtained from the procedure request apparatus 104 to the procedure request apparatus 10 when the request is made.
4 (step (11)). Inquiry generator 3
02 passes the identifier to the inquiry reception device 303 in the procedure execution device 105 using the communication means (step (12)). The inquiry reception device 303 extracts the response to the request for remote procedure processing corresponding to the received identifier from the output queue management device 301 using the identifier as a key, and passes it together with the identifier to the remote procedure execution device 110 (step (13)). The remote procedure execution device 110 passes the received response and identifier to the remote procedure execution device 108 of the procedure requesting device 104 using the communication means (step 14). The procedure request device 104 notifies the request entity 102 of the response and the identifier received by the remote procedure execution device 108 (step (15)). As a result, the request entity 102 can obtain and obtain a remote procedure processing response at any time, so that there is no notification of a sudden response from the procedure requesting apparatus 104, and the internal processing of itself is not interrupted, so that the efficiency of the client system is improved. It is possible to perform good operation.

(Embodiment 3) A third embodiment of the present invention will be described below with reference to the drawings. FIG. 5 is a system configuration diagram of a client / server system according to a third embodiment of the inquiry type remote procedure processing device of the present invention. In FIG. 5, 101 is an inquiry-type remote procedure processing device according to the present invention, which is the same as in the first embodiment, 102 is a request entity similar to the first embodiment, 103 is a response entity similar to the first embodiment, and 104 is the first embodiment. Procedure requesting device similar to 10
5 is a procedure execution device similar to that of the first embodiment, 106 is an output queue management device similar to that of the first embodiment, 107 is a request identifier generation device similar to that of the first embodiment, and 108 is a remote procedure execution similar to that of the first embodiment. A device, 109 is a collection acceptance device similar to that of the first embodiment, 110 is a remote procedure execution device similar to that of the first embodiment, 111 is a request collection device similar to that of the first embodiment, and 112 is a queue management device similar to that of the first embodiment. , 113 are monitoring devices similar to those in the first embodiment, and 501 is a request frequency measuring device for measuring the frequency of remote procedure processing and instructing the request collecting device 111 to collect requests in descending order of frequency.

The operation of the inquiry type remote procedure processing device configured as described above will be described with reference to FIG. In FIG. 6, 104, 105, 110, 11
Reference numerals 1 and 501 denote the respective elements constituting the inquiry type remote procedure processing device described above, and 601 exists in the request frequency measuring apparatus, and requests the remote procedure processing for each procedure requesting apparatus 104 from the remote procedure executing apparatus 110. A counter unit 602 that obtains and integrates each number is provided in a request frequency measuring device 602 and is a control unit 603 for each predetermined elapsed time.
A timer unit 603 that generates an interrupt is present in the request frequency measuring device, and when the timer unit 602 generates an interrupt, the integrated value of the remote procedure processing request up to the present from the counter unit is acquired, rearranged in descending order of the value, and then acquired. Counter section 60
And a control unit that resets the integrated value of 1 to zero,
(1) to (6) are the order of processing steps. A request for remote procedure processing issued through the procedure requesting device 104 is always passed through the procedure executing device in the procedure executing device 105 (step (1)). The counter unit 601 accumulates the number of requests in the integration counter for each procedure requesting device 104 held by itself through the remote procedure executing device 110 (step (2)). On the other hand, the timer unit 602 notifies the control unit 603 of an interrupt when the time set by the system or the user has elapsed (step (3)). The control unit 603 that has received this interrupt acquires the value of the cumulative counter for each procedure requesting device 104 that is currently accumulated from the counter unit 601, and rearranges the value in descending order of the value (step (4)). And the control unit 603
Resets the value of each integration counter of the counter unit 601 to zero (step (5)). Request frequency measuring device 50
In accordance with this rearranged order, 1 instructs the request collection device 111 to collect the request for remote procedure processing to the corresponding procedure request device 104 (step (6)). As a result, the request collection order can be changed according to the frequency of requests for remote procedure processing from the procedure requesting device 104. Therefore, the server system side must manage the processing frequency of remote procedure processing requests of the corresponding client system. Is possible.

(Embodiment 4) A fourth embodiment of the present invention will be described below with reference to the drawings. FIG. 7 is a system configuration diagram of a client / server system according to a fourth embodiment of the inquiry type remote procedure processing device of the present invention. In FIG. 7, 101 is an inquiry-type remote procedure processing device according to the present invention, which is the same as in the first embodiment, 102 is a request entity similar to the first embodiment, 103 is a response entity similar to the first embodiment, and 104 is the first embodiment. Procedure requesting device similar to 10
5 is a procedure execution device similar to that of the first embodiment, 106 is an output queue management device similar to that of the first embodiment, 107 is a request identifier generation device similar to that of the first embodiment, and 108 is a remote procedure execution similar to that of the first embodiment. A device, 109 is a collection acceptance device similar to that of the first embodiment, 110 is a remote procedure execution device similar to that of the first embodiment, 111 is a request collection device similar to that of the first embodiment, and 112 is a queue management device similar to that of the first embodiment. , 113 is a monitoring device similar to that of the first embodiment, and 701 is a request collecting device 11 that collects requests in order from those specified by the user's request.
1 is a collection priority management device.

The operation of the inquiry type remote procedure processing device configured as described above will be described with reference to FIG. In FIG. 8, 104, 105, 110, 11
Reference numerals 1 and 701 denote the respective elements that make up the inquiry-type remote procedure processing device described above. Reference numeral 801 is a request frequency measuring apparatus that is present in the request frequency measuring apparatus and requests remote procedure processing for each procedure requesting apparatus 104 from the remote procedure executing apparatus 110. A counter unit 802 that obtains and accumulates each number obtains an integrated value of the remote procedure processing requests from the counter unit 801 up to the present time according to a request from the user 803, notifies the user 803, and notifies the user 803. And an input / output unit that resets the integrated value of the counter unit 801 to zero according to an instruction,
(1) to (9) are the order of processing steps. A request for remote procedure processing issued through the procedure requesting device 104 is always passed through the procedure executing device in the procedure executing device 105 (step (1)). The counter unit 801 accumulates the number of requests in the integration counter for each procedure requesting device 104 held by itself through the remote procedure executing device 110 (step (2)). On the other hand, when the user 803 tries to change the order of the procedure requesting device for collecting the remote procedure processing request at any time, the user 803 can give the instruction to the input / output unit 802 to obtain the current request status ( Step (3)). In this case, the input / output unit 802 acquires from the counter unit 801 the value of the cumulative counter for each procedure requesting device 104 that is currently accumulated (step (4)), and notifies the user 803 via the input / output unit 802. (Step (5)). The processing from steps (3) to (5) is not always necessary, and the user 80
It depends on the requirement of 3. The request for changing the order of the procedure requesting device that collects the request for remote procedure processing by the user 803 (step (6)) is directly notified to the request collecting device 111 of the collecting order by the collection priority management device 701 ( Step (7)). When the user 803 wants to reset the accumulated requests for remote procedure processing (step (8)), the input / output unit 802 resets the value of each integration counter of the counter unit 801 to zero (step (9)). ). As a result, the request collection order can be changed according to the request from the user of the server system, so that the server system can manage the processing priority of the remote procedure processing request of any client system. Become.

[0028]

As described above, according to the present invention, a procedure requesting device including a request identifier generating device, an output queue managing device, a collection receiving device, a remote procedure executing device, and an inquiry generating device, a monitoring device, and a request. By providing a procedure execution device consisting of a collection device, a remote procedure execution device, an output queue management device, an inquiry reception device, a request frequency measurement device, and a collection priority management device, internal processing of the client when a remote procedure processing request is made. The system can be operated efficiently without interruption, the processing load of the server can be reduced even if the number of corresponding clients increases, and the server manages the processing frequency and processing priority of requests from arbitrary clients. It is possible to realize excellent remote procedure processing that can be performed.

[Brief description of drawings]

FIG. 1 is a system configuration diagram of a client / server system including an inquiry type remote procedure processing device according to a first embodiment of the present invention.

FIG. 2 is a processing diagram showing a flow of processing using the inquiry type remote procedure processing device according to the first embodiment of the present invention.

FIG. 3 is a system configuration diagram of a client / server system including an inquiry type remote procedure processing device according to a second embodiment of the present invention.

FIG. 4 is a processing diagram showing a flow of processing using the inquiry type remote procedure processing device according to the second embodiment of the present invention.

FIG. 5 is a system configuration diagram of a client / server system including an inquiry type remote procedure processing device according to a third embodiment of the present invention.

FIG. 6 is a processing diagram showing a flow of processing using the inquiry type remote procedure processing device according to the third embodiment of the present invention.

FIG. 7 is a system configuration diagram of a client / server system including an inquiry type remote procedure processing device according to a fourth embodiment of the present invention.

FIG. 8 is a processing diagram showing a flow of processing using the inquiry type remote procedure processing device according to the fourth embodiment of the present invention.

FIG. 9 is a system configuration diagram of a client / server system including a conventional remote procedure processing device.

FIG. 10 is a processing diagram showing the flow of remote procedure processing using a conventional remote procedure processing device in time series.

[Explanation of symbols]

 101 Inquiry-type remote procedure processing device 102 Request entity 103 Response entity 104 Procedure requesting device 105 Procedure executing device 106 Output queue managing device 107 Request identifier generating device 108 Remote procedure executing device 109 Collection accepting device 110 Remote procedure executing device 111 Request collecting device 112 Output Queue Management Device 113 Monitoring Device 301 Output Queue Management Device 302 Inquiry Generation Device 303 Inquiry Reception Device 501 Request Frequency Measurement Device 601 Counter Unit 602 Timer Unit 603 Control Unit 701 Collection Priority Management Device 801 Counter Unit 802 Input / Output Unit 803 User 901 Remote procedure processor 902 Input queue device

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Satoshi Matsumoto 1006 Kadoma, Kadoma City, Osaka Prefecture Matsushita Electric Industrial Co., Ltd.

Claims (4)

[Claims] 1. A request identifier generating device having means for generating an identifier corresponding to a request for remote procedure processing from a request entity and notifying the request entity of the request of the identifier.
An output queue management device having means for temporarily storing a corresponding identifier together with a request, and means for extracting an identifier corresponding to an arbitrary request from the output queue management device for collecting requests from the procedure execution device and passing it to the remote procedure execution device. Remote procedure execution having a collection accepting device having: a means for passing an identifier corresponding to a request to a procedure execution device using communication means, and a means for receiving a response and an identifier corresponding to a request from a procedure execution device using communication means A procedure requesting device configured from a request entity that inputs a request for remote procedure processing from the request entity and outputs a response and an identifier corresponding to the request to the request entity, and monitors the status of the response entity and detects anomalies in the response entity If there is a monitoring device that has a means for instructing the request collection device to give a request collection stop command, and unless there is a stop command from the monitoring device, A request collecting device having a means for periodically collecting requests to the procedure requesting device using communication means in a specified order or an instructed order; and an identifier corresponding to a remote procedure processing response from a response entity. A remote procedure execution device having means for passing to the procedure requesting device using the communication means and means for receiving the identifier corresponding to the request from the procedure requesting device using the communication means, and an identifier corresponding to the request received by the remote procedure execution device And an output queue management device having means for temporarily storing
A query type characterized by comprising a procedure execution device for outputting a request for remote procedure processing to a response entity and inputting a response corresponding to the request from the response entity, and the procedure execution device for invoking a request for remote procedure processing. Remote procedure processor. 2. A query generation device having means for passing the identifier to a procedure execution device by means of communication means in response to a response inquiry of remote procedure processing from a request entity accompanied by an identifier obtained at the time of requesting remote procedure processing. From a request entity composed of a request identifier generation device, an output queue management device device, a collection reception device, and a procedure request device composed of a remote procedure execution device to a request input and request entity for remote procedure processing A procedure requesting device that outputs a response corresponding to a request, an output queue management device that adds a means for temporarily storing a response to a remote procedure processing request from a response entity together with a corresponding identifier, and a query generation device Means for retrieving the response of the corresponding remote procedure processing from the output queue management device by the identified identifier and passing it to the remote procedure execution device And a procedure execution device that outputs a request for remote procedure processing to a response entity composed of a monitoring device, a request collection device, and a remote procedure execution device, and inputs a response corresponding to the request from the response entity. 2. The inquiry-type remote procedure processing apparatus according to claim 1, wherein the procedure requesting apparatus is configured to activate the response of the remote procedure processing. 3. A request frequency having a procedure requesting device and means for instructing the request collecting device to measure the frequency of requests for remote procedure processing from an arbitrary procedure requesting device and to collect the requests in descending order of frequency. The inquiry-type remote procedure processing apparatus according to claim 1, wherein the procedure execution apparatus including a measuring apparatus is configured to dynamically change a request collection order for an arbitrary procedure requesting apparatus. 4. A collection priority management having a procedure requesting device and means for instructing the request collecting device to collect the request in the order of the procedure requesting device designated by the request of the user of the inquiry type remote procedure processing device. 2. The inquiry type remote procedure processing apparatus according to claim 1, wherein the procedure execution apparatus including the apparatus is added to statically change the order of collecting requests for an arbitrary procedure requesting apparatus.