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.

Abstract: A method, a network device, and a non-transitory computer-readable storage medium are described in relation to an transport congestion control notification service. The transport congestion control notification service may include providing congestion notification by a network device according to a schedule. The congestion notification may be implemented as explicit congestion notification bits included in packets. The schedule may govern the starting and stopping of the congestion notification. The schedule may be generated based on historical congestion states of relevance to the network device. The schedule may be generated by the network device or by an external device and provisioned at the network device.

Abstract: A source network device may receive a multicast data stream to be provided to a plurality of network devices of a network, and may generate, for the multicast data stream, a segment routing header that identifies the plurality of network devices to be provided the multicast data stream. The source network device may cause the multicast data stream to be serially provided to the plurality of network devices identified in the segment routing header without requiring the plurality of network devices to store and reconstruct the segment routing header and without requiring the plurality of network devices to maintain state.

Abstract: A source network device may receive a multicast data stream to be provided to a plurality of network devices of a network, and may generate, for the multicast data stream, a segment routing header that identifies the plurality of network devices to be provided the multicast data stream. The source network device may cause the multicast data stream to be serially provided to the plurality of network devices identified in the segment routing header without requiring the plurality of network devices to store and reconstruct the segment routing header and without requiring the plurality of network devices to maintain state.

Abstract: Embodiments described herein allow reduced latency and computational costs by identifying a slice associated with a packet and determining an action to be performed with respect to the packet without having to perform deep packet inspection on the packet. An aspect of the present disclosure is a method comprising receiving a packet including a slice identifier corresponding to a slice of a network, the slice identifier having a plurality of bits; determining a bit value for each bit in a subset of the plurality of bits; and performing an action with respect to the packet based on the bit value of at least one bit in the subset.

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.

Abstract: A system described herein may provide a technique for the differentiated Quality of Service (“QoS”) treatment of different traffic types associated with the same application (e.g., a “multi-persona” application) by a wireless network, without the exposure of an application identifier of the application to the wireless network. The application may provide a traffic type indication, based on which a User Equipment (“UE”) may establish one or more QoS flows or other types of communication sessions with the wireless network, where the QoS flows or other types of communication sessions are associated with a network slice that is associated with the traffic type. The communication sessions may include Data Radio Bearers (“DRBs”), backhaul links, protocol data unit (“PDU”) sessions, or other suitable types of communication sessions.

Abstract: A system described herein may provide a technique for the differentiated Quality of Service (“QoS”) treatment of different traffic types associated with the same application (e.g., a “multi-persona” application) by a wireless network, without the exposure of an application identifier of the application to the wireless network. The application may provide a traffic type indication, based on which a User Equipment (“UE”) may establish one or more QoS flows or other types of communication sessions with the wireless network, where the QoS flows or other types of communication sessions are associated with a network slice that is associated with the traffic type. The communication sessions may include Data Radio Bearers (“DRBs”), backhaul links, protocol data unit (“PDU”) sessions, or other suitable types of communication sessions.

Abstract: A device may receive, from a source, data destined for a destination. The device may identify a protocol associated with the data. The protocol may be used to transmit the data. The device may determine whether the protocol is unsupported by the device. The device may identify control information, associated with the protocol, based on determining that the protocol is unsupported by the device. The control information may identify an action, to perform on the data, other than dropping the data. The device may perform the action based on the control information.

Abstract: A first routing instance may receive, from a second routing instance, forwarding information identifying a next-hop. The first routing instance may receive, via a component of the first routing instance, network traffic. The first routing instance may determine, based on the network traffic and the forwarding information, an interface to a component of the second routing instance. The first routing instance may provide, to the component of the second routing instance, the network traffic via the interface. The second routing instance may provide the network traffic to the next-hop.

Abstract: A first routing instance may receive, from a second routing instance, forwarding information identifying a next-hop. The first routing instance may receive, via a component of the first routing instance, network traffic. The first routing instance may determine, based on the network traffic and the forwarding information, an interface to a component of the second routing instance. The first routing instance may provide, to the component of the second routing instance, the network traffic via the interface. The second routing instance may provide the network traffic to the next-hop.

Abstract: A device may receive, from a source, data destined for a destination. The device may identify a protocol associated with the data. The protocol may be used to transmit the data. The device may determine whether the protocol is unsupported by the device. The device may identify control information, associated with the protocol, based on determining that the protocol is unsupported by the device. The control information may identify an action, to perform on the data, other than dropping the data. The device may perform the action based on the control information.

Abstract: A computing device ranks multiple routing pairs based on a current routing configuration for weighted links in a network, and ranks the multiple routing pairs based on a proposed routing configuration, different than the current routing configuration, for the weighted links in the network. The computing device compares a current rank order of a first routing pair and a second routing pair in the multiple routing pairs with a proposed rank order of the first routing pair and the second routing pair. The computing device identifies a change between the current rank order and the proposed rank order and generates a data structure that indicates the identified change between the current rank order and the proposed rank order for the first routing pair and the second routing pair.

Abstract: A method may include receiving, at a first network device, a test initiation message from a control device, wherein the test initiation message includes at least an identification of a second network device. The method may further include retrieving the identification of the second network device from the test initiation message and generating test data including at least source information associated with the first network device, destination information associated with the second network device, and timestamp information associated with a time at which the test data is generated. In addition, the method may include transmitting the test data to the second network device via a data network under test and receiving return test data from the second network device. Further, the method may include generating performance information based on the return test data received from the second network device.

Abstract: A computing device ranks multiple routing pairs based on a current routing configuration for weighted links in a network, and ranks the multiple routing pairs based on a proposed routing configuration, different than the current routing configuration, for the weighted links in the network. The computing device compares a current rank order of a first routing pair and a second routing pair in the multiple routing pairs with a proposed rank order of the first routing pair and the second routing pair. The computing device identifies a change between the current rank order and the proposed rank order and generates a data structure that indicates the identified change between the current rank order and the proposed rank order for the first routing pair and the second routing pair.

Abstract: A method may include receiving, at a first network device, a test initiation message from a control device, wherein the test initiation message includes at least an identification of a second network device. The method may further include retrieving the identification of the second network device from the test initiation message and generating test data including at least source information associated with the first network device, destination information associated with the second network device, and timestamp information associated with a time at which the test data is generated. In addition, the method may include transmitting the test data to the second network device via a data network under test and receiving return test data from the second network device. Further, the method may include generating performance information based on the return test data received from the second network device.