System and method for message management across a network

US2020257579A1 · US · A1

Patent metadata
FieldValue
Publication numberUS-2020257579-A1
Application numberUS-202016859510-A
CountryUS
Kind codeA1
Filing dateApr 27, 2020
Priority dateJul 24, 2018
Publication dateAug 13, 2020
Grant date

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

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.

First claim

Opening claim text (preview).

What is claimed is: 1 . A method comprising: identifying a plurality of connections associated with a plurality of network function (NF) endpoints; receiving, from a requestor, a first protocol call of a first protocol type directed to a first NF endpoint of the plurality of NF endpoints; converting the first protocol call to a second protocol call of a second protocol type different the first protocol type; transmitting, to a second NF endpoint of the plurality of NF endpoints, the second protocol call over a first connection from the first NF endpoint to the second NF endpoint, the first connection comprising one of the plurality of connections associated with the plurality of NF endpoints; receiving, from the second NF endpoint, a first protocol response over a second connection from the second NF endpoint to the first NF endpoint, the second connection comprising a different one of the plurality of connections associated with the plurality of NF endpoints; converting the first protocol response to a second protocol response, the second protocol response being based on the protocol associated with the first protocol call; and transmitting, to the requestor, the second protocol response. 2 . The method of claim 1 , further comprising: receiving, from a second requestor, a third protocol call directed to the first NF endpoint, the third protocol call of the first protocol type; converting the third protocol call to a fourth protocol call of the second protocol type; transmitting, to the second NF endpoint, the fourth protocol call over the first connection; receiving, from the second NF, a third protocol response over the second connection, the third protocol response being based on the different protocol associated with the second protocol call; converting the third protocol response to a fourth protocol response, the fourth protocol response being based on the protocol associated with the first protocol call; and transmitting, to the second requestor, the fourth protocol response. 3 . The method of claim 1 , 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 second protocol call is a gRPC Remote Procedure Call (gRPC) call. 5 . The method of claim 1 , wherein the first 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 second protocol call comprises a binary protocol call. 7 . The method of claim 1 , further comprising: storing a plurality of NF endpoint addresses associated with the plurality of NF endpoints, wherein the plurality of connections is based on the plurality of NF endpoints. 8 . A system comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the system to: identify a plurality of connections associated with a plurality of network function (NF) endpoints; receive, from a requestor, a first protocol call directed to a first NF endpoint of the plurality of NF endpoints; convert the first protocol call to a second protocol call associated with a different protocol than a protocol associated with the first protocol call; transmit, to a second NF endpoint of the plurality of NF endpoints, the second protocol call over a first connection from the first NF endpoint to the second NF endpoint, the first connection comprising one of the plurality of connections associated with the plurality of NF endpoints; receive, from the second NF endpoint, a first protocol response over a second connection from the second NF endpoint to the first NF endpoint, the second connection comprising a different one of the plurality of connections associated with the plurality of NF endpoints; convert the first protocol response to a second protocol response, the second protocol response being based on the protocol associated with the first protocol call; and transmit, to the requestor, the second protocol response. 9 . The system of claim 8 , wherein the memory stores instructions that, when executed by the one or more processors, cause the system to: receive, from a second requestor, a third protocol call directed to the first NF endpoint, the third protocol call being based on the protocol associated with the first protocol call; convert the third protocol call to a fourth protocol call, the fourth protocol call being based on the different protocol associated with the second protocol call; transmit, to the second NF endpoint, the fourth protocol call over the first connection; receive, from the second NF, a third protocol response over the second connection, the third protocol response being based on the different protocol associated with the second protocol call; convert the third protocol response to a fourth protocol response, the fourth protocol response being based on the protocol associated with the first protocol call; and transmit, to the second requestor, the fourth protocol response. 10 . The system of claim 8 , 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 second protocol call is a gRPC Remote Procedure Call (gRPC) call. 12 . The system of claim 8 , wherein the first 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 second protocol call comprises a binary protocol call. 14 . The system of claim 8 , wherein the memory stores instructions that, when executed by the one or more processors, cause the system to: store a plurality of NF endpoint addresses associated with the plurality of NF endpoints, wherein the plurality of connections is based on the plurality of NF endpoints. 15 . A non-transitory computer-readable medium comprising instructions stored thereon, the instructions, when executed by one or more processors, cause the one or more processors to: identify a plurality of connections associated with a plurality of network function (NF) endpoints; receive, from a requestor, a first protocol call directed to a first NF endpoint of the plurality of NF endpoints; convert the first protocol call to a second protocol call associated with a different protocol than a protocol associated with the first protocol call; transmit, to a second NF endpoint of the plurality of NF endpoints, the second protocol call over a first connection from the first NF endpoint to the second NF endpoint, the first connection comprising one of the plurality of connections associated with the plurality of NF endpoints; receive, from the second NF endpoint, a first protocol response over a second connection from the second NF endpoint to the first NF endpoint, the second connection comprising a different one of the plurality of connections associated with the plurality of NF endpoints; convert the first protocol response to a second protocol response, the second protocol response being based on the protocol associated with the first protocol call; and transmit, to the requestor, the second protocol response. 16 . The non-transitory computer-readable medium of claim 15 , further comprising instructions that, when executed by the one or more processors, cause the one or more processors to: receive, from a second requestor, a third protocol call

Assignees

Inventors

Classifications

  • Address table lookup; Address filtering · CPC title

  • G06F9/547Primary

    Remote procedure calls [RPC]; Web services · CPC title

  • H04L67/02Primary

    based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title

  • Route determination based on the nature of the carried application · CPC title

  • Router architectures · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US2020257579A1 cover?
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 net…
Who is the assignee on this patent?
Cisco Tech Inc
What technology area does this patent fall under?
Primary CPC classification G06F9/547. Mapped technology areas include Physics.
When was this patent published?
Publication date Thu Aug 13 2020 00:00:00 GMT+0000 (Coordinated Universal Time) (A1). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).