CN113138869A - Remote calling method and device - Google Patents
Remote calling method and device Download PDFInfo
- Publication number
- CN113138869A CN113138869A CN202110507722.6A CN202110507722A CN113138869A CN 113138869 A CN113138869 A CN 113138869A CN 202110507722 A CN202110507722 A CN 202110507722A CN 113138869 A CN113138869 A CN 113138869A
- Authority
- CN
- China
- Prior art keywords
- remote
- parameter
- invocation
- calling
- target process
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
- G06F9/548—Object oriented; Remote method invocation [RMI]
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/544—Remote
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer And Data Communications (AREA)
Abstract
The application provides a remote calling method and a remote calling device, wherein the method comprises the following steps: judging whether the remote calling parameters hit a preset calling parameter management and control list or not; when the remote calling parameter hits the control list, determining whether the remote calling parameter meets the calling condition of the target process based on a control strategy preconfigured in the control list; and when the remote calling parameter meets the calling condition of the target process, transmitting the remote calling parameter to the target process, and initiating remote calling aiming at the target process. According to the method and the device, intelligent management and control can be performed on the remote calling parameters in the management and control list based on the preconfigured management and control strategy without manual intervention.
Description
Technical Field
The present application relates to the field of communications, and in particular, to a remote invocation method and apparatus.
Background
When a called process has a service exception while performing a remote call, if the call continues to be performed, unnecessary consumption of system resources of a call initiator may be caused. For this case, manual intervention is usually required to close all calling services of the called process. However, with manual intervention, the operation is complicated and the processing cycle is long.
Disclosure of Invention
The application provides a remote calling method, which comprises the following steps:
judging whether the remote calling parameters hit a preset calling parameter management and control list or not;
when the remote calling parameter hits the control list, determining whether the remote calling parameter meets the calling condition of the target process based on a control strategy preconfigured in the control list;
and when the remote calling parameter meets the calling condition of the target process, transmitting the remote calling parameter to the target process, and initiating remote calling aiming at the target process.
Optionally, before determining whether the remote invocation parameter hits the preset invocation parameter management and control list, the method further includes:
counting the number of times of wrong calling of each remote calling parameter of the target process in a preset time period;
judging whether the counted wrong calling times of each remote calling parameter reach a preset threshold value or not;
and storing the remote calling parameters of which the wrong calling times reach the preset threshold value in the remote calling parameters to the calling parameter control list.
Optionally, the method further includes:
and regularly emptying the calling parameter management and control list based on the preset time period.
Optionally, the determining, based on the control policy preconfigured in the control list, whether the remote invocation parameter meets the invocation condition of the target process includes:
calculating a decision score for the remote invocation parameter;
judging whether the calculated judgment score is larger than a control threshold value preconfigured in the control list or not;
when the judgment score is larger than the control threshold value, determining that the remote calling parameter meets the calling condition of the target process;
when the judgment score is smaller than or equal to the control threshold value, determining that the remote calling parameter does not meet the calling condition of the target process.
Optionally, the calculating a decision score for the remote invocation parameter includes:
randomly distributing decision scores for the remote calling parameters based on a preset random algorithm; or
Calculating the remote calling success rate of the remote calling parameter, and setting the calculated remote calling success rate as the judgment score of the remote calling parameter; or
Calculating the remote calling success rate of the remote calling parameters, and distributing corresponding judgment scores to the calculated remote calling success rate; wherein the assigned decision score is inversely proportional to the remote invocation success rate.
Optionally, the method further includes:
when the remote calling parameter does not hit the control list, transmitting the remote calling parameter to the target process, and initiating remote calling aiming at the target process;
and when the remote calling parameter does not meet the calling condition of the target process, terminating the remote calling for the target process.
The present application further provides a remote calling device, comprising:
the first judgment module is used for judging whether the remote calling parameters hit a preset calling parameter management and control list or not;
the determining module is used for determining whether the remote calling parameter meets the calling condition of the target process based on a control strategy preconfigured in the control list when the remote calling parameter hits the control list;
a calling module, configured to transfer the remote calling parameter to the target process when the remote calling parameter meets the calling condition of the target process, and initiate a remote call for the target process
Optionally, the apparatus further comprises:
the counting module is used for counting the error calling times of each remote calling parameter of the target process in a preset time period;
the second judgment module is used for judging whether the counted wrong calling times of each remote calling parameter reach a preset threshold value or not;
and the storage module is used for storing the remote calling parameters of which the error calling times reach the preset threshold value in the remote calling parameters to the calling parameter management and control list.
Optionally, the apparatus further comprises:
and the clearing module is used for regularly clearing the calling parameter management and control list based on the preset time period.
Optionally, the determining module is specifically configured to:
calculating a decision score for the remote invocation parameter;
judging whether the calculated judgment score is larger than a control threshold value preconfigured in the control list or not;
when the judgment score is larger than the control threshold value, determining that the remote calling parameter meets the calling condition of the target process;
when the judgment score is smaller than or equal to the control threshold value, determining that the remote calling parameter does not meet the calling condition of the target process.
Optionally, the determining module is further configured to:
randomly distributing decision scores for the remote calling parameters based on a preset random algorithm; or
Calculating the remote calling success rate of the remote calling parameter, and setting the calculated remote calling success rate as the judgment score of the remote calling parameter; or
Calculating the remote calling success rate of the remote calling parameters, and distributing corresponding judgment scores to the calculated remote calling success rate; wherein the assigned decision score is inversely proportional to the remote invocation success rate.
Optionally, the invoking module is further configured to:
when the remote calling parameter does not hit the control list, transmitting the remote calling parameter to the target process, and initiating remote calling aiming at the target process;
and when the remote calling parameter does not meet the calling condition of the target process, terminating the remote calling for the target process.
In the method, when remote calling aiming at a target process is initiated based on a remote calling parameter, whether the remote calling parameter hits a calling parameter management and control list is judged; when the remote calling parameter hits the control list, determining whether the remote calling parameter meets the calling condition of the target process based on a control strategy preconfigured in the control list; if the remote calling parameter meets the calling condition of the target process, the remote calling parameter is transmitted to the target process to initiate remote calling aiming at the target process, so that the system can intelligently control the remote calling parameter in a control list based on a preconfigured control strategy without manual intervention.
Drawings
Fig. 1 is a schematic diagram illustrating remote invocation performed in the related art according to an embodiment of the present application;
FIG. 2 is a flow chart of a remote invocation method according to an embodiment of the present application;
fig. 3 is a flowchart illustrating a process of creating a call parameter management list for a target process according to an embodiment of the present application;
fig. 4 is a flowchart illustrating a process of intelligently managing and controlling a remote invocation parameter based on a preconfigured management and control policy according to an embodiment of the present application;
FIG. 5 is a logic block diagram of a remote invocation device according to an embodiment of the present application;
fig. 6 is a hardware structure diagram of a remote invocation terminal carrying the remote invocation device according to an embodiment of the present application.
Detailed Description
Referring to fig. 1, fig. 1 is a schematic diagram illustrating a remote call execution in the related art according to the embodiment.
As shown in FIG. 1, system A is the initiator of the remote invocation, and system B is the callee of the remote invocation. The system B can provide a service process for the system A to be remotely called.
When the service process provided by the system a is called remotely, the system a may transmit a remote call parameter (usually, the remote call parameter is carried in the remote call request) by sending the remote call request to a call interface corresponding to the service process in the system B.
When the service process receives a call request sent by the system A through a call interface, the call request can be analyzed, remote call parameters carried in the call request are obtained, then the service process is executed to aim at the remote call parameters in the system B, and a corresponding call result is returned to the system A after the processing is finished. If the remote call is abnormal, the system A cannot receive the call result returned by the system B, and a call error occurs to the system A.
When the system a has a call error, if the call continues to be executed, the call initiator may consume system resources unnecessarily, and may even consume system resources when the remote call parameter is called in a very large amount.
For this case, manual intervention is usually required to close all calling services of the served process to manage the remote call initiated by the system a. When all the calling services of the service process are closed, all the calling services initiated by the system a are interrupted.
However, in practical applications, the failure of the remote invocation parameter is probably caused by the failure of the invocation parameter transmission due to the unstable service of the system a and the packet loss of part of the invocation request, and other invocation parameters except the remote invocation parameter may still be able to invoke the service process normally at present.
Therefore, in this case, if all the calling services of the service process are shut down through manual intervention, all the calling parameters cannot obtain correct calling results, so that the calling parameters that can still normally call the service process cannot be called.
Therefore, the remote invocation is controlled through manual intervention, so that the operation is complex, the processing period is long, and partial invocation parameters (such as invocation parameters failing in remote invocation) of the service process cannot be controlled.
In view of the above, the present application provides a remote invocation method, which determines whether a remote invocation parameter hits an invocation parameter management and control list when initiating a remote invocation for a target process based on the remote invocation parameter; when the remote calling parameter hits the control list, determining whether the remote calling parameter meets the calling condition of the target process based on a control strategy preconfigured in the control list; if the remote calling parameter meets the calling condition of the target process, the remote calling parameter is transmitted to the target process, remote calling aiming at the target process is initiated, and the system can intelligently control the remote calling parameter in the control list based on the preconfigured control strategy without manual intervention.
Moreover, for the remote call parameter which does not hit the management and control list, normal remote call can be continuously executed on the target process, so that only the remote call parameter in the management and control list can be managed and controlled, and management and control on part of the call parameter of the target process are realized.
The present application is described below with reference to specific embodiments and specific application scenarios.
Referring to fig. 2, fig. 2 is a remote invocation method applied to a remote invocation terminal according to an embodiment of the present application, where the method performs the following steps:
The remote call terminal may include a terminal for initiating a remote call to a target process provided by the server; for example, the remote invocation terminal may include a mobile terminal, a PC terminal, etc. of the user.
The server may include a server that provides a target process for the remote call terminal, a server cluster, or a cloud platform constructed based on the server cluster.
The target process is a service process which is provided by the server and can be used for remote calling.
The target process may be provided with a calling interface (e.g., an API interface) by the server, the calling interface may be predefined by the server as to a plurality of types of remote calling parameters, and the remote calling terminal may send a calling request to the calling interface of the target process and transfer the remote calling parameters to the target process to remotely call the target process.
In this example, the remote invoking terminal may create a corresponding invoking parameter control list for the target process in advance locally, where the control list is used to store a part of the remote invoking parameters of the target process that needs to be controlled.
When the user initiates remote calling aiming at the target process through the remote calling terminal, the remote calling terminal can control the remote calling parameters hitting the control list based on the preconfigured control strategy.
Certainly, in practical applications, the server may provide a plurality of different service processes for the remote invocation terminal, and in this case, the server may preset a corresponding invocation parameter management and control list for each service process.
The remote call parameters stored in the control list may include a remote call parameter that is incorrectly called when a remote call is initiated to the target process.
For example, in an illustrated embodiment, the server may store, in the management and control list, a remote invocation parameter, of which the number of times of incorrect invocation reaches a preset threshold in a preset time period, among remote invocation parameters of the target process.
In this way, when a user initiates a remote call to a target process, the remote call terminal may only manage some call parameters that have been incorrectly called in the control list when the user initiates the remote call to the target process, and may continue to execute normal remote calls for the remote call parameters that have not hit the control list.
Referring to fig. 3, fig. 3 is a processing flow for creating a call parameter management list for a target process according to this embodiment, which includes the following steps:
in this example, the remote invocation terminal counts each remote invocation parameter of the target process, and when the number of wrong invocation times within a preset time period is counted, a counter may be preset locally, and after a user initiates a remote invocation for the target process through the remote invocation parameter, if the remote invocation terminal fails to receive an invocation result for the invocation returned by the server, the remote invocation is in error, and the remote invocation terminal may add one to the number of wrong invocation times of the remote invocation parameter through the counter.
When the remote call initiated by the remote call parameter to the target process occurs an error again within the preset time period, the remote call terminal may add one more error call times to the remote call parameter by the counter in the same manner, and so on until finally counting the error call times of the remote call parameter in the preset time period.
The preset time period may be a periodic time range set by a user; for example, assuming that the time range is 30 minutes, the server may use 30 minutes as a statistical period, and periodically perform statistics on the number of times of incorrect calls of each remote call parameter of the target process in the time range.
In this embodiment, when the remote invocation terminal counts the number of times of incorrect invocation of each remote invocation parameter within a preset time period, the counted number of times of incorrect invocation of each remote invocation parameter may be respectively compared with a preset threshold value to determine whether the counted number of times of incorrect invocation reaches the preset threshold value. The preset threshold value can be set by a user based on actual requirements.
For the remote call parameter whose counted number of times of wrong call reaches the preset threshold, the remote call terminal may use the remote call parameter as the remote call parameter to be managed and controlled, and store the remote call parameter into the management and control list. Of course, for the remote invocation parameter with the counted number of incorrect invocation less than or equal to the preset threshold, no special processing may be performed at this time.
And step 304, regularly clearing the calling parameter management and control list based on the preset time period.
In this example, since the factor causing the incorrect invocation is not generally constant, when the number of times of the invocation error of a certain remote invocation parameter reaches a preset threshold value and is saved in the control list, if the factor causing the incorrect invocation changes, the remote invocation parameter resumes to be normal with respect to the remote invocation of the target process, in this case, the remote invocation parameter is still saved in the control list, and the execution of the incorrect control on the remote invocation parameter capable of normally invoking the target process is caused.
For example, if a call error occurs in a certain remote call parameter, which is caused by a packet loss occurring in a call request due to unstable service of the current system, when the number of times of the call error of the remote call parameter reaches a preset threshold and is stored in the management list, if the server of the current system recovers to be stable after a period of time, the remote call parameter may have been able to normally call the target process, and therefore, in this case, the remote call parameter is still stored in the management list as the managed remote call parameter, and the remote call parameter may be erroneously managed.
In this example, in order to avoid the occurrence of the situation of causing the wrong management and control, the created management and control list may be cleared by the remote invoking terminal at regular time based on the preset time period. After the emptying is completed, in the next preset period, the remote calling terminal can count the calling times of each remote calling parameter in the period again, and the counted remote calling parameters with the wrong calling times reaching the preset threshold value are stored in the control list to create the control list again.
Therefore, in an application scene that a system service is unstable and a part of call request packet is lost to cause a call error, the remote call terminal introduces a mechanism for updating the control list at regular time, so that the remote call parameters in the control list can be dynamically maintained, and the remote call parameters with the wrong call times reaching a preset threshold value in a preset time period can be placed into the control list for intelligent control. When the system service is recovered stably and the number of times of wrong calling of the remote calling parameter in a preset time period is reduced to be below a preset threshold value, the remote calling parameter is not put into a control list as a calling parameter needing to be controlled any more, but normal remote calling can be executed aiming at the target process, and therefore the problem that the wrong calling of the remote calling parameter of the target process can be controlled normally due to the fact that factors causing wrong calling are changed can be solved.
In this example, after the remote invocation terminal creates the corresponding invocation parameter management and control list for the target process, when the user initiates the remote invocation for the target process again, the remote invocation terminal may parse the invocation request of the remote invocation at this time, obtain the remote invocation parameter used by the remote invocation at this time, and then match the remote invocation parameter with the remote invocation parameter stored in the management and control list respectively to determine whether the remote invocation parameter used by the remote invocation at this time hits the management and control list.
On one hand, when the remote calling parameter used in the remote calling is not matched with the remote calling parameter in the control list, the remote calling parameter is not hit in the control list, and at the moment, the remote calling terminal can transmit the remote calling parameter to the target process to execute normal remote calling aiming at the target process.
On the other hand, when the remote invocation parameter used in the present remote invocation matches any remote invocation parameter in the control list, at this time, the remote invocation parameter hits the control list, and the remote invocation terminal may perform intelligent control on the remote invocation parameter based on a control policy preconfigured by the user for the control list, so as to determine whether the remote invocation parameter meets the invocation condition of the target process.
The management and control strategy can be preconfigured by a user according to actual requirements.
In an embodiment, the execution logic of the governing policy may include:
and calculating a judgment score for the remote calling parameter, and determining whether the remote calling parameter meets the calling condition of the target process by judging whether the calculated judgment score is larger than a control threshold value pre-configured in a control list.
Referring to fig. 4, fig. 4 is a processing flow for performing intelligent management and control on a remote invocation parameter based on a preconfigured management and control policy, shown in this embodiment, and includes the following steps:
in this example, the remote invocation terminal calculates the decision score for the remote invocation parameter, and the calculation may be implemented by:
in one approach, the remote call terminal may randomly assign a decision score to the remote call terminal through a predetermined random algorithm. In this way, there is greater flexibility in assigning different decision scores at random even if multiple calls are made to the target process through the same remote call parameter.
In another manner, the remote invocation terminal may calculate a remote invocation success rate of the remote invocation parameter, and then set the calculated remote invocation success rate as a decision score of the remote invocation parameter. When the remote call success rate is obtained, the number of times of successful call of the remote call parameter can be calculated to be the total number of times of remote call.
Or, after the remote invocation terminal calculates the remote invocation success rate of the remote invocation parameter, it may allocate a corresponding decision score to the calculated remote invocation success rate, where the decision score allocated to the calculated remote invocation success rate may be inversely proportional to the remote invocation success rate, that is, the higher the remote invocation success rate is, the lower the allocated decision score is, whereas, the lower the remote invocation success rate is, the higher the allocated decision score is, thereby preferentially allocating a lower decision score to the remote invocation parameter with the higher remote invocation success rate.
By the method, the judgment score can be set strictly according to the calling success rate of the remote calling parameter, so that the calling success rate of the remote calling parameter can be used as a reference when whether the remote calling parameter meets the calling condition of the target process or not is determined aiming at the judgment score subsequently, and the remote calling parameter with higher calling success rate can meet the calling condition of the target process more easily.
In this example, the user may also pre-configure a corresponding regulatory threshold for the regulatory list. The control threshold value can be set and modified by a user according to actual requirements. After the remote call terminal calculates the decision score of the remote call parameter, the decision score may be compared with the control threshold to determine whether the decision score is greater than the control threshold.
When the decision score is greater than the control threshold, the remote invocation terminal may determine that the remote invocation parameter satisfies the invocation condition of the target process. On the contrary, when the decision score is less than or equal to the control threshold, the remote invocation terminal may determine that the remote invocation parameter does not satisfy the invocation condition of the target process.
It should be noted that the control threshold may be used to characterize a control proportion for the remote invocation parameter in the control list.
For example, in implementation, the decision score and the control threshold may be specific values within a range of 0 to 100, a user may modify the control threshold according to actual requirements, when the user wishes to prohibit remote invocation of all remote invocation parameters in the control list for a target process, the control threshold may be set to 100, the control threshold is the maximum at this time, the calculated decision scores of all remote invocation parameters are all smaller than the control threshold, and in this case, it may be default that all remote invocation parameters in the control list do not satisfy the invocation condition of the target process. On the contrary, when the user wishes to release the remote invocation of all the remote invocation parameters in the control list for the target process, the control threshold may be set to 0, at this time, the control threshold is the minimum, the calculated decision scores of all the remote invocation parameters are all greater than the control threshold, and in this case, all the remote invocation parameters in the control list may be defaulted to meet the invocation condition of the target process.
In this example, when the remote invocation terminal performs intelligent control on the remote invocation parameter based on a control policy preconfigured for the control list by the user, and then determines that the remote invocation parameter meets the invocation condition of the target process, the remote invocation parameter may be transferred to the target process, and remote invocation on the target process is initiated. And when the remote calling terminal receives a calling result returned by the server, the calling execution is finished. When the remote calling terminal does not receive the calling result returned by the server side, the calling is wrong at the moment, the remote calling terminal can update the wrong calling times of the remote calling parameters, and when the wrong calling times of the remote calling parameters reach a preset threshold value, the remote calling is stored in a control list, and detailed processes are not repeated.
Of course, if it is determined that the remote invocation parameter does not satisfy the invocation condition of the target process, the remote invocation terminal may directly terminate this remote invocation for the target process. In this case, the remote invocation terminal may simulate the result of a remote invocation failure and output the result to the user (e.g., output a prompt message to the user via the user interface) to prompt the invocation failure.
In the above embodiment, when a remote call for a target process is initiated based on a remote call parameter, whether the remote call parameter hits a call parameter management and control list is determined; when the remote calling parameter hits the control list, determining whether the remote calling parameter meets the calling condition of the target process based on a control strategy preconfigured in the control list; if the remote calling parameter meets the calling condition of the target process, the remote calling parameter is transmitted to the target process, remote calling aiming at the target process is initiated, and the system can intelligently control the remote calling parameter in the control list based on the preconfigured control strategy without manual intervention.
Moreover, for the remote call parameter which does not hit the management and control list, normal remote call can be continuously executed on the target process, so that only the remote call parameter in the management and control list can be managed and controlled, and management and control on part of the call parameter of the target process are realized.
Corresponding to the method embodiment, the application also provides an embodiment of the device.
Referring to fig. 5, the present application provides a remote invoking device 50, which is applied to a remote invoking terminal; referring to fig. 6, a hardware architecture related to a remote invocation terminal carrying the remote invocation device 50 generally includes a CPU, a memory, a non-volatile memory, a network interface, an internal bus, and the like; in the case of a software implementation, the remote invocation device 50 may be generally understood as a computer program loaded in a memory, and a logic device formed by combining software and hardware after being executed by a CPU, where the device 50 includes:
a first judging module 501, configured to judge whether a remote call parameter hits a preset call parameter management and control list;
a determining module 502, configured to determine, when the remote invocation parameter hits the control list, whether the remote invocation parameter satisfies an invocation condition of the target process based on a control policy preconfigured in the control list;
a calling module 503, configured to transfer the remote calling parameter to the target process when the remote calling parameter meets the calling condition of the target process, and initiate a remote call for the target process
In this case, the apparatus 50 may further include:
a counting module 504, configured to count the number of times of incorrect invocation of each remote invocation parameter of the target process within a preset time period;
a second determining module 505, configured to determine whether the counted number of times of incorrect invocation of each remote invocation parameter reaches a preset threshold;
a saving module 506, configured to save the remote invocation parameter with the number of incorrect invocations reaching the preset threshold in the remote invocation parameters to the invocation parameter management and control list.
In this case, the apparatus 50 may further include:
and an emptying module 507, configured to regularly empty the call parameter management and control list based on the preset time period.
In this example, the determining module 502 is specifically configured to:
calculating a decision score for the remote invocation parameter;
judging whether the calculated judgment score is larger than a control threshold value preconfigured in the control list or not;
when the judgment score is larger than the control threshold value, determining that the remote calling parameter meets the calling condition of the target process;
when the judgment score is smaller than or equal to the control threshold value, determining that the remote calling parameter does not meet the calling condition of the target process.
In this example, the determining module 502 is further configured to:
randomly distributing decision scores for the remote calling parameters based on a preset random algorithm; or
Calculating the remote calling success rate of the remote calling parameter, and setting the calculated remote calling success rate as the judgment score of the remote calling parameter; or
Calculating the remote calling success rate of the remote calling parameters, and distributing corresponding judgment scores to the calculated remote calling success rate; wherein the assigned decision score is inversely proportional to the remote invocation success rate.
In this example, the calling module 503 is further configured to:
when the remote calling parameter does not hit the control list, transmitting the remote calling parameter to the target process, and initiating remote calling aiming at the target process;
and when the remote calling parameter does not meet the calling condition of the target process, terminating the remote calling for the target process.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.
Claims (12)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110507722.6A CN113138869A (en) | 2016-01-15 | 2016-01-15 | Remote calling method and device |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610029333.6A CN106980545B (en) | 2016-01-15 | 2016-01-15 | Remote calling method and device |
| CN202110507722.6A CN113138869A (en) | 2016-01-15 | 2016-01-15 | Remote calling method and device |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610029333.6A Division CN106980545B (en) | 2016-01-15 | 2016-01-15 | Remote calling method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113138869A true CN113138869A (en) | 2021-07-20 |
Family
ID=59341117
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610029333.6A Active CN106980545B (en) | 2016-01-15 | 2016-01-15 | Remote calling method and device |
| CN202110507722.6A Pending CN113138869A (en) | 2016-01-15 | 2016-01-15 | Remote calling method and device |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610029333.6A Active CN106980545B (en) | 2016-01-15 | 2016-01-15 | Remote calling method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN106980545B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110032454B (en) * | 2018-01-12 | 2024-08-20 | 北京京东尚科信息技术有限公司 | Remote calling method, system, related equipment and computer readable storage medium |
| CN110808948B (en) * | 2019-09-23 | 2022-03-11 | 中移（杭州）信息技术有限公司 | Remote procedure call method, device and system |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR101086203B1 (en) * | 2011-07-15 | 2011-11-23 | 에스지에이 주식회사 | Malicious process pre-blocking system and method for judging the behavior of malicious processes in advance |
| US20120254901A1 (en) * | 2011-03-29 | 2012-10-04 | Denso Corporation | Method and system for restoring an application in a dynamically linked environment |
| US20140013429A1 (en) * | 2011-11-29 | 2014-01-09 | Tencent Technology (Shenzhen) Company Limited | Method for processing an operating application program and device for the same |
| US20140270125A1 (en) * | 2013-03-15 | 2014-09-18 | Comcast Cable Communications, Llc | Admission Control Of A Communication System |
| CN104219316A (en) * | 2014-09-12 | 2014-12-17 | 微梦创科网络科技（中国）有限公司 | Method and device for processing call request in distributed system |
| US20150288715A1 (en) * | 2014-04-03 | 2015-10-08 | Automattic, Inc. | Systems And Methods For Protecting Websites From Botnet Attacks |
| CN105138388A (en) * | 2014-06-09 | 2015-12-09 | 腾讯科技（深圳）有限公司 | Virtual machine monitoring method and apparatus |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2002056152A2 (en) * | 2001-01-10 | 2002-07-18 | Psionic Software Inc | Computer security and management system |
| US8719325B2 (en) * | 2003-02-28 | 2014-05-06 | Microsoft Corporation | Method to initiate server based collaboration on e-mail attachments |
| CN1937683A (en) * | 2006-06-06 | 2007-03-28 | 北京恒基伟业投资发展有限公司 | Mobile phone long-distance operating method and device |
| CN103795703A (en) * | 2011-04-18 | 2014-05-14 | 北京奇虎科技有限公司 | Method for ensuring user network security and client |
| CN102137111A (en) * | 2011-04-20 | 2011-07-27 | 北京蓝汛通信技术有限责任公司 | Method and device for preventing CC (Challenge Collapsar) attack and content delivery network server |
| CN102497453A (en) * | 2011-12-28 | 2012-06-13 | 用友软件股份有限公司 | Calling device and calling method for remote programs |
| CN103645940A (en) * | 2013-12-04 | 2014-03-19 | 清华大学 | Remote calling method and system |
-
2016
- 2016-01-15 CN CN201610029333.6A patent/CN106980545B/en active Active
- 2016-01-15 CN CN202110507722.6A patent/CN113138869A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120254901A1 (en) * | 2011-03-29 | 2012-10-04 | Denso Corporation | Method and system for restoring an application in a dynamically linked environment |
| KR101086203B1 (en) * | 2011-07-15 | 2011-11-23 | 에스지에이 주식회사 | Malicious process pre-blocking system and method for judging the behavior of malicious processes in advance |
| US20140013429A1 (en) * | 2011-11-29 | 2014-01-09 | Tencent Technology (Shenzhen) Company Limited | Method for processing an operating application program and device for the same |
| US20140270125A1 (en) * | 2013-03-15 | 2014-09-18 | Comcast Cable Communications, Llc | Admission Control Of A Communication System |
| US20150288715A1 (en) * | 2014-04-03 | 2015-10-08 | Automattic, Inc. | Systems And Methods For Protecting Websites From Botnet Attacks |
| CN105138388A (en) * | 2014-06-09 | 2015-12-09 | 腾讯科技（深圳）有限公司 | Virtual machine monitoring method and apparatus |
| CN104219316A (en) * | 2014-09-12 | 2014-12-17 | 微梦创科网络科技（中国）有限公司 | Method and device for processing call request in distributed system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106980545B (en) | 2021-03-23 |
| CN106980545A (en) | 2017-07-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10715448B2 (en) | System and/or method for predictive resource management in file transfer servers | |
| US10389801B2 (en) | Service request processing method, related apparatus, and system | |
| US9100854B2 (en) | Quality of service application controller and user equipment application profiler | |
| CN101023646B (en) | Resource management | |
| CN107613030A (en) | A method and system for processing service requests | |
| CN114867065B (en) | Base station calculation load balancing method, equipment and storage medium | |
| CN108183950B (en) | Method and device for establishing connection of network equipment | |
| JP6359114B2 (en) | Method, system, and apparatus for adaptive allocation determination for shared resources | |
| JP2006511137A5 (en) | ||
| CN109861920A (en) | A kind of method and device of elasticity current limliting | |
| EP3480983A1 (en) | Data transmission method and apparatus | |
| US8086731B2 (en) | Method, system and apparatus for collecting statistics of characteristic value with threshold | |
| CN111459676B (en) | Node resource management method, device and storage medium | |
| WO2015130199A1 (en) | Method, computer program and node for management of resources | |
| CN106980545B (en) | Remote calling method and device | |
| CN117527906A (en) | Data scheduling processing method and device and electronic equipment | |
| CN115002225B (en) | Request processing method, device and readable medium | |
| CN119697126B (en) | SIP signaling transmission and flow control method, device and computer equipment | |
| CN113328906B (en) | Flow real-time monitoring method and device, storage medium and electronic equipment | |
| CN111078386A (en) | A control method and control device of a distributed scheduling system | |
| CN112152971A (en) | Method and apparatus, electronic device and medium for controlling network usage behavior | |
| CN112260962B (en) | Bandwidth control method and device | |
| JP6856521B2 (en) | Communication devices, communication systems and programs | |
| CN114896037A (en) | Dynamic process control method and device, storage medium and electronic device | |
| CN106899510B (en) | A transmission rate control method and device based on iSCSI protocol |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210720 |