Secure service chaining

US10798187B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-10798187-B2
Application numberUS-201715627084-A
CountryUS
Kind codeB2
Filing dateJun 19, 2017
Priority dateJun 19, 2017
Publication dateOct 6, 2020
Grant dateOct 6, 2020

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.

In one embodiment, secure service chaining can be implemented efficiently for content delivery systems. An orchestrator can determine a service chain for processing a request from a client for content. The orchestrator can determine a capability identifying nodes of the service chain. The orchestrator can then transmit, to the client, a redirect message having the capability, wherein the redirect message redirects the request to a first node of the service chain. The nodes of the service chain can verify the capability and carry out the service chain. Service functions can be applied to the traffic flow associated with delivering the content to the user.

First claim

Opening claim text (preview).

What is claimed is: 1. A method for service chaining, the method comprising: determining a service chain for processing a request from a client for content; determining a capability identifying nodes of the service chain; and transmitting, to the client, a redirect message having the capability, wherein, the redirect message includes a message and a name of the content, the redirect message redirects the request to a first node of the service chain, and the capability of the redirect message includes a service chain identifier identifying the service chain. 2. The method of claim 1 , further comprising: signing the capability to generate a signature to be verified by nodes of the service chain, wherein the redirect message further includes the signature. 3. The method of claim 1 , wherein the redirect message includes a signature of the message and the name of the content. 4. The method of claim 1 , wherein the capability of the redirect message comprises addresses and port numbers of the nodes of the service chain. 5. The method of claim 1 , wherein the capability of the redirect message comprises an identifier for a further capability identifying further node(s) of the service chain to be provided to the first node of the service chain. 6. The method of claim 1 , wherein the capability identifies a time period during which the capability is valid within the service chain. 7. An orchestrator for service chaining, the orchestrator comprising: at least one memory element having instructions stored thereon; and at least one processor coupled to the at least one memory element and configured to execute the instructions to cause the orchestrator to perform operations including: determining a service chain for processing a request from a client for content; determining a capability identifying nodes of the service chain; and transmitting, to the client, a redirect message having the capability, wherein, the redirect message includes a message and a name of the content, the redirect message redirects the request to a first node of the service chain, and the capability of the redirect message includes a service chain identifier identifying the service chain. 8. The orchestrator of claim 7 , wherein the operations further include: signing the capability to generate a signature to be verified by nodes of the service chain, wherein the redirect message further includes the signature. 9. The orchestrator of claim 7 , wherein the redirect message includes a signature of the message and the name of the content. 10. The orchestrator of claim 7 , wherein the capability of the redirect message comprises addresses and port numbers of the nodes of the service chain. 11. The orchestrator of claim 7 , wherein the capability of the redirect message comprises an identifier for a further capability identifying further node(s) of the service chain to be provided to the first node of the service chain. 12. The orchestrator of claim 7 , wherein the capability identifies a time period during which the capability is valid within the service chain. 13. One or more computer-readable non-transitory media comprising one or more instructions for service chaining, that when executed on a processor configure the processor to: determine a service chain for processing a request from a client for content; determine a capability identifying nodes of the service chain; and transmit, to the client, a redirect message having the capability, wherein, the redirect message includes a message and a name of the content, the redirect message redirects the request to a first node of the service chain, and the capability of the redirect message includes a service chain identifier identifying the service chain. 14. The one or more computer-readable non-transitory media of claim 13 , wherein the instructions, that when executed on the processor, further configure the processor to: sign the capability to generate a signature to be verified by nodes of the service chain, wherein the redirect message further includes the signature. 15. The one or more computer-readable non-transitory media of claim 13 , wherein the redirect message includes a signature of the message and the name of the content. 16. The one or more computer-readable non-transitory media of claim 13 , wherein the capability of the redirect message includes addresses and port numbers of the nodes of the service chain. 17. The one or more computer-readable non-transitory media of claim 13 , wherein the capability of the redirect message comprises an identifier for a further capability identifying further node(s) of the service chain to be provided to the first node of the service chain. 18. The one or more computer-readable non-transitory media of claim 13 , wherein the capability identifies a time period during which the capability is valid within the service chain.

Assignees

Inventors

Classifications

  • H04L67/02Primary

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

  • Routing a service request depending on the request content or context · CPC title

  • Data redirection of data network streams · CPC title

  • H04L67/51Primary

    Discovery or management thereof, e.g. service location protocol [SLP] or web services · CPC title

  • above the transport layer · 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 US10798187B2 cover?
In one embodiment, secure service chaining can be implemented efficiently for content delivery systems. An orchestrator can determine a service chain for processing a request from a client for content. The orchestrator can determine a capability identifying nodes of the service chain. The orchestrator can then transmit, to the client, a redirect message having the capability, wherein the redire…
Who is the assignee on this patent?
Cisco Tech Inc
What technology area does this patent fall under?
Primary CPC classification H04L67/02. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Oct 06 2020 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 12 related publications on this page (citations in our corpus or others sharing the same primary CPC).