SYSTEM AND METHOD FOR IMPLEMENTING AUGMENTED OBJECT MEMBERS FOR REMOTE PROCEDURE CALL

• US 20150081774A1
• Filed: 09/12/2014
• Published: 03/19/2015
• Est. Priority Date: 09/13/2013
• Status: Abandoned Application

• Current Assignee: John Wason
• Original Assignee: John Wason
• Inventors: Wason, John
• Application Number:
  US14/485,222
• Publication Number:
  US 20150081774A1
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: H04L 67/133 Protocols for remote procedure calls [RPC]

Abstract

A communication method and system configured to facilitate integration of complex automation systems composed of disparate components that may run with different processes, are distributed over a network, or are embedded devices. The system/method allows for a client to rapidly access functionality exposed by a service within a client-service system employing a distributed application structure utilizing an augmented object-oriented model of multiple member types. The system/method allows interconnected nodes to communicate through message passing and remote procedure calling so as to reduce latency within a system composed of distributed resources.

Claims

1. A system for executing Remote Procedure Call comprising:

at least one client in operable communication with a server;

a message passing layer comprising endpoints, located at said at least one client and said server, connected by channels; and

an object-oriented Remote Procedure Call (RPC) layer.

2. The system of claim 1 wherein said RPC layer comprises a plurality of object members being executable by said at least one client and said server.

3. The system of claim 2 wherein one of said object members is a property member configured to get or set a variable value.

4. The system of claim 2 wherein one of said object members is a wire member configured to communicate a most recent value between said service and at least one client.

5. The system of claim 2 wherein one of said object members is a function member configured to allow a function of zero or more parameters to be called by said at least one client.

6. The system of claim 2 wherein one of said object members is an event member configured to allow said service to notify said at least one client.

7. The system of claim 2 wherein one of said object members is an object reference (objref) member configured to retrieve object references from said service.

8. The system of claim 2 wherein one of said object members is a pipe member configured to allow said at least one client to request a pipe endpoint be created with a matching endpoint in said service in order to send/receive packets between endpoints in order.

9. The system of claim 2 wherein one of said object members is a callback member configured to allow said service to execute a function on said at least one client.

10. The system of claim 2 wherein one of said object members is a memory member configured to allow said at least one client to read or write randomly accessible memory segments.

11. A method of client-server communication comprising:

creating an endpoint within a client node upon connection to a service;

creating an endpoint within a service for each client node connected to said service; and

generating interface code configured to pack and unpack parameters and object members into or out of packets sent between said client node endpoint and said service endpoint.

12. The method of claim 11 wherein said object members comprise at least one of a function member, an event member, an object reference member, a pipe member, a callback member, a wire member, and a memory member.

13. The method of claim 11 wherein said endpoints are created in response to executing a pipe member by transmitting a connect request from said client to said service allowing either endpoint to send or receive packets in order.

14. The method of claim 13 further comprising deleting said endpoints upon a close operation initiated by either said client or said service.

15. The method of claim 11 wherein said endpoints are created in response to executing a wire member by transmitting a connection request from said client to said service and generating a packet containing a value upon setting of an OutValue by either of said endpoints.

16. The method of claim 11 wherein executing said wire member further comprises:

sending said packet;

upon receipt of said packet containing said value, comparing a timestamp of said packet to a timestamp of a current value;

upon a determination that said timestamp of said packet is older than said timestamp of said current value, discarding said packet; and

upon a determination that said timestamp of said packet is newer than said timestamp of said current value, replacing said current value with said value contained in said packet.

17. The method of claim 11 further comprising executing a callback member wherein said service requests a function by transmitting a packet to said client and, upon receipt, said client executes said function and returns a resulting value to said service.

18. A method of client-server communication comprising:

in response to execution of an object member, creating an endpoint within a client node upon connection to a service;

in response to execution of an object member, creating an endpoint within a service for each client node connected to said service; and

generating interface code configured to pack and unpack parameters and object members into or out of packets sent between said client node endpoint and said service endpoint.

19. The method of claim 18 wherein said object members comprise at least one of a function member, an event member, an object reference member, a pipe member, a callback member, a wire member, and a memory member.

20. The method of claim 18 further comprising deleting said endpoints upon a close operation initiated by either said client or said service.