Disclosed herein are system, method, and computer program product embodiments for providing an API description of an external network service and using the API to integrate the external service into a network. An embodiment operates by receiving, from a service provider, a description of an application programming interface (API), transmitting a call to the service provider using the API for creating a new instance of a service and transmitting to the service provider a traffic flow upon which the service will be applied.
Legal claims defining the scope of protection, as filed with the USPTO.
1. A method for integrating external services into a first network, comprising: receiving, at a network element, a traffic flow addressed to a destination; receiving, at the network element, a description of an application programming interface (API) call from a service provider, wherein the description includes parameters; generating an API call including the parameters to be passed to the service provider, wherein generating the API call comprises: based on the traffic flow, generating variables corresponding to the parameters specified by the description of the API call; and substituting the variables for the corresponding parameters; transmitting the API call to the service provider to initiate a service; prior to transmission of the traffic flow to the destination, transmitting, to the service provider, the traffic flow to be processed by the initiated service; and after the traffic flow is processed by the initiated service, receiving, from the service provider, the traffic flow to forward on to the destination.
2. The method of claim 1 , wherein the description specifies a format for the API call.
3. The method of claim 2 , wherein transmitting the API call comprises transmitting the API call according to the format.
4. The method of claim 1 , wherein the network element resides in a first network, and the service provider processes a second traffic flow from a second network element residing in a second network independent from the first network.
5. The method of claim 1 , wherein the API call is transmitted to the service provider using at least one of Advance Message Queuing Protocol (AMQP), Simple Object Access Protocol (SOAP), Representational state transfer (REST), and Java Message Service (JMS).
6. A non-transitory computer-readable device having instructions stored thereon that, when executed by at least one computing device, causes the at least one computing device to perform operations comprising: receiving, at a network element, a traffic flow addressed to a destination; receiving, at the network element, a description of an application programming interface (API) call from a service provider, wherein the description includes parameters; generating an API call including the parameters to be passed to the service provider, wherein generating the API call comprises: based on the traffic flow, generating variables corresponding to the parameters specified by the description of the API call; and substituting the variables for the corresponding parameters; transmitting the API call to the service provider to initiate a service; prior to transmission of the traffic flow to the destination, transmitting, to the service provider, the traffic flow to be processed by the initiated service; and after the traffic flow is processed by the initiated service, receiving, from the service provider, the traffic flow to forward on to the destination.
7. The non-transitory computer-readable device of claim 6 , wherein the description specifies a format for the API call.
8. The non-transitory computer-readable device of claim 7 , wherein transmitting the API call comprises transmitting the API call according to the format.
9. The non-transitory computer-readable device of claim 6 , wherein the network element resides in a first network, and the service provider processes a second traffic flow from a second network element residing in a second network independent from the first network.
10. The non-transitory computer-readable device of claim 6 , wherein the API call is transmitted to the service provider using at least one of Advance Message Queuing Protocol (AMQP), Simple Object Access Protocol (SOAP), Representational state transfer (REST), and Java Message Service (JMS).
11. A system comprising a memory and one or more processors coupled to the memory, the one or more processors configured to: receive, at a network element, a traffic flow addressed to a destination; receive, at the network element, a description of an application programming interface (API) call from a service provider, wherein the description includes parameters; generate an API call including the parameters to be passed to the service provider, wherein generating the API call comprises: based on the traffic flow, generating variables corresponding to the parameters specified by the description of the API call; and substituting the variables for the corresponding parameters; transmit the API call to the service provider to initiate a service; prior to transmission of the traffic flow to the destination, transmit, to the service provider, the traffic flow to be processed by the initiated service; and after the traffic flow is processed by the initiated service, receive, from the service provider, the traffic flow to forward on to the destination.
12. The system of claim 11 , wherein the description specifies a format for the API call.
13. The system of claim 12 , wherein the one or more processors are configured to transmit the API call according to the format.
14. The system of claim 11 , wherein the system resides in a first network, and the service provider processes a second traffic flow from a second network element residing in a second network independent from the first network.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
June 17, 2019
July 28, 2020
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.