US 10,567,551 B1Granted

System and method for improving infrastructure to infrastructure communications

AssigneeGoogle Inc.

InventorsGautam Suresh Nirodi, Michael Collins, Stephen Anthony Meyers

Life of this patent

Estimating the term…

Loading patent…

Abstract

Systems and methods are provided for improving communications between infrastructures using RPCs. An authoritative endpoint in a first infrastructure receives a registration request from a non-authoritative server in a second infrastructure through a transport layer on which a remote procedure call (RPC) layer depends. This request establishes a connection with the authoritative endpoint. The authoritative entity authenticates and registers the non-authoritative entity, and receives RPCs from client devices through the non-authoritative entity. The authoritative entity provides responses to the RPCs through the non-authoritative entity over the established connection. The authoritative entity also performed load-shedding operations, such as notifying the non-authoritative entity of a time to live of the connection. The RPC requests and responses sent over the connection may be chunked into frames, each frame identifying a stream to which it belongs.

Claims20

Dependent claims

A method of sending remote procedure call (RPC) requests, comprising:

sending, by one or more non-authoritative clients to an authoritative proxy, a registration request;
establishing, by the one or more non-authoritative clients, a multiplexed RPC connection with the authoritative proxy based on the registration request;
chunking, by the one or more non-authoritative client, a payload of each of a plurality of RPC requests into a plurality of frames of different sizes;
assigning, by the one or more non-authoritative client, an identifier to each frame, the identifier indicating a given stream of a plurality of streams to which the frame belongs, the given stream being specific to a given RPC request of the plurality of RPC requests;
including the assigned identifier in a frame header of each frame;
sending, by the one or more non-authoritative client through the multiplexed RPC connection with the authoritative proxy, the frames in each of the plurality of streams over the multiplexed RPC connection to a corresponding receive buffer at one or more authoritative servers, such that smaller frames in the plurality of streams are not delayed by larger preceding frames of the plurality of streams;
receiving, by the one or more non-authoritative client through the multiplexed RPC connection with the authoritative proxy, a control frame from the one or more authoritative servers instructing the one or more non-authoritative client to suspend transmission of the frames in the given stream when the corresponding receive buffer for the given stream is reaching a storage capacity;
suspending, by the one or more non-authoritative client, transmission of the frames in the given stream;
continuing, by the one or more non-authoritative client, transmission of the frames in other streams of the plurality of streams;
receiving, by the one or more non-authoritative clients, through the multiplexed RPC connection with the authoritative proxy, a plurality of response frames from the one or more authoritative servers;
and
assembling, by the one or more non-authoritative clients, the received plurality of response frames into at least one response to at least one of the plurality of RPC requests.

9 more elements

A system for sending remote procedure call (RPC) requests, comprising:

one or more non-authoritative clients comprising a memory and
one or more processors in communication with the memory, the one or more processors configured to:
send a registration request to an authoritative proxy;
establish a multiplexed RPC connection with the authoritative proxy based on the registration request;
chunk a payload of each of a plurality of RPC requests into a plurality of frames;
assign an identifier to each frame, the identifier indicating a given stream of a plurality of streams to which the frame belongs, the given stream being specific to a given RPC request of the plurality of RPC requests;
include the assigned identifier in a frame header of each frame;
send, through the multiplexed RPC connection with the authoritative proxy, the frames in each of the plurality of streams to a corresponding receive buffer of one or more authoritative servers, such that smaller frames in the plurality of streams are not delayed by larger preceding frames of the plurality of streams;
receive, through the multiplexed RPC connection with the authoritative proxy, a control frame from the one or more authoritative servers instructing the one or more processors to suspend transmission of the frames in the given stream when the corresponding receive buffer for the given stream is reaching a storage capacity;
suspend transmission of the frames in the given stream;
continue transmission of the frames in other streams of the plurality of streams;
receive, through the multiplexed RPC connection with the authoritative proxy, a plurality of response frames from the one or more authoritative servers;
and
assemble the received plurality of response frames into at least one response to at least one of the plurality of RPC requests.

11 more elements

A non-transitory computer-readable medium storing instructions executable by one or more processors for performing a method of sending remote procedure call (RPC) requests from one or more non-authoritative clients, the method comprising:

sending a registration request to an authoritative proxy;
establishing a multiplexed RPC connection with the authoritative proxy based on the registration request;
chunking a payload of each of a plurality of RPC requests into a plurality of frames;
assigning an identifier to each frame, the identifier indicating a given stream of a plurality of streams to which the frame belongs, the given stream being specific to a given RPC request of the plurality of RPC requests;
including the assigned identifier in a frame header of each frame;
sending, through the multiplexed RPC connection with the authoritative proxy, the frames in each of the plurality of streams to a corresponding receive buffer of one or more authoritative servers, such that smaller frames in the plurality of streams are not delayed by larger preceding frames of the plurality of streams;
receiving, through the multiplexed RPC connection with the authoritative proxy, a control frame from the one more authoritative servers with instructions to suspend transmission of the frames in the given stream when the corresponding receive buffer for the given stream is reaching a storage capacity;
suspending transmission of the frames in the given stream;
continuing transmission of the frames in other streams of the plurality of streams;
receiving, through the multiplexed RPC connection with the authoritative proxy, a plurality of response frames from the one or more authoritative servers;
and
assembling the received plurality of response frames into at least one response to at least one of the plurality of RPC requests.

9 more elements

Dependencies are inferred from the claim text.