Slice-based recovery and convergence

Patent metadata

Field	Value
Publication number	US-12177113-B2
Application number	US-202217701945-A
Country	US
Kind code	B2
Filing date	Mar 23, 2022
Priority date	Mar 23, 2022
Publication date	Dec 24, 2024
Grant date	Dec 24, 2024

Abstract

A method may include identifying network slices associated with transmitting data in a network and determining, by a routing device, that a failure associated with a path used to transmit data has occurred. The method may also include determining, by the routing device, whether the failure is associated with one of the plurality of network slices. The method may further include prioritizing, by the routing device, a route selection process in response to determining that the failure is associated with one of the plurality of network slices.

First claim

What is claimed is:

1. A method, comprising:
identifying a plurality of network slices associated with transmitting data in a network;
determining, by a routing device, that a failure associated with a path used to transmit data has occurred, wherein the failure corresponds to a failure of a link in the path or a failure of a router in the path;
determining, by the routing device, whether the failure is associated with one of the plurality of network slices; and
prioritizing, by the routing device, a route selection process to identify an alternate path in response to determining that the failure is associated with one of the plurality of network slices.

2. The method of claim 1 , further comprising:
forwarding, by a network device, information identifying the plurality of network slices to the routing device.

3. The method of claim 2 , further comprising:
forwarding, by the routing device, the information identifying the plurality of network slices to at least one other routing device.

4. The method of claim 1 , further comprising:
determining that the failure is associated with a first network slice having a first priority, and wherein the prioritizing comprises:
identifying, by the routing device, at least one alternate route associated with the first network slice prior to identifying alternate routes associated with paths not having the first priority.

5. The method of claim 4 , wherein the prioritizing further comprises:
storing, by the routing device and in a routing table, at least one route associated with the first network slice affected by the failure prior to storing other routes not associated with the first network slice.

6. The method of claim 4 , wherein the prioritizing further comprises:
installing, by the routing device and in a routing table, routes associated with network slices affected by the failure, prior to installing other routes based on at least one of a priority, service level agreement (SLA) information, quality of service (QOS) information or a convergence metric associated with the network slices.

7. The method of claim 1 , wherein each of the plurality of network slices has a corresponding slice identifier (ID), the method further comprising:
mapping, by the network device, the slice ID associated with a first one of the plurality of network slices into a format readable by the routing device; and
forwarding, by a network device, the mapped slice ID to the routing device.

8. The method of claim 1 , wherein the prioritizing comprises:
receiving, from a network device, information identifying the plurality of network slices; and
storing, by the routing device, the information identifying the plurality of network slices.

9. The method of claim 1 , further comprising:
forwarding, by the routing device, a selected route associated with a first one of the plurality of network slices to another router associated with the first slice.

10. The method of claim 1 , further comprising:
identifying a new path to transmit data associated with a first one of the network slices associated with the failure prior to identifying new paths associated with the failure and not associated with a network slice.

11. A system, comprising:
a first device comprising a processor, wherein the first device is configured to:
store information identifying a plurality of network slices associated with transmitting data in a network, and
forward the information to other devices in the network; and

a routing device configured to:
receive the information identifying the plurality of network slices from the first device,
determine that a failure associated with a path used to transmit data has occurred, wherein the failure corresponds to a failure of a link in the path or a failure of a router in the path,
determine whether the failure is associated with one of the plurality of network slices; and
prioritize a route selection process to identify an alternate path in response to determining that the failure is associated with one of the plurality of network slices.

12. The system of claim 11 , wherein the routing device is further configured to:
forward the information identifying the plurality of network slices to at least one other routing device.

13. The system of claim 11 , wherein the routing device is further configured to:
determine that the failure is associated with a first network slice having a first priority, and when prioritizing, the routing device is further configured to:
identify at least one alternate route associated with the first network slice prior to identifying alternate routes associated with paths not having the first priority.

14. The system of claim 13 , wherein when prioritizing, the routing device is further configured to:
store, in a routing table, the at least one alternate route associated with the first network slice prior to storing other routes in the routing table.

15. The system of claim 11 , wherein the routing device is further configured to:
install, in a routing table, routes associated with network slices affected by the failure, prior to installing other routes based on at least one of a priority, service level agreement (SLA) information, quality of service (QOS) information or a convergence metric associated with the network slices.

16. The system of claim 11 , wherein each of the plurality of network slices has a corresponding slice identifier (ID), and wherein the first device is further configured to:
map the slice ID associated with a first one of the plurality of network slices into a format readable by the routing device, and
forward the mapped slice ID to the routing device.

17. The system of claim 11 , wherein the routing device is further configured to:
forward a selected route associated with a first one of the plurality of network slices to another routing device associated with the first network slice.

18. A routing device, comprising:
a memory configured to store information identifying a plurality of network slices associated with transmitting data in a network; and
processing logic configured to:
determine that a failure associated with a path used to transmit data has occurred, wherein the failure corresponds to a failure of a link in the path or a failure of a router in the path,
determine whether the failure is associated with one of the plurality of network slices, and
prioritize a route selection process to identify an alternate path in response to determining that the failure is associated with one of the plurality of network slices.

19. The routing device of claim 18 , wherein the processing logic is further configured to:
determine that the failure is associated with a first network slice having a first priority, and

when prioritizing, the processing logic is further configured to:
identify at least one alternate route associated with the first network slice prior to identifying alternate routes associated with paths not having the first priority.

20. The routing device of claim 18 , wherein the routing device further comprises:
a routing table, and

wherein the processing logic is further configured to:
install, in the routing table, routes associated with network slices affected by the failure, prior to installing other routes in the routing table based on at least one of a priority, service level agreement (SLA) information or quality of service (QOS) information associated with the network slices.

Assignees

• Verizon Patent & Licensing Inc

Inventors

• PATIL Sudhakar Reddy
• Taft David
• Morris Nicklous D
• Jalil Luay

Classifications

• H04L47/24

  Traffic characterised by specific attributes, e.g. priority or QoS · CPC title

• H04W24/04

  Arrangements for maintaining operational condition · CPC title

• H04L45/28 Primary

  using route fault recovery · CPC title