System and method for message management across a network
Systems, methods, and computer-readable media for managing service calls over a network may include a signal routing engine with a maintained forwarding table for various network functions and micro-services in a services back end for the network. The signal routing engine can include a call conversion service for converting REST API calls to an internal network call protocol for increasing network function processing speeds, decreasing bandwidth usage, and improving network responsiveness and manageability.
1. A method for managing service calls across a network, the method comprising:
prior to receiving a text-based protocol call from a requestor,
receiving a plurality of network function (NF) endpoint addresses;
caching a plurality of connections among a plurality of NF endpoints using the plurality of NF endpoint addresses; and
storing, in a forwarding table, the plurality of NF endpoint addresses;
receiving, from the requestor, the text-based protocol call directed to a first NF endpoint;
generating a binary protocol call based on the text-based protocol call;
transmitting, to a second NF endpoint, the binary protocol call over a first cached connection from the first NF endpoint to the second NF endpoint based on the forwarding table;
receiving, from the second NF endpoint, a binary protocol response over a second cached connection from the second NF endpoint to the first NF endpoint based on the forwarding table;
converting the binary protocol response to a text-based protocol response; and
transmitting, to the requestor, the text-based protocol response.
2. The method of claim 1 , further comprising:
receiving, from a second requestor, a second text-based protocol call directed to the first NF endpoint;
generating a second binary protocol call based on the second text-based protocol call;
transmitting, to the second NF endpoint, the second binary protocol call over the first cached connection;
receiving, from the second NF, a second binary protocol response over the second cached connection;
converting the second binary protocol response to a second text-based protocol response; and
transmitting, to the second requestor, the second binary protocol response.
3. The method of claim 2 , wherein the first NF endpoint is within a first service provider network and the second NF endpoint is within a second service provider network.
4. The method of claim 1 , wherein the binary protocol call is a gRPC Remote Procedure Call (gRPC) call.
5. The method of claim 1 , wherein the text-based protocol call is a Hypertext Transfer Protocol (HTTP) call to a representational state transfer (REST) application programming interface (API).
6. The method of claim 1 , wherein the plurality of NF endpoint addresses is received from a global router.
7. The method of claim 1 , wherein the first NF endpoint runs in a Cloud Native Environment (CNE).
8. A system for managing calls across a network, the system comprising:
one or more processors; and
memory storing instructions that, when executed by the one or more processors, cause the system to:
prior to receiving a text-based protocol call from a requestor,
receive a plurality of network function (NF) endpoint addresses;
cache a plurality of connections among a plurality of NF endpoints using the plurality of NF endpoint addresses; and
store, in a forwarding table, the plurality of NF endpoint addresses;
receive, from the requestor, the text-based protocol call directed to a first NF endpoint;
generate a binary protocol call based on the text-based protocol call;
transmit, to a second NF endpoint, the binary protocol call over a first cached connection from the first NF endpoint to the second NF endpoint based on the forwarding table;
receive, from the second NF endpoint, a binary protocol response over a second cached connection from the second NF endpoint to the first NF endpoint based on the forwarding table;
convert the binary protocol response to a text-based protocol response; and
transmit, to the requestor, the text-based protocol response.
9. The system of claim 8 , wherein the memory further stores instructions further causing the system to:
receive, from a second requestor, a second text-based protocol call directed to the first NF endpoint;
generate a second binary protocol call based on the second text-based protocol call;
transmit, to the second NF endpoint, the second binary protocol call over the first cached connection;
receive, from the second NF, a second binary protocol response over the second cached connection;
convert the second binary protocol response to a second text-based protocol response; and
transmit, to the second requestor, the second binary protocol response.
10. The system of claim 9 , wherein the first NF endpoint is within a first service provider network and the second NF endpoint is within a second service provider network.
11. The system of claim 8 , wherein the binary protocol call is a gRPC Remote Procedure Call (gRPC) call.
12. The system of claim 8 , wherein the text-based protocol call is a Hypertext Transfer Protocol (HTTP) call to a representational state transfer (REST) application programming interface (API).
13. The system of claim 8 , wherein the plurality of NF endpoint addresses is received from a global router.
14. The system of claim 8 , wherein the first NF endpoint runs in a Cloud Native Environment (CNE).
15. A non-transitory computer readable medium comprising instructions stored thereon, the instructions, when executed, causing one or more processors to:
prior to receiving a text-based protocol call from a requestor,
receive a plurality of network function (NF) endpoint addresses;
cache a plurality of connections among a plurality of NF endpoints using the plurality of NF endpoint addresses; and
store, in a forwarding table, the plurality of NF endpoint addresses;
receive, from the requestor, the text-based protocol call directed to a first NF endpoint;
generate a binary protocol call based on the text-based protocol call;
transmit, to a second NF endpoint, the binary protocol call over a first cached connection from the first NF endpoint to the second NF endpoint based on the forwarding table;
receive, from the second NF endpoint, a binary protocol response over a second cached connection from the second NF endpoint to the first NF endpoint based on the forwarding table;
convert the binary protocol response to a text-based protocol response; and
transmit, to the requestor, the text-based protocol response.
16. The non-transitory computer readable medium of claim 15 , further comprising instructions further causing the one or more processors to:
receive, from a second requestor, a second web protocol call, the second web protocol call directed to a second NF endpoint;
transmit, to the second NF endpoint, a second text-based protocol call directed to the first NF endpoint;
generate a second binary protocol call based on the second text-based protocol call;
transmit, to the second NF endpoint, the second binary protocol call over the first cached connection;
receive, from the second NF, a second binary protocol response over the second cached connection;
convert the second binary protocol response to a second text-based protocol response; and
transmit, to the second requestor, the text-based protocol response.
17. The non-transitory computer readable medium of claim 16 , wherein the first NF endpoint is within a first service provider network and the second NF endpoint is within a second service provider network.
18. The non-transitory computer readable medium of claim 15 , wherein the binary protocol call is a gRPC Remote Procedure Call (gRPC) call.
19. The non-transitory computer readable medium of claim 15 , wherein the text-based protocol call is a Hypertext Transfer Protocol (HTTP) call to a representational state transfer (REST) application programming interface (API).
20. The non-transitory computer readable medium of claim 15 , wherein the plurality of NF endpoint addresses is received from a global router, and wherein the first NF endpoint runs in a Cloud Native Environment (CNE).