SYSTEMS AND METHODS FOR LOW OVERHEAD REMOTE PROCEDURE CALLS
A system and method for providing low overhead remote procedure calls are disclosed. A particular embodiment includes: generating, by use of a data processor, a data packet having a command type header portion and a payload portion; branding, by use of the data processor, the data packet with a command type header from the group: an event type, a remote procedure call (RPC) request type, an RPC response type, and an RPC signal type; packing data into the payload portion based on a data representation corresponding to the command type header, if the command type header is an event type; specifying an interface and a method to invoke on a remote system, if the command type header is an RPC request type; and causing the data packet to he transferred to a subsystem via an inter-process data communication.
1 . A method comprising;
generating, by use of a data processor, a data packet having a command type header portion and a payload portion;
branding, by use of the data processor, the data packet with a command type header from the group: an event type, a remote procedure call (RPC) request type, an RPC response type, and an RPC signal type;
packing data into the payload portion based on a data representation corresponding to the command type header, if the command type header is an event type;
specifying an interface and a method to invoke on a remote system, if the command type header is an RPC request type; and
causing the data packet to be transferred to a subsystem via an inter-process data communication.
2 . The method as claimed in claim 1 including defining a buffer for passing parameters for the method, if the command type header is an RPC request type.
3 . The method as claimed in claim 1 including defining a buffer for passing a result, if the command type header is an RPC response type.
4 . The method as claimed in claim 1 including defining a buffer for passing signaling data, if the command type header is an RPC signal type.
5 . The method as claimed in claim 1 wherein the subsystem is a part of a vehicle information and control system.
6 . The method as claimed in claim 1 wherein the data packed into the payload portion includes data corresponding to vehicle state change information.
7 . The method as claimed in claim 1 wherein the subsystem is in a different layer of a vehicle information and control system.
8 . The method as claimed in claim 1 wherein the subsystem is in a different layer of a vehicle information and control system, at least one layer of the vehicle information and control system substantially mirroring the functionality of the different layer.
9 . A system comprising;
one or more data processors; and
a vehicle information and control system, executable by the one or more data processors, to
generate a data packet ha v Mg a command type header portion and a payload portion;
brand the data packet with a command type header from the group an event type, a remote procedure call (RPC) request type, an RPC response type, and an RPC signal type;
pack data into the payload portion based on a data representation corresponding to the command type header, if the command type header is an event type;
specify an interface and a method to invoke on a remote system, if the command type header is an RPC request type; and
cause the data packet to be transferred to a subsystem via an inter-process data communication.
10 . The system as claimed in claim 9 being further configured to define a buffer for passing parameters for the method., if the command type header is an RPC request type.
11 . The system as claimed in claim 9 being further configured to define a buffer for passing a result, if the command type header is tan RPC response type.
12 . The system as claimed in claim 9 being further configured to define a buffer for passing signaling data, if the command type header is an RPC signal type.
13 . The system as claimed in claim 9 wherein the subsystem is a part of a vehicle information and control system.
14 . The system as claimed in claim 9 wherein the data packed into the payload portion includes data corresponding to vehicle state change information.
15 . A non-transitory machine-useable storage medium embodying instructions which, when executed by a machine, cause the machine to:
generate a data packet having a command type header portion and a payload portion;
brand the data packet with a command type header from the group: an event type, a remote procedure call (RPC) request type, an RPC response type, and an RPC signal type;
pack data into the payload portion had on a data representation corresponding to the command type header, if the command type header is an event type;
specify an interface and a method to invoke on as remote system, if the command type header is an RPC request type; and
cause the data packet to be transferred to a subsystem is an inter-process data communication.
16 . The machine-useable storage medium as claimed in claim 15 being further configured to define a buffer for passing parameters for the method, if the command type header is an RPC request type.
17 . The machine-useable storage medium as claimed in claim 15 being further configured to define a buffer for passing a result, if the command type header is an RPC response type.
18 . The machine-useable storage medium as claimed in claim 15 being further configured to define a buffer for passing signaling data, if the command type header is an RPC signal type.
19 . The machine-useable storage medium as claimed in claim 15 wherein the subsystem is a at of a vehicle information and control system.
20 . The machine-useable storage medium as claimed in claim 15 wherein the data packed into the payload portion includes data corresponding to vehicle state change information.