TWI556612B - Timeout controlling unit for remote procedure call and method for remote procedure call - Google Patents

Description

Timeout control unit and remote program call method suitable for remote program call

The present invention relates to a timeout control unit, and more particularly to a timeout control unit and a remote program call method suitable for remote program calls.

Remote Procedure Call (RPC) is an important feature of the operation of distributed application systems. Individual systems can call other system programs through RPC during operation. After other system operation results are returned, the original process (thread) is continued. . Although RPC has a synchronous and asynchronous operation, RPC often operates in a synchronous manner based on business logic requirements. However, these decentralized processes will cause different perceptions of the operating results due to the session timeout, which seriously affects the correctness of business logic.

Synchronous RPC is often used for corporate trading activities. The timeout for the talks is mostly set by the requester, and the setting cannot be changed according to the object. more. Therefore, when the timeout of the talks is too short, the remote program has not been completed, and the requester actively interrupts, which is likely to cause the state of the requester and the responder to be inconsistent. When the timeout of the talks is too long, the user and related resources are locked and cannot be released when the system enters the waiting state, which is likely to cause a deadlock.

In the face of the above problems, the current common practice involves the use of a common technology platform. For example, both the requester and the respondent use Java Session Bean to ensure that the system program and the session have the same life cycle. However, when faced with a heterogeneous technology platform, this method cannot be implemented. Be applicable. Another method is that both the requesting party and the responding party adopt a technology that conforms to the transaction specification and perform the compensation action in the abnormal situation, but the compensation action is another RPC calling procedure, and there is also a risk of failure, so Will cause infinite compensation loops. Therefore, how to design a system or method to solve the above problems is one of the current important research and development topics, and it has become an urgent need for improvement in related fields.

Accordingly, one aspect of the present invention is to provide a timeout control unit suitable for use in a Remote Procedure Call. The timeout control unit includes a blocker, a message agent module, and a session control module. When receiving the processing request sent by the requesting unit, the timeout control unit transmits the processing request to a responding unit, so that the responding unit processes the processing request, and the meeting control module is used to arrive at a preset time. When judging the responder unit is Whether to return a processing result, and when the processing result is not returned to the requesting unit, the negotiation control module controls the blocking device to send a blocking request to the responding unit, so that the responding unit interrupts the processing according to the blocking request. The processing of the request, and the message proxy module transmits a session timeout message to the requesting unit.

According to an embodiment of the invention, the blocker is further configured to determine whether the responding unit successfully interrupts the processing of the processing request. If not, the message proxy module transmits a reservation status message to the requesting unit, and when the responding unit returns the processing result, the message proxy module transmits a callback message to the requesting unit.

According to another embodiment of the present invention, the blocker is configured to block a status message returned by the responding unit, and determine whether the responding unit successfully interrupts the processing of the processing request.

According to still another embodiment of the present invention, the timeout control unit further includes a timer, and the talk control module is further configured to start the timer when the timeout control unit receives the processing request, and arrive at the timer When the time is preset, it is judged whether the responding unit returns the above processing result.

According to still another embodiment of the present invention, the conversation control module is further configured to store a processing program identifier that is returned by the responding unit to one of the timeout control units corresponding to the processing request.

According to still another embodiment of the present invention, the blocking request includes the processing program identification code, and the responding unit interrupts the processing of the processing request according to the processing program identification code in the blocking request.

According to still another embodiment of the present invention, the timeout control unit is further included Contains a request message queue. The request message queue is configured to receive and temporarily store the processing request, and the negotiation control module is further configured to control the request message queue to transmit the processing request to the responding unit.

According to still another embodiment of the present invention, the timeout control unit further includes a response message queue. The response message queue is used to receive and temporarily store the above processing results.

Another aspect of the present invention provides a remote program calling method, comprising the steps of: receiving a processing request sent by a requesting unit by using a timeout control unit; and transmitting the processing request to the processing request by using a timeout control unit a responding unit, such that the responding unit processes the processing request; when a predetermined time arrives, determining whether the responding unit returns a processing result to the timeout control unit; if yes, using the timeout control unit to process the processing result Returning to the requesting unit; and if not, transmitting a blocking request to the responding unit by using the timeout control unit, so that the responding unit interrupts the processing of the processing request according to the blocking request, and transmits the using the timeout control unit Talk about the timeout message to the requester unit.

According to an embodiment of the present invention, the remote program calling method further includes: using a timeout control unit to determine whether the responding unit successfully interrupts the processing of the processing request; if not, transmitting a reservation status message to the request by using the timeout control unit The square unit, and when the responding unit returns the processing result to the timeout control unit, transmits a callback message to the requesting unit by using the timeout control unit.

According to another embodiment of the present invention, in the remote program calling method, the timeout control unit is used to determine whether the responding unit is successfully interrupted. In the step of processing the request, the timeout control unit determines whether the responder unit successfully interrupts the processing of the processing request according to the blocking status message returned by the responding unit to one of the timeout control units.

According to still another embodiment of the present invention, the remote program calling method further includes: receiving and storing a processing program identification code that is returned by the responding unit to one of the timeout control units corresponding to the processing request.

According to still another embodiment of the present invention, in the remote program calling method, the blocking request includes the processing program identification code, and the responding unit interrupts the processing of the processing request according to the processing program identification code in the blocking request.

The advantage of applying the present invention is that by using a time-out control unit in a system for performing a remote program call, the interaction process of the remote program call is monitored and managed, in particular, whether the program is time-out and overtime Provide corresponding processing when it occurs, thus ensuring consistency of system transaction results. In the present invention, the time for judging whether or not the timeout can be specified according to different calling objects is highly flexible. In addition, the existing remote program call system can perform the technical means of the present invention only by slightly modifying the relevant code, and the present invention is generally applicable to various different technology platforms. The technology can be implemented by an intermediary device between the requesting party and the responding party, that is, the requesting party and the responding party do not need to modify the main logic of the program. The device proposed by the invention can be independently controlled and managed by itself, and has the advantages of being freely adjustable for the length of Timeout, and is commonly used in various technical platforms.

110, 110a‧‧‧ time-out control unit

112, 112a‧‧‧ meeting control module

114‧‧‧Blocker

116, 116a‧‧‧Message Agent Module

120‧‧‧Handling requests

121‧‧‧Processing program identification code

122‧‧‧Process results

124‧‧‧Block request

126‧‧‧Talks overtime message

128‧‧‧Retention status message

129‧‧‧callback message

130‧‧‧Requester unit

132‧‧‧Blocking status message

140‧‧‧Respondent unit

210‧‧‧Timer

220‧‧‧Request message queue

222‧‧‧Response message queue

302, 304, 306, 308, 310, 402, 404, 502‧ ‧ steps

FIG. 1 is a block diagram of a timeout control unit suitable for a remote program call according to an embodiment of the present invention.

2 is a block diagram of a timeout control unit suitable for a remote program call according to an embodiment of the present invention.

FIG. 3 is a schematic flow chart of a method for calling a remote program according to an embodiment of the present invention.

FIG. 4 is a schematic flow chart of a method for calling a remote program according to an embodiment of the present invention.

FIG. 5 is a schematic flow chart of a method for calling a remote program according to an embodiment of the present invention.

The embodiments are described in detail below with reference to the accompanying drawings, but the embodiments are not intended to limit the scope of the invention, and the description of the structure operation is not intended to limit the order of execution, any component recombination The structure, which produces equal devices, is within the scope of the present invention. In addition, the drawings are for illustrative purposes only and are not drawn to the original dimensions. For ease of understanding, the same elements in the following description will be denoted by the same reference numerals.

The terms used in the entire specification and the scope of the patent application, unless otherwise specified, generally have the ordinary meaning of each term used in the field, the content disclosed herein, and the particular content. Certain terms used to describe the disclosure are discussed below or elsewhere in this specification to provide additional reference to those skilled in the art in the description of the disclosure. guide.

In this document, "one" and "the" can be used to mean one or more, unless the article specifically defines the article. It will be further understood that the terms "comprising", "comprising", "having", and <RTIgt; One or more of its other features, regions, integers, steps, operations, elements, components, and/or groups thereof.

Please refer to Figure 1. FIG. 1 is a block diagram of a timeout control unit 110 suitable for a remote procedure call according to an embodiment of the present invention. The timeout control unit 110 can be used to provide intermediate services to the requestor unit 130 and the responder unit 140.

In an embodiment, the requesting unit 130 may be a requesting party of a transaction activity, such as a card swipe machine, an enterprise resource planning system (ERP system) endpoint, or a list of available Electronic device for purchasing goods. The responder unit 140 can be a responder that processes transaction activities, such as a card authorization server, an enterprise resource planning system signature management system, or an e-commerce server. The timeout control unit 110 is configured to provide an intermediate service to provide corresponding processing when the program of the authorization or confirmation of the transaction activity between the requestor unit 130 and the responder unit 140 occurs during a session timeout. .

In this embodiment, the timeout control unit 110 includes a session control module 112, a blocker 114, and a message. A message agent module 116. In an embodiment, the timeout control unit 110 includes at least one processor and a memory, and the talk control module 112, the blocker 114, and the message proxy module 116 are stored in the memory, and The processor performs its function. In another embodiment, the talk control module 112, the blocker 114, and the message proxy module 116 are hardware components of a system chip or other executable instructions.

In one embodiment, the timeout control unit 110 is an intermediary device that is independent of the requestor unit 130 and the responder unit 140. In another embodiment, the timeout control unit 110 is integrated into the requestor unit 130 or the responder unit 140 in a software manner. In yet another embodiment, the timeout control unit 110 is a hardware component of a system chip or other executable instructions included in the requestor unit 130 or the responder unit 140.

When receiving the processing request 120 sent by the requesting unit 130, the timeout control unit 110 transmits the processing request 120 to the responding unit 140, so that the responding unit 140 processes the processing request 120. The meeting control module 112 is configured to determine whether the responding unit 140 returns a processing result 122 when a predetermined time arrives. If so, the control module 112 controls the message proxy module 116 to transmit the processing result 122 back to the requestor unit 130. If no (ie, the processing result 122 is not returned to the requestor unit 130), the negotiation control module 112 controls the blocker 114 to send a blocking request 124 to the responder unit 140, such that the responder unit 140 interrupts the processing of the processing request 120 according to the blocking request 124, and the message proxy module 116 transmits a talk timeout message 126 to The requester unit 130. It should be noted that the preset time is an adjustable time, and the timeout control unit 110 may adjust the preset time according to the type of the processing request 120.

In another embodiment, the blocker 114 is further configured to determine whether the responder unit 140 successfully interrupts the processing of the processing request 120 according to the blocking request 124. If not, the message proxy module 116 transmits a reservation. The status message 128 is sent to the requester unit 130, and when the responder unit 140 returns the processing result 122, the message proxy module 116 transmits a callback message 129 to the requestor unit 130. In an embodiment, the blocker 114 determines whether the responder unit 140 successfully interrupts the processing request 120 according to the blocking status message 132 returned by the responder unit 140.

In an example, the responder unit 140 successfully interrupts the processing of the processing request 120 after receiving the blocking request 124, and the responding unit 140 returns the blocking status message 132 according to the resistance. The process of successfully interrupting the processing request 120 is described in the off status message 132.

In another example, the responder unit 140 may not interrupt the processing of the processing request 120 after receiving the blocking request 124 due to system resource locking or some system factors. At this time, the responding unit 140 returns. The status message 132 is blocked and the processing of the processing request 120 cannot be interrupted in the blocking status message 132. In this example, the message broker module 116 transmits a reservation status message 128 to the requestor unit 130, and the requestor unit 130 records and retains the status of the processing request 120 based on the reservation status message 128. Thereafter, when the responder unit 140 completes the location When the processing of the request 120 is performed and the processing result 122 is returned, the message proxy module 116 transmits the callback message 129 to the requesting unit 130, and then the requesting unit 130 according to the callback message 129 and the foregoing The status record of request 120 is processed and the processing request 120 is completed.

In another embodiment, the meeting control module 112 is further configured to store the processing program identifier 121 returned by the responding unit 140 to one of the timeout control units 110 corresponding to the processing request 120. In still another embodiment, the blocking request 124 includes the handler identification code 121, and the responder unit 140 processes the interrupt request 120 based on the handler identification code 121 in the blocking request 124. In this embodiment, the responder unit 140 utilizes at least one processor to simultaneously process multiple requests from a plurality of requestor units or timeout control units, and assign a corresponding handler identifier to each request. . When the responder unit 140 receives the blocking request 124 including the handler identifier 121 corresponding to the processing request 120, the at least one processor of the responder unit 140 interrupts the processing request according to the handler identifier 121. 120 processing.

Please refer to Figure 2. FIG. 2 is a block diagram of a timeout control unit 110a suitable for a remote program call according to an embodiment of the present invention. Compared with the timeout control unit 110 shown in FIG. 1 , in the embodiment, the timeout control unit 110a further includes a timer 210, a request message queue 220, and a response message. Response message queue 222. In one embodiment, the timer 210 is implemented by a chip, and the request message queue 220 and the response message queue 222 are implemented by storage elements such as a memory or a hard disk. Another In one embodiment, the timeout control unit 110a includes at least one processor and a memory, and the timer 210 is implemented by a timing program or a module and stored in the memory, and executed by the processor. Features. The functions and operations of the Talk Control Module 112a and the Message Agent Module 116a are similar to those of the Talk Control Module 112 and the Message Agent Module 116 shown in FIG. 1 and will not be described herein.

In this embodiment, the meeting control module 112a is further configured to start the timer 210 when the timeout control unit 110a receives the processing request 120, and determine that the timer 210 reaches the preset time. Whether the response unit unit 140 returns the processing result 122. The request message queue 220 is configured to receive the temporary storage request 120, and the negotiation control module 112a is further configured to control the request message queue 220 to transmit the processing request 120 to the responder unit 140. The response message queue 222 is configured to receive and temporarily store the processing result 122. When the message proxy module 116a wants to return the processing result 122 to the requestor unit 130, the message proxy module 116a receives the response message. The processing result 122 is read in column 222.

FIG. 3 is a schematic flow chart of a method for calling a remote program according to an embodiment of the invention. The remote program calling method can be implemented as a computer program product (such as an application) and stored in a computer readable recording medium, and the computer can execute the remote program calling method after reading the recording medium. Computer-readable recording media can be read-only memory, flash memory, floppy disk, hard disk, optical disk, flash drive, tape, network accessible database or familiar with the art can easily think of the same The function of the computer can read the recording medium.

This remote program call method can be applied to, but not limited to, the timeout control unit 110 as shown in FIG. For convenience and clarity of explanation, the following description of the remote program calling method is described in conjunction with the timeout control unit 110 shown in FIG.

In step 302, the processing request 120 sent by the requester unit 130 is received by the timeout control unit 110.

In step 304, the processing request 120 is transmitted to the responder unit 140 by the timeout control unit 110 such that the responder unit 140 processes the processing request 120.

In step 306, the meeting control module 112 determines whether the responding unit 140 returns the processing result 122 to the timeout control unit 110 when a preset time arrives. If yes, go to step 308; if no, go to step 310.

In the step 308, the conversation control module 112 of the timeout control unit 110 controls the message proxy module 116 to transmit the processing result 122 back to the requester unit 130.

In the step 310, the talk control module 112 of the timeout control unit 110 controls the blocker 114 to send the blocking request 124 to the responder unit 140, so that the responder unit 140 is interrupted according to the blocking request 124. The processing request 120 processes and transmits the talk timeout message 126 to the requestor unit 130 using the message broker module 116 of the timeout control unit 110.

Please refer to Figure 4. FIG. 4 is a schematic flow chart of a method for calling a remote program according to an embodiment of the invention. Compared to Figure 3 The far-end program calling method further includes step 402 and step 404 in this embodiment. This remote program call method can be applied to, but not limited to, the timeout control unit 110 as shown in FIG. For convenience and clarity of explanation, the following description of the remote program calling method is described in conjunction with the timeout control unit 110 shown in FIG.

In step 402, the blocker 114 of the timeout control unit 110 determines whether the responder unit 140 successfully interrupts the processing of the processing request 120.

If not, in step 404, the message status module 128 of the timeout control unit 110 is used to transmit the reservation status message 128 to the requestor unit 130, and the response result unit 122 is returned to the response unit 122 to the When the control unit 110 is used, the message proxy module 116 of the timeout control unit 110 transmits the callback message 129 to the requestor unit 130.

Please refer to Figure 5. FIG. 5 is a schematic flow chart of a method for calling a remote program according to an embodiment of the invention. In the present embodiment, the remote program calling method further includes step 502 and step 510, as compared with the remote program calling method shown in FIG. This remote program call method can be applied to, but not limited to, the timeout control unit 110 as shown in FIG. For convenience and clarity of explanation, the following description of the remote program calling method is described in conjunction with the timeout control unit 110 shown in FIG.

In step 502, the timeout control unit 110 receives and uses the negotiation control module 112 to store the handler ID 121 corresponding to the processing request 120 that the responder unit 140 returns to the timeout control unit 110.

In contrast to step 310, in step 510, the blocking request 124 includes a handler identification code 121, and the responder unit 140 interrupts the processing of the processing request 120 based on the handler identification code 121 in the blocking request 124.

It should be understood that the steps mentioned in the present embodiment can be adjusted according to actual needs, and can be performed simultaneously or partially simultaneously, unless the order is specifically stated.

In summary, the present invention monitors and manages the interaction process of a remote program call by using a timeout control unit in a system for performing a remote program call, in particular, determining whether the program is out of date, and Corresponding processing is provided when the time occurs, so as to ensure the consistency of the system transaction results.

In the present invention, the time for judging whether or not the timeout can be specified according to different calling objects is highly flexible. In addition, the existing remote program call system can perform the technical means of the present invention by only slightly modifying the relevant code. The technology can be implemented by an intermediary device between the requesting party and the responding party, that is, the requesting party and the responding party do not need to modify the main logic of the program. The device proposed by the invention can be independently controlled and managed by itself, and has the advantages of being freely adjustable for the length of Timeout, and is commonly used in various technical platforms.

The present disclosure has been disclosed in the above embodiments, but it is not intended to limit the disclosure, and any person skilled in the art can make various changes and refinements without departing from the spirit and scope of the disclosure. The scope of protection of the disclosure is defined by the scope of the patent application attached. Prevail.

110‧‧‧Timed Control Unit

112‧‧‧Talk Control Module

114‧‧‧Blocker

116‧‧‧Message Agent Module

120‧‧‧Handling requests

121‧‧‧Processing program identification code

122‧‧‧Process results

124‧‧‧Block request

126‧‧‧Talks overtime message

128‧‧‧Retention status message

129‧‧‧callback message

130‧‧‧Requester unit

132‧‧‧Blocking status message

140‧‧‧Respondent unit

Claims (14)

A timeout control unit suitable for a remote procedure call, the timeout control unit comprising: a blocker; a message agent module; and a session control module And the timeout control unit transmits the processing request to a responding unit when receiving a processing request sent by the requesting unit, so that the responding unit processes the processing request, and the meeting control module uses Determining whether the responding unit returns a processing result when a preset time arrives, and when the processing result is not returned to the requesting unit, the negotiation control module controls the blocking device to send a blocking Requesting to the responder unit, causing the responder unit to interrupt the processing of the processing request according to the blocking request, and the message proxy module transmits a session timeout message to the requesting unit, wherein the blocking unit The device is further configured to determine whether the responding unit successfully interrupts the processing of the processing request, and if not, the message proxy module transmits a reservation status message to the requesting unit. When the Responder and return the result of the processing unit, the module sends a message back to the proxy call (callback) message to the requestor cell. The timeout control unit of claim 1, wherein the blocker determines whether the responder unit successfully interrupts the processing of the processing request according to a blocking status message returned by the responding unit. The timeout control unit of claim 1 further includes a timer, and the talk control module is further configured to start the timer when the timeout control unit receives the processing request, and When the timer reaches the preset time, it is determined whether the responding unit returns the processing result. The timeout control unit of claim 1, wherein the negotiation control module is further configured to store a processing program identifier returned by the responding unit to one of the timeout control units corresponding to the processing request. The timeout control unit of claim 4, wherein the blocking request includes the handler identification code, and the responder unit interrupts the processing of the processing request according to the handler identifier in the blocking request. The timeout control unit of claim 1, further comprising: a request message queue for receiving and temporarily storing the processing request, and the meeting control module is further configured to control the request message. The column transmits the processing request to the responder unit. The timeout control unit of claim 1 further includes: a response message queue for receiving and temporarily storing the processing result. The timeout control unit of claim 1, wherein the timeout control unit is an intermediate device independent of the requestor unit and the responder unit Set. The timeout control unit of claim 1, wherein the timeout control unit is integrated into the requestor unit or the responder unit in a software manner. The timeout control unit of claim 1, wherein the timeout control unit is a hardware component of a system chip or other executable instruction included in the requestor unit or the responder unit. A remote program calling method includes: receiving, by a time-out control unit, a processing request sent by a requesting unit; transmitting, by the time-out control unit, the processing request to a responding unit, so that the responding unit processes The processing request; when a preset time arrives, determining whether the responding unit returns a processing result to the timeout control unit; if yes, using the timeout control unit to transmit the processing result back to the requesting unit If not, the timeout control unit is used to send a blocking request to the responding unit, so that the responding unit interrupts the processing of the processing request according to the blocking request, and uses the timeout control unit to transmit a meeting. Time message to the requester unit; and using the timeout control unit to determine whether the responder unit is successfully interrupted Processing of the processing request, if not, transmitting a reservation status message to the requesting unit by using the timeout control unit, and utilizing the timeout when the responding unit returns the processing result to the timeout control unit The control unit transmits a callback message to the requestor unit. The remote program calling method of claim 11, wherein in the step of determining whether the responder unit successfully interrupts the processing request by using the timeout control unit, the timeout control unit is based on the responding unit Returning to one of the timeout control units to block the status message, determining whether the responder unit successfully interrupts the processing of the processing request. The remote program calling method of claim 11, further comprising: receiving and storing a handler identifier returned by the responding unit to one of the timeout control units corresponding to the processing request. The remote program calling method of claim 13, wherein the blocking request includes the handler identification code, and the responder unit interrupts the processing of the processing request according to the handler identifier in the blocking request.