IP Library › Granted Patent US 11,240,264
Granted Patent B2
US 11,240,264 · App. 16/300,953 · Granted Feb 1, 2022

System and method for security service collaboration

Inventors: Daniel Migault (Montreal, CA); Makan Pourzandi (Montreal, CA); Bruno Medeiros de Barros (São Paulo, BR); Tereza Cristina Carvalho (São Paulo, BR); Thiago Rodrigues Meira de Almeida (Vila Figueira—Suzano, BR)
Assignee: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
H04L63/1458H04L45/306H04L45/64H04L69/22
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,240,264
App. No.
16/300,953
Granted
Feb 1, 2022
Kind
B2
Abstract

Systems and methods are provided for mitigating security attacks by enabling collaboration between security service functions. A Service Function Chaining (SFC) node receives a packet and determines whether to apply a service function to the packet. Responsive to determining that the packet has been treated by the service function, the packet can be reclassified and switched to a different SFC path.

Claims (48)

1. A method at a service function chaining (SFC) node, comprising:

receiving a packet including a first SFC Path identifier (ID) and a first SFC Index;

determining whether to apply a first service function to the packet;

setting a treated indicator in the packet in accordance with applying the first service function to the packet; and one of:

responsive to determining that the packet has not been treated by the first service function:

forwarding the packet in accordance with first SFC Path ID and first SFC Index; or

responsive to determining that the packet has been treated by the first service function:

selecting a second SFC Path ID and a second SFC Index associated with the first SFC Path ID and the first SFC Index;

modifying the packet by replacing the first SFC Path ID and first SFC Index with the second SFC Path ID and second SFC Index; and

forwarding the modified packet in accordance with the second SFC Path ID and second SFC Index.

2. The method of claim 1 , further comprising, determining whether to apply the first service function to the packet in accordance with determining if the first service function has already been applied to the packet.

3. The method of claim 2 , further comprising, determining if the first service function has already been applied to the packet in accordance with the treated indicator in the packet.

4. The method of claim 1 , further comprising, determining whether to apply the first service function to the packet in accordance with a collaboration agreement.

5. The method of claim 4 , wherein the collaboration agreement defines at least one of an amount of resources the SFC node has allocated for applying the first service function and a bandwidth of traffic to which the SFC node will apply the first service function.

6. The method of claim 1 , further comprising, determining whether to apply the first service function to the packet in accordance with a tunnel the packet was received on.

7. The method of claim 1 , wherein the treated indicator is stored as metadata in the packet.

8. The method of claim 1 , wherein the treated indicator is a field in a network service header.

9. The method of claim 1 , wherein the second SFC Path ID and the second SFC Index to are selected to bypass a subsequent instance of the first service function in the first SFC Path.

10. The method of claim 1 , further comprising, selecting a tunnel for forwarding the packet to a second domain in accordance with the second SFC Path ID and second SFC Index.

11. A service function chaining (SFC) node comprising circuitry including a processor and a memory, the memory containing instructions executable by the processor whereby the SFC node is operative to:

receive a packet including a first SFC Path identifier (ID) and a first SFC Index;

determine whether to apply a first service function to the packet;

set a treated indicator in the packet in accordance with applying the first service function to the packet; and one of:

responsive to determining that the packet has not been treated by the first service function:

forward the packet in accordance with first SFC Path ID and first SFC Index; or

responsive to determining that the packet has been treated by the first service function:

select a second SFC Path ID and a second SFC Index associated with the first SFC Path ID and the first SFC Index;

modify the packet by replacing the first SFC Path ID and first SFC Index with the second SFC Path ID and second SFC Index; and

forward the modified packet in accordance with the second SFC Path ID and second SFC Index.

12. The SFC node of claim 11 , further operative to determine whether to apply the first service function to the packet in accordance with determining if the first service function has already been applied to the packet.

13. The SFC node of claim 12 , further operative to determine if the first service function has already been applied to the packet in accordance with the treated indicator in the packet.

14. The SFC node of claim 11 , further operative to determine whether to apply the first service function to the packet in accordance with a collaboration agreement.

15. The SFC node of claim 14 , wherein the collaboration agreement defines at least one of an amount of resources the SFC node has allocated for applying the first service function and a bandwidth of traffic to which the SFC node will apply the first service function.

16. The SFC node of claim 11 , further operative to determine whether to apply the first service function to the packet in accordance with a tunnel the packet was received on.

17. The SFC node of claim 11 , wherein the treated indicator is stored as metadata in the packet.

18. The SFC node of claim 11 , wherein the treated indicator is a field in a network service header.

19. The SFC node of claim 11 , wherein the second SFC Path ID and the second SFC Index to are selected to bypass a subsequent instance of the first service function in the first SFC Path.

20. The SFC node of claim 11 , further operative to select a tunnel for forwarding the packet to a second domain in accordance with the second SFC Path ID and second SFC Index.

21. A non-transitory computer readable storage medium storing executable instructions, which when executed by a processor, cause the processor to:

receive a packet including a first SFC Path identifier (ID) and a first SFC Index;

determine whether to apply a first service function to the packet;

set a treated indicator in the packet in accordance with applying the first service function to the packet; and one of:

responsive to determining that the packet has not been treated by the first service function:

forward the packet in accordance with first SFC Path ID and first SFC Index; or

responsive to determining that the packet has been treated by the first service function:

select a second SFC Path ID and a second SFC Index associated with the first SFC Path ID and the first SFC Index;

modify the packet by replacing the first SFC Path ID and first SFC Index with the second SFC Path ID and second SFC Index; and

forward the modified packet in accordance with the second SFC Path ID and second SFC Index.

Assignments (4)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 30, 2022
From: ERICSSON TELECOMUNICAÇÕES S.A.
To: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
Reel/Frame 060390/0703 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 7, 2021
From: ERICSSON TELECOMUNICAÇÕES S.A.
To: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
Reel/Frame 059586/0032 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 7, 2021
From: MIGAULT, DANIEL; POURZANDI, MAKAN
To: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
Reel/Frame 058317/0008 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 7, 2021
From: CARVALHO, TEREZA CRISTINA; RODRIGUES MEIRA DE ALMEIDA, THIAGO; MEDEIROS DE BARROS, BRUNO
To: ERICSSON TELECOMUNICAÇÕES S.A.
Reel/Frame 058317/0781 →
Continuity (2)
Provisional Application 62336137 · May 13, 2016
Related Publication 20200314139A1 · Oct 1, 2020