Abstract:
In one embodiment, a service chain data packet is instrumented as it is communicated among network nodes in a network providing service-level and/or networking operations visibility. The service chain data packet includes a particular header identifying a service group defining one or more service functions, and is a data packet and not a probe packet. A network node adds networking and/or service-layer operations data to the particular service chain data packet, such as, but not limited to, in the particular header. Such networking operations data includes a performance metric or attribute related to the transport of the particular service chain packet in the network. Such service-layer operations data includes a performance metric or attribute related to the service-level processing of the particular service chain data packet in the network.
Abstract:
In one embodiment, a method comprises selecting, by an ingress provider edge router, one of first or second provider edge routers as a primary router for reaching a destination via a core network, and selecting the other of the first or second provider edge routers as a backup router for reaching the destination via the core network; and inserting, into an IPv6 data packet destined for the destination, a primary label assigned by the primary router and a repair label assigned by backup router, and an IPv6 extension header specifying first and second segment identifiers associated with the respective first and second provider edge routers and a protected flag that enables fast rerouting of the IPv6 data packet to the backup router if the primary router is unavailable.
Abstract:
In one embodiment, a segment routing and tunnel exchange provides packet forwarding efficiencies in a network, including providing an exchange between a segment routing domain and a packet tunnel domain. One application includes the segment routing and tunnel exchange interfacing segment routing packet forwarding (e.g., in a Evolved Packet Core (EPC) and/or 5-G user plane) and packet tunnel forwarding in access networks (e.g., replacing a portion of a tunnel between an access node and a user plane function for accessing a corresponding data network). In one embodiment, a network provides mobility services using a segment routing data plane that spans segment routing and tunnel exchange(s) and segment routing-enabled user plane functions. One embodiment uses the segment routing data plane without any modification to a (radio) access network (R)AN (e.g., Evolved NodeB, Next Generation NodeB) nor to user equipment (e.g., any end user device).
Abstract:
In one embodiment, a method comprises detecting, by a first provider edge router, a second provider edge router providing reachability to a prescribed destination address prefix via a protected next hop address; allocating, by the first provider edge router, a minor forwarding table associated with the second provider edge router and identifying a destination used by the second provider edge router for reaching the prescribed destination address prefix; and the first provider edge router sending repair information to a Border Gateway Protocol (BGP)-free core network router in the core network, the repair information enabling the BGP-free core network router to add a context label and reroute a received data packet to the first provider edge router if the second provider edge router is unavailable, the context label enabling the first provider edge router to identify the destination in the rerouted data packet for delivery to the destination address prefix.
Abstract:
In one embodiment, a method comprises detecting, by a provider edge router configured for providing reachability for core network traffic to a prescribed destination address prefix, a backup provider edge router relative to the prescribed destination address prefix; allocating, by the provider edge router, a distinct protected next-hop address for reachability to at least the destination address prefix via the provider edge router; and sending via a core network, by the provider edge router, repair information for the prescribed destination address prefix to ingress provider edge routers and a BGP-free core network router in the core network, the repair information enabling the ingress provider edge routers to insert primary and backup switching labels into each data packet of the core network traffic enabling the BGP-free core network router to reroute the received packet to the backup provider edge router if the provider edge router is unavailable.
Abstract:
In one embodiment, a Segment Routing network node provides efficiencies in processing and communicating Internet Protocol packets in a network. This Segment Routing node typically advertises (e.g., using Border Gateway Protocol) its Segment Routing processing capabilities, such as Penultimate Segment Pop (PSP) and/or Ultimate Segment Pop (USP) of a Segment Routing Header (including in the context of a packet that has multiple Segment Routing Headers). Subsequently, an Internet Protocol Segment Routing packet having multiple Segment Routing Headers is received. The packet is processed according to a Segment Routing function, with is processing including removing a first one of the Segment Routing Headers and forwarding the resultant Segment Routing packet. The value of the Segments Left field in the first Segment Routing Header identifies to perform PSP when the value is one, to perform USP when the value is zero, or to perform other processing.
Abstract:
In one embodiment, Ethernet Virtual Private Network (EVPN) is implemented using Internet Protocol Version 6 (IPv6) Segment Routing (SRv6) underlay network and SRv6-enhanced Border Gateway Protocol (BGP) signaling. A particular route associated with a particular Internet Protocol Version 6 (IPv6) Segment Routing (SRv6) Segment Identifier (SID) is advertised in a particular route advertisement message of a routing protocol (e.g., BGP). The SID includes encoding representing a particular Ethernet Virtual Private Network (EVPN) Layer 2 (L2) flooding Segment Routing end function of the particular router and a particular Ethernet Segment Identifier (ESI), with the particular SID including a routable prefix to the particular router. The particular router receives a particular packet including the particular SID; and in response, the particular router performs the particular EVPN end function on the particular packet.
Abstract:
Resource rationing for network slices in segment routing networks may be provided. A network slice may be created in a communication network. A portion of network resource may be dedicated to the network slice. The dedicated portion of network resource may be bound to the network slice using a segment identifier. The segment identifier may be advertised to the communication network. Data packets associated with the network slice may be routed using the dedicated portion of network resource.
Abstract:
In one embodiment, Segment Routing Internet Protocol Version 6 (SRv6) micro segments (“uSIDs”) are included in destination addresses, and possibly in other Segment Identifiers (“SIDs”), of packets transported through a network, and invoking corresponding network behavior, including, but not limited to, realization of corresponding network slices. In one embodiment, network nodes are configured to perform differential network slice realization functionality based on values slice-representative value(s) provided by global and/or local uSIDs of packets. This configuration may be defined by a controller in the network and/or routing protocol advertisements. Responsive to a received packet, a network node identifies and performs the corresponding network slice realization functionality based on slice-representative value(s) provided by one or more global and/or local uSIDs of the destination address of the received packet. Various encodings within an IPv6 Destination Address of the encapsulating packet are disclosed.
Abstract:
In one embodiment, a network comprises a first forwarding domain using a first data plane forwarding protocol and a second forwarding domain using a second data plane forwarding protocol different than the first data forwarding plane forwarding protocol. The first forwarding domain includes a first path node and a particular border node. The second forwarding domain includes a second path node and the particular border node. The particular border node performs Segment Routing or other protocol interworking between the different data plane forwarding domains, such as for transporting packets through a different forwarding domain or translating a packet to use a different data forwarding protocol. These forwarding domains typically include Segment Routing (SR) and SR-Multiprotocol Label Switching (SR-MPLS). Paths through the network are determined by a Path Computation Engine and/or based on route advertisements such associated with Binding Segment Identifiers (BSIDs) (e.g., labels, Internet Protocol version 6 addresses).