Device and method for controlling remote procedure call
US-2015331729-A1 · Nov 19, 2015 · US
US9894183B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9894183-B2 |
| Application number | US-201715412300-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 23, 2017 |
| Priority date | May 13, 2014 |
| Publication date | Feb 13, 2018 |
| Grant date | Feb 13, 2018 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Controlling a remote procedure call from a client computer to a server computer, the client computer extracts a periodic remote procedure call from among a plurality of remote procedure calls from the client computer and extracts a non-periodic remote procedure call from among the plurality of remote procedure calls from the client computer. The client computer identifies a first information associated with the extracted periodic remote procedure call that is an item whose value is determined to represent data targeted by the periodic remote procedure call. The client computer identifies a second information associated with the extracted non-periodic remote procedure call that is a targeted data value of the item, and sets a priority level, used to select for execution the periodic procedure call, based on the first information and the second information.
Opening claim text (preview).
What is claimed is: 1. A computer-implemented method for controlling a remote procedure call from a client to a server, comprising: executing, by a client computer, a plurality of remote procedure call from the client to the server; extracting, by the client computer, a first remote procedure call from among the plurality of remote procedure calls the first remote procedure call being a periodic remote procedure call; extracting, by the client computer, a second remote procedure call from among the plurality of remote procedure calls, the second remote procedure call being a non-periodic remote procedure call; and determining, regarding a third remote procedure call from the client to the server, either of a mode of the third remote procedure call and a mode of a process based on the third remote procedure call, by using first information obtained through the first remote procedure call and second information obtained through the second remote procedure call, wherein the second information is information representing specific data targeted by the non-periodic remote procedure call, such that the third remote procedure call is distinguished from other remote procedure calls as targeting the specific data.
Related publications grouped by family.
Answers are generated from the same data shown on this page.