Which makes Segment Routing the best suited approach for 5G?

The fifth generation (5G) of cellular networks promises to be a major step in the evolution of wireless technology. 5G is planned to be used in a very broad set of application scenarios. These scenarios have strict heterogeneous requirements that will be accomplished by enhancements on the radio access network and a collection of innovative wireless technologies. Softwarization technologies, such as Software-Defined Networking (SDN) and Network Function Virtualization (NFV), will play a key role in integrating these different technologies. Network slicing emerges as a cost-efficient solution for the implementation of the diverse 5G requirements and verticals. The 5G radio access and core networks will be based on a SDN/NFV infrastructure, which will be able to orchestrate the resources and control the network in order to efficiently and flexibly and with scalability provide network services.

So 5G Alone Isn’t Enough — It’s imperative to know, how to transform existing network Infrastructure for the 5G Era

Segment Routing & Traffic Engineering

With 5G, network operators are evolving to a cloud-based network model that will reduce costs, scale rapidly and speed the development of new services. However, as we move cloud technologies out of the data center and into the wide area network, traffic engineering becomes essential. The mechanics of moving packets around a WAN in a deterministic way requires an end-to-end smart network fabric that scales efficiently across multiple network domains. The signaling protocols currently used to reserve IP network resources, LDP and RSVP-TE, are simply not scalable for the 5G era. Hence, in order to operationalize 5G, the industry needs to move to segment routing.

Simply, segment routing provides tunnels for services such as VPRN or VPWS across multiple networks without the need for other protocols such as LDP or RSVP. A segment routing path is a sequential list of sub-paths or segments encoded as a stack of one or more MPLS labels or IPv6 addresses. It is easy to implement as it is based on extensions to IGP routing protocols such as IS-IS or OSPF in common use today. In a fully realized 5G implementation, segment routing uses a centralized SDN path control element (PCE) to determine paths through the network. This allows operators to dynamically engineer forwarding paths with much more granular policy parameters such as physical diversity, link state, available bandwidth, accumulative latency and maximum number of forwarding hops.

Although it has been around for a while, industry adoption has been slow — about 10 percent of the industry to date*. So, what is holding operators back? In the majority of cases, it simply requires a software upgrade to a router to support it, along with minimal training for personnel to move from RSVP/LDP. In part, the slow rate of adoption is because the pressing need for segment routing lies somewhere in the future. Why do today what you can put off until tomorrow? Other reasons include uneven support from vendors and a lack of incumbent reference cases.

Besides greater simplicity and reduced operations costs, the real force driving adoption of segment routing is the coming of 5G. New 5G services will have various requirements for bandwidth, latency, reliability and security that can be served by placing computing engines and data in the appropriate private or public cloud, whether that is at the edge, in the core or somewhere in between. Network slices are engineered to provide connectivity with the desired level of service between the end user and these resources across multiple network domains. This could be for a specific application, such as an IoT sensor network for a highway, or for a specific enterprise customer.

Background of Segment Routing

Currently, networks that need to adapt to services are evolving towards service-driven networks. Network adaptation to services refers to reactive adjustments of the network architecture and configurations based on service requirements. This model does not match the rapid development of services. Moreover, it makes network deployment more complex and network maintenance more difficult.

Figure below shows a service-driven network where explicit paths are calculated based on the requirements of applications. The network is dynamically adjusted in real time to rapidly meet service change requirements.

Segment Routing Fundamentals

Segment Routing involves the following concepts:

-Segment Routing domain: a set of Segment Routing nodes.

-SID: unique identifier of a segment. A SID is mapped to an MPLS label on the forwarding plane.

-Segment Routing global block (SRGB): a set of local labels reserved for Segment Routing.

Table below describes different types of segments.

Figure: Prefix, adjacency, and node SID examples

In plain terms, a prefix segment indicates a destination address, and an adjacency segment indicates a link for outgoing data packets. The prefix and adjacency segments are similar to the destination IP address and outbound interface in conventional IP forwarding, respectively. In an IGP area, an NE propagates its node SID and adjacency SID through extended IGP messages, so that any NE in the area can obtain information about the other NEs.

Combining prefix (node) and adjacency SIDs in sequence can construct any network path. Every hop on a path identifies a next hop, which is based on the segment information on the top of the label stack. The segment information is stacked in sequence at the top of the data header. If the top SID identifies another node, the receive end forwards the received data packet to that node through equal-cost multi-path routing (ECMP). If the top SID identifies the local node, the receive end removes the top SID and proceeds with the following procedure.

Prefix, adjacency, and node segments can be used independently or in combinations. They are mainly used in the following three modes:

1. Prefix segment-based mode: An IGP uses the shortest path first (SPF) algorithm to compute the shortest path. This mode is also called Segment Routing-Best Effort (SR-BE).

As shown in below figure, node Z is connected to the destination network with a prefix SID of 68. After an IGP propagates the prefix SID, each node in the IGP area learns the prefix SID of the network from node Z and then runs SPF to compute the shortest path to the network.

Figure: Prefix segment-based forwarding path

2. Adjacency segment-based mode: As shown in below figure, an adjacency segment is allocated to each adjacency on the network, and a segment list with multiple adjacency segments is defined on the ingress, so that any strict explicit path can be specified. In this mode, path adjustment and traffic optimization can be implemented in a centralized manner, facilitating software-defined networking (SDN) implementation. This mode is mainly used for Segment Routing-Traffic Engineering (SR-TE).

Figure: Adjacency segment-based forwarding path

3. Mode in which adjacency and node segments are combined: As shown in Figure below, adjacency and node segments are combined, and the adjacency segment allows a path to forcibly include a specified adjacency. Nodes can run SPF to compute the shortest path based on node segments or establish multiple paths to load-balance traffic. The paths computed in this mode are not strictly fixed. Therefore, they are also called loose explicit paths. This mode is mainly used for SR-TE.

Figure: Adjacency segment- and node segment-based forwarding path

SR-BE Tunnel Establishment

A forwarding path established using SR-BE technology is an LSP without a tunnel interface. This type of LSP is called SR LSP for short. The establishment and data forwarding of SR LSPs are similar to those of LDP LSPs.

Figure below shows how an SR LSP is established

The establishment procedure is as follows:

1. Manual configuration: The prefix SID and SRGB are manually configured on the desired NE and then propagated through an IGP packet.
2. Label distribution: Each NE parses the received IGP packet and computes a label value by summing up the start value in the local SRGB range and the prefix SID. In addition, each NE computes an outgoing label value by summing up the start value in the next-hop SRGB range and the prefix SID.
3. Path computation: Based on IGP-collected topology information, the NEs use the same SPF algorithm to compute a label forwarding path and then generate a forwarding entry.
4. Similar to traffic forwarding over MPLS LDP LSPs, traffic forwarding over SR LSPs also involves push, swap, and pop operations on label stacks and supports penultimate hop popping (PHP), MPLS QoS, and other features.

SR-TE Tunnel Establishment

SR-TE is a new TE tunnel technology that uses Segment Routing as a control protocol. A tunnel established using SR-TE is called an SR-TE tunnel.

SR-TE tunnels support the attributes of MPLS TE tunnels. In addition, they support bidirectional forwarding detection (BFD).

SR-TE tunnels can be manually configured. Manual configuration is suitable for small-scale networks because it does not require the cooperation of a controller. However, this method does not support bandwidth reservation. In addition to manual configuration, another way to generate an SR-TE tunnel is to run the Constrained Shortest Path First (CSPF) algorithm for path computation on the ingress. Although this way supports bandwidth reservation, the computed path is only locally optimal. SR-TE tunnels can also be generated by using a controller for path computation, as shown in Figure below.

The establishment procedure is as follows:

1. Manual configuration: Configure IGP SR on forwarders to generate link topology and label information.
2. Topology and label information reporting: BGP-LS reports the information to the controller.
3. Link generation: PCEP computes a label forwarding path.
4. Information delivery: Tunnel attributes and LSP information are delivered by NETCONF and PCEP, respectively.
5. Tunnel creation: An SR-TE tunnel is automatically created between PEs based on tunnel attributes and LSP information.

An SR-TE tunnel generated by a controller has the following advantages:

• The controller supports bandwidth computation and resource reservation, and can therefore compute a globally optimal path.
• The controller can cooperate with network applications. Upon receipt of an application-generated requirement, the controller can quickly respond to the requirement and compute a network forwarding path that meets the requirement, helping achieve a service-driven network.
• The controller does not require a lot of manual tunnel configurations, making this method more suitable for large-scale networks.

Segment Routing TI-LFA FRR

Traditional Loop-Free Alternate (LFA) and remote LFA (RLFA) technologies have constraints on the network topology and therefore cannot achieve 100% fault protection. This document uses RLFA as an example to describe the differences between RLFA and Topology-Independent Loop-Free Alternate (TI-LFA).

If RLFA is used and the link between B and E is faulty, B forwards data packets to C. Because the cost between C and D is 1000, C considers that the optimal path to F passes through B. As a result, the packets are forwarded back to B, causing a loop and forwarding failure.

If TI-LFA is used and the link between B and E is faulty, B directly uses TI-LFA FRR backup entries to add new path information (node SID of C and adjacency SID for C-to-D) to the data packets to ensure that the packets can be forwarded along the backup path.

TI-LFA establishes a backup path over an explicit path without topology constraints, theoretically achieving 100% FRR protection.

Segment Routing Advantages

Segment Routing has the following advantages:

1. Simplified MPLS control plane: Segment Routing does not require LDP or RSVP-TE deployment. Instead, it uses an IGP to distribute labels and compute paths, without changing the existing MPLS forwarding architecture. Table below compares Segment Routing with MPLS.

2. Simplified TE technology and improved capacity expansion capability: MPLS TE is a connection-oriented technology. To maintain the connection status, nodes need to exchange a large number of refresh packets. This increases the control plane load.

Segment Routing controls service paths only through label operations on the ingress. It does not require transit nodes to maintain path information, reducing the control plane load.

MPLS TE and Segment Routing need to maintain different numbers of connection states.

• For MPLS TE, the number of connection states to be maintained is directly proportional to the number of TE tunnels. That is, the number of connection states to be maintained is equal to the number of nodes raised to the power of 2.
• For Segment Routing, the ingress maintains tunnel status. The number of connection states to be maintained is equal to the sum of the number of nodes and the number of connections.

3. Smoother network evolution to SDN

• Existing protocols are extended, enabling the network to smoothly evolve.
• The ingress controls and adjusts service paths through the source routing technology, enabling the network to quickly respond to the requirements of upper-layer applications.
• Balancing centralized control and distributed control/forwarding prevents controller performance from becoming a service bottleneck.

Segment Routing Applications

After SR tunnels are established, service traffic needs to be steered to the tunnels. This process is called traffic steering. Because SR-BE tunnels do not have tunnel interfaces, the traffic steering mode of SR-BE is different from that of SR-TE.

SR-BE supports the following traffic steering modes:

• Tunnel policy: Use a tunnel type prioritizing policy to select SR-BE tunnels.
• Static route: When configuring a static route, specify the next hop as the destination address of an SR-BE tunnel and configure the route to recurse to the SR-BE tunnel based on the next hop.
• IP route recursion to tunnels: Configure a public IP route, such as a BGP route, to recurse to an SR-BE tunnel based on the next hop of the route.

SR-TE supports the following traffic steering modes:

• Tunnel policy: Use a tunnel type prioritizing policy to select SR-TE tunnels or a tunnel binding policy to bind SR-TE tunnels.
• Static route: When configuring a static route, specify the outbound interface of the route as an SR-TE tunnel interface.
• Auto route: An IGP uses an auto route related to an SR-TE tunnel functioning as a logical link to compute a path. The outbound interface of the route is used as an SR-TE tunnel interface.
• Policy-based routing: The outbound interface in an apply clause is used as an SR-TE tunnel interface.

Routes and services that can recurs to SR tunnels include static routes, BGP public network routes, and L3VPN, VPLS, VPWS, and EVPN services.

Migration to 5G Transport era holding the hand of Segment routing

Migration to segment routing is relatively easy. In the beginning, it can be deployed in some parts of the network with paths stitched through from one network to another, then expanded gradually across multiple networks. It can be encapsulated to travel across networks that do not support segment routing. Many operators start using it with shortest path first (SPF) routing and then add a centralized PCE later.

E2E SR-TE Set up for 5G sliced network:

Unified Management Solution by Blue Planet:

Summary

In tomorrow’s network there will be hundreds of times more users and devices that need to access network functions. Services and data will be located in a variety of smart central offices and distributed data centers. Not only do we need more paths through the network, we need many more different types of paths. Engineering the traffic traversing the resulting network fabric with today’s tools will overwhelm tomorrow’s network operations teams. Segment routing is one of a handful of key technologies that will not only make 5G networks work better, it will make them manageable and affordable to run.

Thank you!!

Monowar Hossain

Microwave Unit Head (Planning and Operation)

VEON, Bangladesh

Email: monowar.hossain@banglalink.net

Mobile: +8801962424691

Originally published at https://www.linkedin.com.