# US 2020/0267079 A1 · Using border gateway protocol to expose maximum segment identifier depth to an external application

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2020/0267079 A1
- Document ID: US20200267079A1
- Status: Published application
- Kind: A1
- Application number: 16/869,391
- Filed: 2020-05-07
- Published: 2020-08-20
- Earliest claimed: 2015-07-02
- Assignees: Telefonaktiebolaget LM Ericsson (publ)
- Applicants: Telefonaktiebolaget LM Ericsson (publ)
- Inventors: Evgeny TANTSURA; Gregory MIRSKY
- Web page: https://patentgrep.com/patent/US20200267079A1

## CPC

- H04L 45/72: {Routing based on the source address}
- H04L 45/02: Topology update or discovery
- H04L 45/507: {Label distribution}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method of exposing a maximum segment identifier depth (MSD) value of the network device is described. The method comprises transmitting to a centralized controller an attribute Type Length Value (TLV). A type of the attribute TLV includes a type of a maximum segment identifier depth (MSD) indicating that the MSD is a link MSD, a length of the attribute TLV includes a length of the MSD, and a value of the attribute TLV includes the MSD, which is a maximum number of segment routing (SR) labels supported at a link of the network node. The centralized controller is to use the attribute TLV to compute an SR tunnel with one or more SR labels, a label stack depth of the SR tunnel does not exceed the MSD, and the SR labels are used for steering a packet through an SR network.

## Claims

### Claim 1

A method implemented by a network node, the method comprising:
transmitting to a centralized controller an attribute Type Length Value (TLV), wherein a type of the attribute TLV includes a type of a maximum segment identifier depth (MSD) indicating that the MSD is a link MSD, a length of the attribute TLV includes a length of the MSD, and a value of the attribute TLV includes the MSD, which is a maximum number of segment routing (SR) labels supported at a link of the network node, wherein the centralized controller is to use the attribute TLV to compute an SR tunnel with one or more SR labels, a label stack depth of the SR tunnel does not exceed the MSD, and the SR labels are used for steering a packet through an SR network.

### Claim 2 (depends on 1)

The method of claim 1, wherein the attribute TLV is a Border Gateway Protocol Link State (BGP-LS) extension message.

### Claim 3 (depends on 2)

The method of claim 2 further comprising:
negotiating capabilities of a BGP session; and
verifying that the centralized controller supports reception of MSDs in BGP-LS extension messages.

### Claim 4 (depends on 3)

The method of claim 3, wherein transmitting to the centralized controller the attribute TLV is performed in response to verifying that the centralized controller supports reception of MSDs in BGP-LS extension messages.

### Claim 5 (depends on 1)

The method of claim 1, wherein the network node does not support Path Computation Element Communication Protocol (PCEP) and does not participate in Interior Gateway Protocol(s) (IGP).

### Claim 6 (depends on 1)

The method of claim 1, wherein the network node is an ingress node of the SR tunnel.

### Claim 7

A network node, comprising:
a processor and a memory, said memory containing instructions executable by the processor to cause the network node to:
transmit to a centralized controller an attribute Type Length Value (TLV), wherein a type of the attribute TLV includes a type of a maximum segment identifier depth (MSD) indicating that the MSD is a link MSD, a length of the attribute TLV includes a length of the MSD, and a value of the attribute TLV includes the MSD, which is a maximum number of segment routing (SR) labels supported at a link of the network node, wherein the centralized controller is to use the attribute TLV to compute an SR tunnel with one or more SR labels, a label stack depth of the SR tunnel does not exceed the MSD, and the SR labels are used for steering a packet through an SR network.

### Claim 8 (depends on 7)

The network node of claim 7, wherein the attribute TLV is a Border Gateway Protocol Link State (BGP-LS) extension message.

### Claim 9 (depends on 8)

The network node of claim 8, wherein the instructions executable by the processor are further to cause the network node to:
negotiate capabilities of a BGP session; and
verify that the centralized controller supports reception of MSDs in BGP-LS extension messages.

### Claim 10 (depends on 9)

The network node of claim 9, wherein to transmit to the centralized controller the attribute TLV is performed in response to verifying that the centralized controller supports reception of MSDs in BGP-LS extension messages.

### Claim 11 (depends on 7)

The network node of claim 7, wherein the network node does not support Path Computation Element Communication Protocol (PCEP) and does not participate in Interior Gateway Protocol(s) (IGP).

### Claim 12 (depends on 7)

The network node of claim 7, wherein the network node is an ingress node of the SR tunnel.

### Claim 13

A non-transitory machine-readable storage medium that provides instructions that, if executed by a processor of a network node, will cause said processor to perform operations comprising:
transmitting to a centralized controller an attribute Type Length Value (TLV), wherein a type of the attribute TLV includes a type of a maximum segment identifier depth (MSD) indicating that the MSD is a link MSD, a length of the attribute TLV includes a length of the MSD, and a value of the attribute TLV includes the MSD, which is a maximum number of segment routing (SR) labels supported at a link of the network node, wherein the centralized controller is to use the attribute TLV to compute an SR tunnel with one or more SR labels, a label stack depth of the SR tunnel does not exceed the MSD, and the SR labels are used for steering a packet through an SR network.

### Claim 14 (depends on 13)

The non-transitory machine-readable storage medium of claim 13, wherein the attribute TLV is a Border Gateway Protocol Link State (BGP-LS) extension message.

### Claim 15 (depends on 14)

The non-transitory machine-readable storage medium of claim 14, wherein the operations further comprise:
negotiating capabilities of a BGP session; and
verifying that the centralized controller supports reception of MSDs in BGP-LS extension messages.

### Claim 16 (depends on 15)

The non-transitory machine-readable storage medium of claim 15, wherein transmitting to the centralized controller the attribute TLV is performed in response to verifying that the centralized controller supports reception of MSDs in BGP-LS extension messages.

### Claim 17 (depends on 13)

The non-transitory machine-readable storage medium of claim 13, wherein the network node does not support Path Computation Element Communication Protocol (PCEP) and does not participate in Interior Gateway Protocol(s) (IGP).

### Claim 18 (depends on 13)

The non-transitory machine-readable storage medium of claim 13, wherein the network node is an ingress node of the SR tunnel.

### Claim 19

A method in a network controller, the method comprising:
receiving from a network node an attribute Type Length Value (TLV), wherein a type of the attribute TLV includes a type of a maximum segment identifier depth (MSD) indicating that the MSD is a link MSD, a length of the attribute TLV includes a length of the MSD, and a value of the attribute TLV includes a value of the MSD, which is a maximum number of segment routing (SR) labels supported at a link of the network node; and
using the attribute TLV to compute an SR tunnel with one or more SR labels, wherein a label stack depth of the SR tunnel does not exceed the MSD, and the SR labels are used for steering a packet through an SR network that includes the network node.

### Claim 20 (depends on 19)

The method of claim 19, wherein the attribute TLV is a Border Gateway Protocol Link State (BGP-LS) extension message.

### Claim 21 (depends on 20)

The method of claim 20 further comprising:
negotiating capabilities of a BGP session; and
verifying that the network node supports transmission of MSDs in BGP-LS extension messages.

### Claim 22 (depends on 19)

The method of claim 19, wherein the network node does not support Path Computation Element Communication Protocol (PCEP) and does not participate in Interior Gateway Protocol(s) (IGP).

### Claim 23

A centralized controller comprising:
a processor and a memory, said memory containing instructions executable by the processor to cause the centralized controller to:
receive from a network node an attribute Type Length Value (TLV), wherein a type of the attribute TLV includes a type of a maximum segment identifier depth (MSD) indicating that the MSD is a link MSD, a length of the attribute TLV includes a length of the MSD, and a value of the attribute TLV includes a value of the MSD, which is a maximum number of segment routing (SR) labels supported at a link of the network node, and
use the attribute TLV to compute an SR tunnel with one or more SR labels, wherein a label stack depth of the SR tunnel does not exceed the MSD, and the SR labels are used for steering a packet through an SR network that includes the network node.

### Claim 24 (depends on 23)

The centralized controller of claim 23, wherein the attribute TLV is a Border Gateway Protocol Link State (BGP-LS) extension message.

### Claim 25 (depends on 24)

The centralized controller of claim 24, wherein the instructions executable by the processor are further to cause the centralized controller to:
negotiate capabilities of a BGP session; and
verify that the network node supports transmission of MSDs in BGP-LS extension messages.

### Claim 26 (depends on 23)

The centralized controller of claim 23, wherein the network node does not support Path Computation Element Communication Protocol (PCEP) and does not participate in Interior Gateway Protocol(s) (IGP).

### Claim 27

A non-transitory machine-readable storage medium that provides instructions that, if executed by a processor of a centralized controller, will cause said processor to perform operations comprising:
receiving from a network node an attribute Type Length Value (TLV), wherein a type of the attribute TLV includes a type of a maximum segment identifier depth (MSD) indicating that the MSD is a link MSD, a length of the attribute TLV includes a length of the MSD, and a value of the attribute TLV includes a value of the MSD, which is a maximum number of segment routing (SR) labels supported at a link of the network node; and
using the attribute TLV to compute an SR tunnel with one or more SR labels, wherein a label stack depth of the SR tunnel does not exceed the MSD, and the SR labels are used for steering a packet through an SR network that includes the network node.

### Claim 28 (depends on 27)

The non-transitory machine-readable storage medium of claim 27, wherein the attribute TLV is a Border Gateway Protocol Link State (BGP-LS) extension message.

### Claim 29 (depends on 28)

The non-transitory machine-readable storage medium of claim 28 further comprising:
negotiating capabilities of a BGP session; and
verifying that the network node supports transmission of MSDs in BGP-LS extension messages.

### Claim 30 (depends on 27)

The non-transitory machine-readable storage medium of claim 27, wherein the network node does not support Path Computation Element Communication Protocol (PCEP) and does not participate in Interior Gateway Protocol(s) (IGP).
